Startup Errors for Windows 9x/Me Startup errors can come from a variety of causes: -
Problems with Windows configuration, including boot files, Registry, Win.Ini , System.Ini , Config.sys , and Autoexec.bat files -
Failure to load vital device drivers, such as Himem.sys -
Problems with drives , including virtual memory ( swapfile ), ATA/IDE, and SCSI configuration  | The CD included with this book contains important Study Lab material for this chapter, as well as Chapters 2 “22 in this book. The Study Lab for each chapter contains terms to study, exercises, and practice tests ”all in printable PDF format (Adobe Acrobat Reader is included on the CD, too). These Study Lab materials will help you gear up for the A+ Exam. Also, the CD includes an industry-leading test engine from PrepLogic, which simulates the actual A+ test so that you can be sure that you're ready when test day arrives. Don't let the A+ test intimidate you. If you've read the chapters, worked through the Study Lab, and passed the practice tests from PrepLogic, you should be well prepared to ace the test! Also, you'll notice that some words throughout each chapter are in bold format. These are study terms that are defined in the Study Lab. Be sure to consult the Study Lab when you are finished with this chapter to test what you've learned. |
The following sections are designed to help you understand the causes of the most common problems with Windows 9x/Me startup that you might encounter on the A+ Certification Exam and learn the solutions. error in Config.sys line xx (Windows 9x Only) Config.sys is used to load real-mode drivers in Windows 9x. If you see an error in Config.sys line xx error message, check for one of the following causes: -
A reference to a driver file or folder that isn't present or might be misspelled -
A misspelling of the command in the Config.sys file; for example, Device=C:\Windows\Emm386.exe RAM is correct, whereas Devise=C:\Windows\Emm386.exe RAM is not a recognized command because Devise is not a recognized word You can use the step-by-step startup from the Windows 9x boot menu referred to earlier to bypass all or selective lines in Config.sys to see if your system performs normally.  | With Windows 98 but not Windows 95, you can also use the MSConfig utility ( see "Using MSConfig," p. 747 , to disable the loading of Config.sys or edit its contents). |
| | To help determine the cause of these problems, you might find it helpful to use the System Configuration utility ( MsConfig.exe ) with Windows 98/Me or the step-by-step startup option with Windows 95. These options can help you isolate the particular program or operation that triggers the error. |
Bad/Missing Command Interpreter If you see this error message, check the following possibilities: -
The Command.com file has been deleted from the root folder of the Windows drive (normally C:\ ) ” Restart the system with the Windows Emergency Boot Disk (EBD) and run Sys C: to restore Command.com and other boot files. | | The process of making the EBD for Windows is discussed in Chapter 15, "Preparing Hard and Floppy Drives with Windows," in the section "Creating a Boot Disk Suitable for Hard Disk Preparation," p. 484 . |
-
The Command.com file has been replaced with a Command.com file from a different version of Windows or MS-DOS ” Restart the system with the Windows EBD and run Sys C: to restore Command.com and other boot files. -
The wrong Command.com file was reloaded into memory after a command-prompt program such as Xcopy (which overwrites Command.com in memory) was run ” If you are not using a multiboot feature to enable you to run MS-DOS on the same system, delete all MS-DOS versions of Command.com on your system (such as in the \DOS folder). -
A computer virus is present on the system ” Boot with the Windows EBD and run an antivirus program to repair the problem. Himem.sys Not Loaded If you start Windows 9x with the Safe Mode Command Prompt option, neither the Windows Registry nor the Config.sys files (either of which can run Himem.sys ) is processed , so Himem.sys will not be loaded. Restart the computer normally and Himem.sys will be loaded into memory. | | See "Windows Safe Mode," p. 728 , for more information about using Safe Mode Command Prompt to start your computer. |
Missing or Corrupt Himem.sys If you are starting Windows 9x/Me normally and see a message indicating that Himem.sys is missing or corrupt, the file might be damaged or deleted. On Windows 9x/Me, Himem.sys is normally found in the \Windows folder. To fix a missing or corrupted Himem.sys in Windows 98, you can restore Himem.sys from the Windows 98 EDB. With Windows 95, you must copy Himem.sys from the Windows 95 installation CD-ROM or disks. | | It's rare to see a corrupt or missing Himem.sys with Windows Me because Windows Me features Windows File Protection, which automatically restores missing or corrupted system files. If the backup copy of Himem.sys isn't available, you're prompted to provide the Windows CD to reload the file from CD. |
Device Referred to in System.ini / Win.ini /Registry Not Found The Windows Registry, System.ini , and Win.ini files are used for hardware and software configuration information for Windows. These configuration files refer to programs and protected-mode drivers that must be accessed during the boot process. If you see an error message such as Device xxx referred to in System.ini/Win.ini/Registry not found , the most likely cause is that the file being referred to has been removed from the system incorrectly. To avoid this problem, use the appropriate option: -
For hardware, use the Remove button in the Device Manager before you physically remove the hardware from the system. Using Remove removes Registry and .ini file entries for the device so it will not be referred to when the system is restarted. -
Open the Add/Remove Programs icon in the Windows Control Panel, select the program you want to remove, and select Add/Remove (Windows 9x) or Change/Remove (Windows 2000). This starts the uninstall program for applications and utilities listed on the menu. -
Use the program's own uninstall option or a third-party uninstall program. Any of these options should remove both the program and references to it in the Registry and other locations, such as System.ini or Win.ini . If the program is removed by deleting its folder, leaving references in the Registry, System.ini , or Win.ini , use the error message to determine which file contains the reference. | | For Windows 98/Me/XP, the easiest way to remove a reference in System.ini , Win.ini , or any startup routine (including the Registry) is to use the MSConfig program ( see "Using MSConfig," p. 747 , for more information). |
caution  | I can't harp on this enough. If you are not fully versed in working with the Windows Registry, you are better off not tinkering with it! Although making changes to the Registry can dramatically enhance system performance, it can also result in dire consequences if you make but a single error while working with a Registry entry. Always, always, always be sure to make a backup of the Registry before you make any changes. More experienced Windows users than you have rendered their PCs inoperable after fiddling with the Registry. You have been warned . |
Alternatively, you can use a text editor such as Notepad or Edit to remove references to a missing program or device in Windows 9x's System.ini or Win.ini . You can also manually edit the Windows Registry to remove references to a missing device. See Chapter 18, "Using and Optimizing Windows," for information on Registry editors. Windows Protection Error A Windows Protection Error takes place during the startup process or during the shutdown process when a VxD (32-bit virtual device driver) or .386 driver file is loaded or unloaded. Protection errors also can occur if there are driver conflicts, virus infections of Win.com or Command.com , hardware conflicts, bad memory, or a bad motherboard. To determine if a hardware conflict or driver file is to blame, start the system with the Bootlog ( Logged ) option. If the error recurs , restart the system in Safe Mode. Use EDIT or Notepad to examine the Bootlog, and look at the end of the Bootlog for the last driver file initialized . Search for the driver and examine its properties in My Computer/Windows Explorer to determine what hardware or software it works with. Uninstall the program. If this doesn't solve the problem, check the system hardware for errors and try reinstalling Windows. Alternative Startup Methods for Windows 9x/Me If Windows won't start normally, what next ? Try one of the alternative startup methods we cover in the following sections to see if you can get to the Windows Desktop to make changes in your system configuration and get back to work. To display alternative startup options for Windows, press the Ctrl key with Windows 98/Me; press the F8 key with Windows 95. Windows Safe Mode Windows uses Safe Mode to recover from startup problems. There are three different Safe Mode startup options: -
Safe Mode ” In Safe Mode, the system uses a standard VGA display driver, doesn't process the Config.sys or Autoexec.bat files present on a Windows 9x system, and doesn't load most 32-bit device drivers, including those used for hard disk and CD-ROM access and for networking. This mode loads the Windows GUI and enables the user to access the Windows Explorer and Windows Device Manager, although Windows 9x cannot display hardware resources used when the system is in Safe Mode. -
Safe Mode with Network Support ” You also can select Safe Mode with Network Support (Windows 9x) or Safe Mode with Networking (Windows 2000/XP) to add bare-bones network support to Safe Mode. This mode also uses the Windows GUI and enables network connections so you can access drivers or needed support items through the network or the Internet. -
Safe Mode Command Prompt ” When this mode is selected, the computer does not boot to the Windows GUI, but boots to a command prompt without loading the Windows Registry, Config.sys , or Autoexec.bat . If you need to start Windows with special command-line options, choose Command Prompt Only mode instead. | | Remember, if you are running only one operating system, you will have to be quick to boot into Safe Mode. After you have powered the system on, keep your finger over the F8 button and press it immediately after the BIOS hardware startup message moves off the screen. You'll only have a couple of seconds to do this, so be ready. After pressing F8, a menu showing various boot options available to you will appear. Choose Safe Mode from the list of options. If you are dual booting your PC, you will be presented with a boot options menu each time you boot the system. |
Starting Windows 9x/Me in Safe Mode Windows 9x/Me automatically starts in Safe Mode if the system didn't start successfully on the previous startup. To run Safe Mode or other startup options, you can display the Windows 9x/Me startup menu by pressing the F8 or Ctrl key on a Windows 9x/Me system as soon as the system's power-on self-test (POST) is complete. Select the Safe Mode option you want to use from the options listed. Using Safe Mode Safe Mode can be used to start the system if normal startups fail, because Safe Mode uses a minimal set of drivers (for example, VGA instead of chipset-specific SuperVGA drivers) and services. By using only the minimum drivers and services to start the system, potential conflicts that can prevent the system from starting are bypassed. You can use the Windows Device Manager to remove devices in Safe Mode, but Safe Mode in Windows 9x cannot show you configuration details such as the hardware resources used by each device. You can access troubleshooters in either version of Windows, and if you start Windows in Safe Mode with Network Support, you might still have access to the Internet for additional help. Other Startup Options for Windows 9x/Me Windows 9x/Me offer additional startup options, which include the following: -
Step-by-Step Confirmation ” Select this option to selectively run or skip commands in Config.sys , Autoexec.bat , and the Windows Registry. -
Logged ” Select this option to create a hidden text file called Bootlog.txt , which is stored in the root folder of the default Windows drive. Bootlog.txt records startup events and is useful for finding problems that prevent Windows from starting. Windows 9x also offers these additional startup options: -
Command Prompt Only ” Select this option to start the system at a command prompt after processing Config.sys , Autoexec.bat , and the Windows Registry. This provides a DOS-like environment suitable for running legacy programs that cannot run with Windows in memory. You can also use it to start Windows 9x with special startup switches (see Chapter 18). -
Previous Version of MS-DOS ” Loads the previous version of MS-DOS (if still present on the system). -
Safe Mode Command Prompt ” Starts the system without loading Config.sys , Autoexec.bat or the Windows Registry to produce a clean-boot environment. | | With Windows 98/Me (as well as Windows XP), you can use MSConfig 's Advanced dialog to start Windows with special startup switches without the need to boot into command-prompt mode first. See "Using MSConfig" later in this chapter for details. |
Press the function keys listed in Table 20.1 to start Windows 9x/Me with the option listed. Table 20.1. Windows 9x/Me Startup Option Function Keys | Startup Key | Startup Option Selected | Windows Version | Equivalent to Windows Startup Command | | F4 | Previous Version of MS-DOS | 95, 98 | n/a | | F5 | Safe Mode | 95, 98, Me | Win/d:m | | Shift-F5 | Safe Mode Command Prompt | 95, 98 | n/a | | F6 [*] | Safe Mode with Network Support | 95, 98 | Win/d:n | | Shift-F8 | Step-by-Step Confirmation | 95, 98, Me | n/a | [*] Not listed onscreen, but a valid option Table 20.2 lists some typical uses for the Windows 9x/Me startup menu options. Table 20.2. Using the Windows 9x/Me Startup Menus for Troubleshooting | Problem | Windows Version | Startup Option to Select | Notes | | Windows won't start after you install new hardware or software. | Me | Safe Mode | Boots computer with minimal devices installed; use System Restore (if available) to reset the computer to a previous working condition. | | Windows won't start after you install new hardware or software. | 9x | Safe Mode | Boots computer with minimal devices installed. Use Device Manager to remove or reconfigure last-installed hardware, or Add/Remove Programs to remove last-installed software. Then, restart the computer. See "Using the Windows Device Manager," p. 703 for details. | | Windows won't start after you install a different video card or monitor. | Me, 9x | Safe Mode | Select PCI VGA adapter for the video driver in the Display Properties sheet, and restart the computer. Reinstall the drivers needed for the video card as prompted. | | Windows can't start normally, but you need access to the Internet to research the problem or download updates. | Me, 9x | Safe Mode with Networking | You can use Windows Update and the Internet, but some devices won't work in this mode. This mode also uses 640x480 and 16- color display mode. | | Windows doesn't finish starting normally, and you want to know what device driver or process is preventing it from working. | 9x, Me | Enable Boot Logging | This option creates a file called bootlog.txt in the root directory of the boot drive (C:\). Restart the computer in Safe Mode and open this file with Notepad or Wordpad to determine the last driver file that loaded. You can update the driver or remove the hardware device using that driver to restore your system to working condition. | | Windows is loading programs you don't need during its startup process. | Me, 98 | Boot computer in Safe or Normal Mode; click Start, Run, and then type MSConfig | Use MSConfig to disable one or more startup programs. You can also use MSConfig to restore damaged files or to start System Restore to reset your computer to an earlier condition. ( MSConfig is not included with Windows 95.) | |
