Jim Adney
2003-12-11 03:27:48 UTC
I brought home a couple of old Zip 100 drives from work when they
upgraded everyone to Zip 250s. Since we all use Win 2k I figured it
would be easy to install in my Win2k PC at home and give me an easy
way to carry large files home.
I can't get it to work at home. The drive is recognized, and I've
assigned it the letter Z:, and it seems to work, but a few bootups
later it's still there, but it can no longer see disks that are in it.
Instead I get an error message that says, "Please insert a disk in
drive Z:" even though there is already a disk there.
Installing the latest version of Iomegaware gets me the special Zip
icon, but still won't read, plus even the Zip icon disappears the next
time I boot up. I did get it to read the very first time I booted, but
that changed on the next reboot.
I've tried 2 different drives, and I think the drives are both good.
I've taken both drives back to work and checked them there and they
work fine there.
The drives are labeled with instructions for jumpering them SIX
different ways: Master, Slave, CS, Master A, Slave A, and CS A. I
finally got an explanation from Iomega that A stands for A:, so you
can configure these to come up as your A: drive. I have them set up as
Slave, on an 80 conductor IDE cable with a Maxtor jumpered as Master.
The Maxtor continues to work just fine.
The hardware manager lists the driver for the Zip drive as disk.sys,
even after installing the Iomegaware.
Task Manager shows that Iomegaware is running a process called
imgicon.exe, and there is also a process called imgiconupdate.exe that
runs for just a few seconds after I log in.
The latest thing I did was to remove the IomegaWare and remove the
hardware driver (from its association with this drive.) On reboot it
recognized the drive again, installed disk.sys as the driver and the
drive worked fine. I rebooted 3 times and it continued to work fine. I
booted up tonight and I'm back to a Z: drive that shows up in
explorer, but doesn't know that there is a disk in it.
FWIW, the motherboard is a Gigabyte with a Via chipset. The Via
chipset drivers are installed.
Any suggestions as to what I've overlooked?
-
-----------------------------------------------
Jim Adney ***@vwtype3.org
Madison, WI 53711 USA
-----------------------------------------------
upgraded everyone to Zip 250s. Since we all use Win 2k I figured it
would be easy to install in my Win2k PC at home and give me an easy
way to carry large files home.
I can't get it to work at home. The drive is recognized, and I've
assigned it the letter Z:, and it seems to work, but a few bootups
later it's still there, but it can no longer see disks that are in it.
Instead I get an error message that says, "Please insert a disk in
drive Z:" even though there is already a disk there.
Installing the latest version of Iomegaware gets me the special Zip
icon, but still won't read, plus even the Zip icon disappears the next
time I boot up. I did get it to read the very first time I booted, but
that changed on the next reboot.
I've tried 2 different drives, and I think the drives are both good.
I've taken both drives back to work and checked them there and they
work fine there.
The drives are labeled with instructions for jumpering them SIX
different ways: Master, Slave, CS, Master A, Slave A, and CS A. I
finally got an explanation from Iomega that A stands for A:, so you
can configure these to come up as your A: drive. I have them set up as
Slave, on an 80 conductor IDE cable with a Maxtor jumpered as Master.
The Maxtor continues to work just fine.
The hardware manager lists the driver for the Zip drive as disk.sys,
even after installing the Iomegaware.
Task Manager shows that Iomegaware is running a process called
imgicon.exe, and there is also a process called imgiconupdate.exe that
runs for just a few seconds after I log in.
The latest thing I did was to remove the IomegaWare and remove the
hardware driver (from its association with this drive.) On reboot it
recognized the drive again, installed disk.sys as the driver and the
drive worked fine. I rebooted 3 times and it continued to work fine. I
booted up tonight and I'm back to a Z: drive that shows up in
explorer, but doesn't know that there is a disk in it.
FWIW, the motherboard is a Gigabyte with a Via chipset. The Via
chipset drivers are installed.
Any suggestions as to what I've overlooked?
-
-----------------------------------------------
Jim Adney ***@vwtype3.org
Madison, WI 53711 USA
-----------------------------------------------