Puppy Linux Discussion Forum

[charlie6]

above post continued ...
BUT
if placing gtkdialog-0.8.4 in /usr/bin/ instead , then here get pburn-3.7.13 (as also pburn-3.7.12) running OK ...

I'm a bit puzzled about this (gtkdialog pets placing the application in /usr/sbin then --> pburn returns broken pipr error ; OK if placed in /usr/bin -->?? )

charlie

[Dromeno]

gtkdialog 0.8.3 is named as a dependency. But I can not find a pet for it yet. Does it exist?

[Dromeno]

oops sorry, just found it here

http://www.murga-linux.com/puppy/viewtopic.php?mode=attach&id=63543

[don570]

I got the same pipe error as Charlie6 got when I tried the latest pburn
with Exprimo.

I'll have to check if placing gtkdialog in /usr/bin/ corrects the
problem?? ...but that's odd.

______________________________________________________

[zigbert]

Version 3.7.14
See main post


Changelog 3.7.14
- Bugfix: Rely on ONLY gtkdialog as executable - not gtkdialog4 (thanks to Charlie6 and don570)

[zigbert]

Version 3.7.15
See main post

Changelog
- Bugfix: Calculate size of directory content when tmpdir is on another filesystem than Puppy.
- Bugfix: Calculate free space in bar when tmpdir is on another filesystem than Puppy.

[charlie6]

Hi Sigmund!
this pburn works awesome !

I regularly need to blank cd-rw's (with all these puppies stored since 2008 and remasterings ... ).
I noticed that when selecting «blank complete» (in place of «fast blank») i have also to select the «advanced» thumbnail, and there to click «refresh command» to activate the «all» blanking present in the command line field.

If not, pburn blanks «fast», even if the «complete» checkbox has been checked in the «erase disk» thumbnail.

Some CD-RW's here (Philips brand CD-RW's) need that «workaround»; otherwise they are not full blanked ---> not possible to burn them.
I did not notice this with the Verbatim's CD-RW's.

cheers, Charlie

[zigbert]

Charlie
Thank you for the report
Will look into this


Sigmund

[jamesbond]

Ziggy,

the latest mkisofs from cdrtools (not cdrkit) doesn't support "-allow-limited-size" option, this causes UDF buring to fail if one uses mkisofs from cdrtools instead of cdrkit. I don't know what's the equivalent option, I presume that with cdrtools it will automatically work that way even without that option.

cheers!

[zigbert]

Charlie
I could not see any issues with the blanking command.
Be aware that the command in the 'Advanced' tab only is used if the checkbox 'Allow manual edit' is turned on.

To check this fully, you can look into the file /root/.pburn/tmp/exec. This file holds the executing burn-command.


Do I miss something?
Sigmund

[zigbert]

Jamesbond
Thank you for the report.
I have made a simple check for the -allow-limited-size switch.

func_burn_option line 197

[zigbert]

Version 3.7.16
See main post

Changelog
- Bugfix: Burn UDF with cdr-tools backend (thanks to jamesbond)

[jamesbond]

Thanks Sigmund for your prompt response.
That should fix it.

cheers!

[zigbert]

Version 3.7.17
See main post

Changelog
- Bugfix: Info button in burn-option dialog doesn't work.
- Add finnish (zephyr2) to the credits
- Dependency check should use yellow (not red) for missing optional dependencies.

[gcmartin]

This may have already been answered elsewhere, but, I ran into a use issue on Pburn version 3.7.15 in FATDOG620.

My camera uses mini DVD+RW (30minute - 1.4GB)

I was trying to blank a TDK DVD+RW and when it reach 99.4% of the DVD's disc size, it fails with the following screens below.

Note: as one can see, there is plenty of temp space, even for a 1.4GB disc to be blanked.

PBurn log is follows: