|
|
|
|
The Win32 NDIS Framework
|
 | Network Monitors |
| Applications Which Use Non-Standard Protocols |
| Network Adapter Test Programs |
WinDis 32 consists of a set of sample Win32 applications (the WinDis 32 SDK) and supporting DLL's and NDIS protocol drivers (the Win32 NDIS Framework) that demonstrate use of the framework to directly access NDIS MAC adapters.
The WinDis 32 SDK applications include:
| NDIScope MFC Application - Which allows the user to dynamically select
and bind with any installed Ethernet adapter and then displays adapter information. The
Open button allows the user to select the protocols to be captured, and then starts the
HookPeek application. |
| HookPeek Win32 Console Application - Which binds with a specified adapter and then dumps all received packets to the console display. |
The WinDis 32 DDK components include:
| PCANDIS5.SYS Protocol Driver - A dynamically-loadable NDIS
5.0 Protocol
Driver For Windows 2000. |
| PCANDIS4.SYS Protocol Driver - A dynamically-loadable NDIS 4.0 Protocol
Driver For Windows NT. |
| PCANDIS3.VXD Protocol Driver - A dynamically-loadable NDIS 3.1 Protocol
Driver for Windows 95. |
| W32N50.DLL Platform API DLL - A DLL which exports the Win32 NDIS API and hides platform dependencies associated with accessing the registry and protocol drivers. |
| Uniform Win32 API For Access Of NDIS Adapters - A common Win32 API is
used to access NDIS adapters from Win32 on the Windows 95, Windows 98, Windows NT and
Windows 2000 platforms. |
| Simple NdisRequest API From Win32 - Making NDIS requests from Win32 is
almost as simple as making them from within a kernel-mode driver. |
| Dynamically Loadable NDIS Protocol Drivers - On the Windows 95,
Windows 98, Windows Millennium, Windows
NT and Windows 2000 platforms supporting NDIS protocol drivers can be dynamically loaded
on demand from the Win32 applications. |
| Network Control Panel Installation - Dynamic loading of the NDIS
protocol driver is not always appropriate. In particular, dynamic binding depends on the
adapters being installed and bound to other protocols such as TCP/IP so that WinDis 32 can
find them. If it is necessary to install an adapter for the exclusive use of WinDis 32,
the PCANDIS# driver can be installed and bound to the adapter in the
"traditional" manner using the Network Control Panel. |
| "Adapter Chooser" Dialog - The NDIScope SDK application
includes code which examines the registry for installed NDIS adapters. An "Adapter
Chooser" dialog displays a list of installed adapters. |
| Multiple Concurrent Adapter Opens - The handle-based WinDis 32 API
allows the Win32 applications to bind to multiple NDIS adapters concurrently. |
| Performance-Oriented Packet Read Mechanism - The HookPeek application
packet read mechanism and the design of the companion NDIS protocol drivers include the
capability to queue multiple concurrent asynchronous Win32 packet reads and systematically
handle received packets at the Win32 level. |
| BSD Packet Filter (BPF) Filter - The PCANDIS# protocol drivers include
PCAUSA's port of the BPF filter pseudo-machine from the Unix environment to Windows. This
provides a general and flexible mechanism for Win32 applications to specify a protocol
filtering "program" which will be executed by the protocol drivers to reject
unwanted packets as early as possible. |
| Packet Time Stamps And Sequence Numbers- The data structure used to
pass received packets from the NDIS protocol drivers to the Win32 application includes a
packet timestamp and a driver assigned sequence number. The latter is intended to be used
to detect when packets are lost because of a lack of resources at the driver level. |
| Other Performance Improvements - Asynchronous packet I/O using APCs and I/O Completion Ports. |
WinDis 32 SDK Applications - WinDis 32 sample applications are
currently built using Microsoft Visual C/C++ V5.0. There is no problem converting to use
of Microsoft Visual C/C++ V6.0.
WinDis 32 DDK Windows NT Device Drivers - Are built using Microsoft Visual C/C++ V5.0 on the Windows NT platform.
In order to compile the WinDis 32 Windows NT 4.0 device driver you must also have the Windows NT 4.0 Device Driver Kit (DDK) from Microsoft.
WinDis 32 DDK Windows 9X Device Drivers - Are built using Microsoft Visual C/C++ V5.0 on the Windows 9X platform.
.
To download the Rawether for Windows Sample Executables, please send an empty email to:
You will receive an auto-responder email message containing the download URL.
If you have concerns about how your email address will be used, please see the PCAUSA Privacy Statement.
Rawether for Windows Documentation - If you are interested in more details about Rawether for Windows and the Win32 NDIS Framework:
| Download HtmlHelp Documentation - You can download Rawether for
Windows documentation in HtmlHelp format by
clicking here.
 |
The documentation includes:
| Introduction To WinDis 32 |
| WinDis 32 API Reference |
| WinDis 32 SDK Documentation |
| WinDis 32 DDK Documentation |
| WinDis 32 Knowledge Base |
You can also view the following information from the new Rawether.net website:
- Rawether Frequently Asked Questions List
- This answers many common questions about Rawether for Windows.
- Rawether Knowledge Base
- Provides information about a variety of topics associated with Rawether for Windows.
- Rawether Release Notes
- Includes current Version History and News about the Rawether as well as Download links.
- License Agreement And Limited Warranty
- The End User License and Limited Warranty offered with PCAUSA products.
- Customer Comments
- What PCAUSA customers have to say.
|
|
Win32
NDIS Framework (WinDis 32) |
||||||||||||||||||||||||||||
|
Prices good through July 31, 2009.
In addition, PCAUSA has constructed a new website dedicated to this product. As we build the new Rawether.net website (and make a transition to the new Rawether for Windows product name) we are doing out best to improve on-line information.
If the information presented here has not satisfactorily answered your questions, consider visiting the Rawether.net site by clicking below.
We welcome your comments about the PCAUSA.COM and RAWETHER.NET sites.
And certainly, if you have remaining unanswered questions please contact our Sales Department.
|
PCAUSA Home ·
Privacy Statement ·
Products ·
Ordering ·
Support ·
Utilities ·
Resources
|
