NdisSetEvent and NdisInitializeEvent are not exported to VxDs; however,
they are exported to the PE Loader’s export table, so writing a protocol
driver using the Windows 2000 DDK as a .SYS driver will expose these
functions.
This will have the added benefit of letting you use the same (or similar
driver based on the same source code base) across all Windows platforms
(98/98SE/ME/2K/XP).Take a look at the Windows XP DDK sample NDISUIO as a
starting point.
You’ll have to modify the .INF file. Posted below. The proper way to
rewrite the .INF is to have an inf that handles all 9x/ME->2K/XP
platforms through .NT, etc, directives…
Bryan
This posting is provided “AS IS” with no warranties, and confers no
rights. You assume all risk for your use. (c) 2001 Microsoft
Corporation. All rights reserved.
; NDISUIO.INF
;
; NDISUIO Transport
;
; Copyright 2001, Microsoft Corporation
[version]
signature=“$CHICAGO$”
Class=NetTrans
provider=%V_MS%
[Manufacturer]
%V_MS%=MS
[MS]
%NDISUIO.DeviceDesc%= NDISUIO.ndi, NDISUIO
;***********************************************************************
*****
; NDISUIO
;***********************************************************************
*****
[NDISUIO.ndi]
CopyFiles=NDISUIO.CopyFiles
AddReg=NDISUIO.ndi.reg
DeviceID=NDISUIO
MaxInstance=8
[NDISUIO.ndi.reg]
HKR,Ndi,DeviceID,NDISUIO
HKR,Ndi,MaxInstance,8
;;;HKR,Ndi,NdiInstaller,“MyNdi.dll,MyNdiProc”
; NDIS info
HKR,NDIS,LogDriverName,“NDISUIO”
HKR,NDIS,MajorNdisVersion,1,05
HKR,NDIS,MinorNdisVersion,1,00
; Interfaces
HKR,Ndi\Interfaces,DefUpper,“”
HKR,Ndi\Interfaces,DefLower,“ndis3,ndis4,ndis5”
HKR,Ndi\Interfaces,UpperRange,“”
HKR,Ndi\Interfaces,LowerRange,“ndis3,ndis4,ndis5”
; Install-Remove Sections
HKR,Ndi\Install,“NDISUIO.Install”
HKR,Ndi\Remove,“NDISUIO.Remove”
; Context help
HKR,Ndi,HelpText,%NDISUIO_HELP%
[NDISUIO.Install]
AddReg=NDISUIO.AddReg
DelReg=NDISUIO.Ins.DelReg
CopyFiles=NDISUIO.CopyFiles
[NDISUIO.AddReg]
HKR,DevLoader,*ndis,*ntkern
HKR,DeviceVxDs,“ndisuio.sys”
[NDISUIO.CopyFiles]
ndisuio.sys
[NDISUIO.Remove]
DelReg=NDISUIO.Rmv.DelReg
DelFiles=NDISUIO.CopyFiles
[NDISUIO.Rmv.DelReg]
;***********************************************************************
*****
; Destination Directories
;***********************************************************************
*****
[DestinationDirs]
NDISUIO.CopyFiles = 11 ; LDID_SYS
[SourceDisksNames]
[SourceDisksFiles]
;***********************************************************************
*****
; Localizable Strings
;***********************************************************************
*****
[strings]
V_MS=“Microsoft”
V_CLASSNAME=“Network Protocol”
; Devices
NDISUIO.DeviceDesc=“Sample NDISUIO Protocol Driver”
; Parameters
PARAM_YES=“Yes”
PARAM_NO=“No”
PARAM_OFF=“Off”
PARAM_NONE=“None”
; Context help
NDISUIO_HELP=“Sample Protocol Driver”
-----Original Message-----
From: Ken Nguyen [mailto:xxxxx@hotmail.com]
Sent: Thursday, September 06, 2001 11:53 AM
To: NT Developers Interest List
Subject: [ntdev] NdisSetEvent and NdisInitializeEvent in VPacket sample
in 98ddk
I added the NdisInitializeEvent and NdisSetEvent calls in the Vpacket
Sample. When build it reports Link errors that they are unresolved
external
symbols. Anyone know why and how to resolve these errors?
Thanks
Ken
Get your FREE download of MSN Explorer at
http://explorer.msn.com/intl.asp
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com