Page 107 of 118

Posted: Tue 22 Jul 2014, 06:59
by zigbert
rg66
That link is from the old NLS method.
I have now deleted the symlink from the installation pack.
Thank you for sharing


Sigmund

Posted: Tue 22 Jul 2014, 07:06
by zigbert
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)

Posted: Mon 18 Aug 2014, 07:41
by jamesbond
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 :wink:

Posted: Mon 18 Aug 2014, 07:55
by zigbert
jamesbond
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)
Could you test if this works ok for you. pBurn should not rely on busybox.


Sigmund

Posted: Mon 18 Aug 2014, 09:45
by jamesbond
zigbert wrote:pBurn should not rely on busybox.
Agreed - the idea is that it should work equally well with or without busybox.

Code: Select all

grep -F 'Xdialog' <<< $(ps -eo pid,command)
Could you test if this works ok for you. 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 ... :(

Posted: Mon 18 Aug 2014, 20:38
by zigbert
I have used ps -eo for at least 2 years in several apps, so I think it will work also for busybox - else someone would have complained. :)

Since it works for you, I'll make an update soon.


Sigmund

Problem to burn BluRay-Data-Discs

Posted: Tue 19 Aug 2014, 10:27
by antilet
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?

Posted: Tue 19 Aug 2014, 13:12
by zigbert
To burn Blu-ray you have to use a recent pBurn - not the one in Precise. But Puppy Precise uses the cdrkit as its burning backend instead of cdrtools which the recent pBurn requires.

Either go from precise to slacko or another more modern Puppy, or install cdrtools to your Precise.


Sigmund

Posted: Tue 19 Aug 2014, 14:08
by zigbert
Version 4.3.7
See main post

Changelog
Bugfix: Do not rely on busybox ps (thanks to jamesbond)

Posted: Thu 21 Aug 2014, 10:32
by antilet
zigbert wrote:Either go from precise to slacko or another more modern Puppy, or install cdrtools to your Precise.
OK. I tried Slacko 5.7 (pBurn 4.3.4 is inside) - with the same Result:
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.
Any other hints befor I give Windows a try?

Posted: Thu 21 Aug 2014, 10:48
by rcrsn51
antilet wrote:Any other hints befor I give Windows a try?
The definitive work on Blu-ray and Puppy was done here with PeasyDisc. However, I have not tested this in Slacko 57.

Posted: Fri 22 Aug 2014, 14:02
by zigbert
Version 4.3.8
See main post

Changelog
- Extended DVD/BD-info in 'Disc is not blank'-dialog

Posted: Sun 24 Aug 2014, 19:23
by antilet
rcrsn51 wrote:The definitive work on Blu-ray and Puppy was done here with PeasyDisc. However, I have not tested this in Slacko 57.
Sure very handy, but only one folder and no verify,.close or not close session?

Just for the record- pBurns error-message:

Code: Select all

closing session: -[ CLOSE SESSION failed with SK=5h/ INVALID FIELD IN CDB: Input/output error
btw: what is the correct/best filesystem for blurays?

Posted: Sun 24 Aug 2014, 20:22
by zigbert
antilet
If PeasyDisc works for you, it would be interesting to compare the burning commands. The commands are built into a temporary execution-file.

PeasyDisc: /tmp/go.sh
pBurn: /root/.pburn/tmp/exec

It would be great if you took the time to show us the content of those files after a blu-ray burn. The commands will show us what filesystem settings that are used. I don't know if there is any preferred filesystem for blu-ray as long as you use it as a data-storage (and not for video).


Thank you
Sigmund

Posted: Sun 24 Aug 2014, 20:24
by rcrsn51
antilet wrote:but only one folder
Create a temporary source folder. Drag symlinks from your various data folders into the source folder. Select the source folder for burning.
close or not close session
Typically, you would not want to close a BD session because that prevents you from adding more data.
and no verify
Version 3.2 now has a Verify option after writing data to disc.

More importantly, was the burn successful with PeasyDisc? Did you get to 100% without errors? How full is the disc?

What Puppy are you using? The versions of Precise will be unreliable if you burn large amounts of data.

Posted: Mon 25 Aug 2014, 02:40
by ASRI éducation
zigbert wrote:Version 4.3.8
Thank you zigbert.
Regards

Posted: Tue 26 Aug 2014, 05:26
by zigbert
rcrsn51 wrote:The definitive work on Blu-ray and Puppy was done here with PeasyDisc.
You are using the attribute -use-the-force-luke=notty for burning with growisofs. I can't find any documentation of this parameter, but looking at -use-the-force-luke=tty, it might be interesting. Can you give some knowledge?


Thanks
Sigmund

Posted: Sat 30 Aug 2014, 19:07
by zigbert
Version 4.3.9
See main post

Changelog
- New Overburn/overwrite-msg if size requires it.
- - - - Specific DVD/BD info in the 'overburn' dialog to alternatively overwrite existing data.
- - - - Added the attribute -use-the-force-luke=tty to skip interactive msg from growisofs.
- - - - Added the attribute -use-the-force-luke=spare:none to overburn BD.
- - - - Help: Adjusted overburn info.
- Bugfix: Auto-set overburning of BD/DVD if chosen/required.
- Set uid and gid to 0 for rockridge filesystem on the burnt media.

:-( mkisofs has failed: 255

Posted: Sat 06 Sep 2014, 07:37
by charlie6
Hi,
using version 4.3.9 with all dependencies checked OK (excepted for Nero ...):

wanting to burn 955MB pictures files from a 1GB SD car to a non-empty DVD-RW, Multisession, with 4.38 GB free (according to the «memory space bar» footer) , i got the following error message:
Pburn version 4.3.9

###################################################
COMMAND:
###################################################
#!/bin/sh
mkisofs -iso-level 4 -r -D -V "pictWB14" -p pBurn4_4 -o "/mnt/home/Pburn.iso" -C 0,0 -M /dev/sr1 -exclude-list /root/.pburn/tmp/exclude -graft-points -path-list=/root/.pburn/tmp/graft_points
growisofs -use-the-force-luke=notray -use-the-force-luke=tty -C 0,0 -M /dev/sr1="/mnt/home/Pburn.iso"

###################################################
OUTPUT:
###################################################
Warning: Creating ISO-9660:1999 (version 2) filesystem.
Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in the OS.
Setting input-charset to 'UTF-8' from locale.
SUSP signatures version 1 found
Rock Ridge signatures version 1 found
Rock Ridge id 'RRIP_1991A'
mkisofs: Inode number overflow, too many files in file system.
growisofs: -C argument is insane.
How can this message be interpreted? Are there too much files to burn? what is the limit then?

Thanks for any reply!
Charlie

Posted: Sat 06 Sep 2014, 08:35
by zigbert
Charlie
I can reproduce the error - will investigate...

You can solve this by using the default burn-setting - 'on-the-fly'.
Normally, there aren't many reasons for using a temporary storage when burning DVDs.