>>I have a situation where I'm trying to create the install disks before I know the name of the \\server\share where the app will reside.
>>
>>The installation will create a directory on the server which has two subdirectories. One contains the apps data and the other contains a workstation setup created with the setup wizard. To set up a PC, the user will run setup.exe from the server.
>>
>>I need to include a config.fpw file in the PC install which sets DEFAULT and PATH to the server but I can't include it (compressed) in the PC setup because I don't yet know the name of the share.
>>
>>Does any of this make sense?
>>
>>Once the network installation is done, the support staff could create a config.fpw file in the PC setup directory which could be copied down to each PC during the PC installation. Can I do this without having the support staff do the copy manually?
>>
>>I thought I could use the "Post-setup executable" in the setup wizard to do a COPY but it'll only call an executable.
>>
>>Thanks in advance for any help
>
>Larry,
>
>What I did involved using a post setup executable. Since I couldn't very well copy over the copy of the executable on the server (someone might be using it), I created an installation program to be copied to the user's local drive by the setup wizard. This executable was then run. It created the icon for the real program in the same group. It also modified AUTOEXEC.BAT (to set up the FOXPRWCFG environment variable) and created the CONFIG.FPW file using low level file I/O. This also served the purpose of creating a local directory for temp files. In my case, this situation was necessary, since I had one case that wasn't like all the others and I had to dynamically set DEFAULT path and PATH.
>
>The most significant downside was that the install program as well as a unnecessary runtime library were left behind. However, that seems to me to be a small price when compared to everything else.
>
>hth,
>
>George

I was hoping not to have to create another .exe. But, I may have to do exactly that.

thanks