Annoying SCSI issue

[Torvus]

Okay, this is getting old. I ordered a Seagate Barracuda 4 for my system so I could burn and do some other stuff on my computer in the mean-time. Everything's cool, I get the drive in the mail, hook it up, jumper it and power on my system. Okay, my system boots up and shows it at ID 0 (funny, I thought I set it to 1). It then enumerates my two SCSI CDs, at ID 2 and ID 4. All cool still. I boot into DOS so I can fdisk my drive and get it running, but lo and behold, fdisk only shows my IDE drives, not my SCSI drive. After some tinkering around, I find out that if I take all devices off of my primary IDE, the SCSI drive will show in fdisk. That won't really cut it, I'm afraid, since I'll be losing about 10 gigs worth of storage. Okay, so here's the system configuration:
ABIT BH-6 w/ latest BIOS
Future Domain SCSI controller 1601
Diamond Monster MX 300 Soundcard
Diamond Viper 550
Intel DSL modem
Realtek 10/100 NIC
3 IDE hard drives (Western Digital and a Seagate on the Primary, an IBM deskstar on the Secondary) I haven't heard of any incompatibility between the Seagate SCSI and IDE drives, but perhaps somebody could shed some light on this issue?

<ed> bad link <\ed>

 

[Slikkster]

This is a blurb from Adaptec's site:

Adaptec's ISA and PCI SCSI controller cards provide termination power to the SCSI bus. If one or more devices also set to provide Termination Power to the SCSI bus, then the devices may not be detected normally by FDISK.


Most hard drives have an option for Termination Power (often labeled as &quot;TP&quot; or &quot;TermPWR&quot. If the hard drives that you're using have jumper settings for Termination Power, then verify the jumpers are set to:

&quot;Disabled&quot; or &quot;Receive Termination Power from SCSI bus&quot;

Also, check your SCSI Bios to see if it's set to auto-configure the ID's for your devices...if that's the case, the jumper you've set on the drive will probably be meaningless at best, and maybe troublesome at worst. If the bios is set to auto-configure device ID's for the SCSI bus, then I'd remove the jumper, or at least check the manual to see where the jumper should be placed if the controller auto-configures.

 

[mnlkmh]

Sound like you have the scsi card mapping the scsi hd to c:
(I have a old Adaptec 2904VL that can do that anyway)
If there is drives on the IDE bus they will conflict with each other.