Please note, that wrong parameters can cause the scanner to hang in a way
that is locking up the SCSI bus really weird.
For the NCR53c400 card that came with mine, this seems to be a really
hard lockup. I have to power-cycle the scanner _AND_ reboot the machine
if this happens rmmod/insmod of the SCSI driver does _not_ do the job.
Only rebooting without power-cycling the scanner results in a system lockup
at the moment the SCSI driver is loaded.
I suppose with a better SCSI adapter the reboot might not be needed, but I
assume the scanner still would need to be power-cycled.
Thus if you want to do remote debugging, it might be advisable to take care
that someone is present, so he can power-cycle the scanner if necessary.
I would be willing to give you access at negotiated times (dialup-line, but
ISDN 64kBit), but I suppose it won't help much, as I have FW 1.00 which seems
to work using my "alternate-correction" hack.
Maybe people should try mscan and muscan for comparision, as I have never
heard complaints about those. If these work, we might be able to draw
conclusions from that.
CU,ANdy
-- = Andreas Beck | Email : <andreas.beck@ggi-project.org> =
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com