surprise STF refurb
Posted: 22 Feb 2022 04:36
So a couple weeks ago I picked up the STF I mentioned in this thread. That PSU is long gone, and I've jury-rigged a Meanwell RD50A for power. I bought this as untested, and I'm poking it to determine if it'll be a salvage, or a donor. Waaay on the backburner, I have my H5 board that I'd like donor parts for, and I don't want to tear up a working machine.
Things are rarely so binary though, and this machine might be close to working.
At the moment, I occasionally get many bombs (20+) on boot, OR, the system boots to desktop but it doesn't read the floppy correctly. It reads some filenames but with garbage appended, and says 0 bytes are used on the disk. The disk itself is good, and the floppy drive is good: I can drop both into another machine and they're healthy. So I've eliminated those as the likely problem.
So I guess maybe the floppy controller is at issue? It looks like somebody's played with it before -- I don't imagine these were originally socketed -- but that might just mean they tried to replace and the problem persisted.
But from there... I'm not really sure how to debug this issue. This is a TOS 1.0 machine (which I'm enjoying, because I've never had one before), but one of the TOS chips has been replaced.
That suggests there was a (suspected) ROM issue in the past, too?
So, I'm curious what folks reckon. Is it a bad ROM which I'd fix by dropping in 1.4 anyway, or a bad WD1772, or a bad joint on the socket, or something else? I haven't touched any mandatory fixes on this yet, fwiw, so those are all up for grabs too.
Things are rarely so binary though, and this machine might be close to working.
At the moment, I occasionally get many bombs (20+) on boot, OR, the system boots to desktop but it doesn't read the floppy correctly. It reads some filenames but with garbage appended, and says 0 bytes are used on the disk. The disk itself is good, and the floppy drive is good: I can drop both into another machine and they're healthy. So I've eliminated those as the likely problem.
So I guess maybe the floppy controller is at issue? It looks like somebody's played with it before -- I don't imagine these were originally socketed -- but that might just mean they tried to replace and the problem persisted.
But from there... I'm not really sure how to debug this issue. This is a TOS 1.0 machine (which I'm enjoying, because I've never had one before), but one of the TOS chips has been replaced.
That suggests there was a (suspected) ROM issue in the past, too?
So, I'm curious what folks reckon. Is it a bad ROM which I'd fix by dropping in 1.4 anyway, or a bad WD1772, or a bad joint on the socket, or something else? I haven't touched any mandatory fixes on this yet, fwiw, so those are all up for grabs too.