Branches
Releases
|
Version
|
Focus
|
Date
|
|
2.01.01a43
|
Minor bugfixes |
10-Jul-2008 15:08 |
|
2.01.01a42
|
Minor feature enhancements |
25-Jun-2008 12:01 |
|
2.01.01a41
|
Minor bugfixes |
16-Jun-2008 14:37 |
|
2.01.01a40
|
Minor feature enhancements |
26-May-2008 13:30 |
|
2.01.01a39
|
Minor bugfixes |
28-Apr-2008 17:32 |
|
2.01.01a38
|
Minor feature enhancements |
05-Mar-2008 21:57 |
|
2.01.01a37
|
Minor feature enhancements |
03-Jan-2008 10:32 |
|
2.01.01a36
|
Minor bugfixes |
23-Oct-2007 15:16 |
|
2.01.01a35
|
Minor feature enhancements |
03-Sep-2007 11:41 |
|
2.01.01a34
|
Minor bugfixes |
21-Aug-2007 09:12 |
Articles referencing this project
Comments
[»]
CDRTools under windows - enumerate system DVD drives
by Bob Wya - May 17th 2007 16:22:39
Hi
I am trying to use the CDRTools scanbus facility in an Windows AutoIt
Script. It handly lists all the CD/DVD drives in my system. Allows me to
get the manufacturer of the drives and to identify emulated drives...
However is there anyway to get the stupid Windows drive letter for the
optical drives (D:. E:, etc.)? Maybe from the SCSI bus address?
Cheers
Bob
[reply]
[top]
[»]
Re: CDRTools under windows - enumerate system DVD drives
by ExGirl - Jul 12th 2007 09:50:25
> However is
> there anyway to get the stupid Windows
> drive letter for the optical drives (D:.
> E:, etc.)? Maybe from the SCSI bus
> address?
What about Administrative Tools->Computer Management->Disk Management?
There you can change drive letter.
[reply]
[top]
[»]
[wish] support for large files
by macias - Mar 19th 2007 14:03:09
So far I can burn exactly 4GB file (one file = 4GB) on
DVD (using k3b as GUI frontend), however it would be
good to see support for larger files so I could fit one
file which would occupy the whole disc.
Any plans in supporting really :-) large files?
thank you for great tool!
[reply]
[top]
[»]
Re: [wish] support for large files
by E. Bloch - Apr 3rd 2007 07:22:46
You may have luck with genisoimage, see cdrkit package. The isofs
representation remains broken (file size displayed is the modulo 4GB
residual) but the UDF part should work well with large files.
[reply]
[top]
[»]
Re: [wish] support for large files
by Jörg Schilling - Apr 6th 2007 04:49:26
The "large file limit" is 2**31 -2 bytes.
Mkisofs already writes larger files since
a long time. Mkisofs supports to write the max.
size of UDF files (234 GB) since 2002 but
limits the size to 4 GB - 2kB for consistency
with ISO-9660.
If you like to write files larger than
4 GB - 2kB, then you need to wait a few weeks.
Mkisofs will start to support files up to
8 TB with ISO-9660 soon. Note that compatibility
and consistency is better than implementing
hacks.
[reply]
[top]
[»]
There is a better option these days.
by karmaflux - Mar 12th 2007 09:43:47
Oh, look. Jörg is calling linux "broken" again. Raise your hand if you're
surprised.
For those of you who don't think one CD burning application is worth
altering the entire linux drive addressing system, there is a better
option. It's called "cdrkit" and it's a fork of cdrecord from before Jörg
screwed the license up. It's being run by some debian devs, but I can
attest it works on slackware too.
The freshmeat entry for cdrkit is here:
http://freshmeat.net/projects/cdrkit/
and the project home page is
http://www.cdrkit.org
[reply]
[top]
[»]
Re: There is a better option these days.
by Andraž 'ruskie' Levstik - Mar 12th 2007 12:38:40
And here's another alternative:
http://libburnia.pykix.org/
It works great and I had no probs with it.. It still lacks it's own iso
genarting app but other than that should be good enough for day-to-day
use...
[reply]
[top]
[»]
Re: There is a better option these days.
by Jörg Schilling - Mar 12th 2007 13:46:50
I recommend you to inform yourself before writing.
The software distributed by Debian is only
to fool users :-(
There is no development at the Debian variant
except for introducing new bugs. The original
software on the other side is constantly under developement.
Cdrtools is still the best solution and all
people who reported problems with debians
destroyed version were happy after the did
go back to the original.
[reply]
[top]
[»]
Re: There is a better option these days.
by karmaflux - Mar 16th 2007 17:24:21
Debian's software, like libburn, is under constant development. They're
also truly Free software packages. Furthermore, they're not in Sun's
pocket, so they actually work right under linux.
The parent post is typical Jörg FUD; prospective users, please try both
and judge for yourself.
[reply]
[top]
[»]
Re: There is a better option these days.
by Jörg Schilling - Jul 7th 2007 10:48:44
libburn is no Debian peoject...
This kind of incorrect claims is typical for the people behind cdrkit...
Cdrtools is a free
project that depends on nobody who pays for it.
All people from Debian who are involved in the
disput and who started it, are payed for their
work at Debian. Besides the fact that the Debian
fork you are talking about is dead for a while,
tell me who has which commercial interests in
the this act against OSS that has been initiated
by a small number of people from Debian?
I understand that people like you cannot live with the truth and call it
FUD...
[reply]
[top]
[»]
Buring
by dorphell - Sep 12th 2006 10:53:40
A [relatively] recent feature in cdrtools (in mkisofs) enables it to detect
file changes while burning 'on-the-fly' and quits the burn.
I.e. with a command such as:
mkisofs /files | cdrecord -options -
It errors with something like:
mkisofs: File '/so/and/so' did grow
I've looked at both manuals and couldn't find a way to turn this
off. Is there a hidden flag of some sort or some way to counter this?
[reply]
[top]
[»]
Re: Buring
by E. Bloch - Apr 3rd 2007 07:23:57
There was a bug related to that which we fixed in genisoimage, see cdrkit
package.
[reply]
[top]
[»]
Virus?
by aleoje - Jul 19th 2006 13:34:54
ScanMail is detecting a virus in 2.01.
Is this possible?
"ScanMail detected and removed a virus from the original
mail entity. You can safely save or delete this replacement
attachment."
[reply]
[top]
[»]
Re: Virus?
by CoderGuy - Jun 8th 2007 22:45:06
> ScanMail is detecting a virus in 2.01.
> Is this possible?
>
> "ScanMail detected and
> removed a virus from the original mail
> entity. You can safely save or delete
> this replacement attachment."
>
I ran into this issue (not with scanmail though) and went back and
downloaded from another source, didn't have issues the second time around.
I don't believe it's actually a virus, just some add-on content that
tripped the scanner.
Best Regards,Jim
-- "Suicide Hotline, please hold" Translation = You're hosed~
[reply]
[top]
[»]
Seems great to me
by hairdude - Mar 29th 2006 10:05:29
Well, I don't know about much, but this seems like a great, free tool to
me. Just wanted to say thanks.
[reply]
[top]
[»]
Liteon DVD burner not working
by Patrick - Feb 12th 2006 15:33:57
I purchased a Lite-On SHW-1635S Dual-layer DVD burner last month with a
gift card I received for Christmas.
This burner claims write speeds of
48X CD-R
24X CD-RW
8X DVD-RW
8X DVD+RW
4X DVD+R DL
16X DVD+R
Yet, I was only able to get
16X CD-R (with 52X capable blank CD-R)
6X DVD+R (with 16X capable blank DVD+R)
error attempting to burn DVD+R DL (2.4X capable)
I started examining the source code to cdrtools (version 2.01) and noticed
that cdrecord has some due to a bug (intentional or not) in Lite-on's
firmware, dating back to 1998 or so. The changelog mentions something to
this effect.
It's a moot point trying to get this fixed, since I took the drive back
and exchanged it for a different brand/model (which works fine).
I use Linux, compile cdrtools from source, and used K3b (also compiled
from source). Any others' ideas? Thanks
[reply]
[top]
[»]
Re: Liteon DVD burner not working
by Patrick - Feb 12th 2006 15:37:22
> I started examining the source code to
> cdrtools (version 2.01) and noticed that
> cdrecord has some due to a bug
> (intentional or not) in Lite-on's
> firmware, dating back to 1998 or so.
> The changelog mentions something to this
> effect.
The above should say:
I started examining the source code to cdrtools (version 2.01) and noticed
that cdrecord has some FIXES to accommodate a bug (intentional or not) in
Lite-on's firmware....
Many apologies!
[reply]
[top]
[»]
Never use this software directly but get a patched version from a major distribution
by Roberto Jimeno - Feb 6th 2006 04:13:06
Never use Jörg Schilling's cdrtools directly since this guy is being paid
by Sun and that means that other operating systems like Linux are not taken
into account. You have to use the patched cdrtools versions from a major
Linux distribution like RedHat, SUSE or Debian since that cdrtools
incorporate a set of patches that make it useful and stable.
For DVD+-RW recording use dvd+rw-tools
[reply]
[top]
[»]
Re: Never use this software directly but get a patched version from a major distribution
by Jörg Schilling - Feb 9th 2006 00:24:19
I hope that Freshmeat is removing your silly comments that publish lies on
me and cdrtools and
that advertizes for a product with unclear license.
[reply]
[top]
[»]
Re: Never use this software directly but get a patched version from a major distribution
by Jörg Schilling - Feb 9th 2006 00:34:07
About 50% of all prolems with cdrtools on
RedHat, SuSE or Debian are a _result_ of the
patches applied by these distributions and
another 40% of the problems on Linux based
systems are a result of bugs in the Linux
Kernel.
I recommend to use the original and unmodified
software and to use Operating systems that do
not boycot CD/DVD writing.
[reply]
[top]
[»]
Re: Never use this software directly but get a patched version from a major distribution
by karmaflux - May 1st 2006 20:41:58
> another 40% of the problems on Linux based
> systems are a result of bugs in the
> Linux Kernel.
Those aren't "bugs," Jorg; they're deliberate design decisions which you
refuse to accept. Linux is not UNIX. Get used to it, please. Your tools
are better, but I'm forced to use a different software package because you
decided not to support the device interface on Linux.
[reply]
[top]
[»]
Re: Never use this software directly but get a patched version from a major distribution
by Thomas M. - Aug 18th 2006 17:35:50
If you read these comments and don't know what the fuss is about you might want to read this article
first. Tom
[reply]
[top]
[»]
Re: Never use this software directly but get a patched version from a major distribution
by scdbackup - May 27th 2006 03:39:41
Although it can be a bit cumbersome with SuS9.0 include files i prefer to
compile cdrecord binaries from Joerg's original sources. This is especially
rewarding now since the recent development version 2.01.01a09 includes
unlimited DVD support and there is no need any more to maintain a
cdrecord-ProDVD binary with temporary license keys.
As for dvd+rw-tools (aka growisofs): i still prefer this over cdrecord for
DVD because it can pipe a data stream of unpredicted length.
The main advantage of cdrecord with DVD is its unified command interface
for CD and DVD. You might be able to talk some stone-old CD frontend into
burning DVD that way.
Thank heaven for cdrecord and mkisofs !
[reply]
[top]
[»]
Re: Never use this software directly but get a patched version from a major distribution
by CoderGuy - Jun 14th 2007 16:47:30
> Never use Jörg Schilling's cdrtools
> directly since this guy is being paid by
> Sun and that means that other operating
> systems like Linux are not taken into
> account. You have to use the patched
> cdrtools versions from a major Linux
> distribution like RedHat, SUSE or Debian
> since that cdrtools incorporate a set of
> patches that make it useful and stable.
>
> For DVD+-RW recording use dvd+rw-tools
Up until recently I have utilized this tool for personal use only.
Recently have impelted it for a company that shoots panoramas and duplicates in mass
quantities. They do alot of data transfer and are very thorough in their
process for baking up their data and requested DVD backups of info as well
as servers to contain the info. This software has not fallen short of what
it says, and I will definately suggest to future clientel~
Regards, Jay
-- "Suicide Hotline, please hold" Translation = You're hosed~
[reply]
[top]
[»]
new
by Georgia - Jan 16th 2006 05:01:41
New user..
Can't record new files on a cd.. Anyway, looks like a great site.
Interested in editing music files when I have time.
-- List Georgia realestate 4 free.
[reply]
[top]
[»]
DVD/DVD+RW?
by MusicJ - Oct 20th 2005 10:32:27
Any plans to support DVDRs or DVD+RWs?
-- Jason
[reply]
[top]
[»]
Re: DVD/DVD+RW?
by Chaotic Thought - Oct 28th 2005 01:32:35
See the homepage and look for cdrecord-prodvd; that is the version that
supports DVD writing.
[reply]
[top]
[»]
Re: DVD/DVD+RW?
by Jörg Schilling - Feb 9th 2006 00:26:23
Cdrecord supports DVD-R since February 1998
and DVD+R since April 2003.
[reply]
[top]
[»]
creating a mac bootable cd
by Dario - Jun 9th 2005 10:58:54
I have Yellowdog Linux installed on powermac G3. Im trying to create a
bootable/live Linux CD that runs on a mac. Everything i have tried so far
has failed.
This is the directory structure on my CD
/boot
/boot/yaboot
/boot/yaboot/ofboot.b
/boot/yaboot/yaboot.conf
/boot/yaboot/msg
/boot/yaboot/hfs.map
/boot/yaboot/yaboot
/boot/yaboot/.yaboot.conf.swp
/boot/kernels
/boot/kernels/264dario
/boot/kernels/264dario/System.map
/boot/kernels/264dario/vmlinux
/boot/kernels/264dario/modules.tar.bz2
/boot/kernels/264dario/config
/boot/stages
/boot/stages/stage1.gz
/boot/stages/stage2.tar.bz2
This is my yaboot.conf file
timeout=0
device=cd:
default=Linux
message=/boot/yaboot/msg
image=/boot/kernels/264dario/vmlinux
label=Linux
initrd=/boot/stages/stage1.gz
read-only
This is my ofboot.b file
<CHRP-BOOT>
<COMPATIBLE>
MacRISC MacRISC2 MacRISC3 MacRISC4
</COMPATIBLE>
<DESCRIPTION>
EzBackup sa boot loader
</DESCRIPTION>
<BOOT-SCRIPT>
" screen" output
load-base release-load-area
boot cd:,\boot\yaboot\yaboot
</BOOT-SCRIPT>
</CHRP-BOOT>
This is my hfs.map file
# ext. xlate creator type comment
.hqx Ascii 'BnHx' 'TEXT' "BinHex file"
.mov Raw 'TVOD' 'MooV' "QuickTime Movie"
.bin Raw 'ddsk' 'DDim' "Floppy or ramdisk image"
.img Raw 'ddsk' 'DDim' "Floppy or ramdisk image"
.b Raw 'UNIX' 'tbxi' "bootstrap"
yaboot Raw 'UNIX' 'boot' "bootstrap"
vmlinux Raw 'UNIX' 'boot' "bootstrap"
.conf Raw 'UNIX' 'conf' "bootstrap"
* Ascii '????' '????' "Text file"
and my mkisofs command
mkisofs -o $ROOTDIR/../<myiso>.iso \
-R -J -V "$VOLID" \
-hide-rr-moved \
-v -d -N \
-chrp-boot \
-hfs --netatalk -probe -part --no-desktop \
-hfs-bless /boot/yaboot \
-map $ROOTDIR/yaboot/hfs.map \
-A "$APPID"
Can anyone give me any ideas?
[reply]
[top]
[»]
MKISOFS Hide Folder
by John M - Jun 9th 2005 08:06:51
I am creating a hybrid iso image, and am having alot of trouble getting a
folder to appear on HFS and not appear on ISO. I need to hide the folder
called "image" which is in a folder called "Temp" both
of which are in a folder called "Hybrid" which contains
MKISOFS.exe and cygwin1.dll. Here is what I tried:
mkisofs -hfs -r -joliet-long -relaxed-filenames -allow-lowercase -hide
*.html -hide-joliet *.html -hide-hfs *.inf -hide-hfs *.EXE -V "Hybrid
CD" -hfs-volid "Hybrid CD" -map map.txt -part -no-desktop -o
Hybrid.iso -path-list Hybrid.txt -graft-points -hide image -hide-joliet
image
This hides everything listed (html on iso, rr and joliet, and inf/exe on
hfs) but it doesn't hide the folder called "image" from the hfs
filesystem. Please help. Thanks alot.
John Milton
[reply]
[top]
[»]
Re: MKISOFS Hide Folder
by John M - Jun 9th 2005 08:47:34
In my original post, the last line said
> but it doesn't hide the folder called
> "image" from the hfs
> filesystem.
I made a mistake, I really need to hide the "image" folder from the ISO
and Joliet filesystems. I only want the "image" folder in the HFS
filesystem. Sorry about the confusion.
John Milton
[reply]
[top]
[»]
readcd Input/output error on MacOSX 10.4
by rob - Jun 2nd 2005 01:55:48
Hi,
I have installed cdrtools 2.01 on my iBook under MacOSX 10.4.1 (Darwin
8.1.0), using "IODVDServices" as the device (specified in the
'/private/etc/default/cdrecord' file). cdrecord successfully checks the
combo-drive, but readcd fails to read an Audio-CD, coming up with an
Input/output error:
osx:~ roal$ disktool -u disk2; cdrecord -checkdrive
disk2 device will be unmounted ...
***Notifications Complete for type 1
***Responding yes to unmount - disk2
***Disk Unmounted('disk2')
Cdrecord-Clone 2.01 (powerpc-apple-macosx8.1.0) Copyright (C) 1995-2004
Jörg Schilling
scsidev: 'IODVDServices'
devname: 'IODVDServices'
scsibus: -2 target: -2 lun: -2
Using libscg version 'schily-0.8'.
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'MATSHITA'
Identifikation : 'CD-RW CW-8124 '
Revision : 'DB0D'
Device seems to be: Generic mmc2 DVD-ROM.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-2 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P
RAW/R96R
osx:~ roal$ disktool -u disk2; readcd f=mycd
disk2 device will be unmounted ...
***Notifications Complete for type 1
***Responding yes to unmount - disk2
***Disk Unmounted('disk2')
Read speed: 4233 kB/s (CD 24x, DVD 3x).
Write speed: 4233 kB/s (CD 24x, DVD 3x).
Capacity: 43647 Blocks = 87294 kBytes = 85 MBytes = 89 prMB
Sectorsize: 2048 Bytes
Copy from SCSI (0,0,0) disk to file 'mycd'
end: 43647
readcd: Input/output error. read_g1: scsi sendcmd: no error
CDB: 28 00 00 00 00 00 00 00 10 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: F0 00 05 00 00 00 00 0A 00 00 00 00 64 00 00 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x64 Qual 0x00 (illegal mode for this track) Fru 0x0
Sense flags: Blk 0 (valid)
resid: 32768
cmd finished after 2.713s timeout 40s
readcd: Input/output error. Cannot read source disk
readcd: Retrying from sector 0.
readcd: Input/output error. Error on sector 0 not corrected. Total of 1
errors.
Time total: 54.060sec
Read 0.00 kB at 0.0 kB/sec.
Max corected retry count was 0 (limited to 128).
The following 1 sector(s) could not be read correctly:
0
Is this a problem with MacOSX 10.4 or with the MATSHITA CW-8124
drive?
Thanks!
rob.
[reply]
[top]
[»]
A really useful program
by wiremore - Apr 19th 2005 01:55:18
All of these comments seem so negative. I would like to point out that this
is the only (afaik) CD or DVD burning software for Linux, and that it works
really well. I for one am really grateful to Jörg Schilling for
writing this and giving it away for free. I have just successfully and
happily burned yet another CD using this software.
[reply]
[top]
[»]
Re: A really useful program
by William W. Ferrell - Apr 26th 2005 12:57:34
> All of these comments seem so negative.
> I would like to point out that this is
> the only (afaik) CD or DVD burning
> software for Linux, and that it works
> really well. I for one am really
> grateful to Jörg Schilling for
> writing this and giving it away for
> free. I have just successfully and
> happily burned yet another CD using this
> software.
You're on Freshmeat; look around and see plenty of other tools,
like cdrdao, dvd+rw-tools, and so on. cdrecord is old and "mature" but it
certainly misbehaves often enough to make it not worth using on many
platforms. Between that and its annoying dual-licensing (DVD mastering
requires a non-free (as in speech) license for this thing) it's just not
worth the bother.
[reply]
[top]
[»]
Re: A really useful program
by Thomas M. - Apr 27th 2005 23:48:20
Yes, there are alternatives to cdrtools. But that's not the point: one has
to give credit where credit is due and Jörg Schilling made some nice
contributions to OSS/FS with cdrtools being the most important one. Tom
[reply]
[top]
[»]
Re: A really useful program
by Veerakumar - May 19th 2005 01:27:27
Definetely cdrecord is a very good and stable program. If you or the so
called linux distributions (RedHat, Suse and etc) falter in compiling and
packaging the software, it's definetly not the fault of cdrecord / cdrtools
author - Jorg Schilling. Don't piss him or criticize him without an ounce
of sense. Have you ever read the whole documentation of cdrecord before
compiling? Nah. It's true linux kernel scsi interface changes now and then.
But it's not jorg fault for cdrtools not working with the new unsupported
kernel. It's your or distributors fault for building cdrtools with
unsupported kernel. If you want a free dvd burning solution go for it; you
are free man. It doesn't means you would point finger at Jorg. May be Jorg
shouldn't even read or post in forums where people don't know a single
thing and think they know everything. Self made bosses.
-- Visit me at Veera
[reply]
[top]
[»]
cdrecord run scsi command time out
by henry - Jan 26th 2005 00:02:36
Hi All,
I have run cdrtools-2.01 to the system,which have linux(2.4.17),AMD x86
cpu, pdc20618 ide controller and sony CD-R/RW CRX230A.
It seem not to work well.
1.when I can run "cdrecord blank=fast driveropts=burnfree speed=2
dev=0,0,1" ,sometime
the CDRW can work completely but it occupy the memory very large to
20M.
cdrtools command the memory fs=4M defaultly?
=========================
when no run cdrecord
=========================
# cd /proc
# cat meminfo
total: used: free: shared: buffers: cached:
Mem: 59797504 26144768 33652736 0 155648 10240000
Swap: 0 0 0
MemTotal: 58396 kB
MemFree: 32864 kB
MemShared: 0 kB
Buffers: 152 kB
Cached: 10000 kB
SwapCached: 0 kB
Active: 1924 kB
Inactive: 14576 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 58396 kB
LowFree: 32864 kB
SwapTotal: 0 kB
SwapFree: 0 kB
#
=========================
when run cdrecord
=========================
# cat meminfo
total: used: free: shared: buffers: cached:
Mem: 59797504 58617856 1179648 0 77824 10436608
Swap: 0 0 0
MemTotal: 58396 kB
MemFree: 1152 kB
MemShared: 0 kB
Buffers: 76 kB
Cached: 10192 kB
SwapCached: 0 kB
Active: 27208 kB
Inactive: 21036 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 58396 kB
LowFree: 1152 kB
SwapTotal: 0 kB
SwapFree: 0 kB
#
2.when there occur error just as:
========================================================================================
scsi : aborting command due to timeout : pid 6828, scsi0, channel 0, id 0,
lun 0 0x2a 00 00 00 25 0e 00 00 1f 00
scsi : aborting command due to timeout : pid 7943, scsi0, channel 0, id 0,
lun 0 0x2a 00 00 00 25 0e 00 00 1f 00
/opt/bin/cdrecord: Input/output error. write_g1: scsi sendcmd: cmd timeout
after 80.030 (40) s
CDB: 2A 00 00 00 25 0E 00 00 1F 00
cmd finished after 80.030s timeout 40s
write track data: error after 19427328 bytes
/opt/bin/cdrecord: A write error occured.
/opt/bin/cdrecord: Please properly read the error message above.
scsi : aborting command due to timeout : pid 9201, scsi0, channel 0, id 0,
lun 0 0x00 00 00 00 00 00
scsi : aborting command due to timeout : pid 10312, scsi0, channel 0, id
0, lun 0 0x00 00 00 00 00 00
/opt/bin/cdrecord: Input/output error. test unit ready: scsi sendcmd: cmd
timeout after 80.026 (40) s
CDB: 00 00 00 00 00 00
cmd finished after 80.026s timeout 40s
scsi : aborting command due to timeout : pid 11430, scsi0, channel 0, id
0, lun 0 0x35 00 00 00 00 00 00 00 00 00
/opt/bin/cdrecord: faio_wait_on_buffer for writer timed out.
scsi : aborting command due to timeout : pid 14770, scsi0, channel 0, id
0, lun 0 0x35 00 00 00 00 00 00 00 00 00
/opt/bin/cdrecord: Input/output error. flush cache: scsi sendcmd: cmd
timeout after 240.030 (120) s
CDB: 35 00 00 00 00 00 00 00 00 00
cmd finished after 240.030s timeout 120s
Trouble flushing the cache
scsi : aborting command due to timeout : pid 18105, scsi0, channel 0, id
0, lun 0 0x35 00 00 00 00 00 00 00 00 00
scsi : aborting command due to timeout : pid 21449, scsi0, channel 0, id
0, lun 0 0x35 00 00 00 00 00 00 00 00 00
=======================================================================================
then the scsi will abort all command time and time and my system become to
slow.
and the the time to timeout become longer and longer.and the cdrecord
command can not
return so long time.
How I can solve it ?
3. when the cdrw can not work well,I kill the process and make command
"cdrecord -scanbus" .
there occur error:
=======================================================================================
Linux sg driver version: 3.1.22
scsi : aborting command due to timeout : pid 38144, scsi0, channel 0, id
0, lun 0 0x5b 00 02 00 00 00 00 00 00 00
scsi : aborting command due to timeout : pid 46527, scsi0, channel 0, id
0, lun 0 0x00 00 00 00 00 00
scsi : aborting command due to timeout : pid 47646, scsi0, channel 0, id
0, lun 0 0x00 00 00 00 00 00
scsi : aborting command due to timeout : pid 48754, scsi0, channel 0, id
0, lun 0 0x5b 00 02 00 00 00 00 00 00 00
=======================================================================================
it will try again and again.there are some scsi command to execute to
reset the device
just as the power on reset? I confuse whether the sony cdrw can be reset
by command to
let it work normal when occur error.
I need your help and Please give me some advice.
Best Regards
Henry
[reply]
[top]
[»]
Licensing question
by Ronny Løken - Jan 21st 2005 06:38:52
Hi, I have a short question about the nature of the license for
cdrecord-prodvd and cdrtools.
Is this software free and unrestricted for personal use?
If so, why does cdrecord-prodvd produce the output
Unlocked features:
Limited features:
I am using SuSE 9.1, and have trouble with the "SuSE" version
when burning CUE/BIN audio-CDs.
[reply]
[top]
[»]
Multiple CD Burner support
by Kingtrae - Nov 9th 2004 15:06:57
is there multiple CD burner support built into cdrecord? I'm
trying to make a CD burning machine with multiple burners
[reply]
[top]
[»]
Re:
by root - Dec 7th 2004 04:16:50
Not very nice, burning is broken on latest kernels. People
will be afraid of switching to linux. Solution? someone that
is willing and knows how to code like the Author himself.
Coding: good coder values: poor from this Author. I have
spent days cursing with "rage" nearly a heart attack,
because 2.6.9 does not work. "2.4" kernel has troubles too
mind you on debian argg. Would not have wrote this rant
but it is 7:00 AM for past 24 hours (yes serious) "I" been
trying to get this to work.
I am a student do not have the time to play with burning. I
need to backup things. Contribute? yes but have no skills in
code. What is linux coders waiting for?? those that do
know how to code. It is obviously the Author has no wish to
upgrade to the "nicer" looking /dev/hdX interface. " 0,1,0"
"0,5,2" seems nicer? Well, do not know maybe he has a
reason for not wanting. From a user view it is broken for 1
year. I left windows for linux, but I am not sure if I made
the right choice now. I am frustrated, tired, going from
distro to distro for cdrecords / cdrtools. The 2.03 worked
only version that did!! Well, I had other problems and
switched to Debian and like it. (aside from recording)
This problem is very serious not just for me forget me. It
is bad for any user that seems helpless because it does not
work. Being open source is nice, people can jump in and
help. However, catchy catch. Not all users know how to
code. What can a user do in this case? Again, surely hope
this is fixed soon or someone starts a new project. Not to
discourage the Author who already did a well job on the
old code part. However, rebellion is only going to hurt the
user.
[reply]
[top]
[»]
Re: Burning is broken ???
by Douw - Dec 8th 2004 20:33:49
Just run k3b as root - root - get it ?
You can do this in your user by opening a "File Manager - Super user"
press F4 on that and then type "k3b" and enjoy ... !
> Not very nice, burning is broken on
> latest kernels.
[reply]
[top]
[»]
Re: Burning is broken ???
by root - Dec 9th 2004 02:19:07
I appreciate for your reply however this is worse now. The
recent "2.6.9-1" kernel has more issues. Now it hangs
sometimes as root too, besides root can be dangerous.
[reply]
[top]
[»]
Help needed with the cdrtools project
by Jörg Schilling - Sep 8th 2004 03:57:23
As you may have noted, more and more people
who just don't know enough about
free software
try to tear me into useless discussions about
licensing and thus steal my time.
Nearly nobody helps me to answer support
questions in the cdrtools related mailing lists.
The Linux kernel people constantly add new snares
to the SCSI generic transport interface,
making
it harder and harder to implement CD/DVD writing
on Linux.
Please note that I am one of the most active coder in the Open Source /
Free Software scene.
Cdrtools
is not the only project I am working on. I actively maintain more
than 20 MB of sourcecode...
If I don't get help in the near future, I cannot
continue the same way as before.
Free Software never has been intended as it currently is (with a majority
of only consuming users).
Contributing to a project may be done
in many ways, e.g. by helping to manage the web pages.
I need people who are willing to contribute
their time to my projects in order to to be able to continue working
on free software....
[reply]
[top]
[»]
Re: Help needed with the cdrtools project
by arys - Sep 8th 2004 12:04:58
Ahh, so now it's the community that doesn't understand free software. The
way I see it, you're adding a clause to your software that is in violation
of the GPL. You're claiming that you're doing so in retaliation to SuSE
"discrediting" you, which you apparently think is both in violation of the
GPL, as well as of copyright law.
If you weren't quite so ignorant as you obviously are, you'd already know
that there is absolutely -nothing- wrong with SuSE using your code to
produce their own open-source derivative, nothing wrong with them adding
features to it, and nothing wrong with it having some problems as a result
of these added features.
Before you decry the community as being ignorant, you might want to do a
little reading yourself.
If you stopped developing cdrtools tomorrow, someone else would pick up
where you left off. I doubt you would even be missed at this point. Perhaps
they're not helping or contributing because they don't feel you're
trustworthy.
> As you may have noted, more and more
> people
> who just don't know enough about
>
> free software
> try to tear me into useless discussions
> about
> licensing and thus steal my time.
>
>
> Nearly nobody helps me to answer
> support
> questions in the cdrtools related
> mailing lists.
>
>
> The Linux kernel people constantly add
> new snares
> to the SCSI generic transport
> interface,
> making
> it harder and harder to implement CD/DVD
> writing
> on Linux.
>
>
> Please note that I am one of the most
> active coder in the Open Source / Free
> Software scene.
> Cdrtools
> is not the only project I am working on.
> I actively maintain more
> than 20 MB of sourcecode...
>
>
> If I don't get help in the near future,
> I cannot
> continue the same way as before.
>
>
> Free Software never has been intended as
> it currently is (with a majority of only
> consuming users).
>
> Contributing to a project may be done
> in many ways, e.g. by helping to manage
> the web pages.
> I need people who are willing to
> contribute
> their time to my projects in order to to
> be able to continue working on free
> software....
>
[reply]
[top]
[»]
Re: Help needed with the cdrtools project
by Jörg Schilling - Sep 9th 2004 02:18:03
I don't decry the community. However I don't like
people who write about the community but are
not part of it.
As it seems that you never made any contribution
to the free software pool, I would not count
you as a part of the community.
[reply]
[top]
[»]
A warning to cdrecord users
by arys - Aug 23rd 2004 08:55:30
I invite you to read the following article that was recently posted at
MozillaZine regarding the maintainer's questionable behaviour:
http://weblogs.mozillazine.org/gerv/archives/006193.html
The maintainer makes the claim that he is adding a provision to the
licensing of his software which, in and of itself, violates the GPL
himself. Further, he claims that the producers of the SuSE Linux
distribution are violating section 6 of the PREAMBLE of the GPL. In his
ignorance he has perhaps overlooked the fact that it isn't actually
-possible- to violate the preamble of the GPL, as the terms and conditions
of the license haven't even begun in that document.
It has been suggested that the true motivation for this addition is the
fact that SuSE has patched the current version of cdrecord to include DVD
writing support; a feature which the maintainer only offers in a
proprietary, commercial form. In either case, it would be wise not to
upgrade to a development version of cdrecord until a fork is created, or
the maintainer takes the time to re-read the license that he supposedly has
released his software under.
[reply]
[top]
[»]
Re: A warning to cdrecord users
by Jörg Schilling - Sep 8th 2004 03:24:01
You are completely uninformed and make
false claims :-(
SuSE's version is cdrecord is completely broken.
The so called DVD support does not work (except
in rare cases). As the applied patch ignores
the data structures inside cdrecord, the patch
in addition causes cdrecord to missbehave even
when writing CDs.
What SuSE does is to discredit the reputation
of the original author which is forbidden by the
GPL and in addition is a violation of the
Copyright law.
Is is funny to see that people like you always
cry for a "fork" but never contribute anything
to Open Source projects :-(
[reply]
[top]
[»]
Re: A warning to cdrecord users
by arys - Sep 8th 2004 11:59:19
% You are completely uninformed and make
> false claims :-(
Funny that you don't actually bring up any evidence to support that. On
the other hand, the fact that you mistook the preamble of the GPL as being
an actual -condition- of the license is a clear example of your ignorance.
Care to actually try and discredit my claims?
> SuSE's version is cdrecord is completely
> broken.
> The so called DVD support does not work
> (except
> in rare cases). As the applied patch
> ignores
> the data structures inside cdrecord, the
> patch
> in addition causes cdrecord to
> missbehave even
> when writing CDs.
And what's your point? You released the source under the GPL, which you
claim you attribute to your software despite violating it yourself. If
someone wishes to take your source code and write their own version they're
permitted to, even if that implementation is technically inferior to your
own. So far, you have no case.
> What SuSE does is to discredit the
> reputation
> of the original author which is
> forbidden by the
> GPL and in addition is a violation of
> the
> Copyright law.
Is that so? Care to point out the provisions in U.S. copyright law, as
well as the provisions in the GPL, that state that you're not allowed to
use GPL'ed source code to produce a product that isn't as good as your own?
Really, I'd be interested in seeing it, assuming it exists. I'm going to
say that it doesn't, and that even if it did, it wouldn't apply in this
case. Feel free to prove me wrong.
> Is is funny to see that people like you
> always
> cry for a "fork" but never contribute
> anything
> to Open Source projects :-(
Ooh, big man with big insults. And a frowny-face to boot. How old are you
again?
People cry "fork" because of people like you, who live in ignorance of the
licenses that you've released your own software under. SuSE is within their
right to remove your ridiculous clause from the source if they so choose.
That is, unless you've never accepted -any- patches from outside sources to
cdrtools, which incidentally would also fall under that same license. If
that's the case then sure, you could very well relicense your software, but
people would still be free to use the source for the previous version, and
continue on where you left off.
I strongly suggest you do some reading and inform yourself before you
attempt to discredit me again.
[reply]
[top]
[»]
Re: A warning to cdrecord users
by Jörg Schilling - Sep 9th 2004 02:01:51
You should inform yourself before writing.
The US Copyright law does not apply to cdrecord.
Read the European and the German Copyright laws...
[reply]
[top]
[»]
CDRecord running on RedHat 7.3
by Thom Paine - Aug 17th 2004 10:13:45
I'm having trouble getting cdrecord to work properly to burn a dvd on
RedHat 7.3.
I get the scsi sendcmd error and it aborts the burn.
I'm trying to write to dvd-rw discs and I have the exact same drive in my
box running FC2 and it works well.
I'm not sure how else to troubleshoot this right now.
Any help would be appreciated.
Thanks.
[reply]
[top]
[»]
Re: CDRecord running on RedHat 7.3
by Jörg Schilling - Sep 8th 2004 03:25:30
Use cdrecord-ProDVD
ftp://ftp.berlios.de/pub/cdrecord/ProDVD/
[reply]
[top]
[»]
Re: CDRecord running on RedHat 7.3
by arys - Sep 9th 2004 09:58:11
I would strongly suggest that you use dvd+rw-tools
(http://fy.chalmers.se/~appro/linux/DVD+RW/) and K3B
(http://k3b.sourceforge.net). They are a great alternative to the
commercial package that the cdrecord author is attempting to sell, and has
the added bonus of being licensed under terms that aren't suspect.
> I'm having trouble getting cdrecord to
> work properly to burn a dvd on RedHat
> 7.3.
>
> I get the scsi sendcmd error and it
> aborts the burn.
>
> I'm trying to write to dvd-rw discs and
> I have the exact same drive in my box
> running FC2 and it works well.
>
> I'm not sure how else to troubleshoot
> this right now.
>
> Any help would be appreciated.
>
> Thanks.
[reply]
[top]
[»]
Sorry, I'm new to this...
by Hitokiri - Jul 26th 2004 14:32:25
Does cdrtools support ExacLink and other such technologies that remove the
possibility of buffer-underrun errors?
[reply]
[top]
[»]
Re: Sorry, I'm new to this...
by Jörg Schilling - Sep 8th 2004 03:27:21
RTFM is sooooo simple and even faster than
writing here...
Any documented Buffer underrun method is supported
[reply]
[top]
[»]
Re: Sorry, I'm new to this...
by Tom Rowan - Dec 21st 2004 10:24:54
> RTFM is sooooo simple and even faster
> than
> writing here...
>
> Any documented Buffer underrun method is
> supported
>
Yes but for people TRULY new to this, RTFM may be a challenge too! :p
[reply]
[top]
[»]
Re: Sorry, I'm new to this...
by William W. Ferrell - Apr 26th 2005 13:06:50
> Does cdrtools support ExacLink and other
> such technologies that remove the
> possibility of buffer-underrun errors?
Yes, it does. Add "-driveropts=BURNFREE" to your command line to enable
the drive's buffer underrun protection.
As an aside, if we (as a community) would stop with all the snide comments
(like "RTFM!") and actually give helpful answers, we might actually
encourage more people to join and support the community instead of
running folks off with such a nasty attitude. (This is aimed squarely at
the software's author who posted a reply to the parent post here -- dude,
*you* don't have to offer "newbie" support for your application but you
surely don't have to throw out snide remarks like that one when someone
dares to ask a basic question...)
[reply]
[top]
[»]
Problems compiling?
by Ryan Egesdahl - Apr 19th 2004 15:51:30
If you are having problems compiling cdrtools-2.0.3 because you get strange
errors like "parse error before U8" in a file included from
"scsi-linux-sg.c" and complaints that user "bin" does
not exist (say because you use something like LFS), then this patch is for
you. I scoured the internet for the fixes just a few minutes ago to produce
it.
<--- SNIP: cdrtools-2.0.3-fixincludeandinstall.patch --->
diff -u -r ./DEFAULTS/Defaults.linux
../cdrtools-new/DEFAULTS/Defaults.linux
--- ./DEFAULTS/Defaults.linux 2003-02-15 18:01:48.000000000 -0600
+++ ../cdrtools-new/DEFAULTS/Defaults.linux 2004-04-19
17:31:02.920133451 -0500
@@ -34,5 +34,5 @@
#
DEFINSMODEF= 444
DEFINSMODEX= 755
-DEFINSUSR= bin
-DEFINSGRP= bin
+DEFINSUSR= root
+DEFINSGRP= root
Only in .: diff.patch
diff -u -r ./libscg/scsi-linux-sg.c
../cdrtools-new/libscg/scsi-linux-sg.c
--- ./libscg/scsi-linux-sg.c 2002-10-21 11:20:35.000000000 -0500
+++ ../cdrtools-new/libscg/scsi-linux-sg.c 2004-04-19
17:31:02.952128286 -0500
@@ -66,6 +66,13 @@
#if LINUX_VERSION_CODE >= 0x01031a /* <linux/scsi.h> introduced
in 1.3.26 */
#if LINUX_VERSION_CODE >= 0x020000 /* <scsi/scsi.h> introduced
somewhere. */
/* Need to fine tune the ifdef so we get the transition point right.
*/
+
+/******** New code to include the u8 type... */
+#define __KERNEL__
+#include <asm/types.h>
+#undef __KERNEL__
+/* End of new code ***************************/
+
#include <scsi/scsi.h>
#else
#include <linux/scsi.h>
<--- SNIP
------------------------------------------------------->
And for those of you who don't know what to do with it, just cut and paste
it into a file of the appropriate name, save it to the base source
directory for cdrtools-2.0.3 and run:
patch -Np1 -i cdrtools-2.0.3-fixincludeandinstall.patch
That's it! Now go build it.
[reply]
[top]
[»]
Re: Problems compiling?
by Jörg Schilling - Sep 8th 2004 03:31:10
The cause for the compilation problems is
a bug in the Linux kernel include files.
It is a bad idea to try to "fix" correct
code instead of fixing the bugs.
After 2 years, the bug in the Linux kernel
has been fixed in 2.6.8. Unfortunately
Linux-2.6.8.1 started to break CD/DVD writing
in suid root applications by breaking interfaces :-(
[reply]
[top]
[»]
Any ideas? Burn died with MagicSpin 8x Dvd-+r rw
by yucele - Dec 23rd 2003 08:57:32
I am pretty new at this, just bought the DVD-r the other day.
I got this trying to burn a 2.5 gig file, any help would be greatly
appriciated.
Regards,
Yucel
(ps image is xiso)
[root@yucel-linux Pan]# dvdrecord speed=1 -dao dev=0,0,0 image.iso
dvdrtools v0.1.3
Portions (c) 2002 Red Hat, Inc.
Based on:
Cdrecord 1.11a15 (i386-redhat-linux-gnu) Copyright (C) 1995-2001
Schilling
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.5'
dvdrecord: Warning: using inofficial libscg transport code version
(schily-RH-sc
si-linux-sg.c-1.69-RH-O_EXCL '@(#)scsi-linux-sg.c 1.69 02/01/18
Copyright
1997 J. Schilling').
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'DVDRW '
Identifikation : 'IDE1008 '
Revision : '0052'
Device seems to be: Generic mmc2 DVD.
Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd).
Driver flags : SWABAUDIO BURNFREE
Supported modes: PACKET SAO
Starting to write CD/DVD at speed 2 in write mode for single session.
Last chance to quit, starting real write in 0 seconds. Operation
starts.
trackno=0
dvdrecord: Input/output error. write_g1: scsi sendcmd: no error
CDB: 2A 00 00 13 21 66 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 21 02 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x21 Qual 0x02 (logical block address out of range) [No
matching qua
lifier] Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.003s timeout 200s
write track data: error after 0 bytes
Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00
-- yucele@yahoo.com
[reply]
[top]
[»]
Re: Any ideas? Burn died with MagicSpin 8x Dvd-+r rw
by Jörg Schilling - Dec 23rd 2003 16:41:40
You are talking about an illegal branch from
cdrecord that violates the GPL
(GPL § 2 Paragraph c) and GPL Preamble Section 6).
Please don't blame the original version
with problems caused by illegal hacks.
If you like to write DVDs, use the official
cdrecord-ProDVD from ftp://ftp.berlios.de/pub/cdrecord/ProDVD
it is free for personal use and it is maintained
software....
[reply]
[top]
[»]
Re: Any ideas? Burn died with MagicSpin 8x Dvd-+r rw
by Chris Siegler - Jan 17th 2004 10:40:16
> You are talking about an illegal branch
> from
> cdrecord that violates the GPL
> (GPL § 2 Paragraph c) and GPL Preamble
> Section 6).
>
>
> Please don't blame the original version
> with problems caused by illegal hacks.
>
>
> If you like to write DVDs, use the
> official
> cdrecord-ProDVD from
> ftp://ftp.berlios.de/pub/cdrecord/ProDVD
> it is free for personal use and it is
> maintained
> software....
Try "growisofs" instead. It's free and works great.
DVD+RW/+R/-R[W] for
Linux
[reply]
[top]
[»]
Re: Any ideas? Burn died with MagicSpin 8x Dvd-+r rw
by maartenvs - Jun 17th 2004 06:35:01
> You are talking about an illegal branch
> from
> cdrecord that violates the GPL
> (GPL § 2 Paragraph c) and GPL Preamble
> Section 6).
the program doesn't read commands interactively. So how can this violate
GPL 2-c which only speaks of interactive programs?
[reply]
[top]
[»]
Re: Any ideas? Burn died with MagicSpin 8x Dvd-+r rw
by Jörg Schilling - Sep 8th 2004 03:34:00
> the program doesn't read commands
> interactively. So how can this violate
> GPL 2-c which only speaks of interactive
> programs?
You are wrong, read the source luke.....
[reply]
[top]
[»]
Re: Any ideas? Burn died with MagicSpin 8x Dvd-+r rw
by arys - Aug 23rd 2004 08:45:00
I find it particularly ironic that you would refer to a vendor-modified
version of cdrecord as violating the GPL, when by adding the following
clause, you yourself are violating it:
/*
* You are not allowed to modify or remove the following code.
* I am sorry that I am forced to do things like this, but defective
* versions of cdrecord cause a lot of work load to me and it seems
* to be impossible to otherwise convince SuSE to cooperate.
* As people contact me and bother me with the related problems,
* it is obvious that SuSE is violating subsection 6 in the preamble
of
* the GPL.
*
* Note that although the SuSE test is effective only for SuSE, the
* intention to have non bastardized versions out is not limited
* to SuSE. It is bad to see that in special in the "Linux" business,
* companies prefer a model with many proprietary differing programs
* instead of cooperating with the program authors.
*/
Under the GPL, that particular clause is simply not permitted. You've
already released it under the GPL, and if a distribution maker feels the
need to remove that code, they may feel free to do so. Don't complain about
violations of a license that you yourself don't even adhere to.
Or go ahead and try. If you do a fork will be created, and you'll very
likely be forgotten about entirely within a matter of a few weeks.
I think the real problem that you have is that SuSE is providing DVD
writing support for free, whereas you're attempting to make a commercial
profit from it. Thanks for providing the advertisement to your own product
by the way, that helps to solidify my point quite well.
> You are talking about an illegal branch
> from
> cdrecord that violates the GPL
> (GPL § 2 Paragraph c) and GPL Preamble
> Section 6).
>
>
> Please don't blame the original version
> with problems caused by illegal hacks.
>
>
> If you like to write DVDs, use the
> official
> cdrecord-ProDVD from
> ftp://ftp.berlios.de/pub/cdrecord/ProDVD
> it is free for personal use and it is
> maintained
> software....
[reply]
[top]
[»]
Re: Any ideas? Burn died with MagicSpin 8x Dvd-+r rw
by Jörg Schilling - Sep 8th 2004 03:37:45
You are wrong!
Cdredcord is accepted as free software
by Debian with no problems. Note that Debian
is the only left over Linux distribution that
did not go commercial. Debian is still is still
engaged to free software rules and not
to to the rules of the stock market like orthers...
[reply]
[top]
[»]
Re: Any ideas? Burn died with MagicSpin 8x Dvd-+r rw
by arys - Sep 8th 2004 12:09:42
I'm wrong, you say? I don't see any proof of that being offered. On the
other hand, I see that you've either mistakenly or purposefully referred to
the PREAMBLE of a license as being an actual condition of said license,
which it isn't.
Not raking in much cash from that commercial version, are you?
> You are wrong!
>
>
> Cdredcord is accepted as free software
> by Debian with no problems. Note that
> Debian
> is the only left over Linux distribution
> that
> did not go commercial. Debian is still
> is still
> engaged to free software rules and not
> to to the rules of the stock market like
> orthers...
>
[reply]
[top]
[»]
OSS DVD Extensions
by Robert M. Stockmann - Jun 20th 2003 20:16:45
Date: Mon, 16 Jun 2003 12:51:18 -0700 (PDT)
From: Robert M. Stockmann via RT
<news-admins@freshmeat.net>
To: Robert M.Stockmann <stock@stokkie.net>
Subject: [fm #28664] (news-admins)
Submission report - OSS DVD extensions
On Mon, 16 Jun 2003, Joel Williams via RT
wrote:
> The following notes are in response to your
recent freshmeat.net submission:
>
> - freshmeat prefers not to list patches whenever
possible. Have you contacted
> the authors of the main project about including
your patch in their code?
Hi,
Read
http://crashrecovery.org/oss-dvd/DISCLAIMER.html.
Joerg Schilling has emailed stating the following
:
"
Please note that all these patches will not work
with a recent version of cdrecord because the
creators do not really maintain them.
As I am constantly fixing bugs and adding new
features, there is a high propability that using
one of the programs above may give you far
worse results that with the original software.
"
Basicly Joerg states that the result after patching
won't be supported by him. Well thats quite
understandable. My experiences with the patch :
ftp://crashrecovery.org/pub/linux/cdrtools/cdrtools-2.0-dvd.patch.gz
which i created on 2 februari 2003, is that it does
a better job for me as e.g. the dvdrtools
package. Joerg's comment about the dvdrtools
package is this :
"
It is known not to work correctly! It definitely
breaks the official functionality and many
problems with drives different from Pioneer A03
have been reported.
"
I have created several RPMS and SRPM based
packages which include the
cdrtools-2.0-dvd.patch . See e.g.
http://crashrecovery.org/download-ossdvd.html
The reason i didn't publish it sofar on
fresmeat.net for a period of over 4 months, is
that i first wanted some test results, and people
emailing me about troubles. I'm quite convinced
now that my patch _and_ the offered RPM and
SRPM packages should be on freshmeat.net.
Regards,
Robert
--
Robert M. Stockmann - RHCE
Network Engineer - UNIX/Linux Specialist
crashrecovery.org stock@stokkie.net
[reply]
[top]
[»]
Re: OSS DVD Extensions
by Chris Siegler - Oct 15th 2003 22:47:56
The patch works great. I downloaded the SRPM and rebuilt it with
rpmbuild --rebuild and then installed the RPMs with --oldpackages
(since my current cdrtools packages were slightly newer builds). My Pioneer
DVR-105 wrote a iso image to a DVD-R with cdrecord dev=0,0,0
driveropts=burnfree speed=4 -dao image.iso without any problems.
Before using this patch I used the non-opensource version of cdrecord
called ProDVD but you have to install a "key" to make the free version
work, it's limited to 1X speed, and cannot be used for commercial work.
AFAIK it's also impossible to buy. Brilliant marketing!
[reply]
[top]
[»]
Re: OSS DVD Extensions
by Jörg Schilling - Sep 9th 2004 03:30:18
Please get yourself informed before writing
false claims.
cdrecord-ProDVD never has been limited in speed
for DVD writing. If cdrecord does not write
faster than 1x, then you either used speed=1
or your drive/media combination is not capable
of writing faster (which is a common problem).
Note that now that now that cdrtools-2.01 is out
the patch is extremely obsolete and does not
fit to the design of the original data structures
anymore.
[reply]
[top]
[»]
mkisofs > 2 GB files ?
by JCFrench - Jun 18th 2003 15:50:58
Hello,
I'm using cdrecord-prodvd to backup my files
on DVD, and I need to be able to backup files
that are larger than 2GB. Is this planned for the
future?
Thanks
[reply]
[top]
[»]
Re: mkisofs > 2 GB files ?
by jesterbl - Aug 12th 2003 17:23:18
My co-worker is copying 4GB size chunks to DVD for a HD image (i.e. it's
not sliced up). You can ask him about it if you need to, his name is Bret
and his email is: frederic|at|nosc(dot)mil
R/
Brian Jester
[reply]
[top]
[»]
Re: mkisofs > 2 GB files ?
by Holger Jakobs - Oct 3rd 2003 01:47:32
My version of mkisofs (2.0) has an option
-split-output
which produces serveral files of approx. 1 GB,
so no large file support is necessary for creating
bigger ISO images. cdrcord will concatenate
these automatically when writing the track.
Holger
-- --
Holger Jakobs, Bergisch Gladbach, Germany
[reply]
[top]
[»]
Yet another cdrecord problem
by avpet - Jun 18th 2003 12:55:48
Hi,
So in my case I use cdreccord 2.0 under cygwin and Win98 with TEAC W54E.
This device was listed as fully compatible with released versions of
cdrecord. And, it's a pity, I have this messages when burning image
previuosly read by cdrecord (note that I had upgraded my device firmaware
and have had the same result):
Read speed: 1764 kB/s (CD 10x, DVD 1x).
Write speed: 706 kB/s (CD 4x, DVD 0x).
Capacity: 1 Blocks = 2 kBytes = 0 MBytes = 0 prMB
Sectorsize: 2048 Bytes
Copy from file 'd:/cd1.raw' to SCSI (0,0,0) disk
end: 1
/cygdrive/c/WINDOWS/SYSTEM/READCD: I/O error. write_g0: scsi sendcmd:
retryable error
CDB: 0A 00 00 00 01 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 20 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x20 Qual 0x00 (invalid command operation code) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.000s timeout 40s
/cygdrive/c/WINDOWS/SYSTEM/READCD: I/O error. Cannot write destination
disk
Does this problem have any solution
[reply]
[top]
[»]
SCSI-USB
by khutmah - Jun 2nd 2003 18:31:42
Hi, I currently use a HP cd-writer 8200 series, external over USB.
After running 'cdrecord -scanbus' I get alisting of all my drives except
the recorder... what I'd like to know is if there will ever be support for
scsi-over-usb recorders.
Meanwhile I use cd-mate (www.cd-mate.com) which recognizes my
recorder...
Khut Mah
[reply]
[top]
[»]
Re: SCSI-USB
by Luis Freitas - Jul 5th 2003 08:12:27
I have used this same cd-writer model with success on USB on two different
machines.
You need a reasonably recent kernel, 2.2.22 or any 2.4.x will do. And you
need to install the USB storage device, as root, issue this command:
modprobe usb-storage
Also, on the machines I used, the kernel did not detect new USB devices
after the boot. So you might need to connect and power-up the cd-recorder
before you power-up the computer.
> Hi, I currently use a HP cd-writer 8200
> series, external over USB.
> After running 'cdrecord -scanbus' I get
> alisting of all my drives except the
> recorder... what I'd like to know is if
> there will ever be support for
> scsi-over-usb recorders.
> Meanwhile I use cd-mate
> (www.cd-mate.com) which recognizes my
> recorder...
>
> Khut Mah
[reply]
[top]
[»]
Re: SCSI-USB
by khutmah - Jul 18th 2003 17:52:34
HI, thanks for your response (although I took so long to answer) and for
the time taken. Anyway, your info isn't of much help because this recorder
is connected to a windows machine.
Thank you, once again.
Khut Mah
>
> I have used this same cd-writer model
> with success on USB on two different
> machines.
>
> You need a reasonably recent kernel,
> 2.2.22 or any 2.4.x will do. And you
> need to install the USB storage device,
> as root, issue this command:
>
> modprobe usb-storage
>
> Also, on the machines I used, the kernel
> did not detect new USB devices after the
> boot. So you might need to connect and
> power-up the cd-recorder before you
> power-up the computer.
>
>
> % Hi, I currently use a HP cd-writer
> 8200
> % series, external over USB.
> % After running 'cdrecord -scanbus' I
> get
> % alisting of all my drives except the
> % recorder... what I'd like to know is
> if
> % there will ever be support for
> % scsi-over-usb recorders.
> % Meanwhile I use cd-mate
> % (www.cd-mate.com) which recognizes my
> % recorder...
> %
> % Khut Mah
[reply]
[top]
[»]
cdreccord problem
by xinos03 - May 22nd 2003 12:48:53
Hi,
I use cdreccord 2.0 with my liteon LTR 48125S.
But I have this messages when I try to burn :
cdrecord: Input/output error. write_g1: scsi sendcmd: no error
CDB: 2A 00 00 00 05 16 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 04 00 00 00 00 0A 00 00 00 00 08 03 00 00
Sense Key: 0x4 Hardware Error, Segment 0
Sense Code: 0x08 Qual 0x03 (logical unit communication crc error
(ultra-dma/32)) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.033s timeout 200s
Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00
write track data: error after 2666496 bytes
Can anyone have a solution
[reply]
[top]
[»]
CDrecord is a Great Program Except...
by CrazyDuke - Apr 23rd 2003 19:22:11
I really appriciate this program, and I have not had any
problems with it until now. I have been playing with
linux distro's on different machines and really got to
like this program with varius front end programs. It
worked, it didn't piss and moan about not having a
specific definintion for CD-R drives in aspi drivers like
windows.
So, I finally took the plunge, swiched to a linux based
OS, and used your program on my new computer.
. . . And I can't get it to burn more than a few hundred
kilobytes.
Played with the settings; tinkered with different front
ends; and tried manually using cdrecord from bash.
I've tried different speeds, dummy on and off, etc...
All I get is this:
Last chance to quit, starting dummy write 0 seconds.
Operation starts.
Waiting for reader process to fill input buffer ... input
buffer ready.
BURN-Free is ON.
Turning BURN-Free off
Starting new track at sector: 0
Track 01: 1 of 148 MB written (fifo 89%) [buf 66%]
8.2x.cdrecord: Input/
output error. write_g1: scsi sendcmd: no error
CDB: 2A 00 00 00 03 07 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 71 00 05 00 00 00 00 0A 00 00 00 00 21
02 00 00
Sense Key: 0x5 Illegal Request, deferred error,
Segment 0
Sense Code: 0x21 Qual 0x02 (invalid address for
write) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.002s timeout 40s
write track data: error after 1587200 bytes
Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00
00 00 00 00 00
Writing time: 6.870s
Average write speed 147.9x.
Fixating...
WARNING: Some drives don't like fixation in dummy
mode.
Fixating time: 0.001s
cdrecord: fifo had 89 puts and 26 gets.
cdrecord: fifo was 0 times empty and 3 times full, min
fill was 84%.
[reply]
[top]
[»]
Re: CDrecord is a Great Program Except...
by Raven Morris - Aug 28th 2003 20:30:55
> I really appriciate this program, and I
> have not had any
> problems with it until now. I have been
> playing with
> linux distro's on different machines and
> really got to
> like this program with varius front end
> programs. It
> worked, it didn't piss and moan about
> not having a
> specific definintion for CD-R drives in
> aspi drivers like
> windows.
>
> So, I finally took the plunge, swiched
> to a linux based
> OS, and used your program on my new
> computer.
>
> . . . And I can't get it to burn more
> than a few hundred
> kilobytes.
>
> Played with the settings; tinkered with
> different front
> ends; and tried manually using cdrecord
> from bash.
>
> I've tried different speeds, dummy on
> and off, etc...
>
> All I get is this:
> Last chance to quit, starting dummy
> write 0 seconds.
> Operation starts.
> Waiting for reader process to fill input
> buffer ... input
> buffer ready.
> BURN-Free is ON.
> Turning BURN-Free off
> Starting new track at sector: 0
> Track 01: 1 of 148 MB written (fifo
> 89%) [buf 66%]
> 8.2x.cdrecord: Input/
> output error. write_g1: scsi sendcmd: no
> error
> CDB: 2A 00 00 00 03 07 00 00 1F 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 71 00 05 00 00 00 00 0A 00
> 00 00 00 21
> 02 00 00
> Sense Key: 0x5 Illegal Request, deferred
> error,
> Segment 0
> Sense Code: 0x21 Qual 0x02 (invalid
> address for
> write) Fru 0x0
> Sense flags: Blk 0 (not valid)
> cmd finished after 0.002s timeout 40s
>
> write track data: error after 1587200
> bytes
> Sense Bytes: 70 00 00 00 00 00 00 0A 00
> 00 00 00 00
> 00 00 00 00 00
> Writing time: 6.870s
> Average write speed 147.9x.
> Fixating...
> WARNING: Some drives don't like fixation
> in dummy
> mode.
> Fixating time: 0.001s
> cdrecord: fifo had 89 puts and 26 gets.
> cdrecord: fifo was 0 times empty and 3
> times full, min
> fill was 84%.
>
I have used cdrtools for years now, but it just started giving me that
error above. I am going to try upgrading cdrtools and other software
related, and see if it stops doing it.
- raven morris
-- "Time flies like an arrow. Fruit flies like a banana." -- Groucho Marx
[reply]
|