Windows Forum

Ask something
Discussion Locked

vb Package Installation - reboot problem

0 helpful
6 replies

by muthuarumugam

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

After package the vb developed application, and installing it, at the begenning of the installation itself - installation process asked to reboot the machiene. after reboot - if we try to install - the same happen again and again.

Any help is appreciated.

Thanks in advance.

6 replies

by tjc

Try doing a ctrl+alt+del and end task on everything except "systray" and "explorer" and try the install again and see what happens. Some times open dll and ocx files will cause the problems.

by sl-campbell

First, need to know what version of VB and which service pack and on what OS the program was created with and where are you trying to install it, (OS).

The reason for asking is that I have have this problem several times and it depends greatly onwhether the system is Win95, (one problem), a Win2000, (another problem) or something else or all, (a third problem). All these problems can be resolved.

Make SURE that you are using the most recent SP of VB6 AND that the recieving PC has the most recent OS Service Pack!

My GUESS is that you are installing to a Win2000 machine and your VB6 isn't up-to-date.

If the recieving system is Win 2000, then I would say that the problem is being caused by a program that was created on a system which has later versions of one or more system files. In Windows 2000/ME, system files are protected and are not updated on the restart.
During installation the setup program detects that some system files need to updated and goes into a reboot to do this. But Win 2000 or ME does not allow an update of system files via application installation - only through a Windows update.
This percieved problem is caused by the Oleaut32.dll.
Check the date of this file in the setup list of your VB setup program and the date on the system the application is to be installed. Guess is that dll on the 'receiving system' is older.

You can either update the receiving system with a service pack that contains a version of this dll that is newer than that which setup is trying to install, or go the otherway around and include a version in your package that is equal to or less than the one on the receiving PC (use VB6 SP4 so the needed files in the VB redist folder get added - these files are inany case older than the ones on Win 2000.

(oops - need more space...)

by sl-campbell

I am tracking this question so is the above doesn't help then post a comment to your question, with more detail on VB ver./sp and OS ver./sp, and if possible info on the files and versions/dates that are listed in the bootstrap section of the setup.lst.

Merry Christmas!

This discussion is closed to new replies.