IML errors include problems with Initial Machine
Load (IML) or Initial Program Load (IPL). Most of these
errors can be corrected without replacing any FRUs. IML
errors are associated
with:
An I999XXXX error is displayed.
Computer powers-on without POST
error, but operating
system does not work.
The system starts up in BASIC.
IML and IPL errors can be caused by any of the
following conditions:
Invalid selectable drive startup
sequence (default
drive not in startup sequence)
Operating system not found
IML code not found
Related hardware failure (SCSI
adapter, hard disk,
SCSI cable)
Unrelated hardware failure
(misleading error due
to problem on SCSI Bus).
Checking Startup Sequence and
Hard Disk Drive
- Start computer from RefDisk, Main Menu > Set
Features.
- Select Set Startup Sequence, is default HD (usually
ID6) in startup sequence?
If not, follow
instructions
on the screen, then return to Step 2.
- Default drive IS in startup sequence, exit from
screen and
Main Menu. Go to step 5.
Default drive NOT in startup
sequence, follow instructions on the screen, then
continue with step 4.
- Remove RefDisk, power-off computer, then power-on
computer.
"F1" (Insert Diskette) icon appears, no
operating system found. Go to step 5.
"Not OK" icon appears,
system cannot access System Partition. Try updating
system programs.
- Install OS on device in startup
sequence -OR- change startup sequence to include device
with an OS
Power-on computer, check for normal
power-up sequence and run advanced diagnostic tests.
If problem
still exists, suspect SCSI controller, then hard disk
drive.
Notes:
Password Jumper:
It may be necessary to move the power-on
password jumper
(J22-Bermuda, JMP1=Lacuna/85, J10-90, J16-95) to enable
an IML to the reference diskette in
drive A. Moving this jumper forces stage 1 POST routine
to branch to
the diskette, rather than attempt to load stage 2 from
the Fixed disk system
partition. (A reference diskette must be present in the
a: drive)
The Stage 2 POST code on
reference diskette
is identical to the code loaded onto system partition.
Moving this
jumper sets all default values, except ASCII terminal
mode. Moving the Power-On password jumper is effective
for
only 1 Power-On cycle because stage 1 POST tracks
(records) the position
of the jumper each time it is run.
ASCII Terminal Mode:
If ASCII terminal mode is set (96-8N1,
Visible in information panel), the battery voltage must
be removed from the planar to reset it.
(Slide stiff paper under the battery clip for approx 10
to 15 minutes).
ASCII terminal mode will be automatically
set by stage
1 POST if there is no primary video adapter detected
(XGA adapter is missing
from the system).
Note: Complex based
"Complex", CPU on planar "planar", both "System"
I999xxxx Error Codes
| Symptom / Error |
Cause / -Action to take |
I999 001X
I999 002X
I999 003X
I999 004X
(see individual codes below) |
Only valid when running system from hard disk:
- Restore System Partition |
| I999 001X |
Invalid hard disk IML record.
A valid master IML record was not found on the hard disk. |
| I999 0015 |
90/95 - Followed by 96-8N1 means that the system could find no output display.
- Check that cable is connected. |
| I999 002X |
Hard Disk IML Record Load Error |
| I999 003X |
Incompatible Disk IML Record/Planar.
The IML boot record loaded from the hard disk did not have a planar ID matching the system. |
| I999 004X |
Disk IML record incompatible with processor board. |
| I999 005X |
Disk IML not attempted. |
I999 0053
I999 0054
I999 0056
I999 0057
I999 0059 |
Only valid when running system from Ref Disk:
- Restart computer from Refdisk
- If same error appears, try new Refdisk |
| I999 006X |
Disk stage 2 image load read error.
- Power Off the computer
- Toggle Password Override Jumper
- Start with Reference Disk
- Restore System Partition
|
I999 0063
I999 0067
I999 0069 |
Only valid when running system from Ref Disk:
- Restart computer from Refdisk
- If same error appears, try new Refdisk |
I999 007X
|
Disk stage 2 checksum (read) error.
The actions for these errors are only valid when running the system from the hard disk:
- Restore the System Partition
|
I999 009X
|
System Board BIOS newer than Disk IML Partition.
The actions for these errors are only valid when running the system from the hard disk:
- Restore the System Partition
|
I999 00X1
I999 00X2
I999 00X3
I999 00X4
I999 00X6
I999 00X7
I999 00X9
(see individual codes below) |
Only valid when running system from Ref Disk:
- Restart computer from Refdisk
- If same error appears, try new Refdisk |
| I999 00X1 |
Invalid Diskette IML Record.
A valid master IML record was not found on the diskette. |
| I999 00X2 |
Diskette IML Record Load Error. |
| I999 00X3 |
Incompatible Diskette IML Record/Planar.
The IML boot record loaded from diskette did not have a planar ID matching the system. |
| I999 00X4 |
Incompatible Diskette IML Record/Processor Card.
The IML boot record loaded from diskette did not have model/submodel byte value matching the system. |
| I999 00X5 Power On Password jumper (POP):
Bermuda: J22
Lacuna/85: JMP1
Model 90: J10
Model 95: J16 |
Diskette IML Not Attempted.
Diskette IML was not attempted because of a fatal disk IML error or active system security.
Reference Diskette recovery prevented
- Power Off computer
- Toggle Password Override Jumper
- Power On computer |
| I999 00X6 |
Diskette POST/BIOS/BASIC Image Load Error.
The system image could not be loaded from the diskette. |
| I999 00X7 |
Diskette stage 2 IML checksum error. |
| I999 00X9 |
System Board BIOS newer than Diskette BIOS. |
|
| I999 0301 |
No bootable device found, HD or floppy
This may be a hardware failure Check:
- Cabling
- Termination
- Adapter / Controller
- Hard drive |
| I999 0302 |
Invalid disk boot record (missing OS)
- Install an operating system
- check for a valid startup sequence
- are all devices in startup-sequence present?
|
| I999 0303 |
System Partition boot failure
- Restore System Partition |
| I999 0304 |
No bootable device found with ASCII-console
Probably no operation system installed
- Install operation system
- Does startup sequence contain default drive? |
| I999 0305 |
No startable device found
Probably no operation system installed
- Install operation system
- Does startup sequence contain default drive? |
| I999 0306 |
Invalid CD-ROM or R/W optical drive error.
- Restart computer from startable Floppy or HD. |
| I999 0401 (Fatal) |
Unauthorized Access
Clear POP before replacing parts!
- Replace Planar or Complex
(Whichever contains the ROM) |
I999 0402 (Fatal)
I999 0403 (Fatal)
(see individual codes below) |
- Replace Planar or complex
(Whichever contains the ROM) |
| I999 0402 |
Missing IBM copyright notice, alternate processor error |
| I999 0403 |
Incompatible Disk IML Record.
The IBM ROM IML routine would have detected incompatible incompatible IML record.
The ROM may not be an IBM ROM so the system access error is generated. |
| I999 06XX |
IBM Overlay errors. |
I999 0600 (Fatal)
I999 0607 (Fatal)
I999 0609 (Fatal) |
Recovery prevented
- Power Off the computer
- Toggle Password Override Jumper
- Insert Reference Disk
- Power On the computer
- Restore the System Partition
|
| I999 80XX |
ThinkPad system partition
- Reseat HD. Check Startup Sequence
- Hard Disk Drive
- System Board |
X can be any number
Usually Fatal I999xxx Errors
The following errors normally require processor FRU replacement:
I9990401 - Unauthorized access.
I9990402 - Missing ROM IBM Copyright notice
I9990403 - Non IBM IML routine
I9990600 - IML Overlay Logistics Error
I9990607 - IML Overlay Checksum Error
I9990609 - IML Overlay ID Error
I999 0022 - Disk IML record load (read) error
> I have upgraded an 8595 with a Type 3, Evergreen 150Mhz Proc.Comp..
I've formatted a 1 Gg HDD and created a new IML Partition. I can see it
just fine in system setup on CHIPID=6. However, when I boot I get
I999 0022 - Disk IML record load (read) error If I boot a DOS diskette,
I have no C-drive?
From Tim Clarke:
If it's an actual read error on the IML boot record and
it couldn't recover (it tries 20 different 5-sector records for a Type-3)
then the area at the "end" of the drive's capacity is suspect. Backup operational
partitions and do an LLFormat from Advanced Diagnostics without clearing
the "grown defect list". Then Restore System Partition and then verify
IML is O.K. before reloading operational partitions.