public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: DervishD <raul@pleyades.net>
To: Margit Schubert-While <margitsw@t-online.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Slow writer...
Date: Wed, 2 Jul 2003 16:51:27 +0200	[thread overview]
Message-ID: <20030702145127.GB409@DervishD> (raw)
In-Reply-To: <5.1.0.14.2.20030702152720.00b01000@pop.t-online.de>

    Hi Margit :)

 * Margit Schubert-While <margitsw@t-online.de> dixit:
> http://www.cdrlabs.com/reviews/index.php?reviewid=185&page=Features
> It could be that "POWEREC" is biting you.

    Oh, I thought that the only thing that affected speed was the
VariRec (is that one that makes writing at 4x), and that must be
enabled explicitly. Thanks a lot, I will try to see if POWEREC is
giving me hell ;)) How can I get rid of POWEREC with cdrecord,
without needing to install the recorder on a WinDOS?

    BTW, the POWEREC issue makes sense, since the writer will stop at
20x/16x (depending on what's being written, data/audio), but I'm
afraid that the only solution is using better quality media
(currently I'm using Traxdata, 40x capable, and a Plextor disk that
is supposed to be capable of 48x, maybe Plextor gives low quality
sample disks ;)))?) or disabling POWEREC (Windows only Plextools, I'm
afraid...) and take the risk...

    Thanks a lot for pointing this :))

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/

  reply	other threads:[~2003-07-02 14:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02 13:50 Slow writer Margit Schubert-While
2003-07-02 14:51 ` DervishD [this message]
2003-07-02 22:31   ` DervishD
  -- strict thread matches above, loose matches on Subject: below --
2003-07-01 21:30 DervishD
2003-07-02 11:17 ` Jens Axboe
2003-07-02 14:12   ` DervishD

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=20030702145127.GB409@DervishD \
    --to=raul@pleyades.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=margitsw@t-online.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