Tom Stepleton
banner
stepleton.bsky.social
Tom Stepleton
@stepleton.bsky.social
AI research engineer, glider pilot. Apple Lisa power user. @[email protected] on Mastodon. Most of my posts will be about old computers; occasionally I'll mention flying.
@breakintoprogram.co.uk so the problem with my Spectrum+ was the Z80, it turns out. The address bus was stone dead, +0V on all sixteen lines. Subbing in the CPU from my Jupiter Ace got it going; a replacement is now on order. Thanks for the chat on Sunday!
November 18, 2025 at 1:23 AM
Just in time for #PERQtober ! An adapter to replace your missing or broken #PERQ T2 landscape monitor with a VGA display: codeberg.org/stepleton/pe... Thanks to @[email protected] for early advice.
September 29, 2025 at 10:24 PM
The Olivetti Programma P203 (1967) uses a circuit construction technique known as "transistor jail"
(or "cordwood" [1]. Seen at [2].)

[1] en.wikipedia.org/wiki/Printed...
[2] www.thecomputerchurch.org
August 26, 2025 at 3:24 AM
Wheeling Airglow (en.wikipedia.org/wiki/Airglow... ) out to the runway at the British Human Powered Flying Club's 2025 Icarus Cup event, Lasham Airfield, Hampshire.
June 20, 2025 at 8:04 PM
Happy Pride #rc2014
June 4, 2025 at 12:04 AM
#Smalltalk -80 on #PERQ --- Mario Wolczko's implementation (www.wolczko.com/st80/) running with maybe some gremlins still to sort out.
May 20, 2025 at 12:12 AM
Here are some images from ICL's looping demo that runs on the #PERQ 2T2 under PNX 5.
April 22, 2025 at 11:58 PM
OK, so the #PERQ 2T2's disk system will work if:
* you let it warm up for a bit
* you have the logic analyser attached to U9 on the EIO board
* ...and running
April 22, 2025 at 11:58 PM
This is pretty funny to, like, maybe three people on Earth.
February 25, 2025 at 11:18 PM
I post what from This is .
January 28, 2025 at 10:55 PM
After learning the true meaning of "we're not doing presents this Christmas", it was off to the makerspace to hastily laser-engrave and laser-cut jigsaw puzzles for everyone.
December 27, 2024 at 3:35 AM
I would have mentioned the 4051 if you hadn't, of course! Running the 6800 at a mighty 800 kHz. They were working on this 4051 at the vintageTEK museum last year, and as nice as the 6800 was, check out these gorgeous 6820 PIAs...
December 22, 2024 at 9:04 PM
With U141 replaced, U159 starts pulsing. I fixed the mouse. I have a working PERQ at last! I can run manufaturer demos that are honestly pretty good for the 1980s! The honeymoon lasts a week, and then some chip in the hard drive system fails. That's what I've been fixing ever since. (fin)
December 21, 2024 at 3:11 PM
A brief check with the logic analyser and we had our smoking gun. You can see data going into one of the 74S225 and then one of the bits missing when it comes out. U141 is the culprit.
December 21, 2024 at 3:11 PM
We've learnt to be suspicious of 74S225 chips: it seems they don't age very well. It's been necessary to replace two of them in the PERQ already, since they made the display look like this. (That's a whole different story.) Good thing a PERQ 2 system uses about 30 of the things...
December 21, 2024 at 3:11 PM
Anyway, why is this happening. Well, what does the Z80 code encounter on its journey between the PERQ CPU and the I/O-handling Z80? The schematic shows that it filters through these 74S225 memory chips, which basically handle the traffic jam of a two-lane highway for data merging down into one lane.
December 21, 2024 at 3:11 PM
Maybe it only applies if you're lucky. I think my PERQ's Z80 was experiencing some truly Buster Keaton-level good luck. BTW @ctrlaltrees.bsky.social , this bug is why that keyboard glitch you saw was happening..
December 21, 2024 at 3:11 PM
It's especially important because the instruction the Z80 runs to send configuration to U159 is D3, the "OUT" instruction. 53 does something entirely different. Suddenly it's clear why U159 wasn't getting set up properly. The Z80 was running corrupted code!
December 21, 2024 at 3:11 PM
The scene: A and I at the bench. A reads eavesdropped bytes from the logic analyser. I follow along in the code. We start finding differences. What should be C3 becomes 43 in the PERQ. 96 is 16. D3 is 53. Something is turning some high-bit binary 1s into 0s! *dramatic music, fade to commercial*
December 21, 2024 at 3:11 PM
But then at the end of the show, there was a breakthrough. To understand, it helps to know that (a) in the PERQ, I/O is handled by a second processor, a Z80 (b) the main processor has to download code to it to use the mouse, and (c) we know what that code should be.
December 21, 2024 at 3:11 PM
I'm so grateful to @binarydinosaurs.co.uk for the chance to exhibit, but regret being so absorbed in the troubleshooting! I didn't socialise much and I feel a bit bad about it. Sorry to fellow exhibitors; I do really like seeing you all there and wish I had made more time to chat!
December 21, 2024 at 3:11 PM
BTW, this troubleshooting is happening in public at the wonderful Retro Computer Festival at the Centre for Computing History in Cambridge. Only have a broken computer? Exhibit yourself trying to fix it as a kind of live diorama, a bit like a blacksmith pounding on hot iron in a "living museum".
December 21, 2024 at 3:11 PM
So let's find that pulse-maker. I've probably got the #1 spot in 2024 for Time Spent Looking at PERQ Schematics, so it's not hard to trace the signal back to p8-15 of www.bitsavers.org/pdf/perq/per... and U159 in particular, an Intel 8254 programmable interval timer...
December 21, 2024 at 3:11 PM
The mouse isn't a normal mouse, it's more like a graphics tablet. Its dedicated "mouse pad" is a circuit board that detects the mouse's location. To work, the mouse needs to receive steady signal pulses from the computer, but it wasn't getting those. Our problem lies elsewhere...
December 21, 2024 at 3:11 PM
About a month ago I fixed the mouse on my circa-1983 #PERQ 2T2 computer: a key feature for an early graphical workstation. It was a wild troubleshooting journey --- in the end, there was nothing wrong with the mouse itself. You might not believe what it was...
December 21, 2024 at 3:11 PM