Page 96 of 118
Posted: Tue 29 Jan 2013, 19:27
by 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
gtkdialog 0.8.3
Posted: Thu 31 Jan 2013, 11:30
by Dromeno
gtkdialog 0.8.3 is named as a dependency. But I can not find a pet for it yet. Does it exist?
Found it
Posted: Thu 31 Jan 2013, 11:36
by Dromeno
piping error
Posted: Mon 04 Feb 2013, 21:25
by 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.
______________________________________________________
Posted: Mon 04 Feb 2013, 21:47
by 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)
Posted: Thu 07 Feb 2013, 12:41
by 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.
blanking cd complete
Posted: Sat 09 Mar 2013, 13:13
by 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
Posted: Sat 09 Mar 2013, 20:50
by zigbert
Charlie
Thank you for the report
Will look into this
Sigmund
Posted: Tue 12 Mar 2013, 05:43
by 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!
Posted: Wed 13 Mar 2013, 07:26
by 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
Posted: Wed 13 Mar 2013, 07:38
by zigbert
Jamesbond
Thank you for the report.
I have made a simple check for the -allow-limited-size switch.
func_burn_option line 197
Code: Select all
#Check for huge files (over 4Gb) that requires udf switch on
if [ $UDF = true ] || [ "`find -L "$TMPDIR" -size +4G`" ]; then
UDF_OPTS="-udf"
[ $MKISOFS = genisoimage ] && UDF_OPTS="$UDF_OPTS -allow-limited-size" #only cdrkit uses this switch
UDF=true #activate checkbox if large file is detected
fi
func_build_command line 357
Code: Select all
if [ "$MEDIATYPE" = "DVD" ] && [ "$UDF" = "true" ]; then #support of files bigger than 4GB
[ $MKISOFS = genisoimage ] && echo -n "-allow-limited-size " >> $WORKDIR/parameters #only cdrkit uses this switch
echo -n "-udf " >> $WORKDIR/parameters
fi
Sigmund
Posted: Thu 14 Mar 2013, 18:03
by zigbert
Version 3.7.16
See main post
Changelog
- Bugfix: Burn UDF with cdr-tools backend (thanks to jamesbond)
Posted: Thu 14 Mar 2013, 20:58
by jamesbond
Thanks Sigmund for your prompt response.
That should fix it.
cheers!
Posted: Fri 29 Mar 2013, 16:31
by 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.
Posted: Mon 01 Apr 2013, 04:56
by 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:
Code: Select all
Pburn version 3.7.15
###################################################
COMMAND:
###################################################
growisofs -use-the-force-luke=notray -Z /dev/sr1=/dev/zero
###################################################
OUTPUT:
###################################################
Executing 'builtin_dd if=/dev/zero of=/dev/sr1 obs=32k seek=0'
/dev/sr1: restarting DVD+RW format...
/dev/sr1: "Current Write Speed" is 4.1x1352KBps.
31457280/1463386112 ( 2.1%) @4.0x, remaining 4:33 RBU 100.0% UBU 1.9%
49938432/1463386112 ( 3.4%) @4.0x, remaining 4:14 RBU 100.0% UBU 94.4%
68419584/1463386112 ( 4.7%) @4.0x, remaining 4:04 RBU 100.0% UBU 94.4%
86900736/1463386112 ( 5.9%) @4.0x, remaining 4:13 RBU 100.0% UBU 94.4%
o
o
o
o
o
1398571008/1463386112 (95.6%) @4.0x, remaining 0:11 RBU 100.0% UBU 94.4%
1417052160/1463386112 (96.8%) @4.0x, remaining 0:08 RBU 100.0% UBU 94.4%
1435533312/1463386112 (98.1%) @4.0x, remaining 0:05 RBU 100.0% UBU 94.4%
1454014464/1463386112 (99.4%) @4.0x, remaining 0:01 RBU 100.0% UBU 94.4%
:-[ WRITE@LBA=ae730h failed with SK=5h/LOGICAL BLOCK ADDRESS OUT OF RANGE]: No space left on device
:-( write failed: No space left on device
/dev/sr1: flushing cache
/dev/sr1: stopping de-icing
/dev/sr1: writing lead-out
Here to help
Posted: Sun 07 Apr 2013, 03:28
by charlie6
Hi Sigmund,
launching pburn-3.7.17 from console reports
# pburn
/usr/local/pburn/func_gui_options: line 7: /root/.pburn/pburnhlp-auto: No such file or directory
have then created an empty file /root/.pburn/pburnhlp-auto --> pburn seems running OK
is this correct?
Cheers, Charlie
I did the same charlie - works fine :)
Posted: Mon 08 Apr 2013, 05:14
by Eyes-Only
Hi Charlie6,
I got the exact same problem with pburn 3.7.17 and when trying to boot via cli to see why it wouldn't start I got the same reply. So I made a "dummy file" by that name under "/root/.pburn/" - works fine now!
You just won't get any help documentation under "Help" on the menubar if I remember correctly
until after you've started pburn. See, once you're finally able to do so that dummy file is replaced with a real help file.
At least this is how it worked on my Puppy systems. Anyone else's mileage may vary.
Cheers/Amicalement,
Eyes-Only
"L'Peau-Rouge d'Acadie"
Posted: Mon 08 Apr 2013, 09:07
by charlie6
Bonjour Eyes-only
about
/root/.pburn/pburnhlp-auto: No such file or directory
i also picked-up and copied the
/root/.pburn/pburnhlp-auto
from a former pburn-3.7.15 installation.
--> seems working OK
charlie
Posted: Mon 08 Apr 2013, 16:40
by zigbert
Hello guys
Thank you for reporting
Would you please test 3.7.18
It should hopefully fix it
Sigmund
Posted: Tue 09 Apr 2013, 17:41
by Eyes-Only
That fixed it Zigbert! Thanks so much - and also for everything that you do to make Puppy the very special distro for us that it is my Puppian Friend!
Cheers/Amicalement,
Eyes-Only
"L'Peau-Rouge"