pBurn 4.3.19

[zigbert]

HI @Zigbert and thank you very much for your latest efforts. I understand the items you are addressing to make pBurn easy to understand and use.

I have couple PCs which have 2 DVD burners in each system. 1 has DVD+BluRay.

Here's my questions:
If I have a multi-session DVD. Will PBurn:
- replicate this to another DVD?

Yes, it will copy (with 'Copy data disc') all sessions to the new DVD. It is a bit-for-bit copy.

- replicate this to an ISO?

Export to ISO-image (File menu) generates a new filestructure of _all_ files on disc, but the session information will be lost, because this is not a part of the filesystem information.

- If its a bootable DVD, will this change your answer?

pBurn can not generate bootable images, but a bit-for-bit copy will keep all boot informartion.

Next:
If I mount a DVD and after opening pBurn, I address it via its path in the left-hand pane;
- can I select any/all information on the left side to be incorporated on the right side for burning to a new DVD?

Yes, as long as you have 2 drives, and the burn-device is not the one shown in the left-panel, it will work as any other local directory.

- And, is there a way to tell PBurn to keep the bootable stuff from the mounted DVD for adding to the DVD which will be burned?

No.pBurn does not generate boot-images. If anyone want to look at pBurn-support of bootable discs, I will sure help out. But for now, this is out of my scope for pBurn.

Lastly, some of my DVDs (the newer ones) have more media information on them than will fit on a normal DVD. To copy the entirety I can use DL DVDs that I have.

If this is a question, the answer is yes

My last Question:

• Is there any difference in the duplicaton process when copying to a DL disc for video media?

Thanks in advance for any guidance.

No. but I guess, some players will complain about a DVD-DL.


Sigmund

[OscarTalks]

I have installed pBurn 4.3.0 in Wheezy and am experiencing a problem.
Trying to do a blank (complete) of a CD-RW which I do quite often.
I choose "blank (complete)" and then set the speed to 4, then press the burn button as usual.
The burn process window opens up but it is just black blank, no yellow text and nothing happens.

Maybe I am doing something silly or need to do something else with the preferences in this version?

[pemasu]

I got this in my new (unpublished yet) dpup wheezy with pburn 4.30:
# pburn -m blank
/usr/local/pburn/func_burn_options: line 291: /root/.pburn/tmp/MEDIATYPE_FULL: No such file or directory
/usr/local/pburn/func_burn_options: line 292: /root/.pburn/tmp/MEDIATYPE: No such file or directory
scsidev: '/dev/cdrom'
devname: '/dev/cdrom'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
cdrecord: Warning: Cannot read drive buffer.
cdrecord: Warning: The DMA speed test has been skipped.
EXIT="Ready"
EXIT="Ready"
readlink: missing operand
Try `readlink --help' for more information.
readlink: missing operand
Try `readlink --help' for more information.

......cut repeates several time above rows.......

/usr/local/pburn/func_exec: line 6: /root/.pburn/tmp/COPY_BURN_ISO: No such file or directory
/usr/local/pburn/func_exec: line 228: syntax error near unexpected token `)'
/usr/local/pburn/func_exec: line 228: ` verify)'
Killed

I had preinstalled OscarTalks compiled dvd+rwtools and cdrtools pets with woof building.

Cheers.

[pemasu]

Okay. Step 2. sg kernel driver which cdrecord depends on was missing. Why. When you woof scsi iso, the 3builddistro throws scsi drivers to the initrd.gz. And they are not available in puppy sfs under /lib/modules/*/scsi/*

I did copy the scsi drivers to the right location from where they were transferred to the initrd. depmod > modprobe sg > cdrecord blank=fast > under the result:

# cdrecord blank=fast
Cdrecord-ProDVD-ProBD-Clone 3.01a16 (i686-pc-linux-gnu) Copyright (C) 1995-2013 Joerg Schilling
Linux sg driver version: 3.5.34
Using libscg version 'schily-0.9'.
No target specified, trying to find one...
Using dev=2,0,0.
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'Slimtype'
Identifikation : 'DVD A DS8A8SH '
Revision : 'KA14'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE FORCESPEED
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
cdrecord: Warning: Cannot read drive buffer.
cdrecord: Warning: The DMA speed test has been skipped.
Starting to write CD/DVD/BD at speed 10 in real BLANK mode for single session.
Last chance to quit, starting real write 0 seconds. Operation starts.
#

Cdrecord started to work when I enabled sg kernel driver. The cd was blanked.

Now Pburn 4.30. After I had manually edited the command to be just cdrecord blank=fast:
# pburn -m blank
/usr/local/pburn/func_burn_options: line 291: /root/.pburn/tmp/MEDIATYPE_FULL: No such file or directory
/usr/local/pburn/func_burn_options: line 292: /root/.pburn/tmp/MEDIATYPE: No such file or directory
EXIT="Ready"
gettochdr: Input/output error
scsidev: '/dev/sr0'
devname: '/dev/sr0'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
cdrecord: Warning: Cannot read drive buffer.
cdrecord: Warning: The DMA speed test has been skipped.
cd-info: Can't get first track number. I give up.
EXIT="Ready"
readlink: missing operand
Try `readlink --help' for more information.
/usr/local/pburn/func_exec: line 6: /root/.pburn/tmp/COPY_BURN_ISO: No such file or directory
/usr/local/pburn/func_exec: line 228: syntax error near unexpected token `)'
/usr/local/pburn/func_exec: line 228: ` verify)'
Killed
# /usr/local/pburn/func: line 473: kill: (23486) - No such process

And same result with default options. Hmm.....Am I still missing something or...

[zigbert]

Thank you guys - fixed
Syntax error in func_exec


Sigmund

[zigbert]

Version 4.3.1
See main post

Changelog
- Bugfix: Execution fails (thanks to OscarTalks)

[pemasu]

pBurn 4.3.1 blanks now cd. And that black screen contains cdrecord info now ok.
Thanks.

[zigbert]

pemasu
Good news


Thank you for validation
Sigmund

[OscarTalks]

pBurn 4.3.1
Just tried to burn an .iso and got an error.
Log attached.

[zigbert]

OscarTalks
What a log

The command pBurn built for you is absolutely non-sense. I try to reproduce it, but without luck. Can you describe how you got there?


Thank you
Sigmund

[zigbert]

... I tried to a burn which crashed (well hung actually) after I tried to change the label name, next attempt burnt fine ...

Interesting. I did some testing, and adding a space to the volume label corrupts the session. What did you do to make it trouble?


Sigmund

[OscarTalks]

Hi Sigmund,

It is Wheezy 3.5.2.7 and I uninstalled pBurn 4.2.0 and installed 4.3.1 .pet as usual when I upgrade to a new pBurn version.

The .iso is just a remaster of another Puppy. I just clicked the "burn iso" button then selected the file, set the speed as usual and when I click the burn button I got the error. I tried it twice with the same result.

I have done this many times before. I went back to pBurn 4.2.0 and burned the .iso in the normal way.

[zigbert]

Version 4.3.2
See main post

Changelog
- Bugfix: Burn iso-image (thanks to OscarTalks)


Thanks a lot to OscarTalks for feedback
Sigmund

[zigbert]

Version 4.3.3
See main post

Changelog
- Do add Preparer, Publisher, Volume to command only for first session.
- Faster disc-info (Tools menu).
- Bugfix: If Volume/Publisher is set empty at first session, Default values shows up in burn-option dialog at second session.
- Bugfix: Publisher nor Volume can contain space when burning CD.
- Bugfix: Dummy burn a CD on-the-fly

[matiasbatero]

Hi Zigbert, how are you?

I'm sure that you remember me with the trick to solve issues on multisession recording.

I'm working on a burning program, but using pure-udf filesystem instead.
There are differences between PBurn and my actual project, on device detection.

But i need to ask, before. ¿You don't use growisofs for some reason?

**DVD/BD burning manipulation are very simplified using that tool.
In my personal experience, this tool removed me a lot of code.

I saw that your program have cddetect as dependency, to perform media detection. I found, that growisofs (that only works with DVD/BD in all senses and doesn't have a detection utility) can be used to detect media, indirectly using its own error codes.

For example, dvd+rw-mediainfo /dev/sr0
Only works if DVD or BD are inside. And return exit codes for other states.
*Device empty (251)
*Open tray (250)
*Invalid medium.. (that is a reference to CD). (252)
*Invalid device (130)

The detection is very very quickly (instantaneously).
And in my opinion it's very usefull, because you have 3 functions in one.. (detection, burning dvd, burning bd, with great simplification).

This is not a recommendation, Pburn works great, and i'm identified with "if it works, don't touch" ,but, we have a similar projects and maybe, something useful by my side, could be useful for you.

Regards,
Matías Gastón.

PD: sorry for my english

[gcmartin]

As I remember the cautions on using Growisofs is on subsequent use where the -M parm replaces -Z, as "ALL" of the prior parms used to write the DVD MUST be used as well to add additional file(s)/folder(s) to an pre-existing multimedia DVD/BD.

Is this still true, even for UDF? Or is there a Growisofs multi-session standard that is employed?

Curious

[matiasbatero]

As I remember the cautions on using Growisofs is on subsequent use where the -M parm replaces -Z, as "ALL" of the prior parms used to write the DVD MUST be used as well to add additional file(s)/folder(s) to an pre-existing multimedia DVD/BD.

Is this still true, even for UDF? Or is there a Growisofs multi-session standard that is employed?

Curious

Yes, but these cautions are not important for growisofs only. The only difference, is that growisofs works directly with mkisofs and it need to pass parameters in one line. If you want to use cdrecord, you have 2 steps.. mkisofs and then cdrecord, so you have the same caution here.

Growisofs is designed to work with iso9660, not udf.

UDF is another standard, and another concept of filesystem. UDF doesn't have this caution of "same parameters" on multisessions, beacuse it works different. Multisession disc in UDF mode, is perfomed using "Packet-Writting" feature, and it works like a USB pendrive (transparently).

Growisofs doesn't work with UDF so, nothing to do. But, it have a function to burn any generic file to the disk. So it can be used to burn UDF filesystems. or any filesystem.. EXT4 for example.. on a DVD...

Great no??

[zigbert]

But i need to ask, before. ¿You don't use growisofs for some reason?

For the record: pBurn uses growisofs for burning and media-detection (not the quick one) for DVD/BD.

I saw that your program have cddetect as dependency, to perform media detection. I found, that growisofs (that only works with DVD/BD in all senses and doesn't have a detection utility) can be used to detect media, indirectly using its own error codes.

For example, dvd+rw-mediainfo /dev/sr0
Only works if DVD or BD are inside. And return exit codes for other states.
*Device empty (251)
*Open tray (250)
*Invalid medium.. (that is a reference to CD). (252)
*Invalid device (130)

The detection is very very quickly (instantaneously).
And in my opinion it's very usefull, because you have 3 functions in one.. (detection, burning dvd, burning bd, with great simplification).

As your last trick, this one is also very interesting, and I am glad you make the effort to share it. Thank you!
I would happily get rid of the cddetect dependency if possible. What I am not sure of, is the fact that you use error-code 252 for CD detection. Do you really find this reliable?


Sigmund

[matiasbatero]

But i need to ask, before. ¿You don't use growisofs for some reason?

For the record: pBurn uses growisofs for burning and media-detection (not the quick one) for DVD/BD.

I saw that your program have cddetect as dependency, to perform media detection. I found, that growisofs (that only works with DVD/BD in all senses and doesn't have a detection utility) can be used to detect media, indirectly using its own error codes.

For example, dvd+rw-mediainfo /dev/sr0
Only works if DVD or BD are inside. And return exit codes for other states.
*Device empty (251)
*Open tray (250)
*Invalid medium.. (that is a reference to CD). (252)
*Invalid device (130)

The detection is very very quickly (instantaneously).
And in my opinion it's very usefull, because you have 3 functions in one.. (detection, burning dvd, burning bd, with great simplification).

As your last trick, this one is also very interesting, and I am glad you make the effort to share it. Thank you!
I would happily get rid of the cddetect dependency if possible. What I am not sure of, is the fact that you use error-code 252 for CD detection. Do you really find this reliable?


Sigmund

Hi zigbert,

I did a lot of tests using cd, cdrw, dvd etc.. and i couldn't found any exception. 252 error code seems works only for CD and CDRW mediums.
DVD and BD structures always returns 0.

I examined on growisofs source code, if 252 is a exclusive code, o general errors. And i find that, dvd+rw-mediainfo reports a exclusive value for non dvd/bd mediums situations. And the only incompatible media are CD structures, so there is no alternative. A lot of my experiments, support this observation. So, for me, it's a secure trick.

Code: Select all

fprintf (stderr,":-( non-DVD media mounted, exiting...\n"),
	exit (FATAL_START(EMEDIUMTYPE));

Code: Select all

# define EMEDIUMTYPE	ERROR_MEDIA_INCOMPATIBLE

I'm using this on my script for burn images, on cd/dvd and USB pendrives! .. and growisofs error codes, gives me a correct differentiation of all mediums for all cases.. I think that is very reliable. This script also was tested by another people (around 6) with correct report inclusively.

*Sorry for the confusion, i referred to the Growisofs package (dvd+rw-tools), not pure growisofs command. I don't know if your program uses only a isolated growisofs command. This is important... Really, i don't know if growisofs can work without the rest of dvd+rw-tools package.

These numbers are obteined, by

Code: Select all

dvd+rw-mediainfo <path>
echo $?

And, the correct numbers are:

0 : DVD or BD inside.
252 : No compatible medium, no dvd/bd structure.. (and always is referenced to CD/CDRW cases).
251 : Empty drive, or open tray.
150 : Incompatible device (ex: /dev/sda)
130 : Invalid device path (ex: /dev/cuak)

Inclusive, it helped me with USB pendrives differentiation. Using err:150 as a first step and then with lsblk.

[gcmartin]

While on this subject, I have a problem where pBurn might be able to address.

I have a multi-session DVD which has a folder "/boot/grub". I want to copy a single file into that DVD's folder.

Can pBurn do this? Or can GROWISOFS do this? Or, is it advised to create a file in a HDD folder, /boot/grub/singleFile, and copy that folder to the multi-session disc? Or ...?

Thanks in advance for insight.