🚀 go-pugleaf

I've just started reading this group, and find that I'm not alone with my
OS/2 2.0 problems.  I too had the video problems on an AST with SVGA..IBM
tech support sent the same hand-labled fix to me.  I must say that I am 
much happier with the AST's native capabilities (IBM suggested first that I 
change all references to svga to vga in config.sys...blechhhh!!!).  I was
unable, however, to get any assurances that the new bhsvga.dll would be
standard in OS/2 (sigh).  Like an earlier poster, I have also had OS/2 just
seemingly decide it can't find anything any more (the os2char.dll paradox)
even though all config files are in seemingly perfect order.  To the posters
who suggested more than chkdsk: no reported errors from both.  To whoever 
suggested HPFS:  not exactly sure, but I don't think that would help me. 
I have to have at least one FAT partition for reasons I can't explain here.
I also have problems with NETWARE (might be NW's fault) communicating as
it should during shutdown..that is to say, unless NETWARE times out, trying
shutdown has no effect.  It's close 'em all down by hand time usually.  

Now, before all of the blowtorches come out, I want to say that I am making
an honest effort to live with this stuff, and that IBM did come clean with
the driver patch.  I do, however, think that it's a shame that a product 
heralded by IBM so loudly should come unglued in the ways that it does (I'm
mainly referring to the boot failures).  I hope this problem gets at least
*some* attention from IBM.

Oh yeah, to the poster who said that NT was originally going to be named 
OS/2 3.0, I think MS owns the rights to the name "OS/2 3.0".  This is 
further supported by a reply from good (?!?) ole bgates@microsoft.com
to a fellow employee that NT will be renamed OS/2 3.0 at some point 
(not exactly how he put it, but this is the gist).

Tom Wilson
ctwilson@rock.concert.net
sasctw@duckhead.unx.sas.com   (certainly *NOT* a SAS spokesperson)