>>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
>
>It's much better to set PATH/DEFAULT using values stored in distributed locally (as part of installation package) Config.dbf. Your app should also has configuration utility allowing to set this values when a user will start the app first time.

Thanks, I think you beat the 35 second barrier!