>I'm learning but I'm still not happy with all of the requirements. For example, we used to be able to distribute a demo on 2 diskettes. When the user was finished, all they had to do was delete one folder and their computer was as good as new. Now it appears we will have to go to a CD, intstall files in multiple folders, and register a bunch of files. This means we will have to spend some time developing a decent uninstall program that will fully clean up the mess because I rarely see an uninstall program that deletes everything.
>

I gave up on distribution of sizable applications on floppy long ago, for a number of reasons, not the least of which was the number of calls Igot saying that someone could not read what was on the floppy. The CD-ROM distribtion medium is pretty-well as ubiquitous a medium for WInApps as youcan find; Ican't remember thelasttime I got a call from someone sayingthat there wasn't a CD-ROM drive available ontheir system. Media costs are reasonable, and a single CD lets you put things that you'd like to have present on the target system at hand; for example, I include the Windows Script Host self-installer and the PowerToys TweakUI with my apps; WSH I require, and TweakUI is there for convenience.

>I think it is very rude for a developer to scatter files around someone's computer then have the nerve to tell them in the uninstall program that "some things may have to be manually deleted". I'm not going to place our company in that low life class.
>

That's largely a function of the install tool; InstallShield is pretty good about tracking things that it installs or changes,and provides amechanism for the developer toextend or repalce that functionality. Some things that accompany an app should not be removed when the app is uninstalled; user-developed data is one example.