I actually bought a copy of OS/2 Warp when it came out because I was interested in its preemptive multi-tasking, and it was a decent operating system for what it's worth. I was definitely more stable than Window 3.11, but its real problem was compatibility. Back in the early 90s, everything was about getting compatibility, and while OS/2 had good compatibility, didn't have perfect compatibility. As well, I worked at…
Half an operating system: The triumph and tragedy of OS/2
41–50 of 191 posts
Re: Half an operating system: The triumph and tragedy of OS/2
#42I actually bought a copy of OS/2 Warp when it came out because I was interested in its preemptive multi-tasking, and it was a decent operating system for what it's worth. I was definitely more stable than Window 3.11, but its real problem was compatibility. Back in the early 90s, everything was about getting compatibility, and while OS/2 had good compatibility, didn't have perfect compatibility. As well, I worked at…
My computer had 8mb RAM at the time and NT required 16 to install so I "borrowed" another 8 from one of the school computers, installed NT and then returned the memory. It ran well enough on 8.
Even with what was bleeding edge hardware at the time, I still remember trying to finish writing my senior project using Corel Draw and Microsoft Word on Windows 3.11, and having my computer crash ever 30-45 mins, and my project partner eventually broke down and started crying because of how frustrating it was.
Re: Half an operating system: The triumph and tragedy of OS/2
#43Great read. In the end, it seems like a classic failure to resolve the innovator's dilemma. IBM decided that the future of computing would revolve around mainframes because they liked mainframes , not because that's where the facts led them. And ultimately they paid the price for it.
I think it's a bit more complicated than that. Put yourself in the shoes of someone who'd grown up on mainframes. The systems you're used to are fabulously expensive, sure, but their operating systems have sophisticated architectures that allow them to easily juggle multiple users running multiple programs while maintaining the security of the system overall. They are the completest expression ever realized of forty…
Re: Half an operating system: The triumph and tragedy of OS/2
#44Earlier quoted context omitted.
My computer had 8mb RAM at the time and NT required 16 to install so I "borrowed" another 8 from one of the school computers, installed NT and then returned the memory. It ran well enough on 8.
I was lucky enough to have a 486DX-50 (not a DX2-66)with 16 MB of RAM, so it ran perfectly for me. Even with what was bleeding edge hardware at the time, I still remember trying to finish writing my senior project using Corel Draw and Microsoft Word on Windows 3.11, and having my computer crash ever 30-45 mins, and my project partner eventually broke down and started crying because of how frustrating it was.
Re: Half an operating system: The triumph and tragedy of OS/2
#45OS/2 had many flaws but its multitasking was unseen on a PC at the time. I remember formatting a floppy while running two 16-bit Windows sessions (which were communicating with each other) and multiple DOS windows, thinking I was in the future. Even Windows 95 was limited by many system calls being funneled through single threaded BIOS or DOS 16-bit land.
Re: Half an operating system: The triumph and tragedy of OS/2
#46A couple of decades later, Dave Cutler is still around at Microsoft and worked on the hypervisor for the Xbox One at the ripe young age of 71, allowing games to run seamlessly beside apps.
From http://www.theverge.com/2013/11/8/5075216/xbox-one-tv-micros...
>Underneath it all lies the magic — a system layer called the hypervisor that manages resources and keeps both platforms running optimally even as users bounce back and forth between games, apps, and TV.
>To build the hypervisor, Multerer recruited the heaviest hitter he could find: David Cutler, a legendary 71-year-old Microsoft senior technical fellow who wrote the VMS mainframe operating system in 1975 and then came to Microsoft and served as the chief architect of Windows NT.
>It appears his work bridging the two sides of the One has gone swimmingly: jumping between massively complex games like Forza Motorsport 5, TV, and apps like Skype and Internet Explorer was seamless when I got to play with a system in Redmond. Switching in and out of Forza was particularly impressive: the game instantly resumed, with no loading times at all. "It all just works for people," says Henshaw as he walks me through the demo. "They don’t have to think about what operating system is there."
Re: Half an operating system: The triumph and tragedy of OS/2
#47OS/2 had many flaws but its multitasking was unseen on a PC at the time. I remember formatting a floppy while running two 16-bit Windows sessions (which were communicating with each other) and multiple DOS windows, thinking I was in the future. Even Windows 95 was limited by many system calls being funneled through single threaded BIOS or DOS 16-bit land.
Couldn't the Amiga already do all that multitasking on a 256KB machine, years before?
Re: Half an operating system: The triumph and tragedy of OS/2
#48Re: Half an operating system: The triumph and tragedy of OS/2
#49Great read. In the end, it seems like a classic failure to resolve the innovator's dilemma. IBM decided that the future of computing would revolve around mainframes because they liked mainframes , not because that's where the facts led them. And ultimately they paid the price for it.
I think it's a bit more complicated than that. Put yourself in the shoes of someone who'd grown up on mainframes. The systems you're used to are fabulously expensive, sure, but their operating systems have sophisticated architectures that allow them to easily juggle multiple users running multiple programs while maintaining the security of the system overall. They are the completest expression ever realized of forty…
History doesn't repeat itself. But it sure does rhyme.
Re: Half an operating system: The triumph and tragedy of OS/2
#50I called DEC and they too believed it existed, so they (while I was still on the line) called their contact at IBM. After being transferred twice, we arrived at the person who could mail me the driver, but I would have to sign an NDA. Myself and the DEC rep explained we didn't want source or a beta driver, just the release one. He insisted every customer had to sign. I said I'd think about it. After hanging up, the DEC rep couldn't stop laughing. He asked if I wanted a free copy of NT compliments of DEC. I took it and it had the correct driver.
I tried, but they had no chance.