Liquidlen said:
Do a search at Microsoft for Zip errors, I am sure I read some issue a couple of years back that reminds me of your problem .Sorry I don't have time right now.
Are there any events logged when you have a failed read?
I found a few possibilities.....
1. This behavior occurs because removable media can be reported as malfunctioning if a cartridge is not present in the removable media device.
When the disk controller BIOS queries a removable media device, it stores the device status information in memory. At startup, Windows NT sends a query to determine the status of devices connected to the disk controller. Depending on the firmware installed, the BIOS revision, or the characteristics of the disk controller, removable media can be reported as malfunctioning if a cartridge is not present in the removable media device.
2. This problem occurs when the PATH statement in the Autoexec.bat file, Windows NT System Environment Variables, or User Environment Variables for <user name> refers to a floppy disk drive or CD-ROM drive.
If the Autoexec.bat file refers to a floppy disk or CD-ROM drive, Windows NT 4.0 does not display the error when you log on, but when you run applications.
3. When you use an Iomega Zip IDE Insider drive to re-partition and reformat a Zip cartridge using LBA mode, the cartridge will be unreadable from other SCSI, Parallel, IDE Zip drives (operating in non-LBA mode), or ATAPI Zip drives.
None of these seem to be it, although the closest reason may be the first one even though I'm running on XP Pro.