Re: wfd.c and ATAPI Zip

1999-06-07 Thread Soren Schmidt
It seems Chris D. Faulhaber wrote: > > I have an off-brand (NEC) Zip Drive with: > > which does have buggy firmware; I also have another one with: > > that has no problem when I remove the 64 block limitation. > > In this case, I would use strncmp instead of strcmp to test the first 2

Re: wfd.c and ATAPI Zip

1999-06-07 Thread Mike Smith
> On Mon, 7 Jun 1999, Mike Smith wrote: > > > > 12.A, 21.*, and 23.* are known to be buggy...13.A doesn't appear to be. > > > Since the current method of sorting out the revisions doesn't seem to > > > be perfect, would it be acceptible to consider them all buggy unless known > > > not to be (i.e

Re: wfd.c and ATAPI Zip

1999-06-07 Thread Chris D. Faulhaber
On Mon, 7 Jun 1999, Mike Smith wrote: > > 12.A, 21.*, and 23.* are known to be buggy...13.A doesn't appear to be. > > Since the current method of sorting out the revisions doesn't seem to > > be perfect, would it be acceptible to consider them all buggy unless known > > not to be (i.e. compare ap

Re: wfd.c and ATAPI Zip

1999-06-07 Thread Mike Smith
> On Tue, 8 Jun 1999, Junichi Satoh wrote: > > > Hmm... > > > > I have an ATAPI ZIP drive: > > > > wdc0: unit 1 (atapi): , removable, intr, > > iordis > > wfd1: medium type unknown (no disk) > > wfd1: buggy Zip drive, 64-bl

Re: wfd.c and ATAPI Zip

1999-06-07 Thread Chris D. Faulhaber
Here is a patch that checks for the revision numbers instead of simply the inquiry string (and adds my buggy revision): --- wfd.c.orig Thu Feb 18 17:06:08 1999 +++ wfd.c Mon Jun 7 12:02:25 1999 @@ -243,17 +243,21 @@ return -1; /* -* The IOMEGA ZIP 100, at f

Re: wfd.c and ATAPI Zip

1999-06-07 Thread Chris D. Faulhaber
On Tue, 8 Jun 1999, Junichi Satoh wrote: > Hmm... > > I have an ATAPI ZIP drive: > > wdc0: unit 1 (atapi): , removable, intr, > iordis > wfd1: medium type unknown (no disk) > wfd1: buggy Zip drive, 64-block transfer limit s

Re: wfd.c and ATAPI Zip

1999-06-07 Thread Junichi Satoh
>> My thoughts now are: >> 1) My two drive are somewhat 'rogue' in that they don't conform to the >> driver's expectations. >> 2) When the driver was written, the '!strcmp' should be 'strcmp' since >> strcmp returns 0 when equal (-1 or 1 when < or >), in which case my patch >> makes sense: >> >>

wfd.c and ATAPI Zip

1999-06-06 Thread Chris D. Faulhaber
I have two boxes with ATAPI Zip Drives: Box1: wdc1: unit 1 (atapi): , removable, intr, iordis wfd0: medium type unknown (no disk) Box2: wdc1: unit 0 (atapi): , removable, intr, iordis wfd0: medium type unknown (no disk) wfd0: buggy Zip drive, 64-block transfer limit set The drive on Box1 gets ti