dll's that crash the OS

[wolfykaos]

We make exes in a machine with Win 2000, VB 6 (service pack 4) and Install Shield 3, and then when we install it in Win 98 we've got 2 problems:

1) When we make the setup program of our app the instalation it looks ok, but when we install and then reboot it appears: "RUNDLL -> Error loading POWRPROF.DLL The System cannot find the file especified...". We don´t include this DLL in our setup program, cos it already exists on the system (and we doesn´t need it also for nothing). This error disappears using MSCONFIG.EXE, desactivating "loadingPowerProfile" options, but we need to make a clean installation, without error messages.

2) Also, when we reboot after running the setup program the OS request USERENV.DLL, then we tried to include it in the setup program, install again, reboot again, and it says: "USERENV.DLL is attached to NTDLL.DLL: rtlsubautoritysid export that not exists". Then we included NTDLL.DLL in our setup program, install, reboot, and it says: "USERENV.DLL is attached with KERNEL32.DLL: privcopyfileexw export that not exists". Then we included KERNEL32.DLL in our setup program, install, reboor, and then the OS cannot boot and finally quits saying: "ERROR LOADING KERNEL".

Our setup program worked correctly some time ago, but in any moment it started to fail (we don´t know why or what). We were using win98 in the machine we use to make setup programs, and someone told us to use Win2000 to make them, but it still fails.

We know this seems so complicated and ugly, but we need a hand, please.


Thanks a lot

 

[mainegeek]

Does the built program work on the platform in which it was created? Also, when building include all required files and
have them install to built programs directory or sub directies.This might eliminate any shared files or version conflicts. After installation,verify paths of installed files. Create an uninstall as well.

 

[wolfykaos]

Hi Mainegeek:

- It would be so dangerous to try to install in the machine we use to program (and create exes), because if it crashes the system we'll have to reinstall a lot of things, and first do a very careful backup.
- We've tried, as you said, to make installshield put the DLL's into different folders (not system folders), and it also crashes... Perhaps InstallShield puts another DLL's in Windows/system that can't be controled.
- We cannot do an uninstall if we doesn't know what are we doing wrong... It seems like InstallShield does something more than installing DLL's and OCX.

Any other clue?

Thanx a lot for your help, I'm working on this for several weeks and I'm desperated.


Cheers