The information in this article applies to:
SUMMARYThis 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 editing the registry.
Before you edit the registry, make sure you understand how to restore it if
a problem occurs. For information about how to do this, view the "Restoring
the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help
topic in Regedt32.exe. 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:
Q237957 OFF2000: How to Use a Log File to Troubleshoot Setup Problems Q230861 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: Q224434 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).For detailed information about how perform a clean start of Windows 95, please click the article number below to view the article in the Microsoft Knowledge Base: Q177604 Multimedia: Troubleshooting Using Clean Boot of Windows 95 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: Q151634 Protected-Mode CD-ROM Drive Support in Windows 95For 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: Q167069 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:
md c:\win95tmp del *.tmpNOTE: Do not delete these files when you are running Windows, because Windows or a Windows program may be using one of these files. 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: Q190630 OFF97: Kernel32.dll Error Installing 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: Q174713 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:
cd <drive>:\Windowswhere <drive> is the drive letter that contains the Windows folder. Typically, <drive> is drive C. NOTE: The swap file exists in the Windows folder if Windows manages virtual memory settings on your computer. If you chose to manage virtual memory settings on the computer, the swap file exists at the root level of the hard disk. To determine whether Windows manages virtual memory settings, right-click My Computer, click Properties, click Performance, and then click Virtual Memory. del Win386.swp 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: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD). 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:
c:\windows\command\attrib -h -s -r c:\system.1st c:\windows\command\attrib -h -s -r c:\windows\system.dat ren c:\windows\system.dat *.dax copy c:\system.1st c:\windows\system.dat 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:
c:\windows\command\attrib -s -h -r c:\windows\system.dat Q131431 How to Troubleshoot Registry Errors 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 discussed in this article are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability. The third-party contact information included in this article is provided to help you find the technical support you need. This contact information is subject to change without notice. Microsoft in no way guarantees the accuracy of this third-party contact information. For information about how to contact the companies mentioned in this article, query in the Knowledge Base for one of the following articles: Q65416 Hardware and Software Third-Party Vendor Contact List, A-K Q60781 Hardware and Software Third-Party Vendor Contact List, L-P Q60782 Hardware and Software Third-Party Vendor Contact List, Q-Z 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: Q200375 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. Additional query words: OFF2000
Keywords : kbdta kbdtatshoot DTIR |
Last Reviewed: December 20, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |