1. Forum
  2. Usenet
  3. COMP.SYS.IBM.PS2.HARDWARE

  • Adaptect AHA-1640 @0000.adf error

    From [email protected]@21:1/5 to All on Tue Jul 11 21:08:24 2023
    Does anyone know how the Adaptec AHA-1640 cards die with the @0000.adf error? I noticed one of the resistor packs had a crack in it, so I replaced it with no luck. Looking for other ideas. I've seen it mentioned before around the internet, here and
    on the Facebook group... but can't seem to find any decent discussion about it.

    I've posted here and on Facebook. Any help would be greatly appreciated.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From IBMMuseum@21:1/5 to All on Tue Jul 11 22:29:55 2023
    Does anyone know how the Adaptec AHA-1640 cards die with the @0000.adf error?

    The Adaptec AHA-1640 uses a C&T 82C612 MCA interface chip - there is a link to the datasheet for the 82C611/82C612 on the AHA-1640 page. POS ID is set external to the chip, with two examples shown in the datasheet. We need to determine how that is
    implemented on the AHA-1640 (and a handful of other adapters that use the 82C612):

    Logitech ScanMan Adapter, ID 6DACh
    National Instruments MC-MIO-16, ID 5EDFh
    Creative Labs Soundblaster MCV (non-Pro), ID 5084h

    Several other adapters have a C&T marking on a PLCC-68 package, but I don't know if those would be the 82C611 or 82C612 (but both do the POS ID in the same/similar way)...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From IBMMuseum@21:1/5 to All on Thu Jul 13 10:22:08 2023
    Does anyone know how the Adaptec AHA-1640 cards die with the @0000.adf error?

    I'm actually thinking that the "Device not ready" logic as shown on Page 15 physical is getting confused - More study of this mechanism is needed.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From richard smice@21:1/5 to IBMMuseum on Thu Jul 13 12:39:46 2023
    On Thursday, July 13, 2023 at 1:22:09 PM UTC-4, IBMMuseum wrote:
    Does anyone know how the Adaptec AHA-1640 cards die with the @0000.adf error?
    I'm actually thinking that the "Device not ready" logic as shown on Page 15 physical is getting confused - More study of this mechanism is needed.


    I have had Future domain cards fail in a similar fashion...... I inserted reprogrammed e-proms in and every thing played fine...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Louis Ohland@21:1/5 to richard smice on Thu Jul 13 17:12:20 2023
    Interesting. POSIDs are implemented with logic gates or something
    SIMMple and fast. No need to query an EPROM.

    richard smice wrote:
    On Thursday, July 13, 2023 at 1:22:09 PM UTC-4, IBMMuseum wrote:
    Does anyone know how the Adaptec AHA-1640 cards die with the @0000.adf error?
    I'm actually thinking that the "Device not ready" logic as shown on Page 15 physical is getting confused - More study of this mechanism is needed.


    I have had Future domain cards fail in a similar fashion...... I inserted reprogrammed e-proms in and every thing played fine...


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From IBMMuseum@21:1/5 to All on Thu Jul 13 17:10:27 2023
    I have had Future domain cards fail in a similar fashion...... I
    inserted reprogrammed e-proms in and every thing played fine...

    The Future Domain SCSI adapters don't use the 82C611/82C612 chipset, which has an external mechanism for passing the POD ID of the adapter (several adapters use these microchannel interface chips) and have a "Device not ready" ('0000') mechanism for the
    system if the adapter fails. The error is repeatable with the Adaptec AHA-1640 implementation; Lionel and I each have one adapter affected this way.

    The ROM of the Future Domain SCSI adapters is to boot from an attached hard drive; They can be used ROM-less with a SCSI CD-ROM, for instance. The AHA-1640, on the other hand, has a ROM BIOS extension ('U6'), microcode ROM ('U5'), and three socketed PALs.
    It i unknown right now where the POS ID logic is on the AHA-1640 adapter, or how it is implemented. All socketed chips (ROMs and PALs) on the AHA-1640 are required.

    Once I have an opportunity, I'm going to start switching PALs from a known-good AHA-1640, and also might try the microcode ROM (POS ID logic likely won't be in the ROM BIOS extension chip)...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)