PRB: Setup Cannot Access Required Initialization FileLast reviewed: July 17, 1997Article ID: Q103709 |
1.00
WINDOWS
kbsetup kbprb
The information in this article applies to:
SYMPTOMSRunning Setup creates a message box titled
Setup Initialization Errorand the message:
Cannot access required initialization fileThe message box contains a STOP icon and an OK button. When you choose OK, the program ends.
CAUSEAn incorrect version of LZEXPAND.DLL may cause the problem. The problem may also be caused by:
RESOLUTIONCheck that the correct version of LZEXPAND.DLL is available and that other versions do not occur earlier on the dynamic-link library (DLL) search path.
MORE INFORMATIONThe Setup program uses the LZEXPAND.DLL file from Windows 3.1 to decompress files from the installation disks. An incorrect (old) version of this DLL is the most common reason for Setup to give the "Cannot access required initialization file" error message. Several versions of LZEXPAND.DLL have been released, some of them with particular software packages. These may have installed the DLL in the Windows directory rather than the Windows SYSTEM directory. Windows 3.1 installs the DLL in the Windows SYSTEM directory (by default, C:\WINDOWS\SYSTEM). The Windows 3.1 version of LZEXPAND.DLL is 9,936 bytes and is dated 03/05/92 or later. It contains major changes from earlier versions shipped with Windows version 3.0 and some other software. If multiple copies of LZEXPAND.DLL exist on your system, remove or rename all except the one in the Windows SYSTEM directory. If the size and date on that DLL do not seem correct, and the Setup error persists, expand a new copy of the DLL from either your Windows 3.1 installation disks or from the Visual C++ installation disks. Refer to the file PACKING.TXT on disk one to determine which disk and directory contains LZEXPAND.DLL. You can expand the file from the floppy disk by using the Windows 3.1 EXPAND utility. For example,
EXPAND a:\redist\lzexpand.dl c:\windows\system\lzexpand.dllOther possible, but less common causes of this problem are:
|
Additional reference words: 1.00
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |