Which Puppy versions would have that? I know I could probably download and install a pet for it on quite a few older versions, but sometimes it's handy to know if one has to.zigbert wrote:Version 3.7.13
Depends on gtkdialog 0.8.3
pBurn 4.3.19
Zhaan - AMD K6 2 500, 512MB RAM, ATI Rage 128 VR. Full install Wary 5.5 [url=http://tinyurl.com/dy66kh8]HardInfo Report[/url]
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
- OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
Upup presice has it already, and the upcoming Slacko will have it too.Jades wrote:Which Puppy versions would have that? I know I could probably download and install a pet for it on quite a few older versions, but sometimes it's handy to know if one has to.zigbert wrote:Version 3.7.13
Depends on gtkdialog 0.8.3
Sigmund
Ok, fixed.OscarTalks wrote:Hello Sigmund
So have you taken the latest Pburn (3.7.12) for gtkdialog-0.8.0 down from the repo / website?
If I want to update Pburn I must now also update gtkdialog as well (eg in Slacko 5.3.3)?
With Pmusic you left 2.6.7 available.
3.7.12 is reuploaded and available from the main post
Sigmund
- charlie6
- Posts: 1230
- Joined: Mon 30 Jun 2008, 04:03
- Location: Saint-Gérard / Walloon part of Belgium
Hi Sigmund,
pburn-3.7.13 does not start here:
on dPup-Exprimo-5X3.4.12 (with kernel k3.4.2), i have installed
gtkdialog-exprimo-0.8.4.pet
and
pburn-3.7.13.pet
...should work as gtkdialog is at least 0.8.3
here are the terminal returned comments
it tells: write error: Broken pipe ... continuously
I get the same using version 3.7.12.
thanks for any advice
pburn-3.7.13 does not start here:
on dPup-Exprimo-5X3.4.12 (with kernel k3.4.2), i have installed
gtkdialog-exprimo-0.8.4.pet
and
pburn-3.7.13.pet
...should work as gtkdialog is at least 0.8.3
here are the terminal returned comments
it tells: write error: Broken pipe ... continuously
I get the same using version 3.7.12.
thanks for any advice
- Attachments
-
- capture16706.jpg
- (29.27 KiB) Downloaded 670 times
- charlie6
- Posts: 1230
- Joined: Mon 30 Jun 2008, 04:03
- Location: Saint-Gérard / Walloon part of Belgium
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
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
gtkdialog 0.8.3 is named as a dependency. But I can not find a pet for it yet. Does it exist?
piping error
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.
______________________________________________________
with Exprimo.
I'll have to check if placing gtkdialog in /usr/bin/ corrects the
problem?? ...but that's odd.
______________________________________________________
Last edited by don570 on Tue 05 Feb 2013, 21:18, edited 1 time in total.
- charlie6
- Posts: 1230
- Joined: Mon 30 Jun 2008, 04:03
- Location: Saint-Gérard / Walloon part of Belgium
blanking cd complete
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
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
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!
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!
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
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
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
Jamesbond
Thank you for the report.
I have made a simple check for the -allow-limited-size switch.
func_burn_option line 197
func_build_command line 357
Sigmund
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
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:Here to help
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
- Attachments
-
- Request2format.png
- Select Blank DVD button near top of window
- (47.45 KiB) Downloaded 549 times
-
- Request2format-error_msg.png
- Error message
- (25.94 KiB) Downloaded 537 times