Great! Well it most assuredly crashes the target system if its not the same as the development one. (hee hee). Have created an installshield app to do the deployment installation and it was in this testing I discovered the crash situation. What a show stopper it was! Glad we use imaging and removable drives to rebuiild test platforms. Having removed those files from the install everything seems to work in the sterile environment. Now for the beta testers...

>You definitely want to leave those out! You never want to distribute operating system core files with your app. Those files are core OS files
>for 95, 98, NT and above. Replacing them will certainly crash the target system (and violate MS license agreements, those long winded agreements
>that everyone just hits 'yes' to)
>
>You were having problems with the OLEAUT and OLEPRO files, which you can redistribute. Updating them is tough with the PDW because it
>itself was written in VB and uses them. If you manually include them in the wizard though, it should install them after rebooting the system.
>
>HTH,
>Ed
>
>>OK so I can leave them out without fear. Because when I include them out 95 test machines give us a "blue screen of death" and it has to be re-imaged.
>>
>>>>Looking at my deployment installation. I have listed in my dependancy file:
>>>>GDI32.DLL
>>>>KERNEL32.DLL
>>>>USER32.DLL
>>>>Is anyone including these in their setups? If so what are the Windows 95 vs 98 issues? My thanks in advance.
>>>
>>>These are dependencies but are not included in the CAB file. So no problem between Windows flavor!!!