dueker@xenon.arc.nasa.gov (The Code Slinger) (04/16/91)
I have two floppy drives on my A1000 (1 int, 1 ext), and lately, I've
had a couple of disks that will work fine on one drive, but will give
a READ/WRITE error system requester when files are accessed on certain
tracks.
It would appear that one of the drives has gone out of alignment. If
that is true (anybody else with an educated guess?), how would I go
about determining which drive is/has gone bad? Other than taking two
disks to another Amiga and see which disk barfs on that one?
Thanks muchly,
Chris
------------------------------------------------------------------------
"Ah, Benson, you are so mercifully free of the ravages of intellegence!"
"Oh, thank you, Master!" - from the movie, TIME BANDITS
------------------------------------------------------------------------
dueker@xenon.arc.nasa.gov | Chris Dueker (The Code Slinger)
duke@well.sf.ca.us | Mtn. View, CA (Sillycon Valley!)cac5961@rouge.usl.edu (Castor Christian A) (04/18/91)
In article <1991Apr16.152150.2478@nas.nasa.gov> dueker@xenon.arc.nasa.gov writes: >I have two floppy drives on my A1000 (1 int, 1 ext), and lately, I've >had a couple of disks that will work fine on one drive, but will give >a READ/WRITE error system requester when files are accessed on certain >tracks. > >It would appear that one of the drives has gone out of alignment. If >that is true (anybody else with an educated guess?), how would I go >about determining which drive is/has gone bad? Other than taking two >disks to another Amiga and see which disk barfs on that one? My dual drive A2000 exhibited similar symptoms recently. I noticed that sometimes when booting up, a requestor would pop up saying that the "disk had a read/write error". Additionally, I was unable to use the MessyDOS, the transformer, and several heavy-protected software when using this particular drive (DF0:). If I used DF1: everything would run smoothly. I disassembled DF0: and found the problem. There was some lint at the end of the read/write head's stepping motor shaft. The lint would prevent the read/write head to fully align with track 0. Carefully, I removed all of the lint, and reassembled the drive. It has been working flawlessly ever since. > >Thanks muchly, > Chris >------------------------------------------------------------------------ >"Ah, Benson, you are so mercifully free of the ravages of intellegence!" >"Oh, thank you, Master!" - from the movie, TIME BANDITS >------------------------------------------------------------------------ >dueker@xenon.arc.nasa.gov | Chris Dueker (The Code Slinger) >duke@well.sf.ca.us | Mtn. View, CA (Sillycon Valley!) - chris c -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Christian Castor - cac5961@usl.edu or chris@usl.edu - CIS: 73030,2734 Plink: ChrisC - (318)232-2045 - Snail: PO Box 43402,Lafayette LA 70504 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-