Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!haven!umd5!cgs From: cgs@umd5.umd.edu (Chris G. Sylvain) Newsgroups: comp.sys.ibm.pc Subject: Re: DMA transfer Keywords: comp.sys.ibmpc Message-ID: <5421@umd5.umd.edu> Date: 6 Oct 89 15:57:01 GMT References: <9577@attctc.Dallas.TX.US> Reply-To: cgs@umd5.umd.edu (Chris G. Sylvain) Organization: University of Maryland, College Park Lines: 22 In article <9577@attctc.Dallas.TX.US> chasm@attctc.Dallas.TX.US (Charles Marslett) writes: >After a long series of hassles with MSDOS and its demented attitude toward >device drivers, I would strongly reccommend you avoid writing a device >driver and making your access to the device "clean." [...] MSDOS just does >not understand any kind of block device that is not part of the file system! Much as I respect the poster and the great volumes of very informative technical information he has posted in the past, I submit that the above is a false assertion. Please check with the folks at IOtech in Cleveland, Ohio. Their IEEE-488 interface card for the PC's is shipped with a device driver that installs itself as "\DEV\IEEEIN" and "\DEV\IEEEOUT". Both DMA and non-DMA transfers are supported. Please excuse me if I have misunderstood the technical details of the assertion. I have used their product with success. -- --==---==---==-- Borogove: A thin, shabby-looking bird something like a live mop -- ARPA: cgs@umd5.UMD.EDU BITNET: cgs%umd5@umd2 -- -- UUCP: ..!uunet!umd5.umd.edu!cgs --