How do you fix a 1571?
Keith
<9JJh5.60902$3E6.6...@news1.alsv1.occa.home.com> wrote:
>I just got my C-128D in the mail, unfortunately I don't think the drive
>survived the trip. When I turn on the computer in 128 mode, the disk drive
>makes a loud knock, then the error light comes on and the drive stops. I
>was able to get it to read a directory only one time, now I just get File
>Not Found errors.
>
>Can anyone shed some light on how to fix this problem?
It probably has a bad head, try CMD they have a number of 1571
disk drive heads for a low price. http://www.cmdweb.com/
COMMODORE HUT
please check my other post to see what else I have for sale
CHUPY
"Jeff Hall" <jha...@home.com> wrote in message
news:9JJh5.60902$3E6.6...@news1.alsv1.occa.home.com...
> I just got my C-128D in the mail, unfortunately I don't think the drive
> survived the trip. When I turn on the computer in 128 mode, the disk
drive
> makes a loud knock, then the error light comes on and the drive stops. I
> was able to get it to read a directory only one time, now I just get File
> Not Found errors.
>
> Can anyone shed some light on how to fix this problem?
>
> Jeff
>
>
>
Hernan Vergara
On Wed, 2 Aug 2000, Jeff Hall wrote:
> I just got my C-128D in the mail, unfortunately I don't think the drive
> survived the trip. When I turn on the computer in 128 mode, the disk drive
> makes a loud knock, then the error light comes on and the drive stops. I
> was able to get it to read a directory only one time, now I just get File
> Not Found errors.
>
> Can anyone shed some light on how to fix this problem?
Did it come with that cardboard like disk inserted in the drive, or
just a regular disk or no disk at all in the drive?
If not, then you'll have to get one or make one. There was a program
that would draw the exact size to cut out a piece of thin carton.
What this does is to push the head al the way back, for
transportation.
Short of that, I guess you should open the machine and push the head
back yourself and see what happens? I think this is done so the
head can find track 18 from track 1 (outermost track in the disk)
Hope it helps.
Hernan
Jeff Hall
survived the trip. When I turn on the computer in 128 mode, the disk drive
makes a loud knock, then the error light comes on and the drive stops. I
was able to get it to read a directory only one time, now I just get File
Not Found errors.
Can anyone shed some light on how to fix this problem?
Thanks
Jeff
Christian Link
>It probably has a bad head, try CMD they have a number of 1571
>disk drive heads for a low price. http://www.cmdweb.com/
Ray Carlsen had some tips as of how to fix a broken drive head as
well. They're in his 1571 document (Heck, and I really am too lazy to
dig out the URL again; maybe Ray can jump in himself?). Depending on
the original poster's soldering skills, this may be worth a try. He
could contact CMD later, anyway...
Greetings,
Chris.
Jeff Hall
When I try to format a disk, the drive head "thingy" starts moving towards
the front of the drive as it writes each track. Just before it gets to the
half way point, the "thingy" runs out of room and can't move forward
anymore. This causes one of the springs below to trip, making a loud
knocking sound. The drive eventually gives up and reports a bad disk error.
The "thingy" stays butted up against the stop it ran into. So if I try to
format the disk again, it fails right away.
So, the problem seems to be two things:
1. The "thingy" is running out of room to move forward
2. The "thingy" is not able to retract.
Ok, so there is my hi-tech analysis!
Jeff
"COMMODORE HUT" <COMMOD...@HOTMAIL.COM> wrote in message
news:soetd6...@corp.supernews.com...
> if you do need a replacement drive i have 1 for $25.00
> please check my other post to see what else I have for sale
> CHUPY
> "Jeff Hall" <jha...@home.com> wrote in message
> news:9JJh5.60902$3E6.6...@news1.alsv1.occa.home.com...
Christian Link
>1. The "thingy" is running out of room to move forward
>2. The "thingy" is not able to retract.
Erm, am I the only one getting dirty thoughts at reading this? E.g.,
if it would be possible circumsizing a bumper or the whole drive head
;-))) ?
Ooops, excuse me, it's early in the morning already and I certainly
need some sleep, I guess ;-) ...
Greetings,
Chris.
Nicolas Welte
> So, the problem seems to be two things:
> 2. The "thingy" is not able to retract.
>
Sounds like a dirty track 0 sensor. That is another thingy which can detect
if your thingy already moved back into its home position. Since your thingy
does not move back at all, there probably is dirt in the sensor thingy so
it thinks the head thingy already has returned home.
Nicolas
Jeff Hall
Seriously, should I just run a cleaning disk through it?
Jeff
"Nicolas Welte" <we...@chemie.uni-konstanz.de> wrote in message
news:3987E363...@chemie.uni-konstanz.de...
Jeff Hall
how to properly do this?
Jeff
"Hernan Vergara" <hver...@accessnv.com> wrote in message
news:Pine.BSI.3.95.100080...@coyote.accessnv.com...
> Hi Jeff,
>
>
> On Wed, 2 Aug 2000, Jeff Hall wrote:
>
> > I just got my C-128D in the mail, unfortunately I don't think the drive
> > survived the trip. When I turn on the computer in 128 mode, the disk
drive
> > makes a loud knock, then the error light comes on and the drive stops.
I
> > was able to get it to read a directory only one time, now I just get
File
> > Not Found errors.
> >
> > Can anyone shed some light on how to fix this problem?
>
Jeff Hall
was shipped.
Nicolas Welte
>
> Ok so how do I clean my thingy's head sensor? hehe this is too funny now.
>
> Seriously, should I just run a cleaning disk through it?
Yes, seriously: Blow your thingy's head sensor to get dust out, if that
doesn't help, and the previous owner was a heavy smoker, you might have to
put some solvent (ethanol or isopropanol) onto a small cloth and clean its
slit. This thingy is a small black device that has a small slit in the
middle (*giggle*) and three wires running to it. Your head thingy has a
plastic tab attached to it, that will insert into the slit when moving back
;-) You should find it quite easily, good luck.
Ah, after all this talk I will visit girls.c64.org for a while to find
relief.
Nicolas
Daniel Morrow
taking the computer apart and if you want to use another device as device 8 and
don't want to waste a device number. If you don't mind wasting a device number
check out ftp://ftp.funet.fi/ and look for a file talking about changing the
device number (the c64 version probably has the 128dcr specific information as
well, make sure to check for it all throughout the file - it is probably at the
bottom from what I remember) and use that information to change the device
number to 11 or something. You only have to cut a trace or two between two
small jumper pads with a knife/razor blade or something. The other option if
you can't fix the internal drive is to use similar (found in the same file?)
information from funet to cut pin one of one chip under the internal drive, I
found it a little cramped of a space to do that in myself but you might be able
to insert wire cutters through a hole in the case (that is already there of
course) and clip it from there. I did all of this with mine and even did some
light soldering to add switches to all of these conductors even though I didn't
need to (my 128dcr's internal drive still works fine but I want to be prepared
for the day it doesn't) and it works great. Good luck and later!
COMMODORE HUT
try to format in both
have you tried several different disks in the drive
sometimes the software written on one drive will not load on another drive
due to one or the other being out of alignment sometimes bothnews:twWh5.62598$3E6.6...@news1.alsv1.occa.home.com...
chupy
I prefer this method over cutting
"Daniel Morrow" <vide...@cdsnet.net> wrote in message
news:398895A3...@cdsnet.net...
Jeff Hall
with diskette cleaning solution. This did not help.
I physically push the R/W head back as far as it will go. Each time I
REBOOT the computer, the R/W head moves forward (it makes the familiar
pattern of boot sounds the first time). On each successive boot, the drive
attempts to perform the same series of movements, but this time, it starts
from the last position it was in, and hits the end of the line.
So, I can't figure out what is causing the R/W to fail to retract.
Any ideas?
"Nicolas Welte" <we...@chemie.uni-konstanz.de> wrote in message
news:398839C4...@chemie.uni-konstanz.de...
Nicolas Welte
>
> I cleaned the top and bottom parts of the R/W head with a cotton swap coated
> with diskette cleaning solution. This did not help.
>
> I physically push the R/W head back as far as it will go. Each time I
> REBOOT the computer, the R/W head moves forward (it makes the familiar
> pattern of boot sounds the first time). On each successive boot, the drive
> attempts to perform the same series of movements, but this time, it starts
> from the last position it was in, and hits the end of the line.
I didn't say the R/W head has to be cleaned. There is an optical sensor
that is able to see if the head is in track 0 position, which it sees
because the plastic tab which is attached to the R/W head assembly blocks
the light path. If dirt is in there, the light is always blocked and
therefore the drive will always think it already arrived on track 0 and
therefore it will never move into that direction.
Try to find that sensor, it's easy to spot if you look at the R/W head and
watch it where it goes if you push it back.
Nicolas
Nicolas Welte
> Try to find that sensor, it's easy to spot if you look at the R/W head and
> watch it where it goes if you push it back.
I forgot: NEVER EVER move the R/W head manually if the drive is powered on!
The 1571 keeps the stepper drive energized all the time to keep the head in
position, very unlike the 1541. Moving the head in this situation can give
cause to misalignment.
Nicolas
Bruno Serra
> was shipped.
That's good.
From my experience, I would say that when something goes wrong with a
1541/1571 drive and before starting reading Ray Carlsen's repair guide or
opening the drive juste start using a cleaner disk with a little of water (use
ethanol or everything else later) and the appropriate routine to clean the
drive R/W head. If it doesn't help then use a disk alignement program
(loaded from another drive of course) with an original working disk. Run
the program twice or more if need be. If it still doesn't work then open
the drive and try eveything Nicolas Welte or Ray Carlsen will tell.
Good luck,
Bruno.
Daniel Morrow
chupy wrote:
> you can also bend up 1 leg on a chip if you do not want to cut the pc board
> I prefer this method over cutting
>
Good point ;-). I had forgotten about that yet other option. Good luck and
later!
Raymond Carlsen
> coated with diskette cleaning solution. This did not help. I physically
> push the R/W head back as far as it will go. Each time I REBOOT the
> computer, the R/W head moves forward (it makes the familiar pattern of
> boot sounds the first time). On each successive boot, the drive
> attempts to perform the same series of movements, but this time, it
> starts from the last position it was in, and hits the end of the line.
Jeff,
As Nicolas mentioned, try cleaning the track zero sensor. It's located
at the rear of the drive. It's a black plastic block with three wires going
to it. When the head moves back during an Initialize or Format, a small
black plastic tab moves between the two halves of the sensor and blocks the
IR light path. Dust in the sensor area can fool the drive into thinking it
is already at track zero, so it steps forward all the time. Try compressed
air to blow the dust out of your drive. There are several other sensors
that may need cleaning. Get back to me with the results. Check out my 1571
repair article for more information. You will be the first to see my very
first attempt at creating a website. It's as close to generic as I can make
it, so anyone should be able to read it: http://landru.myhome.net/rcarlsen
Ray Carlsen CET
Carlsen Electronics
Steve Douglas
1. You have an electrical "looseness" somewhere.
Solution: unconnect and reconnect every connector. Re-seat every chip.
2 The drive is physically busted.
Solution: repair or replace the busted parts (sorry can't help).
3. The drive is physically "confused".
Solution: try formatting a disk (or anything which knocks the head). Try
re-aligning the drive if that don't cure the problem.
If none of that works assume #2, and good luck.
Steve
Steve Douglas
most likely cause (and yes it is not in my list). So I'll shut up now....
Steve