From: Gene Heskett <gene.heskett@gmail.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Phillip Susi <psusi@cfl.rr.com>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: floppy question of the hour
Date: Wed, 28 May 2008 17:46:30 -0400 [thread overview]
Message-ID: <200805281746.30925.gene.heskett@gmail.com> (raw)
In-Reply-To: <20080528134257.GA16164@csclub.uwaterloo.ca>
On Wednesday 28 May 2008, Lennart Sorensen wrote:
>On Tue, May 27, 2008 at 05:49:18PM -0400, Phillip Susi wrote:
>> Yes, the interleave slows you down, since after accessing sector 1, the
>> head must wait to pass over 3 other sectors before finally reaching
>> sector 2, therefore, you can only read 1/4 of the sectors on the track
>> each revolution of the disk. That leaves 4 revolutions at 300 rpm
>> giving 0.8s to read a track, or 64 seconds to read all 80 tracks, plus
>> seek time. That still does not explain 3 minutes though... not sure
>> what else could be slowing you down.
>
>Just do what the Amiga did: Read the entire track into a buffer in
>memory, then deal with the sectors, and write the entire track back. :)
That would be a huge improvement, but I'm afraid it would need someone far more
familiar with floppy.c than I.
I am beginning to figure out how to make it work though. The sequence goes
something like this:
1. insert disk in drive, wait 5 minutes just in case, didn't help.
2. setfdprm /dev/fd0 COCO7203.5
3. getfdprm /dev/fd0 (fails, no such device)
4. dd if=/dev/fd0 bs=256 count=1
5. wait 20 to 40 secs for it to fail with an i/o error
6. setfdprm /dev/fd0 COCO7203.5
7. getfdprm /dev/fd0
DS DD sect=18 ssize=256
8. dd if=disk.image of=/dev/fd0 bs=256
then about 4 minutes later:
9. dd if=dev/fd0 of=test.dsk;cmp disk.image test.dsk
Eof "disk.image" (its shorter than the 720k disk itself)
3 more minutes for step 9 and I know if I have a good write. You can do the
setfdprm 100 times and it fails silently everytime, but attack it with dd once,
and /dev/fd0 gets well and works. 4 or 5 years ago it all worked straight off
with the tools we had then.
FWIW, kernel is now 2.6.26-rc4, stable so far with a 49 hour uptime.
Hell of a way to run a train, guys, really. :)
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Ambidextrous, adj.:
Able to pick with equal skill a right-hand pocket or a left.
-- Ambrose Bierce, "The Devil's Dictionary"
prev parent reply other threads:[~2008-05-28 21:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-24 1:14 Gene Heskett
2008-05-24 9:28 ` Stefan Richter
2008-05-24 12:52 ` Gene Heskett
2008-05-27 21:49 ` Phillip Susi
2008-05-27 22:26 ` Gene Heskett
2008-06-01 19:00 ` Jan Engelhardt
2008-06-02 0:50 ` Gene Heskett
2008-06-02 10:28 ` Kay Sievers
2008-05-28 13:42 ` Lennart Sorensen
2008-05-28 19:38 ` Phillip Susi
2008-05-28 19:59 ` Lennart Sorensen
2008-05-28 21:58 ` Gene Heskett
2008-05-28 21:50 ` Gene Heskett
2008-05-28 21:46 ` Gene Heskett [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200805281746.30925.gene.heskett@gmail.com \
--to=gene.heskett@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=psusi@cfl.rr.com \
--cc=stefanr@s5r6.in-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®