VOGONS


First post, by Susanin79

User metadata
Rank Member
Rank
Member

LOGI PC88XT motherboard — resurrection log

As promised in the “Bought these (retro) hardware today” thread, here’s a dedicated log for bringing a LOGI PC88XT motherboard back to life.
This is the second board from a lot that was sold as non-working / for parts. It carries marks from a previous (apparently unsuccessful) repair. I’ll post diagnosis and repair progress here.

Board description

  • Model: LOGI PC88XT
  • Chipset: IBM PC/XT-compatible
  • CPU: not installed
  • FPU: not installed
  • ISA slots: 8 × 8-bit
  • RAM: up to 640 KB, DIP-16
  • BIOS: not installed

Initial inspection

  • Damaged traces/pads near the PSU connector
  • Evidence of previous repair work
  • Bent pins
  • C16: missing tantalum capacitor on the +5 V rail

What’s been done so far

  • Removed old capacitors
  • Cleaned the affected area
  • Checked all pads and nearby traces for continuity and lift
  • Repaired broken signal/data traces and reinforced any suspicious runs (0.2 mm copper jumpers are used only on signals)
  • Traced the primary PSU rails to confirm correct continuity of +5 V, ±12 V, −5 V, GND, and Power-Good

Conclusion

The board has clearly seen better days and shows signs of an unsuccessful past repair, but I’m going to try to bring it back. I started with the obvious: severed traces are restored, questionable ones reinforced, and I’ll reuse the alternative capacitor pads that are in better shape. Next step is to install replacement capacitors, source a CPU, and choose a suitable BIOS (I’ll probably begin with a diagnostic ROM) for the first power-up.
I’ll keep this thread updated.

Reply 1 of 7, by Susanin79

User metadata
Rank Member
Rank
Member

Found a broken XT Auva motherboard. Will use it as a donor for CPU, memory, BIOS.
Need to solder new power capacitors and motherboard would be ready for the next repair step.

Reply 2 of 7, by devius

User metadata
Rank Oldbie
Rank
Oldbie

Good luck!

It's very nice that some of the component values are on the silkscreen.

Reply 3 of 7, by Susanin79

User metadata
Rank Member
Rank
Member

All tantalum capacitors on power lines were bad and have been replaced with a new one.
The CPU, BIOS, and DRAM ICs were temporarily borrowed from an Auva XT clone I bought recently.

The system now boots, though there are still issues with RAM, the keyboard, and the floppy subsystem—still a solid step forward.

Landmark diagnostic BIOS clearly indicate a problems

Reply 4 of 7, by twiz11

User metadata
Rank Member
Rank
Member
Susanin79 wrote on 2025-12-08, 21:43:
All tantalum capacitors on power lines were bad and have been replaced with a new one. The CPU, BIOS, and DRAM ICs were temporar […]
Show full quote

All tantalum capacitors on power lines were bad and have been replaced with a new one.
The CPU, BIOS, and DRAM ICs were temporarily borrowed from an Auva XT clone I bought recently.

The system now boots, though there are still issues with RAM, the keyboard, and the floppy subsystem—still a solid step forward.

Landmark diagnostic BIOS clearly indicate a problems

have you switched with known good keyboards?

Reply 5 of 7, by Susanin79

User metadata
Rank Member
Rank
Member

Yes, keyboard, floppy controller and floppy drive with cable were checked on IBM 5160. They are works fine, no issues detected.
Checking all traces continuity now. Due to the initial condition, there might be issues with the traces I suppose

Reply 6 of 7, by twiz11

User metadata
Rank Member
Rank
Member
Susanin79 wrote on 2025-12-08, 22:06:

Yes, keyboard, floppy controller and floppy drive with cable were checked on IBM 5160. They are works fine, no issues detected.
Checking all traces continuity now. Due to the initial condition, there might be issues with the traces I suppose

Check continuity through vias, not just along traces.

Reply 7 of 7, by Susanin79

User metadata
Rank Member
Rank
Member

Glad to inform, that issue with the memory was solved using a XTRAMTEST BIOS, with this diagnostic BIOS the faulty IC was identify and replaced. Big thanks to Adrian and Dave.
As for Keyboard, then it was simple - Keyboard fixed via keylock jumper. I am totally forgot about it and when the trace was done the idea to set a jumper here came into my mind.

Not everything clear with the FDC, it just start working when the keylock jumper was installed. Then stopped working when I tried to enable a turbo mode. The board didn't work stable in turbo mode by the way. My 4164s modules are 200 ns and can not be run at this speed. The FDC returned back to life since couple of hours of my attempts to fix it and just start working again while I checking the signals using an oscilloscope.

So, the next steps would be:
- try to find faster memory chips to test turbo mode
- run Rudi diagnostic to confirm slow refresh results from Landmark
- do the stress test to confirm that the board is work stable