JDBP>CT>
    >  >                 It has been suggested that this is to do with the way
    >  > Borland defaults 'char', but setting this to signed or unsigned makes
    >  > no difference, and trying the /K2 switch (neither unsigned or signed)
    >  > gives errors from the compiler.
    >CT>

JDBP>  I've found a solution.  I tried adding explicit casts to unsigned char
    >  * to the string literals, but that messes up the resource compiler.

JDBP>  What you need to do is change the declarations of the offending
    >  functions from taking PSZ parameters to taking UCHAR * parameters.
    >  Borland C++ will then implicitly cast the string literals to the
    >  correct type, and call the correct overloaded function.

JDBP>  Well, it works with 2.1A mod 41 and BC++OS2 1.5 on my home machine, at
    >  least. (-:

That's it?  Gee, I knew the minute I reinstalled BC++OS2 v1.0 someone
would come up with a fix.  Where'd you get mod 41?  I only have mod
37...

Michael Douglass
___
 .Mike's Mail Internet:   MICHAEL.DOUGLASS{at}LCHANCE.SAT.TX.US

--- Maximus/2 2.01wb