Discussion Locked

computer freezes when accessing Zip disk

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
IDE Zip on secondary cable with CDRW as slave or as master (I've tried both ways). Motherboard BIOS has been updated and new drivers from Iomega have been loaded for Zip. OS is Win Me. Processor is 800 MHz & computer has 64 MB RAM. If I try to format zip disk, computer freezes. If I try to copy large files, computer freezes. When the CDRW was removed, Zip apparently worked.

7 replies

by donmars

sounds like an IRQ conflict to me. Also assuming you have both drives on one cable? Place the master on the first connector from the motherboard connected end, the slave follows that. To check your IRQ setup go to control panel>system>device find the cdrw right mouse click it,(or is it double click?) goto properties, resources tab, note the IRQ. Do same for zip drive. You want to make sure they are not trying to use the same IRQ. You could also check under cmos setup(advanced) if IRQ steering is enabled, if it is then windows automatically assigns IRQs'Try disabling it if it is enabled and set IRQ yourself as above, or enable it if its not and reboot computer. remember to assign only free IRQs' or one that wont be used at the same time with another component.

by jwilczyn

It looks that your Zip drive doesn't work with CDRW. Try this - put the Zip drive as a slave on primary IDE controller (where you have your HD) and leave CDRW on secondary IDE controller. I don't think you have problem with IRQs, it's only hardware incompatible.
Good luck

by cascom

If the CDRW drive is a late model (24x8x4 or faster) you can slave it after the hard disk.
Make sure the hard disk is set to master and not in default setting.
Set the Zip drive to master using the jumpers on the back, and connect it to the secondary controller by itself.
Incompatibility is caused by the read mode of the CDRW drive being too fast for the Zip drive to acknowledge commands.
Had the same problem a couple of months ago with a client's PC.

This discussion is closed to new replies.