Testing Unsigned Drivers

Here’s the setup:

We had a legacy driver that would claim SCSI devices: cd-roms, changers,
disks, whatever. Whichever ones were going to be managed by our service
would be claimed by our driver so that nobody else would talk to it.

We are working on converting this to a PNP driver. In theory, this PNP
driver will get called when a device comes online and we will decide if we
want to attach to the device or not. If we don’t, then SCSIDISK should
take. The end result could be, e.g., a library with 6 drives where we’ve
taken the 3 we want and SCSIDISK has the other 3.

The problem I’m running into now is that this isn’t a class specific
driver, it’s an encompassing driver like SCSIDISK, that handles multiple
storage classes. So during bootup, given the choice between SCSIDISK and
my driver, Windows will pick SCSIDISK, because it’s signed and mine isn’t.
My driver won’t even get called. I can test my driver to some extent by
setting it up as a more specific driver, but how can I fully test this
type of driver without a signature?

You either have to implement class lower filter drivers for all scsi
classes (disk, tape, cdrom etc,) or a scsi adapter bus filter driver. I
prefer the bus filter driver approach, microsoft prefers that you didn’t
implement bus filter drivers, but they do not provide an alternative for
your situation.

===========================
Mark Roddy
Consultant, Microsoft DDK MVP
Hollis Technology Solutions
xxxxx@hollistech.com
www.hollistech.com
603-321-1032

-----Original Message-----
From: xxxxx@otg.com
To: “NT Developers Interest List”
Date: Tue, 10 Sep 2002 16:11:18 -0400
Subject: [ntdev] Testing Unsigned Drivers

> Here’s the setup:
>
> We had a legacy driver that would claim SCSI devices: cd-roms,
> changers,
> disks, whatever. Whichever ones were going to be managed by our
> service
> would be claimed by our driver so that nobody else would talk to it.
>
> We are working on converting this to a PNP driver. In theory, this PNP
> driver will get called when a device comes online and we will decide if
> we
> want to attach to the device or not. If we don’t, then SCSIDISK should
> take. The end result could be, e.g., a library with 6 drives where
> we’ve
> taken the 3 we want and SCSIDISK has the other 3.
>
> The problem I’m running into now is that this isn’t a class specific
> driver, it’s an encompassing driver like SCSIDISK, that handles
> multiple
> storage classes. So during bootup, given the choice between SCSIDISK
> and
> my driver, Windows will pick SCSIDISK, because it’s signed and mine
> isn’t.
> My driver won’t even get called. I can test my driver to some extent
> by
> setting it up as a more specific driver, but how can I fully test this
> type of driver without a signature?
>
> —
> You are currently subscribed to ntdev as: xxxxx@hollistech.com
> To unsubscribe send a blank email to %%email.unsub%%