pBurn 4.3.19
Version 3.5.0
See main post
Changelog
- Improved Blu-ray (BD-R) support.
- Detection of DVD-mediatype in disc-info window.
- Detection of Blu-ray in burn-options window.
- First run installation is now done in 'no' time. (thanks to big_bass)
- Bugfix: Blu-ray discs was detected as DVD in statusbar. (thanks to flash)
- Bugfix: Size-detection of burnt BD-R sessions in statusbar. (thanks to flash)
- Bugfix: mkdir $HOME/my-documents/tmp if not exist and using as the default temporary storage. (thanks to big_bass)
- Bugfix: Startup-check for temp-dir always shows up if placed inside /mnt/home. (thanks to otropogo)
- Bugfix: Pburn won't open burn-option dialog if previous sessions contains not valid joliet extensions.
- Bugfix: Detect optical device in Porteus (thanks to Ahua in the Porteus forum)
- Bugfix: Not allowing capitals in file extension - *.CUE and *.TOC (thanks to sebus)
- Bugfix: Tray autoloads at once it has opened tray.
- NLS: Added: LOC395
- NLS: Changed: LOC126, 240, 333, 392
- NLS: Removed: LOC400
See main post
Changelog
- Improved Blu-ray (BD-R) support.
- Detection of DVD-mediatype in disc-info window.
- Detection of Blu-ray in burn-options window.
- First run installation is now done in 'no' time. (thanks to big_bass)
- Bugfix: Blu-ray discs was detected as DVD in statusbar. (thanks to flash)
- Bugfix: Size-detection of burnt BD-R sessions in statusbar. (thanks to flash)
- Bugfix: mkdir $HOME/my-documents/tmp if not exist and using as the default temporary storage. (thanks to big_bass)
- Bugfix: Startup-check for temp-dir always shows up if placed inside /mnt/home. (thanks to otropogo)
- Bugfix: Pburn won't open burn-option dialog if previous sessions contains not valid joliet extensions.
- Bugfix: Detect optical device in Porteus (thanks to Ahua in the Porteus forum)
- Bugfix: Not allowing capitals in file extension - *.CUE and *.TOC (thanks to sebus)
- Bugfix: Tray autoloads at once it has opened tray.
- NLS: Added: LOC395
- NLS: Changed: LOC126, 240, 333, 392
- NLS: Removed: LOC400
So people are using Pburn on a distro where KDE is default, in preference to K3B. Interesting.zigbert wrote:- Bugfix: Detect optical device in Porteus (thanks to Ahua in the Porteus forum)
Do you know a good gtkdialog program? Please post a link here
Classic Puppy quotes
ROOT FOREVER
GTK2 FOREVER
Classic Puppy quotes
ROOT FOREVER
GTK2 FOREVER
There I was testing Slacko 5.3.2.4, then I saw that 5.3.2.6 had just came out. While I was blanking the CDRW, in preparation for burning the new Slacko ISO to it, it occurred to me that it seemed to have been a long time since Zigbert had brought out Pburn 3.4.3 - and that was most unlike his traditional pace of releasing new versions...
Delighted to see you're still developing Pburn, it's a certain entry in my top 3 all-time favourite burning apps, along with ImgBurn on Windows and CDVDBurn on RISC OS.
After extensive experience with burning discs in the ancient Sony CRX100E (24x Read, 4x Write, 2x Re-Write CD burner) in my K6 2 500 I humbly submit the following addition to the Potential Pitfalls section:-
Pay close attention to the minimum and maximum writing speeds of your media, and compare them with the maximum writing speeds of your drive. Writing to media with a minimum speed setting higher than your drive is capable of will result in failure - for example, attempting to write to a 4x-10x CDRW on a drive with a maximum RW speed of 2x. This is most likely to be an issue when using new discs in an old system.
Delighted to see you're still developing Pburn, it's a certain entry in my top 3 all-time favourite burning apps, along with ImgBurn on Windows and CDVDBurn on RISC OS.
After extensive experience with burning discs in the ancient Sony CRX100E (24x Read, 4x Write, 2x Re-Write CD burner) in my K6 2 500 I humbly submit the following addition to the Potential Pitfalls section:-
Pay close attention to the minimum and maximum writing speeds of your media, and compare them with the maximum writing speeds of your drive. Writing to media with a minimum speed setting higher than your drive is capable of will result in failure - for example, attempting to write to a 4x-10x CDRW on a drive with a maximum RW speed of 2x. This is most likely to be an issue when using new discs in an old system.
Last edited by Jades on Sat 25 Feb 2012, 23:53, edited 2 times in total.
Zhaan - AMD K6 2 500, 512MB RAM, ATI Rage 128 VR. Full install Wary 5.5 [url=http://tinyurl.com/dy66kh8]HardInfo Report[/url]
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Forgot to mention this.
Feature Request
The first run of Pburn should automatically pop up the window to select the Burner Device, there have been a few occasions where I've set up a new pupsave and Puppy and Pburn have selected the wrong optical drive as the burner.
Feature Request
The first run of Pburn should automatically pop up the window to select the Burner Device, there have been a few occasions where I've set up a new pupsave and Puppy and Pburn have selected the wrong optical drive as the burner.
Zhaan - AMD K6 2 500, 512MB RAM, ATI Rage 128 VR. Full install Wary 5.5 [url=http://tinyurl.com/dy66kh8]HardInfo Report[/url]
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Re: feature request
On the last point, I'd hope that that was still optional - I'm currently having major problems with a dodgy HDD and am booting Puppy from LiveCD with the Pupsave on a USB stick. Pburn has been invaluable in trying to salvage my data, considering that I cannot currently boot XP at all. In my circumstances, Pburn automatically writing its temporary storage to the HDD would be a very bad thing indeed.01micko wrote:Temporary storage is coded to $HOME/my-documents/tmp and I bet nearly all frugal users change this immediately to /mnt/home (well I do anyway). Of course this may not be the best choice for an USB install, you would probably want to mount a hdd partition for that.
Zhaan - AMD K6 2 500, 512MB RAM, ATI Rage 128 VR. Full install Wary 5.5 [url=http://tinyurl.com/dy66kh8]HardInfo Report[/url]
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
3.5.0 quirks
Installed pburn 3.5.0 in lupu 5.2.8 today, and tried copying my lupu liveCD.
As usual, pburn opened with the temp directory set to /root/my-documents/tmp, which limits tmp storage to the free space left in my 2fs save file, by default, so I immediately set out to change it.
As usual, I selected the existing folder /pburn on a non-home partition (sda3), but must have hit the wrong key in the file navigator, because the tmp window then showed /sda3/2GBsd/ as the temp directory.
I tried again, and this time correctly selected /sda3/pburn, but now got the following error message:
Now, looking at the directory, I noticed that 2GBsd was the first entry (alphabetically) in the /sda3 partition. So I renamed /sda3/pburntmp to sda3/1pburntmp, and tried resetting it as the temp directory. This time, it took effect. Makes no sense to me but, perhaps to others...
NB: after closing and re-opening Pburn, I find that the temporary directory has defaulted back to /root/my-documents/tmp, just as it has in previous versions.
NB2: When I discover this, I try changing the temporary file from the /file/preferences menu. There, /sda3/pburntmp gives the same:
message, while from the "burn" window, it's still accepted (but reverts again as soon as I close the window and reopen it - so who knows if it works?)
Next, I choose burn-on-the-fly, select the burn and source drives
NB: I also find it impossible to set these - they default to cd-rom whenever I reopen pburn, and must be designated anew.
And start the copy of my lupu 5.2.8 LiveCd, using the default automatic speed setting. Everything seems to run fine until the end, then there's an error message instead of the invitation to verify, and so I save the log:
One other small annoyance (I haven't retried copying an audio disk yet, that would be a large annoyance), the inability to set the target directory for the pburn log, and the inability of the pburn log to automatically set a unique tag (dd/mm/yy_nn would be nice).
I wish now I had more CD-RW disks. Turning out coasters with Pburn is even more annoying.
As usual, pburn opened with the temp directory set to /root/my-documents/tmp, which limits tmp storage to the free space left in my 2fs save file, by default, so I immediately set out to change it.
As usual, I selected the existing folder /pburn on a non-home partition (sda3), but must have hit the wrong key in the file navigator, because the tmp window then showed /sda3/2GBsd/ as the temp directory.
I tried again, and this time correctly selected /sda3/pburn, but now got the following error message:
Then I tried creating a new folder, /sda3/pburntmp but got exactly the same error messageselection is not a directory
Now, looking at the directory, I noticed that 2GBsd was the first entry (alphabetically) in the /sda3 partition. So I renamed /sda3/pburntmp to sda3/1pburntmp, and tried resetting it as the temp directory. This time, it took effect. Makes no sense to me but, perhaps to others...
NB: after closing and re-opening Pburn, I find that the temporary directory has defaulted back to /root/my-documents/tmp, just as it has in previous versions.
NB2: When I discover this, I try changing the temporary file from the /file/preferences menu. There, /sda3/pburntmp gives the same:
selection is not a directory
message, while from the "burn" window, it's still accepted (but reverts again as soon as I close the window and reopen it - so who knows if it works?)
Next, I choose burn-on-the-fly, select the burn and source drives
NB: I also find it impossible to set these - they default to cd-rom whenever I reopen pburn, and must be designated anew.
And start the copy of my lupu 5.2.8 LiveCd, using the default automatic speed setting. Everything seems to run fine until the end, then there's an error message instead of the invitation to verify, and so I save the log:
I then try booting from the freshly burned disk, and it seems to work fine. In fact, I'm online with it right now.Pburn version 3.5.0
###################################################
COMMAND:
###################################################
cdrecord -v dev=/dev/sr0 fs=8m driveropts=burnfree -isosize /dev/sr1
###################################################
OUTPUT:
###################################################
wodim: No write mode specified.
wodim: Assuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
scsidev: '/dev/sr0'
devname: '/dev/sr0'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.10
SCSI buffer size: 64512
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
TOC Type: 1 = CD-ROM
Driveropts: 'burnfree'
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'HL-DT-ST'
Identification : 'DVDRAM GSA-H10N '
Revision : 'JL10'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x000A (CD-RW)
Profile: 0x0012 (DVD-RAM)
Profile: 0x0011 (DVD-R sequential recording)
Profile: 0x0015 (DVD-R/DL sequential recording)
Profile: 0x0016 (DVD-R/DL layer jump recording)
Profile: 0x0014 (DVD-RW sequential recording)
Profile: 0x0013 (DVD-RW restricted overwrite)
Profile: 0x001A (DVD+RW)
Profile: 0x001B (DVD+R)
Profile: 0x002B (DVD+R/DL)
Profile: 0x0010 (DVD-ROM)
Profile: 0x0009 (CD-R)
Profile: 0x000A (CD-RW) (current)
Profile: 0x0008 (CD-ROM)
Profile: 0x0002 (Removable disk)
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Drive buf size : 1053696 = 1029 KB
Drive DMA Speed: 12264 kB/s 69x CD 8x DVD
FIFO size : 8388608 = 8192 KB
Speed set to 1764 KB/s
Track 01: data 129 MB padsize: 30 KB
Total size: 148 MB (14:42.17) = 66163 sectors
Lout start: 148 MB (14:44/13) = 66163 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 3
Reference speed: 6
Is not unrestricted
Is erasable
Disk sub type: High speed Rewritable (CAV) media (1)
ATIP start of lead in: -11745 (97:25/30)
ATIP start of lead out: 359848 (79:59/73)
1T speed low: 4 1T speed high: 10
2T speed low: 4 2T speed high: 0 (reserved val 6)
power mult factor: 1 5
recommended erase/write power: 5
A1 values: 24 1A D8
A2 values: 26 B2 4A
Disk type: Phase change
Manuf. index: 40
Manufacturer: INFODISC Technology Co., Ltd.
Blocks total: 359848 Blocks current: 359848 Blocks remaining: 293685
Starting to write CD/DVD at speed 10.0 in real TAO mode for single session.
Last chance to quit, starting real write in 4 seconds. 3 seconds. 2 seconds. 1 seconds. 0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Starting new track at sector: 0
Track 01: 0 of 129 MB written.
Track 01: 1 of 129 MB written (fifo 100%) [buf 99%] 4.9x.
Track 01: 2 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 3 of 129 MB written (fifo 100%) [buf 99%] 10.8x.
Track 01: 4 of 129 MB written (fifo 100%) [buf 99%] 10.4x.
Track 01: 5 of 129 MB written (fifo 100%) [buf 100%] 10.7x.
Track 01: 6 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 7 of 129 MB written (fifo 100%) [buf 99%] 10.7x.
Track 01: 8 of 129 MB written (fifo 100%) [buf 100%] 10.4x.
Track 01: 9 of 129 MB written (fifo 100%) [buf 99%] 10.6x.
Track 01: 10 of 129 MB written (fifo 100%) [buf 99%] 10.4x.
Track 01: 11 of 129 MB written (fifo 100%) [buf 99%] 10.7x.
Track 01: 12 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 13 of 129 MB written (fifo 100%) [buf 99%] 10.6x.
Track 01: 14 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 15 of 129 MB written (fifo 100%) [buf 100%] 10.6x.
Track 01: 16 of 129 MB written (fifo 100%) [buf 99%] 10.2x.
Track 01: 17 of 129 MB written (fifo 100%) [buf 99%] 10.6x.
Track 01: 18 of 129 MB written (fifo 100%) [buf 100%] 10.3x.
Track 01: 19 of 129 MB written (fifo 100%) [buf 99%] 10.5x.
Track 01: 20 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 21 of 129 MB written (fifo 100%) [buf 99%] 10.6x.
Track 01: 22 of 129 MB written (fifo 100%) [buf 99%] 10.2x.
Track 01: 23 of 129 MB written (fifo 100%) [buf 99%] 10.5x.
Track 01: 24 of 129 MB written (fifo 100%) [buf 99%] 10.2x.
Track 01: 25 of 129 MB written (fifo 100%) [buf 100%] 10.5x.
Track 01: 26 of 129 MB written (fifo 100%) [buf 99%] 10.1x.
Track 01: 27 of 129 MB written (fifo 100%) [buf 99%] 10.5x.
Track 01: 28 of 129 MB written (fifo 100%) [buf 100%] 10.2x.
Track 01: 29 of 129 MB written (fifo 100%) [buf 99%] 10.4x.
Track 01: 30 of 129 MB written (fifo 100%) [buf 99%] 10.2x.
Track 01: 31 of 129 MB written (fifo 100%) [buf 99%] 10.5x.
Track 01: 32 of 129 MB written (fifo 100%) [buf 99%] 10.1x.
Track 01: 33 of 129 MB written (fifo 100%) [buf 99%] 10.4x.
Track 01: 34 of 129 MB written (fifo 100%) [buf 99%] 10.8x.
Track 01: 35 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 36 of 129 MB written (fifo 100%) [buf 99%] 10.7x.
Track 01: 37 of 129 MB written (fifo 100%) [buf 99%] 10.4x.
Track 01: 38 of 129 MB written (fifo 100%) [buf 100%] 10.7x.
Track 01: 39 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 40 of 129 MB written (fifo 100%) [buf 99%] 10.7x.
Track 01: 41 of 129 MB written (fifo 100%) [buf 100%] 10.4x.
Track 01: 42 of 129 MB written (fifo 100%) [buf 99%] 10.6x.
Track 01: 43 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 44 of 129 MB written (fifo 100%) [buf 99%] 10.6x.
Track 01: 45 of 129 MB written (fifo 100%) [buf 99%] 10.2x.
Track 01: 46 of 129 MB written (fifo 100%) [buf 99%] 10.6x.
Track 01: 47 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 48 of 129 MB written (fifo 100%) [buf 100%] 10.6x.
Track 01: 49 of 129 MB written (fifo 100%) [buf 99%] 10.2x.
Track 01: 50 of 129 MB written (fifo 100%) [buf 99%] 10.6x.
Track 01: 51 of 129 MB written (fifo 100%) [buf 100%] 10.3x.
Track 01: 52 of 129 MB written (fifo 100%) [buf 99%] 10.5x.
Track 01: 53 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 54 of 129 MB written (fifo 100%) [buf 99%] 10.5x.
Track 01: 55 of 129 MB written (fifo 100%) [buf 99%] 10.1x.
Track 01: 56 of 129 MB written (fifo 100%) [buf 99%] 10.5x.
Track 01: 57 of 129 MB written (fifo 100%) [buf 99%] 10.2x.
Track 01: 58 of 129 MB written (fifo 100%) [buf 100%] 10.5x.
Track 01: 59 of 129 MB written (fifo 100%) [buf 99%] 10.1x.
Track 01: 60 of 129 MB written (fifo 100%) [buf 99%] 10.5x.
Track 01: 61 of 129 MB written (fifo 100%) [buf 100%] 10.2x.
Track 01: 62 of 129 MB written (fifo 100%) [buf 99%] 10.4x.
Track 01: 63 of 129 MB written (fifo 100%) [buf 99%] 10.2x.
Track 01: 64 of 129 MB written (fifo 100%) [buf 100%] 10.4x.
Track 01: 65 of 129 MB written (fifo 100%) [buf 99%] 10.6x.
Track 01: 66 of 129 MB written (fifo 100%) [buf 99%] 10.4x.
Track 01: 67 of 129 MB written (fifo 100%) [buf 99%] 10.7x.
Track 01: 68 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 69 of 129 MB written (fifo 100%) [buf 99%] 10.7x.
Track 01: 70 of 129 MB written (fifo 100%) [buf 99%] 10.4x.
Track 01: 71 of 129 MB written (fifo 100%) [buf 100%] 10.7x.
Track 01: 72 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 73 of 129 MB written (fifo 100%) [buf 99%] 10.7x.
Track 01: 74 of 129 MB written (fifo 100%) [buf 100%] 10.3x.
Track 01: 75 of 129 MB written (fifo 100%) [buf 99%] 10.5x.
Track 01: 76 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 77 of 129 MB written (fifo 100%) [buf 99%] 10.6x.
Track 01: 78 of 129 MB written (fifo 100%) [buf 99%] 10.2x.
Track 01: 79 of 129 MB written (fifo 100%) [buf 99%] 10.6x.
Track 01: 80 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 81 of 129 MB written (fifo 100%) [buf 100%] 10.6x.
Track 01: 82 of 129 MB written (fifo 100%) [buf 99%] 10.2x.
Track 01: 83 of 129 MB written (fifo 100%) [buf 99%] 10.6x.
Track 01: 84 of 129 MB written (fifo 100%) [buf 100%] 10.3x.
Track 01: 85 of 129 MB written (fifo 100%) [buf 99%] 10.4x.
Track 01: 86 of 129 MB written (fifo 100%) [buf 99%] 10.2x.
Track 01: 87 of 129 MB written (fifo 100%) [buf 99%] 10.5x.
Track 01: 88 of 129 MB written (fifo 100%) [buf 99%] 10.1x.
Track 01: 89 of 129 MB written (fifo 100%) [buf 99%] 10.5x.
Track 01: 90 of 129 MB written (fifo 100%) [buf 99%] 10.2x.
Track 01: 91 of 129 MB written (fifo 100%) [buf 100%] 10.5x.
Track 01: 92 of 129 MB written (fifo 100%) [buf 99%] 10.1x.
Track 01: 93 of 129 MB written (fifo 100%) [buf 99%] 10.5x.
Track 01: 94 of 129 MB written (fifo 100%) [buf 100%] 10.2x.
Track 01: 95 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 96 of 129 MB written (fifo 100%) [buf 99%] 10.8x.
Track 01: 97 of 129 MB written (fifo 100%) [buf 100%] 10.4x.
Track 01: 98 of 129 MB written (fifo 100%) [buf 99%] 10.6x.
Track 01: 99 of 129 MB written (fifo 100%) [buf 99%] 10.4x.
Track 01: 100 of 129 MB written (fifo 100%) [buf 99%] 10.7x.
Track 01: 101 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 102 of 129 MB written (fifo 100%) [buf 99%] 10.7x.
Track 01: 103 of 129 MB written (fifo 100%) [buf 99%] 10.4x.
Track 01: 104 of 129 MB written (fifo 100%) [buf 100%] 10.7x.
Track 01: 105 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 106 of 129 MB written (fifo 100%) [buf 99%] 10.7x.
Track 01: 107 of 129 MB written (fifo 100%) [buf 100%] 10.3x.
Track 01: 108 of 129 MB written (fifo 100%) [buf 99%] 10.5x.
Track 01: 109 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 110 of 129 MB written (fifo 100%) [buf 99%] 10.6x.
Track 01: 111 of 129 MB written (fifo 100%) [buf 99%] 10.2x.
Track 01: 112 of 129 MB written (fifo 100%) [buf 99%] 10.6x.
Track 01: 113 of 129 MB written (fifo 100%) [buf 99%] 10.3x.
Track 01: 114 of 129 MB written (fifo 100%) [buf 100%] 10.6x.
Track 01: 115 of 129 MB written (fifo 100%) [buf 99%] 10.2x.
Track 01: 116 of 129 MB written (fifo 100%) [buf 99%] 10.5x.
Track 01: 117 of 129 MB written (fifo 100%) [buf 100%] 10.2x.
Track 01: 118 of 129 MB written (fifo 100%) [buf 99%] 10.4x.
Track 01: 119 of 129 MB written (fifo 100%) [buf 99%] 10.2x.
Track 01: 120 of 129 MB written (fifo 100%) [buf 99%] 10.5x.
Track 01: 121 of 129 MB written (fifo 100%) [buf 99%] 10.1x.
Track 01: 122 of 129 MB written (fifo 92%) [buf 99%] 10.5x.
Track 01: 123 of 129 MB written (fifo 79%) [buf 99%] 10.2x.
Track 01: 124 of 129 MB written (fifo 67%) [buf 100%] 10.5x.
Track 01: 125 of 129 MB written (fifo 53%) [buf 99%] 10.1x.
Track 01: 126 of 129 MB written (fifo 40%) [buf 99%] 10.4x.
Track 01: 127 of 129 MB written (fifo 28%) [buf 100%] 10.8x.
Track 01: 128 of 129 MB written (fifo 14%) [buf 99%] 10.3x.
Track 01: 129 of 129 MB written (fifo 2%) [buf 99%] 10.7x.wodim: Input/output error. read error on input file
Writing time: 98.574s
wodim: fifo had 2134 puts and 2134 gets.
wodim: fifo was 1 times empty and 1992 times full, min fill was 0%.
Min drive buffer fill was 99%
One other small annoyance (I haven't retried copying an audio disk yet, that would be a large annoyance), the inability to set the target directory for the pburn log, and the inability of the pburn log to automatically set a unique tag (dd/mm/yy_nn would be nice).
I wish now I had more CD-RW disks. Turning out coasters with Pburn is even more annoying.
otropogo@gmail.com facebook.com/otropogo
After all these years with Puppy coding, it seems clear to me that if you want to offer good apps, - time will pass.Jades wrote:Delighted to see you're still developing Pburn
The Pburn timeline looks like this:
2007 24.Nov: Pburn 0.1 - Initial release.
2008 18.Aug: Pburn 2.0.0 - Things begins to settle
2009 26.Sep: Pburn 3.1.0 - Last release with new features.
2012 25.Feb: Pburn 3.5.0 - The 32. bugfix-release after 3.1.0
Added. Thanks a lot. I have never thought of this, but it is sure obvious.Jades wrote:I humbly submit the following addition to the Potential Pitfalls section:-
Pay close attention to the minimum and maximum writing speeds of your media, and compare them with the maximum writing speeds of your drive. Writing to media with a minimum speed setting higher than your drive is capable of will result in failure - for example, attempting to write to a 4x-10x CDRW on a drive with a maximum RW speed of 2x. This is most likely to be an issue when using new discs in an old system.
Sigmund
I will add to todo-listJades wrote:Forgot to mention this.
Feature Request
The first run of Pburn should automatically pop up the window to select the Burner Device, there have been a few occasions where I've set up a new pupsave and Puppy and Pburn have selected the wrong optical drive as the burner.
If more than 1 device is detected, always show window.
Sigmund
Re: feature request
3.5.0 is only checking for available free space in $HOME/my-documents/tmp. At last, - that is what matters.Jades wrote:On the last point, I'd hope that that was still optional - I'm currently having major problems with a dodgy HDD and am booting Puppy from LiveCD with the Pupsave on a USB stick. Pburn has been invaluable in trying to salvage my data, considering that I cannot currently boot XP at all. In my circumstances, Pburn automatically writing its temporary storage to the HDD would be a very bad thing indeed.01micko wrote:Temporary storage is coded to $HOME/my-documents/tmp and I bet nearly all frugal users change this immediately to /mnt/home (well I do anyway). Of course this may not be the best choice for an USB install, you would probably want to mount a hdd partition for that.
Re: 3.5.0 quirks
This sounds strange, so I gave it a test.otropogo wrote:Installed pburn 3.5.0 in lupu 5.2.8 today, and tried copying my lupu liveCD.
As usual, pburn opened with the temp directory set to /root/my-documents/tmp, which limits tmp storage to the free space left in my 2fs save file, by default, so I immediately set out to change it.
As usual, I selected the existing folder /pburn on a non-home partition (sda3), but must have hit the wrong key in the file navigator, because the tmp window then showed /sda3/2GBsd/ as the temp directory.
I tried again, and this time correctly selected /sda3/pburn, but now got the following error message:
Then I tried creating a new folder, /sda3/pburntmp but got exactly the same error messageCode: Select all
selection is not a directory
Now, looking at the directory, I noticed that 2GBsd was the first entry (alphabetically) in the /sda3 partition. So I renamed /sda3/pburntmp to sda3/1pburntmp, and tried resetting it as the temp directory. This time, it took effect. Makes no sense to me but, perhaps to others...
NB: after closing and re-opening Pburn, I find that the temporary directory has defaulted back to /root/my-documents/tmp, just as it has in previous versions.
NB2: When I discover this, I try changing the temporary file from the /file/preferences menu. There, /sda3/pburntmp gives the same:
Code: Select all
selection is not a directory
message, while from the "burn" window, it's still accepted (but reverts again as soon as I close the window and reopen it - so who knows if it works?)
I can not reproduce your trouble. What type of filesystem are you working on?
Also checked that the setting is new in the burn-options dialog.
Sigmund
Small annoyance, but still annoying.otropogo wrote:One other small annoyance (I haven't retried copying an audio disk yet, that would be a large annoyance), the inability to set the target directory for the pburn log, and the inability of the pburn log to automatically set a unique tag (dd/mm/yy_nn would be nice).
When it comes to your burn-error, I can't say more than; as long as wodim prints an error, Pburn has to take that serious, and point you to the error-dialog. If the burning seems to work for you - Great! But there still seems to be an error - or a bug in wodim.
Sigmund
cue still does not burn
Sadly .cue does get accepted, but it does error even before starting writing
Log as well as cue attached
sebus
Log as well as cue attached
sebus
- Attachments
-
- error.zip
- (2.54 KiB) Downloaded 170 times
sebus
Looking at your log, this line is interestingWould you please try to set burn mode to raw. Since burning cue, don't show the burn-options dialog, you have to set this in the exec-file: /root/.pburn/tmp/exec
After selected the cue-file, pburn shows up a confirmation-dialog before the actual burning starts. Now, Pburn has built the command, and it is time to edit the exec file:
change -dao to -raw96r
Do you have an uncommon/old burner device?
Sigmund
Looking at your log, this line is interesting
Code: Select all
wodim: CUE sheet still not accepted. Please try to write in RAW (-raw96r) mode.
After selected the cue-file, pburn shows up a confirmation-dialog before the actual burning starts. Now, Pburn has built the command, and it is time to edit the exec file:
change -dao to -raw96r
Do you have an uncommon/old burner device?
Sigmund
The log file also shows what device is used:
http://support.dell.com/support/edocs/s ... /specs.htm
DVD+-RW GSA-H73N
The exec does NOT get created while the dialog waits for an input! (see attached)
I can try to run cdrecord from command line, but it does not do cue with raw!
An "ancient" threads with same error (but also a mention of a bug):
http://us.generation-nt.com/bug-401308- ... 07061.html
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402222
It seems that update to an ancient cdrecord is needed (at least in Fatdog64)
Cdrecord-yelling-line-to-tell-frontends-to-use-it-like-version 2.01.01a03-dvd
So I updated (compiled) cdrecord from
http://cdrecord.berlios.de/private/cdrecord.html
ftp://ftp.berlios.de/pub/cdrecord
to
Cdrecord-ProDVD-ProBD-Clone 3.00 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2010 Jцrg Schilling
and can burn .cue/bin with no problems (log attached) from command line
./cdrecord dev=/dev/sr0 -dao -v -text cuefile="/mnt/sdb1/Music/ADELE-21.cue"
sebus
http://support.dell.com/support/edocs/s ... /specs.htm
DVD+-RW GSA-H73N
The exec does NOT get created while the dialog waits for an input! (see attached)
I can try to run cdrecord from command line, but it does not do cue with raw!
Code: Select all
# cdrecord dev=/dev/sr0 -raw96r -v -text cuefile="/mnt/sdb1/Music/ADELE-21.cue"
wodim: The cuefile= option only works with -dao.
Usage: wodim [options] track1...trackn
Use wodim -help
to get a list of valid options.
Use wodim blank=help
to get a list of valid blanking options.
Use wodim dev=b,t,l driveropts=help -checkdrive
to get a list of drive specific options.
Use wodim dev=help
to get a list of possible SCSI transport specifiers.
http://us.generation-nt.com/bug-401308- ... 07061.html
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402222
It seems that update to an ancient cdrecord is needed (at least in Fatdog64)
Cdrecord-yelling-line-to-tell-frontends-to-use-it-like-version 2.01.01a03-dvd
So I updated (compiled) cdrecord from
http://cdrecord.berlios.de/private/cdrecord.html
ftp://ftp.berlios.de/pub/cdrecord
to
Cdrecord-ProDVD-ProBD-Clone 3.00 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2010 Jцrg Schilling
and can burn .cue/bin with no problems (log attached) from command line
./cdrecord dev=/dev/sr0 -dao -v -text cuefile="/mnt/sdb1/Music/ADELE-21.cue"
sebus
- Attachments
-
- cdrecord3.zip
- (2.24 KiB) Downloaded 289 times
-
- no nexec.png
- (47.61 KiB) Downloaded 336 times
Last edited by sebus on Mon 27 Feb 2012, 11:15, edited 7 times in total.
Re: 3.5.0 quirks
Ok. I tested setting temp folder to /sda3/pburn again, and got the same error message as previously.zigbert wrote:This sounds strange, so I gave it a test.otropogo wrote:..
....
I noticed that 2GBsd was the first entry (alphabetically) in the /sda3 partition. So I renamed /sda3/pburntmp to sda3/1pburntmp, and tried resetting it as the temp directory. This time, it took effect. Makes no sense to me but, perhaps to others...
NB: after closing and re-opening Pburn, I find that the temporary directory has defaulted back to /root/my-documents/tmp, just as it has in previous versions.
NB2: When I discover this, I try changing the temporary file from the /file/preferences menu. There, /sda3/pburntmp gives the same:
Code: Select all
selection is not a directory
message, while from the "burn" window, it's still accepted (but reverts again as soon as I close the window and reopen it - so who knows if it works?)
I can not reproduce your trouble. What type of filesystem are you working on?
Also checked that the setting is new in the burn-options dialog.
Sigmund
BTW the partition is formated vfat.
I then used the folder 1pburntmp, and succeeded as before in entering it in the temp field. This time, however, I hit the save button (previously neglected), and saved the file pburn.pnb to /root.
Now, the temp file preference appears as changed after closing and reopening pburn. Of course, this still doesn't explain the previous refusals with /sda3/pburn and /sda3/pburntmp, which made getting to the save stage impossible, since the preference couldn't be entered.
A clue may exist in that, after achieving this save (or apparent save, as I haven't actually tested it with a burn), I then tried changing the preference again to /sda3/pburn, and now, for the first time ever, the entry was accepted without any error message!
I then saved, and got the warning 'pburn.pbn exists. Replace?' and chose replace. Again the preference selection survived closing and reopening pburn.
I then changed the name of /sda3/1pburntmp to /sda3/pburntmp and set the temp preference to that and saved.
Now, when I open pburn, it displays /sda3/pburntmp as the temporary folder. However, I note that BOTH the pburntmp AND pburn folders display a folder named pburn_symlink_tree.
Hope this helps.
As for the unverified burn - in retrospect, my statement that "it works" may not mean much, since I have the Puppy528.sfs file written to the hard drive, so the CD only boots the system and loads the sfs and 2fs files into memory from the hard drive.
otropogo@gmail.com facebook.com/otropogo