pBurn 4.3.19
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
- charlie6
- Posts: 1230
- Joined: Mon 30 Jun 2008, 04:03
- Location: Saint-Gérard / Walloon part of Belgium
Hi Sigmund,
on dpup-wheezy-3.5.2.5as also on 3.5.2.11:
using PBurn-4.3.5, blanking a DVD-rw returns the following log:
What would i have to do?
Thanks for answering
Greetings!
Charlie
on dpup-wheezy-3.5.2.5as also on 3.5.2.11:
using PBurn-4.3.5, blanking a DVD-rw returns the following log:
Do i have to care about the last lines reporrting «failed»?Pburn version 4.3.5
###################################################
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: "Current Write Speed" is 4.1x1352KBps.
35782656/4706074624 ( 0.8%) @4.1x, remaining 13:03 RBU 100.0% UBU 2.0%
54099968/4706074624 ( 1.1%) @4.0x, remaining 14:19 RBU 100.0% UBU 53.1%
71991296/4706074624 ( 1.5%) @3.9x, remaining 13:56 RBU 100.0% UBU 63.3%
90603520/4706074624 ( 1.9%) @4.0x, remaining 13:35 RBU 100.0%
... etc ...
4672552960/4706074624 (99.3%) @4.0x, remaining 0:06 RBU 100.0% UBU 85.7%
4691099648/4706074624 (99.7%) @4.0x, remaining 0:02 RBU 100.0% UBU 55.1%
:-[ WRITE@LBA=231020h failed with SK=5h/INVALID ADDRESS FOR WRITE]: Invalid argument
write failed: Invalid argument
/dev/sr1: flushing cache
/dev/sr1: writing lead-out
What would i have to do?
Thanks for answering
Greetings!
Charlie
Charlie
Question 1:
After blanking, did pBurn show the error or finish dialog? I suspect the Error dialog, since you have posted here
Question 2:
Did the DVD work after blanking, or ... ?
If yes is the answer, I should think of more information in the error-message for this behavior.
As said in the blanking dialog (with red text); blanking of DVD's might be troublesome for some burner devices. For those, the solution is to overwrite existing data. This is done in the burn-option-dialog.
Sigmund
Question 1:
After blanking, did pBurn show the error or finish dialog? I suspect the Error dialog, since you have posted here
Question 2:
Did the DVD work after blanking, or ... ?
If yes is the answer, I should think of more information in the error-message for this behavior.
As said in the blanking dialog (with red text); blanking of DVD's might be troublesome for some burner devices. For those, the solution is to overwrite existing data. This is done in the burn-option-dialog.
Sigmund
- charlie6
- Posts: 1230
- Joined: Mon 30 Jun 2008, 04:03
- Location: Saint-Gérard / Walloon part of Belgium
Hello Sigmund !
here using wheezy-3.5.2.5 + latest 01micko pup_event_files-140714.tar.gz (seems working nice)
PBurn reports «mkisofs: No such file or directory» ... mkisofs is well present on my system ...! (see attached pBurn18jui2014.log.tar.gz )
thanks in advance for your time!
Greetings
Charlie
here using wheezy-3.5.2.5 + latest 01micko pup_event_files-140714.tar.gz (seems working nice)
it finishes dialog (see shot hereunder)zigbert wrote:Question 1:
After blanking, did pBurn show the error or finish dialog? I suspect the Error dialog, since you have posted here
it works: i could re-use the DVD and burn datas on it again.zigbert wrote:Question 2:
Did the DVD work after blanking, or ... ?
If yes is the answer, I should think of more information in the error-message for this behavior.
I tried to overwrite existing datas and got the below documented error.zigbert wrote:As said in the blanking dialog (with red text); blanking of DVD's might be troublesome for some burner devices. For those, the solution is to overwrite existing data. This is done in the burn-option-dialog.
Sigmund
PBurn reports «mkisofs: No such file or directory» ... mkisofs is well present on my system ...! (see attached pBurn18jui2014.log.tar.gz )
thanks in advance for your time!
Greetings
Charlie
- Attachments
-
- pburn435_overwrite.jpg
- overwriting
- (45.25 KiB) Downloaded 661 times
-
- pBurn18jui2014.log.tar.gz
- overswriting log
- (862 Bytes) Downloaded 282 times
-
- pburn-4.3.5.jpg
- blanking complete
- (49.96 KiB) Downloaded 680 times
Hey Sigmund
I noticed that pBurn has a broken symlink:
/root/.config/rox.soureforge.net/OpenWith/.application_x-cd-image/Burn with pBurn points to ../../../../usr/local/apps/Pburn, but there is pBurn.
Another thing - have you been considering to suppress those ugly chars in log window after "Last chance to quit" msg?
I've got quite good results using this in func_exec (line 27):
Thanks &
Greetings!
I noticed that pBurn has a broken symlink:
/root/.config/rox.soureforge.net/OpenWith/.application_x-cd-image/Burn with pBurn points to ../../../../usr/local/apps/Pburn, but there is pBurn.
Another thing - have you been considering to suppress those ugly chars in log window after "Last chance to quit" msg?
I've got quite good results using this in func_exec (line 27):
Code: Select all
$WORKDIR/exec | tr -s '\b' '\n' >> $LOG 2>&1
Greetings!
- Attachments
-
- Screenshot.jpg
- (60.9 KiB) Downloaded 808 times
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]
[b][color=green]Omnia mea mecum porto.[/color][/b]
Charlie
The blanking process (backend) did not report error (which is a bit strange when looking at your log. The output is pointed to stdout, not stderr.), so pBurn wisely does not see this as an error. We should therefor expect the disc to be useful. The log output is still a bit awkward...
Your overwrite output is sent to stderr, and is grabbed by the pBurn error-checker. I have added the following Error-msg for your case:
Problem writing to disc
Please blank disc in 'Blank complete' mode.
Sigmund
The blanking process (backend) did not report error (which is a bit strange when looking at your log. The output is pointed to stdout, not stderr.), so pBurn wisely does not see this as an error. We should therefor expect the disc to be useful. The log output is still a bit awkward...
Your overwrite output is sent to stderr, and is grabbed by the pBurn error-checker. I have added the following Error-msg for your case:
Problem writing to disc
Please blank disc in 'Blank complete' mode.
Sigmund
That's strange, Slacko-5.7 + busybox tr here as well...zigbert wrote:When it comes to the 'tr' fix, I can't get it to work. It strips all info in $LOG, and log-box shows no progress. I only have the busybox 'tr', and I guess that explains it all. I am running Slacko 5.7
What exact action were you doing while testing this?
In my case it was blanking and then burning an ISO image onto 80mm mini CD-RW.
Hmm, did you try to invoke this directly?
Code: Select all
cdrecord dev=/dev/sr0 blank=all 2>&1 | tr -s '\b' '\n'
Anyway, it's not so crucial, after all.
Greetings!
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]
[b][color=green]Omnia mea mecum porto.[/color][/b]
Version 4.3.6
See main post
Changelog
- Added Error-msg if growisofs wants you to do a full blanking. (Thanks to Charlie6)
- Bugfix: Export iso with only 1 non-video-file in burnlist gives option to build video-iso.
- Bugfix: Broken symlink to rox:OpenWith - Burn with pBurn. (thanks to SFR)
- Bugfix: Removed dead NLS-link from pet. (thanks to rg66)
See main post
Changelog
- Added Error-msg if growisofs wants you to do a full blanking. (Thanks to Charlie6)
- Bugfix: Export iso with only 1 non-video-file in burnlist gives option to build video-iso.
- Bugfix: Broken symlink to rox:OpenWith - Burn with pBurn. (thanks to SFR)
- Bugfix: Removed dead NLS-link from pet. (thanks to rg66)
In 4.3.6 - "ps | grep" etc to detect running instance of Xdialog, etc only works if you use busybox version of ps. This is the case in puppy (ps is a symlink to busybox) but may not be true on others (=Fatdog) where ps is actually the full ps. As a result, dialogs are not closed when they should be.
The fix is simple, use "busybox ps" instead of "ps" on line 99, and 305 on func_exec, line 326 on "pburn" and line 383 on func_gui. Doing this will not harm other puppies anyway.
For your consideration
The fix is simple, use "busybox ps" instead of "ps" on line 99, and 305 on func_exec, line 326 on "pburn" and line 383 on func_gui. Doing this will not harm other puppies anyway.
For your consideration
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]
jamesbond
In the more recent code I have instead used the following code which works with the full ps.
Could you test if this works ok for you. pBurn should not rely on busybox.
Sigmund
In the more recent code I have instead used the following code which works with the full ps.
Code: Select all
grep -F 'Xdialog' <<< $(ps -eo pid,command)
Sigmund
Agreed - the idea is that it should work equally well with or without busybox.zigbert wrote:pBurn should not rely on busybox.
On a quick test, it seems to work. But "busybox ps" doesn't recognise "-eo", so puppies that symlink ps to busybox will fail this. One format that will work equally well is "ps -ef" but the output format is different ...Could you test if this works ok for you. pBurn should not rely on busybox.Code: Select all
grep -F 'Xdialog' <<< $(ps -eo pid,command)
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]
Problem to burn BluRay-Data-Discs
May be I did something wrong, but I'm not able to burn a BR with success.
I want to use BluRay-Discs to backup my important files and verify the burned data.
First, I used pBurn 3.7.5 (which came with Precise 5.4.3) - Error at about 98 %
Second, I updated pBurn to 4.3.6 (still in Precise 5.4.3) - but don't get a start-burn-pop-up. After pressing the burn-botton, pBurn displays a pop-up, telling me that the burn-command will be build, but nothing happens after that.
Third, I gave porteus (3.0.1) a try which comes with pburn 4.0.1 - the error occured while pBurn tried to close the disc.
The BRs with error in burn-process are readable. So I have serveral burned BluRays with data but I never know if all is burned and if the burned data are ok.
What can I do?
I want to use BluRay-Discs to backup my important files and verify the burned data.
First, I used pBurn 3.7.5 (which came with Precise 5.4.3) - Error at about 98 %
Second, I updated pBurn to 4.3.6 (still in Precise 5.4.3) - but don't get a start-burn-pop-up. After pressing the burn-botton, pBurn displays a pop-up, telling me that the burn-command will be build, but nothing happens after that.
Third, I gave porteus (3.0.1) a try which comes with pburn 4.0.1 - the error occured while pBurn tried to close the disc.
The BRs with error in burn-process are readable. So I have serveral burned BluRays with data but I never know if all is burned and if the burned data are ok.
What can I do?
[color=blue][size=75]Toshiba Satallite M30X-124 | ATI Mobility Radeon 9700 | Intel PRO/Wireless 2200BG
Most Linux need special boot options to boot on this laptop: i8042.nomux=1 highres=off nohz=off irqpoll[/size][/color]
Most Linux need special boot options to boot on this laptop: i8042.nomux=1 highres=off nohz=off irqpoll[/size][/color]
OK. I tried Slacko 5.7 (pBurn 4.3.4 is inside) - with the same Result:zigbert wrote:Either go from precise to slacko or another more modern Puppy, or install cdrtools to your Precise.
Any other hints befor I give Windows a try?antilet wrote:Third, I gave porteus (3.0.1) a try which comes with pburn 4.0.1 - the error occured while pBurn tried to close the disc.
[color=blue][size=75]Toshiba Satallite M30X-124 | ATI Mobility Radeon 9700 | Intel PRO/Wireless 2200BG
Most Linux need special boot options to boot on this laptop: i8042.nomux=1 highres=off nohz=off irqpoll[/size][/color]
Most Linux need special boot options to boot on this laptop: i8042.nomux=1 highres=off nohz=off irqpoll[/size][/color]