- ndisprot sample code and Win98SE/ME
- Posted by Riga on July 21st, 2004
Hi,
Does any one know how to build the ndisprot for Win98SE/ME ?
I use the WinXP SP1 DDK (select the win 2K build environment) to build the
ndisprot.sys.
But the ndisprot.inf could not used to install ndisprot.sys on win98SE/ME.
Any suggestion ?
- Posted by Fengfen Liu [MSFT] on July 21st, 2004
Hi, Riga, from the readme file, ndisprot is not supposed to work on
win98SE/ME:
The sample works on Windows 2000, Windows XP, and Windows Server 2003 32-bit
and 64-bit platforms.
Thanks
Fengfen
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Riga" <Riga@IPNDOTCOM> wrote in message
news:%23Uuav8ybEHA.368@TK2MSFTNGP10.phx.gbl...
- Posted by Stephan Wolf [MVP] on July 21st, 2004
See
"Q. How can I adapt NDISUIO to work on Windows 98/ME?"
http://www.ndis.com/faq/QA12030301.htm
Note: NDISUIO has been renamed to NDISPROT in the Windows 2003 version
of the DDK.
Stephan
---
On Wed, 21 Jul 2004 22:26:34 +0800, "Riga" <Riga@IPNDOTCOM> wrote:
- Posted by Riga on July 22nd, 2004
Thanks for your help, i will try it.
Another question, how could i start this protocol driver. In win XP, i could
uee "net start ndisprot" to start it. In win98SE, could i use the same
command ?
"Stephan Wolf [MVP]" <stewo68@hotmail.com> ???
news:4jatf0hebi8ahbuuduk0d55u3f85eu87nl@4ax.com ???...
- Posted by Riga on July 22nd, 2004
I could install the protocol driver, but seems this driver is not loaded by
ndis.vxd.
How could i check what happened ?
The INF is listed below
;-------------------------------------------------------------------------
; NDISIPC.INF -- Sample NDIS Protocol Driver
;
; Copyright (c) 2003, Microsoft Corporation
;-------------------------------------------------------------------------
[version]
signature = "$CHICAGO$"
Class = NetTrans
provider = %Msft%
[Manufacturer]
%Msft%=MSFT
[MSFT]
%NDISIPC.DeviceDesc%= NDISIPC.ndi, NDISIPC
;************************************************* **************************
; NDISIPC
;************************************************* **************************
[NDISIPC.ndi]
CopyFiles=NDISIPC.CopyFiles
AddReg=NDISIPC.ndi.reg
DeviceID=NDISIPC
MaxInstance=8
[NDISIPC.ndi.reg]
HKR,Ndi,DeviceID,,NDISIPC
HKR,Ndi,MaxInstance,,8
; NDIS info
HKR,NDIS,LogDriverName,,"NDISIPC"
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,,,"NDISIPC.Install"
HKR,Ndi\Remove,,,"NDISIPC.Remove"
; Context help
HKR,Ndi,HelpText,,%NDISIPC_HELP%
[NDISIPC.Install]
AddReg=NDISIPC.AddReg
DelReg=NDISIPC.Ins.DelReg
CopyFiles=NDISIPC.CopyFiles, NDISIPC.CopyFiles.inf
[NDISIPC.AddReg]
HKR,,DevLoader,,*ndis,*ntkern
HKR,,DeviceVxDs,,"NDISIPC.sys"
[NDISIPC.CopyFiles]
NDISIPC.sys
[NDISIPC.CopyFiles.inf]
NDISIPC9X.inf
[NDISIPC.Remove]
DelReg=NDISIPC.Rmv.DelReg
DelFiles=NDISIPC.CopyFiles, NDISIPC.CopyFiles.inf
[NDISIPC.Rmv.DelReg]
;************************************************* **************************
; Destination Directories
;************************************************* **************************
[DestinationDirs]
NDISIPC.CopyFiles = 11 ; LDID_SYS
NDISIPC.CopyFiles.inf = 17 ; LDID_INF
[SourceDisksNames]
[SourceDisksFiles]
;************************************************* **************************
; Localizable Strings
;************************************************* **************************
[strings]
Msft="Microsoft"
V_CLASSNAME="Network Protocol"
; Devices
NDISIPC.DeviceDesc="NDIS Protocol Driver"
; Parameters
PARAM_YES="Yes"
PARAM_NO="No"
PARAM_OFF="Off"
PARAM_NONE="None"
; Context help
NDISIPC_HELP="A driver to support user-mode I/O on NDIS devices"
"Stephan Wolf [MVP]" <stewo68@hotmail.com> ???
news:4jatf0hebi8ahbuuduk0d55u3f85eu87nl@4ax.com ???...
- Posted by Stephan Wolf [MVP] on July 22nd, 2004
On Thu, 22 Jul 2004 15:28:49 +0800, "Riga" <Riga@IPNDOTCOM> wrote:
Please check whether the driver is not loaded vs. fails
initialization. Notice the difference. The first would mean the system
does not load the driver. The second means the fiver loads but
something goes wrong during DriverEntry() or it does not bind to
miniports.
You should add some DbgPrint() code to your driver so you can print
messages to the debugger console.
Stephan
- Posted by Stephan Wolf [MVP] on July 22nd, 2004
On Thu, 22 Jul 2004 11:16:03 +0200, "Stephan Wolf [MVP]"
<stewo68@hotmail.com> wrote:
....and DbgPrint() AFAIK only works with the DEBUG version of NDIS.VXD.
Otherwise, your driver won't actually load (maybe that's your
problem?).
Stephan
- Posted by Bryan S. Burgin [MSFT] on July 23rd, 2004
See http://www.ndis.com/faq/QA12030301.htm.
Bryan S. Burgin
bburgin@microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights.
- Posted by Riga on July 23rd, 2004
Thanks, now i could see the debug message, and i know that my driver is
really loaded.
"Stephan Wolf [MVP]" <stewo68@hotmail.com> ???
news:5qfvf05a3o2v2d7sk3ugje3p91af134rd2@4ax.com ???...
- Looking for sample code to read DMI memory. (Programming) by Timothy Lange
- Dispatch Driver sample code (Drivers) by incognito
- How to compiling Ndis 5.0 NDIS_WDM sample for Win98se/ windows 2000? (Drivers) by jitian
- Code review of cross platform code sample (Programming) by Otto Wyss
- Sample code for NDIS 802.11 driver? (Drivers) by Lin Sun

