MS> Is it possible to create [a bound] .EXE using the Watcom v10 environment?

If you create a 16bit OS/2 exe,  and you have BIND.EXE (and a couple of
other libs) from an older Microsoft compiler product,  it will probably
work.

However,  it is much easier to do this:  Place a dos-only version of your
program in the "STUB" of your OS/2-only (even 32bit) program.
This,in effect,  is two EXE's in one.  All of the EXE's in \watcom\binb are
like this.  You will need to tell WLINK something like "option
stub=foo.exe".

The default stub program is the one that prints "This is an OS/2
program" and exits.


 MS> Is the lack of 16-bit header files the major problem?

This is a problem,  and probably a mistake on Watcom's part.  You should
complain (I am simply adding "\msc\include" to the end of my
INCLUDE environment variable,  which finds the MSC 6 os/2 header files).

 MS> Or is that really an issue? Can the Watcom linker 
 MS> produce "bound" .EXE files, or is there another 
 MS> utility that does this?  I don't have the OS/2 1.x

The BIND program,  as far as I know,  was only shipped with MS compilers
(or IBM compilers that were really just MS compilers).   Sometimes a
"two in one" exe is smaller than a BOUND program.

 MS> toolkit, or (that I'm aware) access to a copy. Isn't

It was on the devcon#3 cdrom.  Everyone should have a subscription to the
devcon cdrom (I'm thinking about making it a prerequisite for OS2PROG
members )


--- Maximus/2 2.01