Should I do something about this, or will you. I case it's my task, please point me to knowledge.pemasu wrote:Don570 found behavior has been explained in Exprimo thread. It is due to one script in Exprimo.
Thank you
Sigmund
pBurn 4.3.19
ask Scottman
It's a script that Scottman wrote that is causingZigbert wrote:Should I do something about this, or will you.
the trouble, so I've asked Scottman to look into it.
The script is in the Startup folder and makes links for the
partitions. Apparently he did this to make
the open dialog box more friendly.
_________________________________________-
Tried the same thing with an old multisession DVD+RW. Should it make any difference if the disk is mounted or not?zigbert wrote:Does this happen for mini-DVDs or is it a general behavior for Disc info?Flash wrote:I installed 3.4.1 and, just fooling around, clicked Tools -> Disc info with my multisession Puppy mini-DVD in the drive. Here's the result:
- Attachments
-
- Pburn Disc info for multisession 4.7 GB DVD+RW.jpg
- (66.36 KiB) Downloaded 410 times
Mounted or unmounted should give the same result. I couldn't find any DVD-RW disc but tried both DVD-R and CD-RW to check my system. It works.... hmmm, does the sizebar (bottom left) show correct info, or .... ???Flash wrote:Tried the same thing with an old multisession DVD+RW. Should it make any difference if the disk is mounted or not?
Sigmund
Re: ask Scottman
Okeeey, I see. So Pburn actually works. It shows the name of the directory. What more do you expectdon570 wrote:The script is in the Startup folder and makes links for the partitions.
It is of course possible to ask Pburn to follow symlinks and show the actual directory. But this has other downsides..... user gets another result in the field than he/she defined, and that could confuse even more.
Sigmund
Here is the reply I got from Scottman about the script in Startup folder
/root/Startup/gtk-mnt-links
http://www.murga-linux.com/puppy/viewto ... &start=360
____________________________________________________
/root/Startup/gtk-mnt-links
http://www.murga-linux.com/puppy/viewto ... &start=360
____________________________________________________
Did you check with a multisession DVD?zigbert wrote:Mounted or unmounted should give the same result. I couldn't find any DVD-RW disc but tried both DVD-R and CD-RW to check my system. It works.... hmmm, does the sizebar (bottom left) show correct info, or .... ???Flash wrote:Tried the same thing with an old multisession DVD+RW. Should it make any difference if the disk is mounted or not?
This is the same multisession Puppy DVD+RW as before. I haven't booted it or written anything new to it. The drive is a Blu-Ray burner, but I'm pretty sure that doesn't matter. I've seen the same thing from a DVD burner.
- Attachments
-
- Pburn says multisession DVD+RW is empty.jpg
- (64.78 KiB) Downloaded 385 times
Great.don570 wrote:Here is the reply I got from Scottman about the script in Startup folder
/root/Startup/gtk-mnt-links
http://www.murga-linux.com/puppy/viewto ... &start=360
____________________________________________________
I will dig into my disc-chaos and see if I can find a DVD+RW disc. And no, I did not check multisession. Did you check the sizebar? Is it working correct for the discs not working in disc-information?Flash wrote:Did you check with a multisession DVD?
This is the same multisession Puppy DVD+RW as before. I haven't booted it or written anything new to it. The drive is a Blu-Ray burner, but I'm pretty sure that doesn't matter. I've seen the same thing from a DVD burner.
Sigmund
I checked the sizebar, and even posted a screenshot of it, like before. Now both screenshots have disappeared. Hmm.zigbert wrote:...Did you check the sizebar? Is it working correct for the discs not working in disc-information?
Anyway, Pburn's sizebar showed the 4.7 GB multisession DVD+RW as completely empty, just as it did the 1.4 GB mini-DVD-RW (with scratch-resistant coating
.)Flash
I found a DVD-R and a DVD+RW disc for testing. I burnt mutisession and they both worked in sizebar and disc-info dialog. So the answer is simple - I have no idea what's going on here
I looked back in this thread to grab your info of the BD-RE disc. Could you also ship the output for the mini-dvd (or another DVD since they all fail). We need to compare...
Another interesting thing to test would be to see how your discs behave with another burner-device (that will tell us if it is reading or writing that differs). The developing of Pburn has not been like the other tools that I have made. - Pburn meets _many_ different hardware. Some of the users complaining about Pburn didn't succeed to burn in Windows or other burner-apps, and just mean that Pburn should work for them. In my eyes this is some kind of a comedy, but there have been cases where I have struggled in days, and then get the info that the hardware probably is broken.... - Not really funny. Your device is sure working, but it is new, and what do I know - it might handle things differently. Please give as much info as possible.... that would be output of dvd+rw-mediainfo /dev/sr0 for different type of discs.
Thank you
Sigmund
I found a DVD-R and a DVD+RW disc for testing. I burnt mutisession and they both worked in sizebar and disc-info dialog. So the answer is simple - I have no idea what's going on here
I looked back in this thread to grab your info of the BD-RE disc. Could you also ship the output for the mini-dvd (or another DVD since they all fail). We need to compare...
Another interesting thing to test would be to see how your discs behave with another burner-device (that will tell us if it is reading or writing that differs). The developing of Pburn has not been like the other tools that I have made. - Pburn meets _many_ different hardware. Some of the users complaining about Pburn didn't succeed to burn in Windows or other burner-apps, and just mean that Pburn should work for them. In my eyes this is some kind of a comedy, but there have been cases where I have struggled in days, and then get the info that the hardware probably is broken.... - Not really funny. Your device is sure working, but it is new, and what do I know - it might handle things differently. Please give as much info as possible.... that would be output of dvd+rw-mediainfo /dev/sr0 for different type of discs.
Thank you
Sigmund
Code: Select all
# dvd+rw-mediainfo /dev/sr0
INQUIRY: [HL-DT-ST][BD-RE BH12LS35 ][1.00]
GET [CURRENT] CONFIGURATION:
Mounted Media: 43h, BD-RE
Current Write Speed: 2.3x4495=10338KB/s
Write Speed #0: 2.3x4495=10338KB/s
GET [CURRENT] PERFORMANCE:
Write Performance: 2.3x4495=10338KB/s@[0 -> 12088319]
Speed Descriptor#0: 02/12088319 R@8.0x4495=35903KB/s W@2.3x4495=10338KB/s
READ DISC INFORMATION:
Disc status: complete
Number of Sessions: 1
State of Last Session: complete
Number of Tracks: 1
READ FORMAT CAPACITIES:
formatted: 12088320*2048=24756879360
00h(3000): 11826176*2048=24220008448
01h(800): 11564032*2048=23683137536
30h(3000): 11826176*2048=24220008448
30h(5000): 11564032*2048=23683137536
30h(1000): 12088320*2048=24756879360
31h(800): 12219392*2048=25025314816
READ TRACK INFORMATION[#1]:
Track State: complete incremental
Track Start Address: 0*2KB
Free Blocks: 0*2KB
Track Size: 12088320*2KB
FABRICATED TOC:
Track#1 : 14@0
Track#AA : 14@12088320
Multi-session Info: #1@0
READ CAPACITY: 12088320*2048=24756879360 
couldn't open pburn 3.4.1, can't save log path in pburn3.3.7
Just installed Pburn 3.4.1, after repeated frustration trying to copy a CD (my Puppy 5.2.8 disk) with v. 3.3.5.
But when I clicked on pburn in the multimedia menu, no application window opened, nor was there any error message.
I then decided to try 3.3.7, and it duly appeared when called. And eventually I was successful in burning a copy of my lupu disk. But not before going several rounds with Pburn over the temporary folder.
For reasons that are not clear to me it tells me my folder /mnt/home/pburn is illegal because it's "in a sym_link tree". I note that although I merely created a folder called "pburn" in my home directory (a vfat partition), puppy added /sym_link/ to /mnt/home/pburn. I finally found peace only after changing the name to "pburn_logs" and moving it to an ntfs partition.
Now, if only I could save the path for saving burn logs, so I wouldn't have to navigate there from root every time I want to save a burn log (the reason I wanted it in "home" - the path is a lot shorter.)
But when I clicked on pburn in the multimedia menu, no application window opened, nor was there any error message.
I then decided to try 3.3.7, and it duly appeared when called. And eventually I was successful in burning a copy of my lupu disk. But not before going several rounds with Pburn over the temporary folder.
For reasons that are not clear to me it tells me my folder /mnt/home/pburn is illegal because it's "in a sym_link tree". I note that although I merely created a folder called "pburn" in my home directory (a vfat partition), puppy added /sym_link/ to /mnt/home/pburn. I finally found peace only after changing the name to "pburn_logs" and moving it to an ntfs partition.
Now, if only I could save the path for saving burn logs, so I wouldn't have to navigate there from root every time I want to save a burn log (the reason I wanted it in "home" - the path is a lot shorter.)
otropogo@gmail.com facebook.com/otropogo
Re: couldn't open pburn 3.4.1, can't save log path in pburn3.3.7
otropogo
Pburn 3.4.1 requires gtkdialog 0.8 which is not found in Puppy 5.2.8 (else you install it).
You have mentioned the path for the log-file for at least 3 years now ... and each time I have made a test-burn to verify that I am able to set the path for the log-file. 
Funny for me, not for you.... I am sorry, but I can't reproduce your trouble. I need more info.
For the setting of temporary directory, /mnt/home could be a weak point, since this is the home of your frugal install. Be aware that the warning at startup can be skipped by enable the checkbox at bottom of the dialog.
Sigmund
Pburn 3.4.1 requires gtkdialog 0.8 which is not found in Puppy 5.2.8 (else you install it).
You have mentioned the path for the log-file for at least 3 years now
... and each time I have made a test-burn to verify that I am able to set the path for the log-file. Funny for me, not for you.... I am sorry, but I can't reproduce your trouble. I need more info.For the setting of temporary directory, /mnt/home could be a weak point, since this is the home of your frugal install. Be aware that the warning at startup can be skipped by enable the checkbox at bottom of the dialog.
Sigmund
Re: couldn't open pburn 3.4.1, can't save log path in pburn3.3.7
Thanks for the update, I must have misread the description, which I thought stated that all recent versions of Puppy contained all the necessary dependencies.zigbert wrote:otropogo
Pburn 3.4.1 requires gtkdialog 0.8 which is not found in Puppy 5.2.8 (else you install it).
You have mentioned the path for the log-file for at least 3 years now
For the setting of temporary directory, /mnt/home could be a weak point, since this is the home of your frugal install. Be aware that the warning at startup can be skipped by enable the checkbox at bottom of the dialog.
Sigmund
re: /mnt/home I'm booting from CD each time, using a lupusave.2fs file on a hard drive partition (which then becomes "/mnt/home" and is automatically and permanently mounted until shutdown). I can't remember whether that meets the definition of "frugal", but I didn't think so. Does it explain the difficulty of saving the location of the log save folder?
Also, while composing this response, I opened Pburn 3.3.7 and got a message warning me that my temporary file folder /mnt/sda5/pburn_logs does not exist or isn't mounted. That's a problem, because, the drive icon has a green dot on it, which normally means it IS mounted.
And I've now opened pmount, and Pmount also tells me it's mounted and has 4.8GB of free space available...What to do?
I navigated to it in the pburn file browser, and lo and behold, it shows a subfolder /pburn_logs/pburn_symlink_tree, which seems to stalk me everywhere I try to create a useable temporary folder for pburn, foiling my efforts.
When I click on it, it shows the subfolder (previously it didn't) and the 4GB of storage, but then reports that temporary storage could not be established in a symlink_tree!
OK, I'm stumped. I don't recall having these problems previously, but then I've been using a second burner lately and doing my burns on the fly.
And after all that, all I had to show for it was the pburn splash popup, with which I could do nothing but close it.
And now, pburn seems totally disabled. I get the initial popup, and then (sometimes) the temporary storage error message, and that's it - the end of the line. All I can do is close the popup(s). Time to uninstall again, I guesss...
That's all the info I can think to offer you.
otropogo@gmail.com facebook.com/otropogo
Here's a BD-RE with (I think) 2 sessions on it (but they only show as one session when the disk is mounted in either Windows or Puppy, I suppose because both sessions contain a directory with the same name. The contents of that top-level directory are not the same in both sessions though.)
I plan to burn a multisession Puppy BD-RE soon, to see what that looks like. Here's what a multisession mini-DVD looks like in the LG Blu-Ray burner:
The multisession mini-DVD boots fine from the Blu-Ray burner. When I mount it it looks normal; I can see all the saved sessions.
Code: Select all
# dvd+rw-mediainfo /dev/sr0
INQUIRY: [HL-DT-ST][BD-RE BH12LS35 ][1.00]
GET [CURRENT] CONFIGURATION:
Mounted Media: 43h, BD-RE
Current Write Speed: 2.3x4495=10338KB/s
Write Speed #0: 2.3x4495=10338KB/s
GET [CURRENT] PERFORMANCE:
Write Performance: 2.3x4495=10338KB/s@[0 -> 12088319]
Speed Descriptor#0: 02/12088319 R@8.0x4495=35903KB/s W@2.3x4495=10338KB/s
READ DISC INFORMATION:
Disc status: complete
Number of Sessions: 1
State of Last Session: complete
Number of Tracks: 1
READ FORMAT CAPACITIES:
formatted: 12088320*2048=24756879360
00h(3000): 11826176*2048=24220008448
01h(800): 11564032*2048=23683137536
30h(3000): 11826176*2048=24220008448
30h(5000): 11564032*2048=23683137536
30h(1000): 12088320*2048=24756879360
31h(800): 12219392*2048=25025314816
READ TRACK INFORMATION[#1]:
Track State: complete incremental
Track Start Address: 0*2KB
Free Blocks: 0*2KB
Track Size: 12088320*2KB
FABRICATED TOC:
Track#1 : 14@0
Track#AA : 14@12088320
Multi-session Info: #1@0
READ CAPACITY: 12088320*2048=24756879360
#Code: Select all
# dvd+rw-mediainfo /dev/sr0
INQUIRY: [HL-DT-ST][BD-RE BH12LS35 ][1.00]
GET [CURRENT] CONFIGURATION:
Mounted Media: 13h, DVD-RW Restricted Overwrite
Media ID: CMCW02
Current Write Speed: 2.0x1385=2770KB/s
Write Speed #0: 2.0x1385=2770KB/s
GET [CURRENT] PERFORMANCE:
Write Performance: 2.0x1385=2770KB/s@[0 -> 716799]
Speed Descriptor#0: 02/716799 R@7.9x1385=10901KB/s W@2.0x1385=2770KB/s
READ DVD STRUCTURE[#10h]:
Media Book Type: 00h, DVD-ROM book [revision 0]
Legacy lead-out at: 716800*2KB=1468006400
READ DVD STRUCTURE[#0h]:
Media Book Type: 32h, DVD-RW book [revision 2]
Last border-out at: 2045*2KB=4188160
READ DISC INFORMATION:
Disc status: complete
Number of Sessions: 1
State of Last Session: complete
Number of Tracks: 1
READ FORMAT CAPACITIES:
formatted: 147280*2048=301629440
00h(800): 716192*2048=1466761216
10h(10): 716192*2048=1466761216
13h(10): 568912*2048=1165131776
15h(10): 716192*2048=1466761216
READ TRACK INFORMATION[#1]:
Track State: complete incremental
Track Start Address: 0*2KB
Free Blocks: 0*2KB
Fixed Packet Size: 16*2KB
Track Size: 147280*2KB
Last Recorded Address: 147279*2KB
FABRICATED TOC:
Track#1 : 14@0
Track#AA : 14@147280
Multi-session Info: #1@0
READ CAPACITY: 147280*2048=301629440
#