pBurn 4.3.19
I tried burn on the fly also with same result. I'm pretty sure I was able to burn a DVD, but not a CD, before with v 0.4, but not with 0.5.
Last edited by Henry on Mon 24 Dec 2007, 14:33, edited 1 time in total.
Good morning, Zigbert,
You have been busy!! The new GUI and help files are very fine.
Henry
You have been busy!! The new GUI and help files are very fine.
Henry
Last edited by Henry on Mon 24 Dec 2007, 14:30, edited 1 time in total.
- Dingo
- Posts: 1437
- Joined: Tue 11 Dec 2007, 17:48
- Location: somewhere at the end of rainbow...
- Contact:
The same for me
a couple of problems still
on puppy 3.0.1
1= temp storage:
I have tried to change storage setting in an empty directory on a vfat filesystem, but, after folder selection, the box shows not to me the path. stills blank so, the temp storage is setted somewhere on the pup_save file (to tmp directory I think) not so good thing. Maybe, it's a problem to move temp storage directory in the program?
now:
choosing to leave the settings to default (temp storage on pup_save file) The burn works, fully without problems
cheking box to choose burning on fly, gives an error
INPUT BUFFER ERROR
2= other problem (lesser)
after importing previous disc sessions, the filesize of imported files from session is showed as 0
a couple of problems still
on puppy 3.0.1
1= temp storage:
I have tried to change storage setting in an empty directory on a vfat filesystem, but, after folder selection, the box shows not to me the path. stills blank so, the temp storage is setted somewhere on the pup_save file (to tmp directory I think) not so good thing. Maybe, it's a problem to move temp storage directory in the program?
now:
choosing to leave the settings to default (temp storage on pup_save file) The burn works, fully without problems
cheking box to choose burning on fly, gives an error
INPUT BUFFER ERROR
2= other problem (lesser)
after importing previous disc sessions, the filesize of imported files from session is showed as 0
Excellent burner
Hi, Zigbert,
Merry Christmas!
Henry
Merry Christmas!
Henry
Last edited by Henry on Mon 24 Dec 2007, 14:27, edited 1 time in total.
Dingo
Your #1: When choosing a directory, you must select the dir in the right panel. (not dig inside it). This is somewhat unlogical, and I will rethink this.
your #2: Size of file from imported sessions are not meant to be shown.
Henry
Burning on-the-fly is much easier with DVDs. If you check the 'advanced' - you'll see the burning command. If you ever dive into this, and gets your CDs burnt on-the-fly, please tell us what commandline you get. Burning on-the-fly CDs seems be more system-sensitive than the 'growisofs' command used for DVDs. I'm not at all any kind of guru, - so I want feedback to optimize the burning parameters.
Merry christmas
Sigmund
Your #1: When choosing a directory, you must select the dir in the right panel. (not dig inside it). This is somewhat unlogical, and I will rethink this.
your #2: Size of file from imported sessions are not meant to be shown.
Henry
Burning on-the-fly is much easier with DVDs. If you check the 'advanced' - you'll see the burning command. If you ever dive into this, and gets your CDs burnt on-the-fly, please tell us what commandline you get. Burning on-the-fly CDs seems be more system-sensitive than the 'growisofs' command used for DVDs. I'm not at all any kind of guru, - so I want feedback to optimize the burning parameters.
Merry christmas
Sigmund
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
I have tested Pburn, and I have a very long list of problems. I didn't try a CD, only a DVD, and tested on Dingo.
1.
/proc/ide does not exist in Dingo. All CD/DVD drives are now /dev/sr* and 'probdisk' finds them, or you can look in /sys/block.
2.
The first time I tried it, I ran pburn from a terminal, and choose a directory to burn, clicked "Burn" button, then got the Preferences window -- however that was too late as I saw lots of messages that /tmp had become full. That's all wrong, should default to "on the fly" to avoid such a problem.
3.
Second attempt, I ran Preferences first, chose DVD and on-the-fly, but the "Advanced" option to edit the commandline did not work at all.
4.
I wanted to edit the commandline, as Rockridge option should use '-R' and not '-r', as the latter modifies file attributes to read-only which is bad when files are recovered off the DVD.
5.
When the Preferences window was up, the terminal window kept writing lines about "/tmp/pburn-splash: no such file", continuously, scrolling off the window.
6.
When I clicked the Burn button, a great many error messages in the terminal, including something like "/usr/local/pburn/func-exec: line 13: /tmp/pburn-log: no space left on device" -- but it was a new DVD-R.
1.
/proc/ide does not exist in Dingo. All CD/DVD drives are now /dev/sr* and 'probdisk' finds them, or you can look in /sys/block.
2.
The first time I tried it, I ran pburn from a terminal, and choose a directory to burn, clicked "Burn" button, then got the Preferences window -- however that was too late as I saw lots of messages that /tmp had become full. That's all wrong, should default to "on the fly" to avoid such a problem.
3.
Second attempt, I ran Preferences first, chose DVD and on-the-fly, but the "Advanced" option to edit the commandline did not work at all.
4.
I wanted to edit the commandline, as Rockridge option should use '-R' and not '-r', as the latter modifies file attributes to read-only which is bad when files are recovered off the DVD.
5.
When the Preferences window was up, the terminal window kept writing lines about "/tmp/pburn-splash: no such file", continuously, scrolling off the window.
6.
When I clicked the Burn button, a great many error messages in the terminal, including something like "/usr/local/pburn/func-exec: line 13: /tmp/pburn-log: no space left on device" -- but it was a new DVD-R.
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
zigbert,
One thing I don't understand. You have done it the same way that nathan did, creating a directory in /tmp with symlinks in the case of on-the-fly, but perhaps that isn't necessary. A list of directories and files can be supplied to be burnt, without needing to build a directory of symlinks -- it has been awhile, but I seem to remember that is possible.
Note, I've never had any problem with on-the-fly burning of CDs or DVDs, I think it should be the default for both cases.
One thing I don't understand. You have done it the same way that nathan did, creating a directory in /tmp with symlinks in the case of on-the-fly, but perhaps that isn't necessary. A list of directories and files can be supplied to be burnt, without needing to build a directory of symlinks -- it has been awhile, but I seem to remember that is possible.
Note, I've never had any problem with on-the-fly burning of CDs or DVDs, I think it should be the default for both cases.
[url]https://bkhome.org/news/[/url]
magerlab
In basic you translate the language template and helpfile, and changes filename from english to russian. If files are put into same directory as the english files, program will autodetect new language, and it is then available in 'configure'. To build a new package of russian pbackup you repack it after language is changed. Also keep the configfile in /root/...(.pbackup/pbackuprc or .pfindrc). Please wait to translate Pburn until it reaches beta release. That will be Pburn 0.9.
BarryK
Great bugreport, but I can't recontruct a bleep of it. I guess I need to install dingo for futher testing. The detection of burning devices will have the same trouble in Pbackup.
-R for rockridge will be default in next release. Thank you.
Sigmund
In basic you translate the language template and helpfile, and changes filename from english to russian. If files are put into same directory as the english files, program will autodetect new language, and it is then available in 'configure'. To build a new package of russian pbackup you repack it after language is changed. Also keep the configfile in /root/...(.pbackup/pbackuprc or .pfindrc). Please wait to translate Pburn until it reaches beta release. That will be Pburn 0.9.
BarryK
Great bugreport, but I can't recontruct a bleep of it. I guess I need to install dingo for futher testing. The detection of burning devices will have the same trouble in Pbackup.
-R for rockridge will be default in next release. Thank you.
This symlink-mirror is great for managing filesystem on CD/DVD. You can freely create new dirs on disc, rename links, reorganize linkstructure....And still all links points to the original file. I guess it would be absolutely possible to make graftpoints instead, but it would be a more complex task. And in the end, I don't see the huge drawback.One thing I don't understand. You have done it the same way that nathan did, creating a directory in /tmp with symlinks in the case of on-the-fly, but perhaps that isn't necessary. A list of directories and files can be supplied to be burnt, without needing to build a directory of symlinks -- it has been awhile, but I seem to remember that is possible.
Sigmund
Back after some dingo checking. I was not aware of that dingo has got wodim instead of cdrecord. Pburn uses cdrecord to check if disc is not closed for futher multisession, and to get the adress of previous session.
With cdrecord this returns either adress or nothing. In dingo, with wodim it returns adress or it never returns. - If disc is not a valid multisession disc, wodim asks to reload disc, and then nothing more... If there where another way to check if disc is a multisession disk, Pburn could run a test before using wodim to return adress of last session.
But right now, I don't know any other way to detect a multisession disc...HELP
Sigmund
Code: Select all
SECTIONS="`cdrecord dev=$BURNDEV -msinfo 2> /dev/null | grep -F ","`"
But right now, I don't know any other way to detect a multisession disc...HELP
Sigmund
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
I'm trying to recall the details when I was working on that stuff... yes, there was a problem with trying to determine a multisession disc.zigbert wrote:But right now, I don't know any other way to detect a multisession disc...HELP
But, do you want to detect if it is still open for further burning, or whether it has multiple tracks burnt on it?
'cddetect' returns some info about the tracks, I don't know if that is helpful.
I don't have to stay with cdrkit, I can move over to cdrtools if that is better. Note about the new program names in cdrkit, I kept the old names as symlinks, so no need to use the new names -- makes it easier for us to swap between the two packages.
[url]https://bkhome.org/news/[/url]
Ok, I start to get the grip of this.
I have to do some burning in dingo before 0.7.
Now you can choose cdrtools or cdrkit. I guess something must be better since someone forked the original project. I remember Nathan spoke positive about wodim when he made his GpRip.
Sigmund
Code: Select all
CDINFO="`cddetect -d$BURNDEV`"
DVDINFO="`dvd+rw-mediainfo $BURNDEV`"
...if CD...
if [ "`echo -n "$CDINFO" | grep "MODE21"`" ]; then #MODE21 is multisession
export SECTIONS="`cdrecord dev=$BURNDEV -msinfo 2> /dev/null | grep -F ","`" #get previous session
fi
...if DVD...
if [ "`echo -n "$DVDINFO" | grep "Disc status" | grep "appendable"`" ]; then
export SECTIONS="`cdrecord dev=$BURNDEV -msinfo 2> /dev/null | grep -F ","`" #get previous session
fi
Now you can choose cdrtools or cdrkit. I guess something must be better since someone forked the original project. I remember Nathan spoke positive about wodim when he made his GpRip.
Sigmund
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
I've gone back to cdrtools, see my latest blog post.
I'll try v0.7 now!
Note, with v0.6, I was able to burn an iso file to DVD, but when I wanted to burn a directory it got to the final "burn data" button then failed -- a error message popped up briefly in a window then immediately disappeared. That was using cdrtools.
I'll try v0.7 now!
Note, with v0.6, I was able to burn an iso file to DVD, but when I wanted to burn a directory it got to the final "burn data" button then failed -- a error message popped up briefly in a window then immediately disappeared. That was using cdrtools.
[url]https://bkhome.org/news/[/url]