Ok, now I’m tackling the fun of .inf file writing, and I can’t quite
seem to get it right.
My driver is a non-PNP SCSI miniport for a “virtual” HBA. For those of
you who have read my other recent posts, you know the details…
The problem has got to be either A: a problem with my .inf, or B: a
problem with how I’m going about installing the driver.
Since the device is not PNP, I’m not sure quite what to put for the
hw-id parameter on the line in the INF file’s models section. Since
it’s a required parameter, I just put *. If there’s a
more appropriate hw-id for a non-PNP miniport driver, please let me
know.
The problem I get is that the driver ends up with two devnodes in the
ENUM tree in the registry. One that gets installed when I do the
installation, and another that comes along following the next reboot.
The first one ends at key under ENUM\Root\SCSIADAPTER\0000. I believe
that’s the one I want. But then I get the second one at key
ENUM\Root<mydrivername>\0000. Both have entries underneath those keys
referencing my driver. Once the second one comes into existence, one of
them obviously always fails to load, and thus I get an entry in the
device manager for one of the two instances that has the dreaded yellow
“!” indicating an error.
Whichever instance loads successfully works to communicate with my
device, which is why I’ve put off fixing the .inf file issue until now.
I install the driver by going to the control panel, selecting Add New
Hardware, and going through the steps to add a new device. Since this
is a non-PNP device, I have to tell it to manually add a new device of
type “SCSI and RAID controllers”, and then I select “Have Disk” and put
in a floppy with the files. I presume this is the appropriate
procedure for a non-PNP device.
Anybody have any hints, ideas, suggestions?
Thanks,
- Jay
Jay Talbott
Principal Consulting Engineer
SysPro Consulting, LLC
3519 E. South Fork Drive
Suite 201
Phoenix, AZ 85044
(480) 704-8045
xxxxx@sysproconsulting.com
http://www.sysproconsulting.com
—
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
Hi Jay,
You can just add the key to the \services and your driver will work fine.
Except you’ll see just “SCSI/RAID Controller” instead of “Joy’s Talbot
VSCSI”.
If this is not a problem for you you can skip .inf at all.
If this is a problem I can send you own .inf I use for installing SCSI
miniports.
Did you implement own SRB completion with my code?
Regards,
Anton
On 01/13/02, ““Jay Talbott” ” wrote:
> Ok, now I’m tackling the fun of .inf file writing, and I can’t quite
> seem to get it right.
>
> My driver is a non-PNP SCSI miniport for a “virtual” HBA. For those of
> you who have read my other recent posts, you know the details…
>
> The problem has got to be either A: a problem with my .inf, or B: a
> problem with how I’m going about installing the driver.
>
> Since the device is not PNP, I’m not sure quite what to put for the
> hw-id parameter on the line in the INF file’s models section. Since
> it’s a required parameter, I just put *. If there’s a
> more appropriate hw-id for a non-PNP miniport driver, please let me
> know.
>
> The problem I get is that the driver ends up with two devnodes in the
> ENUM tree in the registry. One that gets installed when I do the
> installation, and another that comes along following the next reboot.
> The first one ends at key under ENUM\Root\SCSIADAPTER\0000. I believe
> that’s the one I want. But then I get the second one at key
> ENUM\Root<mydrivername>\0000. Both have entries underneath those keys
> referencing my driver. Once the second one comes into existence, one of
> them obviously always fails to load, and thus I get an entry in the
> device manager for one of the two instances that has the dreaded yellow
> “!” indicating an error.
>
> Whichever instance loads successfully works to communicate with my
> device, which is why I’ve put off fixing the .inf file issue until now.
>
> I install the driver by going to the control panel, selecting Add New
> Hardware, and going through the steps to add a new device. Since this
> is a non-PNP device, I have to tell it to manually add a new device of
> type “SCSI and RAID controllers”, and then I select “Have Disk” and put
> in a floppy with the files. I presume this is the appropriate
> procedure for a non-PNP device.
>
> Anybody have any hints, ideas, suggestions?
>
> Thanks,
>
> - Jay
>
> Jay Talbott
> Principal Consulting Engineer
> SysPro Consulting, LLC
> 3519 E. South Fork Drive
> Suite 201
> Phoenix, AZ 85044
> (480) 704-8045
> xxxxx@sysproconsulting.com
> http://www.sysproconsulting.com
>
>
> —
> 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
—
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