On Thursday 16 March 2006 8:25 pm, Ben wrote: > On Thursday 16 March 2006 06:10 pm, Rosemary McGillicuddy Climbed A > Telegraph > > Pole and Clicked: > > JoeHill wrote: > > > On Wed, 15 Mar 2006 13:19:37 +1300 > > > > > > Rosemary McGillicuddy got an infinite number of monkeys to type out: > > >> k3b: WARNING: KGenericFactory: instance requested but no instance > > >> name or about data passed to the constructor > > > > > > Plug that *exact* error message into here: > > > > > > http://www.google.ca/linux > > > > > > :-) > > > > Thanks, I did that and obviously people have had the same error. It > > hasn't helped me solve it. I used to be able to use k3b as user to > > copy cds and now I can't. I hadn't try to burn isos until lately, but > > I can't do that either - get "unknown error 254". Thanks anyway > > I have always found it easiest to use cdrecord for burning .iso's > cdrecord dev=/dev/hdd Mandriva-Linux-Free-2006-CD1.x86_64.iso > works very well for me. > of course your cdrom may not be hdd > Hope this helps. > benja22
I had to go back a few years in the archives, but here are some CL aliases
you can place in your /etc/.bashrc:
> alias bdcd='cdrecord -v -eject driveropts=burnfree speed=24 dev=1,0,0
> -data'
>
> alias bacd='cdrecord -v -eject driveropts=burnfree speed=24 dev=1,0,0
> -pad -audio *.wav'
>
> alias biso='cdrecord -v -eject driveropts=burnfree speed=16 dev=1,0,0
> -dao'
>
> alias mkcdimg='mkisofs -r -o cd_image'
>
> alias ripacd='cdparanoia -vB 1- /home/<user>/wav/'
>
> (watch the line wrap, each alias should all be on one line)
These were originally from Tom Brinkman and he added these words of wisdom
ot the next message in the thread:
A few words of caution. 'bdcd' is currently
alias bdcd='cdrecord -v -eject driveropts=burnfree speed=24
dev=ATA:1,1,0 -data'
~~~~~~~~~~~~~
See the difference? I run cooker and I've been kept shuffled
between scsi-emulation and ATA. Current 10.1 beta's have me back
to ATA, which requires adjusting my aliases and editing fstab to
point to the proper device (ie, scd* or hd*). 'cdrecord -scanbus'
will alert you as to which to use. In some early implementations
only 'cdrecord dev=ATA: -scanbus' will work. So try both.
Much of the above (ie, scsi/ATA) is why GUI's often fail.
Also, for anything but audio cd's an image must be made first,
then burned. In the case of 'biso', you've probly already got an
image (ie, iso) so just 'biso name_of.iso' does it.
For data files, 'mkcdimg /path/to/dir/' makes an image of all
the files in dir/. The image is named 'cd_image' and is created
in the dir you run the mkcdimg command in. Then burn with
'bdcd cd_image' in that directory. 'du cd_image' must be less
than 702MB's. Overburning is not advised (doesn't work anyhow ;)
For audio CD's 'bacd' needs to be run in the dir the .wav's
are in. I've needed to add -sao to do audio burns. To avoid
errors when the total time of the wav's is close to 80 minutes.
I believe this is due to a change in newer cdrecord versions.
alias bacd='cdrecord -v -eject driveropts=burnfree speed=24
dev=ATA:1,1,0 -sao -pad -audio *.wav'
Don't know if this is what you're looking for, but it may help someone.
--
Chris
Registered Linux User 283774 http://counter.li.org
20:29:47 up 17 days, 32 min, 2 users, load average: 0.67, 0.92, 0.66
Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk
pgpmB4BLEeha5.pgp
Description: PGP signature
