pBurn 4.3.19
otropogo
Thank you for the detailed feedback.
I am sorry to say that I am not the person to help you with this one...
I do write guis for the Puppy environment, and are most often strict to the existing backends in Puppy. But backends also evolve, and sometimes I take benefit of the recent facilities.
I do work alot with improving Puppy-code, but I have acknowledged my limitations, and won't use my time to offer backends for all the different Puppies/distros.
Sigmund
Thank you for the detailed feedback.
I am sorry to say that I am not the person to help you with this one...
I do write guis for the Puppy environment, and are most often strict to the existing backends in Puppy. But backends also evolve, and sometimes I take benefit of the recent facilities.
I do work alot with improving Puppy-code, but I have acknowledged my limitations, and won't use my time to offer backends for all the different Puppies/distros.
Sigmund
pburn uninstalls and upgrades
Excuse me if I've hit yet another foul ball, but perhaps the following might interest you, or at least other lupu users of pburn.zigbert wrote:otropogo
Thank you for the detailed feedback.
I am sorry to say that I am not the person to help you with this one...
I do write guis for the Puppy environment, and are most often strict to the existing backends in Puppy. But backends also evolve, and sometimes I take benefit of the recent facilities.
I do work alot with improving Puppy-code, but I have acknowledged my limitations, and won't use my time to offer backends for all the different Puppies/distros.
Sigmund
Following Playdayz' suggestions on how to safely merge lupupluslibre with my existing lupu installations, I embarked carefully on the uninstallation of pburn 3.51, noting that pet manager showed that versions 3.4.3, 3.5.0, and 3.5.1 had all been installed and never uninstalled.
Playdayz warned me that uninstalling an earlier version would likely disable any later installations as well by removing some essential elements (if I understood correctly!). And so I proceeded in reverse order, expecting the removal of 3.5.1 to leave me with 3.5.0. However, when I reopened pburn, it identified itself as v. 3.3.4, which I presume was the version bundled with lupu5.2.8 originally.
I then uninstalled Pburn 3.4.3, which was followed by a popup saying "nothing to uninstall...not installed yet", followed by pburn3.5.0, which only gave the "successfully uninstalled' popup.
Finally, I tried to install Pburn 3.5.2, but instead of the option to open the file with package manager, the default file displayed was pupzip.
I had to save the pet to disk before I could install it with package manager. Usually this is done online.
Happily, pburn 3.5.2 opens (in lupupluslibre, that is).
However, I've been unable to find a way to get disk information on DVD+RW disks in the second burner (sr1, on the usb2.0 port). The "info" tab only shows the condition of the DVD+RW disk in sr0.
I've tried repeatedly to get around this by means of the "preferences/burner device tabs", selecting sr1 as the "burner", saving the choice, and then clicking on the "info" tab again. However, only the info on the disk in sr0 is displayed.
It's not the disks, because switching them gives the same result. Nor is it that pburn doesn't sense the disk in sr1, as it gives a warning if the disk has not been loaded. Very frustrating and confusing, especially as the disk info popup doesn't show which burner is being described.
NB: After playing with this function for a while, the info tab stopped working at all, displaying :
"media type: none"
"no writeable media"
in both sr1 and sr0 for the same disks for which it had shown used and free space (albeit only in sr0) only minutes before.
otropogo@gmail.com facebook.com/otropogo
otropogo
Hmmm, your sr1 might not be detected corrected.
Will you please execute these lines in a terminal and post the result here?
This should give us a some brief information.
Thank you
Sigmund
Hmmm, your sr1 might not be detected corrected.
Will you please execute these lines in a terminal and post the result here?
Code: Select all
ls -1 /sys/block | grep sr
Code: Select all
cat /sys/block/sr1/device/vendor
Code: Select all
cat /sys/block/sr1/device/model
Code: Select all
probedisk
Thank you
Sigmund
-
- Posts: 4
- Joined: Thu 29 Dec 2011, 01:37
Source data lost using Pburn 3.4.1
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
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
sh-4.1# ls -1 /sys/block | grep srzigbert wrote:otropogo
Hmmm, your sr1 might not be detected corrected.
Will you please execute these lines in a terminal and post the result here?Code: Select all
ls -1 /sys/block | grep sr
Code: Select all
cat /sys/block/sr1/device/vendor
Code: Select all
cat /sys/block/sr1/device/model
This should give us a some brief information.Code: Select all
probedisk
Thank you
Sigmund
sr0
sr1
sh-4.1# cat /sys/block/sr1/device/vendor
TSSTcorp
sh-4.1# cat /sys/block/sr1/device/model
CD/DVDW SH-S162L
sh-4.1# probedisk
/dev/sda|drive|ATA WDC WD2500LB-55E
/dev/sr0|optical|HL-DT-STDVDRAM GSA-H10N
/dev/sr1|optical|TSSTcorpCD/DVDW SH-S162L
I ran a few more tests :
I tried to mount one of the DVD+RW disks in the sr1 burner with Pmount. Repeated tries all resulted in "ERROR:unable to mount SR1". When placed in sr0, pmount mounted it.
It then tried putting a CD-RW disk in sr1. Again, pburn would not give its information with another disk in sr0.
However, when I left sr0 empty, pburn finally showed the CD-RW's condition.
But when I tried the same trick with the DVD+RW disk, Disc info reported:
mediatype none...no writable media.
When I move it to sr0, it mounts fine with pmount, but pburn continues to give the "no writable media" info report, regardless of whether sr0 or sr1 is selected as the burner device.
When I put the CD-RW back in sr1, info gives the sr1 media information, although sr0 is still selected as burner. But when I close and reopen pburn, then, finally, the media info on the DVD-RW is displayed (both disks are blank). But then the info for the sr1 media is once again inaccessible, even when select it as the burning device.
Hope you can make some sense of this.
otropogo@gmail.com facebook.com/otropogo
NRG File support
Okay Sigmund Berglund i got it. Im now already erase my disc using Pburn. Does Pburn can burn NRG image to disc?
Re: Source data lost using Pburn 3.4.1
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
Re: NRG File support
No it does not, - I don't even know what a NRG-image is.mistfire wrote:Does Pburn can burn NRG image to disc?
Sigmund
NRG is the Nero proprietary format for a CD disk image. When I first learned what a disk image was I made a few of those.. thereafter they were useless to me!
Puppy Linux Blog - contact me for access
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
Re: NRG File support
Nrg2Iso can be used for that. (This guy also has some useful utils for ISO burning.)zigbert wrote:No it does not, - I don't even know what a NRG-image is.mistfire wrote:Does Pburn can burn NRG image to disc?
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind
Little modifications on pburn
zigbert is it possible to integrate nrg2iso as optional add-on in pburn? If the user burn an NRG image on pburn, it converts to ISO first before burn it to Disc. This integration is good for the newbies in pburn.
By the way is it ok to you that you must change the Button label "Blank Disc" to "Erase Disc" to make it more understandable?
I suggest than pburn must be distributed in all-in-one package where its core dependencies are included in the packages if it is possible
By the way is it ok to you that you must change the Button label "Blank Disc" to "Erase Disc" to make it more understandable?
I suggest than pburn must be distributed in all-in-one package where its core dependencies are included in the packages if it is possible
Support of NRG should be doable with nrg2iso. (thank you Dougal)
Does there exist a compiled pet?
Can anyone point me to an (small!!!) NRG image? I need something to test with, and I have no access to neither Nero or Windows.
Dougal also lighted the way to support DAA, GBI and UIF (never heard of any of those ) .... if there is any interest ...
Sigmund
Does there exist a compiled pet?
Can anyone point me to an (small!!!) NRG image? I need something to test with, and I have no access to neither Nero or Windows.
Dougal also lighted the way to support DAA, GBI and UIF (never heard of any of those ) .... if there is any interest ...
Sigmund
Ok, so I compiled nrg2iso from some debian source + patches
source: http://packages.qa.debian.org/n/nrg2iso.html
I made an .nrg image of a slacko iso image in Windows.. it seemed to work ok, then I booted back into Puppy and converted it back from nrg to iso. It mounted ok, but I didn't burn as the md5 did not match the original. The iso size is about 150 bytes out.. smaller.. but I don't know why. BTW, this is not the standard slacko image, it has a little bit more compression than normal, wont work on slow machines, it is for the experiment. (111M)
So.. for the adventurous out there I am posting a slacko-5.3.3-SCSI-high-comp.nrg (PAE version)
checksum: c581c30dc8ab3126596a7c532f302661 slacko-5.3.3-SCSI-high-comp.nrg
Attached is the source code including binary in the package and a separate patches package.
Have fun!
source: http://packages.qa.debian.org/n/nrg2iso.html
I made an .nrg image of a slacko iso image in Windows.. it seemed to work ok, then I booted back into Puppy and converted it back from nrg to iso. It mounted ok, but I didn't burn as the md5 did not match the original. The iso size is about 150 bytes out.. smaller.. but I don't know why. BTW, this is not the standard slacko image, it has a little bit more compression than normal, wont work on slow machines, it is for the experiment. (111M)
So.. for the adventurous out there I am posting a slacko-5.3.3-SCSI-high-comp.nrg (PAE version)
checksum: c581c30dc8ab3126596a7c532f302661 slacko-5.3.3-SCSI-high-comp.nrg
Attached is the source code including binary in the package and a separate patches package.
Have fun!
- Attachments
-
- nrg2iso-0.4.tar.gz
- the patched source and binary, should work on most pups, else easy to recompile
- (11.25 KiB) Downloaded 650 times
-
- nrg-patches.tar.gz
- patches
- (1.46 KiB) Downloaded 650 times
Puppy Linux Blog - contact me for access
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
Well... obviously it isn't the same md5 or size: just like a FLAC or ALAC version of the same audio sample will not be the same (though a more precise example would be a .pet and .deb based around the same tarball -- the bits added at the start/end are different).01micko wrote:I made an .nrg image of a slacko iso image in Windows.. it seemed to work ok, then I booted back into Puppy and converted it back from nrg to iso. It mounted ok, but I didn't burn as the md5 did not match the original. The iso size is about 150 bytes out.. smaller.. but I don't know why.
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind
Dougal.. I meant the image as .iso (checked original md5 in puppy), converted to .nrg in windows (md5 posted) and then back to .iso from .nrg (md5 was different to original iso md5 and iso size was some 150B smaller). So something is lost in the conversion to and from somewhere, maybe harmless, I'll burn it and post results.
EDIT: boots fine, runs fine, note that the md5s of the main sfs, vmlinuz and initrd.gz is the same so the 150B missing must be something other than the puppy files.
EDIT: boots fine, runs fine, note that the md5s of the main sfs, vmlinuz and initrd.gz is the same so the 150B missing must be something other than the puppy files.
Puppy Linux Blog - contact me for access
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
It could be something like metadata... "written by app X on this date..." etc. (I presume iso-9960 has that).01micko wrote:Dougal.. I meant the image as .iso (checked original md5 in puppy), converted to .nrg in windows (md5 posted) and then back to .iso from .nrg (md5 was different to original iso md5 and iso size was some 150B smaller). So something is lost in the conversion to and from somewhere, maybe harmless, I'll burn it and post results.
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind
I checked the most common burning apps for Linux, and this is what I found:mistfire wrote:By the way is it ok to you that you must change the Button label "Blank Disc" to "Erase Disc" to make it more understandable?
______ K3b ______________
Features listed in k3b.org
- Blanking of CDR-Ws.
- Good media detection and optional automatic CD-RW and DVD-RW blanking
'Erase' is not mentioned
______ Brasero ______________
- erase CD/DVD
'Blanking' is not mentioned
______ XfBurn ______________
- It can blank CD/DVD(-RW)s
'Erase' is not mentioned
______ Nero ______________
- Erase DVD
'Blanking' is not mentioned
__________________________
and for the record
- XcdRoast uses blank
- Graveman says: clean rewritable cd and dvd