Path: utzoo!mnetor!uunet!mcrware!jejones
From: jejones@mcrware.UUCP (James Jones)
Newsgroups: comp.sys.m6809
Subject: Re: still more data re disk I/O
Message-ID: <596@mcrware.UUCP>
Date: 19 Jan 88 12:20:37 GMT
References: <593@mcrware.UUCP> <594@mcrware.UUCP>
Organization: Microware Systems Corp., Des Moines, Ia.
Lines: 26
Keywords: floppy disk throughput
Summary: write verification verified

Taking the bit between my teeth, the bull by the horns, the nail by the head,
and so forth, but most importantly loading up the "dmode" utility from CIS
(an RBF equivalent of "xmode") to make it easy to do, I formatted a fresh
disk, turned verify off, and tried the by now very familiar program.

Results, with the program set to do an SS_SSIZ setstat: it took 24
seconds to write the file and 18 seconds to read.  (Why 18 instead of
14? I don't know; it may have had something to do with precisely where
things happened to fall on the disk.  With dmode it will be easy to turn
verify off and then back on, so I can run the program on the very same
floppy I used the other day.  No, I won't post another message when I
do. :-)

So--hypothesis verified.  (Recall that with verify on, it took 1:44 to
write the file, a tad over four times as long.)

The next question, which I don't know the answers to (so I'll shut up
after asking them), is: in practice, how dangerous is it to run with
verify turned off?

		James Jones

(The above, as far as I can tell, doesn't contain any opinions, so how
can they be the opinions of anybody or any organization? Also, if I
strike you as highly ignorant of floppy disk operation, keep in mind
that I'm a software person.  :-)