Hi
I’m posting this question again after several tries.
I’m trying to write a ScsiPort driver for NT V4.
I named the new driver ScsiPortX where X is the incremented number of the
largest existing ScsiPort#. The number was taken as suggested (and thanks
for the help) from the field ScsiPortCount in CONFIGURATION_INFORMATION,
afterward the ScsiPortCount in the CONFIGURATION_INFORMATION was
incremented.
I start the ScsiPortX after the system was loaded and the disk class has
claimed all disk devices. The problem is that when I start the disk
administrator, the scsi class does not contact the new ScsiPort driver.
For a better understating and comparing, I wrote a dummy miniport scsi
driver. When I repeated the same scenario with the miniport, the disk class
contacted the miniport and the disk administrator presented the dummy disks
devices.
As a another try, I repeated the scenario with both drivers. When the
miniport was loaded before the new ScsiPort, the disk scsi class seemed to
“notice” them both. The disk administrator presents the disk devices from
both drivers.
When I tried loading first the ScsiPort and then the miniport, the disk
class did not make any contact with either of them.
Any idea what I miss in the implementation of the ScsiPort ?
Thanks
Miki
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com