![]() If you see any similarities in our situations, you might post back with the information to see if we can figure something out.īTW, I tried various BIOS settings for the parallel port, also. Run Device manager, open properties of your Iomega drive (it does not matter how it was detected, select Driver update, on the bottom of the page click on Install drivers manually, remove mark Show compatible devices, Select Iomega in left list, select your device in right list. Don't want to use write cache on a removable disk!) That's the only apparent difference between the driver as installed on her system and the driver as installed on my system. And in the meantime, the cursor won't move, and it's even damned difficult to get Task Manager to come up!!! When I looked in the driver properties I saw that the Write Cache enabled checkbox was grayed out. Now the Device Manager does list the drive, but it takes Explorer almost 4 minutes just to list the drive contents. On my friend's Dimension 4100 I installed the latest Iomega drivers (not the whole software install, just the drivers) freshly downloaded from the Web site. The Zip drive works faster under W2K than it did under Win98SE, which I used for about 6 months. I occasionally use a parallel port Zip drive with my Inspiron 7500 to give data to other people who use Zip drives. Unlike every other Windows 2000 Pro system I've seen, the system didn't give any indication of having recognized the Zip drive!Īll of the other W2K Pro systems I've seen were installed by me, NOT OEM images, and all of them recognized Zip drives immediately and used them correctly. After I completed the initial setup of the system, I powered down, added the parallel port Zip drive, and rebooted. Select No (you dont want Windows to try to detect your new hardware), and then click Next. In the Control Panel window, double-click Add New Hardware. She had saved her data to a bunch of Zip disks from her old system so that we could restore the data to the new one. Click the Start button and select either Control Panel, or Settings and then Control Panel. Besides a 7200 rpm 20 Meg Maxtor, the system has internal DVD-ROM and CD-ROM. The processor is an 800+ MHz Pentium III. It's got the OEM image (FAT32) of Windows 2000 Professional SP1 on it. I ran into an interesting phenomenon yesterday. What other drives do you have installed on this system? ![]() Which operating system are you using? If multi-boot, does the drive perform the same in all of those operating systems? Is this system running the same OS as the previous system on which the Zip drive worked better?ģ. Driver Navigator is continuing to try to get me to keep the software and is not wanting to refund my money, even though they state a 60 day 100 percent refund if not satisfied. Driver Navigator refunded my money immediately, without question. The higher capacity drives can read the smaller capacity disks (such as 100 MB) easily. ![]() Is this a Zip 100, Zip Plus, or Zip 250?Ģ. After subscribing to Driver Navigator and Driver Update, I learned this was not true. Almost any Zip drive with a USB connection will work, including the 100 MB, 250 MB, and 750 MB models. I deleted them from all of my ZIP disks and never backed them up.Could you provide more information, please? It might be helpful to know a few things, among them:ġ. Thanks to the OP for posting the archive of the tools. You don't *need* to install any of the Iomega tools to access the drive in Windows 95 (guest.exe is not required) as long as your SCSI drivers are working correctly. I had some issues with remnants of the old Windows 3.11 ASPI drivers hanging around after the Windows 95 upgrade that were causing the system to lockup. You can keep both if you use a startup menu to boot directly into DOS or games or whatever and want to access the drive. Windows 95: you will want to disable any 16-bit ASPI drivers in DOS and install the appropriate 32-bit ASPI drivers into Windows 95. To access the ZIP/Jaz/etc drive from DOS or Windows, you have to use guest.exe to assign it a drive letter (which you can put in your autoexec.bat). If you don't have those, you can try various Adaptec drivers, as many cards will work with those. My memory of the intricacies of ASPI had long faded away.ĭOS/Windows 3.x: you will need for ASPI drivers that hopefully came with your SCSI card. In an effort to keep this thread properly necro'ed, I wanted to answer the above as I have just gone through the process of getting an old SCSI ZIP100 working on a W311 machine that I "upgraded" to Windows 95.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |