How Compaq Cloned IBM and Created an Empire
internethistorypodcast.com
internethistorypodcast.com
2016 in that universe is probably a very different world, with lots of different types of devices with different strengths, and a much stronger focus on cross-platform protocols.
The BBC did a fun retelling of the rivalry between Sinclair and Acorn a few years ago. Worth a watch if you haven't already seen it. https://en.wikipedia.org/wiki/Micro_Men
If anything, the 2000 should've used a new chipset instead of being the same as the 1000, and there should've been a much bigger jump in performance on the 3000 and 4000. By offering different chipsets on the high end models and the low end models, they could have captured both the high end and low end markets. As it was, the high end models were useful for the Video Toaster and not a lot else.
In comparison the A500 had one expansion slot on the side.
Arcades had Street Fighter and all the action. Consoles had the most faithful arcade ports as well as all the JRPGs. Amiga/ST had the better sound, less configuration hassles, and for a while, better graphics.
PCs had...flight simulators and spreadsheets and yuck, MS DOS.
As a personal anecdote, i got into the PC world by buying a second hand 486 (DX luckily, i had not the first clue at the time). No sound card, F if i recall what the HDD was (but just having one was a step up from floppy shuffling), and maybe 4MB of ram.
By the time i was done with using it, i had added a sound card, replaced the graphics card, added a CDROM, doubled the ram (if not more), and gotten a whooping 1GB HDD in there.
For the life of the A500 it stayed the same. I did borrow an extra floppy for a while, and that allowed me to speed up the games loading for a while, but it was pretty much a sealed unit for me over those years.
That seems like a contradiction, unless nextstep was a internal project at Apple he took with him when he left.
The IBM luggables were huge and unreliable. They had 2 full height 5 1/4 inch floppy drives, no hard drive, a 4.5MHz 8086, and something like an 8 inch amber screen that you could barely read. Basically, IBM put a bunch of parts they didn't know what to do with into a product and tried to sell it. The only way they could really sell them was to captive audiences like students, like at some engineering schools.
"Halt and Catch Fire" - http://www.imdb.com/title/tt2543312/
HCF - Halt and Catch Fire
IIB - Ignore Interrupt and Branch
PIL - Perform Infinite Loop
etc.
I can't find an exact copy, but this appears to be somewhat of a superset:
http://www.physics.ohio-state.edu/~bcd/humor/instruction.set...
Another:
I like:
CML Compute Meaning of Life
What's the bet its opcode is 0x2A ? :P
This would be pretty handy at times.
One of the drive tests performed during maintenance was a random seek. Normally, the head position was controlled by a servo with a feedback loop, but this one time the servo failed and the magnet drove the head assembly out the back of the equipment and into the wall .. right at crotch height. There was a supplemental maintenance instruction issued shortly afterward to limit the use of that procedure, and to not stand behind the equipment when it was being run.
Its crazy how terse PPC's instructions are, the PPC ISA book felt like reading PHD paper where as ARM's ISA manuals felt like a gentle novel.
Here's a wonderful excerpt from the latest 2.07 ISA:
"The following notation is used in the definitions below. When MMCR0_PMCC = 11, “PMCs” refers to PMCs 1 - 4 and “PMCj” or PMCjCE refers to “PMCj or PMCjCE, respectively, where j = 2 - 4; otherwise, “PMCs” refers to PMCs 1 - 6 and “PMCj” or PMCjCE refers to “PMCj or PMCjCE, respectively, where j = 2 - 6."
Get all of that? Good, now go write code to make use of it.
[1] https://en.wikipedia.org/wiki/Enforce_In-order_Execution_of_...
I'm sure that having programmed PPC assembly language, you find it very natural (IBM motto: "We found five vowels hiding in a corner, and we used them _all_ for the 'eieio' instruction so that we wouldn't have to use them anywhere else")."
-- Linus Torvalds, LKML (http://ozlabs.org/~rusty/linux.conf.au-2004-emails.txt)
But some of these instructions did not perform useful behaviour, many of them freezing the machine. Some were even worse, freezing the machine into a state where it was very rapidly toggling the bus. If you had the wrong thing attached to the bus, it could very literally be Halt and Catch Fire. Instruction $DD on the 6800 was labelled HCF in some instruction set listings for that reason.
The show is fantastic. Season 2 was good as well, but I still liked S01 a little better.