- NDIS 5.1 on Windows 2000
- Posted by ms on June 24th, 2005
I have a problem with running my driver on some Windows 2000 systems.
It uses NdisGetPoolFromPacket, that was introduced in NDIS 5.1. Windows
shows blue screen when trying to load the driver.
What update is required on Windows 2000 to support NDIS 5.1?
ms
- Posted by Pavel A. on June 24th, 2005
"ms" <ms@discussions.microsoft.com> wrote in message news:AAB831A9-1882-42CB-A960-FD5879821503@microsoft.com...
WinXP
--PA
- Posted by Don Burn on June 24th, 2005
Sorry, 2000 supports NDIS 5.0 see
http://msdn.microsoft.com/library/de...3ebe07.xml.asp
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
"ms" <ms@discussions.microsoft.com> wrote in message
news:AAB831A9-1882-42CB-A960-FD5879821503@microsoft.com...
- Posted by ms on June 24th, 2005
It's not that bad. After I installed all critical updates (44 of them), my
driver loads on Windows 2000. But what to write in requirements documentation
of my driver? There must be one key update, not?
ms
"Pavel A." wrote:
- Posted by Pavel A. on June 24th, 2005
"ms" <ms@discussions.microsoft.com> wrote in message news:83F2E7EB-3522-4711-903B-949301C2F5D1@microsoft.com...
You installed these updates over SP4 or earlier SP?
--PA
- Posted by ms on June 24th, 2005
You both can be right. After updating windows, system does not crash, but the
driver is not loaded. I see an error message in event log:
The specified procedure could not be found.
Is there an easy way to find out which function is not found?
ms
"Don Burn" wrote:
- Posted by Skywing on June 24th, 2005
NdisGetPoolFromPacket and other NDIS functions new to NDIS 5.1 are not
present on Windows 2000. This includes SP4 with all available security
hotfixes installed.
If you want your driver to run on Windows 2000, then you cannot static link
to any NDIS routines added after NDIS 5.0.
"ms" <ms@discussions.microsoft.com> wrote in message
news:59DC866A-D738-4BC2-A79D-2E862AA1294A@microsoft.com...
- Posted by Robert Schlabbach on June 24th, 2005
"Don Burn" <burn@stopspam.acm.org> wrote in message
news:IfXue.4495$B_3.1942@fe05.lga...
/network/103prog_123c3b1d-c431-4829-9943-fd060d3ebe07.xml.asp
Hmm, I don't think the information on this page is fully accurate. At least
I've been able to make an NDISWAN 4.0 driver work on the original Windows
95, whereas this page says Windows 95 only supports NDIS 3.1...
Doesn't the NDIS versioning follow the original Windows versioning anyway?
I.e.:
Windows 95 = Windows 4.0 -> NDIS 4.0
Windows 98 = Windows 4.1 -> NDIS 4.1
Windows NT 4.0 -> NDIS 4.0
Windows 2000 = Windows 5.0 -> NDIS 5.0
Windows XP = Windows 5.1 -> NDIS 5.1
Regards,«
--
Robert Schlabbach
e-mail: robert_s@gmx.net
Berlin, Germany
- Posted by Arkady Frenkel on June 25th, 2005
That only show that that driver not use additional functionality of NDIS 4.0
in compare with previous version
Arkady
"Robert Schlabbach" <robert_s@gmx.net> wrote in message
news:uEeLEsPeFHA.2880@TK2MSFTNGP10.phx.gbl...
- Posted by Robert Schlabbach on June 27th, 2005
Actually, the "Dial-Up Networking Update" for Windows 95 retrofits the
NDIS.VXD from OSR2 onto the original Windows 95 release. So I suppose that
after installing the update, Windows 95's NDIS function becomes identical
to OSR2.
Regards,«
--
Robert Schlabbach
e-mail: robert_s@gmx.net
Berlin, Germany
"Arkady Frenkel" <arkadyf@hotmailxdotx.com> wrote in message news:#naBY7XeFHA.3712@TK2MSFTNGP09.phx.gbl...
