This indicates an improper state exists when quitting or closing
a window. The Enlightenment people appear to have a different
method of window management which I noticed when I did a 'top'
command. Each wndow seems to be treated like it is an app!!

I tried changing exit to exit 0
and that didn't work

The strange thing about this bug is it doesn't occur when I use
third party launch programs such as GRun or quick_launch,
then quit pburn.

Today I tried to burn an iso to DVD+RW with Pburn 3.3.4 on a Toshiba laptop.

Pburn 3.3.4 pronounced the blank Verbatim DVD+RW "unwritable". .

So I installed Pburn 3.5.2 and close-dvd+rw tools

There were no indicationsof problems with the installation, but when I clicked on the pburn tab in the start menu of Lupu 5.2.8, nothing happened. After several tries, I uninstalled close-dvd+rw tools, but pburn still wouldn't start.

I then uninstalled pburn 3.5.2, and was able to reopen pburn 3.3.4.

I then used Burniso2 CD to write a 2.2GB iso to the same DVD+RW pburn 3.3.4 had deemed "unwritable", and verified it. Burniso2CD opted to blank the DVD before burning.

End of story...hope this helps._________________otropogo@gmail.com facebook.com/otropogo

So it would appear that the latest version of pburn available to lupu 5.2.8 (-0) users (and perhaps also to users of versions (02,03,04?) is 3.3.7. If this is the best you can do, you could at least advise users of this on the download post. I've now installed 3.3.7, having tried every trick I know of to install 3.5.2.

This includes trying to update lupu 5.2.8 via the 5.2.8-05 pmusic pet. I looked for previous update pets, but couldn't find any links. It seems that your latest pburn will not run on the original version of lupu 5.2.8

Pburn 3.3.7 does open a window on the desktop when called. And it (unlike the natively shipped 3.3.4) recognizes a Verbatim DVD+RW as a writable disk. Slim pickings for all that work.

BTW - you may be interested to know (or at least some of my hapless fellow would-be users of Pburn might), that I am able to run Pburn 3.5.1 on my desktop lupu5.2.8 system, which, IIRC, was updated via pets to version 02, then version 03, and then (after version 03 was found to run videos rather worse than previously), returned to version 02 status.

Package manager does show the lupu update 02 as being installed on my desktop system, but there's no sign of any 'gtkdialog...', so perhaps the lupu update 02 provided the necessary gtk support?

I'm assuming from your post above that pburn 3.5.1 required this support as much as 3.5.2 does._________________otropogo@gmail.com facebook.com/otropogo

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.

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

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.

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

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.

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

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum