pburn makes endless coasters

[bugman]

okay, i burned a bunch of cdrs for a friend

and then i upgraded from 4.12 to 4.31

and then i tried to burn some more cdrs and got nothing but coasters, burns dying out between 150mb and 600mb of the way through a 690mb attempt

[can't remember the exact error, but it would die at a certain point and then fixate what it had gotten--should have known it was not a bad disc but i am inexperienced in such matters]

tried a disc from a different maker, same thing

booted w/ a 4.12 cd, burned another disc, no problem

so i'm guessing either the new pburn or the new kernel doesn't work with my cd burner, anyone else have this problem, know a fix, anything?

thanks!

[`f00]

Generally I use burniso2cd and have never missed a burn, even if it did not 'verify' (this has gotten better recently) - xfburn is faster at blanking rw media (either method) .. only one tester had an issue (probably a upup) and it was solved with xorriso-0.4.0-pup4.pet

ahh, music/data/mixed cdrs I haven't played much with in puppy - it's more about getting liveCD operation reliable for me (interface of pburn kept getting my devices mixed so I stopped using it after a brief try). It does mention that your stored source should be fairly seamless and large enough to hold it all in one glob, I'd think. Someone else who burns more should be along shortly..

:LOL: @rj'

[rjbrewer]

Bugman:

Recently I've been upgrading my 4.3.1 installs to 4.1.2.

[bugman]

Bugman:

Recently I've been upgrading my 4.3.1 installs to 4.1.2.

my brother!



[that's kind of what i've been thinking about too . . .]

[rjbrewer]

Bugman:

Recently I've been upgrading my 4.3.1 installs to 4.1.2.

my brother!



[that's kind of what i've been thinking about too . . .]

Yea; the simple fact is I can use pets to install anything I like from
4.3.1 to 4.1.2, and 4.1.2 is lighter on ram and cpu usage than either
4.3.1 or 4.2.1.
Three out of four of my wireless devices have connection problems
with 4.3.1 unless I use the retro (4.1.2) kernel, and even then 4.3.1
has problems keeping connection after reboot or cold start.

[disciple]

Have you upgraded to the latest Pburn?
http://www.murga-linux.com/puppy/viewtopic.php?t=23881

(actually, you should do that regardless of which Puppy version you run)

[William (Dthdealer)]

Pburn has problems with the growisofs command options, inserting them between others and generally stuffing up. As much as it is a nice application I try to avoid it.

[disciple]

Pburn has problems with the growisofs command options, inserting them between others and generally stuffing up.

Perhaps you could make yourself useful and report these problems What do you use instead of Pburn?

[bugman]

Recently I've been upgrading my 4.3.1 installs to 4.1.2.

actually, i remembered that i really liked the old burner from way back when [2.15?], i'll have to look that one up again

have been thinking a lot lately making about a custom pup, ugly as hell, low ram, old versions of apps, minimum libs, doesn't work on anything but over-10-year-old desktop boxes with dialup

if i ever get the time...

[racepres]

Bugman.. I want one!!
I am currently running 3.0"something" [white Fang] I am slowly getting it exactly like I want it...
It is already really light and fast [for me]
RP

[bugman]

Bugman.. I want one!!
I am currently running 3.0"something" [white Fang] I am slowly getting it exactly like I want it...
It is already really light and fast [for me]
RP

okay, the laziest person in the world [me] already has a customer...

why do people always hold me to my threats?



[starting work on it this very afternoon, who knows?]

[walter90]

I had the same problem when I upgraded from the pburn that comes with 4.2.1 I don't like the newer version at all.

Also, I noticed that you have to select "compatability" mode or you just get useless and/or unreliable crap.

[Flash]

I've never had much luck getting Pburn to do anything, so I don't use it. I don't need to burn much, so I haven't tried to help with its development. I just don't have time.

[Sylvander]

I've never had a problem with Pburn; use it regularly to erase CD-RW's before burning isos with burniso2cd.

[walter90]

I've never had a problem with Pburn; use it regularly to erase CD-RW's before burning isos with burniso2cd.

I use Pburn to erase as well, and there it does just fine. I tried ISOto CD last night when I burned Fluxbox. Fluxbox won't shutdown the normal way but I doubt that's ISOtoCD's fault.

[Shep]

The 8 or 9 CDs, CD R-W and DVD R-W that I have burnt with pburn
have all had their md5sum check okay. I used pburn to erase the
disc as well as burn the ISO. I select the slowest speed, and give it
plenty of space for temp work outside the puppy file tree.

The only misgiving I have is that after I'd quit, I'm almost certain I
noticed that pburn left 3 pburn-related processes running. Very untidy.
Can't quote a particular version, as I'm trialling various puppys.
Pburn has a weird GUI. After clicking on boxes for the options you want,
you then have to click on something to actually implement those options
before you give it the go ahead to burn. If you don't click, it seems that
it doesn't set the CDBURN options you thought you'd selected. Very odd
way of doing things, and likely to trip up quite a few users.