>From [EMAIL PROTECTED] Thu Mar 22 18:27:24 2001
>> Why don't you use a recent version?
>I am using 1.10a17, as I say in the Subject and in the body several
>times. I only mentioned AN-1.10a04 because it had the comment about
>the broken Iomega firmware.
>Where should I get a later version than 1.10a17 ?
1.10a17 is the latest version an I see no reason why there should
be any problem (see below).
...
>> But no more SCSI standard compliant!
>Well, indeed. I'd really like to help produce a better patch.
>If you don't want me to help with this, then fine, I'll go away.
Well I like to be as standard compliant as possible.
If it works in a standard compliant way, then there is no need for a hack...
>I currently have a combination of solutions that work for me (using
>cdrdao to do writes, and cdrecord with my hacky patch to blank CDRWs).
>If you don't want my help to improve the hardware compatibility of
>cdrecord for everyone else then I shan't bother wasting any more of my
>time.
It id definitely a cdrecord topic. From my tests it seems to be mainly
a Linux USB problem.
Last year, I made some tests with the IOMEGA USB drive with a
plain PC of a collegue ....
It dis not work very well so far because there have been problems
after the DMA overrun detection.
Some weks ago, I made tests with my Sony VAIO Transmeta motebook
and it turns out, that it does not work at all if you boot with
the drive connected or if you enable enhanced debugging.
However, if you carefully wait until everything is quiet, then plug in
the drive and start to use it via cdrecord there is absolutely
no problem! No hangs - only a one to two second delay when
detecting the DMA overrun at the beginning.
>Several people on the Linux USB device compatibility list have
>apparently had some problems with various versions of cdrecord 1.10a06
>or later. Unfortunately their reports were rather vague and
>unhelpful, but it's not at all clear that the current version is fully
>compatible.
As you see from my notes, it is clear to me that people have problems
to give more than vague infos about their problems.
>Perhaps there is a timing problem or something.
>PS: I'm slightly frustrated that the effort I went to to produce a
>good bug report according to your instructions, with all the vital
>information first, etc., seems to have been wasted.
Sory, but many things changeed during the last versions and I have absoutely
no time to check reports that are not based on the latest cdrtools
release.
In addition, you may want to run the scgckeck program to see whether
other than the known Linux SCSI problems are present on
your machine.
J�rg
EMail:[EMAIL PROTECTED] (home) J�rg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni) If you don't have iso-8859-1
[EMAIL PROTECTED] (work) chars I am J"org Schilling
URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
