C
Chris Tate
Hi,
I have a SCSI subsystem that communicates with a Windows XPe as a SCSI
"processor device". When XPe boots, it finds my target as a disk drive and
I have determined with the use of a SCSI analyzer that XPe sends numerous
drive specific SCSI commands to it even though it is returning "processor
device" and not a "direct access device" (hard drive). Why does this
happen, and how can it be prevented?
As for specifics on my system, my target uses a Qlogic FAS366U SCSI
controller which will be set to 16-bit async mode in normal operation. The
SBC uses a Symbios SYM53C895 host bus controller. This problem does not
occur if I use Windows 98SE as the OS.
Thanks,
-Chris
I
I have a SCSI subsystem that communicates with a Windows XPe as a SCSI
"processor device". When XPe boots, it finds my target as a disk drive and
I have determined with the use of a SCSI analyzer that XPe sends numerous
drive specific SCSI commands to it even though it is returning "processor
device" and not a "direct access device" (hard drive). Why does this
happen, and how can it be prevented?
As for specifics on my system, my target uses a Qlogic FAS366U SCSI
controller which will be set to 16-bit async mode in normal operation. The
SBC uses a Symbios SYM53C895 host bus controller. This problem does not
occur if I use Windows 98SE as the OS.
Thanks,
-Chris
I