Tweet
Internal Zip100 IDE Write Problem!!
During late February and early March, I recieved several hardware components that I had ordered from various vendors. Once my new system was put together, everything seemed fine. My new Marvel G400 was fried, however, so I am in the process of an RMA with that.
The new processor is an AMD Athlon Thunderbird 900Mhz, not overclocked or anything like that. The new motherboard is an EPoX 8KTA3, which has a VIA Apollo 133 chipset or something...
Now, my Zip100 Internal IDE (ATAPI) which I have had for two years now, and used to work flawlessly with my old 440BX Pentium 2 Chipset, does not like me to have it write data to Zip disks! I hadn't tried to use it since I installed my new motherboard until recently. A friend and I tried to troubleshoot it without any success. We tried updates, motherboard patches, Microsoft hotfixes, the works. Nothing we did to my computer made my Zip drive work. Has anyone had this problem before? Can anyone please help me!? AH! I am going to take a sledge hammer to the Zip drive since it is the only component that did not survive the upgrade. Unless I can make it work again.
The only clues I can provide are this:
When I went to device manager it said that everything was working properly. But my new chipset gave me a crapload of new devices and settings with options that were never avaiable to me before. I could edit whether or not my IDE 1 and 2 were using DMA or PIO. This is where I noticed the first discrepancy... Everything was in DMA mode with the exception of my Zip drive, which said "PIO Only". After all of that tweaking with my friend, somehow, now the Zip100 drive reads "DMA When Available", but still does not work!
These are the symptoms that my Zip drive gets:
I can read any zip disk's contents just fine. I can copy files from the zip disks, format them, anything to them. My Zip drive fails on me when I decide I want to write data to it... I drag something to the disk, and it starts to copy just fine, until the bar hits around 70%, regardless of the filesize and type, and then sits there for about 2 minutes, and then gives me the error that it could not copy the files or folders and that some of my data was lost, blah blah blah...
Any ideas? By the way, I am on Windows 2000 with SP1. Win2K rules!
The new processor is an AMD Athlon Thunderbird 900Mhz, not overclocked or anything like that. The new motherboard is an EPoX 8KTA3, which has a VIA Apollo 133 chipset or something...
Now, my Zip100 Internal IDE (ATAPI) which I have had for two years now, and used to work flawlessly with my old 440BX Pentium 2 Chipset, does not like me to have it write data to Zip disks! I hadn't tried to use it since I installed my new motherboard until recently. A friend and I tried to troubleshoot it without any success. We tried updates, motherboard patches, Microsoft hotfixes, the works. Nothing we did to my computer made my Zip drive work. Has anyone had this problem before? Can anyone please help me!? AH! I am going to take a sledge hammer to the Zip drive since it is the only component that did not survive the upgrade. Unless I can make it work again.
The only clues I can provide are this:
When I went to device manager it said that everything was working properly. But my new chipset gave me a crapload of new devices and settings with options that were never avaiable to me before. I could edit whether or not my IDE 1 and 2 were using DMA or PIO. This is where I noticed the first discrepancy... Everything was in DMA mode with the exception of my Zip drive, which said "PIO Only". After all of that tweaking with my friend, somehow, now the Zip100 drive reads "DMA When Available", but still does not work!
These are the symptoms that my Zip drive gets:
I can read any zip disk's contents just fine. I can copy files from the zip disks, format them, anything to them. My Zip drive fails on me when I decide I want to write data to it... I drag something to the disk, and it starts to copy just fine, until the bar hits around 70%, regardless of the filesize and type, and then sits there for about 2 minutes, and then gives me the error that it could not copy the files or folders and that some of my data was lost, blah blah blah...
Any ideas? By the way, I am on Windows 2000 with SP1. Win2K rules!
Comment