P
Percival P. Cassidy
I used Warp 3 and Warp 4 on many different machines, and for many yearsNo way! I ran OS/2 v2.x and I was a beta tester for OS/2 v3. And the
beta testing things were doing just fine. But just like in IBM's style,
they screwed up in the released version. They changed many of the
drivers and a huge amount of beta testers couldn't even get it to
install (including myself).
Better product, my eye! I have at least a dozen computers right in this
room alone. And I can take that Warp install CD and I can guarantee you
that it will not install on any of them. Then there was all of those
FixPaks! Most of them broke more than they fixed. And old bugs were
coming back to haunt OS/2. That is because every time IBM tried to fix
something, they made it worse than ever before. Then they would plug
back the old code that had the old bugs.
It wasn't a failure of IBM's marketing! Hell IBM spent 2 billion dollars
on OS/2 alone. It was a failure of IBM's programmers couldn't program
their way out of a wet paper bag. And IBM made promises they couldn't
keep. This later became well known as FUD.
now I have been using its OEM successor, eComStation, on modern
hardware. (Why be surprised that Warp4, released in 1996, doesn't have
drivers for much-newer hardware?) The machine on which I am typing this
is running eComStation 2.0 on a 3GHz dual-core machine with a mixture of
SATA and SCSI drives; the on-board sound and Gigabit networking work. It
also runs fine on a ThinkPad T61. The only trouble I've ever had
installing it was from an IDE optical drive on a machine with a weird
combo IDE/FireWire chip, but once I installed an SATA optical drive eCS
installed and ran just fine -- on a 3.4GHz quad-core machine (OS/2 had
support for 64 CPUs from way back).
Perce