12:21 p.m.
Hi,
I'm trying to install FC5t3 on another computer, but I can't burn the
ISOs.
I've tried burning from GNOME and using cdrecord, e.g.
cdrecord dev=/dev/hda -eject -v -dao FC-5-Test3-i386-disc1.iso
(I ran this as root as it complained about setpriority when I didn't).
But on the resulting CDs some files can be copied but other's result in
I/O errors. Last time I posted about verifying CDs I was told that this
process was unreliable.
So we have unreliable CD burning and no reliable way to verify them.
And I have a half-installed computer.
Does anyone have any tips for successful burning of ISOs? (I'm burning
from an up-to-date FC5 test installation).
Will CD burning ever "Just Work"?
Yours depressed and surrounded by corrupt CDs,
Leon...
12:37 p.m.
On Saturday 25 February 2006 10:21 am, Leon Stringer wrote:
Hi,
I'm trying to install FC5t3 on another computer, but I can't burn the
ISOs.
I've tried burning from GNOME and using cdrecord, e.g.
cdrecord dev=/dev/hda -eject -v -dao FC-5-Test3-i386-disc1.iso
(I ran this as root as it complained about setpriority when I didn't).
But on the resulting CDs some files can be copied but other's result in
I/O errors. Last time I posted about verifying CDs I was told that this
process was unreliable.
So we have unreliable CD burning and no reliable way to verify them.
And I have a half-installed computer.
Does anyone have any tips for successful burning of ISOs? (I'm burning
from an up-to-date FC5 test installation).
Will CD burning ever "Just Work"?
Yours depressed and surrounded by corrupt CDs,
Leon...
Check out this thread:
http://www.linuxquestions.org/questions/showthread.php?t=228896
This seems to be a problem in most Linux distributions, but can be overcome
using the steps mentioned in the thread.
Hope this helps.
--Dane
12:57 p.m.
On Saturday 25 February 2006 18:37, Dane Mutters wrote:
Check out this thread:
http://www.linuxquestions.org/questions/showthread.php?t=228896
August 2003?
1:18 p.m.
On Saturday 25 February 2006 10:57 am, Anne Wilson wrote:
On Saturday 25 February 2006 18:37, Dane Mutters wrote:
> Check out this thread:
>
> http://www.linuxquestions.org/questions/showthread.php?t=228896
August 2003?
Yes, I know it's old, but I think it may still be relevant to your problem.
--Dane
1:26 p.m.
On Saturday 25 February 2006 19:18, Dane Mutters wrote:
On Saturday 25 February 2006 10:57 am, Anne Wilson wrote:
> On Saturday 25 February 2006 18:37, Dane Mutters wrote:
> > Check out this thread:
> >
> > http://www.linuxquestions.org/questions/showthread.php?t=228896
>
> August 2003?
Yes, I know it's old, but I think it may still be relevant to your
problem.
Is there a problem? As Stella said, k3b can handle it.
Anne
1:35 p.m.
On Sat, 2006-02-25 at 19:26 +0000, Anne Wilson wrote:
On Saturday 25 February 2006 19:18, Dane Mutters wrote:
> On Saturday 25 February 2006 10:57 am, Anne Wilson wrote:
> > On Saturday 25 February 2006 18:37, Dane Mutters wrote:
> > > Check out this thread:
> > >
> > > http://www.linuxquestions.org/questions/showthread.php?t=228896
> >
> > August 2003?
>
> Yes, I know it's old, but I think it may still be relevant to your
> problem.
>
Is there a problem? As Stella said, k3b can handle it.
Yes, there are two problems:
If GNOME offers to burn ISOs to CD it should work
You should be able to test the CDs reliably.
Because I'm keen to find out where the GNOME problem is I've been
testing with cdrecord.
I've managed one successful burn with:
cdrecord dev=/dev/hda speed=10 padsize=63s -pad -dao -v -eject
FC-5-Test3-i386-disc1.iso
As recommended in the link from the above article
(http://www.troubleshooters.com/linux/coasterless.htm).
I'll install k3b and see what the results are like.
Thanks for your replies!
1:42 p.m.
On Saturday 25 February 2006 19:35, Leon Stringer wrote:
On Sat, 2006-02-25 at 19:26 +0000, Anne Wilson wrote:
> On Saturday 25 February 2006 19:18, Dane Mutters wrote:
> > On Saturday 25 February 2006 10:57 am, Anne Wilson wrote:
> > > On Saturday 25 February 2006 18:37, Dane Mutters wrote:
> > > > Check out this thread:
> > > >
> > > > http://www.linuxquestions.org/questions/showthread.php?t=228896
> > >
> > > August 2003?
> >
> > Yes, I know it's old, but I think it may still be relevant to your
> > problem.
>
> Is there a problem? As Stella said, k3b can handle it.
Yes, there are two problems:
If GNOME offers to burn ISOs to CD it should work
You should be able to test the CDs reliably.
Because I'm keen to find out where the GNOME problem is I've been
testing with cdrecord.
I've managed one successful burn with:
cdrecord dev=/dev/hda speed=10 padsize=63s -pad -dao -v -eject
FC-5-Test3-i386-disc1.iso
As recommended in the link from the above article
(http://www.troubleshooters.com/linux/coasterless.htm).
I'll install k3b and see what the results are like.
Thanks for your replies!
If you set the Verify flag in k3b it will check the md5sum of the burn agains
the md5sum of the original file.
Anne
2:01 p.m.
On Sat, 2006-02-25 at 19:42 +0000, Anne Wilson wrote:
On Saturday 25 February 2006 19:35, Leon Stringer wrote:
>
> I'll install k3b and see what the results are like.
>
> Thanks for your replies!
If you set the Verify flag in k3b it will check the md5sum of the burn agains
the md5sum of the original file.
Sure, but I'm told this isn't reliable due to a long standing problem
(https://www.redhat.com/archives/fedora-test-list/2006-January/msg02061.html).
And as I suspected K3B uses cdrecord underneath as does GNOME. That said
I've just burnt one CD with K3B which has worked first time so it's
doing a better job than GNOME, so I'm getting somewhere.
Thanks,
Leon...
3:21 p.m.
On Saturday 25 February 2006 12:01, Leon Stringer wrote:
On Sat, 2006-02-25 at 19:42 +0000, Anne Wilson wrote:
> On Saturday 25 February 2006 19:35, Leon Stringer wrote:
> > I'll install k3b and see what the results are like.
> >
> > Thanks for your replies!
>
> If you set the Verify flag in k3b it will check the md5sum of the burn
> agains the md5sum of the original file.
Sure, but I'm told this isn't reliable due to a long standing problem
(https://www.redhat.com/archives/fedora-test-list/2006-January/msg02061.htm
l).
And as I suspected K3B uses cdrecord underneath as does GNOME. That said
I've just burnt one CD with K3B which has worked first time so it's
doing a better job than GNOME, so I'm getting somewhere.
Thanks,
Leon...
You might also check out "man cdrecord", paying attention go the examples and
diagnostics near the end. I've used the examples by just copying, then
changing the device and file name and it worked great.
HTH,
Tom
--
Tom Taylor
Linux user #263467
Federal Way, WA
3:29 p.m.
On Saturday 25 February 2006 20:01, Leon Stringer wrote:
On Sat, 2006-02-25 at 19:42 +0000, Anne Wilson wrote:
> On Saturday 25 February 2006 19:35, Leon Stringer wrote:
> > I'll install k3b and see what the results are like.
> >
> > Thanks for your replies!
>
> If you set the Verify flag in k3b it will check the md5sum of the burn
> agains the md5sum of the original file.
Sure, but I'm told this isn't reliable due to a long standing problem
(https://www.redhat.com/archives/fedora-test-list/2006-January/msg02061.htm
l).
I have heard this talked about before. This is not from my experience, but
from what I have heard. People have tried their own verify by md5sum and
been unable to get a correct result. K3b seems to be able to do it. I don't
know whether some corrective has been consciously programmed in, but the
concensus seems to be that if K3b says it's OK, then you can trust it.
And as I suspected K3B uses cdrecord underneath as does GNOME. That said
I've just burnt one CD with K3B which has worked first time so it's
doing a better job than GNOME, so I'm getting somewhere.
HTH
Anne
3:45 p.m.
I'm surprised that nobody on this thread has mentioned the two most valuable
tips when having problems with CD-burning quality:
* Burn at low speeds. 8x is usually good, 4x is failsafe.
* Get quality media. Nothing results in more coasters than poor-quality
media.
Pretty much any tool is going to use cdrecord on the backend, so you just need
to figure out what options to set. Start by adjusting speed options. Try to
keep your system idle while burning, and make sure you have decent throughput
to your drive.
Many tools, including K3B, support verification of the written data, but this
is only a secondary measure. It is much better to avoid problems in the
first place rather than have to detect them afterwards.
--
Patrick "The N-Man" Barnes
nman64(a)n-man.com
http://www.n-man.com/
Have I been helpful? Rate my assistance!
http://rate.affero.net/nman64/
--
6:29 p.m.
Patrick Barnes wrote:
I'm surprised that nobody on this thread has mentioned the two
most valuable
tips when having problems with CD-burning quality:
* Burn at low speeds. 8x is usually good, 4x is failsafe.
I've heard from the experts that burning at a slower speed is not
neccessarily going to make the burn more likely to succeed. As a
matter of fact, some media may actually be worse at slower than rated
speed.
Having said that... I've had a bit of better success when burning at
slower than rated speeds.
* Get quality media. Nothing results in more coasters than poor-quality
media.
But I do agree with this 150% !
I've recently been burning a whole lot of DVDs and CDs.
I unfortunately decided to purchase 'low cost' blank media.
Boy what a mistake that was. At best, my success rate was
pathetic, at worst, it was laughable. :-(
So from now on, its nothing but medium to premium blanks.
... snip ...
Many tools, including K3B, support verification of the written data, but this
is only a secondary measure. It is much better to avoid problems in the
first place rather than have to detect them afterwards.
Having a successful burn guaranteed is always the best, but when
trying out a new batch of blanks, I now highly recommend do the
verification. At least that way, I know I haven't burned a coaster.
Now I've had some turn into a coaster the day after it was burned,
but at least it verified on the day of the burn. :-(
11:06 a.m.
On Sunday 26 February 2006 00:29, Fulko Hew wrote:
Patrick Barnes wrote:
>I'm surprised that nobody on this thread has mentioned the two most
> valuable tips when having problems with CD-burning quality:
>
> * Burn at low speeds. 8x is usually good, 4x is failsafe.
I've heard from the experts that burning at a slower speed is not
neccessarily going to make the burn more likely to succeed. As a
matter of fact, some media may actually be worse at slower than rated
speed.
Quoting from the link below:
" The Media ID is the location of information about the disc. Much like the
disc maker's name in the ID code, the write speed can be faked. The Write
Strategy is the maximum speed the disc was manufactured to use. Burning
faster will often lead to errors. Unfortunately, most DVD recording drives
read the Media ID for determining write speed allowed by the burning
software. Always check the WRITE STRATEGY to ensure the Media ID is not
forged or read incorrectly by the firmware. Both official and hacked
firmwares are known to allow improper burning speeds on certain discs. Many
3RD CLASS and 4TH CLASS quality discs are guilty of placing media ID speeds
on discs with slower write strategies."
That probably explains why my strategy of routinely downgrading burn speeds
has paid off.
Having said that... I've had a bit of better success when burning
at
slower than rated speeds.
> * Get quality media. Nothing results in more coasters than poor-quality
>media.
As mentioned by Dariusz J. Garbowski there is very useful information on
http://www.digitalfaq.com/media/dvdmedia.htm
Anne
3:16 p.m.
On Sat, 2006-02-25 at 19:26 +0000, Anne Wilson wrote:
On Saturday 25 February 2006 19:18, Dane Mutters wrote:
> On Saturday 25 February 2006 10:57 am, Anne Wilson wrote:
> > On Saturday 25 February 2006 18:37, Dane Mutters wrote:
> > > Check out this thread:
> > >
> > > http://www.linuxquestions.org/questions/showthread.php?t=228896
> >
> > August 2003?
>
> Yes, I know it's old, but I think it may still be relevant to your
> problem.
>
Is there a problem? As Stella said, k3b can handle it.
The nautilus cdburner can also handle it.
Anne
4:10 p.m.
On Sat, 2006-02-25 at 15:16 -0600, Jeff Vian wrote:
On Sat, 2006-02-25 at 19:26 +0000, Anne Wilson wrote:
> Is there a problem? As Stella said, k3b can handle it.
The nautilus cdburner can also handle it.
No, nautilus can't. That's my problem. nautilus gave me a stack of
coasters. K3B has been 100% reliable...
7:42 p.m.
On Sat, 2006-02-25 at 22:10 +0000, Leon Stringer wrote:
On Sat, 2006-02-25 at 15:16 -0600, Jeff Vian wrote:
> On Sat, 2006-02-25 at 19:26 +0000, Anne Wilson wrote:
> > Is there a problem? As Stella said, k3b can handle it.
> The nautilus cdburner can also handle it.
No, nautilus can't. That's my problem. nautilus gave me a stack of
coasters. K3B has been 100% reliable...
YMMV. For me, nautilus has done an admirable job and has not created a
single coaster. I have used nautilus as well as k3b since FC4 was
released. I had only used k3b when on FC3.
You have the ability to select burn speed within nautilus as well as
within k3b so for a quick burn from an existing iso file (or even from a
list of files) nautilus has done an outstanding job for me.
Your problems may also stem from the quality of your burner as well as
the media you use.
12:38 p.m.
Leon Stringer wrote:
Hi,
I'm trying to install FC5t3 on another computer, but I can't burn the
ISOs.
I've tried burning from GNOME and using cdrecord, e.g.
cdrecord dev=/dev/hda -eject -v -dao FC-5-Test3-i386-disc1.iso
(I ran this as root as it complained about setpriority when I didn't).
But on the resulting CDs some files can be copied but other's result in
I/O errors. Last time I posted about verifying CDs I was told that this
process was unreliable.
So we have unreliable CD burning and no reliable way to verify them.
And I have a half-installed computer.
Does anyone have any tips for successful burning of ISOs? (I'm burning
from an up-to-date FC5 test installation).
Will CD burning ever "Just Work"?
Yours depressed and surrounded by corrupt CDs,
Leon...
Use K3B, click on tools, click on burn cd or dvd image.
1:28 p.m.
On Saturday 25 February 2006 1:38 pm, Stella Ferrell wrote:
Leon Stringer wrote:
> Hi,
><snip>
></snip>
Use K3B, click on tools, click on burn cd or dvd image.
Also, you might check the verify written data option near the bottom of the
dialog box. <shrug> It worked for me.
-Jpearson
4:31 p.m.
Leon Stringer wrote:
Hi,
I'm trying to install FC5t3 on another computer, but I can't burn the
ISOs.
I've tried burning from GNOME and using cdrecord, e.g.
cdrecord dev=/dev/hda -eject -v -dao FC-5-Test3-i386-disc1.iso
(I ran this as root as it complained about setpriority when I didn't).
But on the resulting CDs some files can be copied but other's result in
I/O errors. Last time I posted about verifying CDs I was told that this
process was unreliable.
So we have unreliable CD burning and no reliable way to verify them.
Yes, rather irritating. ;)
And I have a half-installed computer.
Does anyone have any tips for successful burning of ISOs? (I'm burning
from an up-to-date FC5 test installation).
I'll get burned at the stake for this answer, but in lieu of additional
conditions being specified which limit the number of available responses
to a specific range....
Use Nero Burning ROM in Windows XP. It more or less "just works" every
time.
Will CD burning ever "Just Work"?
In Linux, I'm starting to think the answer is "no". I got my first
CD burner about 7-8 years ago, and used it in Linux for many years.
I also used CDRWin and another app I forget the name of now in Windows
occasionally when I wanted to burn DAO mode, but once DAO mode was
supported in Linux on my burner, I stuck with Linux burning using
xcdroast for a very long time.
Then at some point, something changed in the kernel which broke CD
burning for me, and it wasn't fixed for months. During that time,
I switched to using CDRwin for everything in Windows again. It
was frustrating rebooting just to burn a CD, but necessary.
Then, cd burning worked again. Yay! Only it failed randomly sometimes
for some reason that I couldn't figure out. Eventually I discovered
it was because of autorun or magicdev or something like that, so I
blew those away and it worked again. Then, if I tried to mount a
CD on CDROM unit #2, it would fry the burn happening on CDburner
unit #1 (both on same IDE cable).
Ever since then, which was around RHL 7.1 or maybe 7.2, CD burning
has been working then broken, then working, then broken, etc., at
least for me. I've tried 3 different burners, one a DVD burner, and
have experienced unreliable behaviour which I considered unacceptable.
Each time, I scan the lists and bugzilla and find various reports of
problems, and then just work around it temporarily by rebooting a box
into XP and using Nero or CDRwin. As much as I hate Windows totally,
I don't remember the last time I burned a frisbee in the evil
proprietary OS.
It's been about 6 months since I tried in Linux, on FC4, so I'm not
sure what the current state is like. Rather than finding out by
endlessly experimenting, I've just kept using Nero in XP, as it
doesn't seem to vary over time, even with various OS updates, etc.
All I can say is that hopefully all of the different aspects of
why cd/dvd burning in Linux is currently a bumpy ride for at least
some people, eventually get worked out, whatever the root cause(s)
happen to be.
Another option for me I suppose, would be to set up an older machine
running RHL 7.0 or whatever the last version was that worked flawless
for me, and just leave it at that OS version forever just to burn
CDs with. ;o)
Yours depressed and surrounded by corrupt CDs,
Sometimes it is the media, and other times it may be the burn speed
too. Try different speeds, and different media. I find that once
I've found solid media, if I stick to that same brand for a long time,
I end up making almost zero frisbees.... unless I try to burn in
Linux.
HTH.
--
Mike A. Harris * Open Source Advocate * http://mharris.ca
Proud Canadian.
7:59 p.m.
On Sat, 2006-02-25 at 17:31 -0500, Mike A. Harris wrote:
Leon Stringer wrote:
> Hi,
>
> I'm trying to install FC5t3 on another computer, but I can't burn the
> ISOs.
>
> I've tried burning from GNOME and using cdrecord, e.g.
>
> cdrecord dev=/dev/hda -eject -v -dao FC-5-Test3-i386-disc1.iso
>
> (I ran this as root as it complained about setpriority when I didn't).
>
> But on the resulting CDs some files can be copied but other's result in
> I/O errors. Last time I posted about verifying CDs I was told that this
> process was unreliable.
>
> So we have unreliable CD burning and no reliable way to verify them.
Works for me, using nautilus on FC4. Everything worked and all disks
were usable.
Yes, rather irritating. ;)
> And I have a half-installed computer.
>
> Does anyone have any tips for successful burning of ISOs? (I'm burning
> from an up-to-date FC5 test installation).
Try burning at lower speeds. When FC3 came out there were a lot of
complaints from people about cd quality when using the max possible
speed. When the suggestion was made to try lower speeds the complaints
stopped. I can only assume the results were favorable.
I'll get burned at the stake for this answer, but in lieu of
additional
conditions being specified which limit the number of available responses
to a specific range....
Use Nero Burning ROM in Windows XP. It more or less "just works" every
time.
> Will CD burning ever "Just Work"?
In Linux, I'm starting to think the answer is "no". I got my first
CD burner about 7-8 years ago, and used it in Linux for many years.
I also used CDRWin and another app I forget the name of now in Windows
occasionally when I wanted to burn DAO mode, but once DAO mode was
supported in Linux on my burner, I stuck with Linux burning using
xcdroast for a very long time.
xcdroast quality went away for me around FC1 time. I struggled with it
and finally switched to k3b full time with FC2. No complaints since.
Then at some point, something changed in the kernel which broke CD
burning for me, and it wasn't fixed for months. During that time,
I switched to using CDRwin for everything in Windows again. It
was frustrating rebooting just to burn a CD, but necessary.
Then, cd burning worked again. Yay! Only it failed randomly sometimes
for some reason that I couldn't figure out. Eventually I discovered
it was because of autorun or magicdev or something like that, so I
blew those away and it worked again. Then, if I tried to mount a
CD on CDROM unit #2, it would fry the burn happening on CDburner
unit #1 (both on same IDE cable).
That happens, and I used to get exactly the same with burning and using
another cd device on windows. (I have not tried cd burning in Windows
for over 2 years so I do not know the state there now.) The IDE bus
apparently cannot handle 2 devices that way.
Ever since then, which was around RHL 7.1 or maybe 7.2, CD burning
has been working then broken, then working, then broken, etc., at
least for me. I've tried 3 different burners, one a DVD burner, and
have experienced unreliable behaviour which I considered unacceptable.
Each time, I scan the lists and bugzilla and find various reports of
problems, and then just work around it temporarily by rebooting a box
into XP and using Nero or CDRwin. As much as I hate Windows totally,
I don't remember the last time I burned a frisbee in the evil
proprietary OS.
It's been about 6 months since I tried in Linux, on FC4, so I'm not
sure what the current state is like. Rather than finding out by
endlessly experimenting, I've just kept using Nero in XP, as it
doesn't seem to vary over time, even with various OS updates, etc.
All I can say is that hopefully all of the different aspects of
why cd/dvd burning in Linux is currently a bumpy ride for at least
some people, eventually get worked out, whatever the root cause(s)
happen to be.
Another option for me I suppose, would be to set up an older machine
running RHL 7.0 or whatever the last version was that worked flawless
for me, and just leave it at that OS version forever just to burn
CDs with. ;o)
> Yours depressed and surrounded by corrupt CDs,
Sometimes it is the media, and other times it may be the burn speed
too. Try different speeds, and different media. I find that once
I've found solid media, if I stick to that same brand for a long time,
I end up making almost zero frisbees.... unless I try to burn in
Linux.
YMMV, but I have not even booted to Windows with a cd burner available
on that OS for over 2 years. Factors involved are media quality, burner
quality, memory available, activity (both on the system as a whole and
on the file system), how you are burning (on the fly or from an image),
and probably more. A critical one is the speed of your system and
amount of memory available.
HTH.
--
Mike A. Harris * Open Source Advocate * http://mharris.ca
Proud Canadian.
4:18 a.m.
On Saturday 25 February 2006 22:31, Mike A. Harris wrote:
Then, cd burning worked again. Yay! Only it failed randomly sometimes
for some reason that I couldn't figure out. Eventually I discovered
it was because of autorun or magicdev or something like that, so I
blew those away and it worked again. Then, if I tried to mount a
CD on CDROM unit #2, it would fry the burn happening on CDburner
unit #1 (both on same IDE cable).
You could call that one self-inflicted :-)
Ever since then, which was around RHL 7.1 or maybe 7.2, CD burning
has been working then broken, then working, then broken, etc., at
least for me. I've tried 3 different burners, one a DVD burner, and
have experienced unreliable behaviour which I considered unacceptable.
Each time, I scan the lists and bugzilla and find various reports of
problems, and then just work around it temporarily by rebooting a box
into XP and using Nero or CDRwin. As much as I hate Windows totally,
I don't remember the last time I burned a frisbee in the evil
proprietary OS.
In contrast, I have been burning in linux, first on Mandrake/Mandriva then on
FC4, for over 4 years. When K3B first came out I had problems with it, but I
had been happily burning with XCDRoast, so I stuck with that for another 6
months or so. Since then K3B has been fine. I still use either, depending
on what I want to do. In neither case did I have to do anything other than
run the application's setup.
All I can say is that hopefully all of the different aspects of
why cd/dvd burning in Linux is currently a bumpy ride for at least
some people, eventually get worked out, whatever the root cause(s)
happen to be.
As Jeff remarked, speed can be the cause of problems. I always set the
maximum burn speed for half the rate that the drive claims. Coasters are
almost unknown for me.
I don't think that applications are the cause of your problems, Mike, so maybe
it's media, or maybe it's settings.
Anne
12:19 p.m.
Anne Wilson wrote:
All I can say is that hopefully all of the different aspects of
>why cd/dvd burning in Linux is currently a bumpy ride for at least
>some people, eventually get worked out, whatever the root cause(s)
>happen to be.
>
As Jeff remarked, speed can be the cause of problems. I always set the
maximum burn speed for half the rate that the drive claims. Coasters are
almost unknown for me.
I don't think that applications are the cause of your problems, Mike, so maybe
it's media, or maybe it's settings.
Except for the fact that I burn all my disks in Windows at the full
rated speed of the media normally, and every single disk verifies
properly, and works fine. I even have an ancient 1994 CDROM drive
which my burns work fine on, which is rather surprising. DVD's I
burn in Windows, work fine on all of my computer DVD players, as
well as my standalone unit.
I haven't made a frisbee burning in Windows for as long as I can
even remember now.
Burning in Linux either yields media that does not verify, or which
doesn't work. Please tell me how that is "media" every time that is
the cause. I think not.
Just to restate - I have seen a number of people report that they
are able to burn CD/DVD in Linux with great reliability, and some
people report that their burns do not verify, while others say they
do. So this isn't a 100% "it works for everyone" or "it does not
work for anyone" thing.
There are a great many variables involved, however I exclude the brand
of media and speed of burning from the equation, because the same drive
with the same media, booted into "that other OS", burns them perfect
every single time - for /me/.
I just want to /use/ my hardware and consider it to be a black box
that either works or does not. I prefer the functionality of getting
properly burned media that just works flawlessly for me period, far
more than I care what OS burned them for me, or what software happened
to be used, etc.
This should not be rocket science really. There are various bug reports
and confirmations that the kernel is (or at least has been for a long
time) screwy WRT media verification. Well, verification is a very
important part of the puzzle to me, and something I want to point and
click and have work, not hack around.
About once every 6 months, I try some test burns to RW media in
Linux, with the idea that if it works properly, I'll finally be able
to ditch the evil OS once again. So far, the experiment has not
turned out in my favour. Bad media you say? Funny, the same RW
disk re-erased and the same .iso image burned to it and verified in
the evil OS with Nero or CDRwin, verifies for me, and then works.
Perhaps there are evil anti-OSS pixies in my hardware. From the
looks of the number of bugs reported in bugzilla, and the results
of a quick google search however, I sure am not alone.
--
Mike A. Harris * Open Source Advocate * http://mharris.ca
Proud Canadian.
6:13 a.m.
On Sat, 2006-02-25 at 17:31 -0500, Mike A. Harris wrote:
In Linux, I'm starting to think the answer is "no". I
got my first
CD burner about 7-8 years ago, and used it in Linux for many years.
I also used CDRWin and another app I forget the name of now in Windows
occasionally when I wanted to burn DAO mode, but once DAO mode was
supported in Linux on my burner, I stuck with Linux burning using
xcdroast for a very long time.
Then at some point, something changed in the kernel which broke CD
burning for me, and it wasn't fixed for months. During that time,
I switched to using CDRwin for everything in Windows again. It
was frustrating rebooting just to burn a CD, but necessary.
This is exactly the root of my frustration. With FC1 burning was 100%
reliable. Then it broke and I've had trouble ever since. Presumably that
was the change between 2.4 and 2.6 kernels and change to IDE CD drive
handling.
12:23 p.m.
Leon Stringer wrote:
On Sat, 2006-02-25 at 17:31 -0500, Mike A. Harris wrote:
>In Linux, I'm starting to think the answer is "no". I got my first
>CD burner about 7-8 years ago, and used it in Linux for many years.
>I also used CDRWin and another app I forget the name of now in Windows
>occasionally when I wanted to burn DAO mode, but once DAO mode was
>supported in Linux on my burner, I stuck with Linux burning using
>xcdroast for a very long time.
>
>Then at some point, something changed in the kernel which broke CD
>burning for me, and it wasn't fixed for months. During that time,
>I switched to using CDRwin for everything in Windows again. It
>was frustrating rebooting just to burn a CD, but necessary.
This is exactly the root of my frustration. With FC1 burning was 100%
reliable. Then it broke and I've had trouble ever since. Presumably that
was the change between 2.4 and 2.6 kernels and change to IDE CD drive
handling.
From googling, and a bit of bugzilla surfing, that is what the problem
appears to be for many people. I had various problems even on FC1,
RHL 8, 9, and the latter few RHL 7.x releases too however. The problems
definitely werent all related though, and I did manage to work around
some of them. Problem is though, I don't _want_ to "work around" things
myself manually for something like this. Sometimes you just want
certain things to "work" without having to screw around or surf for
kludges. So I bite my tongue, curse under my breath at Mr. Gates,
and reboot to a useable solution, hating every minute of it, but
being happy with the end result.
--
Mike A. Harris * Open Source Advocate * http://mharris.ca
Proud Canadian.
7:22 a.m.
On 02/25/2006 10:31 PM, Mike A. Harris wrote:
Leon Stringer wrote:
> Hi,
>
> I'm trying to install FC5t3 on another computer, but I can't burn the
> ISOs.
>
> I've tried burning from GNOME and using cdrecord, e.g.
>
> cdrecord dev=/dev/hda -eject -v -dao FC-5-Test3-i386-disc1.iso
>
> (I ran this as root as it complained about setpriority when I didn't).
>
> But on the resulting CDs some files can be copied but other's result in
> I/O errors. Last time I posted about verifying CDs I was told that this
> process was unreliable.
>
> So we have unreliable CD burning and no reliable way to verify them.
Yes, rather irritating. ;)
> And I have a half-installed computer.
>
> Does anyone have any tips for successful burning of ISOs? (I'm burning
> from an up-to-date FC5 test installation).
I'll get burned at the stake for this answer, but in lieu of additional
conditions being specified which limit the number of available responses
to a specific range....
Use Nero Burning ROM in Windows XP. It more or less "just works" every
time.
And where do I get this stuff? Anybody giving free Windows XP out there? ;-)
Sorry to hear about your problems. I've had completetly opposite
experiences to Mike -- lots of problem when burning on Windows (well,
truth is it was some 5 years back I run any Windows on my boxes :) and
only when I eventually switched completely to Linux I had 100% reliable
burning. The only failures were to due to bad media or myself really
loading up the machine with very CPU+HD+network intensive tasks. And
that my experience since Mandrake 6 through RH 7.3, RH 9 and FC3 on SCSI
Teac 4x recorder and later on Pioneer 105 DVD recorder.
I felt I neede to add my comment to this rather depressing thread. Hope
your problems will get fixed, guys!
Dariusz
___________________________________________________________
Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail
http://uk.messenger.yahoo.com
7:36 a.m.
Dariusz J. Garbowski wrote:
On 02/25/2006 10:31 PM, Mike A. Harris wrote:
> Leon Stringer wrote:
>> Hi,
>>
>> I'm trying to install FC5t3 on another computer, but I can't burn the
>> ISOs.
>>
>> I've tried burning from GNOME and using cdrecord, e.g.
>>
>> cdrecord dev=/dev/hda -eject -v -dao FC-5-Test3-i386-disc1.iso
>>
>> (I ran this as root as it complained about setpriority when I didn't).
>>
>> But on the resulting CDs some files can be copied but other's result in
>> I/O errors. Last time I posted about verifying CDs I was told that this
>> process was unreliable.
>>
>> So we have unreliable CD burning and no reliable way to verify them.
>
> Yes, rather irritating. ;)
>
>> And I have a half-installed computer.
>>
>> Does anyone have any tips for successful burning of ISOs? (I'm burning
>> from an up-to-date FC5 test installation).
>
> I'll get burned at the stake for this answer, but in lieu of additional
> conditions being specified which limit the number of available responses
> to a specific range....
>
> Use Nero Burning ROM in Windows XP. It more or less "just works" every
> time.
And where do I get this stuff? Anybody giving free Windows XP out
there? ;-)
Sorry to hear about your problems. I've had completetly opposite
experiences to Mike -- lots of problem when burning on Windows (well,
truth is it was some 5 years back I run any Windows on my boxes :) and
only when I eventually switched completely to Linux I had 100%
reliable burning. The only failures were to due to bad media or myself
really loading up the machine with very CPU+HD+network intensive
tasks. And that my experience since Mandrake 6 through RH 7.3, RH 9
and FC3 on SCSI Teac 4x recorder and later on Pioneer 105 DVD recorder.
I felt I neede to add my comment to this rather depressing thread.
Hope your problems will get fixed, guys!
Dariusz
___________________________________________________________ Yahoo!
Messenger - NEW crystal clear PC to PC calling worldwide with
voicemail http://uk.messenger.yahoo.com
Try using gnomebaker. Seems to work great.
12:30 p.m.
Dariusz J. Garbowski wrote:
> Use Nero Burning ROM in Windows XP. It more or less "just
works" every
> time.
And where do I get this stuff? Anybody giving free Windows XP out there?
;-)
This suggestion may or may not be economically, morally, or ethically
viable for some people for certain. I certainly am not advocating
Windows here, just mentioning that it is a solution that works for me
as a workaround for the time being for certain classes of problems. ;)
Sorry to hear about your problems. I've had completetly opposite
experiences to Mike -- lots of problem when burning on Windows (well,
truth is it was some 5 years back I run any Windows on my boxes :) and
only when I eventually switched completely to Linux I had 100% reliable
burning. The only failures were to due to bad media or myself really
loading up the machine with very CPU+HD+network intensive tasks. And
that my experience since Mandrake 6 through RH 7.3, RH 9 and FC3 on SCSI
Teac 4x recorder and later on Pioneer 105 DVD recorder.
I felt I neede to add my comment to this rather depressing thread. Hope
your problems will get fixed, guys!
Yeah, hopefully. ;) Maybe ESR will write a nasty letter about CD
burning support in Linux, and it'll get slashdotted and covered in
all major online media, leading to rock solid CD burning/verifying
support a few weeks later. ;) It worked somewhat for printing
anyway, so we can remain hopeful. ;)
--
Mike A. Harris * Open Source Advocate * http://mharris.ca
Proud Canadian.
4:32 p.m.
Mike A. Harris wrote:
Yeah, hopefully. ;) Maybe ESR will write a nasty letter about CD
One imagines Mike Harris could have a similar effect, given his
long-standing connexion with a major Linux vendor. Go for it Mike: I've
been turning out duds on three different DVD burners (2x LG, one a brand
I don't recognise in my Acer Aspire) on Fedora Core and SUSE. I've not
tried Windows, had no reason to until now: now the Q is how to reformat
my laptop's drive to NTFS (I'm not keen on the in-place conversion).
burning support in Linux, and it'll get slashdotted and covered
in
all major online media, leading to rock solid CD burning/verifying
support a few weeks later. ;) It worked somewhat for printing
anyway, so we can remain hopeful. ;)
--
Cheers
John
-- spambait
1aaaaaaa(a)computerdatasafe.com.au Z1aaaaaaa(a)computerdatasafe.com.au
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
do not reply off-list
12:57 p.m.
søn, 26 02 2006 kl. 13:30 -0500, skrev Mike A. Harris:
Yeah, hopefully. ;) Maybe ESR will write a nasty letter about CD
burning support in Linux, and it'll get slashdotted and covered in
all major online media, leading to rock solid CD burning/verifying
support a few weeks later. ;) It worked somewhat for printing
anyway, so we can remain hopeful. ;)
http://icculus.org/burn/
Libburn is the eventual replacement for Jorg' cdrecord grip on Linux
burning, see we didn't even need ESR for this one.
I encourage talented people to start contributing so it can get in shape
faster and free us all.
- David
--
Obligatory shameless blog plug - the GNOME commentary located at:
www.lovesunix.net/blog
3:09 p.m.
David Nielsen wrote:
søn, 26 02 2006 kl. 13:30 -0500, skrev Mike A. Harris:
>Yeah, hopefully. ;) Maybe ESR will write a nasty letter about CD
>burning support in Linux, and it'll get slashdotted and covered in
>all major online media, leading to rock solid CD burning/verifying
>support a few weeks later. ;) It worked somewhat for printing
>anyway, so we can remain hopeful. ;)
http://icculus.org/burn/
Libburn is the eventual replacement for Jorg' cdrecord grip on Linux
burning, see we didn't even need ESR for this one.
I encourage talented people to start contributing so it can get in shape
faster and free us all.
It's good to see that someone is creating an alternative to cdrecord.
Hopefully it will do as much as cdrecord can do, and hopefully it has
pleasant friendly developers too. ;o)
I don't think that will fix kernel bugs though, unless there is a
libburn.ko included that replaces the buggy kernel code. ;)
--
Mike A. Harris * Open Source Advocate * http://mharris.ca
Proud Canadian.
4:27 p.m.
Mike A. Harris wrote:
David Nielsen wrote:
> søn, 26 02 2006 kl. 13:30 -0500, skrev Mike A. Harris:
>
>> Yeah, hopefully. ;) Maybe ESR will write a nasty letter about CD
>> burning support in Linux, and it'll get slashdotted and covered in
>> all major online media, leading to rock solid CD burning/verifying
>> support a few weeks later. ;) It worked somewhat for printing
>> anyway, so we can remain hopeful. ;)
>
>
>
> http://icculus.org/burn/
>
> Libburn is the eventual replacement for Jorg' cdrecord grip on Linux
> burning, see we didn't even need ESR for this one.
>
> I encourage talented people to start contributing so it can get in shape
> faster and free us all.
It's good to see that someone is creating an alternative to cdrecord.
<sip>
Hopefully it will do as much as cdrecord can do, and hopefully it has
pleasant friendly developers too. ;o)
<sip>
I don't think that will fix kernel bugs though, unless there is a
libburn.ko included that replaces the buggy kernel code. ;)
I use growisofs to burn DVDs, so cdrecord with its patches aren't
responsible for my problems.
It's enough to make me think somewhat seriously of installing Debian (I
can't think of anything else atm that supports 2.4 kernels). Maybe a
RHEL 3 clone.
5:03 p.m.
John Summerfield said:
I use growisofs to burn DVDs, so cdrecord with its patches
aren't
responsible for my problems.
It's enough to make me think somewhat seriously of installing Debian (I
can't think of anything else atm that supports 2.4 kernels). Maybe a
RHEL 3 clone.
I don't know if it helps, but for my burner (Pioneer DVR-110D), I'm always
required to run `cdrecord -fix` to finalize any disc I burn which is more
than a few hundred megs. I honestly have no idea why this is, but it
doesn't seem to cause any other problems.
~~Peter
6:49 a.m.
On Sat, 25 Feb 2006 18:21:17 +0000, Leon Stringer wrote:
I'm trying to install FC5t3 on another computer, but I can't
burn the
ISOs.
I've tried burning from GNOME and using cdrecord, e.g.
cdrecord dev=/dev/hda -eject -v -dao FC-5-Test3-i386-disc1.iso
I just burned a CD with:
cdrecord mycd.iso
It chose TAO rather than DAO, and 4x because it's a CD-RW I just blanked
with "cdrecord blank=fast". The CD mounts OK if I mount as root,
otherwise it tell me "You are not privileged to mount the volume
'volume-name'." But it tells me this for other CDs too.
-Paul
7:07 a.m.
On Sun, 26 Feb 2006 05:49:30 -0700, Paul Dickson wrote:
On Sat, 25 Feb 2006 18:21:17 +0000, Leon Stringer wrote:
> I'm trying to install FC5t3 on another computer, but I can't burn the
> ISOs.
>
> I've tried burning from GNOME and using cdrecord, e.g.
>
> cdrecord dev=/dev/hda -eject -v -dao FC-5-Test3-i386-disc1.iso
I just burned a CD with:
cdrecord mycd.iso
It chose TAO rather than DAO, and 4x because it's a CD-RW I just blanked
with "cdrecord blank=fast". The CD mounts OK if I mount as root,
otherwise it tell me "You are not privileged to mount the volume
'volume-name'." But it tells me this for other CDs too.
I forgot to mention, I'm writing the CD as root (an old habit for this
specific task).
-Paul
10:08 a.m.
On 2/25/06, Leon Stringer <leon.stringer(a)ntlworld.com> wrote:
Hi,
I'm trying to install FC5t3 on another computer, but I can't burn the
ISOs.
I've tried burning from GNOME and using cdrecord, e.g.
cdrecord dev=/dev/hda -eject -v -dao FC-5-Test3-i386-disc1.iso
Try using -pad. I haven't burned a coaster in years (on probably four
or five burners). DVDs are sadly another matter, but even then my
failure rate has been about 5-8%, not too shabby really, and that was
on an older DVD burner.
I also use the ATA: drive specification and burnfree
(driverops=burnfree) if your drive supports it. I always use cdrecord
at the command line (I hate the idea of having to load in most of KDE
just to run k3b).
--
_ Ben Steeves bcs(a)metacon.ca
( ) The ASCII ribbon campaign ben.steeves(a)unb.ca
X against HTML e-mail GPG ID: 0xB3EBF1D9
/ \ http://www.metacon.ca/ascii Yahoo Messenger: ben_steeves
10:46 a.m.
On 02/26/2006 04:08 PM, Ben Steeves wrote:
On 2/25/06, Leon Stringer <leon.stringer(a)ntlworld.com> wrote:
> Hi,
>
> I'm trying to install FC5t3 on another computer, but I can't burn the
> ISOs.
>
> I've tried burning from GNOME and using cdrecord, e.g.
>
> cdrecord dev=/dev/hda -eject -v -dao FC-5-Test3-i386-disc1.iso
Try using -pad. I haven't burned a coaster in years (on probably four
or five burners). DVDs are sadly another matter, but even then my
failure rate has been about 5-8%, not too shabby really, and that was
on an older DVD burner.
I've had mixed results with DVD burning due to questionable media
quality. The moment I switched to Taiyo Yuden-based Verbatims I have
100% success rate! Make sure you buy good quality media (e.g. not all
Verbatims are good either!) -- see "Blank Media & Quality FAQ"
http://www.digitalfaq.com/media/dvdmedia.htm
You can also look at "Where to buy good media"
http://www.digitalfaq.com/dvdguides/buyerguides/buymedia.htm
Disclaimer: I have no connection to either this website nor am I selling
any media. I'm just a user who found those guides useful.
Regards,
Dariusz
___________________________________________________________
Yahoo! Photos NEW, now offering a quality print service from just 8p a photo
http://uk.photos.yahoo.com
7:44 a.m.
On 2/26/06, Dariusz J. Garbowski <thuforuk(a)yahoo.co.uk> wrote:
On 02/26/2006 04:08 PM, Ben Steeves wrote:
>DVDs are sadly another matter, but even then my
> failure rate has been about 5-8%, not too shabby really, and that was
> on an older DVD burner.
I've had mixed results with DVD burning due to questionable media
quality. The moment I switched to Taiyo Yuden-based Verbatims I have
100% success rate! Make sure you buy good quality media (e.g. not all
Verbatims are good either!) -- see "Blank Media & Quality FAQ"
Ironically, with my older LG single-layer burner, I burned a lot more
DVD coasters with brand-name Memorex discs than I did with no-name
discs. On my new Samsung dual-layer burner, I haven't burned any
coasters* except when something external happened (like droping the X
server out from under the shell running the burn -- accidentally of
course :-).
*with single-layer media, that is. I have yet to try dual-layer media.
PS: I use growisofs from the command line for all my DVD burning
needs, and cdrecord for CD burning (also from the shell). I don't
need no steenkin' GUI. :-)
Ben
--
_ Ben Steeves bcs(a)metacon.ca
( ) The ASCII ribbon campaign ben.steeves(a)unb.ca
X against HTML e-mail GPG ID: 0xB3EBF1D9
/ \ http://www.metacon.ca/ascii Yahoo Messenger: ben_steeves
8:19 a.m.
On Tuesday 28 February 2006 07:44, Ben Steeves wrote:
On 2/26/06, Dariusz J. Garbowski <thuforuk(a)yahoo.co.uk> wrote:
> On 02/26/2006 04:08 PM, Ben Steeves wrote:
> >DVDs are sadly another matter, but even then my
> > failure rate has been about 5-8%, not too shabby really, and
> > that was on an older DVD burner.
>
> I've had mixed results with DVD burning due to questionable media
> quality. The moment I switched to Taiyo Yuden-based Verbatims I
> have 100% success rate! Make sure you buy good quality media
> (e.g. not all Verbatims are good either!) -- see "Blank Media &
> Quality FAQ"
Ironically, with my older LG single-layer burner, I burned a lot
more DVD coasters with brand-name Memorex discs than I did with
no-name discs. On my new Samsung dual-layer burner, I haven't
burned any coasters* except when something external happened (like
droping the X server out from under the shell running the burn --
accidentally of course :-).
cdrecord dev=ATA:1,1,0 -atip .... with a blank in your burner
will return who actually manufactured the media. "Brand" names don't
make theirs, they just add their logo on the label side. This adds a
little value to generic Cdr's as it improves reflectability slightly,
an makes the discs much more durable. Generics are just as good as
Brand names, if they're for temp storage, or won't be handled much.
They are afterall, mostly the same manufacturers as the Brand names
an much cheaper.
Memorex are readily available here close to where I live. In the
past most 100 spindles were Prodisc, a good vendor. Lately the last
half dozen spindles have been an 'average' quality vendor,
Disk type: Short strategy type (Phthalocyanine or similar)
Manuf. index: 22
Manufacturer: Ritek Co.
The Taiyo Yuden blanks that Dariusz mentioned are very good media,
probly the best. I've also bought Brand name 100-spindles in the
past that were comprised of blanks made by several different vendors.
Some of them were Bahre, a non-orange forum Indian vendor... poor
quality. I bought a 100 spindle of Imation recently, only to find
they were this crap.
*with single-layer media, that is. I have yet to try dual-layer
media.
PS: I use growisofs from the command line for all my DVD burning
needs, and cdrecord for CD burning (also from the shell). I don't
need no steenkin' GUI. :-)
Same here. IMO, most peoples problems are because they depend on a
GUI without really knowin what they, or the GUI is doin.
As to the OP's subject, I burn iso's with 'biso Name_of_the.iso'
(alias biso='cdrecord -v -eject driveropts=burnfree speed=16
dev=ATA:1,1,0 -dao'). The most important option being -dao. 16x is
1/3 speed for my Plextor an the media I use (52x).
--
Tom Brinkman Corpus Christi, Texas
6645
days inactive
6648
days old
37 comments
18 participants
participants (18)
-
Anne Wilson -
Ben Steeves -
Dane Mutters -
Dariusz J. Garbowski -
David Nielsen -
Fulko Hew -
Jeff Vian -
John Pearson -
John Summerfield -
Leon Stringer -
Mike A. Harris -
Partha Bagchi -
Patrick W. Barnes -
Paul Dickson -
Peter Gordon -
Stella Ferrell -
Thomas Taylor -
Tom