[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Write Signal on Disk II Question
- Subject: Re: Write Signal on Disk II Question
- From: "Charlie" <charlieDOTd@verEYEzon.net>
- Date: Mon, 12 Nov 2007 18:11:30 GMT
- Newsgroups: comp.sys.apple2
- References: <473500c1$0$32532$4c368faf@roadrunner.com><nf9Zi.38$OJ.0@trndny06> <5RhZi.60$Vp3.32@trnddc05> <4735d085$0$8807$4c368faf@roadrunner.com> <rjnZi.1348$VB6.450@trnddc06> <47364055$0$32548$4c368faf@roadrunner.com> <DvuZi.1791$jH2.405@trnddc01> <47368074$0$20642$4c368faf@roadrunner.com> <1194817188.506052.311720@19g2000hsx.googlegroups.com> <47384a9c$0$4374$9b4e6d93@newsspool4.arcor-online.net>
- Xref: g2news1.google.com comp.sys.apple2:30431
"Linards Ticmanis" <ticmanis@gmx.de> wrote in message
news:47384a9c$0$4374$9b4e6d93@newsspool4.arcor-online.net...
> ferdimh@gmx.de wrote:
>
>> Using a '74 one can reencode the signal read from disk and write it to
>> another disk at the same time. Then you only need to step over the
>> tracks while reading and you shold have a working copy (maybe you'll
>> need some circuitry to avoid writing during the seek).
>
> A good idea, however it won't work if you start/end the writing in the
> middle of a sector. The rotation speed is not constant enough to "hit"
> the exact same bit the next time around. So you will need to start/end
> the write in a gap. This means you have to detect gaps. Also, nibble
> counts won't be exact without taking extra measures. So the idea of
> doing this entirely "dumb" is probably not workable.
It might work if both disks were driven by the same motor. Of course that
would be a major mechanical hack.
Charlie