I recently installed an internal Iomega IDE zip drive. Currently, it is configured as the slave on the primary IDE. When I go to start Windows, I get an inacessable boot device error...sometimes. Other times when i start up, win 2k chugs along like nothing is wrong and the drive functions just fine. The device manager says that the device is working properly and I ran Iomega Ware for win2K. Help!!

Hi, your zip drive should not be considered as a hard disk in yor computer. So, make your hd single drive. that should take care of the problem.

I'm not quite sure what Lipu is trying to tell you. When it chugs along just fine, is there a Zip cartridge in the drive? It shouldn't matter, but you could try putting the Zip on the Secondary IDE channel. Why did you install IomegaWare. There are know issues with IomegaWare. Windows 2000 will recognize the drive just fine without any additional drivers, but you won't have the built in backup capability--that doesn't work in Windows 2000 anyway. All the systems I build have a Zip drive and I don't install any additional drivers or software from Iomega. I don't have too and I'm reducing my risk of a blue screen--saw too many in NT 4.0 from the IomegaWare.

when I installed my Iomega zip drive for win2k, it says I am missing the file IMGHOOK.dll in a lot of areas any ideas as to why? it worked before..

Tracy, yes I saw that too after someone on Iomega Tech Support (would you believe it?) asked me to downoad and install IomegaTools on Win2K. I have now uninstalled the tools and am using the built-in Win2K driver, which works fine. No more IMGHOOK.DLL errors.