|
Error Messages and Fixes #4 |
This fix is only for:
The Microsoft Network versions 1.2, 1.3, 2.0, 2.5
Microsoft Windows 95
When you attempt to connect to MSN, The Microsoft Network, using the Internet And MSN service type, you may receive one of the following error messages:
Explorer caused an invalid page fault in module Kernel32.dll
Commgr32 caused an invalid page fault in module Kernel32.dll
Mprexe caused an invalid page fault in module Kernel32.dll
Msgsrv32 caused an invalid page fault in module Kernel32.dll
A TCP/IP problem has occurred. Please check if you have TCP/IP installed and selected for your modem
Msnviewr caused an invalid page fault in module Kernel32.dll
Guide.exe caused an invalid page fault in Kernel32.dll
Guide.exe caused an invalid page fault in Mpr.dll
Connection could not be established Error 745
After you receive the error message, your computer may stop responding.
This can happen if your password list file is damaged.
The Fix:
To resolve this issue, re-create your password list file. To do so, use the following steps:
Click Start, point to Find, and then click Files Or Folders.
In the Named box, type *.pwl, and then click Find Now.
In the list of found files, right-click each file, and then click Delete. Continue until the list of found files is empty.
Close the Find window.
Restart the computer. The password list files are re-created automatically when you log on to Windows 95.
NOTE: If you use Microsoft Windows 95 and have installed Windows 95 Service Pack 1, password list files may remain damaged even after you delete them and they are re-created automatically.
To resolve this issue, download and install the Windows 95 Password
List Update. You can obtain this file from the following Microsoft Web
site:
http://www.microsoft.com/windows95/downloads/
Note that the error message stated above can occur when you connect to any site (not just MSN) with Dial-Up Networking if the .pwl file is damaged.
You may also receive this error message when you are using Microsoft
Exchange, Microsoft Schedule+, or Microsoft Outlook 97. The resolution
in this article also works for these programs.
Error
Message: IEXPLORE Caused an Invalid Page Fault...
http://support.microsoft.com/support/kb/articles/Q155/1/16.asp
Err
Msg: Iexplore Caused an Invalid Page Fault in Shell32.dll
http://support.microsoft.com/support/kb/articles/Q188/0/95.ASP
Err
Msg: IExplore Caused an Invalid Page Fault in Module...
http://support.microsoft.com/support/kb/articles/q218/9/83.asp
According to Microsoft, if the style sheet that specifies how web pages are displayed in Internet Explorer contains an invalid instruction or it is damaged, you may receive the following error when you start Internet Explorer 4.0 for Windows, Internet Explorer 5.0 for Windows 95, Internet Explorer 4.0 for Windows Nt 4.0 or Internet Explorer 5.0 for Windows NT 4.0 or you start Windows with the Active Desktop enabled: "Explorer caused an invalid page fault in module MSHTML.DLL at 0137:703e34c." If you are using Windows 95 with the Active Desktop enabled you may be able to fix this problem by following these steps:
1. Restart Windows 95;
2. Press the F8 key when you see the "Starting Windows 95" message;
3. Choose Safe Mode from the Startup menu;
4. Click Start, Settings, Control Panel;
5. Double-click Internet;
6. Click Accessibility on the General tab;
7. Clear the "Format documents using my style sheet" check box or enter
the path to a valid style sheet
8. Click OK;
9. Click OK again;
10. Restart Windows;
11. Click Restore My Active Desktop when the Active Desktop Recovery
screen appears
12. Click Yes.
If you are using Windows NT or Windows 95 with a browser only (not an Active Desktop. follow these steps:
1. Click Start, Settings, Control Panel;
2. Double-click Internet;
3. On the General tab, click Accessibility;
4. Clear the "Format documents using my style sheet" check box or type
the path of a valid style sheet;
5. Click OK;
6. Click OK again. If you are using Windows NT 4.0 with the Active
Desktop enabled, Microsoft suggests modifying the registry. BugNet advises
that you consult your computer manufacturer or technical support department
for assistance due to potential problems that may arise with editing your
registry. For more information visit
http://support.microsoft.com/support/kb/articles/q175/3/79.asp.
Error Message: Invalid Page Fault in Mshtml.dll
http://support.microsoft.com/support/kb/articles/q169/7/47.asp
Mshtml.dll Error When Closing Window Before Rendering Finishes
http://support.microsoft.com/support/kb/articles/Q193/8/47.ASP
Or ONLY ROM BASIC
Well, 1st, the best bet it to get some nerer components.
But you probable have data you want to save.....so:
The original IBM PC, half to have an operating system built in, half to satisfy contractual obligations with Microsoft, had a version of BASIC "burnt" into a ROM chip. If no boot disk was inserted in a floppy drive at system startup, BASIC would load from the ROM. To keep on the good side of Bill Gates's attorneys, Big Blue kept this ROM BASIC in the XT, AT, and even into the PS2 line.
The clone makers, to retain compatibility, kept similar error catching routine in their BIOSes. If no boot files are detected on the hard drive, the NO ROM BASIC error message is displayed in big blocky, really shocking, letters.
This is often good news, in a way. The system recognizes the hard drive, so it is not likely to be a drive crash, or other hardware catastrophe.
Generally, the cause is either that the system files have been erased or corrupted. The other common reason is that the hard drive has been defined improperly in the CMOS SETUP. Investigate the second possibility first. If you start reading and writing to a badly configured hard drive, you'll louse the data up, but GOOD! You need to determine the settings for your drive. See you Hard Drive Manufatures Manual or contact them.
Try booting from a floppy. If you use any drive compression utilities, then you need the proper rescue disk. If you can get to the C drive, and all your data is recognizable, test for viruses!
If the virus test is negative, try fdisk /mbr from the a: prompt.
you'll have to have the fdisk program (it's part of dos) on the boot floppy.
This re-writes the master boot record. if that does not help, the run fdisk.
if you've got any data on the hard drive that you hope to recover, at this
point, make no changes in the partition size!!!
Changing the size of a partition destroys all the data!!! deleting
any partitions will destroy all data in those partitions!!!
For now, go to partition information. look to see if the first (probably
the only) partition on your fixed disk is defined as a dos partition and
is set as active. If it's not active, then switch it to active in fdisk.
If it's not defined as a dos partition, try the following suggestions,
but your situation is starting to look grim.
If your hard drive still does not boot, run the SCANDISK from your floppy, assuming it's there to look for any scrambled sectors. If this does not show any house of horrors, you will need to use NORTON DISKTOOL or the DOS SYS command to shoehorn in the system files. You can run DISKTOOL from your hard drive. SYS must be run from the boot floppy. DISKTOOL will do the trick in some cases where SYS fails. On an older drive try NORTON's CALIBRAT to "tune-up" the drive. The last resort, in any case, is a low level format. For the MFM and RLL drives, you can use DISK MANAGER. For IDE units, a low level format program is built into most newer motherboards. SCSI adapters generally contain a low level formatting utility. After a low level format, except with DISK MANAGER, you will have to run FDISK and then FORMAT /s.
If the system still will not load, replace the drive, or set it as SLAVE
and install a new master hard drive to act as the boot drive.
When you start Windows, you may receive the following error message:
Cannot find a device file that may be needed to run Windows or a Windows application.
The Windows registry or SYSTEM.INI file refers to this device file, but the device file no longer exists.
If you deleted this file on purpose, try uninstalling the associated application using its uninstall program or setup program.
If you still want to use the application associated with this device file, try reinstalling that application to replace the missing file.
<filename>.vxd
NOTE: The specific file may not be named.
This error message can occur for either of the following reasons:
A Windows virtual device driver (VxD) referenced in the System.ini file or registry is missing or damaged.
One of the StaticVxD values in the registry contains invalid data. For example, the value is blank or contains only spaces. In this case, the missing device driver is not named in the error message.
To resolve this problem, follow each step below until the error no longer occurs:
1.If you have recently removed a program or component, reinstall the program or component, then run the uninstall tool if one is available. If no uninstall tool is available for the program or component, contact the manufacturer to obtain instructions on uninstalling.
2.If the missing device driver has a .386 extension, disable the line referring to this device driver in the System.ini file by placing a semicolon (;) at the beginning of the line. For example, if the line referencing the missing device driver reads
device=Example.386
change the line to read
;device=Example.386
3.If the missing device driver has a .vxd extension, it is a driver designed for use with Windows 95 or Windows 98 and is referenced in the registry. In most cases, a program or component with drivers designed for use with Windows 95 or Windows 98 will also be listed in the Add/Remove Programs tool in Control Panel. Following the instructions in step 1 should correct the problem.
For Windows 98
If the error message still occurs after following the instructions
in step 1 or it does not apply, use System File Checker to extract the
missing file from the Windows 98 CD-ROM as follows:
a.Click Start, point to Programs, point to Accessories, point to System Tools, and then click System Information.
b.On the Tools menu, click System File Checker.
c.Click "Extract one file from installation disk," type the name of the file you want to extract in the "Specify the system file you would like to restore" box, and then click Start.
d.In the Restore From box, type the path to the Win98 folder on the Windows 98 CD-ROM. Type the destination folder in the Save File In box if necessary, and then click OK.
e.Click OK, click OK, and then click Yes when you are prompted to restart your computer.
For Windows 95
Use the following syntax to extract a file from a known cabinet file:
extract <cabinet> <filename> /l <destination>
For example, to extract the Windows 95 Unidrv.dll file from the Win95_10.cab file on a disk in drive A to the Windows\System folder on drive C, use the following command: extract a:\win95_10.cab unidrv.dll /l c:\windows\system
4.If a specific device driver is not named in the error message, one of the StaticVxD values in the registry is probably blank or contains only spaces. The StaticVxD values are located in the registry keys below the following key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD
Use Registry Editor to locate and delete any StaticVxD value in the registry that contains invalid data, is blank, or contains only spaces.
When Windows starts, the System.ini file and the registry are read to obtain a list of device drivers to load. When Windows cannot locate a virtual device driver that it is attempting to load, an error message is generated.
Virtual device drivers are files required by various programs to communicate with your computer's hardware.
The following sample registry key contains a StaticVxD value:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\COMBUFF
The data for this StaticVxD value is "*COMBUFF" (without the quotation
marks; the quotation marks appear in Registry Editor but are not part of
the VxD name). The asterisk (*) preceding the VxD name indicates that the
VxD is internal to the Vmm32.vxd file. If the VxD referenced by the StaticVxD
value is not internal to the Vmm32.vxd file, its name is not preceded by
an asterisk and typically has a .vxd extension.
When you attempt to view a Web page using Internet Explorer, you may receive the following error message:
Cannot open Internet site https://<Web address>. A connection to the server could not be established.
Reason
You have mismatched Windows Sockets dynamic-link library (DLL) files.
For example, this behavior can occur if you install the Windows Sockets
(Winsock) 2.0 update for Windows 95 on a Windows 95-based computer, upgrade
to Windows 98, and then attempt to revert to your previous version of Winsock
by running the Ws2bakup.bat file.
Your Dial-Up Networking (DUN) or Internet settings are incorrect.
How To Fix This:
To resolve this behavior, remove and then reinstall the Transmission
Control Protocol/Internet Protocol (TCP/IP). To do so, follow these steps:
1.Click Start, point to Settings, click Control Panel, and then double- click Network.
2.On the Configuration tab, click TCP/IP, and then click Remove. Repeat this step for each instance of TCP/IP before continuing to step 3.
3.Click OK, and then click Yes when you are prompted to restart your computer.
4.Click Start, point to Settings, click Control Panel, and then double-click Network.
5.Click Protocol, click Add, click Microsoft in the Manufacturers box, click TCP/IP, and then click OK.
NOTE: If receive version conflict error messages during this process, click No when you are prompted to keep a newer version of the file.
6.Restart your computer.
7.If these steps do not resolve this behavior, repeat the steps, but remove and reinstall all installed network components.
8.If the problem still occurs, check with your Internet service provider
to verify your Internet settings.
Windows 95/98
When you start Windows, you may receive the following error message:
Windows encountered an error while backing up the system registry. Make sure you have enough space on the drive for three copies of the file c:\windows\user.dat. This error should not cause any loss of information, but if space is not made on the drive you may experience additional problems.
Reason:
This error can occur for either of the following reasons:
There is not enough free space on the hard disk containing Windows 95.
A damaged driver is being loaded from the Config.sys or Autoexec.bat file.
What to do:
To resolve this issue, use the appropriate method:
Free additional space on the hard disk containing Windows.
Identify which driver is causing the problem. To do so, follow these steps:
1.Restart the computer. For Windows 95, when you see the "Starting Windows 95" message, press the F8 key, and then choose Step-By-Step Confirmation from the Startup menu.
For Windows 98, restart the computer. As the computer starts, press and hold down the CTRL key until you see the Windows 98 Startup Menu, and then choose Step-By-Step Confirmation.
2.Press Y at each prompt except for the "Process your startup device drivers (Config.sys)" and "Process your startup command file (Autoexec.bat)" prompts.
If the error message no longer occurs, the problem is with a driver being loaded from the Config.sys or Autoexec.bat file. To determine if the problem driver is being loaded from the Config.sys file, repeat steps 1-2, but press Y at the "Process your startup device drivers (Config.sys)" prompt. If the problem returns, a driver being loaded in the Config.sys file is damaged. If the problem does not occur, repeat steps 1-2 again, but press Y at the "Process your startup command file (Autoexec.bat)" prompt. Once you identify the driver that is causing the problem, contact the driver's manufacturer for assistance, or reload the driver from the original disk.
Drivers:
The following drivers, when damaged, are known to cause the error message
stated above:
Cs.exe (loads in the Config.sys file)
Other drivers may also cause this error message.