Xref: utzoo comp.periphs.scsi:1303 comp.os.msdos.programmer:1835 comp.sys.ibm.pc.hardware:2864 Path: utzoo!attcan!uunet!crdgw1!uakari.primate.wisc.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!vsi1!daver!news.chips.com!chuckl From: chuckl@chips.com (Chuck Linsley) Newsgroups: comp.periphs.scsi,comp.os.msdos.programmer,comp.sys.ibm.pc.hardware Subject: Re: SCSI software interface for PCs Keywords: SCSI,IBM PC,CAM Message-ID: <1006@news.chips.com> Date: 5 Nov 90 21:11:53 GMT References: <1990Nov2.120037.11620@ccu.umanitoba.ca> Reply-To: chuckl@news.UUCP (Chuck Linsley) Followup-To: comp.periphs.scsi Organization: Chips and Technologies, San Jose, CA Lines: 32 In article <1990Nov2.120037.11620@ccu.umanitoba.ca> shad04@ccu.umanitoba.ca (Dan Fandrich) writes: >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? This is exactly the reason the SCSI Common Access Method (CAM) Committee was formed. They are working on a software interface which works across not only different brands of host adapters, but (with only minor tweaks) different operating systems, and even completely different hardware platforms. I don't know the current status of the proposal. It's been months since I've been to a committee meeting, and for some reason the mailings aren't getting routed to me. But there are some companies that are selling products which they claim comply with the latest version of the proposed standard. For complete, current information contact: I. Dal Allen ENDL 14426 Black Walnut Court Saratoga, CA 95070 USA (408) 867-6630 -- Chuck Linsley chuckl@chips.com #include