JP> SS>
JP>   > Since I use my OS/2 machine for programming DOS (and
hopefully soon, OS/2)
JP>   > apps ...
JP>   >                     ... I've had some bad code (e.g. stray
pointers, bad
JP>   > addresses, etc.) that locked OS/2 (2.11) tight as a drum.  ...
JP> SS>

JP>   This is not to say that VDDs are in general badly written.  On the
JP>   contrary, in a couple of years that one sequence was the only way that
JP>   I found to cause a TRAP from a VDM.  And even that was undocumented
JP>   stuff that I shouldn't really have been fiddling with.  Nevertheless,
JP>   it is important to bear in mind that VDDs may not be perfect.

A good thing to bear in mind, but one might also consider that 2.11,
at least on my machines at work, a friend's machine at home, and a
number of test machines at his work, was the most unstable, hang-happy,
downright _evil_ version of OS/2 ever released. I've had great success
running every other version of OS/2 2.0 and above on every machine I've
installed it on, and the friend i mentioned is an OS/2 veteran from the
1.x years. The machines we installed it on ranged from the cheapest
clones to PS/2's, and it could not be made to run worth a crap on any
of them. Just my 2 cents...

Kelly

___
 X KWQ/2 1.2g NR X Look Ma, I'm a *Beta Tester*: KWQ Mail/2 for OS/2 v2.X!

--- Maximus/2 2.01wb