*** Quoting Mike Bilow to Kevin Ring dated 05-08-95 ***
> 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.

DevCon?  I'm assuming this is an IBM-related BBS? 

*** Quoting Mike Bilow to Kevin Ring dated 05-08-95 ***
> 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.

I have v3.1... I believe it supports USE16 and USE32.... Will this do?  How
does WASM compare with TASM (the DOS version, which I have now)?  I was
considering buying Watcom C as well because I've heard its the best for
OS/2 (and cross-platform) development.  

*** Quoting Mike Bilow to Kevin Ring dated 05-08-95 ***
> 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.

Yep, no device drivers for now...

Thanks for the info!  

--- T.A.G. 2.7c Standard