dlz@psuvm.bitnet.UUCP (10/29/87)
This is a posting for a friend:
I own a 1541 Commodore Disk Drive and I am having numerous problems.
First of all, when I try to read or write to disk I usually get random errors
(error 23). Most of the time this happens when the drive is writing the
high density tracks (1-17). I tried alignment at least 10 times in the past
week and I also tried speed adjustment (normal, faster (302 rpms), and slower
(298 rpms). The second problem is that the drive sometimes skips tracks.
For example, the one disk I formatted had track 3 where track 1 SHOULD have
been on the disk. When the drive tried to go to track 2 the head hit the
metal bar that prevents the head to go farther than track 0. I tried a
second write-timing chip (I don't remember the chip number), but still no
luck. Can anyone help??? I'm going to take it to a shop soon but I was
wondering if anyone can help. Thanks.
--------------------------
| BITNET: DLZ @ PSUVM |-------------
| UUCP: %s!psuvax1!psuvm.BITNET!dlz |
---------------------------------------
hedley@cbmvax.UUCP (10/31/87)
In article <23764DLZ@PSUVM> DLZ@PSUVM.BITNET (Mark C. Denchy) writes: >This is a posting for a friend: > > I own a 1541 Commodore Disk Drive and I am having numerous problems. >First of all, when I try to read or write to disk I usually get random errors >(error 23). Most of the time this happens when the drive is writing the >high density tracks (1-17). I tried alignment at least 10 times in the past >week and I also tried speed adjustment (normal, faster (302 rpms), and slower >(298 rpms). The second problem is that the drive sometimes skips tracks. >For example, the one disk I formatted had track 3 where track 1 SHOULD have >been on the disk. When the drive tried to go to track 2 the head hit the >metal bar that prevents the head to go farther than track 0. I tried a >second write-timing chip (I don't remember the chip number), but still no >luck. Can anyone help??? I'm going to take it to a shop soon but I was >wondering if anyone can help. Thanks. > Hate to debug long distance like this. Ok, we know the head is not where is should be, but the processor is running happily ( or seems to be ) so all that seems ok. Therefore, it might be the drive mechanism itself refusing to move properly, or the circuits which command the drive to move. Check there. Hedley