But they left S, X, and Z rotationally symmetric, so if you choose a non-palindrome vanity plate with only those characters, you can mount it upside-down and fool plate-readers.
Well, ackchyually, the first releases of FrameMaker were created on Sun 3/50 workstations with 4MB of (unexpandable, soldered-in) RAM on a 16Mhz 68020. Most customers had the same model, and could work on modestly-sized documents with ease.
But it's not a lot of space for documents of hundreds of pages, so typical customers who were using FrameMaker to write user manuals for their products had to use "book" files to tie together individually edited chapter files. Then, once in a while you'd have to push the "generate" button on the book to get all the page numbers consistent between chapters, all the cross-references updated, and generate the updated Table Of Contents, Index, etc. You're welcome.
But there's a potential degenerate case where Chapter 1 might have a forward reference to Chapter 2 ("see page 209"), but due to some editing in Chapter 2, the referenced material now on page 210. Well, in some fonts, "209" is wider than "210" (since "1" can be skinny). So, during the Generate operation, the reference becomes "see page 210". But there's some tiny chance that this skinnier text changes the including paragraph to have one less line, so there's some tinier chance that Chapter 1 takes one less page, so Chapter 2 starts one page earlier, and now the referenced material is back on page 209. So now we're in a loop.
This was such an unlikely edge case that nobody else noticed that it even existed, much less that it was detected. I didn't bother with a fancy error message; it would just give a little one-word popup: "Degenerate". Years later, mild panic ensues when a customer calls in, irate that the software is calling them a degenerate. (And it wasn't even a real example, just some other bug that triggered it.)
You are saying that because the word processing and publishing software hasn't moved forward since those days, in fact it has moved backward. You can thank Microsoft's monopoly for this.
Colossus: The Forbin Project is simply a renamed release of The Forbin Project, a few months after the later had a poor opening. Didn’t help the box office much. I liked it, back when it was easy to dismiss as an impossible dystopia.
Waymo halted service in San Francisco as of Saturday at 8 p.m., following a power outage that left approximately 30% of the city without power. The autonomous cars have been causing traffic jams throughout the city, as the vehicles seem unable to function without traffic signals.
That was one option I thought of at first (mentioned in the first section), but the info I found indicated that the /370 models used the same firmware as the "plain" 5170s - if there were any BIOS extensions, they were probably somewhere on the add-on cards. The AT/370 also had 512K of on board RAM, while this BIOS seems to indicate 640K.
Plenty of people remember, and used, them. Just not people who tend to hang out here. I knew several IBM VM dev types who had them as light dev/remote mainframe access machines, usually at home. They were popular enough there was a followon product: the PC/390 which was the same idea, more advanced processor, based on a PS/2 microchannel platform (and, AFAIK, OS/2).
You want really obscure? Unisys had the same idea with the "Micro-A", which was a PC running OS/2 with a coprocessor card with a single chip implementation of an A-series mainframe. I know of 2, possibly 3, still around.
Details: The IBM AT/370 used standard bios on the motherboard, and the two 68k custom cards had their own bioses. The 68ks were very heavily modified by one of the motorola engineers.
Its the second version of the AT Bios that was disgusting was verion 2, that ran on 6mhz 286s and prevented you from swapping the crystal for a 16Mhz/8Mhz speed up. The first version had bugs, and the third version was for the 8Mhz machines. ( still a few bugs ).
Oops. Anyway, I remember attending a talk by one of the IBM engineers back when they first released the XT/370. He said that they looked at all possible ways to integrate their production line as a kind of secondary track off of one of the main production lines for the PC/XT, but the most economical option ended up being a separate facility that would receive normal pallets of regularly boxed, end-user XTs from the main factory, unbox them, make the mods, and pack them back into XT/370-labeled boxes for shipping.
The high sale price was due to the fact that this was a rare "REVENGE of the Jedi" rather than the normal "RETURN of the Jedi" poster. The back-story is that the movie title was originally going to be "Revenge..." but then there was pushback because Yoda had said "A Jedi craves not revenge" in the previous episode, so it got changed.
And there are 2 varieties of this "revenge" poster, too. Both of which were in this collection. One without the date, and one with [0] which sells for ~1/3 as much. Even though these were printed in reasonably high quantity and distributed straight to the collector market at the time of the movie's promotion, since the franchise was by then quite popular.
Yeah, and I suppose you’re going to tell me that Han didn’t shoot first, either. Did you refer to an original 1980 70mm release print, before all the fiddling around they did on subsequent releases? And newspapers and fanzines from 1982 that covered the issue (at first, LucasFilm denied these posters even existed).
On the other hand, it seems that you are, in fact, correct. Oh, well.
