Article ID: 238259 - Last Review: June 6, 2008 - Revision: 2.1 OFF2000: Office Stops During Setup: Troubleshooting Steps on Windows 95This article was previously published under Q238259 On This PageSUMMARY
This article contains information about troubleshooting steps to use when you are installing Microsoft Office programs under Microsoft Windows 95 and Setup seems to stop responding (hang) without apparent errors.
MORE INFORMATIONIMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986
(http://support.microsoft.com/kb/256986/EN-US/
)
Description of the Microsoft Windows Registry
To troubleshoot the problem of Setup stopping, perform the following tasks. Some items can be combined to save time and effort. Then try Office Setup again. Make Sure Setup Has Actually Stopped RespondingSetup may appear to be hung but in fact is continuing slowly. Wait longer (about 20 minutes) before ending Setup. Before concluding that Setup is stopped, check the CD-ROM drive light and hard disk light for activity. Also, press CTRL+ALT+DEL and check whether the Office Setup task appears as "Not Responding" in the Close Programs dialog box.Create a Verbose Log FileIf Setup stops and you do not receive any error messages, you can use a verbose log file to determine what action Setup was performing when it stopped. Create a verbose log file by using the following steps:
237957
(http://support.microsoft.com/kb/237957/EN-US/
)
OFF2000: How to Use a Log File to Troubleshoot Setup Problems
230861
(http://support.microsoft.com/kb/230861/EN-US/
)
OFF2000: How to Customize Office Setup Logging Options
Quit All Unnecessary ProgramsQuit all unnecessary programs that are running before you run Office 2000 Setup. To do so, use the following steps:
NOTE: If a beta version of Office 2000 has been installed, you must uninstall it before installing the final version. Although Setup should prompt you to remove such a pre-release version, the alert may not appear. For detailed information about this problem and removing the beta installed version, please click the article number below to view the article in the Microsoft Knowledge Base: 224434
(http://support.microsoft.com/kb/224434/EN-US/
)
OFF2000: Beta 2 Not Detected During Setup
Clean Start Windows 95If the issue continues to occur, start Windows 95 without loading any TSR (terminate-and-stay-resident) programs or device drivers (this is called a clean boot or clean start).Setup from a Flat FileIf there is enough space available on the hard disk, make a flat file of the contents of Office 2000 CD-ROM disk 1 by following these steps:
Start Windows in Safe ModeWindows has a built-in troubleshooting mode called Safe Mode. It bypasses startup files and uses only basic system drivers, including basic networking. When you start Windows in Safe Mode, Windows uses only the mouse, keyboard, and standard video graphics adapter (VGA) device drivers. This makes Safe Mode useful for isolating and resolving error conditions that are caused by both real-mode and Windows-based drivers. Windows also has troubleshooting features that may help you identify the problem. To start Windows in Safe Mode and make the additional troubleshooting features available, follow these steps:
For additional information about determining whether Windows is using protected-mode drivers, please click the article number below to view the article in the Microsoft Knowledge Base: 151634
(http://support.microsoft.com/kb/151634/EN-US/
)
Protected-Mode CD-ROM Drive Support in Windows 95
For additional information about installing real-mode drivers for the
CD-ROM drive, please click the article number below
to view the article in the Microsoft Knowledge Base:
167069
(http://support.microsoft.com/kb/167069/EN-US/
)
Installing Real Mode CD-ROM Drivers
Check for a Valid Temporary Folder and Delete Temporary FilesThere should be at least 50 megabytes (MB) of free space on the hard disk that contains the temporary folder. To check for a temporary folder and delete excess files from that folder, follow these steps:
Check the Hard Disk for Disk Errors and FragmentationUse the ScanDisk program to check the hard disk for lost clusters and other file allocation table (FAT) errors and to test the hard disk integrity. You can also use the ScanDisk program to repair any of these problems. To run ScanDisk, follow these steps:
Turn Off the CD-ROM Drive Cache and DMAIf the problem occurs while you are reading from a CD-ROM drive, try turning off the CD-ROM drive cache. This may make the drive more reliable but reduce performance. To turn off the CD-ROM drive cache, follow these steps:
Also, turn off DMA or Direct Memory Access as detailed in the "Workaround" section of the following Microsoft Knowledge Base article: 190630
(http://support.microsoft.com/kb/190630/EN-US/
)
OFF: Kernel32.dll and Other Errors When You Install Products with DMA Enabled
Verify That the Compact Disc Is Clean and UnscratchedIf the problem occurs while you are installing from a CD-ROM, verify that the CD is clean by wiping it with a soft, lint-free cloth. Also ensure that there are no large scratches on the CD. If the CD is damaged and unreadable, error messages may appear during installation.For additional information, please click the article number below to view the article in the Microsoft Knowledge Base: 174713
(http://support.microsoft.com/kb/174713/EN-US/
)
Troubleshooting Installation from Compact Disc Media
Check for a Corrupted Swap FileSetup problems may also occur if your Windows swap file is corrupted. To create a new swap file, restart the computer in MS-DOS mode, delete the Win386.swp file in the Windows folder, and then restart the computer. To create a new swap file, follow these steps:
Check for Software UpdatesOutdated and incompatible software may also cause Setup problems. Check with the manufacturer of the computer for various software updates, such as BIOS updates, OEM Windows updates, and hardware driver updates such as CD-ROM and DVD-ROM, video, and printer drivers. If you are using third-party partitioning software--for example, EZDrive or Ontrack Disk Manager--verify that you have the most recent version of these products.Scan the Computer for VirusesIf a virus is present on your computer and has damaged some files, problems may appear when you run Setup. Scan the hard disk and floppy disks with a virus detector. If the virus detector finds a virus on your computer, remove the virus before you run Office Setup again.NOTE: Do not run a virus detector terminate-and-stay-resident (TSR) program while you run Setup. Run a virus detector before you run Setup and then turn it off. Check for Registry CorruptionWARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.When you start Windows in Safe Mode, Windows does not read the entire registry. Therefore, damage to the registry may not be evident when you run Windows in this mode. It may be necessary to replace the existing registry (System.dat) with a backup to determine whether the problem is caused by a damaged registry. To troubleshoot a damaged registry, follow these steps:
If replacing the System.dat file with the System.1st file resolves the issue, the problem may be related to registry damage. Note that you may have to reinstall programs and device drivers that you installed after you installed Windows to update the new registry. If the issue is not resolved, restore the original registry. To do this, follow these steps:
131431
(http://support.microsoft.com/kb/131431/EN-US/
)
How to Troubleshoot Registry Errors in Windows 95
Check HardwareIf you exhaust all other troubleshooting steps and you still receive error messages, it is possible that one or more pieces of your hardware are incompatible with Windows or are damaged. To identify a problem with your computer hardware, contact your computer vendor.Badly seated memory or bad memory has been reported to cause Kernel32.dll error messages. Switching memory around in the motherboard memory banks has been known to correct some of these issues. It has also been reported that running the Atron 380 Bus Mastering Ethernet Card can cause Kernel32.dll errors. Removing this card from the computer may resolve these error messages. The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products. Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information. For information about how to contact the companies mentioned in this article, visit the following Microsoft Web site: http://support.microsoft.com/gp/vendors
(http://support.microsoft.com/gp/vendors)
Reinstall Windows in a New FolderUse this method only after you try all of the other troubleshooting steps in this article. If you reinstall Windows in a new folder, you must reinstall all Windows-based programs under the new Windows installation.For additional information, please click the article number below to view the article in the Microsoft Knowledge Base: 200375
(http://support.microsoft.com/kb/200375/EN-US/
)
OFF2000: How to Install Windows 95 to New Folder
Turn Off Enhanced BIOS FeaturesMost computers have several enhanced settings that allow the computer to fully use the computer hardware. These high-speed settings can cause the system to become unstable; turning off these features may make the computer more stable. Contact your computer manufacturer for information about entering the basic input/output system (BIOS) and changing the BIOS settings. You can enter the BIOS on most systems immediately after turning on the power. Usually a keystroke (such as DEL) is required to enter the BIOS. Below are the common features that can interfere with Microsoft Office programs:
WARNING: Incorrectly altering hardware BIOS settings can cause serious problems that may cause your computer to fail to start or function properly. Microsoft cannot guarantee that problems that result from the incorrect setting of hardware BIOS options can be solved. Alter the hardware BIOS settings at your own risk. APPLIES TO
| Article Translations
|

Back to the top
