[Q] Ndis version vs. Windows version.

Daum

unread,

Jul 18, 2003, 2:15:59 PM7/18/03

to

Hello, everyone.

I want know what's the NDIS version should I adapt according to Windows O/S
version.

Where can I find like the mapping table between windows O/S and Ndis
version?

For example, NDIS5.0<->Win2K and NDIS5.1<->WinXP.

Thank you for your help.

Have a nice day.

//DAUM

Bryan S. Burgin [MSFT]

unread,

Jul 18, 2003, 4:30:50 PM7/18/03

to

Daum,

What might be better to determine the version of NDIS running on the system
at the time is to call NdisReadConfiguration with the special keyword
"NdisVersion". This way you can let NDIS tell you instead of keeping a
table.

See the documentation for NdisReadConfiguration for more information.

HTH,

Bryan S. Burgin
bbu...@microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.

Daum

unread,

Jul 18, 2003, 5:25:09 PM7/18/03

to

Thank you for your good information.

Please, give me more information.

I want know the NDIS version relation to Windows version before my Ndis
driver was installed.

Your suggestion was meaningful only after Ndis driver installed.

Is there any other information or documentation about Ndis version relation
to Windows O/S version?

Can Ndis version in Win2K be Ndis5.1?

Thank you.

""Bryan S. Burgin [MSFT]"" <bbu...@online.microsoft.com> wrote in message
news:E3AI5tWT...@cpmsftngxa06.phx.gbl...

Daum

unread,

Jul 18, 2003, 7:23:05 PM7/18/03

to

Thank you for your good information.

Please, give me more information.

I want know the NDIS version relation to Windows version before my Ndis
driver was installed.

Your suggestion was meaningful only after Ndis driver installed I think.

James Antognini

unread,

Jul 19, 2003, 10:51:54 AM7/19/03

to

It's not clear to me why you would use such information. Yes, it is
conceivable that one could split an NDIS driver into several
executables, with DriverEntry ascertaining OS level and NDIS level by
inference (see below), then loading an appropriate second executable
suited to the level and finally establishing the miniport and protocols
entry points as appropriate to NDIS level. But it seems like a lot of
programming work. The only case where I've seen that sort of effort (in
fact, I made it) was in performance paths, where a higher OS level had
much better performance for certain activities.

As for OS level versus NDIS level, to the best of my knowledge (as you
seem to realize), Win2K implies NDIS 5.0, and XP and higher, NDIS 5.1
(at least; I suspect that some day we'll see NDIS 6.0 and successors
associated with higher OS levels).

--
If replying by e-mail, please remove "nospam." from the address.

James Antognini
Windows DDK MVP

Stephan Wolf

unread,

Jul 21, 2003, 5:11:42 PM7/21/03

to

Since the same NDIS driver binary can be used on several OS variants
it can be very useful to know the underlying OS type and version.

For instance, NDIS 5.0 specifies scatter/gather lists. These are fully
supported in W2K (and higher). However, W98 SE does not support
scatter/gather lists and thus good old map registers need to be used
instead. So its crucial here to know the OS type.

Actually, it is very easy to determine the Windows type and version:

1. Get the OS type by calling NdisReadConfiguration("Environment") ->
NDIS_ENVIRONMENT_TYPE.

2. Get the supported NDIS version by calling
NdisReadConfiguration("NdisVersion").

3. From the combination of the two, determine the exact OS type and
version according to the table in the DDK docs under "NDIS Versions"
(http://msdn.microsoft.com/library/en-us/network/hh/network/103prog_4qjr.asp).

Stephan
---