Jump to content

IBM PCjr Troubleshooting Guide

From RetroTechCollection

This guide covers diagnostic procedures for the IBM PCjr (4860). The PCjr has a smaller and less rigorous POST than the 5150/5160/5170, and some of the most common PCjr complaints are software/timing issues rather than hardware failures.

Power-On Audio Beep Codes

[edit | edit source]

The PCjr BIOS uses the same beep coding scheme as the 5150 family. Beeps are produced by the PC speaker, mixed in with the SN76496 audio.

IBM PCjr power-on audio codes
Pattern Meaning
(no beep) No power, no system clock, bank-0 RAM failure, dead CPU or dead motherboard
1 short POST OK
2 short Numeric error on screen
1 long, 1 short Motherboard failure
1 long, 2 short Display adapter failure (video circuitry)
Continuous PSU or motherboard fault — check external brick voltage and motherboard tantalums

Numeric POST Codes

[edit | edit source]

The PCjr ROM POST is shorter than the AT's; the BIOS reports a small set of codes on the screen if the failure occurs after the video has initialised.

Code Meaning
101 System board error
102 ROM checksum error — BIOS, BASIC, or one of the installed cartridges
110 Motherboard parity error (note: PCjr does not implement DRAM parity check; this code is reserved on the PCjr)
201 Memory test failure — the bytes preceding the "201" identify the failing segment / bit
301 Keyboard error (also seen when the IR receiver does not receive a valid wake-up burst within the keyboard test window)
401 Display adapter test failure (built-in video)
501 Display alternate test failure (RGB / composite output)
601 Diskette / drive test failure (4860-067 only)
1301 Internal modem test failure (when the IBM PCjr Internal Modem sidecar is present)

Common Symptoms

[edit | edit source]

System will not power up

[edit | edit source]
  • Verify the wall outlet, the AC mains lead, and the external power brick output. The PCjr's brick supplies regulated DC at the system unit's DIN connector; check the pinout in the IBM PCjr Technical Reference.
  • Verify there is no short on the brick output. A failed tantalum on the motherboard's +5 V line will pull the brick to fold-back protection and the system will not power up.
  • Remove all sidecars and cartridges. Re-test. A faulty sidecar (especially a memory or modem sidecar with a failed tantalum) is a common cause of "PCjr will not start."

Keyboard not responding

[edit | edit source]
  • Replace the 4×AA cells in the keyboard. Low cells reduce IR range.
  • Move the keyboard within 10 ft / 3 m of the system unit IR receiver and direct it towards the system unit.
  • Reduce ambient IR interference: close blinds against sunlight, turn off plasma TVs and CCFL fluorescent fittings near the system.
  • If the keyboard still fails, fit the optional keyboard cord between the keyboard and the system unit. If the cord works, the fault is in the IR transmitter or receiver. If the cord also fails, the fault is in the keyboard scan matrix or the system unit's keyboard controller.
  • The PCjr Technical Reference documents a self-test mode that lights one LED for each pressed key — useful for confirming key matrix faults.

Keystrokes lost during disk access

[edit | edit source]

This is a known PCjr limitation, not a fault. The PCjr has no DMA controller, so floppy reads/writes consume all CPU time. The IR keyboard interrupt cannot be serviced during disk access and the keystroke is dropped. The Tandy 1000 has the same limitation in its earliest revision. Workarounds: avoid typing during disk access; use a directly-cabled keyboard with hardware that buffers keystrokes; install a third-party PCjr DMA-style accelerator (some sidecars added a DMA controller).

Cartridge does not work

[edit | edit source]
  • Power off, remove and reinsert the cartridge.
  • Clean the cartridge edge connector and the slot fingers with a soft eraser or contact cleaner.
  • Verify the cartridge is one of the two PCjr cartridge formats (32 KB or 64 KB ROM with proper /CS routing).
  • Some third-party cartridges (especially homebrew SD-card cartridges) require very precise chip-select timing; if the cartridge does not work on one slot, try the other.
  • If the system boots normally to BASIC without any cartridge but hangs at POST with the cartridge fitted, the cartridge ROM may have a corrupt header (the PCjr BIOS scans cartridges at well-known offsets during POST).

Sidecar fault

[edit | edit source]
  • Unlatch all sidecars and boot. If the system POSTs, re-add sidecars one at a time.
  • Verify each sidecar's edge connector is clean and seats fully.
  • A modem sidecar or a memory sidecar with a failed tantalum on its internal regulator will pull the system rails down. Replace the cap (see IBM PCjr Capacitor Replacement Guide).
  • If multiple sidecars are fitted and the PCjr now resets randomly, current draw may exceed what the standard external brick can supply. Fit the IBM PCjr Power Expansion Attachment.

Video noise / wavy display

[edit | edit source]
  • Verify the composite or RGB cable is fully seated and not running parallel to mains cables.
  • Verify the external power brick is supplying clean DC; ripple from aged electrolytics in the brick produces noise on the video output.
  • The PCjr TV Connector (RF modulator) is inherently noisier than the direct RGB output to the IBM 4863 display; use RGB if available.

"PCjr cliff" software incompatibility

[edit | edit source]

Some PC-compatible software written before late 1984 fails to run on the PCjr because of differences in the memory map (video RAM placement) and the absence of DMA. This is a software compatibility issue, not a hardware fault. A common symptom is the program loading and then immediately exiting to DOS, or hanging at a blue/black screen. Use software that explicitly supports the PCjr or use a sidecar that remaps video memory (Racore PC Drive, Tecmar Captain Jr.).

No-Beep / No-Video Diagnostics

[edit | edit source]
  1. Verify the external AC brick is producing DC at the system unit connector.
  2. Verify the system unit's +5 V rail comes up (probe on the motherboard).
  3. Pull all sidecars and cartridges. Re-test.
  4. If still dead, swap the keyboard (or fit the cord) to rule out the keyboard receiver.
  5. If still dead, reseat the BIOS ROM and the CPU.
  6. Inspect motherboard tantalum capacitors for shorts (see IBM PCjr Capacitor Replacement Guide).
  7. Bank-0 RAM failure on the PCjr motherboard produces a 'dead' system. The PCjr Technical Reference identifies the bank-0 chips by silkscreen.

Cassette Port

[edit | edit source]

The PCjr cassette port is functional and supported by Cassette BASIC in ROM. Most surviving units have never had it used. If you wish to use it, see the PCjr Technical Reference for the pinout and PCjr BASIC's CSAVE / CLOAD commands.

Battery / RTC

[edit | edit source]

The PCjr has no battery-backed CMOS and no RTC. There is no battery to replace and no SETUP to run. If the date and time are wrong on every boot, that is normal — set them manually from DOS (DATE and TIME commands) or via a sidecar that adds an RTC.

Internal Modem (4860-067)

[edit | edit source]

If the optional IBM PCjr Internal Modem sidecar is fitted and the system reports a 1301 error:

  • Check that the sidecar latches fully.
  • Verify telephone-line connectivity (RJ-11 phone jack to wall and to the modem).
  • Some modems require a specific country code jumper; verify against the modem documentation.
[edit | edit source]

References

[edit | edit source]