pBurn 4.3.19
Ok, here is a test release for those who wants to burn/convert NRG images.
- Attachments
-
- pburn-3.5.3.pet
- (66.57 KiB) Downloaded 433 times
-
- Posts: 4
- Joined: Thu 29 Dec 2011, 01:37
Re: Source data lost using Pburn 3.4.1
The file system is ext3zigbert wrote:Hmmm, This is weird. The emergency stop is not meant to bring you back to the main window. What kind of filesystem are you using?dougblackburn wrote:Configuration:
Wary Puppy 5.2.2 full hard drive installation
Micron Millenium 767mb ram, 733mgz Pentium III
20gb hard drive about 15% used
Problem description:
I had created a directory /dougstuff. This directory had many sub-directories and files. I opened Pburn and right clicked this directory to select it. Then I clicked on the burn drop down menu and selected to burn a data cd. When the next screen came up I clicked on the burn icon to start the burn. During what looked like a pre-burn process I changed my mind and hit the emergency stop. From previous experience I knew the actual burn had not started. The Pburn application re-displayed the selection screen. I de-selected /dougstuff. Then I quit Pburn. At this point I was going to zip /dougstuff, but it was gone. I couldn't find it with the zip application, using ROX, or using xterm. I used Photorec help restore /dougstuff. Then, I created another directory /dougtest and copied dougstuff to it. Now I had /dougstuff and /dougtest/dougstuff. Then I burned /dougtest/dougstuff (without hitting the emergency stop) successfully. Now I was ready to see if I could duplicate this problem. So, I selected /dougtest/dougstuff for burn and hit the emergency stop during the pre-burn process. But, Pburn did not send me back to the selection screen. It terminated. So, I opened Pburn from the puppy menu again. A dialogue box came up asking me if I wanted to clear temporary storage and start again. I replied yes. The selection screen was displayed. At this point, I checked to see if /dougstuff and dougtest/dougstuff were still available. They were still available. I had to hit the emergency stop about 4 times in order to get it to finally return to the selection screen instead of terminating. When it did return to the selection screen, I de-selected /dougtest/dougstuff. Then I checked to see if /dougtest/dougstuff was still available. To my surprise /dougtest/dougstuff was available, but /dougstuff was gone. So, I restored /dougstuff from /dougtest/dougstuff and tried the whole thing again selecting /dougtest/dougstuff to burn. This time it took me many emergency stops to finally get the application to return to the selection screen instead of terminating. I am still not sure at what point in the process the emergency stop has to be hit in order to return to the selection screen. Finally, when it returned to the selection screen, I de-selected /dougtest/dougstuff and /dougstuff was gone again.
Conclusion:
Source date is lost when the emergency stop returns the user to the selection screen. It is possible the source data was gone upon return to the selection screen or before. I always checked my source data after de-selection.
Doug
Sigmund
Version 3.6.0
See main post
Changelog
- Optional support of NRG-image (nero format) if nrg2iso is installed. (thanks to 01micko)
- Optional tool: Convert NRG to ISO.
- Verify iso-image burnt mulitsession to CD.
- Move locales to /usr/share/locale/.
- Bugfix: Ask to blank disc if required when entering burn options (bug introduced in 3.5.0).
- Bugfix: Define Audio-CD correct in statusbar.
- NLS: Added: LOC_IMAGE, 137, 205, 356, 357
- NLS: Changed: LOC126, 306, 307, 322, 351
- NLS: Removed: LOC_ISO, 124
- DOC: Multisession: Now supports verifing (md5sum) of CD-R(W).
See main post
Changelog
- Optional support of NRG-image (nero format) if nrg2iso is installed. (thanks to 01micko)
- Optional tool: Convert NRG to ISO.
- Verify iso-image burnt mulitsession to CD.
- Move locales to /usr/share/locale/.
- Bugfix: Ask to blank disc if required when entering burn options (bug introduced in 3.5.0).
- Bugfix: Define Audio-CD correct in statusbar.
- NLS: Added: LOC_IMAGE, 137, 205, 356, 357
- NLS: Changed: LOC126, 306, 307, 322, 351
- NLS: Removed: LOC_ISO, 124
- DOC: Multisession: Now supports verifing (md5sum) of CD-R(W).
Be aware that version 3.6.0 introduce a new optional dependency - nrg2iso. 01micko has compiled it, and you will find a link to it from the main post....
....or here: http://murga-linux.com/puppy/viewtopic. ... 199#626199
Sigmund
....or here: http://murga-linux.com/puppy/viewtopic. ... 199#626199
Sigmund
FREE_SIZE
@zigbert
"func -available_size" sometimes fails because "df -m | grep ' /$'" can match 2 lines, in some case maybe PUPMODE=7 (and may depend on the kernel).
The code in 'func' (lines 1199-1204) could be more simple:
FREE_SIZE=`df -m "$TMPOUTDIR" 2> /dev/null | tail -n1 | tr -s " " | cut -s -f 4 -d ' '`
[ "$FREE_SIZE" ] || FREE_SIZE=0 #precaution
See:
"func -available_size" sometimes fails because "df -m | grep ' /$'" can match 2 lines, in some case maybe PUPMODE=7 (and may depend on the kernel).
Code: Select all
# df -m | grep ' /$'
rootfs 1648 15 1634 1% /
unionfs 1648 15 1634 1% /
FREE_SIZE=`df -m "$TMPOUTDIR" 2> /dev/null | tail -n1 | tr -s " " | cut -s -f 4 -d ' '`
[ "$FREE_SIZE" ] || FREE_SIZE=0 #precaution
See:
Code: Select all
# df -m /root/my-documents/tmp
Filesystem 1M-blocks Used Available Use% Mounted on
unionfs 1648 15 1634 1% /
Code: Select all
# df -m /mnt/home/tmp
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/sda3 83142 9248 69671 12% /initrd/mnt/dev_save
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
checking TMPOUTDIR
But i think we are better to check more, if the '/mnt/*' is really mounted.
or something...
Code: Select all
NOTMOUNTED=""
case "$TMPOUTDIR" in
/mnt/*) MNTPNT=$(df "$TMPOUTDIR" 2>/dev/null | grep -o '[^ ]*/mnt/.*')
[ "$MNTPNT" ] || NOTMOUNTED="y"
;;
esac
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
jamesbond suggests a new and faster way of 'Fast' blanking rewritable DVD/BD. The problem is that both of us only had DVD+RW discs to play with. If you have any DVD-RW or BD-RE and wants to help out, please read on....
The existing code in Pburn to blank/erase a DVD/BD disc (the fast and dirty way) is by
James reports endless of waiting for him and shares the alternative code
This only erase the first Mb of the disc....
Personally I haven't had much trouble with the first command, but my test shows that the new command is much faster.
Please test the new command with DVD-RW / BD-RE and report back. Time is interesting, but if blanking actually was successfully is even more important. For DVD+RW things seems to be just fine.
Thank you all
Sigmund
The existing code in Pburn to blank/erase a DVD/BD disc (the fast and dirty way) is by
Code: Select all
dvd+rw-format -force /dev/sr0
Code: Select all
dd if=/dev/zero of=/dev/sr0 bs=32k count=32
Personally I haven't had much trouble with the first command, but my test shows that the new command is much faster.
Code: Select all
# time dvd+rw-format -force /dev/sr0
* BD/DVD±RW/-RAM format utility by <appro@fy.chalmers.se>, version 7.1.
* 4.7GB DVD+RW media detected.
* formatting 92.3|
real 0m18.088s
user 0m0.000s
sys 0m0.003s
#
#
# time dd if=/dev/zero of=/dev/sr0 bs=32k count=32
32+0 records in
32+0 records out
1048576 bytes (1.0 MB) copied, 3.75384 s, 279 kB/s
real 0m3.784s
user 0m0.007s
sys 0m0.000s
#
Thank you all
Sigmund
shinobar
If temporary storage points to a not mounted directory, there will show up a message when startup Pburn telling that temporary storage is small. This is not exactly the correct message, but still a warning of something wrong. MAYBE this is the place for enhanced checking.
See line 117 of /usr/local/pburn/pburn
Sigmund
If temporary storage points to a not mounted directory, there will show up a message when startup Pburn telling that temporary storage is small. This is not exactly the correct message, but still a warning of something wrong. MAYBE this is the place for enhanced checking.
See line 117 of /usr/local/pburn/pburn
Sigmund
shinobar
Ok, a bug. There is already a check for missing temporary storage but it fails if checking also finds the storage too small. I have switched the checking order so that missing dir is detected even if size of storage is small.
has now become
Ok, a bug. There is already a check for missing temporary storage but it fails if checking also finds the storage too small. I have switched the checking order so that missing dir is detected even if size of storage is small.
Code: Select all
#missing temporary-storage directory
if [ ! -d "$OUTDIR" ]; then
GUI_LOW_TEMP="<text use-markup=\"true\"><label>\"$LOC344\"</label></text>$GUI_TEMPORARY_STORAGE"
STARTUP_CHECK=true
fi
#let's check if free space is bigger than 10GB free space.
. $APPDIR/func -available_size
if [ $FREE_SIZE -lt 10000 ]; then
GUI_LOW_TEMP="<text use-markup=\"true\"><label>\"$LOC333\"</label></text>$GUI_TEMPORARY_STORAGE"
STARTUP_CHECK=true
fi
Code: Select all
#let's check if free space is bigger than 10GB free space.
. $APPDIR/func -available_size
if [ $FREE_SIZE -lt 10000 ]; then
GUI_LOW_TEMP="<text use-markup=\"true\"><label>\"$LOC333\"</label></text>$GUI_TEMPORARY_STORAGE"
STARTUP_CHECK=true
fi
#missing temporary-storage directory
if [ ! -d "$OUTDIR" ]; then
GUI_LOW_TEMP="<text use-markup=\"true\"><label>\"$LOC344\"</label></text>$GUI_TEMPORARY_STORAGE"
STARTUP_CHECK=true
fi
I accidently tried to burn an ISO on a machine that
only had a player not a burner
There was no warning message. I noticed from the
device's external LED light that no burning was taking place
and the console message didn't mention any burning either
so I realized what was happening but an inexperienced user
would have been very puzzled.
So is there any way to warn a user that a burner isn't present?
Does a device name with 'CD-ROM' imply that a burn isn't possible?
Here's the device that caused the problem.
___________________________________________________
When I was burning the ISO (which was bootable)
pburn didn't mention anywhere that the
resulting disk would be bootable. If there was a message
saying clearly that the burnt disk was 'Bootable' that would clear
up any confusion.
___________________________________________
only had a player not a burner
There was no warning message. I noticed from the
device's external LED light that no burning was taking place
and the console message didn't mention any burning either
so I realized what was happening but an inexperienced user
would have been very puzzled.
So is there any way to warn a user that a burner isn't present?
Does a device name with 'CD-ROM' imply that a burn isn't possible?
Here's the device that caused the problem.
___________________________________________________
When I was burning the ISO (which was bootable)
pburn didn't mention anywhere that the
resulting disk would be bootable. If there was a message
saying clearly that the burnt disk was 'Bootable' that would clear
up any confusion.
___________________________________________
Bad Block Area
zigbert wrote:jamesbond suggests a new and faster way of 'Fast' blanking rewritable DVD/BD. The problem is that both of us only had DVD+RW discs to play with. If you have any DVD-RW or BD-RE and wants to help out, please read on....
The existing code in Pburn to blank/erase a DVD/BD disc (the fast and dirty way) is byJames reports endless of waiting for him and shares the alternative codeCode: Select all
dvd+rw-format -force /dev/sr0
This only erase the first Mb of the disc....Code: Select all
dd if=/dev/zero of=/dev/sr0 bs=32k count=32
Personally I haven't had much trouble with the first command, but my test shows that the new command is much faster.Please test the new command with DVD-RW / BD-RE and report back. Time is interesting, but if blanking actually was successfully is even more important. For DVD+RW things seems to be just fine.Code: Select all
# time dvd+rw-format -force /dev/sr0 * BD/DVD±RW/-RAM format utility by <appro@fy.chalmers.se>, version 7.1. * 4.7GB DVD+RW media detected. * formatting 92.3| real 0m18.088s user 0m0.000s sys 0m0.003s # # # time dd if=/dev/zero of=/dev/sr0 bs=32k count=32 32+0 records in 32+0 records out 1048576 bytes (1.0 MB) copied, 3.75384 s, 279 kB/s real 0m3.784s user 0m0.007s sys 0m0.000s #
Thank you all
Sigmund
Will Test but concerned this will cause confusion on the 750M or so area used for bad block. It only gets written to if the hardware detects an area of a UDF needs to be remapped.
Widgets of Pburn displayed reversed left to right and top
Just FYI,
Put PBurn has the most wild mix-up of the ARM based image of puppy in its dialog.
Not only are the top section on the bottom, Left sections are on the Right.
Put PBurn has the most wild mix-up of the ARM based image of puppy in its dialog.
Not only are the top section on the bottom, Left sections are on the Right.
Yes, that gtkdialog issue was discussed on Barry's blog a while back.
Funnily enough, I saw a similar problem with gtkbuilder based vala guis being reversed in Puppy 4.x.
Funnily enough, I saw a similar problem with gtkbuilder based vala guis being reversed in Puppy 4.x.
Do you know a good gtkdialog program? Please post a link here
Classic Puppy quotes
ROOT FOREVER
GTK2 FOREVER
Classic Puppy quotes
ROOT FOREVER
GTK2 FOREVER
/dev/cdrom is often (usually?) created for any type of optical drive. Some programs use it when they want to play a CD or something.
Do you know a good gtkdialog program? Please post a link here
Classic Puppy quotes
ROOT FOREVER
GTK2 FOREVER
Classic Puppy quotes
ROOT FOREVER
GTK2 FOREVER
Version 3.6.1 is uploaded
See main post
Changelog
- Move native language file to /usr/local/pburn (thanks to shinobar)
- Bugfix: Improved detection of free size of temporary storage. (thanks to shinobar)
- Bugfix: Show message at startup about missing temporary storage if storage is smaller than recommended. (thanks to shinobar)
See main post
Changelog
- Move native language file to /usr/local/pburn (thanks to shinobar)
- Bugfix: Improved detection of free size of temporary storage. (thanks to shinobar)
- Bugfix: Show message at startup about missing temporary storage if storage is smaller than recommended. (thanks to shinobar)
Hi,
It seems that locale file is missing in pburn 3.6.1
Regards,
kfgz
It seems that locale file is missing in pburn 3.6.1
Code: Select all
$ pburn
/usr/share/pburn/pburn: line 88: /usr/share/pburn/locales: No such file or directory
kfgz