Xref: utzoo comp.periphs.scsi:1286 comp.os.msdos.programmer:1797 comp.sys.ibm.pc.hardware:2799 Path: utzoo!attcan!uunet!clyde.concordia.ca!ccu.umanitoba.ca!shad04 From: shad04@ccu.umanitoba.ca (Dan Fandrich) Newsgroups: comp.periphs.scsi,comp.os.msdos.programmer,comp.sys.ibm.pc.hardware Subject: SCSI software interface for PCs Summary: Is there a standard? Keywords: SCSI,IBM PC,tape,Future Domain,CMC,Targa Message-ID: <1990Nov2.120037.11620@ccu.umanitoba.ca> Date: 2 Nov 90 12:00:37 GMT Organization: University of Manitoba, Winnipeg, Canada Lines: 34 I've looked high and low for references to a standard software interface to gain access to a SCSI bus in a PC. What I am looking for is a method of talking to SCSI devices that works regardless of what brand or type of controller is being used. Having a standardized hardware interface (SCSI-1) that allows 8 heterogeneous devices to be connected is just fine and dandy, but what good does it do if you can't use those devices? Someone gave me a SCSI to QIC-36 adapter and a tape drive along with sources to a backup program. Of course, the backup software is for a brand X controller, and I have a brand Y (where X=CMC International Targa and Y=Future Domain TMC-870). I've looked through the TMC-870 BIOS and there is no easy way of using it to send & receive SCSI commands & data. Essentially, I'm forced to shell out the $75 Future Domain wants for the OEM device driver kit and rewrite the backup program. Or I could simply get a Targa SCSI controller and plug it in next to my TMC-870, totally defeating the purpose of SCSI! What I would like to see for SCSI is something like the FTP packet driver specification for Ethernet cards. Packet drivers are available for practically any Ethernet card you care to name, and most networking software purporting to be device independent uses it. Ralf Brown's interrupt list contains no mention of SCSI at all. I'm sending him a detailed description of how CMC International handled (that's past tense -- they're defunct) their software, for inclusion into his list. They supplied a device driver which chains onto INT 78h and contains functions to send a SCSI command, send a command and data, send a command and receive data, and reset the bus, along with others to set the port number, etc. It has its problems, but it's close to what I'm dreaming of. Please share your thoughts. >>> Dan -- Internet: shad04@ccu.umanitoba.ca CI$: 72365,306 FidoNet: 1:153/511.1