From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: DVD-cd usage
Date: Mon, 18 Jul 2005 20:36:44 +0000 (UTC) [thread overview]
Message-ID: <loom.20050718T222513-403@post.gmane.org> (raw)
In-Reply-To: 342e10905071812375a2d17d1@mail.gmail.com
Daniel da Veiga <danieldaveiga <at> gmail.com> writes:
> Ok, you're right, it really does burn cds.
Well googling produces lots of complaints about trouble. But
it looks mostly like old windows stuff...
> So, you're still not able to burn them? Try erasing an RW or writting
> an RW (so you don't spent cds). You should be able to do that with
> k3b, unless you already have mounted the cd (the erase and burn
> operations don't need the drive mounted) but I suppose that would echo
> an error.
I'm using a brand new rw cd. I tried copying 2 .wav files to the cd.
Here's the messages echoed to the K3b screen:
Using cdrecored 2.1
Starting dao writing at 24x speed...
Medium or burner do not support writing at 24x speed
Switching down burn speed to 4x
Starting in 2 seconds
Starting in 1 second
Writing canceled. <by James after 40 minutes>
Removing buffer files
Unlocking drive...
Could not unlock CD drive.
> You don't need anything special on your kernel to burn cds. At least I
> have nothing special on mine. K3b does it all for me.
OK, Maybe my use parameters are missing something?
emerge -Nvp k3b <reveals>
ebuild R ] app-cdr/k3b-0.11.24 +arts -debug +dvdr +encode +flac +kde
-kdeenablefinal +mad +oggvorbis -xinerama 0 kB
ideas?
James
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-18 20:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 17:11 [gentoo-user] DVD-cd usage James
2005-07-18 17:25 ` Daniel da Veiga
2005-07-18 18:57 ` [gentoo-user] " James
2005-07-18 19:37 ` Daniel da Veiga
2005-07-18 20:36 ` James [this message]
2005-07-18 21:09 ` Daniel da Veiga
2005-07-18 21:22 ` James
2005-07-18 21:22 ` Nick Rout
2005-07-18 22:01 ` James
2005-07-18 22:28 ` Nick Rout
2005-07-18 23:03 ` James
2005-07-18 23:32 ` Nick Rout
2005-07-18 23:54 ` James
2005-07-19 0:02 ` Nick Rout
2005-07-19 0:47 ` James
2005-07-19 1:25 ` Holly Bostick
2005-07-19 19:51 ` James
2005-07-19 20:44 ` Holly Bostick
2005-07-20 5:38 ` Rumen Yotov
2005-07-20 18:40 ` James
2005-07-21 4:25 ` Zac Medico
2005-07-21 16:38 ` James
2005-07-21 12:26 ` James Hiscock
2005-07-21 16:42 ` James
2005-07-21 17:40 ` Rumen Yotov
2005-07-19 0:07 ` James
2005-07-21 17:23 ` James
2005-07-21 17:38 ` Dave Nebinger
2005-07-22 17:50 ` James
2005-07-22 18:20 ` Dave Nebinger
2005-07-23 0:32 ` Bob Sanders
2005-07-21 17:58 ` Holly Bostick
2005-07-22 18:13 ` James
2005-07-23 6:13 ` Walter Dnes
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=loom.20050718T222513-403@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.org \
/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