|
Windows 98 Errors and Fixes |
A new Windows 98 bug has been reported by Microsoft Coproration. The bug can occur after you run the System File Checker tool and then try to reboot your computer. Upon reboot your system may be unable to start Windows 98 properly.
When you use the System File Checker (Sfc.exe) tool to restore a Windows 98 system file (for example, the User.exe, Gdi.exe, or Krnl386.exe file) from a Windows 98 cabinet (.cab) file, the wrong version of the file may be extracted from the Mini.cab cabinet file. This can result in the inability to start Windows 98 (for example, your computer may stop responding) or "Windows Protection Error" error messages in normal and Safe mode. This symptom can occur when the System File Checker tool prompts you to restore a corrupt system file during a scan or when you extract and replace a system file using the System File Checker tool.
This behavior occurs because the System File Checker tool baseline file (Default.sfc) contains incorrect information about the source cabinet file locations for some Windows 98 system files. As a result, the System File Checker tool searches for the system file in the specified folder (if it is not in a cabinet file) and then in all cabinet files in the specified folder. The System File Checker tool searches cabinet files using their MS-DOS folder order and extracts the first instance found. If the Mini.cab cabinet file appears in an MS-DOS folder listing before the correct Windows 98 cabinet file (for example, the correct cabinet file for the User.exe file is the Win98_42.cab cabinet file.), the System File Checker tool may find the mini-Windows mode version of the system file in the Mini.cab cabinet file first. The Mini.cab cabinet file contains mini-Windows mode files used only by Windows 98 Setup and DriveSpace.
To work around this behavior, restart your computer using the Windows
98 Startup disk, choose Start Computer With CD-ROM Support from the Windows
98 Startup menu, and then re-extract the file at a command prompt using
the Extract.exe tool. If you need help with using the Extract.exe Tool
please read about this in the Microsoft's
How
to Extract Original Compressed Windows Files
knowledgebase.
Here are some of the more common Dial-Up Networking Errors:
When you try to start Dial-Up Networking, you receive the following error message:
Error 630: The computer is not receiving a response from the modem. Check that the modem is plugged in, and if necessary, turn the modem off, and then turn it back on.
This error message can occur if the modem is using a newly detected serial port installed by Windows 98 hardware detection. If this is the case, change the properties of the Dial-Up Networking connection to use the new modem settings.
Programs run at StartUp from the StartUp folder can also cause this error message.
To temporarily disable programs in the StartUp folder, follow these steps:
1.Click Start > Run and in the Open: box, type msconfig, then press OK
2.In Msconfig click the Startup tab. For programs that may control your modem, click the program's check box to clear it. If you are not sure whether or not a specific program should be disabled, click to clear all of the check boxes except for the following check boxes:
ScanRegistry
TaskMonitor
SystemTray
LoadPowerProfile (is loaded twice normally)
If you receive this error on Windows 98 Second Edition, and you have an 3Com (USR) USB modem, you have 2 options and 1 workaround, until 3Com releases new drivers:
Option 1: Revert back to Windows 98 (Gold) (uninstall Windows 98 Second Edition)
Option 2: Install the modem as a serial device Work-around:
1.Select Start > Settings > Control Panel
2.Double-click Modems, and then verify that your modem is listed on the General tab
3.Click Diagnostics, select the COM port to which your modem is attached, and then click More Info
Your modem should now be accessible to other Windows applications for the remainder of your Windows session.
Note: This will need to be done each time windows has been restarted.
Check the 3Com Web site for further information.
http://consumer.3com.com/voice/index.html
When you try to start Dial-Up Networking, you receive the following error message:
Error 633: The modem is not installed or configured for Dial-Up Networking. To check your modem configuration, double click the Modems icon in Control Panel.
This error message can occur if the Telephon.ini file is missing or damaged. To resolve this issue, please see the following Microsoft Knowledge Base Articles:
Q120221 (How to Rebuild the TELEPHON.INI File)
http://support.microsoft.com/support/kb/articles/Q120/2/21.asp
When you try to connect, you receive the following error message:
Modem not responding (Error 650). For troubleshooting information, click Help.
One workaround suggests enabling a post terminal window. Here's how:
1.Select Start > Programs > Accessories > Communications > Dial-Up Networking
2.Right-click your connection, and choose Properties
3.On the General tab, click the Configure button
4.Select the Options tab
5.Place a check-mark in bring up terminal window after dialing
Just press continue when the post terminal window pops up after you connect.
(650) The computer you have dialed does not respond to a network request
You can get this occasionally when your ISP is busy, and they don't have a free I.P. address to assign to you.
If you are still having problems:
Although it says that it applies to The Microsoft Network version 2.52,
try the solution from Microsofts Knowledge Base Article Q192420.
http://support.microsoft.com/support/kb/articles/q192/4/20.asp
When you try to start Dial-Up Networking, you receive the following error message:
Error 745: An essential file is missing.
Re-install Dial-Up Networking.
This error message can occur when a Dial-Up Networking dynamic-link library (DLL) file is missing or damaged. To resolve this issue, please see Microsoft Knowledge Base Article Q174579. http://support.microsoft.com/support/kb/articles/Q174/5/79.asp
More information on troubleshooting modem problems in Windows 98 can
be found in Microsoft Knowledge Base Article Q190554.
http://support.microsoft.com/support/kb/articles/Q190/5/54.asp
For Microsoft Windows 95/98
When you try to start a program in Windows, you may receive one of the following error messages:
Error starting program. The Comctl32.dll file cannot start. Check the file to determine the problem.
Error starting program. The Comdlg32.dll file cannot start. Check the file to determine the problem.
Error starting program. The Shell32.dll file cannot start. Check the file to determine the problem.
Error starting program. The Lz32.dll file cannot start. Check the file to determine the problem.
Error starting program. The Version.dll file cannot start. Check the file to determine the problem.
Error starting program. The Winmm.dll file cannot start. Check the file to determine the problem.
Some programs replace Windows files with their own files. The Windows Commctrl.dll, Commdlg.dll, Shell.dll, Lzexpand.dll, Ver.dll, or Mmsystem.dll files may have been replaced by files from another program.
What to do:
Extract the corresponding file in place of the one listed in the error
message you received. In the instructions that follow, replace <name>
with the name of the appropriate file. This file will be one of the following
files:
Commctrl.dll for Comctl32.dll
Commdlg.dll for Comdlg32.dll
Shell.dll for shell32.dll
Lzexpand.dll for Lz32.dll
Ver.dll for Version.dll
Mmsystem.dll for Winmm.dll
NOTE: If you are using Windows 98, and Windows 98 starts, use the System File Checker tool to replace the damaged file with a new copy of the original file. For information about how to use System File Checker, click Start, click Help, click the Index tab, type "system file checker" (without quotation marks), click Display, and then double-click Using System File Checker.
Otherwise, restart your computer to a command prompt, and then copy the <name> file from the Windows\Sysbckup folder to the Windows\System folder. This replaces the existing file with the Windows version of the file.
NOTE: The program that replaced the <name> file with another version of the file may have set some of the <name> file's attributes. If you are having trouble copying the file from the Windows\Sysbckup folder to the Windows\System folder, use Windows Explorer to check the <name> file's properties. If the file's Read-Only, Hidden, or System properties are selected, click those check boxes to clear them.
If the <name> file in the Windows\Sysbckup folder is damaged or is not the correct version of the file, extract a new version of the file from your original Windows disks or CD-ROM to the Windows\System folder. To extract a new copy of the <name> file, you need to perform one of the following steps, depending on the file:
Extract the Kommctrl.dll file from the Precopy1.cab file to the Windows\System folder, and then rename the Kommctrl.dll file to Commctrl.dll.
Extract the Commdlg.new file from the Win95_11.cab file to the Windows\System folder, and then rename the Commdlg.new file to Commdlg.dll.
Extract the Shell.new file from the Win95_11.cab file to the Windows\System folder, and then rename the Shell.new file to Shell.dll.
Extract the Lzexpand.dll file from the Precopy1.cab file to the Windows\System folder.
Extract the Ver.new file from the Win95_17.cab file to the Windows\System folder, and then rename the Ver.new file to Ver.dll.
Extract the Mmsystem.dll file from the Win95_13.cab file to the Windows\System folder.
NOTE: The specific cabinet file numbers may vary from version to version.
Use the /A switch to search the entire cabinet set of the appropriate type
(Precopy or Win95).
From http://support.microsoft.com/support/kb/articles/Q220/8/78.ASP
The information in this article applies to: Microsoft Windows 98
When you attempt to manually restore a previous copy of your computer registry using the scanreg command with the /restore switch (scanreg /restore), you may receive the following error message:
To resolve this issue, manually restore the registry files:
NOTE: The following procedure may also be useful if you want to restore a registry that does not appear in the Scanreg tool. This occurs because you can use the Scanreg.ini file to save more that five backups, but Scanreg only displays the five oldest registries. You can also use this method to install a backup registry that does not appear in Scanreg.
Restart your computer, press and hold CTRL until the Windows 98 Startup Menu appears, and then choose Safe Mode Command Prompt Only.
At the command prompt, type path=c:\windows\command, and then press ENTER.
At the command prompt, type the following commands, pressing ENTER after each command:
cd windows\sysbckup
md temp
dir rb*.cab
In the list of .cab files that start with "rb" (such as Rb000.cab), note the name and date of the newest file, the second newest file, and the third newest file.
At the command prompt, type the following commands, pressing ENTER after each command:
copy rb .cab file name c:\windows\sysbckup\temp
cd temp
extract /e rb .cab file name *.*
attrib -r -s -h *.dat
cd \windows
attrib -r -s -h user.dat
attrib -r -s -h system.dat
ren system.dat *.xxx
ren user.dat *.xxx
ren system.ini *.yyy
ren win.ini *.xxx
copy c:\windows\sysbckup\temp\*.*
where rb .cab file name is the name of the newest .cab file you noted in step 4.
Restart your computer.
Test to determine if the issue is resolved, and if it is not, repeat this process, but in step 5, change to the second newest file instead of the newest file. If this does not resolve the issue, repeat this process, but in step 5, change to the third newest file.
MORE INFORMATION
Note that when the scanreg command with the /restore switch does not
work correctly, the .cab file you are attempting to restore is damaged.
If this procedure does not work correctly the first time, Microsoft recommends
backing up all remaining .cab files before attempting it again
*With the machine switched off at the wall but with the power cable left in to keep it grounded.
*Remove and clean the CPU Heatsink and the CPU fan.
*Also remove and re-insert the RAM boards securely making sure not to touch the edge connectors and make sure the locking tabs are secure and that the boards are correctly seated (Some boards have to be tilted to get them to click and then made upright.
*Also check that the system is well ventilated and has good airflow
around it. If you are working in a hot climate then you may also have to
use Thermal grease between the CPU and the heatsink and also remove any
stickers from the top of the CPU as some of these are made a thin rubberized
plastic which stops the heat dissipation.