>>Ed - the switches worked great. Thanks ever so much. One thing I don't understand about the installation process is why it leaves a setup subdirectory in the application directory after setup has run. I've never encountered this before. I am using the network setup - zipping it up - sending it out to the field via email (they hate floppies) where it will be copied to a temp file and unzipped. They will then execute the bat file with setup.exe /Q0 which will do the "invisible install". This all appears to work correctly except it not only installs the application in the appication directory but a setup subdirectory is installed in the application directory also. I would prefer not to have the setup subdirectory. Any thoughts?
>>
>
>I believe it does that to provide you with a way of uninstalling by invoking the SETUP.EXE in that directory interactively or with the /U or /UA parameters. If you select your application in the Control Panel applet Add/Remove Programs, it invokes the program in the SETUP subdirectory to permit reinstallation or uninstallation. If you don't want it, you can simply delete it, but then you'll not be able to invoke the uninstall from Control Panel's Add/Remove Programs.
>

One more thing - if you don't mind hacking the .STF (completely undocumented and potentially very unsafe) you can eliminate the SETUP directory creation and copies; you'll want to edit the line called UnInstall to eliminate all the group actions except the WriteTableFile line. In one of my install scripts, line 12 labelled references a number of other lines in a Group statement. If you blank out all the group line references there -except- the WriteTableFile line, which records the results of the setup in SETUP.STF, none of the other files (there's a CopySection and some CopyFile lines, as well as two AddRegData lines that create the uninstall registry entries; these line numbers should be blanked in the Group statement labelled Uninstall). Back up before trying this - there might be other, unwanted side-effects. I normally leave the subdirectory to provide an uninstall; I can usually spare the space.


>>Thanking you in advance for your assistance.
>>
>>Gaylen
>>
>>
>>
>>
>>>Ed - Where would you suggest I look for documentation on the /Q0 and /Q1 switches. I could not find anything on them in the resource materials I have.
>>>
>>
>>>The reference material for Office contains a description of Office97's command line switches, most of which are available to VFP Setup Wizard's SETUP - you might want to check Appendix B of the Office 97 docs after listing the supported switches. The last time I checked, Setup Wizard supported:
>>/A Administrative (puts setup in place for network installs)
>>/G filename Generate installation log file
>>/Q[0|1|T] Quiet mode - several UI options
>>/QN[0|1|T] Quiet mode with reboot suppression
>>/R Reinstall
>>/U[A] Uninstall [A removes all shared components as well]
>>/X filename Set network log location to track install instances
>>/Y Install without copying files
>>
>>
>>
>>>The Office 97 reference goes into a bit more detail. Most of what I've learned about it came from experimentation and hacking the install files before I switched to wrapping a Setup Wizard runtime install with InstallShield, letting InstallShield manage everything but the runtime file install (I launch it inside an InstallShield script with /QNT to suppress user input and the Setup Wizard display screen.)
>>
>>>If you use non-interactive installs with the /Q options, you'll need to check for a SETUP.STF in the default target directory, and either erase it or use the /R command line switch as well.
>>
>>>Again thanks for coming to my aid
>>>
>>>Gaylen