IBM 5100 Troubleshooting Guide

This guide documents fault diagnosis for the IBM 5100 Portable Computer. The 5100 predates the IBM PC POST numeric error code system by six years and does not use POST beep codes; instead it relies on a Diagnostic ROS accessible via a keyboard sequence at power-on, a front-panel "Display Registers / RAM Hex" switch for live RAM inspection, and the per-symptom troubleshooting decision tree in IBM Maintenance Analysis Procedures (MAP) document 1608314.

Reference Documents

• SY31-0405-3 — IBM 5100 Maintenance Information Manual (MIM), October 1979. Theory of operation, diagnostic procedures, PALM microcode appendix.
• 1608314 — IBM 5100 Maintenance Analysis Procedures (MAP), March 1976. Per-symptom decision tree.
• SY31-0429-2 — IBM 5100 Communications / Serial I/O MIM, October 1976.

Initial Diagnosis Workflow

The 5100 power-on sequence is:

1. Power LED on rear illuminates.
2. Fan spins (if fitted) and PSU rails stabilise.
3. Executable ROS self-test runs (silent — no beep code on 5100).
4. Language interpreter loads from Language ROS.
5. Language banner appears on the 5-inch CRT (e.g. "BASIC READY" or "APL READY") — this is the "POST passed" indication.

If any of these does not occur, stop and diagnose at that stage.

Stage 1 — No Power

• Mains lead seated and switch on rear is ON.
• Mains fuse intact on the 5100 PSU board.
• Voltage selector (where present) set correctly for your mains.
• PSU rails present? Probe at the planar power connector.

Stage 2 — Power But No Display

• CRT raster only, no characters — Executable ROS not running, or video timing chain failed.
• No raster at all — flyback / deflection failure on the CRT board; cathode emission failure.
• Garbled characters — RAM (RWS) failure or Executable ROS bit error.

Use the front-panel "Display Registers / RAM Hex" switch — this displays the first 512 bytes of RAM live in hex. If the display is stable and shows valid hex, the basic video chain is working and the issue is downstream (Language ROS or PALM).

Stage 3 — Banner Wrong / Language Banner Garbled

• Garbled "BASIC READY" or "APL READY" indicates Language ROS bit failure or socket oxidation.
• Reseat Language ROS modules.
• Try the other language (toggle the front-panel APL / BASIC switch) — if one language banner appears clean and the other is garbled, the failed Language ROS module is isolated.

Stage 4 — Banner Appears But System Won't Accept Input

• Keyboard fault — reseat keyboard cable.
• Keyboard foam pad degradation — reform or replace pads.
• PALM input handling failure — see PALM diagnosis.

Diagnostic ROS

A keyboard sequence at power-on enters Diagnostic ROS — the operator can read and write RAM, video memory, PALM registers, interrupt vectors and the clock counter in hex, effectively assembly-language access without an operating system.

The Diagnostic ROS is documented in MIM SY31-0405. Once in Diagnostic ROS, the operator can:

• Read PALM registers and verify the processor is alive.
• Read / write RAM cells to check the RWS subsystem.
• Read Language ROS to verify the interpreter is intact.
• Trace PALM microcode execution to isolate a failing instruction class.

Front-Panel Switches as Diagnostic Aids

• Display Registers / RAM Hex — live hex view of first 512 bytes of RAM. Useful for verifying RAM and video timing chain.
• Reverse Display — toggles internal CRT inversion. Useful to test the video logic.
• APL / BASIC — toggles language. Useful to isolate Language ROS bit failures.
• Display 64 / Left 32 / Right 32 — column-view mode. Useful to isolate column drivers.

PALM Diagnosis

The PALM board carries 13 bipolar gate arrays. PALM failures are rare in practice but terminal when they occur — there are no replacement gate arrays available outside donor 5100s.

Symptoms of PALM failure:

• System will not exit Executable ROS self-test.
• Diagnostic ROS will not load.
• Random check-stop with a specific code displayed.

Diagnosis:

1. Reseat the PALM board edge connector — oxidised pins are the most common cause of "dead PALM" symptoms that are not actually PALM failures.
2. Reseat ROS / RWS cards.
3. Verify PSU rails to the PALM board.
4. If all of the above are confirmed good and the system still does not run, a PALM gate array has failed.

Tape Drive Faults

Common DC300 tape drive symptoms:

• No tape activity at all — drive belt perished or capstan motor failure.
• Tape spins but read errors — head dirty; alignment drift; oxide shedding from the cartridge tape itself.
• Write succeeds but read of same data fails — head alignment.
• Catastrophic tape jam — eject and inspect the cartridge; if the tape has spilled, replace the cartridge.

CRT Faults

• No raster — flyback failure; check for HV at anode (using HV probe only). No HV → flyback or horizontal output transistor failed.
• Raster but no characters — video timing chain (vertical scan generation from PALM).
• Dim raster — cathode emission loss; CRT is end-of-life.
• Single horizontal line — vertical deflection failure.
• Single vertical line — horizontal deflection failure (rare; usually accompanied by flyback failure).
• Bright single spot — both deflections failed; immediately power off to avoid burning the phosphor.

ROS / RWS Memory Faults

• Garbled banner — Language ROS bit error.
• Refusal to complete Executable ROS self-test — Executable ROS bit error or PALM fault.
• RAM size mismatch — RWS card failure; reseat each 16 KB module.

The MIM documents how to use Diagnostic ROS to read every ROS address and verify against a checksum.

Tape-Based Customer Acceptance Test

The Customer Acceptance Test is documented in MIM SY31-0405. It uses a customer test tape cartridge that exercises:

• RAM (full pattern test).
• Tape drive (read / write / verify).
• Communications Adapter (if fitted).
• Serial I/O Adapter (if fitted).
• CRT (cursor positioning and character set verification).

This test cartridge is rare but the procedure can be reproduced by writing the appropriate test program in BASIC or APL.

Common Field Symptoms and Resolutions

• Won't power on — Mains lead, switch, fuse, PSU primary.
• Power LED but no fan / no display — PSU bulk filter caps shot. Recap; see IBM 5100 Capacitor Replacement Guide.
• Display works briefly then fades — PSU regulator capacitor failure causing rail droop.
• Banner appears, system hangs on keystroke — keyboard or PALM input handling.
• Garbled banner — Language ROS bit error; reseat ROS modules first.
• Tape drive will not read or write — belt, head, alignment in that order.
• Random reboots / hangs — bulk filter cap ESR rising; recap PSU.
• Smell of fish from PSU — RIFA X2 mains-suppression capacitor venting (if fitted); replace immediately.
• Smell of burnt resistor from PALM board — gate array failure; PALM board is now terminal.

Diagnostic Workflow Summary

1. Power on; observe LED, fan, display chain.
2. If no power, suspect PSU.
3. If power but no display, suspect Executable ROS, PALM, or CRT chain.
4. If display but garbled, use front-panel hex display to verify RAM.
5. If RAM hex stable, check Language ROS by toggling APL / BASIC.
6. Enter Diagnostic ROS (keyboard sequence at power-on) and run the documented self-tests.
7. If self-tests pass, run the Customer Acceptance Test cartridge.
8. Cross-reference any check-stop code against MAP document 1608314.

Related Pages

• IBM 5100
• IBM 5100 Maintenance Guide
• IBM 5100 Capacitor Replacement Guide

References

• Bitsavers — IBM 5100 documents.
• IBM 5100 — Wikipedia. Diagnostic ROS reference.
• IBM PALM processor — Wikipedia. PALM gate-array architecture.
• Dave Dunfield's IBM 5100 collection page. Community restoration notes.