On Fri, 5 May 2000, Pat LaVarre wrote:
> > ... Zip 250s die if you send a command to a LUN other than 0.
> > I don't know why, but they just refuse to take a command or
> > return status after the first non-zero LUN command. Zip 100s
> > seem to have no problem with this ...
>
> Truly?
>
> I'm inclined to think that absolute any device response is compliant -
> but that provoking such a response makes the host in question
> non-compliant.
Yes, any response would be good. However, as far as I can tell, the
device crashes -- no commands are accepted, no status is transferred.
> To let the device do what it pleases, I'd quote BBB 6.2.2 "The device
> shall consider the contents of a valid CBW meaningful when ... the
> bCBWLUN contains a valid LUN supported by the device" and 6.4 "The
> response of a device to a CBW that is not meaningful is not
> specified."
Yes. However, a subsequent command to a valid LUN should work according
to this, and they don't.
> I've been told that idProduct x0001 Zip 100 respond to invalid LUN
> with some obsolete bCSWStatus value. I've been told that Zip 250 and
> later Zip 100 respond to invalid LUN as if a phase error had occurred
> i.e. require a BBB 5.3.4 Reset Recovery to continue.
Hrm, I didn't see a CSW returned at all.
Matt Dharm
--
Matthew Dharm Home: [EMAIL PROTECTED]
Senior Engineer, QCP Inc. Work: [EMAIL PROTECTED]
It was a new hope.
-- Dust Puppy
User Friendly, 12/25/1998
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
