>>I'm going through a built set up now myself again and I'm cursing the Installshield setup. I think it's very frustrating that Express gets you there 95% of the way and then leaves you hanging...
>>
>>My biggest problem with it is that it builds very large installs. I ended up
>
>I agree. My 50 meg setup ended up being nearly 100 megabytes. The most frustrating thing for me was that they disabled the dynamic file loading so that everytime you build you have to manually load all the files. They say that the full version of InstallShield express would do the dynamic load, but I had nothing but trouble with the trial version (be sure you try it before you buy it) I build as often as once per day (sometimes more) so this made this product useless for me.
>
>I ended up writing my own installer in VFP. After I got into it, I was surprised how simple it was. I only needed 6 screens. I just setup a separate project for it: call it Setup.pjx and it will easily generate setup.exe which you can put in the root of a CD along with autorun.inf and have a professional looking/acting installer. As far as registering the dll's, there are plenty of good references here on UT and it is very simple. Mine will put a shortcut anywhere and it is easy to autodetect the operating system so you know the differences. I even found out how to put shortcuts in WinXP (not that straight forward depending on how the end user has things setup).
********
I forgot to mention that you need to be sure to put the VFP runtime dll's in the root of the CD also. They do not need to be registered on the enduser computer for the setup.exe to run. Once your VFP setup.exe begins to run, it can do the registering for other dlls, such as dynazip, etc that you may need.