Calling all gurus. Application distrubution issue:
Posted on 2002-05-08
I have spent a year getting an application ready to market to the general public. One fear I have had is messing up someone's machine with the installation of my app. I am developing on an XP home version machine. My first install attempt on Windows 98 on my kids machine hosed it - exactly what I have feared it. He could not boot up Windows 98 successfully afterwards - until I put back the old DLL's. The package and deployment wizard included msvcrt.dll and some other OLE etc. components. The msvcrt one was the problem child. I know I can remove this and anything else in the bootstrap files section of setup.lst(except the vb runtime) - but will that endanger my app from running? Also I'm using DAO for database access.
So my question is - Can I create a setup package that will be guaranteed not to mess up someone's windows environment and still be reasonably sure the app will run ? Of maybe better posed - how do I minimize the changes of the first and maximize the chances of the 2nd?