Recap: 1GB external Jaz drive which works OK with Adaptec
controller on PC and beautifully with onboard controller
in a Sun IPX goes nuts when talking to the onboard ncr
controller on an Alphastation 200.

Data point: 

ncr0 at pci0 dev 6 function 0: ncr 53c810 fast10 scsi
ncr0: interrupting at isa irq 11
ncr0: minsync=25, maxsync=206, maxoffs=8, 16 dwords burst, normal dma fifo
ncr0: single-ended, open drain IRQ driver
ncr0: restart (scsi reset).
scsibus0 at ncr0: 8 targets
sd0 at scsibus0 targ 3 lun 0: <SEAGATE, ST15230W SUN4.2G, 0738> SCSI2 0/direct fixed
sd0(ncr0:3:0): 10.0 MB/s (100 ns, offset 8)
sd0: 4095MB, 3992 cyl, 19 head, 110 sec, 512 bytes/sect x 8386733 sectors
root on sd0a dumps on sd0b

This configuration works just fine.

It's not terribly important, but why do the Jaz and ncr
devices hate each other so much?

> sd0 at scsibus0 targ 5 lun 0: <iomega, jaz 1GB, H.71> SCSI2 0/direct removable
> sd0(ncr0:5:0): 10.0 MB/s (100 ns, offset 8)
> ncr0: aborting job ...
> ncr0:5: ERROR (90:0) (0-22-0) (8/13) @ (script 1c4:900b0000).
> ncr0: script cmd = 910a0000
> ncr0: regdump: da 10 80 13 47 08 05 1f 01 08 02 2a 80 00 02 00.
> ncr0: restart (fatal error).

...

	Sean.