john ball wrote: I dont recall all the device settings, but you can sort of wing it. the card usually is addressed at 300, irq 5 to stay clear of other common ISA assets (usually a scsi controller) If you want to poke at it, you can boot dos, debug and use the port command to read 300, 310, ... and you will hopefully either find 0xFF as a result of a byte in command, or something which is 0bxxxxx101, that is low order bits = 0x5 after masking. If you find that, you have the main status input from the drive. one bit shows ready on the input port, one bit is the data transfer bits, and the other is the drive busy, as I recall. Most hardware derived from the Everex design, whether it is a controller and drive with a qic-24 -> qic 2 card, and a simple bus interface , or the integrated model like this that goes directly to the qic-24 drives of various densities. some vendors and everex strived to screw this up, but if you could find this port, usually the commands worked. I believe that the controller you have is probably set to 0x300, but I could be wrong. Once I got my bearings the dip switch had the most significant 6 bits of the 10 bit ISA I/O address, with the lower 4 not useful, since the controller was only addressable at 300, 310 ... I'll try to find some of my listings to get a list of possible device addresses, and that would allow you to decode the switches. I don't recall what the other configuration switches did on that controller or others like it, but I don't think they were usually changed. BTW, the DMA channel and DMA Acknowlege had only the requirement that they track each other, most drivers will dynamically figure out where the DMA is if they use it. Also a lot of software could be set not to use DMA and byte transfer for data, as on the old AT bus that was sometimes faster. Jim Jim

Hi All, Dayton starts next month on the 18th. I'll be there. So will 3 of my ham friends from my area (Boston, MA). Any plans for getting together? If not, any recommendations for good restaurants? Thanks Joe Heck