Menu
▾
▴
cdrtools-support — Cdrtools user support
You can subscribe to this list here.
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
(3) |
Sep
|
Oct
|
Nov
(2) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2015 |
Jan
(3) |
Feb
|
Mar
(3) |
Apr
|
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(23) |
Nov
(5) |
Dec
(6) |
| 2016 |
Jan
(22) |
Feb
(20) |
Mar
|
Apr
|
May
(4) |
Jun
(4) |
Jul
|
Aug
(7) |
Sep
(1) |
Oct
|
Nov
(2) |
Dec
(1) |
| 2017 |
Jan
|
Feb
|
Mar
(8) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2018 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
| 2021 |
Jan
(6) |
Feb
(3) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|
From: Richardson, E. J <eri...@lm...> - 2015-05-12 19:20:29
|
> It seems that you are using the wrong devices..... > You started with dev=1,0,0, why did you try to use a different device later on? Whoops! Sorry, that was my bad. I typed this out from memory: > > cdrecord -v speed=2 dev=1,0,0 -multi /tmp/file.raw But the later ones I copied directly from the screen. I am not really switching devices; I just got the machines confused when I typed the first command. > Given the fact that you did not report about errors from the first write process, I assume that you used the right device. Yes, I use dev=2,0,0 for the initial cdrecord. I got this number from cdrecord -scanbus. Using this device does not generate any errors. > Given the fact that you could not mount the device, I assume that you used the wrong UNIX device name. I use /dev/sr0 to mount the device. I cannot mount the drive, using /dev/sr0 OR /dev/dvd, after the first write without manually reloading the tray. After I reload the tray, /dev/sr0 mounts just fine. I cannot perform the second write at all, as I said. From reading the man page, I think I am supposed to use the UNIX device name with the -M in mkisofs, but mkisofs does not like /dev/sr0. It did attempt to write when I used /dev/dvd, which is a link to /dev/sr1, but I don't know enough about Linux device names to know why. As I said in my first email, the attempt to write was unsuccessful. > If there is only on CD-ROM type device on your machine, cdrecord will use the right one without a need to specify dev= - read the man pages.... Yes, I read that in the man pages, but there is a second CD-ROM device that confuses things. The KVM that this machine is on attaches a "bonus" device via USB, which for some reason shows up as a CD drive at 0,0,0. This is why I specify the dev. -Eric J. Richardson -----Original Message----- From: Joerg Schilling [mailto:Joe...@fo...] Sent: Tuesday, May 12, 2015 3:50 AM To: Richardson, Eric J; cd...@ot...; cdr...@li... Subject: Re: EXTERNAL: Re: Problem with growisofs -- cannot write multisession DVDs without ejecting and reloading tray "Richardson, Eric J" <eri...@lm...> wrote: > Hello Jörg, > > Thank you for responding! I would be happy to use cdrtools for writing, if I could figure out how. I tried, Lord how I tried. Unfortunately, I am having less success using mkisofs and cdrecord to make a multisession DVD than I had with growisofs. > > I read your howto here: > http://cdrtools.sourceforge.net/private/man/README/README.multi > > Using this, I figured that I make the initial iso (raw) image with this command: > > mkisofs -R -o /tmp/file.raw file1file1file1_REDHAT.txt > file2file2file2_REDHAT.txt file3file3file3_REDHAT.txt > > So far, so good. I write the file with: > > cdrecord -v speed=2 dev=1,0,0 -multi /tmp/file.raw > > So far, so good. Let's try to mount that baby: > > mount /dev/sr0 /media/ > mount: you must specify the filesystem type > > Fine. Try it with the filesystem type: > > mount -o ro -t iso9660 /dev/sr0 /media/ > mount: no medium found on /dev/sr0 > > Okay, that's not the end of the world. I would like to be able to mount it, but what I REALLY want to do is write a second session. Let's try the msinfo to get the data for the second session: > > cdrecord -msinfo dev=2,0,0 > cdrecord: Warning: Cannot read drive buffer. > cdrecord: Warning: The DMA speed test has been skipped. > 0,93952 > > Great! Let's try a mkisofs now: > > mkisofs -R -C 0,93952 -M /dev/sr0 -o /tmp/file.raw > file4file4file4_REDHAT.txt file5file5file5_REDHAT.txt file6file6file6_REDHAT.txt Setting input-charset to 'UTF-8' from locale. > mkisofs: Input/output error. test unit ready: scsi sendcmd: no error > CDB: 00 00 00 00 00 00 > status: 0x2 (CHECK CONDITION) > Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00 Sense > Key: 0x2 Not Ready, Segment 0 Sense Code: 0x3A Qual 0x00 (medium not > present) Fru 0x0 It seems that you are using the wrong devices..... You started with dev=1,0,0, why did you try to use a different device later on? What if the correct UNIX device name for SCSI dev=1,0,0 on your machine? I recommend you to start with a cdrecord -scanbus If there is only on CD-ROM type device on your machine, cdrecord will use the right one without a need to specify dev= - read the man pages.... If you like to access the block device (e.g. four mounting), you need to know the UNIX device name, I hope that you know the right names for your machine. Given the fact that you did not report about errors from the first write process, I assume that you used the right device. Given the fact that you could not mount the device, I assume that you used the wrong UNIX device name. Jörg -- EMail:jo...@sc... (home) Jörg Schilling D-13353 Berlin joe...@fo... (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/' |
|
From: Joerg S. <Joe...@fo...> - 2015-05-12 09:50:07
|
"Richardson, Eric J" <eri...@lm...> wrote: > Hello Jörg, > > Thank you for responding! I would be happy to use cdrtools for writing, if I could figure out how. I tried, Lord how I tried. Unfortunately, I am having less success using mkisofs and cdrecord to make a multisession DVD than I had with growisofs. > > I read your howto here: > http://cdrtools.sourceforge.net/private/man/README/README.multi > > Using this, I figured that I make the initial iso (raw) image with this command: > > mkisofs -R -o /tmp/file.raw file1file1file1_REDHAT.txt file2file2file2_REDHAT.txt file3file3file3_REDHAT.txt > > So far, so good. I write the file with: > > cdrecord -v speed=2 dev=1,0,0 -multi /tmp/file.raw > > So far, so good. Let's try to mount that baby: > > mount /dev/sr0 /media/ > mount: you must specify the filesystem type > > Fine. Try it with the filesystem type: > > mount -o ro -t iso9660 /dev/sr0 /media/ > mount: no medium found on /dev/sr0 > > Okay, that's not the end of the world. I would like to be able to mount it, but what I REALLY want to do is write a second session. Let's try the msinfo to get the data for the second session: > > cdrecord -msinfo dev=2,0,0 > cdrecord: Warning: Cannot read drive buffer. > cdrecord: Warning: The DMA speed test has been skipped. > 0,93952 > > Great! Let's try a mkisofs now: > > mkisofs -R -C 0,93952 -M /dev/sr0 -o /tmp/file.raw file4file4file4_REDHAT.txt file5file5file5_REDHAT.txt file6file6file6_REDHAT.txt > Setting input-charset to 'UTF-8' from locale. > mkisofs: Input/output error. test unit ready: scsi sendcmd: no error > CDB: 00 00 00 00 00 00 > status: 0x2 (CHECK CONDITION) > Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00 > Sense Key: 0x2 Not Ready, Segment 0 > Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0 It seems that you are using the wrong devices..... You started with dev=1,0,0, why did you try to use a different device later on? What if the correct UNIX device name for SCSI dev=1,0,0 on your machine? I recommend you to start with a cdrecord -scanbus If there is only on CD-ROM type device on your machine, cdrecord will use the right one without a need to specify dev= - read the man pages.... If you like to access the block device (e.g. four mounting), you need to know the UNIX device name, I hope that you know the right names for your machine. Given the fact that you did not report about errors from the first write process, I assume that you used the right device. Given the fact that you could not mount the device, I assume that you used the wrong UNIX device name. Jörg -- EMail:jo...@sc... (home) Jörg Schilling D-13353 Berlin joe...@fo... (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/' |
|
From: Richardson, E. J <eri...@lm...> - 2015-05-11 23:19:58
|
Hello Jörg, Thank you for responding! I would be happy to use cdrtools for writing, if I could figure out how. I tried, Lord how I tried. Unfortunately, I am having less success using mkisofs and cdrecord to make a multisession DVD than I had with growisofs. I read your howto here: http://cdrtools.sourceforge.net/private/man/README/README.multi Using this, I figured that I make the initial iso (raw) image with this command: mkisofs -R -o /tmp/file.raw file1file1file1_REDHAT.txt file2file2file2_REDHAT.txt file3file3file3_REDHAT.txt So far, so good. I write the file with: cdrecord -v speed=2 dev=1,0,0 -multi /tmp/file.raw So far, so good. Let's try to mount that baby: mount /dev/sr0 /media/ mount: you must specify the filesystem type Fine. Try it with the filesystem type: mount -o ro -t iso9660 /dev/sr0 /media/ mount: no medium found on /dev/sr0 Okay, that's not the end of the world. I would like to be able to mount it, but what I REALLY want to do is write a second session. Let's try the msinfo to get the data for the second session: cdrecord -msinfo dev=2,0,0 cdrecord: Warning: Cannot read drive buffer. cdrecord: Warning: The DMA speed test has been skipped. 0,93952 Great! Let's try a mkisofs now: mkisofs -R -C 0,93952 -M /dev/sr0 -o /tmp/file.raw file4file4file4_REDHAT.txt file5file5file5_REDHAT.txt file6file6file6_REDHAT.txt Setting input-charset to 'UTF-8' from locale. mkisofs: Input/output error. test unit ready: scsi sendcmd: no error CDB: 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00 Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.002s timeout 20s mkisofs: Success. Unable to open previous session image '/dev/sr0'. There's no file.raw, so that's an odd definition of "success." Let's try it with /dev/dvd: mkisofs -R -C 0,93952 -M /dev/dvd -o /tmp/file.raw file4file4file4_REDHAT.txt file5file5file5_REDHAT.txt file6file6file6_REDHAT.txt Setting input-charset to 'UTF-8' from locale. mkisofs: Short read on old image Fine. Let's try it with dev=2,0,0: mkisofs -R -C 0,93952 -M dev=2,0,0 -o /tmp/file.raw file4file4file4_REDHAT.txt file5file5file5_REDHAT.txt file6file6file6_REDHAT.txt Setting input-charset to 'UTF-8' from locale. mkisofs: Invalid argument. Invalid bus or target specifier in 'dev=2,0,0'. Cannot open SCSI driver. mkisofs: Invalid argument. Unable to open previous session image 'dev=2,0,0'. Clearly that is not how I specify the device. I cannot write the second session, and am dead in the water. Just for the sake of completeness, I will reload the tray. After ejecting and re-inserting the media, I can now mount it, but only by specifying the filesystem type. After trying several variations on writing a new rawfile, I got this: mkisofs -R -C 0,93952 -M /dev/dvd -o /tmp/file.raw file4file4file4_REDHAT.txt file5file5file5_REDHAT.txt file6file6file6_REDHAT.txt Setting input-charset to 'UTF-8' from locale. ISO-9660 image includes checksum signature for correct inode numbers. SUSP signatures version 1 found Rock Ridge signatures version 1 found Rock Ridge id 'RRIP_1991A' Total translation table size: 0 Total rockridge attributes bytes: 821 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 178 extents written (0 MB) Super! Let's write the new rawfile to the disk: cdrecord -v speed=2 dev=2,0,0 -multi /tmp/file.raw cdrecord: No write mode specified. cdrecord: Assuming -tao mode. cdrecord: Future versions of cdrecord may have different drive dependent defaults. Cdrecord-ProDVD-ProBD-Clone 3.01a27 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2015 Joerg Schilling TOC Type: 3 = CD-ROM XA mode 2 scsidev: '2,0,0' scsibus: 2 target: 0 lun: 0 Linux sg driver version: 3.5.34 Using libscg version 'schily-0.9'. SCSI buffer size: 64512 atapi: 1 Device type : Removable CD-ROM Version : 5 Response Format: 2 Capabilities : Vendor_info : 'TSSTcorp' Identifikation : 'CDDVDW TS-H653B ' Revision : 'SI01' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Current: DVD-R sequential recording Profile: DVD-R/DL sequential recording Profile: DVD-R/DL layer jump recording Profile: DVD+R/DL Profile: DVD+R Profile: DVD+RW Profile: DVD-RW sequential recording Profile: DVD-RW restricted overwrite Profile: DVD-RAM Profile: DVD-R sequential recording (current) Profile: DVD-ROM Profile: CD-RW Profile: CD-R Profile: CD-ROM Profile: Removable Disk Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd). Driver flags : NO-CD DVD MMC-3 SWABAUDIO BURNFREE Supported modes: PACKET SAO LAYER_JUMP Drive buf size : 1376256 = 1344 KB cdrecord: Warning: Cannot read drive buffer. cdrecord: Warning: The DMA speed test has been skipped. FIFO size : 4194304 = 4096 KB Track 01: data 0 MB padsize: 244 KB Total size: 0 MB = 300 sectors Current Secsize: 2048 WARNING: Phys disk size 304 differs from rzone size 0! Prerecorded disk? WARNING: Phys start: 196608 Phys end 196911 WARNING: Drive returns zero media size. Using media size from ADIP. Blocks total: 304 Blocks current: -93648 Blocks remaining: -93948 cdrecord: Data does not fit on current disk. No dice. I believe cdrecord must work at least as well as growisofs -- i.e., I should be able to write a second session to the disk, if only after reloading the tray -- so I must be doing something wrong. But I can't for the life of me figure out what. Thanks again for your help! If I AM doing something wrong, I would love to know. If not, please enjoy Tigger, who needs a bath but does not want one: https://www.youtube.com/watch?v=PM5BCjNswd0 -Eric J. Richardson -----Original Message----- From: Joerg Schilling [mailto:Joe...@fo...] Sent: Friday, May 08, 2015 8:56 AM To: cdr...@li...; Richardson, Eric J; cd...@ot... Subject: EXTERNAL: Re: Problem with growisofs -- cannot write multisession DVDs without ejecting and reloading tray "Richardson, Eric J" <eri...@lm...> wrote: > I am hoping that someone can help me with my growisofs problem. It's not really a Debian problem, but the author: > http://fy.chalmers.se/~appro/linux/DVD+RW/ > suggests I start here anyway. > > I have a (relatively new) server that we used to run Solaris 10 update 7 on. On this system, we would perform backups of certain log files every day to DVD. For this, we used: Do you know that growisofs is unmaintained since 7 years? > Now we are in the process of moving to Red Hat 6.6. I don't think there's anything special about Red Hat, as I was able to duplicate the problem on Slackware 14.1, but that's the system we are trying to work with. Since I'd heard about troubles with the 'genisoimage' program that ships with Red Hat (and Debian, and Ubuntu), I went ahead and downloaded a cdrtools RPM from this helpful fellow: > http://negativo17.org/cdrtools/ > and I also removed the 'fake' cdrtools that comes with Red Hat, just to be safe. So, now we are using Red Hat with a kernel of: > Linux 2.6.32-504.8.1.el6.x86_64 > > Mkisofs is: > mkisofs 3.01a27 (x86_64-unknown-linux-gnu) Copyright (C) 1993-1997 > Eric Youngdale (C) 1997-2015 Joerg Schilling > > Growisofs is: > * growisofs by <ap...@fy...>, version 7.1, > front-ending to mkisofs: mkisofs 3.01a27 (x86_64-unknown-linux-gnu) > Copyright (C) 1993-1997 Eric Youngdale (C) 1997-2015 Joerg Schilling > > And, in case you were curious, cdrecord is: > Cdrecord-ProDVD-ProBD-Clone 3.01a27 (x86_64-unknown-linux-gnu) > Copyright (C) 1995-2015 Joerg Schilling If you have a recent cdrtools installed, why don't you use it for writing? Unlike growisofs, cdrtools is actively maintained. If you have problems with cdrtools, this can be fixed.... You would need to send a bug report - I am not aware of problems in the recent version. Jörg -- EMail:jo...@sc... (home) Jörg Schilling D-13353 Berlin joe...@fo... (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/' |
|
From: Joerg S. <Joe...@fo...> - 2015-05-08 15:09:07
|
"Richardson, Eric J" <eri...@lm...> wrote: > I am hoping that someone can help me with my growisofs problem. It's not really a Debian problem, but the author: > http://fy.chalmers.se/~appro/linux/DVD+RW/ > suggests I start here anyway. > > I have a (relatively new) server that we used to run Solaris 10 update 7 on. On this system, we would perform backups of certain log files every day to DVD. For this, we used: Do you know that growisofs is unmaintained since 7 years? > Now we are in the process of moving to Red Hat 6.6. I don't think there's anything special about Red Hat, as I was able to duplicate the problem on Slackware 14.1, but that's the system we are trying to work with. Since I'd heard about troubles with the 'genisoimage' program that ships with Red Hat (and Debian, and Ubuntu), I went ahead and downloaded a cdrtools RPM from this helpful fellow: > http://negativo17.org/cdrtools/ > and I also removed the 'fake' cdrtools that comes with Red Hat, just to be safe. So, now we are using Red Hat with a kernel of: > Linux 2.6.32-504.8.1.el6.x86_64 > > Mkisofs is: > mkisofs 3.01a27 (x86_64-unknown-linux-gnu) Copyright (C) 1993-1997 Eric Youngdale (C) 1997-2015 Joerg Schilling > > Growisofs is: > * growisofs by <ap...@fy...>, version 7.1, > front-ending to mkisofs: mkisofs 3.01a27 (x86_64-unknown-linux-gnu) Copyright (C) 1993-1997 Eric Youngdale (C) 1997-2015 Joerg Schilling > > And, in case you were curious, cdrecord is: > Cdrecord-ProDVD-ProBD-Clone 3.01a27 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2015 Joerg Schilling If you have a recent cdrtools installed, why don't you use it for writing? Unlike growisofs, cdrtools is actively maintained. If you have problems with cdrtools, this can be fixed.... You would need to send a bug report - I am not aware of problems in the recent version. Jörg -- EMail:jo...@sc... (home) Jörg Schilling D-13353 Berlin joe...@fo... (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/' |
|
From: Marcus M. <ma...@op...> - 2015-03-02 12:14:32
|
> The problem seems to be that k3b is unmaintained since a long time. > > Cdrecord has no problem to write any filesystem image you feed it. It > doesn't > matter what's inside. > > The problem with k3b may be that it does not help you with writing > existing > filesystem images. > > Is this what you want to do? > > Jörg > Yes, I was trying to (re)create BD DL (~46 GiB) from an ISO image backup. It seems that K3b's "Burn Image" module somehow checks the image before calling the external program with appropriate arguments and it obviously doesn't like what it sees. I don't know what bothers K3b about large (BD50) ISO images but it considers them "unusable". :/ I'm confident now that this is a bug and that K3b developers should look into it. Thanks for your help. Regards. Marcus -- http://www.fastmail.com - Or how I learned to stop worrying and love email again |
|
From: Joerg S. <Joe...@fo...> - 2015-03-01 22:11:26
|
Marcus Magick <ma...@op...> wrote: > I have some BD50 ISO images, which I made some time ago on a Windows PC, > and I would like to burn them now on a BD-R DL media so that I could > cleanup some space on a HDD. > > K3b can't seem to burn BD50 ISO images containing UDF 2.5. I described > the issue in openSUSE forum > > https://forums.opensuse.org/showthread.php/505451-K3b-can-t-seem-to-burn-BD50-ISO-images > > and in KDE forum > > https://forum.kde.org/viewtopic.php?f=153&t=125016 > > As those communities were not of much help I lay my hopes in you. :) I'm > trying to understand where is the problem and should this be submitted > as a bug report or a feature request and to whom. > > I realize that Linux doesn't support writing UDF 2.5 (only reading) but > it seems to me that it shouldn't matter if you are just trying to burn > an ISO image containing UDF 2.5. The problem seems to be that k3b is unmaintained since a long time. Cdrecord has no problem to write any filesystem image you feed it. It doesn't matter what's inside. The problem with k3b may be that it does not help you with writing existing filesystem images. Is this what you want to do? Jörg -- EMail:jo...@sc... (home) Jörg Schilling D-13353 Berlin joe...@fo... (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/' |
|
From: Marcus M. <ma...@op...> - 2015-03-01 12:56:50
|
I have some BD50 ISO images, which I made some time ago on a Windows PC, and I would like to burn them now on a BD-R DL media so that I could cleanup some space on a HDD. K3b can't seem to burn BD50 ISO images containing UDF 2.5. I described the issue in openSUSE forum https://forums.opensuse.org/showthread.php/505451-K3b-can-t-seem-to-burn-BD50-ISO-images and in KDE forum https://forum.kde.org/viewtopic.php?f=153&t=125016 As those communities were not of much help I lay my hopes in you. :) I'm trying to understand where is the problem and should this be submitted as a bug report or a feature request and to whom. I realize that Linux doesn't support writing UDF 2.5 (only reading) but it seems to me that it shouldn't matter if you are just trying to burn an ISO image containing UDF 2.5. Couldn't some program simply read raw data in the ISO image and then burn it to a media bit by bit, or things just don't work that way? I see that growisofs (part of dvd+rw-tools) has a function called 'builtin_dd' which burns an image to a disk, if I understand correctly. It is also stated on dvd+rw-tools' web page that growisofs depends on cdrtools, namely mkisofs, but I speculate that in this case I don't need mkisofs because I already have (UDF 2.5) file system in the image and I'm "merely" trying to burn it on a BD-R DL disk. Right? K3b claims that it supports Blu-ray and in doing so it relies on cdrtools (cdrecord) and dvd+rw-tools (growisofs). Further, growisofs supports BD while cdrtools (cdrecord) also claims "support for Blu-ray", so it's rather confusing even for an advanced user like me - who gets the job done and how? :S Can somebody explain to me, what program operates an optical drive and performs actual burning on a blank media? Can cdrecord recreate a double layer BD (50GB) from it's (previously acquired under Win) ISO image that contains UDF 2.5? How about growisofs? If it turns out that any of those command line programs can burn ISO image containing UDF 2.5 to a blank BD-R DL media then this definitely becomes a bug report to K3b developers. Despite widely popular claims for "Blu-ray support" I see that most of Linux users with BD burners use proprietary Nero for Linux 4.0 for burning their BD-R DL (UTF 2.5) media because there was numerous coaster incidents when using OSS tools. :( Any help would be greatly appreciated. Regards, Marcus -- http://www.fastmail.com - Faster than the air-speed velocity of an unladen european swallow |
|
From: Joerg S. <Joe...@fo...> - 2015-01-30 13:33:46
|
Erik Koennecke <eri...@gm...> wrote: > With -paraopts=proof, I get into an endless reading loop with I/O errors, > if I skip them and just use -paranoia, the disks get read, but always with > an output like this: > > [CODE]recording 216.6133 seconds stereo with 16 bits @ 44100.0 Hz > ->'/media/persistent/Hitachi300G/Temp/abcde.2b12e416/track03'... > using lib paranoia for reading. > percent_done: > 27%Tagging track 02 of 22: Moves Like Jagger... > 100% track 3 'We Found Love' recorded with audible hard errors > 100% 0 rderr, 0 skip, 0 atom, 0 edge, 0 drop, 0 dup, 0 drift > 100% 690 reads(211,7%) 77 overlap(0,5 .. 0,5)[/CODE] > > Seems like the whole rip doesn't even try to do some corrections, all > statistics are 0. Always reported with audible hard errors. It makes no > difference if I use another drive. One is a BD drive via USB, the other a > DVD-rewriter via SATA, so it shouldn't be hardware-related. > > If I replace the -paraopts=proof option with > -paraopts=minoverlap=20,retries=200,readahead=600, which is the same except > for the omitted c2check, the I/O errors are gone, and I get basically the > same result, maybe slower. What gives? > > I asked already elsewhere, and got feedback here > http://ubuntuforums.org/showthread.php?t=2257705&p=13217103#post13217103 > that this behaviour was not in 3.00, but in subsequent versions. I use > 3a22, but 3a26 doesn't make a difference according to my last link. The behavior you describe is a result of firmware with deficits: - Does not support c2 errors. Which is unfortunately true for some drives. For this reason, -paraopts=proof was changed with 3.01a23 to no longer include "c2check" by default. So 3.01a26 or 3.01a27 of course would make a difference. Jörg -- EMail:jo...@sc... (home) Jörg Schilling D-13353 Berlin joe...@fo... (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/' |
|
From: Erik K. <eri...@gm...> - 2015-01-30 12:36:08
|
With -paraopts=proof, I get into an endless reading loop with I/O errors, if I skip them and just use -paranoia, the disks get read, but always with an output like this: [CODE]recording 216.6133 seconds stereo with 16 bits @ 44100.0 Hz ->'/media/persistent/Hitachi300G/Temp/abcde.2b12e416/track03'... using lib paranoia for reading. percent_done: 27%Tagging track 02 of 22: Moves Like Jagger... 100% track 3 'We Found Love' recorded with audible hard errors 100% 0 rderr, 0 skip, 0 atom, 0 edge, 0 drop, 0 dup, 0 drift 100% 690 reads(211,7%) 77 overlap(0,5 .. 0,5)[/CODE] Seems like the whole rip doesn't even try to do some corrections, all statistics are 0. Always reported with audible hard errors. It makes no difference if I use another drive. One is a BD drive via USB, the other a DVD-rewriter via SATA, so it shouldn't be hardware-related. If I replace the -paraopts=proof option with -paraopts=minoverlap=20,retries=200,readahead=600, which is the same except for the omitted c2check, the I/O errors are gone, and I get basically the same result, maybe slower. What gives? I asked already elsewhere, and got feedback here http://ubuntuforums.org/showthread.php?t=2257705&p=13217103#post13217103 that this behaviour was not in 3.00, but in subsequent versions. I use 3a22, but 3a26 doesn't make a difference according to my last link. |
|
From: Jim M. <jmi...@ya...> - 2015-01-20 03:06:21
|
Both -udf and -UDF produce the same bug: Actual: When appending a second session, the files from the first session become inaccessible. with -UDF at least, the filenames are visible, but the file content is not there or not accessible. this of course affects the ability to make better use of expensive blu-ray discs. Expected:Previous sessions should be imported properly and be visible as with non-UDF. $ mkisofs -udf -rational-rock -volid Testdisk -output session-1.iso testfile01.txt $ cdrecord gracetime=5 dev=0,0,0 -v -tao -multi session-1.iso $ cdrecord dev=0,0,0 -msinfo $ mkisofs -udf -rational-rock -volid Testdisk -cdrecord-params 0,12077 -prev-session 0,0,0 -output session-2.iso testfile02.txt $ cdrecord gracetime=5 dev=0,0,0 -v -tao -multi session-2.iso ------------- Jim Michaels Jmi...@ya... Ji...@Re... http://RenewalComputerServices.com http://JesusnJim.com (computer repair info, programming) |
|
From: Jim M. <jmi...@ya...> - 2014-12-07 07:59:38
|
it's nearing Christmas. wondering if you would be interested in a drive. if so provide me your mailing address (not sure if the one on cdrtools.org is still accurate?) or email me directly so we can make arrangements. is this going to Germany or USA? curious what the shipping costs would be, I would assume it would need to go DHL... ------------- Jim Michaels Jmi...@ya... Ji...@Re... http://RenewalComputerServices.com http://JesusnJim.com (computer repair info, programming) |
|
From: Joerg S. <Joe...@fo...> - 2014-11-10 12:01:35
|
Deweloper <dew...@wp...> wrote:
> Hello,
>
> I am unable to burn a multisession DVD-RW due to an error during closing the session - writing the first session almost succeds, but it isn't properly closed. The DVD-RW can then be mounted and data can be read from it, but I cannot append another session. In order to be able to write to the DVD-RW again, I have to do cdrecord blank=all (blank=fast is not enough).
>
> I'm using Fedora 20 (kernel 3.16.7-200.fc20.i686) with self-built vanilla cdrecord.
>
> # cat /etc/default/cdrecord
> default= 4,0,0 24 8m burnfree
I would guess that there is a problem with madia/drive compiatibility.
Is the drive halfway new?
Did you try a Verbatim media?
Note that "Optodisc" is not known to be a high quality manufacturer.
Did you try to erase the medium before writing?
Jörg
--
EMail:jo...@sc... (home) Jörg Schilling D-13353 Berlin
joe...@fo... (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'
|
|
From: Deweloper <dew...@wp...> - 2014-11-10 11:04:51
|
Hello,
I am unable to burn a multisession DVD-RW due to an error during closing the session - writing the first session almost succeds, but it isn't properly closed. The DVD-RW can then be mounted and data can be read from it, but I cannot append another session. In order to be able to write to the DVD-RW again, I have to do cdrecord blank=all (blank=fast is not enough).
I'm using Fedora 20 (kernel 3.16.7-200.fc20.i686) with self-built vanilla cdrecord.
# cat /etc/default/cdrecord
default= 4,0,0 24 8m burnfree
Here comes the log of burning the first session (as root):
# mkisofs -r -J -f burn | cdrecord dev=default -timeout=900 -sao -multi -tsize=361356s -v -data -
Setting input-charset to 'UTF-8' from locale.
Cdrecord-ProDVD-ProBD-Clone 3.01a24 (i686-pc-linux-gnu) Copyright (C) 1995-2014 Joerg Schilling
TOC Type: 1 = CD-ROM
scsidev: '4,0,0'
scsibus: 4 target: 0 lun: 0
Linux sg driver version: 3.5.34
Using libscg version 'schily-0.9'.
Driveropts: 'burnfree'
SCSI buffer size: 64512
atapi: 1
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'MATSHITA'
Identifikation : 'DVD-RAM UJ-840S '
Revision : '1.11'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Current: DVD-RW sequential recording
Profile: DVD-RAM
Profile: DVD+R/DL
Profile: DVD+R
Profile: DVD+RW
Profile: DVD-RW restricted overwrite (current)
Profile: DVD-RW sequential recording (current)
Profile: DVD-R sequential recording
Profile: DVD-ROM
Profile: CD-RW
Profile: CD-R
Profile: CD-ROM
Profile: Removable Disk
Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd).
Driver flags : NO-CD DVD MMC-3 SWABAUDIO BURNFREE
Supported modes: PACKET SAO
Drive buf size : 1605632 = 1568 KB
cdrecord: Warning: Cannot read drive buffer.
cdrecord: Warning: The DMA speed test has been skipped.
FIFO size : 8388608 = 8192 KB
Track 01: data 705 MB
Total size: 705 MB = 361356 sectors
Current Secsize: 2048
WARNING: Phys disk size 1 differs from rzone size 716800! Prerecorded disk?
WARNING: Phys start: 196608 Phys end 196608
Blocks total: 716800 Blocks current: 716800 Blocks remaining: 355444
Reducing transfer size from 64512 to 32768 bytes.
Starting to write CD/DVD/BD at speed 2 in real SAO mode for multi session.
Last chance to quit, starting real write 0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
BURN-Free is ON.
Starting new track at sector: 0
Track 01: 1 of 705 MB written (fifo 99%) 0,8x. 1,39% done, estimate finish Mon Nov 10 11:15:35 2014
Track 01: 11 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 2,77% done, estimate finish Mon Nov 10 11:09:02 2014
Track 01: 21 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 4,15% done, estimate finish Mon Nov 10 11:07:14 2014
Track 01: 31 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 5,54% done, estimate finish Mon Nov 10 11:06:20 2014
Track 01: 40 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 6,93% done, estimate finish Mon Nov 10 11:05:33 2014
Track 01: 50 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 8,31% done, estimate finish Mon Nov 10 11:05:14 2014
Track 01: 60 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 9,69% done, estimate finish Mon Nov 10 11:05:00 2014
Track 01: 70 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 11,07% done, estimate finish Mon Nov 10 11:04:41 2014
Track 01: 79 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 12,46% done, estimate finish Mon Nov 10 11:04:34 2014
Track 01: 89 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 13,84% done, estimate finish Mon Nov 10 11:04:28 2014
Track 01: 99 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 15,23% done, estimate finish Mon Nov 10 11:04:23 2014
Track 01: 109 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 16,61% done, estimate finish Mon Nov 10 11:04:14 2014
Track 01: 118 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 17,99% done, estimate finish Mon Nov 10 11:04:11 2014
Track 01: 128 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 19,37% done, estimate finish Mon Nov 10 11:04:09 2014
Track 01: 138 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 20,76% done, estimate finish Mon Nov 10 11:04:02 2014
Track 01: 148 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 22,14% done, estimate finish Mon Nov 10 11:04:00 2014
Track 01: 158 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 23,53% done, estimate finish Mon Nov 10 11:03:59 2014
Track 01: 167 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 24,91% done, estimate finish Mon Nov 10 11:03:54 2014
Track 01: 177 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 26,30% done, estimate finish Mon Nov 10 11:03:53 2014
Track 01: 187 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 27,68% done, estimate finish Mon Nov 10 11:03:52 2014
Track 01: 197 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 29,06% done, estimate finish Mon Nov 10 11:03:51 2014
Track 01: 206 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 30,45% done, estimate finish Mon Nov 10 11:03:47 2014
Track 01: 216 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 31,83% done, estimate finish Mon Nov 10 11:03:47 2014
Track 01: 226 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 33,21% done, estimate finish Mon Nov 10 11:03:47 2014
Track 01: 236 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 34,59% done, estimate finish Mon Nov 10 11:03:43 2014
Track 01: 245 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 35,98% done, estimate finish Mon Nov 10 11:03:43 2014
Track 01: 255 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 37,36% done, estimate finish Mon Nov 10 11:03:43 2014
Track 01: 265 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 38,75% done, estimate finish Mon Nov 10 11:03:40 2014
Track 01: 275 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 40,13% done, estimate finish Mon Nov 10 11:03:40 2014
Track 01: 285 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 41,52% done, estimate finish Mon Nov 10 11:03:40 2014
Track 01: 294 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 42,90% done, estimate finish Mon Nov 10 11:03:38 2014
Track 01: 304 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 44,28% done, estimate finish Mon Nov 10 11:03:38 2014
Track 01: 314 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 45,66% done, estimate finish Mon Nov 10 11:03:38 2014
Track 01: 324 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 47,05% done, estimate finish Mon Nov 10 11:03:38 2014
Track 01: 333 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 48,43% done, estimate finish Mon Nov 10 11:03:35 2014
Track 01: 343 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 49,82% done, estimate finish Mon Nov 10 11:03:36 2014
Track 01: 353 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 51,20% done, estimate finish Mon Nov 10 11:03:36 2014
Track 01: 363 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 52,59% done, estimate finish Mon Nov 10 11:03:34 2014
Track 01: 372 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 53,97% done, estimate finish Mon Nov 10 11:03:34 2014
Track 01: 382 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 55,35% done, estimate finish Mon Nov 10 11:03:34 2014
Track 01: 392 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 56,73% done, estimate finish Mon Nov 10 11:03:32 2014
Track 01: 402 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 58,12% done, estimate finish Mon Nov 10 11:03:32 2014
Track 01: 411 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 59,50% done, estimate finish Mon Nov 10 11:03:33 2014
Track 01: 421 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 60,89% done, estimate finish Mon Nov 10 11:03:31 2014
Track 01: 431 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 62,27% done, estimate finish Mon Nov 10 11:03:31 2014
Track 01: 441 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 63,66% done, estimate finish Mon Nov 10 11:03:31 2014
Track 01: 451 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 65,04% done, estimate finish Mon Nov 10 11:03:31 2014
Track 01: 460 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 66,42% done, estimate finish Mon Nov 10 11:03:30 2014
Track 01: 470 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 67,80% done, estimate finish Mon Nov 10 11:03:30 2014
Track 01: 480 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 69,19% done, estimate finish Mon Nov 10 11:03:30 2014
Track 01: 490 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 70,57% done, estimate finish Mon Nov 10 11:03:29 2014
Track 01: 499 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 71,95% done, estimate finish Mon Nov 10 11:03:29 2014
Track 01: 509 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 73,34% done, estimate finish Mon Nov 10 11:03:29 2014
Track 01: 519 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 74,73% done, estimate finish Mon Nov 10 11:03:28 2014
Track 01: 529 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 76,11% done, estimate finish Mon Nov 10 11:03:28 2014
Track 01: 538 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 77,49% done, estimate finish Mon Nov 10 11:03:29 2014
Track 01: 548 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 78,87% done, estimate finish Mon Nov 10 11:03:27 2014
Track 01: 558 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 80,25% done, estimate finish Mon Nov 10 11:03:28 2014
Track 01: 568 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 81,64% done, estimate finish Mon Nov 10 11:03:28 2014
Track 01: 577 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 83,02% done, estimate finish Mon Nov 10 11:03:28 2014
Track 01: 587 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 84,41% done, estimate finish Mon Nov 10 11:03:27 2014
Track 01: 597 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 85,79% done, estimate finish Mon Nov 10 11:03:27 2014
Track 01: 607 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 87,17% done, estimate finish Mon Nov 10 11:03:27 2014
Track 01: 617 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 88,56% done, estimate finish Mon Nov 10 11:03:26 2014
Track 01: 626 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 89,94% done, estimate finish Mon Nov 10 11:03:26 2014
Track 01: 636 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 91,32% done, estimate finish Mon Nov 10 11:03:27 2014
Track 01: 646 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 92,71% done, estimate finish Mon Nov 10 11:03:26 2014
Track 01: 656 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 94,10% done, estimate finish Mon Nov 10 11:03:26 2014
Track 01: 665 of 705 MB written (fifo 100%) [buf 100%] 2,0x. 95,48% done, estimate finish Mon Nov 10 11:03:26 2014
Track 01: 675 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 96,86% done, estimate finish Mon Nov 10 11:03:25 2014
Track 01: 685 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 98,24% done, estimate finish Mon Nov 10 11:03:25 2014
Track 01: 695 of 705 MB written (fifo 99%) [buf 100%] 2,0x. 99,63% done, estimate finish Mon Nov 10 11:03:26 2014
Track 01: 697 of 705 MB written (fifo 100%) [buf 100%] 2,0x.Total translation table size: 0
Total rockridge attributes bytes: 4689
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 0
361356 extents written (705 MB)
Track 01: 705 of 705 MB written (fifo 100%) [buf 100%] 2,0x.
Track 01: Total bytes read/written: 740057088/740057088 (361356 sectors).
Writing time: 267.667s (00:04:27.667)
Average write speed 2,0x.
Min drive buffer fill was 97%
Fixating...
cdrecord: Błąd wejścia/wyjścia. close track/session: scsi sendcmd: no error
CDB: 5B 01 02 00 00 01 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 72 04 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x72 Qual 0x04 (empty or partially written reserved track) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.010s timeout 900s
Fixating time: 1.115s (00:00:01.115)
BURN-Free was not used.
cdrecord: fifo had 22585 puts and 22585 gets.
cdrecord: fifo was 0 times empty and 13043 times full, min fill was 92%.
----------
And below comes the output of cdrecord -atip:
book type: DVD-RW, Version 1.1x (3.2)
disc size: 80mm (1)
maximum rate: Not specified (15)
number of layers:1
track path: Parallel Track Path (0)
layer type: Rewritable Area (2)
linear density: 0.267 �m/bit (0)
track density: 0.74 �m/track (0)
phys start: 196608 (0x30000)
phys end: 196608
end layer 0: 0
bca: 0
phys size:... 1
copyr prot type: 0
region mgt info: 0
cpm: 0
cgms: 0
application code:64
physical code: 246
last rec address:16720128
part v./ext code:2/1
ind wr. power: 15
wavelength code: 7
write str. code: 07 88 75 0E
Manufacturer: 'OPTODISCW002'
rzone size: 36
rzone number: 1
border number: 1
ljrs: 0
track mode: 4 copy: 0
damage: 0
reserved track: 1 blank: 0 incremental: 1 fp: 0
data mode: 1
lra valid: 1
nwa valid: 0
rzone start: 0
next wr addr: 0
free blocks: 0
blocking factor: 16
rzone size: 361360
last recorded addr: 361355
Capacity Blklen/Sparesz. Format-type Type
716192 2048 0x00 Unformated or Blank Media
716192 2048 0x00 Reserved (0)
716192 16 0x10 Reserved (0)
716192 16 0x15 Reserved (0)
WARNING: Phys disk size 1 differs from rzone size 0! Prerecorded disk?
WARNING: Phys start: 196608 Phys end 196608
WARNING: Drive returns zero media size. Using media size from ADIP.
-------
The above is from Esperanza DVD-RW 1,4GB 2x, but same problem occurs when I try "extreme DVD-RW 1,4GB x2SPEED".
|
|
From: Noel B. <noe...@au...> - 2014-08-30 07:55:22
|
On 30/08/2014 00:35, Joerg Schilling wrote: > Noel Butler <noe...@au...> wrote: > >> Something happen to the download site? sourceforge doesnt have any of the 3.x and mos the files in alpha are gone... > > Which files are you missing? > > For me it seems to be OK. > > Jörg It seems some mirrors are dead or its cache is dead, Uni of Kent on UK alpha dir contains SFA, yet it used to! an Australian sf.net cache also shows nothing ____________________________________________________________________________________________________________________ [PARENTDIR] Parent Directory - [DIR] develop/ 2005-03-08 23:39 - [DIR] macos-x/ 2014-06-16 23:31 - [DIR] OLD/ 2010-11-21 09:38 - [DIR] win32/ 2005-03-08 23:39 - [ ] !MD5_SUMS 2002-08-02 20:11 3.4K [ ] btcflash-1.6-sspm.tar.bz2 2004-05-09 22:57 6.8K [ ] cdrtools-bin-powerpc-apple-rhapsody5.6.tar.gz 2000-05-04 08:00 426K [ ] Changelog 2010-05-29 23:24 414K [TXT] COPYING 2012-02-27 07:25 4.4K [TXT] Linux-USB-DMA-Size.patch 2006-12-11 00:19 2.0K [ ] mkhybrid.sed 2000-04-09 02:52 295 [ ] mkisofs.sed 2000-04-09 02:48 228 [ ] ms-i586-pc-linux-gnu 2002-12-01 06:56 127K [ ] multi-extent.iso.bz2 2007-07-19 23:14 39K [ ] skel-1.0-sspm.tar.bz2 2004-04-29 22:09 4.3K [TXT] SUPPORT 2005-03-08 23:09 1.0K [IMG] tatoodata-flipped.pgm 2002-09-03 09:10 1.1M [SND] tatoodata-flipped.raw 2002-09-03 09:19 1.1M [IMG] tatoodata.pgm 2002-09-03 08:48 1.1M [SND] tatoodata.raw 2002-09-03 08:54 1.1M ____________________________________________________________________________________________________________________ Will wait and try again in a day or so, using a VPN I do get a response..well if 3.01a24 is the latest? Thanks |
|
From: Joerg S. <Joe...@fo...> - 2014-08-29 14:35:15
|
Noel Butler <noe...@au...> wrote:
>
>
> Something happen to the download site? sourceforge doesnt have any of
> the 3.x and mos the files in alpha are gone...
Which files are you missing?
For me it seems to be OK.
Jörg
--
EMail:jo...@sc... (home) Jörg Schilling D-13353 Berlin
joe...@fo... (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'
|
|
From: Noel B. <noe...@au...> - 2014-08-29 04:25:06
|
Something happen to the download site? sourceforge doesnt have any of the 3.x and mos the files in alpha are gone... |
|
From: Joerg S. <Joe...@fo...> - 2014-07-30 17:11:50
|
Ady <ad...@ho...> wrote:
> Hello,
>
> In mkisofs, looking at the "-eltorito-platform id" option, from the
> 3.01a manual:
>
> [quote]
> x86 This is the default platform id value and speci-
> fies entries for the PC platform. If no
> -eltorito-platform option appears before the first
> -eltorito-boot option, the default boot entry
> becomes an entry for the x86 PC platform.
>
> PPC Boot entries for the Power PC platform.
>
> Mac Boot entries for the Apple Mac platform.
>
> efi Boot entries for EFI based PCs.
>
> # A numeric value specifying any platform id.
> [/quote]
>
> From the El Torito specification, my understanding is that the above
> "Mac" is equivalent to "0x02".
>
> After using "-eltorito-platform Mac", the result seems to be (by
> means of hex viewer) not 0x02, but 0x01.
You are right, thank you!
This is a cut/paste error.
Jörg
--
EMail:jo...@sc... (home) Jörg Schilling D-13353 Berlin
joe...@fo... (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'
|
|
From: Ady <ad...@ho...> - 2014-07-30 15:41:08
|
Hello,
In mkisofs, looking at the "-eltorito-platform id" option, from the
3.01a manual:
[quote]
x86 This is the default platform id value and speci-
fies entries for the PC platform. If no
-eltorito-platform option appears before the first
-eltorito-boot option, the default boot entry
becomes an entry for the x86 PC platform.
PPC Boot entries for the Power PC platform.
Mac Boot entries for the Apple Mac platform.
efi Boot entries for EFI based PCs.
# A numeric value specifying any platform id.
[/quote]
>From the El Torito specification, my understanding is that the above
"Mac" is equivalent to "0x02".
After using "-eltorito-platform Mac", the result seems to be (by
means of hex viewer) not 0x02, but 0x01.
I don't have a %100 valid ISO image as example. I only used this
"Mac" option with dummy files. My purpose was to check whether the
hex value was the one I was expecting (0x02).
I don't know if the inconsistency (0x01 instead of the expected 0x02)
is generated by using "dummy" (or incompatible, or unexpected) files
as boot image for this platform, or if indeed the problem is in
mkisofs itself.
I also don't know whether the problem is related to the "Mac"
platform ID only, or if instead there is some more-generic problem
with the "-eltorito-platform" option(s) (for instance, when combining
it with "-eltorito-alt-boot").
I don't discard the possibility that I might be misunderstanding or
misusing the options / arguments for the mkisofs command.
This is relevant for mkisofs version 3.01a24, and probably some
others before it too.
Hopefully someone can replicate the behavior and find the solution.
TIA,
Ady.
|
|
From: Joerg S. <Joe...@fo...> - 2014-07-23 09:24:44
|
Lucas Levrel <ll...@ya...> wrote: > Le 22 juillet 2014, Guri Grewal a écrit : > > > I may be using incorrect email address; therefore, I am resending > > my email. Here is the clarification to my question, it is my understanding > > cdrecord command can also be used to burn(record) iso file, clone CD. I wanted > > to know if the cdrecord command can also be used to burn or record the actual CD TOC (ex 150 0001 0002 > > 0003 0004 0005 0006) to a blankCD? > > I'm not an expert but in case no one else answers: I think cdrecord > generates automatically the TOC according to the tracks you give it to > burn. > > What's not clear in your question is: do you want to burn the TOC only? > (i.e. without burning any data?) Let me first mention again the current location of the mailing lists (the debian list usually only distributes spam): http://sourceforge.net/p/cdrtools/mailman/ Cdrecord allows to clone a CD using readcd -clone and later cdrecord -clone on the result (see man page). Cdrecord also allows to use CUE files from cdrwin and similar programs (at long as the content of the files is compliant to the definition). Both methods allows to have a close connection to the way the TOC is created. A TOC without data on the CD does not make sense. "~A |
2 messages has been excluded from this view by a project administrator.
