I've also had success with version 2.00.3
Just to be clear, all the versions except the one currently in sid were compiled from sources (make && make install) downloaded from here:
ftp://ftp.berlios.de/pub/cdrecord/
I think that covers everything.
-Garrett
--- Begin Message ---Hi again!
I have a CyberDrive CW058D. It works perfectly in WinXP and 2.4 with SCSI emulation. I've also found that it works perfectly when I run
#cdrecord dev=/dev/hdc image .iso
under cdrecord version 2.00 and kernel 2.6.10 (no SCSI emulation). When I try it with 2.01 (even the non-alpha 2.01), it hangs up and is totally unkillable. The drive doesn't look or sound like it's doing anything, so I know it's stuck in some kind of loop similar to the one Alan Chandler was talking about above. However, I've found consistent sucess with version 2.00. Therefore perhaps there is something in the transition from 2.00 -> 2.01 that causes the breakage with CyberDrive units? I guess a good first step would be to check out the differences between 2.00 and 2.01...unfortunately I am not a hacker. I so wish I knew C right now....
I've tested on the following versions of cdrecord:
-The one currently in sid (Version: 4:2.01+01a01-2) <not successful> -The one in cdrtools-2.00 (compiled from source) <successful> -The one in cdrtools-2.01 (compiled from source) <not successful>
FYI, info about my system from reportbug:
-- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages cdrecord depends on:
ii debconf 1.4.42 Debian configuration management sy
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii makedev 2.3.1-75 Creates device files in /dev
-- debconf information: * cdrecord/SUID_bit: true //Yes, but I always tested as root cdrecord/MAKEDEVNEW: true cdrecord/do_it_yourself:
-Garrett
--- End Message ---
