Problems during installation

 

It may happen that the first message after start of the Setup program be the following:

 

Translation: Some system files of the used system are not up-to-date. Click on Ok to update automatically the said files. Before to executenewly the installation it will be necessary to rerun Windows. Click on Cancel to get out from the installation without updating.

This message is issued when one or more of the files listed in the section [Bootstrap Files] of the file Setup.ini and already present on the target computer is of a lower version than the instance present in the installation package and is actually running. Here I report a copy of this file list.

[BootStrap Files]

File1=@VB6STKIT.DLL,$(WinSysPathSysFile),,,8/5/98 12.00.00 AM,102912,6.0.81.69

File2=@VB6IT.DLL,$(WinSysPath),,$(Shared),10/2/00 12.00.00 AM,122128,6.0.89.88

File3=@msvbvm60.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,5/27/00 1.10.18 AM,1388544,6.0.88.77

File4=@STDOLE2.TLB,$(WinSysPathSysFile),$(TLBRegister),,7/19/02 9.34.00 AM,16896,2.40.4518.0

File5=@OLEAUT32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,7/19/02 9.34.00 AM,626960,2.40.4518.0

File6=@OLEPRO32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,7/19/02 9.34.00 AM,164112,5.0.4518.0

File7=@asycfilt.dll,$(WinSysPathSysFile),,,7/19/02 9.34.00 AM,143632,2.40.4518.0

File8=@COMCAT.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,6/1/98 12.00.00 AM,22288,4.71.1460.1

File9=@MSVCRT40.DLL,$(WinSysPathSysFile),,,6/1/98 12.00.00 AM,326656,4.21.0.0

File10=@Mscomctl.ocx,$(WinSysPath),$(DLLSelfRegister),$(Shared),6/6/02 6.13.00 PM,1077344,6.1.95.45

File11=@CMCTLIT.DLL,$(WinSysPath),,$(Shared),8/5/98 12.00.00 AM,107008,6.0.80.22

 

After choosing OK the following message will appear:

 

 

Translation: do you want to restart Windows now? If you choose ‘No’ then it will not be possible to restart the installation program until the next system restart.

Normally you will answer Yes and the program will be able to update the concerned system files. But by no means I would accept the obligation to guarantee a correct result.

 

It should in effect be considered that I have no control on this phase of the installation process. In effect this phase is under control of the setup.exe program, which is distributed by MicroSoft with VB and only as binary. The rest of the installation program is managed by a so-called Setup1.exe program for which the VB sources are available. In effect my version of Setup1.exe program is an in-depth customisation of the original by MS.

 

I have tried this setup program on many computers (W95/98, NT, 2000) without creating problems on the computer SW. But sometimes the installation has not got success.