KR> i'm sick to death of slope loving little fucking net nazis for ever
 KR> winging about shit like this. anyone would think that they had some
 KR> right to dictate the way that the board is run! oh, and a gappy new year
 KR> to you and yours.  (-8

I'm too busy trying to figure out how to be part of the Xmas
road toll without actually leaving my study, so I don't have
time to figure out how to be gappy.  I'm also trying to figure
out a few things about 386 assembler programming under OS/2.
I've finally got my act together on a few things.  One is now
I keep a list of all outstanding mysteries, and made them
available for FREQ.  Here is the list so far...

MYST2.ZIP - CSET++/2 2.0 causing linker warning
MYST3.ZIP - BCOS2 1.5 bug
MYST4.ZIP - BCOS2 1.5 bug
MYST5.ZIP - BCOS2 1.5 bug
MYST6.ZIP - Watcom C++ 10.0a bug
MYST9.ZIP - Problem linking with BCOS2 1.5 + OS/2 2.1 doscalls.lib
MYST10.ZIP - BCOS2 1.5 TLINK internal bug
MYST11.ZIP - BCOS2 1.5 TLINK internal bug
MYST12.ZIP - Problem using BCOS2 and LINK386

Some mysteries have already been solved so have been deleted
(is this what you meant by being gappy?).  As you can see, I
have this knack of finding compiler bugs.  I think they are
all bugs except for MYST9 and MYST12.  MYST12 is the killer
one at the moment.  It involves an enormous amount of 386
segmented FUCKING CRAP which I've successfully avoided for
the last 8 years.  I need it to be solved to make the
standard C library replacement nice and kosher.  It's quite
strange.  I'm still chipping away at it though.  I think I
may end up getting a divorce for my efforts though.  :-(
BFN.  Paul.
@EOT:

--- Mksmsg