DM> Do you think you could post the *full* version?  It 
DM> would come in *very*
DM> handy. :-)  (Or, if you put it up on the web, ftp, etc.)  For a few
DM> reasons:

 DN> Sure. It's nothing special really. I'm planning on 
 DN> encapsulating the OS/2 CP API (or most of it, ie. the 
 DN> parts I use ). I have a CPErrorMessage derived from 
 DN> DosMessage which uses a CPE.MSG & CPEH.MSG I created from the
CP INF file.

'Twould be appreciated.  If you would rather not post here, my email is
mcbride{at}ee.ualberta.ca.  Thanks,

DM> A) I'd learn more about OS/2's internals.  :-)  (And, more
DM> importantly, how to use them)

 DN> Get the DDK. Talk about internals yikes! I spent 4 days 

I just mean the API, not the nitty-gritty.  :-)

 DN> pouring over the source for AVIO & VIO windows but am 
 DN> still unable to modify a window's font size on the fly.

Hmmm... that's beyond me.  :-)

DM> B) I'd be able to learn more of the proper 'mindset' for OS/2.  It may
DM> help deprogram me - I'm writing for WinNT at work.  ;-)

 DN> Actually, from what I've heard, you shouldn't have too 
 DN> much trouble between the two except for when you start 
 DN> digging into either .

Such as the API's.  ;-)

DM> C) It would help me debug any other API functions I misuse.  :-)

 DN> A good util I've started using of the DevCon CD's is 
 DN> OS2TRACE, on level 3 mode, it'll output all parameters 
 DN> & returns from a API function call. It doesn't even 
 DN> require the source as it uses passthru libraries.

Ah, but I *know* what I'm sending into the API, and I *know* what I'm
getting back. I display these things on my screen.  What I would like an
automatic method of pulling the rc's from an OS/2 MSG file for is to
prevent needless looking up of error codes.  And to present a standard
error message to the user.  :-)  Without 'shipping' an EXE that is 124KB of
error messages and only 49KB of code.  :-)



--- Maximus/2 3.01