Kevin Ring wrote in a message to All:

 KR> What tools, etc. do I need to write OS/2 programs in ASM?

The main thing you need is the OS/2 Toolkit, which supplies the necessary
INC files for the OS/2 API in ASM and the import libraries.  It is
available on DevCon.  Programming OS/2 in ASM is very much supported by
IBM.

 KR> (Yes, I'm crazy.  Leave me alone )  Can I use TASM?

Yes, but you will need a version of DOS TASM new enough to support the
"USE16" and "USE32" segment directives.  Also, there is
an old bug in TASM that allows it to wrap around a 64 KB boundary if you
enable 386 code generation, so be careful if you use 386-specific
instructions to make "USE16" segments.  The only way to catch
this problem, as far as I know, is to manually check listing files after
assembly.

Borland does supply "Turbo Assembler for OS/2" with their
"Borland C++ for OS/2" product, but it is really just the DOS
TASM made to run as a native OS/2 program and bundled with the OS/2 API INC
files.  Watcom C++ 10.0 also comes with an OS/2 assembler, WASM, and the
OS/2 API INC files.

 KR> I assume I'll need an OS/2 specific linker.

Yes, but you can use the LINK386 linker that comes with OS/2.  If you have
the OS/2 Toolkit, then you get the linker anyway.

 KR> Is there such a beast?  Also, what books are there on the 
 KR> subject? 

I have an ancient book on programming OS/2 1.x in ASM, but that is the only
book I have ever seen on the subject.  If you are concerned about
application level code (as distinct from device drivers), then you can
probably figure out everything you need from one of the standard OS/2 API
references and the INC files.
 
-- Mike


---