Xref: utzoo comp.sys.ibm.pc:35643 alt.msdos.programmer:459
Path: utzoo!utgpu!watmath!att!ucbvax!tut.cis.ohio-state.edu!ukma!gatech!hubcap!hutch%citron.cs.clemson.edu
From: hutch%citron.cs.clemson.edu@hubcap.clemson.edu (David Hutchens)
Newsgroups: comp.sys.ibm.pc,alt.msdos.programmer
Subject: Re: Device driver wanted
Message-ID: <6655@hubcap.clemson.edu>
Date: 2 Oct 89 16:40:33 GMT
References: <27@venice.SEDD.TRW.COM>
Sender: news@hubcap.clemson.edu
Reply-To: hutch%citron.cs.clemson.edu@hubcap.clemson.edu
Lines: 17

From article <27@venice.SEDD.TRW.COM>, by press@venice.SEDD.TRW.COM (Barry Press):
> Newer versions of DOS (3.3?) have a thing called DRIVER.SYS.  Have you
> tried that?

Close, but no cigar.  DRIVER.SYS has the annoying habit of calling
the BIOS to do the actual I/O.  The _Older_ PC/AT, which I believe
the requester said he had, has a screwed up BIOS that IGNORES the
information passed by DRIVER.SYS.  (If he does have a newer one, this
solution should work).

I am one of the "lucky" ones that have a screwed up BIOS, so for me
if not the original poster...  Does anyone have a device driver that
does not use the BIOS at all?

	David Hutchens
	hutch@hubcap.clemson.edu
	...gatech!hubcap!hutch