Several ways to attempt to "fix" this. I say attempt because although
there is a good chance these methods will work, it can't be 100% garanteed.
Install SP3 on the Win 2k pro PC
Go to Windows Update and get all the updates for the Win OS.
Locate, download and instal lthe vb runtimes. I looked for these in Google,
but
I am not sure which one is the right one. This one looks like it is it:
http://www.karenware.com/powertools/runtimes.asp#vb6
You don't specify the SP level of VB. The above link is for VB6, SP5
And the hard, hard way! This involves downgrading the install package.
First, copy the setup package (including the support folder) to the target
computer.
Now locate the file makecab.exe in your develepment PC and copy it
to a diskette or some other media.
When the package is created, a Support folder is also created that contains
the CAB's contents. Locate the setup.lst file INSIDE the Support folder.
Locate this section within setup.lst:
[Bootstrap Files]
[email protected],$(WinSysPathSysFile),,,7/15/00 1:00:00
AM,101888,6.0.84.50
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,5/31/98 1:00:00
AM,22288,4.71.1460.1
[email protected],$(WinSysPathSysFile),$(TLBRegister),,6/3/99 1:00:00
AM,17920,2.40.4275.1
[email protected],$(WinSysPathSysFile),,,3/8/99 1:00:00
AM,147728,2.40.4275.1
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,3/8/99 1:00:00
AM,164112,5.0.4275.1
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,4/12/00 1:00:00
AM,598288,2.40.4275.1
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,8/18/01 7:00:00
AM,1388544,6.0.92.37
This list in your file may vary, but most likely it is one or more of these
files that is causing
the problem. When the message comes up, there is a second message box that
tells you
which file caused the problem. Move, do not close, each message until you
find the one
that states which file is the culprit
Locate the named file in the target machine and copy it to the copy of the
package that you
made. Copy the file to the Support folder. The previous file will be
replaced.
Now right click the just copied file and display it properties. You are
interested in:
The creation date and time
the file size in bytes
the version
Locate the file name in the setup.lst file and replace the creation date,
size and version
with the new data from the copied file. Do not make a mistake, this is
critical.
Save the modified setup.lst.
Locate the .BAT file. Its name should the the same as the project's. Edit
this file
with notepad to correct the makecab.exe file path. Save and run. This will
create a
new cab file.
Now run Setup again. The problem will be corrected, but if another file is
out of
date, the problem will present it self again for that file (and each one
that is out of
date). You will have to repeat the process of copying the file to the
support folder,
modifying the setup.lst file, creeating the new cab and rerunning setup.
This last method is so complicated (but doable!) that you may wonder why I
bothered
to document it. Well, if you have makecab.exe, it can help you get through
an
installation if there is no SP readily available or if the SP install does
not fix this. This
procedure saved my tush once, as I was rehearsing the install of one or our
packages
and this error came up.
I found out that to be fully prepared, you should burn a CD with your
package, including
the support folder, makecab.exe and the latest SPs for Win XP and 2K.
Additionally,
if you ordered it, the critical updates CD wont hurt either ;-)
Good luck.
Saga
pACKAGE INSTALLATION PROBLEM IN WIN 2000 said:
WE HAVE MADE A PACKAGE IN VB 6.0 IT IS WORKING IN NICE IN WIN 98 SE. AND
IT IS WORKING WELL IN WINDOWS 2000 SERVER SP3.
IT IS HAVING PROBLEM IN WINDOWS 2000 PRO. INSTALLATION. SYSTEM CONF. ( P4
1.8 GHz. 256 MB DDR.) NO SERVICE
PACK. WHILE INSTALLATION IN WINDOWS 2000 PRO IT IS GIVING ERROR MESSAGE,
"SOME OF THE FILES IN THIS SYSTEM IS OLD, IT NEED TO BE RESTARTED." EVEN
AFTER RESTART IT IS GINVING THE SAME ERROR MESSAGE.
