Tech Support > Microsoft Windows > Drivers > Re: device installation
Re: device installation
Posted by Don Burn on March 1st, 2004


The service calls only work for legacy NT 4.0 style drivers, if that is what
you are installing go for it. Otherwise use the DDK information, and get
the newest DDK and look at the DevCon source.

--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

"Ellen" <anonymous@discussions.microsoft.com> wrote in message
news:523AB59E-5044-470E-BB92-73C0554D30BE@microsoft.com...
I found they directly call service functions like CreateService,
StartService, etc to load drivers.


Posted by Alex on March 2nd, 2004


What if your driver isn't controlling a device, for example drivers like the
one used in the systeminternals tools; For a driver like this you are
supposed to use the Services API, right?

"Don Burn" <burn@stopspam.acm.org> wrote in message
news:10475u43iahsrf8@corp.supernews.com...


Posted by James Antognini [MSFT] on March 2nd, 2004


There's a whole set of drivers having to do with filtering. Many, if not
most, of these are best set up using DevCon or the APIs it invokes.

--
James Antognini
Windows DDK Support

This posting is provided "AS IS" with no warranties, and confers no rights.

"Alex" <AlX@a> wrote in message
news:%23EgfGz%23$DHA.4012@tk2msftngp13.phx.gbl...


Posted by Alex on March 2nd, 2004


"James Antognini [MSFT]" <jantogni@online.microsoft.com> wrote in message
news:%23Tx1AB$$DHA.1792@TK2MSFTNGP12.phx.gbl...
Why is this prefered to the Services API?



Posted by David J. Craig on March 2nd, 2004


PnP applies to ALL drivers in Windows 2000 and later. The old stuff
will work, but will disable any power management, which is less than
desirable in notebooks. When you have a legacy device type driver with
no real hardware it will be placed on the 'root' PDO just like there was
a magic piece of hardware. You can then receive and handle the various
power and PnP requests. You can even have your device driver create
PDOs that cause other drivers to load as needed and there is still no
hardware. Try reading and understanding the Toaster example. It isn't
simple, but this stuff isn't simple. Eliyas Yakub has created a very
complex example to show how to do almost anything. Taking each piece
one at a time will make it easier to understand, but if you build every
piece and try to use them all at once, you will just get a really big
headache.

"Alex" <AlX@a> wrote in message
news:%23EgfGz%23$DHA.4012@tk2msftngp13.phx.gbl...


Posted by James Antognini [MSFT] on March 2nd, 2004


In many cases the filtering is being done against a device that is PnP, so
these APIs are the way to go. You'd have to work a lot harder to get the
same effect with a legacy driver (which is what a driver loaded by a service
is), and it would be liable to break things.

The common reason not to use these APIs and to use a legacy approach is that
one doesn't understand the WDM model. The WDM or PnP model is,
unfortunately, rather complicated in places, but it's better to come to
understand it as quickly and thoroughly as possible.

--
James Antognini
Windows DDK Support

This posting is provided "AS IS" with no warranties, and confers no rights.

"Alex" <AlX@a> wrote in message news:ujtqzH$$DHA.916@tk2msftngp13.phx.gbl...



Similar Posts