Re: Setup Error on Friends Computer
From: Ken Uzzell (kevala_at_pacific.net.au)
Date: 05/27/04
- Next message: Jeff Johnson [MVP: VB]: "Re: Why are some SQL functions not available?"
- Previous message: AustinMN: "Re: Recommended Fonts for Forms"
- In reply to: Randy Birch: "Re: Setup Error on Friends Computer"
- Next in thread: Grahammer: "Re: Setup Error on Friends Computer"
- Reply: Grahammer: "Re: Setup Error on Friends Computer"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 27 May 2004 11:44:26 +1000
Thanks Randy,
I updated from SP3 to SP5, but after reading the info you supplied it
appears my friend may have windows system files on another drive.
I'll see how he goes with SP5 and I'll forward the info in the kb so he is
aware of potential problems with different drives.
Thank you,
Ken
"Randy Birch" <rgb_removethis@mvps.org> wrote in message
news:OqUeCQ3QEHA.396@TK2MSFTNGP12.phx.gbl...
> There are a couple of possible problems. Read these, and ignore for the
most
> part the Applies to operating systems. Presented in no particular order.
> The search term I used, if you want to find other similar articles, was <
> "oleaut32" and "out of date" > (http://search.microsoft.com)
>
> --
>
> Randy Birch
> MVP Visual Basic
> http://vbnet.mvps.org/
> Please respond only to the newsgroups so all can benefit.
>
> --------------------------------------------------
> Knowledge Base
>
> You receive a "Setup cannot continue because some system files are out of
> date" error message if you use the Package and Deployment Wizard in
> Microsoft Visual Basic 6.0
> PSS ID Number: 831491
> Article Last Modified on 1/12/2004
>
>
> The information in this article applies to:
>
>
> Microsoft Visual Basic Enterprise Edition for Windows 6.0
> Microsoft Visual Basic Professional Edition for Windows 6.0
> Microsoft Visual Basic Learning Edition for Windows 6.0
>
>
>
> SYMPTOMS
> Your computer is running a version of Microsoft Windows 2000, such as
> Windows 2000 Service Pack 2 (SP2). You try to install a Microsoft Visual
> Basic 6.0 application that you package by using the Package and Deployment
> Wizard (PDW) on an earlier version of Windows 2000, such as Windows 2000
> SP1. You receive the following error message:
> 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 for you
now.
> You will need to restart Windows before you can run setup again. Click
> cancel to exit setup without updating system files.
> If you click OK, Windows 2000 restarts and then you receive the error
> message again.
>
> Note On a computer that is running a version of Windows 2000, if you try
to
> install a Visual Basic 6.0 application that you package by using the PDW
on
> Microsoft Windows XP, similar behavior may occur.
> CAUSE
> Deployment package that is created on Windows 2000
> On a computer that is running a version of Windows 2000, if you try to
> install a Visual Basic 6.0 application that you package by using the PDW
on
> an earlier version of Windows 2000, the PDW tries to update the system
files
> of the destination computer. However, Windows 2000 tries to guard its
system
> files. Therefore, after every time you restart the computer, the PDW
cannot
> update these system files and the application installation cannot
complete.
> The behavior that is mentioned in the "Symptoms" section of this article
> occurs.
>
> You can install the latest Windows 2000 service pack to update system
files.
> However, in some scenarios, the development computer may contain specific
> system files that have later version numbers than the system files that
the
> destination computer contains. In this scenario, the PDW tries to update
the
> system files and then prompts you to restart the computer. Windows 2000
does
> not permit the PDW to replace system files. Therefore, after you restart
the
> computer, the PDW detects the old system files again. For example, this
> problem occurs if the development computer contains a later version of the
> Oleaut32.dll file than the destination computer contains.
> Deployment package that is created on Windows XP
> On a computer that is running a version of Windows 2000, if you try to
> install a Visual Basic 6.0 application that you package by using the PDW
on
> Windows XP, the Setup package that contains version 7.0.2600.0 of the
> Msvcrt.dll file tries to replace the Msvcrt.dll file that the destination
> computer contains. Because Windows 2000 does not permit the PDW to replace
> system files, the PDW cannot update this file. Therefore the PDW prompts
you
> to restart the computer to update the Msvcrt.dll file. After you restart
the
> computer, the PDW still cannot update this file and the application
> installation cannot complete. The behavior that is mentioned in the
> "Symptoms" section of this article occurs.
> RESOLUTION
> Deployment package that is created on Windows 2000
> If you use the PDW to package a Visual Basic 6.0 application on a computer
> that is running a later version of Windows 2000, use either of the
following
> methods:
> Use a Windows 2000 service pack to update the Oleaut32.dll file version on
> the destination computer to the Oleaut32.dll file version that the
> deployment package contains or to a later version.
> In the deployment package, include the Oleaut32.dll file version that is
> included with Windows 2000 or an earlier version.
>
> To do this, install Microsoft Visual Studio 6.0 SP4 or later. Visual
Studio
> 6.0 SP4 or later installs the Olepro32.dll file, the Oleaut32.dll file,
and
> the Stdole2.tlb file in the Redist folder. The versions of these files are
> earlier than the versions of the corresponding files that are included
with
> Windows 2000. If you install these files, the PDW tries to install the
> Oleaut32.dll file from the Redist folder.
> Deployment package that is created on Windows XP
> If you use the PDW to package a Visual Basic 6.0 application on a computer
> that is running Windows XP, do not include the Msvcrt.dll file in the
> deployment package. If you must include this file in the deployment
package,
> follow these steps to prevent the PDW from redistributing the Msvcrt.dll
> file:
> Locate the Vb6dep.ini file.
>
> Note This file is typically located in the following folder:
> C:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard
> Open the Vb6dep.ini file in a text editor such as Notepad, and then add
the
> following code to the [Do Not Redistribute] section of this file:
> msvcrt.dll=msc40.dll=msc42.dll=olepro32.dll=oleaut32.dll=stdole2.tlb=
> Rebuild the deployment package, and then copy the package to the
> distribution location.
> Prevent redistribution of the Msvcrt.dll file
> If you use the PDW to package a Visual Basic 6.0 application, remove the
> Msvcrt.dll file from the list of files to include in the package.
>
> Alternatively, if you have already assembled a Setup package and you want
to
> modify the Setup package to prevent the package from redistributing the
> Msvcrt.dll file, follow these steps:
> Open the Setup.lst file in a text editor such as Notepad.
> If the [Bootstrap Files] section and the [PackageName Files] section
contain
> text to specify that the package includes the Msvcrt.dll file, remove this
> text and then re-number the files in these sections.
>
> Note In this step, PackageName is a placeholder for the name of your
> deployment package.
> Save the file.
> The next time that you run the Setup program, this program does not try to
> install the Msvcrt.dll file and the behavior that is mentioned in the
> "Symptoms" section of this article does not occur.
> STATUS
> This behavior is by design.
> REFERENCES
> For additional information, click the following article numbers to view
the
> articles in the Microsoft Knowledge Base:
> 279764 PRB: Multiple "System files are out of date" errors when you
install
> Visual Basic 6.0 application on Windows 2000-based computer
> 330314 PRB: Your computer does not restart after you install a Microsoft
> Visual Basic 6.0 application that includes a MSVCRT.dll file
>
> --------------------------------------------------
>
> PRB: Multiple "System Files Are Out of Date" Errors When You Install
Visual
> Basic 6.0 Application on Windows 2000-based Computer
>
> Q279764
>
> The information in this article applies to:
>
> Microsoft Visual Basic Professional Edition for Windows, version 6.0
> Microsoft Visual Basic Enterprise Edition for Windows, version 6.0
>
> SYMPTOMS
> When you install a Microsoft Visual Basic version 6.0 application that was
> created with the Package and Deployment Wizard onto a computer that is
> running Microsoft Windows 2000, you may receive the following error
message:
> 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 for you
now.
> You will need to restart Windows before you can run setup again. Click
> cancel to exit setup without updating system files.
> After Windows 2000 restarts and you begin the installation again, you
> receive the error message again.
>
>
> CAUSE
> The Package and Deployment Wizard uses a restart to update in-use system
> files. In Windows 2000, system files are protected and are not updated on
> the restart. Each subsequent attempt to install the application results in
> the same error message, and the application cannot complete its
> installation.
>
> The normal procedure to update Windows 2000 system files is to install the
> latest service pack. However, in certain situations, the development
> computer may contain specific system files that have a later version
number
> than those found on Windows 2000. For example, if the setup package was
> created on a Windows Millennium Edition (Me)-based system or a Windows
> 2000-based system with a service pack that is later than the target, the
PDW
> may package a higher version than is on the target Windows 2000 system.
When
> this happens, the application setup detects that it needs to install the
new
> system files, and it prompts you to restart the computer. Because Windows
> 2000 does not allow application installations to replace system files, the
> application setup detects the old system files again when it restarts.
>
> The file that causes this problem is Oleaut32.dll.
>
>
> RESOLUTION
> There are two ways to resolve this problem:
> Use a Windows 2000 Service Pack to update the version of Oleaut32.dll on
the
> target computer to one that is equal to or later than the version of the
> Oleaut32.dll file in the package.
>
>
> Include a version of Oleaut32.dll in the package that is equal to or
earlier
> than the version that shipped with Windows 2000. One way to accomplish
this
> is to install Visual Studio 6.0 Service Pack 4 (SP4) or later. Visual
Studio
> 6.0 SP4 installs three files (Olepro32.dll, Oleaut32.dll, and Stdole2.tlb)
> in the Redist folder. The file versions that SP4 installs are earlier than
> the versions that shipped with Windows 2000. The Package and Deployment
> Wizard then distributes the Oleaut32.dll from the Redist folder instead of
> the System folder.
>
> REFERENCES
> For additional information on other causes for this behavior, click the
> article number below to view the article in the Microsoft Knowledge Base:
> Q191096 PRB: Multiple 'System Files Are Out of Date' Errors
> For additional information about Visual Studio service packs, click the
> article numbers below to view the articles in the Microsoft Knowledge
Base:
> Q194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why
> Q194295 HOWTO: Tell That a Visual Studio Service Pack Is Installed
>
>
> --------------------------------------------------
> FIX: Setup Program Created by PDW Disables Windows 95/98/Me System
>
> Q193034
> The information in this article applies to:
>
> Microsoft Visual Basic Learning Edition for Windows, version 6.0, on
> platform(s):
> the operating system: Microsoft Windows 95
> the operating system: Microsoft Windows 98
> the operating system: Microsoft Windows Millennium Edition
> Microsoft Visual Basic Professional Edition for Windows, version 6.0, on
> platform(s):
> the operating system: Microsoft Windows 95
> the operating system: Microsoft Windows 98
> the operating system: Microsoft Windows Millennium Edition
> Microsoft Visual Basic Enterprise Edition for Windows, version 6.0, on
> platform(s):
> the operating system: Microsoft Windows 95
> the operating system: Microsoft Windows 98
> the operating system: Microsoft Windows Millennium Edition
>
>
> SYMPTOMS
> The Package and Deployment Wizard (PDW) is used to create a standard
> installation program for a program created in Visual Basic 6.0. The target
> system is running Windows 95 and contains two hard drive partitions. The
> first hard drive partition contains the operating system files while the
> second hard drive partition contains the TEMP folder and the installation
> program.
>
> When you run the installation program from the second hard drive
partition,
> the following Setup Error message box appears:
> "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 for you
now.
> You will need to restart Windows before you can run Setup again. Click
> Cancel to exit setup without updating system files."
> After you click OK, one of the following occurs:
>
>
> The system restarts but does not completely install the program. When you
> run the setup program, the following error message appears:
> A required .DLL file, C:\Windows\System\OLEAUT32.DLL was not found.
> During the Start Up process, the following error message appears:
> Windows could not upgrade one or more system files.
>
> You cannot start the system after seeing this message.
> NOTE: This bug only occurs on systems with the following attributes:
> The system is running Windows 95, Windows 98, or Windows Me.
>
>
> The system contains at least two hard disk partitions.
>
>
> The system folder and the TEMP folder reside on different partitions.
>
>
>
> CAUSE
> The following files were removed from the System folder and not updated
> because the Windows\System and Temp folders reside on different hard drive
> partitions:
>
>
> ASYCFILT.DLL
> COMCAT.DLL
> MSVBVM60.DLL
> MSVCRT40.DLL
> OLEAUT32.DLL
> OLEPRO32.DLL
> STDOLE2.TLB
>
>
> These files are updated during reboot via a mechanism built into Windows
95,
> Windows 98, and Windows Me.
>
> RESOLUTION
>
> Make sure the Windows\System and Temp folders are on the same drive.
>
> If this bug has already occurred, you need to copy the following files to
> the System directory and restart Windows:
>
>
> ASYCFILT.DLL
> COMCAT.DLL
> MSVBVM60.DLL
> MSVCRT40.DLL
> OLEAUT32.DLL
> OLEPRO32.DLL
> STDOLE2.TLB
>
> These files are included in your Visual Basic distribution disks or you
can
> download the following file from the Microsoft Download Center:
> Vb6sys.exe
> For additional information about how to download Microsoft Support files,
> click the article number below to view the article in the Microsoft
> Knowledge Base:
> Q119591 How to Obtain Microsoft Support Files from Online Services
> Microsoft used the most current virus detection software available on the
> date of posting to scan this file for viruses. Once posted, the file is
> housed on secure servers that prevent any unauthorized changes to the
file.
>
> This self-extracting executable file contains the files required by the
> System directory. After you run the self-extracting executable file, copy
> the expanded files to your system directory and restart Windows.
>
>
>
> STATUS
> Microsoft has confirmed this to be a bug in the Microsoft products listed
at
> the beginning of this article.
>
> This bug was corrected in Visual Studio 6.0 Service Pack 3.
>
> For more information about Visual Studio service packs, please see the
> following articles in the Microsoft Knowledge Base:
>
> Q194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why
>
> Q194295 HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed
>
>
> MORE INFORMATION
> When you run an installation program created by the Package and Deployment
> Wizard (PDW), the installation copies files to the TEMP directory. As part
> of the installation process, the installation program checks the versions
of
> the previously mentioned files stored in the system directory.
>
> If those files in the System directory are older than the files copied to
> the TEMP directory, the installation program causes Windows to restart and
> to replace the older files in the System directory with the newer files
from
> the TEMP directory during the restart.
>
> If these files are updated, Windows must be restarted.
>
> While Windows is restarting, it first deletes the files in the System
folder
> then attempts to replace them with the files in the TEMP folder. If the
> System and TEMP folders are on different hard drive partitions, the
deletion
> succeeds but the replacement fails; the older version files are deleted
from
> the System directory but the newer version files are not copied to the
> System folder.
> -------------------------
>
- Next message: Jeff Johnson [MVP: VB]: "Re: Why are some SQL functions not available?"
- Previous message: AustinMN: "Re: Recommended Fonts for Forms"
- In reply to: Randy Birch: "Re: Setup Error on Friends Computer"
- Next in thread: Grahammer: "Re: Setup Error on Friends Computer"
- Reply: Grahammer: "Re: Setup Error on Friends Computer"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
