Leadtek Research Inc.
48
DISPLAY TYPE HAS CHANGED SINCE LAST BOOT
Since last powering off the system, the display adapter has been changed. You must configure
the system for the new display type.
ERROR ENCOUNTERED INITIALIZING HARD DRIVE
Hard drive cannot be initialized. Be sure the adapter is installed correctly and all cables are
correctly and firmly attached. Also be sure the correct hard drive type is selected in Setup.
ERROR INITIALIZING HARD DISK CONTROLLER
Cannot initialize controller. Make sure the cord is correctly and firmly installed in the bus. Be
sure the correct hard drive type is selected in Setup. Also check to see if any jumper needs to be
set correctly on the hard drive.
FLOPPY DISK CNTRLR ERROR OR NO CNTRLR PRESENT
Cannot find or initialize the floppy drive controller. make sure the controller is installed
correctly and firmly. If there are no floppy drives installed, be sure the Diskette Drive selection
in Setup is set to NONE.
KEYBOARD ERROR OR NO KEYBOARD PRESENT
Cannot initialize the keyboard. Make sure the keyboard is attached correctly and no keys are
being pressed during the boot.
If you are purposely configuring the system without a keyboard, set the error halt condition in
Setup to HALT ON ALL, BUT KEYBOARD. This will cause the BIOS to ignore the missing
keyboard and continue the boot.
Memory Address Error at ...
Indicates a memory address error at a specific location. You can use this location along with the
memory map for your system to find and replace the bad memory chips.
Memory parity Error at ...
Indicates a memory parity error at a specific location. You can use this location along with the
memory map for your system to find and replace the bad memory chips.
MEMORY SIZE HAS CHANGED SINCE LAST BOOT
Memory has been added or removed since the last boot. In EISA mode use Configuration Utility
to reconfigure the memory configuration. In ISA mode enter Setup and enter the new memory
size in the memory fields.
Memory Verify Error at ...
Indicates an error verifying a value already written to memory. Use the location along with your
system's memory map to locate the bad chip.
OFFENDING ADDRESS NOT FOUND
This message is used in conjunction with the I/O CHANNEL CHECK and RAM PARITY
ERROR messages when the segment that has caused the problem cannot be isolated.