Chapter 27 - General Troubleshooting
| Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
This chapter provides a general approach to troubleshooting. It presents a troubleshooting strategy and identifies tools that are available in Microsoft Windows 98 for finding and correcting problems on your system.
Note This is a general guide to troubleshooting. Most chapters in this book have troubleshooting sections for individual components. When you have the problem narrowed down to a known component, use the troubleshooting section in the chapter that describes that component.
General Troubleshooting Strategy
.gif "Cc768197.spacer(en-us,TechNet.10).gif")
This section discusses an approach for solving system problems. Meticulous record-keeping is essential to successful troubleshooting. You should keep readily accessible all records of the network layout, cabling, previous problems and their solutions, and dates of installation of hardware and software.
Many problems can be avoided with routine virus checks. Be sure to check for viruses before installing or upgrading Windows 98 on a computer that is already in use.
Caution Anti-virus software may interfere with the installation of Windows 98. Disable all anti-virus software before running setup for any operating system. Once Windows 98 is successfully installed, re-enable the anti-virus protection.
To troubleshoot a problem, follow these general guidelines:
Analyze symptoms and factors.
Check to see if the problem is a common issue.
Isolate the source of the problem.
Consult technical support resources.
Analyzing Symptoms
Start troubleshooting by gathering information. Develop a clear understanding of the symptoms and collect pertinent system information to understand the environment in which they occur. Precisely what is not working correctly? Under what conditions does the problem occur? Which aspects of the operating system control those conditions? Is the problem specific to an application, or is it specific to a subsystem (networks, video, and so on)?
Try to narrow down exactly what you expect to have happen versus what is happening.
Consider the following:
What is the issue at hand? What do you expect to happen when the problem is resolved?
Has the system or configuration ever worked? If so, what changed?
Is the error condition reproducible or random?
Is the error specific to a particular system, configuration, or application?
What specific hardware and firmware are involved?
Is software that Windows 98 does not load by default loaded when the problem occurs?
Does the error still occur with Safe Mode?
One strategy for isolating the source of the problem is to attempt to reproduce the symptom using another application that offers similar functionality. If the problem is reproducible, it might be subsystem- or hardware-related. If the problem is not reproducible, investigate the application itself.
Checking for Common Issues
Check to see if the problem is a common issue by reviewing Help and the TXT files included on the Windows 98 compact disc. For example, check Setup.txt and Readme.txt.
See the Troubleshooting topic in Help for the Windows 98 Troubleshooters. Use the Troubleshooters to diagnose and solve technical problems with the following system components and events:
Networking
Modem
Startup and shutdown
Print
DriveSpace 3
Memory
MS-DOS programs
Display
DirectX
Sound
The Microsoft Network
Hardware conflict
Dial-Up Networking
Direct Cable Connection
PC Card
To get troubleshooting assistance from Windows 98 Help
On the Start menu, click Help.
On the Contents tab, click Troubleshooting, and then click Windows 98 Troubleshooters.
Pick a topic from the list.
Identifying the Source of the Problem
Try to identify all the variables that could affect the problem. As you troubleshoot the problem, try to progressively eliminate these variables to isolate the root cause of the issue. Keep records of what you do and the effect of each action. If you must eventually escalate your issue to a support provider, your detailed notes will be invaluable to the technician.
Eliminating variables helps determine the cause of a problem. Do symptoms manifest themselves when you run the system in Safe Mode? If not, you can use the System Configuration Utility (Msconfig.exe) to identify problems with software loading during a normal startup. By selecting Diagnostic startup – interactively load device drivers and software and following the instructions you can safely eliminate all of the items at once to determine if the problem can be isolated using the tool. If the symptoms are no longer reproducible, you can add items back in its Selective startup until the symptoms reappear, thus identifying the problem's source. The System Configuration Utility is described later in this chapter.
Caution Do not modify Config.sys and Autoexec.bat until you have determined it is safe to do so. Your system might require legacy software to access the hard disk through a drive overlay or compression. If your system will run in Safe Mode, you can modify these files without losing access to the drive.
Windows 98 does not load protected-mode device drivers when it is run in Safe Mode. If you determine that the problem is not with software loading at startup using Msconfig.exe, you could attempt to isolate the problem with the protected-mode configuration by disabling suspect devices' drivers. To do so, in Control Panel double-click System and then click the Device Manager tab.
Caution The Plug and Play specification allows an operating system to disable devices at the hardware level. For example, if you disable a COM port in Device Manager, you may be required to enter the CMOS or system setup to re-enable it.
If the problem is the result of a recent change to the system, undo that change. Microsoft System Information (MSInfo) maintains a history of device drivers installed on the system. If you are unsure of a system's recent history, use MSInfo to better understand what has happened. If a device fails and its history indicates a recent upgrade to a new driver, replace it with the original driver and retest. If an update installed from the Windows Update Web site fails to meet your expectations, restore the original files by running the Update Wizard Uninstall from the Tools menu in MSInfo. If everything was fine yesterday, try restoring yesterday's configuration files by running MS-DOS-based Registry Checker with the /restore command prompt option (Scanreg /restore). Restoring a previous day's backup set will result in the loss of any changes made in the interim. Registry Checker is described in "Using Registry Checker" and "Restoring the Registry" later in this chapter.
Test each modification individually to see if it solved the problem. Make note of all modifications and their effect on the symptoms. This provides you with the information product support personnel will request if you eventually determine you need their assistance, and it provides an excellent reference for future troubleshooting.
Checking Technical Support Resources
Technical newsgroups offer peer support for common computer problems. When possible, post persistent problems on the appropriate online forum. Other users may have already discovered, reported, and found workarounds for your problem. Suggestions from others may save you time in tracking down the source of the problem by giving you direction for your troubleshooting. For more information about technical support resources such as Microsoft TechNet, see https://www.microsoft.com/technet/images/prodtechnol/win98/reskit/part5/images/wrknn12.gif .
.gif){kind=link}
Microsoft Help contains information about getting online Microsoft technical support.
To get online Microsoft technical support information from Windows 98 Help
On the Start menu, click Help.
Click Web Help, and then click Support Online to connect to Support Online from Microsoft Technical Support.
Troubleshooting Tools
This section provides an overview of tools that are available in Windows 98. The tools can help you maintain your system in the following ways:
Keep your system running smoothly.
Isolate problem areas.
Diagnose problems.
Fix problems.
Seek further assistance.
Table 27.1 lists system tools installed during Windows 98 Setup. The table includes a brief overview of the tool, and some details about the files that make up the tool. The tools are described in more detail later in the section.
Note This chapter assumes that your Windows 98 files are in the \Windows folder, which is the default folder in which Setup copies the system files.
Table 27 .1 Troubleshooting tools
Tool |
Overview |
File details |
|---|---|---|
Microsoft System Information (MSInfo) |
Displays system information, such as hardware resources, devices installed, and the corresponding device drivers. Use MSInfo to diagnose and solve computer problems. MSInfo can be used to view reports generated by WinRep or DOSRep on a remote system. |
Name: Msinfo32.exe |
Dr. Watson |
A program error debugger that traps application faults (running in ring 3 of the processor), generating a snapshot of the system to aid in the diagnosis of the fault. This tool interprets program errors in Windows-based applications and attempts a diagnosis. When you are running Dr. Watson, it automatically creates a log file when an application fault occurs. The log files are stored in the \Windows\Drwatson directory with a .wlg extension. The log file indicates the program that faulted, the program the fault occurred in, and the memory address where the fault occurred. Dr. Watson cannot create a snapshot in the event of a system hang. |
Name: Drwatson.exe |
System File Checker |
Verifies the integrity of system files. This tool scans the system for changed, deleted, or corrupt files. If necessary, System File Checker can extract the original Windows 98 file. |
Name: Sfc.exe |
Digital Signature Check |
Feature that network administrators can enable to identify drivers that have been digitally signed by Microsoft. This feature can be turned on using Policy Editor (Poledit) or by setting a key in the registry. |
Enabled in registry key: |
Signature Verification Tool |
Tool that determines whether a file has been granted a digital signature and whether that file has been modified after being granted a digital signature. |
Name: Sigverif.exe |
Automatic Skip Driver Agent |
Detects devices that prevent Windows from starting. |
Name: Asd.exe |
Windows Update |
Windows Update is the Web-extension of Windows 98 designed to help your computer continue to work better and run better. Windows Update contains a central catalog of new product enhancements, including service packs and new Windows features. In addition, Windows Update lets you update new system files and device drivers, specific to your computer. |
Name: Iexplore.exe |
System Configuration Utility |
Automates routine Windows troubleshooting steps. System Configuration Utility allows you to modify the system configuration with check boxes. This tool allows you to troubleshoot problems through a process of elimination using check boxes. |
Name: Msconfig.exe |
Registry Checker |
Windows 98 includes both Windows-based and MS-DOS-based programs for scanning, fixing, backing up, and restoring the registry and system configuration files. Registry Checker runs each time Windows starts. |
Names: Scanreg.exe and Scanregw.exe |
Microsoft Backup |
A built-in application that you run to back up the data in your entire system to prevent the loss of data in the event of hardware failure |
Name: Msbackup.exe |
Microsoft System Recovery |
Operating system recovery tool that operates completely in protect mode. Installs a minimal Windows 98 environment with full access to Win32 APIs, drivers, and other resources, and then steps you through the process of recovering files through Microsoft Backup. |
Name: Pcrestor.bat |
Scheduling Tasks |
The Scheduled Task Wizard enables you to run important utilities such as ScanDisk, Disk Defragmenter, and Backup at regular intervals. |
Name: Mstask.exe |
Maintenance Wizard |
The Windows Maintenance Wizard is used to schedule the operation of ScanDisk, Disk Cleanup, Disk Defragmenter, and other tools. |
Name: Tuneup.exe |
Version Conflict Manager |
Windows 98 Setup automatically installs Windows 98 files over a newer file that may be on the hard drive. |
Name: Vcmui.exe |
Windows Report Tool |
Web-based reporting tool that gathers system information and uploads it using HTTP to a support provider. The report includes a snapshot of the system in Microsoft System Information's format. |
Name: Winrep.exe |
MS-DOS Report Tool |
Web-based reporting tool used to gather system files and upload them to an FTP server when Windows is inaccessible. |
Name: Dosrep.exe |
Using MS System Information
Microsoft System Information (MSInfo) collects system information, such as devices installed or device drivers loaded, and provides a menu for displaying the associated system topics. Use MSInfo to diagnose computer problems. For example, if you are having display problems, use MSInfo to determine the display adapter installed on the computer and the status of its drivers.
Use MSInfo to track down an error and to learn the appropriate support tool to resolve the problem. For example, if a device is not functioning, MSInfo reports the following when viewing problem devices:
This device has a problem: Code=##
MSInfo also provides links in the Tools menu to other tools used for troubleshooting.
To launch Microsoft System Information
- Click Start, point to Programs, Accessories, and System Tools, and then click System Information.
Note You can also launch Microsoft System Information by typing msinfo32.exe filename at the command prompt. The command prompt option filename enables you to specify a CAB file that was generated by the Windows Report Tool. For information about the Windows Report Tool, see "Windows Report Tool" later in this chapter.
.gif "Cc768197.wrknn03(en-us,TechNet.10).gif")
The information displayed in MSInfo is divided into three categories: Hardware Resources, Components, and Software Environment. The following sections describe the categories and sub-categories displayed in MSInfo, and explain how this information can be used when troubleshooting.
System Information
System Information provides a general profile of the system. This includes the version of Windows, the version of the Internet Explorer browsing software, CPU, memory, system resources, total and available disk space, and the file system for each partition. Use this information at the beginning of the troubleshooting process to develop a basic picture of the environment in which the problem occurs.
Hardware Resources
The Hardware Resources view displays hardware-specific settings, such as assigned or used interrupt requests (IRQs), I/O addresses, and memory addresses.
Conflicts/Sharing Lists identified resource conflicts between Industry Standard Architecture (ISA) devices, and identifies resources shared by peripheral component interconnect (PCI) devices. Use this information to help you identify some hardware conflicts.
DMA Reports the DMA channels in use, the devices using them, and those free for use.
Forced Hardware Lists hardware devices that have user-specified resources as opposed to system-specified resources. This information is useful when troubleshooting Plug and Play resource conflicts.
I/O Lists all I/O port ranges in use and the devices using each range.
IRQs Summarizes IRQ usage, identifying the devices using the IRQs and showing free IRQs.
Memory Lists memory address ranges in use by devices.
Components
Components displays information about your Windows 98 system configuration. The Components view includes the status of your device drivers, networking, and multimedia software. There is also a comprehensive driver history and a summary of problem devices.
Multimedia Lists sound card and game controller information.
Multimedia — Audio Lists audio CODECs loaded.
Multimedia — Video Lists video CODECs loaded.
Multimedia — CD-ROM Lists the drive letter and model of the CD-ROM drive. With a data CD-ROM in the drive, MSInfo also performs a data transfer test.
Display Lists video card and monitor information.
Infrared Lists Infrared device information.
Input Lists keyboard and mouse information.
Miscellaneous Lists information about any miscellaneous components.
Modems Lists modem information.
Network Lists network adapter, client, and protocol information.
Network — Winsock Lists Winsock version, description, and status information.
Ports Lists serial and parallel port information.
Storage Lists information on hard drives, floppy drives, removable storage, and controllers.
Printing Lists installed printers and printer drivers.
Problem Devices Lists devices with problems. Lists each device flagged in Device Manager, with the corresponding status information.
USB Lists controllers and drivers installed.
History Lists complete driver history or history for the past seven days. Useful for tracking changes to the system's configuration.
System Lists information on BIOS, motherboard, and other system devices.
Note The options to view Basic Information, Advanced Information, or History appear if the component has a device driver.
Software Environment
The Software Environment view displays a snapshot of the software loaded in computer memory.
Drivers — Kernel Drivers Lists kernel-mode (ring 0) device drivers loaded.
Drivers — MS-DOS Drivers Lists real-mode device drivers loaded.
Drivers — User-Mode Drivers Lists user-mode (ring 3) device drivers loaded.
16-bit Modules Loaded Lists loaded 16-bit system-level dynamic-link libraries (DLLs) and programs. Useful for debugging software problems, such as application faults.
32-bit Modules Loaded Lists loaded 32-bit system-level DLLs and programs. Useful for debugging software problems, such as application faults.
Running Tasks Lists currently running executable files. This provides a comprehensive view of the processes running on the system.
Startup Programs Lists programs started automatically either from the registry, the Startup group, or the Win.ini file.
System Hooks Lists programs that are resident in memory and hook system calls.
OLE Registration — INI File Lists OLE file associations controlled by various INI files.
OLE Registration — Registry Lists OLE file associations controlled by the registry.
Caution Hardware information is not available in Safe Mode. While MSInfo can run in Safe Mode, it will be limited to displaying system components and the software environment.
Launching System Tools
With Windows 98, Microsoft System Information should be the first place to go when troubleshooting. To reduce the time spent navigating through the Start menu, you can launch the following utilities from the Tools menu of Microsoft System Information:
Windows Report Tool
Update Wizard Uninstall
System File Checker
Signature Verification Tool
Registry Checker
Automatic Skip Driver Agent
Dr. Watson
System Configuration Utility
ScanDisk
Version Conflict Manager
These troubleshooting tools are covered later in this chapter.
Viewing, Saving, and Printing Information
To view files created by other programs
Click Start, point to Programs, Accessories, and System Tools, and then click System Information.
From the File menu, click Open.
Click Files of type, click a file to open, and then click Open.
You can view the following file formats:
File |
Description |
|---|---|
*.cab |
Report created by the Windows Report Tool (Winrep.exe) or MS-DOS Report Tool. This is the same CAB format used by Windows 95. |
*.txt |
File created by a text editor such as Notepad. You can paste specific information from MSInfo into Notepad, and send it to Technical Support so that they can view only that specific information. |
*.dat |
File created by Hwinfo.exe. |
*.wlg |
Dr. Watson log files. Dr. Watson is used to assist in determining the cause of failures in Windows-based applications. |
*.nfo |
File created by MSInfo. You can view NFO files created on another computer to see its system configuration. |
To save system information
- In MSInfo, go to the File menu, and click Save.
You can save system information in the following file formats:
File |
Description |
|---|---|
*.nfo |
This is the MSInfo file format. These files are saved to the \Windows folder by default. |
*.txt |
Files created by a text editor such as Notepad. You can paste specific information from MSInfo into Notepad, and then send it to Technical Support. |
To export system information
In MSInfo, go to the File menu, and then click Export.
MSInfo exports information in text file (TXT) format. The files are saved to the \Windows folder by default.
To print system information
You can print a report of all system information by clicking Print on the File menu.
Note A typical MSInfo report can total more than 80 pages depending on the hardware and software installed.
To print specific information
Highlight, and then copy the appropriate information.
Paste it into a text editor, such as Notepad, and then print the information from the text editor.
Using Dr. Watson
Dr. Watson (Drwatson.exe) collects detailed information about the state of your system at the time of and slightly before an application fault. Dr. Watson intercepts the software faults, identifying the software that faulted and offering a detailed description of the cause. When enabled, this tool automatically logs this information to the disk (\Windows\Drwatson\*.wlg), and can display it on screen. Dr. Watson indicates the program that caused the application fault, the program the fault occurred in, and the memory address at which the fault occurred. This information can be used to assist product support personnel in determining the cause of the fault.
Starting Dr. Watson
You can configure Dr. Watson to load automatically when Windows starts by creating a shortcut to Drwatson.exe in the Startup folder. This is important when an issue is not easily reproducible. Once Dr. Watson traps the application fault and creates the log, you can contact support for further assistance.
Tip Dr. Watson is best used with reproducible faults. Determining the cause of intermittent faults may prove difficult.
To start Dr. Watson
On the Start menu, click Run, and then type Drwatson. Click OK.
– Or –
Click Start, point to Programs, Accessories, and System Tools, and then click System Information. Select the Tools menu and click Dr. Watson.
Dr. Watson runs minimized, and the icon appears in the Taskbar. Dr. Watson monitors the system for application faults. If an application fault occurs, Dr. Watson generates a snapshot of the software environment. Click the Details button in the error message box to view the information gathered by Dr. Watson.
To generate a log file
- Double-click the Dr. Watson icon in the Windows 98 system tray. Dr. Watson gathers information about the system, and then the Dr. Watson dialog box appears.
When Dr. Watson is loaded, you move out of the text box by clicking any tab. The Dr. Watson window closes if you press the ENTER key.
To view the Advanced tabs in Dr. Watson
Double-click the Dr. Watson icon in the Windows 98 system tray. Dr. Watson gathers information about the system, and then the Dr. Watson dialog box appears.
Click Options, View, and then Advanced View.
The following tabs, which provide detailed information about your system for a support technician, are added to the dialog box:
System
Tasks
Startup
Kernel Drivers
User Drivers
MS-DOS Drivers
16-bit Modules
.gif "Cc768197.wrknn04(en-us,TechNet.10).gif")
Using Dr. Watson with an Application Fault
If you get an application fault, use these general guidelines to isolate the problem.
Try to reproduce the fault to verify that it is not a random failure.
Click Start, point to Programs, Accessories, and System Tools, and then click System Information. Select the Tools menu and click Dr. Watson.
Reproduce the fault.
Click Details on the application fault message box.
Look in the Diagnosis box to determine the source of the fault.
If the problem is intermittent or not easy to reproduce, put Dr. Watson in your Startup folder so that it is always running. The Dr. Watson dialog box provides a text box to provide information about what you were doing when the problem occurred. You should provide which applications were running, and the steps that resulted in the application fault in this box.
Caution After typing the information in the text box, choose File Save or Save As to save the file. If you click OK, the text entered in the text box is not saved.
Customizing Dr. Watson
You customize Dr. Watson by clicking Options from the View menu. Table 27.2 describes these options.
Table 27 . 2 Dr. Watson options in View menu
Option |
Description |
|---|---|
Log Files |
Configures the number of log files to store on the computer and the folder that log files are saved in. |
Disassembly |
Configures the number of CPU instructions and stack frames that are reported in the log file. You need to configure these options only when requested to do so by technical support. |
View |
Configures Dr. Watson to display in Standard View or Advanced View the next time it runs. |
Saving Log Files
When an application fault occurs, the Dr. Watson log file is automatically named Watsonxx.wlg (where xx is an incremented number). By default, Dr. Watson log files are saved to the \Windows\Drwatson folder.
To save the information generated by Dr. Watson
- Click Save on the File menu.
Caution After typing the information in the text box, choose File Save or Save As to save the file. If you click OK, the text entered in the text box is not saved.
Viewing Log Files
You can view a Dr. Watson log file in the Dr. Watson program or from Microsoft System Information (MSInfo).
To view Dr. Watson log files from MSInfo
Open Microsoft System Information (click Start, point to Programs, Accessories, and System Tools, and then click System Information).
Click File, and then click Open.
Go to the folder where you save your Dr. Watson log.
Select Dr. Watson Log File (*.WLG) from the Files of type list.
Select the file, and click Open.
Printing Log Files
Print Dr. Watson log files by selecting Print from the File menu. To print only specific information, use Microsoft System Information to view the log file, and then copy the specific information to a text editor, such as Notepad.
Note A typical Dr. Watson log can be over 15 pages, depending on the software running.
Using System File Checker
System File Checker verifies the integrity of your system files. After scanning for altered files, it offers to restore corrupted files. If a file is found to be corrupt, you will be prompted to restore the original file. By clicking Settings, System File Checker can also be configured to notify you of changed and deleted files. If you choose to restore the file, System File Checker attempts to extract the file from your original Windows 98 installation source.
System File Checker (Sfc.exe) helps you do two things:
Scan system files for corrupt, missing, or changed files. Windows-based applications commonly install shared files that may not be compatible with another application in use. You can use System File Checker to track changes to your Windows configuration and identify the affected files.
Restore original Windows 98 system files.
To start System File Checker
Click Start, point to Programs, Accessories, and System Tools, and then click System Information.
Select the Tools menu and click System File Checker. The following dialog box appears:
.gif "Cc768197.wrknn05(en-us,TechNet.10).gif")
To scan for corrupt files
In System File Checker, click Scan for altered files, and then click Start.
System File Checker scans the system using a default baseline contained in a file named Default.sfc. Default.sfc is copied from the Windows 98 installation source and contains the information shown in Table 27.3 about each system file:
Table 27.3 System File Checker Default.sfc contents
Information |
Description |
|---|---|
Cyclical Redundancy Check (CRC) |
A checksum added to a file entry whenever a file is written to disk. This data is used to see if the file has changed. |
Date, time, size, and version information |
If System File Checker determines a change in date, time, size, or version, it considers the file to be changed. |
When System File Checker identifies a changed file, the user is given several choices to approach the situation. Table 27.4 describes these options.
Table 27 .4 System File Checker options
Option |
Used to |
|---|---|
Update the verification information |
Update the file data in Default.sfc. Choose this option when you have updated a system file without running System File Checker, and are certain that you want to update Default.sfc to use the updated information about the file the next time System File Checker is run. |
Restore file |
Specify the source location of the file to restore and where to save the new copy of the file. You are also prompted to back up the existing file to the \Windows\Helpdesk\SFC folder. Choose to back up the file in case there are problems using the new file. |
Ignore |
Skip the file. The next time System File Checker is run, this file will cause the File Changed dialog box to appear because it was not added to Default.sfc and it was not restored. |
To verify the integrity of your system files
In System File Checker, click Scan for altered files.
Click Start.
Note any files that display a dialog box requesting your action.
When you uninstall a program, System File Checker reports that files necessary for that program (for example, files with .exe, .dll, and .ocx extensions) have been deleted. Select Update verification information to bring the baseline for System File Checker up to date.
If you know a specific system file is corrupt or missing, you can extract it from your original installation media using the following procedure.
To extract a specific system file
In System File Checker, click Extract one file from installation disk.
Enter the name of the file, and then click Start.
In Restore from, type the location of your Windows 98 installation media.
In Save file in, type the location where you want to put the file, and then click OK.
Customizing System File Checker
You can customize the criteria that System File Checker uses to check files. Table 27.5 shows the items that you can customize in the System File Checker Settings dialog box:
Table 27 .5 System File Checker custom settings
Option |
Description |
|---|---|
Settings |
Used to configure how to back up files, log file options, and whether to check for changed or deleted files. |
Search Criteria |
Used to modify the files and folders to scan. |
Advanced |
Used to create a new verification data file, choose a different verification data file to use, or restore the original Default.sfc. |
To customize System File Checker
In System File Checker, click Settings.
Choose one of the three options for Back up file before restoring:
Option
Description
Always back up before restoring
Before restoring the original file, System File Checker will always create a copy of the current file.
Prompt for back up
Before restoring the original file, System File Checker will ask you if you want to save a copy of the current file.
Never back up before restoring
System File Checker will not create copies of the current files before restoring.
The default backup location is C:\Windows\Helpdesk\sfc.
Choose one of the three options for Log File:
Option
Description
Append to existing log
Keeps one log file, and System File Checker adds to that file with every system check.
Overwrite existing log
Overwrites existing log file with every system check.
No log
Does not create a log file.
Click View Log to open the current System File Checker log text file in Notepad.
Check the Check for changed files box to enable System File Checker to prompt you when it finds files that have changed.
Check the Check for deleted files box to enable System File Checker to prompt you when it finds files that have been deleted.
To change the search criteria
Click the Search Criteria tab.
System File Checker shows the list of folders to be checked according to the verification data file.
Click Add Folder to add a folder to the verification data.
Click Add Type to add file extensions to the search criteria.
Enter a file extension. For example, type *.TXT to search for all TXT files.
Click OK.
More Information about System File Checker
Files that are renamed during Windows 98 Setup are not automatically extracted and renamed by System File Checker. For example, Winoa386.new in a CAB file cannot be extracted and renamed to Winoa386.mod.
There are files created during Windows 98 Setup that cannot be found by System File Checker Extract. System File Checker Extract looks for files in the cabinets to extract. If they do not exist in the CAB files, it cannot extract them. For example, files such as Control.ini, Exchange32.ini, and Msbatch.inf are not found.
If you save any changes for the search criteria in Default.sfc, those changes will overwrite the original file.
Points to remember about System File Checker:
System File Checker lets you scan specific system files for errors and restore the original Windows 98 system files.
Files that are renamed during Setup are not automatically extracted and renamed by System File Checker.
Some files created during Setup cannot be found by System File Checker Extract.
If you save any changes for the search criteria in Default.sfc, the changes will overwrite the original file.
Verifying Digital Signatures on Drivers
All drivers shipped with Windows 98 will be digitally signed by Microsoft. You can verify that the drivers you install on your Windows 98 system have met the Windows Hardware Quality Labs (WHQL) standards, and that they have not been modified since they were tested by WHQL. To ensure that the device drivers you are installing are compatible with Windows 98, look for vendors offering drivers signed by Microsoft.
Windows 98 includes the Signature Verification Tool and Signature Checking to identify files that have been signed. This section describes them.
Signature Verification Tool
The Signature Verification Tool (Sigverif.exe) determines whether or not a file is signed. With Sigverif.exe, you can do the following:
View the certificates of signed files to ensure that the file has not been tampered with after being certified.
Search for Signed files in a specific location.
Search for Not signed files in a specific location.
To start the Microsoft Signature Verification Tool
On the Start menu, click Run and then type Sigverif. Click OK.
– Or –
Click Start, point to Programs, Accessories, and System Tools, and then click System Information. Select the Tools menu and click Signature Verification Tool.
Signature Checking on Drivers
Signature Checking can be enabled by system administrators to ensure that Windows 98 inspects files for digital signatures whenever drivers are installed.
Signature Checking has three levels:
Level 0 disables digital signature checking. The dialog box that identifies a digitally signed driver will not appear, and all drivers will be installed on the system if they are signed or not.
Level 1 determines if the driver has passed WHQL testing. A message appears whenever a user tries to install a driver that fails the signature check.
Level 2 blocks installation of a driver that fails the signature check. A dialog box appears with a message informing the user that the driver cannot be installed because it is not digitally signed.
You can start the Signature Checking feature using Policy Editor (Poledit).
To start Signature Checking using Policy Editor
Note For information about setting up, starting, and using Policy Editor, see Chapter 8, "System Policies."
In Policy Editor, set the current Policy Template to Windows.adm, and then open the Default Computer policy.
Enable the check box in Default\Computer\Windows98 System\Install Device Drivers\Digital Signature Check.
The system administrator can set the Security level using the list box.
Caution Making a mistake in editing the registry can cause your system to become unstable and/or unusable.
Wherever possible, use the administrative tools, such as Control Panel or System Policy Editor, to make configuration changes, rather than editing the registry. This is to ensure values are stored properly in the registry when changing the configuration.
If you use Registry Editor to change values, you will not be warned if any entry is incorrect. Editing the registry directly by using Registry Editor can cause errors in loading hardware and software, and can prevent users from being able to start the computer.
You can also start the Signature Checking feature by setting the following registry value:
HKEY_LOCAL_MACHINE \Software \Microsoft \Driver Signing
If the Policy Value is set to "00 00 00 00", the signature checking is set to level 0.
If the Policy Value is set to "01 00 00 00", the signature checking is set to level 1.
If the Policy Value is set to "02 00 00 00", the signature checking is set to level 2.
Using Automatic Skip Driver Agent
Automatic Skip Driver (ASD) Agent is used to detect and automatically disable device drivers or operations that fail during startup. Disabled items can be viewed and re-enabled by running the Automatic Skip Driver Agent (Asd.exe). If you run Asd.exe with no errors in the registry, you will receive a message stating that no critical operation failures occurred.
When Windows 98 starts, it attempts to load all device drivers required for the installed hardware. If a hardware device or its driver is defective, the device driver can fail to load and prevent Windows from starting. Automatic Skip Driver tracks the device load failure using the following steps:
Identifies the specific device(s) that failed to enumerate when Windows 98 started. Enumeration is the process of identifying which Plug and Play devices are in the computer and assigning the appropriate hardware resources to the devices.
After two failed attempts to load, ASD disables the device driver or stops the operation that caused system startup to fail. Windows will no longer attempt to enumerate the component.
If a device is disabled by ASD, it may be identified with a yellow exclamation point (!) in Device Manager. Device Manager identifies devices disabled by ASD with a Code 11.
Along with device drivers, certain problems during startup and during normal operating system operation can be detected by ASD. The following items are examples of operations that ASD monitors:
Starting a device.
Enumerating a device.
Calling a PnP BIOS.
Calling a PCI BIOS.
Calling a VESA BIOS.
Posting a video BIOS.
Mapping an address space.
Setting a graphics device power state.
Posting a video BIOS after standby.
Getting PCI IRQ routing table from a PCIBIOS 2.1 call.
To launch Automatic Skip Driver Agent
On the Start menu, click Run and then type ASD. Click OK.
– Or –
Click Start, point to Programs, Accessories, and System Tools, and then click System Information. Select the Tools menu and click Automatic Skip Driver Agent.
Every problem that ASD has ever detected on that computer is recorded in the Asd.log file.
More Information about Automatic Skip Driver Agent
Automatic Skip Driver Agent tracks device load failures by identifying specific device(s) that failed to enumerate when Windows 98 started.
If a device driver fails to load during startup, run Asd.exe. In the Automatic Skip Driver dialog box, click the operation that failed, and then click Details. The device's Details dialog box appears and provides a recommendation for solving the problem. This may include updating the driver.
Points to remember about Automatic Skip Driver Agent:
The Automatic Skip Driver (ASD) Agent is used to detect device drivers that fail to load or certain operations that fail at startup.
ASD tracks device load failures by identifying the specific device(s) that failed to enumerate when Windows 98 started.
Using Windows Update
Windows Update (lexplore.exe) is an online extension of Windows 98. It helps your computer operate better by providing a central location to find customized files and product enhancements. Product enhancements include service packs, system files, device drivers, and new Windows 98 features.
When Windows 98 is installed, an Internet shortcut to the Windows Update page on www.microsoft.com is created on the Start menu. Windows Update uses Active Setup and ActiveX controls to provide product enhancements. The ActiveX controls are downloaded and installed on your system when you connect to the Windows Update Web page.
Note Windows Update requires browser software that supports ActiveX controls.
Once the controls are installed, they automatically compare device drivers installed on your computer with a database of updated drivers on the server. If any drivers are found to be newer than your current set, they are offered to you to install.
Note Device drivers, system patches, or hot fixes can be uninstalled using the Restore page from the Web site. If you are unable to connect to the Windows Update Web site, you can uninstall the latest updates by using Update Wizard Uninstall (Upwizun.exe) found on the Tools menu of Microsoft System Information. Existing files and drivers are automatically backed up before the new ones are installed.
To use Windows Update
Click Start, and then click Windows Update.
– Or –
Click Start, point to Settings, and then click Windows Update.
Follow the instructions on the screen to install the latest updates.
Windows Update scans your system, generates a list of items that can be updated, and then installs the files for the items you choose to update.
Restricting Access to Windows Update
You can use Policy Editor to restrict access to Windows Update. System administrators can control access to system updates to ensure the Windows 98 configuration remains consistent across all desktops. Use the following check boxes in System Policy Editor to restrict access:
Disable Windows Update disables all access to Windows Update and removes its shortcut from the Start menu.
Override Local Web Page redirects the user to a specified Web page the first time Windows Update is launched.
Override Windows Update Site URL redirects the user to a specified URL when Windows Update is launched.
To restrict access to Windows Update using Policy Editor
Note For information about setting up, starting, and using Policy Editor, see Chapter 8, "System Policies."
In Policy Editor, set the current Policy Template to Windows.adm, and then open the Default Computer policy.
Expand Windows 98 System by clicking the + box next to it, and then select Windows Update.
Disable Windows Update, Override Local Web Page, and Override Windows Update Site URL appear with check boxes next to them. The system administrator can restrict access to Windows Update using the check boxes.
Caution Making a mistake in editing the registry can cause your system to become unstable and/or unusable.
Wherever possible, use the administrative tools, such as Control Panel or System Policy Editor, to make configuration changes, rather than editing the registry. This is to ensure values are stored properly in the registry when changing the configuration.
If you use Registry Editor to change values, you will not be warned if any entry is incorrect. Editing the registry directly by using Registry Editor can cause errors in loading hardware and software, and can prevent users from being able to start the computer.
You can also restrict access to Windows Update by setting the following registry values:
HKEY_LOCAL_MACHINE \Software \Microsoft \Windows \CurrentVersion \Policies \Explorer \NoWindowsUpdate
If the value is set to "1", access to Windows Update is disabled.
If the value for NoWindowsUpdate is deleted, access is permitted.
HKEY_LOCAL_MACHINE \Software \Microsoft \Windows \CurrentVersion \RunOnce \WUCheckShortcut
If the value is set to "WUpdMgr.exe -shortcut", the shortcut to Windows Update is deleted on the subsequent system startup.
HKEY_LOCAL_MACHINE \Software \Policies \Microsoft \WindowsUpdate \Local URL
If a value is specified for a local URL, the first time Windows Update runs, it redirects the user to this location.
HKEY_LOCAL_MACHINE \Software \Policies \Microsoft \WindowsUpdate \Remote URL
If a value is specified for a remote URL, the link to Windows Update redirects the user to this location.
More Information about Windows Update
Points to remember about Windows Update:
Windows Update is an online extension of Windows 98 that helps you maintain a current computer.
You must have browser software that supports ActiveX controls to access Windows Update.
Device drivers, system patches, or hot fixes can be uninstalled using the Restore page from the Web site. If you are unable to connect to the Windows Update Web site, use Update Wizard Uninstall (Upwizun.exe) found on the Tools menu of Microsoft System Information. The original files are automatically backed up to ensure a safe return to the prior state, if needed.
Using the System Configuration Utility
The System Configuration Utility (Msconfig.exe) provides a graphical interface for configuring the Windows 98 startup environment. The System Configuration Utility (MSConfig) lets you troubleshoot by creating a clean environment to test against. If a problem is not reproducible after performing a Diagnostic startup, a process of elimination can be used to identify the source of the issue.
The System Configuration Utility lets you edit lines of Windows 98 configuration files, like Config.sys or System.ini, and provides the ability to "remark" individual lines in the files, preventing the lines from executing or processing on subsequent boots of the computer.
The System Configuration Utility also lets you enable/disable items in your Startup group, and the RUN/RUN SERVICES keys of the registry. You can also use it to create a backup of system files.
To use the System Configuration Utility
Click Start, point to Programs, Accessories, and System Tools, and then click System Information.
From the Tools menu, click System Configuration Utility.
Table 27.6 describes the tabs in System Configuration Utility.
.gif "Cc768197.wrknn08(en-us,TechNet.10).gif")
Select Diagnostic startup to create a clean software environment for troubleshooting, and then click OK to restart the computer.
The Windows 98 Startup menu appears. Select Step-by-Step from the menu options, and choose to process all but the Config.sys and Autoexec.bat files. If, while bypassing these files, the system hangs, restart the computer and step through them line by line, choosing to load all drive overlay and compression software the drive requires.
Determine if the symptoms are alleviated in the clean environment.
If the symptoms are alleviated, a process of elimination can be employed to identify the source of the problem using MSConfig. Continue with step 6 of this procedure to isolate the source of the issue using the Selective Startup Options.
– Or –
If the symptoms still manifest after a Diagnostic startup, investigate the following possibilities:
Advanced troubleshooting options in the System Configuration Utility. For more information, see Table 27.7.
Protected-mode device driver configuration. Launch Device Manager from the View menu in Microsoft System Configuration.
A file is missing, corrupt, or has been replaced. For more information, see "Using System File Checker" earlier in this chapter.
Registry corruption. For more information, see "Using Registry Checker" later in this chapter.
Virus.
Faulty hardware settings. Use the CMOS screen to check the hardware settings.
Unsuccessful upgrade of previous Windows configuration.
Isolate the issue using the Selective startup options.
Using a process of elimination, enable options until the symptoms are reproducible. Once the problem reappears, isolate the issue by narrowing the suspect options down to one source.
Once you have identified the source of the problem, identify the problem using the appropriate tab(s).
Identify issues with the real-mode configuration by disabling all but the Config.sys and Autoexec.bat files and restarting.
Enable the System.ini** **and Win.ini files and restart as prompted to determine if the problem lies in the Windows configuration files.
Test the software loading at startup by enabling the Winstart.bat and Startup options and restarting the system.
The Config.sys and Autoexec.bat tabs use the following conventions to identify settings and minimize the risks inherent in editing configuration files:
Disabled check boxes indicate lines commented out by the tool.
Settings used when the Selective startup option of the file is disabled are identified with a Microsoft Windows logo.
.gif "Cc768197.ch27_01(en-us,TechNet.10).gif")
Previously commented lines are listed without a check box.
A yellow pencil identifies lines edited from within the tool.
The System.ini and Win.ini tabs also follow these conventions and identify sections with a yellow folder. Entire sections can by commented out by disabling the check box for the section.
The Startup tab lists items loading automatically at startup from the Windows 98 Startup group, Win.ini load= and run=, and the registry.
Table 27 .6 System Configuration Utility dialog box tabs
Tab |
Description |
|---|---|
General |
Enable or prevent the loading of all or specific device drivers and software. Prevent the loading of Config.sys, Autoexec.bat, System.ini, Win.ini, and Startup options. Back up or restore Config.sys, Autoexec.bat, System.ini, and Winstart.bat. The Advanced button contains the settings that are described in Table 27.7. |
Config.sys |
Enable or prevent the loading of specific lines in the Config.sys file. Checking a line item edits the Config.sys file and adds REM TSHOOT: to remark out the line. |
Autoexec.bat |
Enable or prevent the loading of specific lines in the Autoexec.bat file. Checking a line item edits the Autoexec.bat file and adds REM TSHOOT: to remark out the line. |
System.ini |
Enable or prevent the loading of specific lines in the System.ini file. Checking a line item edits the System.ini and adds ;REM TSHOOT: to remark out the line. |
Win.ini |
Enable or prevent the loading of specific lines in the Win.ini file. Checking a line item edits the Win.ini and adds ;REM TSHOOT: to remark out the line. |
Startup |
Enable or prevent specific items loaded by the operating system on startup. The information in the Startup tab comes from the registry, Win.ini items on the Startup menu under Programs. |
Table 27 .7 The Advanced button settings of System Configuration Utility
Setting |
Description |
|---|---|
Disable System ROM Breakpoint |
Specifies whether Windows 98 should use ROM address space between F000:0000 and 1 MB for a breakpoint. |
Disable Virtual HD IRQ |
Allows Windows to terminate interrupts from the hard disk controller, bypassing the ROM routines that handle these interrupts. Some legacy hard drives might require that this setting be disabled in order for interrupts to be processed correctly. If this setting is disabled, the ROM routine handles the interrupts, which slows the system's performance. |
EMM Exclude A000-FFFF |
EMM Exclude specifies a range of memory that Windows will not use as an API buffer area. Using or attempting to use certain areas of the upper memory area can interfere with some ISA adapters that use the same memory area. |
Force Compatibility mode disk access |
Forces Windows to use real-mode methods to access the hard drive. No 32-bit disk drivers are loaded in the system (except the floppy driver). Used as a troubleshooting tool to test for problems with protected-mode hard disk drivers. Note that this drastically affects performance. |
VGA 640 x 480 x 16 |
Forces the display to use the industry-standard VGA mode. If the machine is not booting, and this setting allows the machine to boot successfully, then this could indicate a video-related problem. |
Use SCSI Double-buffering |
Grayed out if Windows detected that SCSI double-buffering is required. Enables SCSI double-buffering. Windows 98 detects whether this double-buffering is needed or not, so this should be enabled only if there is a disk access problem. |
Enable Startup menu |
Enables or disables a setting in the Msdos.sys file that controls whether the Start menu appears or not by default. |
Disable ScanDisk after bad shutdown |
Modifies a setting in the Msdos.sys file that controls whether ScanDisk runs automatically following an improper shutdown of Windows 98. |
Limit memory to |
Adds a setting to System.ini that artificially limits the amount of physical memory available to Windows 98. Note that a 16 MB or lower setting may prevent Windows from starting in normal mode. |
Disable fast shutdown |
Instructs Windows 98 to revert to the previous methods of shutting down Windows 98. Some software may not allow this feature, and could manifest problems if fast shutdown is enabled. |
Disable UDF file system |
Disables the Universal Disk Format (UDF) file system for all removable media. Use this to troubleshoot problems encountered with proprietary DVD movie players that are incompatible with UDF. |
Enable Pentium F0 (Lock CmpXchg) workaround |
If an illegal instruction sequence is issued, certain Pentium processors will hang. If this box is checked, Windows will enable the protection routine to avoid hanging under the illegal instruction sequence. Checking this box will write a SWORD registry key "FixP5Lock" with value 1 at HKEY_LOCAL_MACHINE \System\CurrentControlSet\Services\VxD\VMM. Note that this routine makes part of the interrupt description table to be not present, so it is recommended that this feature remain disabled while debugging programs. |
In the System Configuration Utility dialog box, the View menu lets you open other controls in Windows 98, which include the following:
Control Panel
Device Manager
Printers Folder
Display Settings
Multimedia Settings
Fonts Folder
Disabling Entries
When you disable an entry in System.ini or Win.ini from the System Configuration Utility, the following entry is added to the front of the specified line:
;REM TSHOOT:
When you disable an entry in Config.sys or Autoexec.bat from the System Configuration Utility, the following entry is added above and before the specified line:
REM TSHOOT:
Creating Backup Files
Backups of Win.ini, System,ini, Autoexec.bat, and Config.sys can be created with the System Configuration Utility by clicking Create Backup from the General tab. These files have a .pss extension and can later be restored to their original name and configuration by clicking Restore Backup.
Important It is strongly recommended that you create a backup of these four system files before making any changes to an installation with System Configuration Utility.
To create backups of your files
In the System Configuration Utility dialog box, click the General tab.
Click Create Backup.
Click OK.
More Information about System Configuration Utility
The Startup tab lists information about items loading from the registry's run and runservices keys, the Win.ini run= load=, and the Startup group. It does not list Static Virtual Device Drivers (VxDs) and Shell Extensions. Identify items loading automatically at startup as a Static VxD or Shell Extension by using information gathered by Dr. Watson and the software environment category in Microsoft System Information; refer to the product's documentation for instructions on disabling or uninstalling the software.
Points to remember about the System Configuration Utility:
The System Configuration Utility can be used to control the Windows 98 startup environment.
Use the System Configuration Utility to edit Config.sys, Autoexec.bat, System.ini, Win.ini files, and the Startup group.
When changing any of the files listed in the previous bullet, the originals are renamed with the file extension .tsh and a new file is created.
The View menu lets you open other troubleshooting controls in Windows 98, including Control Panel, Device Manager, Printers Folder, Display Settings, Multimedia Settings, and Fonts Folder.
When you disable an entry in System.ini or Win.ini, ;REM TSHOOT: is added to the front of the particular line.
When you disable an entry in Config.sys or Autoexec.bat, ;REM TSHOOT: is added above and before the particular line.
When a line is editing in the System Configuration Utility, a pencil icon appears next to the edited line.
When creating a backup, the files are renamed with the .pss extension in the same folder as the original.
Using Registry Checker
Registry Checker is a system maintenance program that finds and resolves some registry problems, and regularly backs up the registry. Windows 98 provides an MS-DOS-based version for scanning the registry, backing up, and restoring the registry and system configuration files, and a Windows-based version for scanning and backing up the registry.
Registry Checker backs up the registry each day following a successful Windows 98 system startup, maintaining one backup for each day. If a serious problem is found in the registry, Registry Checker will restore the most recent registry from a backup copy.
Note If you want to restore an earlier version of the registry, you must use the MS-DOS-based utility outside of Windows.
Registry Checker maintains compressed backups of the registry and configuration files that have successfully started the computer. Registry Checker will attempt to fix the registry only if a valid backup cannot be found.
ScanRegW is the Windows-based version. This program scans the registry for corruption and determines if it requires optimization, and then backs up the following system configuration files: registry (User.dat and System.dat), Win.ini, and System.ini. This scan occurs automatically when the system is started. You can run Scanregw.exe to force a scan and backup of these files. ScanRegW backs up the registry and configuration files using a compressed CAB file in the \Windows\Sysbckup directory.
ScanReg is the MS-DOS-based version. If ScanRegW detects a problem with the registry, it prompts you to restart the computer to fix the problem, and ScanReg will run automatically. It either restores a known good backup or, if no backups are available, attempts to repair the current registry by removing the corruption. If ScanRegW detects that optimization is required, ScanReg will optimize the registry on the subsequent startup.
For more information about the registry, see Chapter 31, "Windows 98 Registry." For information about restoring a registry, see "Restoring the Registry" later in this chapter.
ScanRegW versus ScanReg
Table 27.8 identifies the differences between ScanRegW and ScanReg.
Table 27 .8 Differences between ScanRegW and ScanReg
Function |
ScanRegW |
ScanReg |
|---|---|---|
Environment |
Windows |
MS-DOS |
Real-mode or Protected- mode? |
Protected-mode |
Real-mode |
Scan registry? |
Yes |
Yes |
Fix registry? |
No |
Yes |
Backup registry? |
Yes |
Yes |
Runs in Safe Mode? |
Yes |
No |
Compresses backup |
Yes |
No |
Runs automatically? |
Yes, every time computer is started. |
Yes, if a registry problem is detected. |
Restores the registry? |
No |
Yes |
Command-line Options
Table 27.9 describes command line options for the ScanRegW and ScanReg utilities of Registry Checker.
Table 27 .9 Command line options for Registry Checker
Command line option |
Description |
Available for |
|---|---|---|
/backup |
Backs up the registry with no prompts to the user. |
ScanReg and ScanRegW |
/restore |
Displays a list of backup files available, sorted by date and time of the backup. |
ScanReg |
"/comment" |
Specifies that a comment be associated with the backup. The comment is displayed with the /restore command. For example: "/comment=this is a backup comment." |
ScanReg and ScanRegW |
/fix |
Repairs the registry files. |
ScanReg |
/autoscan |
Scans the registry files every time it is run, but backs up the registry only once per day. |
ScanRegW |
/scanonly |
Scans the registry files and returns an error, if appropriate; it does not back up the files. |
ScanRegW |
ScanReg.ini
Both ScanRegW and ScanReg use settings from the Scanreg.ini file. Table 27.10 lists the settings.
Table 27 .10 Scanreg.ini settings
Keyname and default value |
Function |
Other values |
|---|---|---|
Backup=1 |
Run ScanReg at startup and make a backup automatically. |
0: ScanReg is not run at startup |
Optimize=1 |
Run ScanReg to optimize the registry, reducing its size to improve performance. |
0: Automatic optimization is skipped |
MaxBackupCopies=5 |
Number of backups to store in the backup folder. |
0 to 99 |
BackupDirectory= |
Backup directory where CAB files are stored. Must be a full path, for example c:\tmp\backup. |
Defaults to Windows\sysbckup |
Files=[dir code,] file1,file2,file3 |
Additional system files to backup into the CAB file. File names are separated by a comma (,). |
None |
Note If ScanReg cannot create a backup in the location specified by the Backup folder in the Scanreg.ini file, it defaults to placing the CAB file in the \Windows folder.
Using ScanRegW to Back up the Registry
Registry Checker automatically makes a backup of your registry once per day as the computer starts, but you can also manually make periodic backups of the registry using ScanRegW. There are several reasons to back up the registry, for example, before editing the registry using Registry Editor, or before installing an application.
ScanRegW stores the backup as a RB0##.cab file in \Windows\Sysbckup, which is a hidden folder. The symbols ## represent backups using digits from 01 to 99 (05 is the default for the number of backups). The files are compressed CAB files (like the files on the Windows 98 compact disc). If you run ScanRegW and your system already has the maximum RB0##.cab files as indicated in Scanreg.ini, the oldest one is deleted.
The RB0##.cab file contains the following files:
System.dat
System.ini
User.dat
Win.ini
To back up your registry
On the Start menu, click Run.
Type ScanRegW, and then click OK.
After scanning the system registry, ScanRegW displays a dialog box asking if you would like to back up the registry. Click Yes.
.gif "Cc768197.wrknn09(en-us,TechNet.10).gif")
– Or –
Type ScanRegW /autoscan to automatically back up the registry without a dialog box. Use this command line switch to have ScanRegW scan and back up the registry as a scheduled task.
Click OK when backup is complete.
ScanRegW informs you when the backup is complete. The backup is stored as the file RB0##.cab in the hidden \Windows\Sysbckup folder.
More Information about Registry Checker
Registry Checker runs automatically with each startup to determine if the system registry has errors, and to back up the registry. Some more points to remember about Registry Checker:
ScanRegW scans and backs up registry (User.dat and System.dat), Win.ini, and System.ini files.
Do not use backups of core configuration files from Windows 95 on a Windows 98 system. The computer will not start.
Backups are stored by default as a file called RB0##.cab in a hidden \Windows\Sysbckup folder.
ScanReg creates RB0##.cab files, where ## represents increments from 01 to 99 (5 is the default setting). The CAB files are compressed using the same compression as the Windows installation media. As such, they can be opened within Windows by double-clicking the file.
To restore a backup, boot to a command prompt and type Scanreg/Restore. For more information, see "Restoring the Registry" later in this chapter.
Using MS Backup
You should perform a full backup of your system regularly to have a current backup of your entire system available to restore in case of hard disk failures. Windows 98 includes a new backup utility called Microsoft Backup (Msbackup.exe), which supports a wider range of backup devices than the Windows 95 backup utility. Support has been added for parallel, IDE/ATAPI, and SCSI backup devices.
Several devices are supported, including the following:
QIC-80 and 80 Wide, 3010 and 3010 Wide, and 3020 and 3020 Wide
TR1, 2, 3, and 4 (Travan)
DAT (DDS1 and 2)
DC 6000
8mm
DLT
Removable media (floppy disks, Iomega Jaz or Syquest cartridges)
Note QIC-40 backup devices are no longer supported by the Windows 98 backup utility.
Installing MS Backup
Microsoft Backup is not a default selection for the Windows 98 installation process. If the utility is installed on Windows 95 before Windows 98 Setup is run, Microsoft Backup will be installed during Setup.
The tool can be added using Add/Remove Programs in Control Panel. It is located in the Disk Tools component. Microsoft Backup requires the same minimum configuration for Windows 98 as well as a hard drive with at least 5.2 MB free disk space. When the backup utility is installed, the program is added to the System Tools menu under Start\Programs\Accessories.
To install Microsoft Backup
In Control Panel, double-click Add/Remove Programs.
Select the Windows Setup tab.
Double-click System Tools.
Check the box next to Backup.
Click OK.
Click Apply.
Copying the files for the selected components runs automatically.
Click OK to complete the installation.
To configure a backup device
- Most backup devices are automatically detected and configured either when you install the device and restart the computer or the first time you run Microsoft Backup. If you install a new device and it is not detected on Startup, go to Control Panel, and use Add New Hardware to detect the device.
To start Microsoft Backup
Click Start, point to Programs, Accessories, and then System Tools.
Click Backup.
If Windows 98 does not detect a backup device, it asks you if you want the Add New Hardware applet. Click Yes, and add the device, or click No to continue.
A dialog box displays three choices, Create a new backup job, Open an existing backup job, and Restore backed up files.
.gif "Cc768197.wrknn11(en-us,TechNet.10).gif")
Click Create a new backup job, and then click OK.
Backup Wizard leads you through the steps required to create a new backup job. The backup utility uses backup jobs to save and reuse file or option selections and to perform backups.
Note Backup Wizard is used only to create new backup jobs. It cannot be used to modify an existing job.
Backup Wizard Configuration
When naming a Backup, you cannot use these characters: \ / : ? * " < > |
To change a setting or review the backup job's summary while progressing through the wizard, use the Back and Next buttons.
If the medium being used to back up the files does not have a unique name, a prompt will be displayed for naming it.
Removable media devices are supported when specifying the option in Microsoft Backup to back up to a file rather than a removable drive.
Restore Wizard Configuration
You can select your files from the catalog stored on your hard disk or from the tape in your drive.
Files are restored in their original folder structure unless you choose to restore all files to an alternate location.
Using Restore Wizard
Restore Wizard presents a series of dialog boxes that lead you through the steps required to restore a backup job. Restore Wizard can be launched from the Microsoft Backup Tools menu or from the Microsoft Backup toolbar.
Note You can restore backups made with the Windows 95 backup. You cannot restore backups made with MS-DOS version 6.x or earlier.
To use Restore Wizard
Click the Restore Wizard button on the Microsoft Backup toolbar, and follow the directions on the screen.
Restore is successful when the Operation completed dialog box appears. Click OK.
Using Reports
Both Backup and Restore create a report for the operation. If unsuccessful, the report can give an indication as to why.
A sample report is shown below.
Start Job Report Job Name: Restore Restore Job Started - 8/13/97 1:47:47PM Processed File Count: 1 Total Bytes Before Compression: 180,736 Operation Completed - Yes Restore Job Ended - 8/13/97 1:47:49PM End Job Report
To set options for the report
Start Microsoft Backup, and then click the Close button in the Welcome to Microsoft Backup window.
Click the Options button, and then click the Report tab.
To view or print a report
Click the Tools menu, and then click Reports.
Click either View or Print.
Note A history of the backup and restore operations for the machine can be found in \Program Files\Accessories\Backup\Reports\Report.txt. You can open the file in Notepad.
Backing up without the Wizard
You can back up files without using Backup Wizard.
To back up without using Backup Wizard
Start Microsoft Backup, and then click the Close button in the Welcome to Microsoft Backup dialog box.
Type the name for the backup job in the Backup Job field.
In What to back up, if All selected files is selected, then all files chosen are backed up. If New and changed files is selected, only new and/or changed files from the previous backup are backed up.
Select which files to back up.
To back up an entire drive, click the box next to the drive.
– Or –
To back up individual folders or files, click the + next to the drive and select the folders, or click the + next to a folder and select files.
Note Back up removable media as a File.
Select the media for the destination for the backup in Where to back up. Type the path to the backup destination, or click the folder icon to the right for the destination.
Click Options to select options for this backup.
The Backup Options dialog box has the following tabs: General, Password, Type, Exclude, Report, and Advanced. Click ? for a description of the features on these tabs. Click OK to return to the Backup Options dialog box.
Click Start to begin the backup.
Restoring without the Wizard
You can restore files without using Restore Wizard.
To restore without using Restore Wizard
Start Microsoft Backup, click the Close button in the Welcome to Microsoft Backup dialog box, and then click the Restore tab.
Select the media where the backup job is located in Restore from.
Next to the Restore from box, type the name of a QIC file, or click the folder icon to the right and search for it.
Click Refresh to open the backup set(s) from the source location specified in Restore from.
Choose the Original or Alternate location for Where to restore.
Click Options for this restore.
The Restore Options dialog box has the following tabs: General, Report, and Advanced. Click OK to return to the Restore Options dialog box. The restore general options are displayed in How to Restore.
Click Start to begin restoring files.
More Information about MS Backup
Points to remember about Microsoft Backup:
Supported devices for Microsoft Backup include (but are not limited to): QIC-80 and 80 Wide, 3010 and 3010 Wide, and 3020 and 3020 Wide, TR1, 2, 3, and 4 (Travan), DAT (DDS1 and 2), DC 6000, 8mm, DLT, and Removable media (for example, floppy disks, and Iomega Jaz or SyQuest cartridges).
QIC-40 backup devices are no longer supported by the Windows 98 backup utility.
You can restore backups made with the Windows 95 backup utility.
You cannot restore backups made with MS-DOS version 6.x or earlier.
Microsoft Backup is not a default selection for the Windows 98 installation process. If the utility is installed on Windows 95 before Windows 98 Setup is run, Microsoft Backup will be installed during Setup.
Backup Wizard is used only to create new backup jobs. It cannot be used to modify an existing job.
Using MS System Recovery
Microsoft System Recovery (Pcrestor.bat) is a quick and easy method to restore your system from a backup. The recovery tool operates completely from protect mode (within the Windows operating system environment).
Microsoft System Recovery takes advantage of the scripting extendibility of the Windows 98 Setup program to install Windows 98, while maintaining access to the Win32 APIs and other critical system resources (such as networks, removable media, and tape devices) needed to access your data.
Microsoft System Recovery uses Msbatch (Msbatch.inf), an automated setup process, to install a minimal Windows 98 environment. Microsoft System Recovery copies Msbatch to a directory called \Restore on the hard drive, and then starts the install process. There are no prompts during the setup process since Msbatch automates the entire setup program. Msbatch is described in detail in Appendix D, "Msbatch.inf Parameters for Setup Scripts."
Finally, Microsoft System Recovery uses a wizard to walk you through the process of recovering system files through Microsoft Backup.
Important You should perform a full backup of your system regularly to have a current backup of your system available to restore in case of hard disk failures. Microsoft System Recovery requires a backup to restore your system files.
It is recommended that you back up your system files at least once a week. For more information about backing up your files, see "Using Microsoft Backup" earlier in this chapter.
To start a system recovery using Microsoft System Recovery
Start the computer using the Windows 98 Startup Disk.
At the command prompt, change the directory to \Tools\Sysrec.
Type pcrestor, and then follow the directions on the screen.
After Windows 98 is set up, Microsoft Recovery Wizard walks you through the process of restoring system and application files from Microsoft Backup. In addition to Microsoft Backup, the System Recovery Wizard installs Microsoft Notepad and Wordpad.
Tip Click the Details button in the wizard for help in recovering your files.
More Information about MS System Recovery
Microsoft System Recovery operates completely in protect mode, and uses an automated batch program to install a minimal Windows 98 environment. It then uses a wizard to step you through a recovery process that lets you recover all or part of your system.
The following is a list of the benefits of Microsoft System Recovery:
No need to create a separate set of disks. The Startup Disk has drivers for most CD-ROM drives, and contains tools to help solve startup problems.
Microsoft System Recovery supports IDE and SCSI removable media devices. Most tape drives, removable drives, and network shares are supported for system restore.
Operates completely in protect mode for faster input/output and system performance.
Simple batch install script makes setup and recovery fast, automatic, and safe.
You can restore the entire system or only certain parts of it.
Scheduling Tasks
Scheduled Task Wizard lets you run useful utilities and routine tasks at regular intervals. You can set the tasks to run at times that are most convenient for you.
Once you have a task scheduled, an icon appears in the Windows taskbar.
.gif "Cc768197.wrknn13(en-us,TechNet.10).gif")
Note If you are upgrading a Windows 95 installation in which System Agent is installed, the System Agent tasks are inherited by the Scheduled Task.
To schedule tasks
Double-click My Computer, and then double-click Scheduled Tasks.
Double-click Add Scheduled Task to start the Scheduled Task Wizard.
Click Next, and enter the information as prompted by the wizard.
For more information about Scheduled Task Wizard, see Chapter 23, "System and Remote Administration Tools."
Using Maintenance Wizard
Maintenance Wizard is used to schedule several performance-improving tasks, such as Disk Defragmenter, ScanDisk, Disk Cleanup, and Compression Agent (on DriveSpace 3 drives).
Note Microsoft Plus! for Windows 98 includes two additional features: you can clean up your Start menu, and you can clean up orphan links in Add/Remove Programs. To obtain Microsoft Plus! for Windows 98, contact your Microsoft reseller.
You can choose time of day or night, or customize the schedule to run the performance improving tasks.
The following list shows a typical schedule for these tasks:
Defragmenter programs, every Wednesday at 1:00 A.M.
ScanDisk, every Tuesday at 1:00 A.M.
Disk Cleanup, every first day of the month at 12:30 A.M.
Compression Agent, every Friday at 1:00 A.M.
For more information about Disk Defragmenter, ScanDisk, and Disk Cleanup, see Chapter 10, "Disks and File Systems."
To start Maintenance Wizard
- Click Start, point to Programs, Accessories, System Tools, and then click Maintenance Wizard.
To view scheduled tasks
- Double-click My Computer, and then double-click Scheduled Tasks. Your tasks appear in the Scheduled Tasks window, preceded by the word "Tune-up" or "Maintenance."
Note You can also launch Maintenance Wizard from the Welcome to Windows 98 screen, which appears after you set up the Windows 98 software.
You can start and run all the tasks in succession anytime with the Tune-Up**/**autorun switch.
To run the tasks in succession
On the Start menu, click Run, and then type Tuneup /autorun. Click OK.
The tasks will run automatically in succession. This does not change the schedule for the tasks that you set in Maintenance Wizard.
Version Conflict Manager
Sometimes, when installing software, you may have a newer version of a file on your system than the one being installed. Windows 98 Setup automatically installs the Windows 98 file over the newer file and stores the newer version of the file in the \Windows\VCM folder. Those files can be viewed with Version Conflict Manager (VCM).
Note The determining factor in identifying an older file is the file version, not the file date.
You can use Version Conflict Manager (Vcmui.exe) to restore an application's version of a file. Reinstalling the entire application is no longer necessary.
To launch Version Conflict Manager
- Click Start, point to Programs, Accessories, System Tools, and then click System Information. Select the Tools menu and click Version Conflict Manager.
Version Conflict Manager displays the file name, the backup date, and the backed- up version of every newer file that was replaced. It also lists the current version being used of that file.
When Version Conflict Manager restores an older file, the older file is moved in the \Windows\VCM folder with the extension changed to .000. You can then use Version Conflict Manager to determine the original configuration.
More Information about Version Conflict Manager
Points to remember:
Windows 98 Setup automatically installs any older Windows 98 files over the newer files on your system.
The determining factor in identifying an older file is the file version, not the file date.
During Setup, newer version files are moved and stored in the \Windows\VCM folder.
When VCM restores an older file, the older file is moved in the \Windows \VCM folder with the extension changed to .000. You can then use VCM to return to the original configuration (using the older file with the newer file stored in \Windows\VCM).
Using Windows Report Tool
The Windows Report Tool (Winrep.exe), is an Internet-based information gathering tool that is installed with Windows 98. This tool provides a means for uploading system information to a support provider for diagnosis.
With the Windows Report Tool, you can submit problem reports over the Internet to a technical support center, or across an intranet to a corporate help desk. The problem report includes system data and can include configuration files. To use Windows Report Tool, you connect to a Web page, and then, using ActiveX control and scripting, the Windows Report Tool is invoked on the local computer.
If you cannot connect to a Web page, you can launch the Windows Report Tool (Winrep) from the Tools menu in the Microsoft System Information utility and save the report as a CAB file. The report can then be transferred to support personnel another way, such as by using FTP or by copying the file to a computer that is connected to the Internet and using Winrep on that system to open and submit the report.
Support personnel using MSInfo to open the CAB file can view the report. For information about MSInfo, see "Using Microsoft System Information" earlier in this chapter. Winrep can write information to a SQL database to track the service requests.
This section describes how to generate a report using Windows Report Tool, and then submit it to a Web server. For information about how to design the Web server to accept Windows Report Tool reports and to update a database, see the paper "OEM and Corporate WinRep Integration" on the Microsoft Windows 98 Resource Kit compact disc.
Note For best results, establish a connection to the Internet before launching Windows Report Tool. If you need to create a new Internet connection, run the Internet Connection Wizard.
To use Windows Report Tool to submit a report
Launch Windows Report Tool from your support Web page.
From the Options menu, click User Information. Fill out the demographic information. At the very least, include phone number(s) and e-mail address.
If you are experiencing problems submitting the report from behind a firewall, select Use alternate data format proxy server. This will reduce the size of the packets sent by Winrep, and use a different data format that is compatible with most proxy servers.
Note Enabling the Use alternate data format proxy server feature will slow down the upload process.
Type a problem in the Problem description box that describes your experience. Include the exact text of any and all error messages encountered.
Tip The first line of the problem description will become the report's title, so use this to summarize the contents of the report.
Type an explanation in the Expected results box detailing the behavior you expect when this problem has been addressed.
Type a detailed history of the events leading up to the issue in the Steps to reproduce the problem box. It is helpful if you number the steps.
From the File menu click Save to back up your work and maintain a record of your issue.
Click Next and follow the instructions given by the support provider to upload your report.
You can also use Windows Report Tool to generate a report, without first connecting to a Web page.
To use Windows Report Tool without first connecting to a Web page
Click Start, point to Programs, Accessories, System Tools, and then click System Information.
Select the Tools menu and click Windows Report Tool.
Optionally, if your support provider asks you to do so, type a space and enter a product information number, including the dashes in the correct places.
Optionally, type a space and then type the name of a CAB file to open, then type another space. This lets you open a previously generated report.
Press the ENTER key to launch Winrep.
Fill out the report form as the procedure "To use Windows Report Tool to submit a report" instructs.
From the File menu, click Save to back up your work and maintain a record of your issue.
Optionally, save the report to a floppy disk, copy it to another system with Internet access, connect to your support provider's Web site, and follow the directions they provide to upload the report.
Using MS-DOS Report Tool
The MS-DOS Report Tool (Dosrep.exe) is an Internet-based reporting tool that can be run outside of Windows (in real-mode). This tool was created to upload system information to a Support Engineer when Windows is not accessible.
To use MS-DOS Report Tool
To launch MS-DOS Report Tool, boot to a command prompt outside of Windows and run Dosrep.exe from the Windows directory. Have your user name, password, and phone number to call your Internet Service Provider (ISP) available.
Note The list of files uploaded by MS-DOS Report Tool is configurable. Edit the Dosrep.ini to add or remove files to be uploaded by the tool.
To receive reports generated by the MS-DOS Report Tool, you must use a File Transfer Protocol (FTP) server on the Internet. Provide users with either the Internet Protocol (IP) address or the friendly name (DNS or HOST) of the FTP server. Also, provide them with the name of the directory on your FTP server in which they will submit reports. The MS-DOS Report Tool then creates the specified directory on the FTP server share and uploads a cabinet (CAB) file to it. To view the uploaded report, use MSInfo to open the report in the directory you specified, and then access its contents.
More Information about MS-DOS Report Tool
Points to remember:
MS-DOS Report Tool is a real-mode reporting tool. As such, you must have access to your modem outside of Windows. Controller-less modems, or Windows only modems, and PC Card modems may not work because they rely on Windows for functionality. To test your modem, type the following at the command prompt outside of Windows:
ECHO ATDT > COM x [enter]
Where x is the COM port your modem is using.
If you do not hear a dial tone, your modem is not accessible at that COM port in real-mode. You can still use the MS-DOS Report Tool to gather system information by typing:
DOSREP [enter]
and then clicking the option named Create and save report.
This will generate a CAB file comprised of the system files that could be uploaded using another machine connected to the Internet. The Windows Report Tool can be used to upload reports created using the MS-DOS Report Tool.
MS-DOS Report Tool will only work with modems. ISDN adapters may not be recognized.
For the MS-DOS Report Tool to be able to submit log files over the Internet, your ISP must support Point-to-Point Protocol (PPP) and clear-text password authentication protocol (PAP).
Troubleshooting Procedures
This section provides basic instructions for troubleshooting problems that may occur when running Windows 98.
Important Create and keep a Startup Disk, and verify that it works before you need it (create and test two Startup Disks for even better protection). Use Registry Checker (ScanRegW) often to backup system configuration files.
A particularly good time for backing up files and updating the Startup Disk is before you install new devices and applications, when you have a known good configuration.
Checking for Free Disk Space
Running out of space on the disk drive used for TEMP and swap files can cause a variety of operational and installation errors. If you need more disk space, see the troubleshooting aid for disk space problems in Help.
To check for free space, try the following:
Click Start, point to Programs, Accessories, System Tools, and then click System Information to view the total and available disk space.
Use the chkdsk drive command at the command prompt to display the available disk space in the Bytes Available on Disk line.
Use the dir drive command at the command prompt to view the bytes free at the end of the DIR display.
You might want to check the swap file settings.
To check the swap file settings
Click Start, point to Programs, Accessories, System Tools, and then click System Information to view the location of the swap file and the available disk space on that drive.
– Or –
In Control Panel, double-click System, click the Performance tab, and then click Virtual Memory.
Important By default, Windows 98 manages the virtual memory settings automatically. Changing these settings manually can adversely affect system performance. The recommended setting in this dialog box is to let Windows manage virtual memory settings.
To check for lost allocation units from a command line
Press and hold down the left CTRL key during system startup to access the Windows Startup menu, and when it appears, select Command Prompt Only.
Note Selecting Safe Mode Command Prompt Only will not load the extended memory driver Himem.sys. The MS-DOS version of ScanDisk requires Himem.sys be loaded to check FAT32 drives.
Run ScanDisk from the \Windows\Command directory, and specify the drive to inspect. For example, you would type SCANDISK C:\ to inspect the C:\ drive.
ScanDisk detects lost allocation units and prompts you to recover them as files. The files will have a .chk extension.
For information about running ScanDisk in Windows 98, see Chapter 10, "Disks and File Systems."
To check the TEMP variable
At the command prompt, type set to display the TEMP variable.
Verify that the TEMP variable points to a valid drive and directory.
Check for free disk space on the drive that contains the TEMP directory. If you are printing multiple copies of a large document, or printing large PostScript documents, increase the minimum available free disk space.
Checking for Disk Corruption
Key operating system data structures prevent system startup if they are damaged. These structures include the master boot record, the boot sector, the file allocation table, and the core operating system files.
Caution Back up key data files before performing any disk repair operations. Do not run any disk utilities that are not specifically designed for Windows 98. Earlier versions of disk repair utilities may not work properly. To prevent possible data loss, use a disk utility, such as ScanDisk, that is specifically designed for Windows 98. For details, see Chapter 10, "Disks and File Systems."
To check for disk corruption with Safe Mode Command Prompt Only
Restart the computer, pressing and holding down the left CTRL key when the Starting Windows 98 message appears, and then select the Safe Mode Command Prompt Only option.
Note Selecting Safe Mode Command Prompt Only will not load the extended memory driver Himem.sys. The MS-DOS version of ScanDisk requires Himem.sys be loaded to check FAT32 drives.
Change to the \Windows\Command directory, and then type scandisk.
This method also checks and repairs the file allocation table.
If corruption is detected, you may need to replace system files. For more information, see "Using System File Checker" earlier in this chapter.
Checking for Correct File Versions
With Windows 98, you can use System File Checker (SFC) to look for system files that have been changed by applications. You can configure System File Checker to notify you when a change is discovered. System File Checker will prompt you to restore the original file from the installation source of your Windows 98 files.
System File Checker scans specific system files for corruption, changes, and to determine if they have been deleted. When configured to do so, it prompts you to restore the original Windows 98 system files.
To scan system files
Click Start, point to Programs, Accessories, and System Tools, and then click System Information.
Select the Tools menu.
Click System File Checker.
Click Scan for altered files and then click Start.
You can also view a file's properties to determine its version number and other information such as its date. You can use this information to determine whether a DLL or other system file is mismatched to your system.
To view information about a system file
In Windows Explorer, right-click the file name, and then click Properties in the context menu.
For a supporting or executable file, click the Version tab. Use the Other Version Information list to see details about the file.
Replacing Corrupted Files
If you have isolated a corrupted file, use System File Checker to restore a working file.
To replace a corrupted file
Click Start, point to Programs, Accessories, and System Tools, and then click System Information.
Select the Tools menu and then click System File Checker.
Select Extract one file from installation disk to restore the original system file, select the file to extract, and then click Start.
Ensure the path to Restore from: is correct and click OK.
In the Backup File dialog box, either accept the default or change the path.
If a dialog box appears explaining the folder does not exist, click Yes.
System File Checker finishes extracting the file and notifies you when it completes the action.
Click OK to return to System File Checker.
Updating System Files and Drivers
Windows Update is the Web extension of Windows 98, and is designed to help your computer operate better. Windows Update contains a central catalog of new product enhancements, including service packs and new Windows features. In addition, Windows Update lets you update system files and device drivers specific to your computer.
To update a file, see "Using Windows Update" earlier in this chapter.
Checking Entries in Startup Files
The Config.sys and Autoexec.bat files contain system startup drivers, settings, and paths, and you may need to verify the accuracy of these entries.
Use the System Configuration Utility to check entries in files. See "Using the System Configuration Utility" earlier in this chapter.
Using Windows 98 Command-Line Switches
Starting Windows 98 with command-line switches is an effective method for isolating issues with your configuration. The switches should be used for troubleshooting only. Use the information to modify your existing configuration and eliminate the conflict. The following switches are available to start Windows 98 from the command prompt:
win [/d:[f] [m] [s] [v] [x]]
To use the command-line switches
Start Safe Mode by starting the computer and pressing and holding down the left CTRL key as Windows 98 starts.
Choose Command Prompt Only at the Windows 98 Startup menu.
Start Windows 98 using the troubleshooting command-line switches by typing win /d: at the command prompt, and adding the appropriate switches
The /d: switch is used for troubleshooting when Windows 98 does not start correctly. The switches in Table 27.11 can be used with the /d: switch.
Table 27 .11 Windows 98 command-line switches
Switch |
Description |
|---|---|
f |
Turns off 32-bit disk access. This is equivalent to disabling the hard disk controller(s) in Device Manager. Try this if the computer appears to have disk problems, or if Windows 98 stalls. This is equivalent to 32BitAccess=FALSE in System.ini. |
m |
Starts Windows 98 in Safe Mode. |
s |
Specifies that Windows 98 should not use ROM address space between F000:0000 and 1 MB for a break point. Try this if Windows 98 stalls during system startup. This is equivalent to SystemROMBreakPoint=FALSE in System.ini. |
v |
Specifies that the ROM routine will handle interrupts from the hard disk controller. This is equivalent to VirtualHDIRQ=FALSE in System.ini. |
x |
Excludes all of the adapter area from the range of memory that Windows 98 scans to find unused space. This is equivalent to EMMExclude=A000-FFFF in System.ini. If this switch resolves the issue, you may have a conflict in the upper memory area (UMA) that requires an Exclude statement. |
Note Each of the System.ini file entries referenced in Table 27.11 belongs in the [386Enh] section of the System.ini file.
Troubleshooting Problems with System Startup
If a computer fails to start Windows 98, start the computer in Safe Mode to try to resolve the problem. Starting Windows 98 in Safe Mode can help you resolve issues that occur when you start Windows 98 normally. These issues include (but are not limited to):
Setup hangs during the first reboot.
Error messages.
Hanging.
Loss of functionality.
Starting Windows 98 in Safe Mode bypasses the current real-mode configuration and loads a minimal protected-mode configuration, disabling Windows 98 device drivers and using the standard VGA display adapter.
If the issue does not occur in Safe Mode, you may be experiencing a conflict with hardware settings, real-mode configuration issues, incompatibilities with legacy Windows programs or drivers, or registry damage.
From within Safe Mode, use the following tasks to find a problem in startup. Many of these steps require changes to system configuration files. The changes are not intended to be permanent; they are techniques for isolating the conflict that resulted in an issue with the normal configuration.
Note Before making changes, create a Windows 98 Startup Disk if you do not already have one. Use Add/Remove Programs in Control Panel to create a Startup Disk.
To troubleshoot system startup in Safe Mode
Start Safe Mode by starting the computer and pressing and holding down the left CTRL key as Windows 98 starts. Determine if the symptom is alleviated.
Start Microsoft System Configuration Diagnostic Startup.
If Microsoft System Configuration Diagnostic Startup starts, go to "Using the System Configuration Utility" earlier in this chapter.
– Or –
If Microsoft System Configuration Diagnostic Startup does not start, continue to step 3 of this procedure.
Enable these Windows Diagnostic switches in Microsoft System Configuration Advanced options:
Disable System ROM Breakpoint
Disable Virtual HD IRQ
EMM Exclude A000-FFFF
Force Compatibility mode disk access
Check protected-mode device configuration:
Check Microsoft System Information Problem Devices category to find problems.
Check Device Manager to disable device drivers to test and/or correct the configuration.
If you suspect a corrupt registry, use scanreg /restore to get a known good backup of the registry.
Check for device conflicts in Microsoft System Configuration's Conflicts/Sharing category below Hardware Resources.
Check for an outdated or damaged VxD by examining Bootlog.txt, and then do the following:
If it is in the Windows System\Iosubsys directory, rename it.
If it has a .386 filename extension, examine the [386Enh] section of System.ini and remark out its lines. When renaming VxDs, be sure to change the .vxd extension. Windows 98 loads all files in the Iosubsys subdirectory that have a .vxd extension.
If it is in Vmm32.vxd, check the \Windows System\Vmm32 directory for a Vmm32 file, and rename or move it.
Restoring the Registry
Windows 98 introduces the Registry Checker that scans the registry for corruption and backs up configuration files once a day. The utility maintains multiple backup sets that can be restored as required. For example, you might restore a previous day's backup if you have installed something on your computer with undesirable results but it did not corrupt the registry. In that event, you could run ScanReg /Restore to return the system to its previous state. ScanReg is the MS-DOS-based Registry Checker.
ScanReg provides a list of available backups and indicates whether the system configuration files stored in the CAB have been used to start Windows 98 successfully. Generally, you should choose the CAB file that was most recently used to start Windows 98. However, returning the system to an older configuration may be warranted when the origin of the undesirable behavior is unknown.
To restore a Registry Checker backup
Note If the computer failed to start because the registry is corrupt, ScanReg will automatically fix the problem. If the computer failed to start because of a change to the registry's content, and the registry is not corrupt, then running ScanReg /Restore and choosing the most recent backup is an appropriate way to fix the problem.
Restart Windows 98. While the system is restarting, press and hold the left CTRL key until you see the Windows 98 Startup menu.
In the Windows 98 Startup menu, select Command Prompt Only.
From the MS-DOS command prompt, type ScanReg /Restore.
A screen appears listing the available backup sets. Select the appropriate backup and determine if the symptom is alleviated on the subsequent start.
Checking Specific Driver Problems
Loading a specific driver in Config.sys, Autoexec.bat, or from the Windows 98 registry may cause a computer to stop responding. This could be due to a hardware or software (device driver or TSR) conflict.
Automatic Skip Driver (ASD) tracks device load failures by identifying the specific device(s) that failed to enumerate and stopped the system from starting. If Windows 98 stops responding when enumerating the same device on subsequent startups, ASD will automatically disable the device.
To check a device driver using Automatic Skip Driver
If a device driver fails to load, launch Automatic Skip Driver Agent from the Tools menu in System Information.
In the Hardware Troubleshooting Agent dialog box, click the operation that failed, and then click Details.
The Enumerating a Device Details dialog box appears and provides a recommendation for solving the problem. This includes updating the driver. It is possible that you will need to upgrade the driver disabled by Automatic Skip Driver.
To manually determine whether hardware or software is stalling the computer, try the following, stopping when the determination has been made.
To manually check a device driver
Press and hold down the left CTRL key when starting Windows 98, and select Safe Mode Command Prompt Only from the Startup menu. If this option prevents the computer from stalling on startup, a device driver or terminate-and-stay-resident (TSR) program is a likely cause of the problem.
Restart the computer, pressing and holding down the left CTRL again, and then select the Step-By-Step Confirmation option to check for TSRs that are loading and may be causing the problem.
If you use disk compression and the computer still stalls after using Safe Mode Command Prompt Only to start the computer, restart the computer in Safe Mode Without Compression by pressing CTRL+F5 when the Starting Windows 98 message appears.
Check the CMOS settings in the computer's BIOS configuration menus, making sure the settings match your installed hardware.
Check the hardware installation and the manufacturer's documentation to verify that all devices are correctly installed.
Check resource settings in Device Manager for specific installed hardware to make sure no conflicts exist in the IRQ, I/O address, DMA channels, and memory addresses used. Compare your actual installation with your hardware documentation for inconsistencies in the settings used. For information, see Chapter 24, "Device Management."
To check whether a specific driver is stalling the computer
Restart the computer.
Press and hold down the left CTRL key when the Starting Windows 98 message appears, and then select Logged (Bootlog.txt).
Search Bootlog.txt for errors.
Checking Whether a Required File Is Missing
Some computers contain devices that require a specific driver in Config.sys to correctly complete the startup process, such as drivers used for partitioning, compression, video, and hard disks.
To check for missing files
Press and hold down the CTRL key when starting Windows 98, and select Step-By-Step Confirmation from the Startup menu.
Respond Yes to all prompts. For any error messages that appear, make note of the driver involved, its location, and the specific wording of the error message. Verify that the specified driver exists in the specified location.
Do not remove any hard disk drivers, disk partitioning drivers, or disk compression drivers when starting Windows 98 using the Step-By-Step Confirmation option or while editing startup files. The following is a partial list of drivers that should not be removed.
Hard disk drivers: |
|
|
|
ah1544.sys |
ilm386.sys |
scsiha.sys |
sstbio.sys |
|
|
|
Partitioning drivers: |
|
|
|
dmdrvr.bin |
evdr.sys |
ldrive.sys |
sstor.sys |
|
|
|
Compression drivers: |
|
|
|
dblspace.bin |
drvspace.bin |
sswap.com |
|
To find out about other system drivers, see the documentation for the hardware or software installed on the system.
Checking Device Configuration
Errors are sometimes caused by conflicts between devices trying to use the same system resources. There are two ways to view your device configuration:
Microsoft System Information
Device Manager
Microsoft System Information (MSInfo) collects system information, such as devices installed or device drivers loaded, and provides a menu for displaying the associated system topics.
To launch Microsoft System Information
- Click Start, point to Programs, Accessories, and System Tools, and then click System Information.
Device Manager provides a central place where you can verify that devices are configured correctly.
To check for resource conflicts among devices
Click Start, point to Programs, Accessories, and System Tools, and then click System Information.
Expand the Components category and select Problem Devices. Devices with hardware conflicts will be identified.
To determine the resource in conflict, expand the Hardware Resources category and select Conflicts/Sharing. Keep in mind that PCI devices can share resources — if neither of the devices are listed under Problem Devices, they are probably sharing the resource.
If necessary, change the devices' resource settings using Device Manager.
To open Device Manager, click System in the Control Panel, and then click the Device Manager tab. For more information about Device Manager, see Chapter 24, "Device Management."
Note If you use multiple hardware profiles, you should first select the appropriate configuration using the list in the device's Resource properties.
Checking Upgrade Issues
The following sections describe how to check upgrade issues.
MS MS-DOS Utilities
The MS-DOS utilities that are installed into the \Windows\Command directory have been enhanced to work with Windows 98. The disk repair utilities that shipped with older versions of MS-DOS and Windows 95 should not be used with Windows 98. Most of the other MS-DOS utilities that worked with Windows 3.1 should continue to work with Windows 98, but if they were bound to an older version of MS-DOS, you may need to use the SETVER command to enable them.
The following MS-DOS utility files will be deleted after you upgrade from an earlier version of Windows:
Defrag.hlp
Mwundel.exe
Mwundel.hlp
Networks.txt
OS2.txt
The following MS-DOS utility files will be upgraded after you upgrade from an earlier version of Windows:
Ansi.sys |
Doskey.com |
Keyboard.sys |
Scandisk.exe |
Attrib.exe |
Drvspace.exe |
Label.exe |
Scandisk.ini |
Chkdsk.exe |
Edit.com |
Mem.exe |
Setver.exe |
Choice.com |
Ega.cpi |
Mode.com |
Share.exe |
Country.sys |
Emm386.exe |
More.com |
Smartdrv.exe |
Debug.exe |
Fc.exe |
Move.exe |
Sort.exe |
Defrag.exe |
Fdisk.exe |
Mscdex.exe |
Subst.exe |
Deltree.exe |
Find.exe |
Nlsfunc.exe |
Sys.com |
Diskcopy.com |
Format.com |
Ramdrive.sys |
Xcopy.exe |
Display.sys |
Keyb.com |
Readme.txt |
|
Disk Utilities
The disk utilities included with Windows 98 have been modified and fully support FAT32. DriveSpace 3 is included with Windows 98. It has been modified to detect FAT32 drives, but it will not compress them. In order to support FAT32, SHARE support has been disabled in the real-mode MS-DOS kernel (sharing support is still provided under protected-mode Windows 98).
Reinstalling Programs
If you upgrade your existing Windows 3.x or Windows 95 directory to Windows 98, then you do not need to reinstall your programs. If you install to a new directory, then you must reinstall all of your Windows-based programs. Copying files from your Windows 3.1 directory to Windows 98 is not supported.
MS-DOS-based Programs
Your existing MS-DOS-based programs should run from Windows 98. If you experience problems with an MS-DOS-based program, you can set it up to run in MS-DOS mode, the single application environment.
To run an MS-DOS-based program in an MS-DOS environment (MS-DOS mode)
Create a shortcut to the MS-DOS-based program.
Right-click the shortcut icon, and then select Properties.
Click the Program tab, and then click Advanced.
Make sure that the MS-DOS Mode box is checked.
When you run a program in MS-DOS mode, it forces Windows 98 to shut down and loads the program in an MS-DOS environment. You will not have access to devices that require protected-mode (Windows) drivers.
If you find an MS-DOS-based program slowing down or stopping when it is in the background, use the following procedure.
To speed up MS-DOS-based programs
Right-click the MS-DOS Prompt icon on the taskbar, and then click Properties.
Click the Misc tab.
Drag the Idle Sensitivity slider toward Low.
In the Background area, make sure that the Suspend Always box is not checked.
Note Applications that run in MS-DOS mode may require additional conventional memory, also referred to as the Transient Program Area (TPA). Optimize the TPA by loading MS-DOS support for devices in the upper memory area (UMA). Refer to the following examples provided with Windows 98:
MS-DOS Mode for Games
MS-DOS Mode for Games with EMS and XMS Support
Anti-Virus Software
Existing anti-virus software should be able to detect, but not always clean, viruses while running on Windows 98. This depends on where the virus was found and how the program chose to clean it. Also, virus shields may not be able to see all file activity, and therefore could miss some virus activity. It is recommended that you update your anti-virus software to a version that was designed to run with Windows 98.
Disk Repair and Optimization Utilities
Most legacy disk repair and optimization programs use direct disk reads and writes (INT25/INT26) for disk access. Because of this, Windows will block these disk repair and optimization programs from executing, in order to protect the data on your disk. This is necessary in a multitasking environment to prevent disk corruption caused by multiple utilities running simultaneously. It is strongly recommended that you upgrade to disk repair software that was designed for Windows 98. For more information, contact your software vendor.
Note If you bypass the disk-locking features of Windows 98 using the Lock <drive letter>: command at a real-mode prompt, and run one of these utilities on a FAT16 drive, you will destroy all long file names. This may not happen on a FAT32 drive as most of these utilities will see the physical FAT32 drives as "device-driven" and will not function.
Windows Shell Enhancements
Most Windows 3.1 and all Windows 95 shell replacements will run on Windows 98, but with many limitations because of the taskbar, 32-bit components, and the new Windows 98 shell. If you want to continue running one of these programs, you should upgrade to a version that was designed to run with Windows 98.