Hardware Reference
In-Depth Information
follow the described earlier in order to check that the computer is correctly
configured and that the system hardware and associated drivers is operating
correctly.
3
If you receive the error message when you attempt to start the computer in
Safe mode, you follow the steps listed below to restore the registry:
(a)
Boot to a command prompt.
(b)
Remove the file attributes from the backup of the registry by typing the
following DOS command:
c:\windows\command\attrib -h -s -r c:\system.1st
(c)
Remove
the
file
attributes
from
the
current
registry
by
typing
the
following DOS command:
c:\windows\command\attrib -h -s -r c:\windows\system.dat
(d)
Rename the registry by typing the following command:
ren c:\windows\system.dat *.dax
(e)
Copy the backup file to the current registry by typing the following
command:
copy c:\system.1st c:\windows\system.dat
4
Restart the computer and verify that the computer's current CMOS settings
are correct.
5
Install a 'clean' copy of Windows in an empty folder. If the new installation
resolves the problem this usually indicates that either one or more of your
Windows core files has been damaged, or that there is an error in the config-
uration of your original installation. You can choose to use the new installation
of Windows, but you will have to reinstall any application programs so that
they are correctly recognized by Windows.
6
If the problem is not resolved with a 'clean' installation, the condition is
probably attributable to faulty hardware. In such a case you may need to con-
tact the motherboard manufacturer as well as the manufacturer of any adapter
cards that are fitted to the system. If you have access to a similar system that
is fault-free, you should, of course, be able to carry out substitution tests.
The virtual device driver (VxD) that is generating the error message can be
any VxD, either a default VxD that is installed, or a third-party .386 driver that
is loaded from the System.ini file. If you do not know which driver is causing
the error message, create a Bootlog.txt file, and then check to see which driver
is the last driver that is initialized. This is typically the driver that is causing the
problem.
Kernel errors
The Kernel32.dll file is a 32-bit dynamic link library (DLL) file that handles
memory management, input/output operations, and interrupts. When you start
Windows, Kernel32.dll is loaded into a protected memory space. An invalid
page fault (IPF) error message will occur when a program tries to access the
protected memory space allocated to Kernel32.dll. Occasionally, the error mes-
sage is caused by one particular program whilst on other occasions it may be
generated by several programs.
