I used burniso2cd for imaging the iso. Because it took so long for Pburn to creating commands or something. But now I used Pburn for imaging....I waited kindly enough minutes so that it started and burned the iso image.
This time the dvd was blanked nicely with Pburn. I have to also tell that my dvd burner is not in its best shape anymore and the dvd rw disk is also quite old, eventhough in good shape, no scratches.
So...just dismiss my previous report. I thought it could be useful to report but...I think not anymore. I could remove the whole post and reference this.....

I haven't seen Pburn kill anything (else you use the emergency button). - I have Geany open 'all' the time ...... ???

Maybe it is rare case and not serious.

Open any file under /usr/local/pburn by geaney.

Start pburn.

Quit pburn.

Confirmed!
Does not happen if another file is open in the first tab in Geany

Ah, good find. We didn't discover that workaround when I reported this years ago. I'll have to use Geany when I mess around with Pburn and co now._________________DEATH TO SPREADSHEETS
- - -
Classic Puppy quotes
- - -
Beware the demented serfers!

No, I thought Pburn 3.70 was supposed to overwrite by default, perhaps with a warning that the disk already contains data which will be overwritten if nothing is done.

So I had another try at burning the blank disk, this time checking the overwrite box and switching the temporary storage (even though temporary storage supposedly isn't needed for DVDs and Blu-Ray) to a 32 GB flash memory stick instead of the default location in RAM.

With the overwrite box checked and the temporary memory location moved to /mnt/sdb1, Pburn burned the 22 GB onto the blanked disk without error, though it took more than 2 hours.

Perhaps the cause of the error Pburn gave on the first try was that the temporary memory location (which was in RAM) was too small even though the computer has 4 GB of RAM. But why did Pburn use the temporary memory at all? It shouldn't need it. If it can't read the data from the source location fast enough to keep up with burning, then it should just slow down the burning process. I don't see how transferring the data from the source USB flash drive to an intermediate or temporary location which is itself a USB flash drive, before burning it speeds up the data transfer at all.

Tomorrow I plan to blank the disk and repeat the same burn to see if Pburn creates a symlink directory in /tmp and uses it for temporary storage even though it was told to put its temporary storage in /mnt/sdb1. That's what seemed to happen tonight, but I'm not certain.

Okay, this morning I blanked the BD-RE again (full blank - not fast blank). It took 2 hours. The BD-RE is a 2x and the burner is capable of 12x but Pburn only blanked at about 1x. I told Pburn to put its temporary memory in /mnt/sdc1. When I opened Pburn it apparently created a pburn_symlink_tree directory in both /tmp and mnt/sdc1. (I can't remember for sure but I think I checked that there was no pburn_symlink_tree directory in either place before I started, but there was that directory in both places after Pburn started blanking the disk.) I monitored the two directories for the whole 2 hours that Pburn took to blank the disk but neither one ever contained anything.

Next I burned the same 22 GB of mp3 files onto the 2x speed BD-RE that I'd just blanked. I checked the box for Pburn to overwrite and left the temporary memory at /mnt/sdc1. It took about an hour and a half and went with no problem or error message. This time, there was no pburn_symlink_tree directory created at all.

Encouraged by my success, I thought I'd try burning the exact same 22 GB onto a 6x speed Verbatim BD-R disk, using the same settings. It took a little less than an hour, but with an error message at the end. When I ejected the tray and reloaded it, the disk mounted ok though and appears to contain everything it should. It appears there was a pburn_symlink_tree directory created in /tmp but not in /mnt/sdc1.

Flash
What I did in Pburn 3.7.2 is to auto-set the correct burning command if media is empty (even if corrupted). That means you don't need to check the 'Overwrite existing...' with Pburn 3.7.2.

Regarding the pburn_symlink_tree this is set to /tmp at first run (until an alternative is set). /tmp should be deleted during shutdown. pburn_symlink_tree is not the place where huge amount of data is hold, but only symlinks to the actual files shown in burnlist. This means not all kind of burning needs it, but still might be there as Pburn don't bother to delete it.

I have checked the code a bit to see if your assumption that /tmp is used instead of the set temporary storage. What I found was that is happens if temporary storage is pointed to a VFAT partition. Else I could not find anything. Let's keep an eye on this....

upgraded the Three Headed Dog Puppy with the new Pburn and can confirm that it fixes a bug I found, where sometimes when a rewritable cd was put in for blanking (particularly a puppy linux cdrw) it would not recognise it and say reinsert into the tray, and try again, and again, and again etc..

Over the last few days I've transferred mp3 files from a hard disk to 8 Blu-Ray, plus 2 DVD, disks using Pburn.

The only real complaint I have about how Pburn worked to do this is that I can't drag highlighted directories from a ROX window into the Pburn burn window. The only way I could find to do what I wanted was to highlight a bunch of directories on the hard disk drive, find their count, then, when it added up to 23 GB according to ROX, drag the highlighted directories into an empty directory I had created on another (USB flash) drive.

Transferring 23 GB from a USB hard disk drive to a USB flash drive takes hours in Puppy. I think it might go considerably faster in Windows but I didn't try it yet. After the transfer, I could then put the 23 GB directory in Pburn's burn window to see if it would fit on a Blu-Ray disk (ROX doesn't count the sizes with enough precision to tell.) A bit of adjustment was usually needed to just fill the Blu-Ray disk without overflowing. (At a dollar a pop, I'm not ready to try overburning a Blu-Ray disk yet. )

At the end, I didn't have enough left to fill a Blu-Ray disk so I used 2 DVDs. The last DVD I overburned by about 50 MB. Pburn gave an error message but the DVD seems to contain everything it should.

Wouldn't it be easier to temporarily move them into a directory on the USB hard disk, and then move them out of it afterwards?_________________DEATH TO SPREADSHEETS
- - -
Classic Puppy quotes
- - -
Beware the demented serfers!