From: Don <north_@www.7f.no-ip.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: r4 issues (one resolved! yay! one new)
Date: Tue, 30 Apr 2002 15:41:02 +0000 [thread overview]
Message-ID: <8f6cf824.0204300634.13b68fe2@posting.google.com> (raw)
In-Reply-To: <Zbuz8.13002$Q42.644924@typhoon.austin.rr.com>
> for cd speeds, 1x == 150kbyte/sec, and any other speed
> is a multiple of that. I imagine you meant write 12x/10x,
> read 32x, which translates to: write: 1.8MB/s / 1.5MB/s,
> read: 4.8 MB/s
Ahhh, now I get it. The cdwriter was overclocked so it was
probably wrapping around to an incredibly slow speed or
somethin. Now that I adjust the speed to the proper setting
(12 * 150) it writes with no errors what-so-ever. Nice.
Thanks for setting me straight, Casey.
Don
prev parent reply other threads:[~2002-04-30 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-30 9:42 [9fans] " Don
2002-04-30 10:27 ` [9fans] " Casey Webster
2002-04-30 15:41 ` Don [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=8f6cf824.0204300634.13b68fe2@posting.google.com \
--to=north_@www.7f.no-ip.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).