Hi All:
Go to Microsoft site or any Search site (www.google.com) and search for
Q191096 or Q279764.

Below is a reply from somebody to the news group regarding this problem,
hope it help
============================================================================
==========

An extra point: If you end up trying to install a package with this problem,
there is a quick workaround to get you out of an immediate jam... Edit the
Setup.lst file to remove the offending files.

Here's an excerpt from a Setup.lst on my machine:

**************

[Bootstrap]
SetupTitle=Install
SetupText=Copying Files, please stand by.
CabFile=ConfigApplet.CAB
Spawn=Setup1.exe
Uninstal=st6unst.exe
TmpDir=msftqws.pdw
Cabs=1

[Bootstrap Files]
File1=@COMCAT.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,5/31/98 12:00:00
AM,22288,4.71.1460.1
File2=@VB6STKIT.DLL,$(WinSysPathSysFile),,,7/15/00 12:00:00
AM,101888,6.0.84.50
File3=@STDOLE2.TLB,$(WinSysPathSysFile),$(TLBRegister),,7/21/00 12:05:02
PM,16896,2.40.4514.1
File4=@ASYCFILT.DLL,$(WinSysPathSysFile),,,7/21/00 12:05:02
PM,143632,2.40.4514.1
File5=@OLEPRO32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,7/21/00
12:05:02 PM,164112,5.0.4514.1
File6=@OLEAUT32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,7/21/00
12:05:02 PM,614672,2.40.4514.1
File7=@MSVBVM60.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,8/21/00
12:00:00 AM,1388544,6.0.89.64
**************

The Bootstrap Files section is the killer. The offending file in Win2K
installations is OLEAUT32.DLL, so if you are on Win2k, remove it from the
list. You should end up with the following:

[Bootstrap Files]
File1=@COMCAT.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,5/31/98 12:00:00
AM,22288,4.71.1460.1
File2=@VB6STKIT.DLL,$(WinSysPathSysFile),,,7/15/00 12:00:00
AM,101888,6.0.84.50
File3=@STDOLE2.TLB,$(WinSysPathSysFile),$(TLBRegister),,7/21/00 12:05:02
PM,16896,2.40.4514.1
File4=@ASYCFILT.DLL,$(WinSysPathSysFile),,,7/21/00 12:05:02
PM,143632,2.40.4514.1
File5=@OLEPRO32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,7/21/00
12:05:02 PM,164112,5.0.4514.1
File6=@MSVBVM60.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,8/21/00
12:00:00 AM,1388544,6.0.89.64

Note the renumbering for MSVBVM60.DLL. You MUST renumber the entries so that
they form a continuous sequence beginning at File1.

Other files in [Bootstrap Files] can give you problems, and in my experience
it is because they are already present on the target system, and functioning
just fine. So, remove their entries from Setup.lst too. After this, your
installation should proceed without a hitch (or with less hitches; the
deployment packages are pretty cruddy really :-).

Emlyn

> -----Original Message-----
> From: Yehuda Rosenblum [mailto:Yehuda@I...]
> Sent: Thursday, 13 June 2002 1:17 AM
> To: professional vb
> Subject: [pro_vb] Re: Package and deployment question
> 
> 
> I have run into this issue.  I have posted previously a 
> solution to this
> issue.  This is caused by the system files in the package being to
> advanced.  Windows does not always work properly when it comes to
> switching system files.  The way we got around it is to use 
> older files
> in the package.  This is done by storing a copy of older files in
> \Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\Redist.
> This is the first place the P & D wizard looks.  If it does not find a
> copy of the required system file there it goes to the Winnt\system32
> directory.  I keep an old version of the system files that are usually
> used (i.e. MSVCRT.DLL, etc.) in the \Program Files\Microsoft Visual
> Studio\VB98\Wizards\PDWizard\Redist directory and let my 
> clients upgrade
> their system files when they wish.
> 
> -----Original Message-----
> From: Frankie LOH [mailto:frankieloh999@h...] 
> Sent: Wednesday, June 12, 2002 11:23 AM
> To: professional vb
> Subject: [pro_vb] Re: Package and deployment question
> 
> Hi;
> 
>   I also encountered the problem previously but my customer is in NT.
> Dr. 
> Niaz, may I ask for the site address to have a look at the article?
> 
> Thanks
> 
> 
> 
> -----Original Message-----
> From: Dr. Niaz Mohammed [mailto:mniaz@k...]
> Sent: Sunday, April 21, 2002 12:12 AM
> To: professional vb
> Subject: [pro_vb] Re: Package and deployment question
> 
> 
> Please read Microsoft Article Nos. Q279764 and Q191096 for a soluition
> of
> the problem.  Two solutions of the problem are: (1) either install a
> service
> pack of Windows 2000  (assuming you are installing on Win2000) before
> installing your package, (2) Create the package on a Windows 
> 2000 system
> that does not have any service pack (of Windows)installed.
> 
> Hope this helps
> 
> Niaz
> 
> ----- Original Message -----
> From: "tom carr" <tomcarr1@y...>
> To: "professional vb" <pro_vb@p...>
> Sent: Thursday, April 18, 2002 8:25 PM
> Subject: [pro_vb] Package and deployment question
> 
> 
> >I am deploying a program using package and deployment 
> wizard.  On some
> >computers it works fine.  On others it gives this message:
> >
> >"Setup can not continue because some system files are out of date on
> your
> >computer.  Click OK if you would like Setup to update these files for
> you
> >now.
> >You will need to restart windows"
> >
> >The user clicks OK and immediately gets a message that says "Do you
> want
> to
> >restart windows now ? "
> >
> >The user clicks Yes and restarts windows, runs setup again 
> and gets the
> >same
> >message again.  It seems the computer was never updated with any new
> files.
> >What is going on ?
> >
> >This has happened twice, both on Win2000 computers.
> >
> >Also, do you think this problem would be eliminated if we 
> bought a cope
> of
> >Wise or Installshield and used one of those instead of Package and
> >Deployment wizard ?
> >
> >
> 
> 
> 
> _________________________________________________________________
> MSN Photos is the easiest way to share and print your photos: 
> http://photos.msn.com/support/worldwide.aspx
> 
> 
> 
> 


***************************************************************************
Confidentiality: The contents of this email are confidential and are
intended only for the named recipient. If the reader of this e-mail is not
the intended recipient you are hereby notified that any use, reproduction,
disclosure or distribution of the information contained in the e-mail is
prohibited. If you have received this e-mail in error, please reply to us
immediately and delete the document.
Viruses: Any loss/damage incurred by using this material is not the sender's
responsibility. Our entire liability will be limited to resupplying the
material. No warranty is made that this material is free from computer virus
or other defect.





-----Original Message-----
From: Zulfazli [mailto:Zulfazli@l...]
Sent: Tuesday, July 23, 2002 10:02 AM
To: professional vb
Subject: [pro_vb] RE: Package and Deployment Wizard


Hi Carolyne,
I've got the same problem three months ago. In my P&D i include the
MDAC_TYP.EXE (v. 2.7). And then it installed the Ado lib in client without
confirming the current version of ADO in client.
After it (P&D) finished it's job, i got a very bad dream in my live. The
system always wanted to restart or got hang. I must reinstall the o/s
system. And i got an answer from this forum, thanks buddy, that point me to
seperate the ado installation from my P&D Installer system.
And whenever i want to install ado in my client that will used by my app, i
install it (ado) first, and then my application.
And I always to make sure that i have unchecked the files : msado25.dll,
msado25.lib (or similiar ado files), mdac_typ.exe, msvcrt.dll. So my app
installer will run smoothly.

HTH
Zulfazli

> -----Original Message-----
> From:	Carolyne Whiting [SMTP:carolyne.whiting@b...]
> Sent:	Friday, July 19, 2002 9:23 PM
> To:	professional vb
> Subject:	[pro_vb] Package and Deployment Wizard
> 
> I've written a VB6.0 program that uses ADO 2.7.  I've compiled it and 
> packaged it.  I have it on the network to download on each users machine.
> 
> I'm getting the following error "Setup cannot continue because some system
> 
> files are out of date on your system.  Click OK if you would like setup to
> 
> update these files you now.  You will need to restart Windows before you 
> can run setup again.  Click cancel to exit setup without updating system 
> files."  I click the Ok and reboot, but I still continue to get the same 
> message.  Any ideas?
> 
> ---
> Visual C# - A Guide for VB6 Developers
> This book will make it easy to transfer your skills 
> from Visual Basic 6 to C#, the language of choice 
> of the .NET Framework.
> http://www.wrox.com/ACON11.asp?ISBN=1861007175&p2p0059
> 


---
Visual C# - A Guide for VB6 Developers
This book will make it easy to transfer your skills 
from Visual Basic 6 to C#, the language of choice 
of the .NET Framework.
http://www.wrox.com/ACON11.asp?ISBN=1861007175&p2p0059