porting WDM driver to NT4

NTDEV
1

Hi. I’m curious as to what it would take to port a Windows 2000 WDM
driver over to NT4 ? At the very least the INF files need to be
different, you’ve got to probe the resources yourself since there’s no PnP
manager, etc.

I’m looking for a high level description and a gross approximation RE how
much of the code might be re-usable, etc. I’m not familiar with
developing non-WDM drivers.

My apologies if I am lacking in detail. I am just trying to get an
initial high-level assement as to where the changes are (PnP, …).

Regards,
Tommy

2

What type of device are you backporting? In what device class does it
operate in on win2k?

D

This posting is provided “AS IS” with no warranties, and confers no
rights

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of M.Tam
Sent: Wednesday, August 06, 2003 9:09 AM
To: Windows System Software Developers Interest List
Subject: [ntdev] porting WDM driver to NT4

Hi. I’m curious as to what it would take to port a Windows 2000 WDM
driver over to NT4 ? At the very least the INF files need to be
different, you’ve got to probe the resources yourself since there’s no
PnP
manager, etc.

I’m looking for a high level description and a gross approximation RE
how
much of the code might be re-usable, etc. I’m not familiar with
developing non-WDM drivers.

My apologies if I am lacking in detail. I am just trying to get an
initial high-level assement as to where the changes are (PnP, …).

Regards,
Tommy

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

Typically you have to dump PnP and Power management. Many times those are in
separate files and you might be able to simply remove them from the build
list. You will also need to dump AddDevice from DriverEntry.

Hmmm … second thought … you may only need to set you INF up as a legacy
driver and do a test in DriverEntry to parse you’re resources if you are
loaded under NT. This means you will carry all that PnP and Power management
code but it will never be called since you are loaded as a legacy driver.
That’s a quick and dirty way of doing things, but it is a start.

–
Gary G. Little
Seagate Technologies, LLC
xxxxx@seagate.com

“M.Tam” wrote in message news:xxxxx@ntdev…
>
> Hi. I’m curious as to what it would take to port a Windows 2000 WDM
> driver over to NT4 ? At the very least the INF files need to be
> different, you’ve got to probe the resources yourself since there’s no PnP
> manager, etc.
>
> I’m looking for a high level description and a gross approximation RE how
> much of the code might be re-usable, etc. I’m not familiar with
> developing non-WDM drivers.
>
> My apologies if I am lacking in detail. I am just trying to get an
> initial high-level assement as to where the changes are (PnP, …).
>
> Regards,
> Tommy
>
>

4

What s the device type?

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com]
On Behalf Of M.Tam
Sent: Wednesday, August 06, 2003 9:09 AM
To: Windows System Software Developers Interest List
Subject: [ntdev] porting WDM driver to NT4

Hi. I’m curious as to what it would take to port a Windows 2000 WDM
driver over to NT4 ? At the very least the INF files need to be
different, you’ve got to probe the resources yourself since there’s no PnP
manager, etc.

I’m looking for a high level description and a gross approximation RE how
much of the code might be re-usable, etc. I’m not familiar with
developing non-WDM drivers.

My apologies if I am lacking in detail. I am just trying to get an
initial high-level assement as to where the changes are (PnP, …).

Regards,
Tommy

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@storagecraft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

5

As was said you will have to get rid of:
(1) AddDevice
(2) IRP_MJ_PNP
(3) IRP_MJ_POWER
(4) IRP_MJ_SYSTEM_CONTROL handling as in the W2K driver

You will have to the functions of AddDevice from with DriverEntry and you
will will have to use Halxxx calls to get your resources.

6

Okay thanks to both you and Gary for the quick and dirty summary. Hope
that gives me rough starting point.

In response to a question, the device is a multifunction device (three
child devices). The child devices are FILE_DEVICE_UNKNOWN .

Tommy

As was said you will have to get rid of:
(1) AddDevice
(2) IRP_MJ_PNP
(3) IRP_MJ_POWER
(4) IRP_MJ_SYSTEM_CONTROL handling as in the W2K driver

You will have to the functions of AddDevice from with DriverEntry and you
will will have to use Halxxx calls to get your resources.

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@tamfamily.com
To unsubscribe send a blank email to xxxxx@lists.osr.com