I used to like
"Keyboard error - press F1 to continue".
Or is this a fake memory, and the BIOS was never that stupid?
The baddest of AI bad guys, the Terminator, has confirmed what the vast majority of IT professionals already know. The machines are not about to rise, not until they can deal with that pesky battery voltage. Spotted by The Register's very own US editor in a New York arcade, an elderly Terminator Salvation arcade game is …
It wasn't that stupid really.
If set to halt on all errors, the press F1 was to indicate a keyboard was now attached and working.
My machines were normally defaulted to "halt on all errors except keyboard" from the makers (gigabyte 486/pentiums boards) and so would sail though regardless if you hadn't connected the keyboard.
This post has been deleted by its author
The Phoenix BIOS message on boot will be familiar to many, and the battery error suggests that whatever is keeping the BIOS settings alive is not long for this world.
But we know (as we see The T800's own view) that The Terminator runs on a 6502, and such BIOS's are not used by 6502 bases systems.
Read a bit of the text there - interesting.
If I recall correctly, doing sloping lines without multiply/divide is called a DDA (Digital something something). I recall descriptions and comparisons in an early graphics textbook.
But, did you know you can do *circles* without mul/div? And no lookup tables. I did one for my "Explore" system on a CP/M S-100 graphics card. It's probably possible to modify that to do ellipses, but I didn't need that, so didn't try.
Fun times. Now I need the old geezer icon again!
Can I paste and have it readable? Probably not....
Here is the Draco source for drawing a circle (Intel 8080 CPU) on a (Godbout?) Spectrum graphics card:
proc nonrec circle(ushort yc, xc, r)void:
int xd, yd;
word negY;
ushort x, y;
xd := make(r, word) << 1;
yd := 0;
x := r;
y := 0;
negY := 0;
while y <= x do
while xd + yd >= 0 do
point(xc + x, yc + y);
point(xc + y, yc + x);
point(xc + x, yc - y);
point(xc - y, yc + x);
point(xc - x, yc + y);
point(xc + y, yc - x);
point(xc - x, yc - y);
point(xc - y, yc - x);
y := y + 1;
negY := negY - 1;
yd := yd + negY << 1;
od;
x := x - 1;
xd := xd + x << 1;
od;
corp;
I was never really an arcade fiend as a kid in the 80s. But I do remember being blown away by OutRun and that arcade game graphics in general were almost always so much better than anything domestic hardware or consoles were capable of back then.
From what I've read, the reason they went into serious decline from the mid-90s onwards is partly because the domestic consoles that were coming out then were dramatically narrowing the gap between themselves and dedicated arcade machine hardware.
I mean, I know it's common nowadays, but seeing an arcade machine that's obviously little more than lightly-modified (at best) generic PC hardware in a fancy case- and probably no better than what many people have at home- isn't really inspiring, is it?
It does require losing another board while you connect another battery to it.
Talked to someone who ran a retro arcade, he said he had found a way to keep boards alive that required a battery of they would stop working.
Unfortunately this place is no longer running as they decided to close down and sold off all the machines!
I had 2 lab machines report this very error on Monday, as they had been powered down over Christmas and new year. The machines are integrated into IOT lab machines (one a CT scanner for RMA/ASICS, one I have no idea what it does except that it goes 'Ping'.....
The test engineers didnt even want the batteries changed after we reset the bios - they worked and they didnt want to risk downing them again....
On the one hand you have the most advanced technology and the incalculable man-years of detailed engineering work that made it possible.
On the other you have the superstitions, magic rituals and cargo-cult behavior believed to keep any of it working
On the other-other hand (I work in nuclear) this is definitely necessary to make it work