Jump to content

IBM PC XT/370 Troubleshooting Guide

From RetroTechCollection

This guide documents fault diagnosis for the IBM PC XT/370. POST is the standard IBM PC XT (5160) POST in the 1xxโ€“19xx range; XT/370-specific failures present as VM/PC boot errors or as cards-not-detected by the XT host BIOS.

Reference Documents

[edit | edit source]
  • IBM SA38-0037-00 โ€” Personal Computer Family Service Information Manual (July 1989), Chapter 6 (XT/370). Authoritative service manual.[1]
  • IBM 6137739 โ€” Virtual Machine/Personal Computer User's Guide (December 1984).
  • IBM PC XT documents โ€” POST codes, BIOS, hardware troubleshooting carry over directly.

Initial Diagnosis

[edit | edit source]

Power-on sequence on a working XT/370:

  1. IBM PC XT POST runs to completion (no error message; single short beep).
  2. PC DOS 2.10 boots from the C: drive.
  3. AUTOEXEC.BAT calls the VM/PC loader.
  4. VM/PC initialises the 370PC-P card via the ISA bus.
  5. VM/PC contacts the IBM 3174 or 3274 mainframe controller via the PC3277-EM card.
  6. VM/PC downloads CMS system files from the host mainframe to local minidisks (first run only).
  7. CMS prompt appears.

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

Stage 1 โ€” XT Host POST Fails

[edit | edit source]

Standard IBM PC XT POST codes apply. The 1xxโ€“19xx code series identifies the failed FRU at the chassis level. Cross-reference with IBM PC XT (5160) Troubleshooting Guide.

Common POST codes:

Selected XT POST codes that apply to the XT/370
Code Meaning First action
1xx Planar / system board Reseat / replace planar
2xx Memory error Identify failing 64 KB block from on-screen address
301 / 302 Keyboard fault Verify keyboard connected; check for stuck keys
6xx Floppy drive fault Cable, drive, controller
17xx Hard disk fault Cable, drive, fixed-disk adapter

Stage 2 โ€” XT POSTs OK but VM/PC Won't Load

[edit | edit source]
  • DOS boots normally โ€” XT chassis is healthy, problem is in the 370PC subsystem.
  • VM/PC initialisation message appears but hangs โ€” 370PC-P card not responding. Reseat the 370PC-P card. Reseat the 370PC-P to 370PC-M backplane connector.
  • VM/PC reports "memory error" or "card not present" โ€” 370PC-M card not detected. Reseat M card; clean backplane connector with deoxidising contact cleaner.
  • VM/PC reports "host connection failed" โ€” PC3277-EM card or the cable to the 3174 / 3274 controller. Check the BNC coax cable, terminator, and controller-side configuration.

Stage 3 โ€” VM/PC Loads but CMS Crashes

[edit | edit source]
  • S/370 Program Check โ€” usually means a guest CMS program has executed an opcode the modified 68000 does not implement. The instruction trap then fails because the unmodified 68000's interpreter does not recognise the opcode either. Resolution: update CMS / VM/PC to a known-good level; or restrict the guest program to instructions documented as supported by the XT/370 emulator.
  • Spurious memory errors โ€” 370PC-M DRAM failure. Run the VM/PC built-in memory test to identify the failing chip.
  • Disk I/O errors โ€” XT 10 MB ST-412 drive failure (more likely than a card fault).

370PC Card Diagnostic Workflow

[edit | edit source]

Because the XT host BIOS does not know about the 370PC cards, the cards do not produce POST codes โ€” they are detected only when VM/PC loads. Diagnostic workflow:

  1. Verify the XT chassis POSTs cleanly with the cards installed.
  2. Verify DOS boots from C:.
  3. Run a small DOS program from C: to confirm RAM is intact (e.g. CHKDSK).
  4. Load VM/PC and observe the initialisation messages.
  5. If VM/PC reports a 370PC-P or 370PC-M error, power off and reseat the cards and the backplane connector.
  6. If the error persists, swap with a known-good card set.

There is no in-system diagnostic for the modified 68000s or the modified 8087. If a card fails, the verdict is replacement โ€” and replacement cards are unobtainium.

3270 Host Connection

[edit | edit source]

The PC3277-EM card (or the standard 3278/79 Emulation Adapter on late-production units) connects to the IBM 3174 or 3274 cluster controller via BNC twinax. Common faults:

  • No carrier on the host link โ€” BNC cable, terminator, or 3174/3274 port.
  • Host connection times out โ€” controller-side configuration. The XT/370's host LU (Logical Unit) must be defined on the controller as a 3278 or 3279 emulator.
  • VM/PC sees the host but cannot download CMS โ€” VM CP (Control Program) configuration on the host mainframe; the user ID must have appropriate permissions and minidisk allocations.

VM/PC Operating System Faults

[edit | edit source]
  • VM/PC boots but CMS commands not recognised โ€” minidisks not formatted. Format using the VM/PC FORMAT command (formats a DOS file as a CMS minidisk).
  • CMS files do not export properly to DOS โ€” character set conversion issue. Use the EXPORT command with explicit EBCDIC-to-ASCII translation.
  • CMS application crashes with "no such opcode" โ€” guest software executed an instruction outside the XT/370 emulator's supported subset. Replace with a different version of the application or a CMS-included tool.

Common Field Symptoms

[edit | edit source]
  • XT POSTs, DOS boots, VM/PC won't load โ€” 370PC card subsystem. Reseat in order of likelihood: backplane connector โ†’ 370PC-P โ†’ 370PC-M โ†’ PC3277-EM.
  • VM/PC loads, CMS prompt appears, but every command hangs โ€” 370PC-P custom 68000 microcode issue, or 370PC-M memory failure.
  • VM/PC loads, host connection fails โ€” coax cable, terminator, controller-side configuration.
  • Random reboots during VM/PC operation โ€” PSU at capacity. Recap PSU; see IBM PC XT/370 Capacitor Replacement Guide.
  • Smell of fish from PSU โ€” RIFA X2 mains-suppression cap is venting. Power off immediately and replace.

Diagnostic Workflow Summary

[edit | edit source]
  1. Power on; observe POST. If POST fails, treat as standard XT chassis fault.
  2. If POST passes, observe DOS boot. If DOS fails, suspect XT hard drive or floppy.
  3. If DOS boots, load VM/PC. If VM/PC fails, reseat the 370PC cards.
  4. If VM/PC loads, attempt host connection. If host connect fails, check the BNC cable and the 3174/3274 controller.
  5. If host connect succeeds, attempt a CMS command. If CMS commands hang, suspect 370PC-P custom 68000 failure.
[edit | edit source]

References

[edit | edit source]