NA> If I remember, it reached a point where I found it to be convoluted and
NA> needlessly complex just to get OS/2 to do the most basic things on newer
NA> hardware. It definately was the device drivers that killed it for me.
NA> Video cards, LAN, hard drives beyond a certain gigabyte count, etc.
NA> 
NA> Around that time I was transitioning from "I'll make it work on OS/2 no
NA> matter what" into "OS/2 is turning into a freaking nightmare". I was also
NA> starting to get some helpful but bleak remarks from fellow OS/2 users
NA> suggesting that I purchase a certain brand of hardware (usually more
NA> expensive), meanwhile in the office where I was subjected to Windows NT
NA> and 2000... things just worked.

That was my experience as well.  OS/2 was the best multitasker for DOS, handled
 my BBS nodes better than DOS by itself, and allowed me to use my computer for
other things at the same time.  This of course was back when few people had
computers, and even less had more than one.  Nothing like today, where
everywhere I turn in my house, I see a computer.

At the time, I upgraded everything else - servers, my PC, etc, and the BBS was
stuck on the old Pentium P-133.  It was so outdated when it comes to hardware,
not to mention I figured when the hardware quit, I would be screwed since the
stuff is so old.  Even the drives were older than dirt.

When I got OS/2 working in VMware ESXi, that was huge.  I freed the BBS from
it's old hardware, no more driver issues ever again, and it all works
fantastic.  Even on my new HP DL-380 which has almost 300GB of ram in it.

Throw the BBS a vCPU on that hardware and it is blazing fast.

- Mark

--- WWIVToss v.1.52 
 * Origin:  http://www.weather-station.org * Bel Air, MD -USA (618:100/12.0)