>>Which temp files are we talking about? The one's created by the post setup executable or the one's created by the application itself? If it's the former, I wouldn't be concerned about them since they'll be deleted when the program tereminates.
>
>I was talking about the temp file written by my post-setup executable. The executable is on the CDROM, and no matter what I do concerning a temporary directory, it always tries to write a tempfile to the whatever directory the post-setup executable is in.
>
>Right now the (messy) installation procedure is
>
>Run d:\bgtol\setup\setup.exe (created by the VFP setup wizard)
>1. The app gets copied to wherever the user wants it
>2. Treeview gets installed
>3. IE control gets installed
>
>Run d:\bgtol\setup2\setup2.exe (created by me, a compiled VFP .exe)
>1. The app asks where the user just installed setup.exe. Registry is written for application path and data path and temp path.
>2. The app installs fonts
>
>Then the user can run the app. This works fine if the entire CDROM contents are on the HD. But if setup2.exe is run from the CDROM, VFP complains it cannot write temp files and quits. So my workaround is to have the user run setup2.bat, which does a "copy *.* %temp%" and then a "%temp%\setup2.exe" and the program runs fine.
>
>My main app actually doesn't have a problem with temporary files; it's going to %temp% fine. It's the mini-executable I wrote. Maybe it's time to dust off the Perl/Tk docs, this is crazy.
>
>Actually, I would really like a good installer that would let me write my Registry settings and install my fonts and register my controls all-in-one.
>
There are any number of good installers available - I use InstallShield Pro, but the majority of what you need is present in InstallShield Express.
Be aware that
any installer that does more than minimal configuration is going to require scripting, and will have some learning curve to it; product like IS Express, with strong wizards, much less than scipt only products.
And there's always the WSH.
>Thanks.
