Frequently Asked Questions

Q. What are the steps needed to rename Microsoft NDISPROT driver?
 

A. If you are not an experienced NDIS driver developer, then it may be easy to overlook all of the steps necessary to "rename" the Microsoft NDISPROT driver sample.

It is obvious that the file name must be changed, but you may not notice that other internal names must also be changed to insure that the resulting renamed driver does not conflict with the standard NDISPROT driver. In addition, some changes must be made to the .INF file as well as the companion UIOTEST application.

Here are the steps to "rename" NDISPROT" to the new name "AcmeNet" for the "AcmeNet, Inc.".

 

1.) Make a copy of the NDISPROT folder.

2.) Rename it AcmeNet

3.) Go to the AcmeNet\sys folder.

4.) Edit the AcmeNet\sys\SOURCES file to change the TARGETNAME:

WAS: TARGETNAME=ndisprot

IS: TARGETNAME=AcmeNet

4.) Edit the AcmeNet\sys\ntdisp.c file to change the protoName:

WAS: protoName = NDIS_STRING_CONST("NdisProt");

IS: protoName = NDIS_STRING_CONST("AcmeNet");

5.) Edit the AcmeNet\sys\ndisprot.h file to change the NT_DEVICE_NAME and the DOS_DEVICE_NAME:

WAS:

#define NT_DEVICE_NAME L"\\Device\\NdisProt"

#define DOS_DEVICE_NAME L"\\DosDevices\\NdisProt"

IS:

#define NT_DEVICE_NAME L"\\Device\\AcmeNet"

#define DOS_DEVICE_NAME L"\\DosDevices\\AcmeNet"

6.) Use the DDK Build command to build the AcmeNet driver.

7.) Edit the AcmeNet\test\uiotest.c file to change the NdisProtDevice:

WAS: NdisProtDevice[] = "\\\\.\\\\NdisProt";

IS: NdisProtDevice[] = "\\\\.\\\\AcmeNet";

8.) Use the DDK Build command to rebuild the uiotest application.

9.) Copy the ndisprot.inf file to AcmeNet.inf

10.) Edit the AcmeNet.inf file:

Global replace: ndisprot -> acmenet

Global replace: NDISPROT -> ACMENET

Global replace: Msft -> Acme

Global replace: Microsoft -> AcmeNet, Inc.

Additional Edits:

WAS:

ACMENET_Desc = Sample NDIS Protocol Driver"

ACMENET_HelpText = "A driver to support user-mode I/O on NDIS devices"

IS:

ACMENET_Desc = AcmeNet NDIS Protocol Driver"

ACMENET_HelpText = "AcmeNet user-mode I/O on NDIS devices"

11.) Install AcmeNet.sys using AcmeNet.inf. The new uiotest.exe application should work with the AcmeNet.sys driver.

I have not actually tried this myself, but these are the steps.

 

 

Topic Status

February 11, 2004 Information posted.

 

PCAUSA Home · Privacy Statement · Products · Ordering · Support · Utilities · Resources
Mailing Lists  · PCAUSA Newsletter · PCAUSA Discussion List
Rawether for Windows, Rawether .NET, WinDis 32 and NDIS Press are trademarks of Printing Communications Assoc., Inc. (PCAUSA)
Microsoft, MS, Windows, Windows Vista, Windows 95, Windows 98, Windows Millennium, Windows 2000, and Win32 are registered trademarks and Visual C++ and Windows NT are trademarks of the Microsoft Corporation.
Copyright © 1996-2007 Printing Communications Assoc., Inc. (PCAUSA)
Last modified: January 20, 2007