home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ukma!darwin.sura.net!convex!bcm!lib!oac.hsc.uth.tmc.edu!jmaynard
- From: jmaynard@oac.hsc.uth.tmc.edu (Jay Maynard)
- Newsgroups: comp.os.os2.programmer
- Subject: Unsupported CDROM drives: Here's a grody idea...
- Message-ID: <7846@lib.tmc.edu>
- Date: 12 Nov 1992 19:36:42 GMT
- Sender: usenet@lib.tmc.edu
- Organization: UT Health Science Center Houston
- Lines: 20
- Nntp-Posting-Host: oac.hsc.uth.tmc.edu
-
-
- I was struck by an idea while writing the article I just posted on getting the
- DAK $199 CDROM drive going to comp.os.os2.misc. It's a really grody hack, but
- has the advantage of sidestepping completely the question of how to do
- low-level hardware access to all these unsupported devices:
-
- How about an OS/2 device driver that, instead of talking to the hardware
- directly, communicates (presumably via one or more named pipes) to a program
- running in a specific DOS session, which would receive the requests and
- process them?
-
- Is this even possible under OS/2? Just how badly am I violating the OS/2
- architecture? I know performance would stink, but it'd at least get access to
- these devices under OS/2 for those of us who can't/don't want to spend several
- hundred dollars on a SCSI adapter and supported CDROM drive. Is it documented
- anywhere just what CDFS.IFS expects of a device driver it's talking to?
- --
- Jay Maynard, EMT-P, K5ZC, PP-ASEL | Never ascribe to malice that which can
- jmaynard@oac.hsc.uth.tmc.edu | adequately be explained by stupidity.
- We survived Jimmy Carter; we'll (probably) survive Bill Clinton.
-