SCA-2 HHD with Atari Falcon or Atari TT ...

[franklukas]

I have a COMPAQ BD0096349A that I cannot get to work with an Atari Falcon or Atari TT regardless of whether it is the only device on the SCSI bus or paired with a SCSI hard drive that works fine on its own.

I assume the hard drive is fine and not defective.

I seem to recall reading that all SCSI devices including 16-bit ones are compatible with the SCSI-1 standard, right? The Compaq drive is an 80-pin model with a 50-pin adapter.

The COMPAQ drive is listed during booting with HDDriver 13.01 and appears in Hddrutil, but after selecting the hard drive, all menu entries under "Medium" remain grayed out.

[uweseimet]

I have a COMPAQ BD0096349A that I cannot get to work with an Atari Falcon or Atari TT regardless of whether it is the only device on the SCSI bus or paired with a SCSI hard drive that works fine on its own.

In general, any additional drive can make an analysis more complicated. If something appears to be wrong with a particular drive, do not connect other devices when analyzing a problem. Concentrate on the non-working hardware only.

I seem to recall reading that all SCSI devices including 16-bit ones are compatible with the SCSI-1 standard, right? The Compaq drive is an 80-pin model with a 50-pin adapter.

I'm afraid this is not correct. A drive is compliant with the standard it claims to be compliant to in the data returned by the INQUIRY SCSI command and/or its manual. Most SCSI drives are compatible not with SCSI-1-CCS, but with SCSI-2 or newer. The device/driver firmware test suite, which you can run from within HDDRUTIL 13, or by running the separate test suite, displays all these data. The SCSI level is also displayed with "Device Information".
Whenever possible, one should prefer SCSI-2 (or newer) to SCSI-1-CCS. Some drives, e.g. by Fujitsu, support both, and you can select the SCSI level with a jumper. With device emulations like SCSI2Pi you can also configure the SCSI level. HDDRIVER and HDDRUTIL offer optimized functionality by using SCSI commands, if available, specified in SCSI standards newer than SCSI-2.

With the Atari, except for some SCSI-1-CCS models distributed by Atari themselves (Seagate ST157N, Syquest SQ555, Maxtor LXT with Atari's System V for the TT on it), SCSI-2 drives have been standard not only for TT and Falcon, but also for the ST, with the ICD Link and similar host adapters. Just like TT and Falcon, these adapters support any SCSI-level, i.e. also those newer than SCSI-2.

Obviously there is no general communication problem with this drive. But if you cannot run any function on the drive after selecting it in HDDRUTIL, the drive may (for whatever reason) report that it is not ready. Some drives require special jumper settings to spin up automatically, and as long as they have not yet spun up they only accept certain commands, e.g. INQUIRY, which besides other data returns the drive name.
The "Last Error" function in HDDRUTIL may display details, but running the test suite (latest version from the download area) is usually best in order to collect more information.

[uweseimet]

I have just tried a 16-bit bus SCSI drive that I sometimes use for testing. It's a Seagate Cheetah ST373307LC, an Ultra-320 SCSI-3 drive. It works fine with a TT and HDDRIVER 13, see screenshot. All HDDRUTIL functionality is available. As you can see, there currently is a Linux partition on it (drive K:).
The drive is connected to the internal SCSI port of the TT. SCSI2Pi is connected to the external port.

I could have made a fortune if I had received just one cent every time somebody claimed that a drive was not working with a TT or Falcon. It always turned out to be one of the typical SCSI issues: Wrong termination (with 16-bit drives the upper 8 bits, which are not used by the Atari, have to be terminated), usage of a Y-cable, a bad cable, simply a bent pin, or wrong jumper settings. TT and Falcon use a standard NCR SCSI controller, which also used by other computer models. There is no reason why this controller would work with other computers, but not with an Atari.
Often the users who reported a non-working drive were absolutely sure that everything was correct, and a few days later they found that they had been missing something.
I can't recall a single SCSI drive that didn't eventually work with HDDRIVER and a TT or Falcon. This also applies to SCSI device emulations like SCSI2Pi or BlueSCSI, where users sometimes misconfigure something and then claim problems with the Atari. Compared with physical SCSI drives, the hardware emulations are actually more complicated. The hardware is a regular SCSI device. Therefore, you have to follow the usual SCSI hardware rules. But additionally, you also have to ensure the correct emulation setup.