Osborne Executive Troubleshooting Guide

This guide details practical, board-level troubleshooting for the Osborne Executive portable computer. It covers common power, display, storage, memory, and logic faults, with diagnostic steps tailored to the Executive’s unique hardware. Use this guide to systematically restore a non-booting, unstable, or malfunctioning Osborne Executive to working order.

🔌 Preliminary & Power-up Checks

Begin by confirming the Executive’s power supply and startup sequence, as many faults stem from PSU or connector issues.

1. Unplug the unit and visually inspect for burnt components, leaking capacitors, or corrosion—especially near the power input and CRT area.
2. Test the mains fuse and the internal 5A fuse on the PSU board.
3. With a multimeter, check voltages at the mainboard edge connector:
   • +5V DC (logic supply)
   • +12V DC (floppy and CRT)
   • -5V DC (RAM bias)
4. If voltages are missing or out of range, recap the PSU and check for failed rectifiers or voltage regulators (notably the 7812, 7805, and 7905).
5. Remove all floppy drives and expansion cards; attempt to power up with mainboard only.
6. Inspect the reset circuit (NE555 timer and associated components) for failed capacitors or stuck reset.

Symptom	Likely Cause	Action
No power, no fan	Blown fuse, failed switch, dead PSU	Replace fuse, test switch, recap/repair PSU
Fan runs, no CRT glow	CRT supply failure, loose CRT connector	Check 12V rail, reseat CRT connectors, test flyback transformer
Powers up, but no beeps or display	Mainboard not receiving correct voltages	Confirm all rails at edge connector, check for shorts

🖥️ Display & Chime Diagnostics

The Osborne Executive’s built-in CRT and beeper provide key startup clues.

No Video, No Beep

• Indicates CPU not running or stuck in reset.
• Check for activity on the Z80 CPU clock pin (should be ~4 MHz square wave).
• Inspect for a stuck reset line (should pulse low then high at power-on).
• Reseat all socketed ICs, especially the Z80, ROM, and video controller (6845).

Raster/Glow, but No Characters

• CRT and video supply are functional, but logic is not generating video.
• Suspect failed 6845 CRTC, video RAM (2114), or character ROM.
• Confirm 6845 receives clock and sync signals.
• Swap 6845 and video RAM if available.

Beep Codes

• The Executive emits a single beep on successful POST; repeated beeps or silence indicate RAM or ROM failure.

Symptom	Likely Cause	Action
CRT glow, no text	Video RAM, 6845 CRTC, or character ROM	Swap/test 2114 RAM, 6845, and ROM chips
No beep at all	CPU, ROM, or major logic fault	Check Z80, ROM, and system clocks; piggy-back or swap chips
Continuous/repeating beeps	RAM failure	Test/replace 4116/4164 DRAMs, check -5V bias

💾 Memory & ROM Faults

The Executive uses dynamic RAM (4116/4164) and mask ROMs for firmware.

RAM Faults

• Black screen, repeated beeps, or random characters on boot are classic RAM failure signs.
• 4116/4164 DRAMs require +5V, +12V, and -5V; loss of -5V will prevent boot.
• Piggy-back a known-good DRAM atop each suspect chip to isolate faults.
• Replace failed DRAMs in sockets; if soldered, desolder and socket for future service.

ROM Faults

• Corrupt or missing ROM will prevent boot or cause garbled display.
• Reseat ROM chips; clean pins and sockets.
• If available, swap with a known-good ROM or use an EPROM adapter.

Symptom	Likely Cause	Action
Repeating beep, no boot	Bad RAM	Test/replace DRAMs, confirm -5V present
Garbled or missing characters	Bad character ROM or video RAM	Swap ROM, test/replace 2114 RAM
No boot, random screen	System ROM failure	Swap ROM, check for address/data bus activity

🥏 Floppy Drive & Storage Subsystem Failures

The Executive’s dual Shugart-compatible floppy drives are a frequent source of problems.

Drive Not Detected / No Boot from Disk

1. Confirm drive power connectors supply +12V and +5V.
2. Listen for drive spin-up and head movement at boot.
3. Clean drive heads and check for stuck or dirty eject mechanisms.
4. Inspect and reseat the 34-pin ribbon cable and edge connectors.
5. Test the WD1793 (or equivalent) floppy controller IC for activity.

Disk Read/Write Errors

• Clean heads with isopropyl alcohol.
• Replace deteriorated drive belts or lubricate rails.
• If errors persist, suspect the floppy controller or TTL glue logic (74LS series).

Symptom	Likely Cause	Action
No drive activity	Power loss, cable fault, dead controller	Check voltages, reseat cables, swap WD1793
Drive spins, no boot	Dirty heads, bad disks, controller fault	Clean heads, try known-good disk, test controller IC
Read/write errors	Head alignment, failing TTL logic	Align heads, test/replace 74LS ICs near controller

💀 Error & Code Table

Beep Pattern	Meaning	Typical Cause
Single beep	POST passed	Normal operation
Continuous beeps	RAM error	Bad DRAM, missing -5V
No beep	CPU/ROM/major logic fault	Dead Z80, ROM, or system clock

⚠️ Connector & Socket Issues

Aged sockets and connectors are a chronic problem in Osborne machines.

1. Reseat all socketed ICs, especially Z80, ROM, 6845, and floppy controller.
2. Clean edge connectors and sockets with contact cleaner.
3. Inspect for cracked solder joints on the mainboard, especially at the PSU and CRT connectors.
4. Replace any visibly corroded or loose sockets.

🔩 Component-level Tests & Voltage Table

Use the following test points to confirm system health:

Test Point	Expected Voltage	Notes
Mainboard +5V rail	+5.0 V DC (±5%)	Logic supply for all ICs
Mainboard +12V rail	+12.0 V DC (±10%)	Drives, CRT, some logic
Mainboard -5V rail	-5.0 V DC (±10%)	DRAM bias (4116/4164)
Z80 pin 6 (Clock)	~4 MHz square wave	Essential for CPU operation
Z80 pin 26 (Reset)	Low → High at power-on	Should pulse low then high
6845 CRTC pin 21 (HSYNC)	15.7 kHz pulse	Confirms video timing

If any voltage is missing, recap the PSU and check associated regulators and diodes.

🔊 Audio & I/O Failures

The Executive’s beeper and serial/parallel ports are prone to age-related faults.

• No beep: Test beeper with a multimeter or swap with a known-good piezo element.
• Serial/parallel port failure: Inspect for broken traces, failed 1488/1489 line drivers, or cold solder joints.
• Keyboard not responding: Reseat keyboard connector, clean contacts, and test for stuck keys.

📎 Related Pages

• Osborne 1 Troubleshooting Guide
• Floppy Disk Repair