The worst-selling Microsoft software product of all time: OS/2 for the Mach 20
devblogs.microsoft.com
devblogs.microsoft.com
While DOS with Windows 286 worked okay, OS/2 for Mach20 never would get past installation.
I finally told my boss that I was getting nowhere with OS/2. She contacted her boss and later relayed to me that OS/2 for Mach20 had been marked as a "non functional product" and would be going away.
The happy ending was that I kept the Mach20 board in my ancient PC and used it for my remaining programming classes. It ran Turbo Pascal and QuickC for DOS quite well.
"¹ If you’re one of those retro-computing archivists, I guess this poses an extraordinary challenge even greater than possessing a Tandy Video Information System: Can you track down one of the three remaining copies of OS/2 for Mach 20?"
There was a big warehouse in Fort Worth where un-sellable products ended up, so I definitely could've won that challenge. They had pallet-loads of brand-new VIS machines bundled with all 20-odd games for around $49.
More accounting fun! This time around revenue recognition. It used to be that you had to ship a physical item to a customer in order to recognize the revenue from the sale. So the place I worked at back then would send out first-draft manuals to customers who had ordered the not-quite-done software. When we finished it and it passed testing, we'd send them the actual diskettes and an updated manual.
I never heard of any complaints being lodged, so it must have been a standard industry practice of the time. Or the salespeople had already smoothed the waves with the customers.
Boss has a Dec laptop that was _thin_ (Digital Hi Note?)
We had a Dec Alpha running an early version of Windows NT
I had a Dec PC that started out as a 486, then got a Pentium 120 upgrade daughter card. (possibly this one, though that looks like a Mid tower and the one I had was full-sized) http://www.computinghistory.org.uk/det/43316/Digital-Persona...
Nowadays...your expansion slots are used for your GPU and....well....maybe a better WiFi card?
That OS/2 for such cards never sold well is not much of a surprise: OS/2 1.x was pretty much pointless anyway, and even the comparably-more-useful Windows 2.x releases were not exactly bestsellers.
I did some OS/2 1.x development on a PS/2 Model 80, a full-height tower that was as expensive as it was heavy. It had a real 80386, VGA, 2MB RAM, plus a whopping 120MB of disk space. The new proprietary MCA bus wouldn't fit any existing expansion cards, and a lot of existing (DOS/Windows) software wasn't available in the new-fangled 3.5" floppy format either.
Switching the thing on was the best part of the experience: the heavy-duty power switch made a very satisfying 'clunk' sound. The duration of the BIOS memory test and the OS/2 boot process were less fun, and software development was downright horrible: despite the US$ 5000 price tag, the OS/2 SDK was extremely limited and slow, and only used the 386 as a slightly faster 286 (whereas DOS-based tooling at the time would let you do some pretty interesting things already).
These days, I tend to buy higher end computers and use them for a long time. For example, I just retired my 2013 Mac Pro this last week. It was running fine, but can’t update to the latest OS and some of my critical software needs the latest OS to run, or will shortly. If it weren’t for that, I probably would have waited another year or two to upgrade.
- Amiga: http://amiga.resource.cx/exp/a2386sx - Atari ST: https://www.atarimagazines.com/startv4n12/pcditto2.html
- Acorn Archimedes: https://chrisacorns.computinghistory.org.uk/32bit_UpgradesA2...
- BBC Micro: https://chrisacorns.computinghistory.org.uk/Computers/Master...
I used Amiga and Archimedes PC cards in the 90s - couldn't tell you which ones - and have seen a BBC Master 512 in use. I admit I've never actually seen an ST hardware emulator though.
(I used the software-based pc ditto on an ST in the 90s, which did a decent job of being a IBM XT, albeit one running at about 1 MHz. But I'm sure it would have run very nicely on a Falcon or TT030.)
I really enjoyed my time developing on OS/2 1.2 and later 1.3 with the IBM intern-developed VESA SVGA driver. It was multitasking that really worked. My first PC was a clone 386DX with socketed cache chips, 8MB RAM, and 11 MHz overclocked ISA bus to make the video updates faster.
My next PC was a PS/2 Model 77 running OS/2 (and later Win NT). It was so hard finding an MCA SoundBlaster-compatible card (by Piper Research) so I could play Doom.
It was the base for LAN Manager, IBM/Microsoft’s answer to Netware. Never anywhere near as popular as Netware, but some people used it.
OS/2 1.x Extended Edition also had some mainframe integration bits (Communications Manager). Useful stuff if you needed to talk to an IBM mainframe.
Uphill, in the snow, both ways, etc, etc.
Operating Systems are in a really weird place right now. I find that macOS has regressed somewhat performance-wise (it was very impressive on my first mac, a powerbook), as has windows. I’ve just switched my PC to Arch, and I think the Linux desktop experience is more or less there these days. The only thing holding me back before was Windows-only games, but the recent Valve sponsored efforts have proved fruitful, and the likes of World Of Warcraft play just great under Proton.
It was very interesting for operating systems in the 1990s, and I think we’re looking at another great period in the 2020s.
There seems to be a lot of focus on taking control from the consumer and into the hands of the manufacturer, similar to the model used by mobile phones already.
Usually there's ways around it like with Apple's system integrity protection and sealed system volume. But attestation is also becoming an ever bigger thing and I could see apps being blocked on those systems in the future.
Sadly, OS/2 Warp was still 16 bit in important places and had a massive flaw in that it had a single I/O queue that could completely lock out the user ( no keyboard or mouse ) even if the OS was technically still running.
I think we are entering an era of several freely available and viable desktops. The pro and con though is they will all be the same from an application perspective since they will all be primarily running POSIX apps ( perhaps with Linux expressions ).
Also, while containers are amazing, they kind of tie us down to the Linux kernel ( at least for now ).
It was an interesting era, retail ads for everything from 10 mhz 8086 to 20 mhz 386 in the same issue.
Meanwhile if you installed Windows 95 on its minimum supported 80386/4M RAM system, you could literally die while waiting for it to boot. I've personally witnessed it once, luckily was very young and had some runway.
And then enjoy horribly distorted greyish 16-color palette.
http://datasheets.chipdb.org/Cyrix/New%20Folder/faq386up.htm
I also inadvertently made a domain controller mirror with SAMBA when fooling around with that.