🚀 go-pugleaf

The company I work for needs to write a set of device drivers for certain cards
installed on 486 PCs under OS/2 2.1.

We have it on good authority (a book on the subject) that we need to generate
these as 16-bit code.  The author recommends we use either Microsoft C 6.0 or
Borland C 3.5 or 4.0.  He used Microsoft 6.0 for his examples.

We have been unable to locate and purchase a copy of MSC 6.0.  According to
Microsoft they don't even make it anymore.

We have tried installing Borland C 4.0 on our machines but have been unable to
make it work properly (interferes with the video driver, does not pick up
necessary libraries, etc.)  Does anyone out there know if there is a special
sequence of installation steps we have to go through to properly install BC 4.0
to run from the command line in OS/2?  Is this possible?

Failing this, does anyone know if Visual C++ 1.5.2 can be set to generate
16-bit cde for device drievrs?  Does it have an assembler supplied with it?  If
not, is it compatible with either the TASM or MASM assemblers?

I am crossposting this to comp.lang.c++ because of the current bandwidth
regarding "best/appropriate compilers".

Thank you.  Please respond via email to andrew.furlong@prior.ca as soon as
possible.

-- 
Andrew Furlong            |  Nothing disappears without a trace.
PRIOR Data Sciences Ltd.  |  The Truth is out there.  Find it.
Kanata Ontario Canada     |  "Toads just fell from the sky."
andrew.furlong@prior.ca   |  "Maybe their parachutes didn't open."