======================================================================= New: As of 20-October-2009, the Installers for VFP6, VFP7, VFP8 SP1 and VFP9 SP0, SP1, SP2 have been recreated to include the latest hotfixes and security updates! wOOdy ======================================================================= This ReadMe explains the usage and commandline-switches for the provided Microsoft Visual FoxPro Runtime installers. After you have installed the VFP runtime once, you then only need to just copy your Application into any directory and it works.. If you would use additional thirdparty components like ActiveX controls, you still have to install them on your own. Explanation of the filename: ============================ The filename of our runtime installers is built by three parts: * Visual FoxPro version (ie. VFP9) * Servicepack level (ie. SP1) * Runtime identifier (RT) For example, the filename 'VFP9SP0RT.exe' stands for runtime installer of Microsoft Visual FoxPro 9.0 without any servicepack. Installation: ============= Just download the runtime you need for your own application to any folder on your machine and execute the installer by either double- clicking the file or [Start] [Run] [OK] The runtime installer provides you a dialog to choose the several VFP specific runtime files (required ones are pre-selected), and to specify the installation directory. The common path where the runtime should be placed as a recommendation by Microsoft is pre- defined. Silent installation: =================== Additionally to the normal execution, our setup routines offers an installation mode without any user interaction. This is called 'silent mode'. The silent mode is controlled by commandline-switches and an optional response file. Command line options: -------------------- Here's an overview of possible commandline options: Option Function ================================================================== /M Runs installation in manual mode, prompting for system directories such as Windows, System, etc. /M=filename Specifies a response file for installation. /S Silent mode, automatic mode with no user choices. /T Install in testmode (no files are really installed) /X pathname Extracts files to pathname. /Z pathname Extracts files to pathname, then reboots. Response file: -------------- While using the commandline option "/M=filename", you are able to specify a response file in order to define components and path information, if you need different settings. The response file contains pairs of keys and values to control the installation process. Currently we provide three keys in our setups: Key Function ================================================================== ZIEL Destination path of runtime files. The default is %CommonFiles%\Microsoft Shared\VFP. SELECT_RT Core runtime files of Visual FoxPro. This key controls the installation of EXE, MTDLL. VC++ runtime files and (since VFP 9.0) the report applications. Default is 'ABCabc' SELECTION Language dependend runtime files of Visual FoxPro. Default is 'ABCa' The keys SELECT_RT and SELECTION use characters to correspondent with the option in the installer. This way, 'A' stands for first option, 'B' for second, and so on... Using lower characters just disables the option in the dialog. Here is a sample how this response file (ie. setup.txt) looks like: ZIEL=C:\Program Files\MyApp SELECT_RT=ABCDabc SELECTION=ABCDEFa To use this response file, call the installer like this: VFP9SP0RT.exe /S /M=setup.txt Feedback: ======== Any feedback related to the VFP runtime installers is welcome. Please don't hestiate to write a mail to support@prolib.de. Disclaimer: ========== This information and the installers are provided "AS IS" with no warranties and confers no rights. The installers are provided as a courtesy of ProLib Software GmbH, Germany for making your life easier. You are using them on your own risk and you are still responsible for following the Microsoft Visual FoxPro license terms. BeerWare: If our work saved you some hassle, feel free to pay us a beer when you meet one of us at any conference... Kind regards, ProLib Development Team.