Prev: Dependency File out of date
Next: Permission of EXE ActiveX running IIS-W7 Classic ASP
From: Dennis Rose on 10 Feb 2010 14:20
Using VB5. Windows must be restarted after installing my VB5 program on a Win
XP computer. This is something that has not happened before.

What I have done different is to include the vbSendMail.dll and the
mswinsck.ocx for the first time.

When I run the VB5 setup wizard to create the application, the wizard hangs
up for about 1 minute after the progress bar reaches 100%, and then completes
OK(this is new).

After I install my application on a computer, I get the message "You must
restart Windows in order to complete setup"(this is new).

I have checked Google and can't find anything that applies to my situstion.

What could be causing a computer to have to be restarted here? And can I do
anything to prevent this restart situation?
From: Paul Clement on 10 Feb 2010 15:07
On Wed, 10 Feb 2010 11:20:01 -0800, Dennis Rose <DennisRose(a)discussions.microsoft.com> wrote:

� Using VB5. Windows must be restarted after installing my VB5 program on a Win
� XP computer. This is something that has not happened before.
�
� What I have done different is to include the vbSendMail.dll and the
� mswinsck.ocx for the first time.
�
� When I run the VB5 setup wizard to create the application, the wizard hangs
� up for about 1 minute after the progress bar reaches 100%, and then completes
� OK(this is new).
�
� After I install my application on a computer, I get the message "You must
� restart Windows in order to complete setup"(this is new).
�
� I have checked Google and can't find anything that applies to my situstion.
�
� What could be causing a computer to have to be restarted here? And can I do
� anything to prevent this restart situation?

I believe that it means that there are files the setup program needs to replace that are still in
use.

When the system reboots Windows has a mechanism that will replace them automatically.


Paul
~~~~
Microsoft MVP (Visual Basic)
From: David Kaye on 10 Feb 2010 16:24
Paul Clement <UseAdddressAtEndofMessage(a)swspectrum.com> wrote:

>I believe that it means that there are files the setup program needs to replace
> that are still in
>use.
>
>When the system reboots Windows has a mechanism that will replace them
> automatically.

This also means that the file(s) are in use with some other program at the
time of installation. Since VB5 is an earlier version and XP has files that
relate to VB6, I'd suggest that he go back and check each and every version
the VB installer is trying to put in just to make sure that it's not trying to
remove an earlier version of a file. Replacing a later file with an
earlier is not *supposed* to happen, but I've seen it happen.

From: Helmut Meukel on 10 Feb 2010 17:38

"Paul Clement" <UseAdddressAtEndofMessage(a)swspectrum.com> schrieb im
Newsbeitrag news:o046n55m4f235jlc69jcbvldmhpg4pb0sk(a)4ax.com...
> On Wed, 10 Feb 2010 11:20:01 -0800, Dennis Rose
> <DennisRose(a)discussions.microsoft.com> wrote:
>
> � Using VB5. Windows must be restarted after installing my VB5 program on
> a Win
> � XP computer. This is something that has not happened before.
> �
> � What I have done different is to include the vbSendMail.dll and the
> � mswinsck.ocx for the first time.
> �
> � When I run the VB5 setup wizard to create the application, the wizard
> hangs
> � up for about 1 minute after the progress bar reaches 100%, and then
> completes
> � OK(this is new).
> �
> � After I install my application on a computer, I get the message "You
> must
> � restart Windows in order to complete setup"(this is new).
> �
> � I have checked Google and can't find anything that applies to my
> situstion.
> �
> � What could be causing a computer to have to be restarted here? And can
> I do
> � anything to prevent this restart situation?
>
> I believe that it means that there are files the setup program needs to
> replace that are still in
> use.
>
> When the system reboots Windows has a mechanism that will replace them
> automatically.
>
>

This always happens if the version is in use.
With mswinsck.ocx this could be the case.

I just searched an older multi boot PC with NT4 Workstation, NT4 Server
and 2 versions of Win2000 on it for mswinsck.ocx.
Found 6 different versions:
version remarks
5.0.37.14 VS97-CD (=VB5)
5.1.43.19 VS97-SP3
6.0.81.67 VS98-CD (=VB6)
6.0.88.4 VS98-SP4
6.0.89.88 VS98-SP5
6.1.97.82 VS98-SP6

Hopefully your setup checked for version and didn't replace a newer one.

HTH.

Helmut.

 | 
Pages: 1
Prev: Dependency File out of date
Next: Permission of EXE ActiveX running IIS-W7 Classic ASP