DAT24i: Invalid EEPROM log

[Uwe Maas]

I have an internal DAT24i drive (C1537A), I would like to get it running under XP Pro.

Unfortunately, neither NTBackup nor HP L&TT can 'see' the drive! From NTBackup you can find an error message in the system log from the change media service stating, that it cannot connect to library tape0, because communication with the device or the determination of device installation information failed.

It gets even weirder: As soon as I started HP LTT, the tape drive is removed from device manager. In the system log you find an error message of the PlugPlayManager, which says, that the tape drive was removed from the system unexpectedly.

At the next startup the tape drive shows up in device manager again.

This computer is a dual boot computer with Win98. In Win98 the DAT24i is working fine! Also HP LTT recognizes the drive, and I can run diagnostics.

The device analysis of LTT states:

Device Analysis for DDS Drives
Rules_DDS001.xml
Product ID is 'C1537A'
Invalid EEPROM log
Serial EEPROM Data is not accessible on this drive
Your drive logs do not indicate that there are any serious problems with your drive

Now comes the tricky part:

Can it be, that XP is more "sensitive" than Win98? As a result, the invalid EEPROM log prompts XP to disable access to the tape drive, while it is working fine under Win98!

And since I use the standard XP-driver (4mmdat.sys) for the tape drive, HP LTT cannot access it either!

If this is the case: What can I do to get a valid EEPROM log, and access to the Serial EEPROM Data?

Many thanks in advance,

Uwe

[Eugeny Brychkov]

Uwe,
if you have support contract/warranty on this DAT24 device then call HP. If not then try to reflash it/upgrade firmware using LTT under win98
Eugeny

[Uwe Maas]

I now cleaned the drive 5 times in a row, and flashed the latest firmware revision (L111) three times: It is still not working under XP, as before.

What I do not understand: How can Win98 work with the drive, if the "Serial EEPROM Data is not accessible on this drive"? And: How is it possible to flash the latest firmware, and then the EEPROM Data is not accessible?

Assume, that I will need to call HP on this one.

Uwe