Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewsl!cbnewsk!dez
From: dez@cbnewsk.att.com (daniel.e.zuccarelli)
Newsgroups: comp.os.os2.programmer
Subject: Re: DOS driver under OS/2
Keywords: device driver
Message-ID: <1990Nov16.133628.6975@cbnewsk.att.com>
Date: 16 Nov 90 13:36:28 GMT
References: <478@epicb.com> <1990Nov15.160926.5036@cbnewsk.att.com> <10480@ubc-cs.UUCP>
Distribution: na
Organization: AT&T Bell Laboratories
Lines: 19

In article <10480@ubc-cs.UUCP>, ballard@cheddar.ucs.ubc.ca (Alan Ballard) writes:
> In article <1990Nov15.160926.5036@cbnewsk.att.com> dez@cbnewsk.att.com (daniel.e.zuccarelli) writes:
> >However you must rewrite your drvier for OS/2, and it
> >must be a bi-modal (both real and protected mode) driver if you plan
> >on calling it from the DOS box (which runs in real mode). 
>  
> Supposedly, some DOS drivers can run unchanged, as long as you *only* call 
> them from the DOS box.  However, the constraints are such that few drivers
> are likely to make it... character mode only, no interrupt handler,
> (hardware) device cannot also be accessed in any way from prot mode.
> 
> Alan Ballard                   | Internet: ballard@ucs.ubc.ca

How would it be possible for OS/2 to install such a driver?
-- 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
"Well, there's not much to see actually; we're inside a Chinese dragon."
					- Dr. Howard Bannister
Dan Zuccarelli - AT&T Bell Labs CB/RV, INTERACTIVE Systems Corp.