Hello folks. I am posting this topic so that others do not suffer as I did. Do any of you remember when I posted the topic "NOW ZIP DRIVE 250 NOT DETECTING PROPERLY"? or something along that line? That topic must have died because I can't find it anywhere.
Anyway, none of you could figure out what my problem is. Some of you just accused my Epox 8RDA+ board of being bad. But you guys are going to kick yourself after you hear this:
Here was my problem in the simplest terms:
"My Zip 250 drive basically does not read disks on my new system. System locks up in stages, and icons on computer as well as on disk take forever to execute when disk is inserted. System takes forever to boot with 250 connected. But when I take the Zip 100 drive off my old system and connect it to the new (in exactly the same way the 250 was hooked), it works fabulous! System boots fast as well. Then when I take the 250 drive and hook it on the old system, it seems to work fine! Problem: There is something rather queer pertaining solely to the compatability of the Zip Drive 250 and the New System!"
Someone pointed out to me at a computer shop that the Zip Drive 250 Jumper positions are different. I looked at the pictures on top of the 250 drive, and sure enough, the standard slave position is when there is NO JUMPER.
I assumed that that placing the jumper pin in the middle (as slave) would be exactly the same as a Zip Drive 100. How on earth would it even cross the my mind that they added the new Slave A setting?
Take a look at this:
Zip Drive 250 ATAPI User Manual
"The Iomega ZIP drive ATAPI added the function of booting from the ZIP drive if set to A: mode. Physically setting a ZIP ATAPI Insider drive in a desktop computer for drive A: mode involves setting a jumper on the configuration clock located on the rear of the drive."
"Note: The physical setup is required when the host BIOS is able to detect that the ZIP drive is drive A: capable, but
is unable to control the drive A: mode enable/disable feature in the drive's firmware.
Note: When booting into MS-DOS the guest DOS driver must be loaded into memory before the sound drivers; if not, the system will hang."
If you guys only knew how many headaches I've experience over this. I just hope that all of us learn from this. Do me a favor and permanently embed this into your heads--should some other uninformed individual as myself run into this.
So here is how it works:
Zip Drive 100:
: : : Master
: : : Slave
: : : Cable Select
Zip Drive 250:
(ZIP drive in standard configuration)
: : : Master
: : : Slave (NO JUMPER PIN!)
: : : Cable Select
(Zip drive set as A: )
: : : Master
: : : Slave
: : : Cable Select
So basically, I had my jumper pin set as Slave A: : : :
This would definitely cause some problems. But why did Win98SE on my old system detect this jumper setting on my Zip 250 just fine?
My only reasonable guess is that since Slave A is for booting in MS-DOS, MS-DOS is FAT16, and Win98 can read FAT16. That's why it didn't freeze up. But WinXP Pro is in NTFS, and trying to bootup from a disk in FAT16 mode would significantly cause problems and freeze!
So there you have it. What do you think about this?
Anyway, none of you could figure out what my problem is. Some of you just accused my Epox 8RDA+ board of being bad. But you guys are going to kick yourself after you hear this:
Here was my problem in the simplest terms:
"My Zip 250 drive basically does not read disks on my new system. System locks up in stages, and icons on computer as well as on disk take forever to execute when disk is inserted. System takes forever to boot with 250 connected. But when I take the Zip 100 drive off my old system and connect it to the new (in exactly the same way the 250 was hooked), it works fabulous! System boots fast as well. Then when I take the 250 drive and hook it on the old system, it seems to work fine! Problem: There is something rather queer pertaining solely to the compatability of the Zip Drive 250 and the New System!"
Someone pointed out to me at a computer shop that the Zip Drive 250 Jumper positions are different. I looked at the pictures on top of the 250 drive, and sure enough, the standard slave position is when there is NO JUMPER.
I assumed that that placing the jumper pin in the middle (as slave) would be exactly the same as a Zip Drive 100. How on earth would it even cross the my mind that they added the new Slave A setting?
Take a look at this:
Zip Drive 250 ATAPI User Manual
"The Iomega ZIP drive ATAPI added the function of booting from the ZIP drive if set to A: mode. Physically setting a ZIP ATAPI Insider drive in a desktop computer for drive A: mode involves setting a jumper on the configuration clock located on the rear of the drive."
"Note: The physical setup is required when the host BIOS is able to detect that the ZIP drive is drive A: capable, but
is unable to control the drive A: mode enable/disable feature in the drive's firmware.
Note: When booting into MS-DOS the guest DOS driver must be loaded into memory before the sound drivers; if not, the system will hang."
If you guys only knew how many headaches I've experience over this. I just hope that all of us learn from this. Do me a favor and permanently embed this into your heads--should some other uninformed individual as myself run into this.
So here is how it works:
Zip Drive 100:
: : : Master
: : : Slave
: : : Cable Select
Zip Drive 250:
(ZIP drive in standard configuration)
: : : Master
: : : Slave (NO JUMPER PIN!)
: : : Cable Select
(Zip drive set as A: )
: : : Master
: : : Slave
: : : Cable Select
So basically, I had my jumper pin set as Slave A: : : :
This would definitely cause some problems. But why did Win98SE on my old system detect this jumper setting on my Zip 250 just fine?
My only reasonable guess is that since Slave A is for booting in MS-DOS, MS-DOS is FAT16, and Win98 can read FAT16. That's why it didn't freeze up. But WinXP Pro is in NTFS, and trying to bootup from a disk in FAT16 mode would significantly cause problems and freeze!
So there you have it. What do you think about this?
Facebook
Twitter