AFAICT, the GEM drivers are just "null installs", so I'm wondering whether you need a driver at all ???
GEM drivers:
ftp://ftp.supermicro.com/driver/SCSI_Backplanes/Qlogic/Readme file for driver installation under Windows:
ftp://ftp.supermicro.com/driver/SCSI_Ba ... Readme.txtQuote:
This is the Windows dummy driver to remove the yellow question mark(s) under Device Manager.
This diskette contains the QLogic GEM318/GEM354/GEM359 driver for the SCA backplane controller.
INF file for driver installation under Win 2K:
ftp://ftp.supermicro.com/driver/SCSI_Ba ... GEM318.infHere are the datasheets for the GEM controllers:
GEM318, QLogic, Guardian Enclosure Management Controller:
http://www.ic72.com/pdf_file/g/105312.pdfGEM359, QLogic, Guardian Enclosure Management Controller:
http://www.ic72.com/pdf_file/g/105312.pdfI confess that I am unfamiliar with SCSI enclosures, so I had to do a bit of reading:
http://ask.adaptec.com/app/answers/deta ... closure%3FQuote:
SAF-TE (SCSI Accessed Fault-Tolerant Enclosures) and SES (SCSI Enclosure Services) are two industry standards for reporting on devices and environmental status of external disk array cabinets. SAF-TE is a hardware interface specification developed jointly by nStor Corp. and Intel Corp. SES is an ANSI standard (NCITS.305:1998) that defines how the enclosure status information is communicated across a SCSI protocol bus. SAF-TE is based on the command protocol defined by the SES standard, but allows for additional vendor specific applications. Both of these protocols provide for real-time monitoring and event management for disk array systems.
http://www.safte.org/Quote:
The SAF-TE processor presents itself to your host operating system as a SCSI processor device (type=3), which is typically assignable as a user-defined SCSI target ID. Management is in-band, over the SCSI interface.
The GEM318 processor supports the following command sets, whereas the GEM359 provides additional support for SES commands. These appear to be standard commands, so I'm wondering whether you could make do with a generic monitoring utility ???
Quote:
SCSI Command Set
The following SCSI commands are supported:
Inquiry
Read Buffer
Write Buffer
Test Unit Ready
Request Sense
Send Diagnostic
Quote:
SAF-TE Command Set
The following SAF-TE commands are supported:
Read Enclosure Configuration
Read Enclosure Status
Read Device Slot Status
Write Device Slot Status
Perform Slot Operation
Send Global Flags
Read Global Flags
FWIW, here is a commercial tool (SMARTMonUX) for monitoring enclosures:
http://www.santools.com/smart/unix/manual/As for identifying the actual processor chip, I doubt that you could do it from within Windows. Normally you would query the device using the SCSI Inquiry command. The reported Inquiry data would include vendor ID, enclosure ID, and product ID. A generic enclosure would report the IDs of the processor chip, whereas a custom enclosure would report the IDs of the OEM. These "vendor-defined inquiry data" are programmed into an "external NVRAM device", eg 24C01A.
FAQ
Search
Login
Register
HDDGURU FILES
For example, I downloaded the file "HDD-Modular.rar" (containing info for the CAGE 8721) but this is not ... there is no backup! 
Hello everyone, after many months from my last message and many vicissitudes with my computer I get to talk about my problem with the SCSI CAGE ENLIGHT 8721.