cymrullewes' game box, mabolgamp, quit working a few weeks ago. She thought it was overheating. It was fairly apparent that wasn't the problem.
Actually, mabolgamp has an MSI motherboard, an MS6330 Rev-3, aka K7T Turbo. About the only thing I like that motherboard for is the diagnostic LED array on it, which enables monitoring the POST if you remove the case side. The POST wasn't even starting; the DLEDs were showing four reds, which has one documented meaning, CPU failure. (There's actually two; the other is "complete chipset failure on the motherboard". That one isn't documented, but I can vouch for it, because that's the way the second MS6330 died. The original one died of bad capacitors. Yes, this motherboard is the second replacement.)
Well, I could have sworn I had a spare AthlonXP 1700+ around someplace that I could use to test whether it was the CPU or the board. I couldn't find it when I went looking for it, though. All I was able to find was a Duron 650 (ironically, the Duron 650 that was on the original MSI board when I originally got whitestar from koyote). So I swapped in the Duron, and the machine booted right up. "Huh," I thought, "failed processor."
The dead processor was an Athlon (Thunderbird) 1200. A little research turned up that the board would actually support Athlon or Duron processors up to 1.5GHz. I hunted around some more for the spare AthlonXP 1700+ (which actually runs at 1463MHz), still couldn't find it; asked around to see if anyone I know had a spare, but no joy; eventually, figured out that the XP1700+ I thought we had spare had been in whitestar when UPS destroyed it, and recalled that I'd ended up discarding it as probably damaged.
So I went looking at AthlonXP CPU prices, and decided at length that the best strategy was to buy an uprated CPU for babylon5, then put babylon5's AthlonXP 1800+ into mabolgamp. I settled on an AtthlonXP 2400+ as being the best price point among CPUs that I could be certain would work on babylon5's Rev-1.1 Asus A7V333 motherboard. (The Rev-2.0 A7V333s support significantly faster CPUs, up to the fastest AthlonXP processors made, but the Rev-1.1 is more limited.) CPU arrived, flashed babylon5's BIOS to the latest version, installed the new CPU, and it came right up, no problem.
Then, on to mabolgamp. It too needed its BIOS updated, which I set out to do first. This led to several hours of tearing my hair out trying unsuccessfully to get the machine to boot from a FreeDOS 9 floppy, interspersed with efforts to try to get it to see the hard disk when booted from a FreeDOS 9 or FreeDOS 7 CD. (I want to know why it's apparently never occured to the FreeDOS developers that someone might want to be able to boot a PC from a FreeDOS CD and access the hard disk from it. You know, as a rescue disk, or; say, to flash new firmware that they'd previously downloaded.) I became all but certain at one point that the floppy drive wasn't working, so I swapped in a different one, and suddenly that didn't work either. I was really starting to wonder if the floppy controller on the motherboard was dead, by the time I found the problem.
Finally I realized what was wrong: "swap floppy drives" was set in the BIOS. The machine wouldn't boot from the 3.5" floppy because the 3.5" floppy wasn't device 0x00; the 5.25" floppy was. (Why does this machine have a 5.25" floppy in it? Old games on floppy discs. Yes, that old. Why did we have the drives swapped in the BIOS to make the 5.25" floppy drive 0x00 when it was physically connected as 0x01? Don't ask me. I haven't the faintest idea. I assume there must have been a reason.)
That problem solved, I could flash the BIOS. (With the latest BIOS, actually, the motherboard supports processors up to an AthlonXP 2200+.) Performing the physical CPU swap was simple... but I couldn't get the new CPU to come up at the right speed.
Further hair-tearing ensued until I realized that the board was, in fact, detecting the CPU speed correctly ... it's just that while the board supports both PC100 and PC133 RAM, it is populated with PC100, which means the BIOS has to limit the bus speed to 100MHz instead of the 133MHz the CPU really wants. This slowed the CPU down from its actual 1533MHz to 1150MHz at its 11.5x clock multiplier, and I couldn't simply increase the clock multiplier to make up for the slower bus because the CPU is locked to a maximum 11.5x multiplier.
"Oh, bugger."
Still, it's got a Palomino core at 1150MHz now instead of a Thunderbird core at 1200. It should be at least comparable.
no subject
The machine wouldn't boot from the 3.5" floppy because the 3.5" floppy wasn't device 0x00; the 5.25" floppy was.
HOLY SHIT!
That woke me up.
no subject
no subject
no subject
no subject
Coppy it off, run it in an emulator.
no subject
They don't.
no subject
These floppies are from old AppleIIes. At this moment in time, I'm not even certain I know where to put my hands on them. Knowing my luck they are back in an open shed in North Carolina.
no subject
Aside from a serial line from an apple ii, I don't know how you'd go to a modern box. I suspect there is some other way.
no subject
It was a whimsy of mine.
no subject
no subject
no subject
Sun hardware, I like. But Sun is dying by degrees, and current Suns are - IMHO - prohibitively expensive for home use. My biggest Sun, I can't run anyway: too much heat and too much power consumption.
no subject
And why can't you set OS X to launch things with a single-click? Linux, FreeBSD, and Windows all let you do that! And don't get me started on Apples proprietary interfaces, so you can't just plug in any old PCI or AGP card, but have to spend 4 or 5 times as much for Mac-specific versions.
I like my Mac a lot, but I haven't figured out what to do with it yet. Every use I can think of, I can do just fine on the PC that I already have running 24/7, except for Mac Bornes (http://www.timac.org/MacBornes/).
By the way, I've been seeing a car occasionally on 290 with the plate CYMRU5. I think it was a Toyota Highlander. I think it was also a Massachusetts plate, so it's probably not
no subject
no subject
no subject