pBurn 4.3.19

Audio editors, music players, video players, burning software, etc.
Message
Author
User avatar
zigbert
Posts: 6621
Joined: Wed 29 Mar 2006, 18:13
Location: Valåmoen, Norway
Contact:

#1641 Post by zigbert »

Be aware that not all CD-player supports CD-R, and even fewer supports CD-RW. It seems to me that the more expensive the CD-player is, the more sensitive it is to home-brewed discs.

BUT, of course, - it should work in the same device that you burnt it in...

For the benefit of Pburn, it would be good if you tested another burner app with the same burner. Like this, I would 'know' if it is Pburn or your hardware that is the trouble.


Thank you
Sigmund

User avatar
stiginge
Posts: 420
Joined: Thu 22 Mar 2007, 10:10
Location: Kerry, Ireland

#1642 Post by stiginge »

zigbert wrote:Be aware that not all CD-player supports CD-R, and even fewer supports CD-RW. It seems to me that the more expensive the CD-player is, the more sensitive it is to home-brewed discs.

BUT, of course, - it should work in the same device that you burnt it in...

For the benefit of Pburn, it would be good if you tested another burner app with the same burner. Like this, I would 'know' if it is Pburn or your hardware that is the trouble.


Thank you
Sigmund
Do you believe that I'd have a substantially better chance so with cd-r disks?

Unfortunately, I do not have another burn-capable cddrive at the moment in my possession, but it's probably worth a try if/when the opportunity arises at a future date.
Buy silver, crash JPMorgan

User avatar
zigbert
Posts: 6621
Joined: Wed 29 Mar 2006, 18:13
Location: Valåmoen, Norway
Contact:

#1643 Post by zigbert »

sebus
I am looking at Pburn, and the initial test of open a cue file works.

Image

It must be said that this is a fake cue-file so it errors during burn.... I don't have a cue file available for testing actual burning.

Can you describe your problem more accurate.


Thanks
Sigmund

User avatar
zigbert
Posts: 6621
Joined: Wed 29 Mar 2006, 18:13
Location: Valåmoen, Norway
Contact:

#1644 Post by zigbert »

I have bought a Blu-ray burner (incredible what we do for Puppy), and will improve the detection of Blu-ray discs.


Sigmund

sebus
Posts: 67
Joined: Fri 20 Jan 2012, 20:57

#1645 Post by sebus »

As I said, Not a valid file!

The file is valid, as I have no problem buring it back on Windows with Imgburn

sebus
Attachments
pburn-cue.png
(113.25 KiB) Downloaded 258 times

User avatar
zigbert
Posts: 6621
Joined: Wed 29 Mar 2006, 18:13
Location: Valåmoen, Norway
Contact:

#1646 Post by zigbert »

Thank you sebus.
I can not see the image right now. It seems to be a problem with the forum...... I'll check tomorrow


Sigmund

User avatar
zigbert
Posts: 6621
Joined: Wed 29 Mar 2006, 18:13
Location: Valåmoen, Norway
Contact:

#1647 Post by zigbert »

For Flash

Image

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

feature request

#1648 Post by 01micko »

Feature request

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.

Code: Select all

if [ -f /etc/rc.d/PUPSTATE ];then . /etc/rc.d/PUPSTATE #are we in Puppy?
 case "$PUPMODE in
 6|12) TEMP_STORAGE=/mnt/home ;;
 *)TEMP_STORAGE=$HOME/my-documents/tmp ;;
 esac
fi
.. or code to that effect.

Thanks for consideration.
Puppy Linux Blog - contact me for access

User avatar
zigbert
Posts: 6621
Joined: Wed 29 Mar 2006, 18:13
Location: Valåmoen, Norway
Contact:

#1649 Post by zigbert »

Mick
Thank you for the code. I have already changed this code for next release to more focus on free space instead of Puppy-installation. I get more frequently response from outside the Puppy world about usiing Pburn in other distros. Because of this, I will try to avoid Puppy-specific where possible.

But in the end, we might want to check Pupmode in addition to free space.... let's see.


Thanks again
Sigmund

User avatar
zigbert
Posts: 6621
Joined: Wed 29 Mar 2006, 18:13
Location: Valåmoen, Norway
Contact:

#1650 Post by zigbert »

sebus wrote:As I said, Not a valid file!

The file is valid, as I have no problem buring it back on Windows with Imgburn

sebus
Sorry for the delay!!!!

Pburn is not allowing capitals in file extension. So... *.cue should work - not *.CUE.

Fixed for next release


Thank you
Sigmund

User avatar
zigbert
Posts: 6621
Joined: Wed 29 Mar 2006, 18:13
Location: Valåmoen, Norway
Contact:

#1651 Post by zigbert »

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

User avatar
zigbert
Posts: 6621
Joined: Wed 29 Mar 2006, 18:13
Location: Valåmoen, Norway
Contact:

#1652 Post by zigbert »

Note that 3.5.0 _only_ has improved the blu-ray support for BD-R. I am not rich enough for owning my own BD-RE nor BDXL, so until status changes, Pburn is only tested with the cheapest blu-ray media. :)


Sigmund

disciple
Posts: 6984
Joined: Sun 21 May 2006, 01:46
Location: Auckland, New Zealand

#1653 Post by disciple »

zigbert wrote:- Bugfix: Detect optical device in Porteus (thanks to Ahua in the Porteus forum)
So people are using Pburn on a distro where KDE is default, in preference to K3B. Interesting.
Do you know a good gtkdialog program? Please post a link here

Classic Puppy quotes

ROOT FOREVER
GTK2 FOREVER

Jades
Posts: 466
Joined: Sat 07 Aug 2010, 22:07
Location: Somewhere in Blighty.
Contact:

#1654 Post by Jades »

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.
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

Jades
Posts: 466
Joined: Sat 07 Aug 2010, 22:07
Location: Somewhere in Blighty.
Contact:

#1655 Post by Jades »

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.
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

Jades
Posts: 466
Joined: Sat 07 Aug 2010, 22:07
Location: Somewhere in Blighty.
Contact:

Re: feature request

#1656 Post by Jades »

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.
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.
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

User avatar
otropogo
Posts: 764
Joined: Sat 24 Oct 2009, 15:17
Location: Montreal
Contact:

3.5.0 quirks

#1657 Post by otropogo »

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:
selection is not a directory
Then I tried creating a new folder, /sda3/pburntmp but got exactly the same 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:
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:
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%
I then try booting from the freshly burned disk, and it seems to work fine. In fact, I'm online with it right now.

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

User avatar
zigbert
Posts: 6621
Joined: Wed 29 Mar 2006, 18:13
Location: Valåmoen, Norway
Contact:

#1658 Post by zigbert »

Jades wrote:Delighted to see you're still developing Pburn
After all these years with Puppy coding, it seems clear to me that if you want to offer good apps, - time will pass.
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
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.
Added. Thanks a lot. I have never thought of this, but it is sure obvious.


Sigmund

User avatar
zigbert
Posts: 6621
Joined: Wed 29 Mar 2006, 18:13
Location: Valåmoen, Norway
Contact:

#1659 Post by zigbert »

Jades 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.
I will add to todo-list
If more than 1 device is detected, always show window.


Sigmund

User avatar
zigbert
Posts: 6621
Joined: Wed 29 Mar 2006, 18:13
Location: Valåmoen, Norway
Contact:

Re: feature request

#1660 Post by zigbert »

Jades wrote:
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.
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.
3.5.0 is only checking for available free space in $HOME/my-documents/tmp. At last, - that is what matters.

Post Reply