I am having the code for a kernal mode system callpaths tracker for windows
2000 .
I need to port the driver to Win NT . So where to start with ? I had install
both
the DDK kits for NT and XP.What are the major changes to be incorporated
with the
driver to make it compatible with NT.I know that 2000 driver is WDM
compatible
does it mean only the recompilation of the code with NT ddk is needed for
porting ?
****************************************************************************
This communication contains information, which is confidential and may also
be privileged. It is for the exclusive use of the intended recipient(s). If
you are not the intended recipient(s), please note that any distribution,
printing, copying or use of this communication or the information in it is
strictly prohibited. If you have received this communication in error,
please notify the sender immediately and then destroy any copies of it.
****************************************************************************
> I know that 2000 driver is WDM compatible
does it mean only the recompilation of the code with NT ddk is needed for porting ?
NO.
To startwith, In WDM drivers you have AddDevice and DriverEntry.
In NT drivers you have only DriverEntry in which you need to keep track of
per instance specifics..
My suggestion is to read "Writing Windows NT Drivers" by Peter Viscarola & Anthony Mason
before you start doing this porting.
HTH.
-Vijay
----- Original Message -----
From: Prasad R
To: Windows System Software Developers Interest List
Sent: Thursday, July 24, 2003 11:02 AM
Subject: [ntdev] Dbt regarding porting
I am having the code for a kernal mode system callpaths tracker for windows 2000 .
I need to port the driver to Win NT . So where to start with ? I had install both
the DDK kits for NT and XP.What are the major changes to be incorporated with the
driver to make it compatible with NT.I know that 2000 driver is WDM compatible
does it mean only the recompilation of the code with NT ddk is needed for porting ?
You are currently subscribed to ntdev as: xxxxx@moschip.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
**************************************************************************** This communication contains information, which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, printing, copying or use of this communication or the information in it is strictly prohibited. If you have received this communication in error, please notify the sender immediately and then destroy any copies of it. ****************************************************************************
As noted, AddDevice, and its purpose, exist only in Win2K and later.
Another thing is power management and PnP.
You might start simply by building your code with the WinNT and seeing
what fails to compile/link. Examine each failure and determine whether
it can be cured merely by small code changes or whether the problem
requires changing the design. To make this task easier, you ought to use
DDKBUILD or equivalent to build in WinXP (or Win2K) in order to get a
browse file; with the browse file, you can see how a particular API is
supported in WinXP and so begin to see what might need changing in
WinNT.
–
If replying by e-mail, please remove “nospam.” from the address.
James Antognini
Windows DDK MVP
NT doesnt support WDM, but u’ve to change it to Legacy driver.
Good Luck
From: Prasad R
>Reply-To: “Windows System Software Developers Interest List”
>To: “Windows System Software Developers Interest List”
>Subject: [ntdev] Dbt regarding porting
>Date: Thu, 24 Jul 2003 11:02:59 +0530
>
>
>
>I am having the code for a kernal mode system callpaths tracker for windows
>2000 .
>I need to port the driver to Win NT . So where to start with ? I had install
>both
>the DDK kits for NT and XP.What are the major changes to be incorporated
>with the
>driver to make it compatible with NT.I know that 2000 driver is WDM
>compatible
>does it mean only the recompilation of the code with NT ddk is needed for
>porting ?
>
>This communication contains information, which is confidential and may also
>be privileged. It is for the exclusive use of the intended recipient(s). If
>you are not the intended recipient(s), please note that any distribution,
>printing, copying or use of this communication or the information in it is
>strictly prohibited. If you have received this communication in error,
>please notify the sender immediately and then destroy any copies of it.
>
>
>
>—
>You are currently subscribed to ntdev as: xxxxx@hotmail.com
>To unsubscribe send a blank email to xxxxx@lists.osr.com
It’s all happening @ F1. Feel the thrill! Race along right here!