I have been having problems installing Iomega Zip 100 drives in Windows NT 4 Workstation. I work in a school district in which the administration hard drives are all partitioned into 3 drives C: E: when the drive is installed it re-letters the drives and leaves the zip drive un re letterable... I have gotten the drive lettered one time only and had to resort to ghosting this particular user's machine.
This conversation is currently closed to new comments.
download from the iomega website the correct drivers for WinNT, and then got to Disk Admin/tools/assign drive letter. If the drive is not being lettered uninstall the software from Iomega, and reboot the PC and install again. Make sure that you are administrator when isntalling the software.
I tried using Disk Administrator. The problem is when you install the drive, it automatically becomes drive and reletters the pre existing d: and e: therefore when I install the zip software, it installs it on then after rebooting the drive is recognizes and becomes therefore making the software I just installed prior to reboot inacessable. This leads to about 100 error messages and freezups.... someone has had to have had this same problem!
I had the same problem. Boot the computer up with a Zip disk in it. When NT come up it will recognize there is media in the drive. Once this is done you can go to Admin Tools and Disk Manager and Assign it a drive letter of your choice. If the driveletter are mixed up assign a drive with a high letter then apply changes until you get them the way you want.
If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.
Problem with zip 100 drives in Windows N
and leaves the zip drive un re letterable... I have gotten the drive lettered one time only and had to resort to ghosting this particular user's machine.