Hello Arne!

Thus quoth Arne de Bruijn to Mike Byrne:
 MB>> Call DosGetMessage().
 MB>> I can't seem to do that in my programs.
 MB>> Keep in mind I'm compiling with VP.

 AdB> Yes, I found that problem too. It seems the function DosGetMessage does 
 AdB> not exists in the OS2 libraries, but a function called 
 AdB> DosTrueGetMessage does. The difference between it and DosGetMessage 
 AdB> is an extra parameter, using 0 for it seems to work fine.
 AdB> [..]

I hope I may butt in here.
In fact, DosGetMessage (and its aliases DOSGETMESSAGE, Dos32GetMessage and
DOS32GETMESSAGE too) does exist in OS2386.LIB. It is a small object (not an
import definition), containing code which calculates the 'extra' parameter
you discovered and then enters Dos32TrueGetMessage. The mystic extra
parameter is the adress of the so called message segment or 0 if there
isn't one. The message segment is added to your programm if you run MSGBIND
to bind one or more message files (different language versions for
instance) to your EXE. Dos32TrueGetMessage will look up the bound message
files first before going to disk. I use this mechanism in my programs to
bind some language versions (german and english in my case) into the EXE
and leave the other optional language versions as separate message files.
If you don't link the mentioned stub into your programs you cannot use
MSGBIND.

bye, Detlef

 ! mailto engert{at}ibm.net, 2:2490/2576.1{at}fidonet, 21:100/1015.9{at}gernet
--- Sqed/32 0.999/r00108