Borland C++ 4.0 and OS/2 Device Drivers

Thread View: comp.os.os2.programmer.tools

4 messages

[T] Back to Threads [V] Tree View [G] Group Articles

4 total messages Started by Andrew Furlong Tue, 15 Aug 1995 13:06

Author: Andrew Furlong
Date: Tue, 15 Aug 1995 13:06

31 lines
2094 bytes

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."

Re: Borland C++ 4.0 and OS/2 Device Drivers

Author: Richard Illes
Date: Tue, 15 Aug 1995 13:13

4 lines
793 bytes

Use the Watcom compiler, it can generate 16 and 32 bit code.  I don't think any
other current compilers can generate anything but 32 bit code.

IBM C 1.0 can generate 16 bit code, and IBM may still sell it.

Re: Borland C++ 4.0 and OS/2 Device Drivers

Author: Will Rose
Date: Wed, 16 Aug 1995 22:13

16 lines
1330 bytes

Andrew Furlong (andrew.furlong@prior.ca) wrote:
: 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.

IBM now seems to be using Watcom for its 16-bit code, such as device drivers.
There was a recent article in DevCon News about this.

Will
cwr@crash.cts.com

Re: Borland C++ 4.0 and OS/2 Device Drivers

Author: D.J. Maconochie
Date: Fri, 18 Aug 1995 06:55

16 lines
1283 bytes

I have used TASM 3.2 to recompile ASM code for use as a Virtual Pascal unit.
TASM will run in a DOS window but compile OS2 PM compatible code. I used the
following command line switches (even though I do not remember what they al
mean).

tasm /MX /ZI /P /OI the last is the most important, directing the compiler to
produce "IBM compatible" code.

Both VP and Speed Pascal produce ASM pseudo-source code on request, which is
dead neat as you can use the code as a template for developing more complex ASM
code without having to remember all the calling conventions etc. (Have other
compilers been doing this for years?

BTW, my newsreader refused to post this follow up just now on the grounds that
the additional text was less than the original article. New police are about!
(Actually I approve).

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads