Can a NT legacy driver be a bus driver in Win2k

NTDEV
1

Can a NT legacy style driver be a bus driver in Win2k? I think the answer
is no because everytime I go to use IoInvalidateDeviceRelations it wants
the PDO of the enumerating driver(BLUE SCREEN w/PNP_FATAL_ERROR). My
problem is that the legacy driver does not have a PDO associated with it.
Is there anyway to get around this, or is this just how it is? You have to
be a WDM driver to be bus driver.

2

Just create a root enumerated pdo device for your ‘legacy’ driver to use as
the pnp stack for bus enumeration.

Mark Roddy
Windows 2000/NT Consultant
Hollis Technology Solutions
www.hollistech.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of
xxxxx@east.sun.com
Sent: Wednesday, June 28, 2000 12:00 AM
To: NT Developers Interest List
Subject: [ntdev] Can a NT legacy driver be a bus driver in Win2k

Can a NT legacy style driver be a bus driver in Win2k? I think the answer
is no because everytime I go to use IoInvalidateDeviceRelations it wants
the PDO of the enumerating driver(BLUE SCREEN w/PNP_FATAL_ERROR). My
problem is that the legacy driver does not have a PDO associated with it.
Is there anyway to get around this, or is this just how it is? You have to
be a WDM driver to be bus driver.

You are currently subscribed to ntdev as: xxxxx@wattanuck.mv.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

3

> Is there anyway to get around this, or is this just how it is? You have to

be a WDM driver to be bus driver.

Surely yes - the bus driver must handle all of the PnP IRPs to its PDOs, and
NT4 driver knows nothing on PnP IRPs.

Max