Nov 26, 2018  A miniport driver communicates with its NICs and with higher-level drivers through the NDIS library. The NDIS library exports a full set of functions (NdisM Xxx and other Ndis Xxx functions) that encapsulate all of the operating system functions that a miniport driver must call. Apr 20, 2017  A minidriver or a miniport driver acts as half of a driver pair. Driver pairs like (miniport, port) can make driver development easier. In a driver pair, one driver handles general tasks that are common to a whole collection of devices, while the other driver handles tasks that are specific to an individual device. The miniport driver sets up the transfer of data from the NIC and then indicates the presence of the received packet to bound higher-level drivers by calling the appropriate NdisXxx function. Connectionless and Connection-Oriented Miniport Drivers. NDIS supports miniport drivers for both connectionless environments and connection-oriented.

• Hp Miniport Driver Download
• Hp Miniport Driver Mac
• Wan Miniport Driver Hp

Wide Area Network (WAN) Miniport driver is handy driver software that enables alternative network connection methods in your Windows computer. But what if you come across issues with your WAN Miniport driver? No need to worry, as these glitches can be resolved through a simple trick: updating the driver to its latest version. Download the latest drivers, firmware, and software for your HP Stream Notebook - 11-d010nr (ENERGY STAR).This is HP’s official website that will help automatically detect and download the correct drivers free of cost for your HP Computing and Printing products for Windows and Mac operating system. Wan Miniport (ip) Driver for Windows 7 32 bit, Windows 7 64 bit, Windows 10, 8, XP. Uploaded on 4/8/2019, downloaded 5594 times, receiving a 91/100 rating by 4371 users.

-->

A minidriver or a miniport driver acts as half of a driver pair. Driver pairs like (miniport, port) can make driver development easier. In a driver pair, one driver handles general tasks that are common to a whole collection of devices, while the other driver handles tasks that are specific to an individual device. The drivers that handle device-specific tasks go by a variety of names, including miniport driver, miniclass driver, and minidriver.

Microsoft provides the general driver, and typically an independent hardware vendor provides the specific driver. Before you read this topic, you should understand the ideas presented in Device nodes and device stacks and I/O request packets.

Every kernel-mode driver must implement a function named DriverEntry, which gets called shortly after the driver is loaded. The DriverEntry function fills in certain members of a DRIVER_OBJECT structure with pointers to several other functions that the driver implements. For example, the DriverEntry function fills in the Unload member of the DRIVER_OBJECT structure with a pointer to the driver's Unload function, as shown in the following diagram.

The MajorFunction member of the DRIVER_OBJECT structure is an array of pointers to functions that handle I/O request packets (IRPs), as shown in the following diagram. Typically the driver fills in several members of the MajorFunction array with pointers to functions (implemented by the driver) that handle various kinds of IRPs.

An IRP can be categorized according to its major function code, which is identified by a constant, such as IRP_MJ_READ, IRP_MJ_WRITE, or IRP_MJ_PNP. The constants that identify major function code serve as indices in the MajorFunction array. For example, suppose the driver implements a dispatch function to handle IRPs that have the major function code IRP_MJ_WRITE. In this case, the driver must fill in the MajorFunction[IRP_MJ_WRITE] element of the array with a pointer to the dispatch function.

Typically the driver fills in some of the elements of the MajorFunction array and leaves the remaining elements set to default values provided by the I/O manager. The following example shows how to use the !drvobj debugger extension to inspect the function pointers for the parport driver.

In the debugger output, you can see that parport.sys implements GsDriverEntry, the entry point for the driver. GsDriverEntry, which was generated automatically when the driver was built, performs some initialization and then calls DriverEntry, which was implemented by the driver developer.

You can also see that the parport driver (in its DriverEntry function) provides pointers to dispatch functions for these major function codes:

• IRP_MJ_CREATE
• IRP_MJ_CLOSE
• IRP_MJ_READ
• IRP_MJ_WRITE
• IRP_MJ_QUERY_INFORMATION
• IRP_MJ_SET_INFORMATION
• IRP_MJ_DEVICE_CONTROL
• IRP_MJ_INTERNAL_DEVICE_CONTROL
• IRP_MJ_CLEANUP
• IRP_MJ_POWER
• IRP_MJ_SYSTEM_CONTROL
• IRP_MJ_PNP

The remaining elements of the MajorFunction array hold pointers to the default dispatch function nt!IopInvalidDeviceRequest.

In the debugger output, you can see that the parport driver provided function pointers for Unload and AddDevice, but did not provide a function pointer for StartIo. The AddDevice function is unusual because its function pointer is not stored in the DRIVER_OBJECT structure. Instead, it is stored in the AddDevice member of an extension to the DRIVER_OBJECT structure. The following diagram illustrates the function pointers that the parport driver provided in its DriverEntry function. The function pointers provided by parport are shaded.

Making it easier by using driver pairs

Over a period of time, as driver developers inside and outside of Microsoft gained experience with the Windows Driver Model (WDM), they realized a couple of things about dispatch functions:

• Dispatch functions are largely boilerplate. For example, much of the code in the dispatch function for IRP_MJ_PNP is the same for all drivers. It is only a small portion of the Plug and Play (PnP) code that is specific to an individual driver that controls an individual piece of hardware.
• Dispatch functions are complicated and difficult to get right. Implementing features like thread synchronization, IRP queuing, and IRP cancellation is challenging and requires a deep understanding of how the operating system works.

To make things easier for driver developers, Microsoft created several technology-specific driver models. At first glance, the technology-specific models seem quite different from each other, but a closer look reveals that many of them are based on this paradigm:

• The driver is split into two pieces: one that handles the general processing and one that handles processing specific to a particular device.
• The general piece is written by Microsoft.
• The specific piece may be written by Microsoft or an independent hardware vendor.

Suppose that the Proseware and Contoso companies both make a toy robot that requires a WDM driver. Also suppose that Microsoft provides a General Robot Driver called GeneralRobot.sys. Proseware and Contoso can each write small drivers that handle the requirements of their specific robots. For example, Proseware could write ProsewareRobot.sys, and the pair of drivers (ProsewareRobot.sys, GeneralRobot.sys) could be combined to form a single WDM driver. Likewise, the pair of drivers (ContosoRobot.sys, GeneralRobot.sys) could combine to form a single WDM driver. In its most general form, the idea is that you can create drivers by using (specific.sys, general.sys) pairs.

Function pointers in driver pairs

In a (specific.sys, general.sys) pair, Windows loads specific.sys and calls its DriverEntry function. The DriverEntry function of specific.sys receives a pointer to a DRIVER_OBJECT structure. Normally you would expect DriverEntry to fill in several elements of the MajorFunction array with pointers to dispatch functions. Also you would expect DriverEntry to fill in the Unload member (and possibly the StartIo member) of the DRIVER_OBJECT structure and the AddDevice member of the driver object extension. However, in a driver pair model, DriverEntry does not necessarily do this. Instead the DriverEntry function of specific.sys passes the DRIVER_OBJECT structure along to an initialization function implemented by general.sys. The following code example shows how the initialization function might be called in the (ProsewareRobot.sys, GeneralRobot.sys) pair.

The initialization function in GeneralRobot.sys writes function pointers to the appropriate members of the DRIVER_OBJECT structure (and its extension) and the appropriate elements of the MajorFunction array. The idea is that when the I/O manager sends an IRP to the driver pair, the IRP goes first to a dispatch function implemented by GeneralRobot.sys. If GeneralRobot.sys can handle the IRP on its own, then the specific driver, ProsewareRobot.sys, does not have to be involved. If GeneralRobot.sys can handle some, but not all, of the IRP processing, it gets help from one of the callback functions implemented by ProsewareRobot.sys. GeneralRobot.sys receives pointers to the ProsewareRobot callbacks in the GeneralRobotInit call.

At some point after DriverEntry returns, a device stack gets constructed for the Proseware Robot device node. The device stack might look like this.

As shown in the preceding diagram, the device stack for Proseware Robot has three device objects. The top device object is a filter device object (Filter DO) associated with the filter driver AfterThought.sys. The middle device object is a functional device object (FDO) associated with the driver pair (ProsewareRobot.sys, GeneralRobot.sys). The driver pair serves as the function driver for the device stack. The bottom device object is a physical device object (PDO) associated with Pci.sys.

Notice that the driver pair occupies only one level in the device stack and is associated with only one device object: the FDO. When GeneralRobot.sys processes an IRP, it might call ProsewareRobot.sys for assistance, but that is not the same as passing the request down the device stack. The driver pair forms a single WDM driver that is at one level in the device stack. The driver pair either completes the IRP or passes it down the device stack to the PDO, which is associated with Pci.sys.

More games of KONAMI: PES 2014: TORRENTTo download via torrent network link above you need to install first and how to make your. Pro Evolution Soccer 14 is action football games has release on 19-Sep-14 by Konami for PC. Download pes 2014 pc full version bagas31. PES is football sport in this game player can play with friend as multiplayers with higher quality of picture in 3D by KONAMI.

Example of a driver pair

Hp Miniport Driver Download

Suppose you have a wireless network card in your laptop computer, and by looking in Device Manager, you determine that netwlv64.sys is the driver for the network card. You can use the !drvobj debugger extension to inspect the function pointers for netwlv64.sys.

In the debugger output, you can see that netwlv64.sys implements GsDriverEntry, the entry point for the driver. GsDriverEntry, which was automatically generated when the driver was built, performs some initialization and then calls DriverEntry, which was written by the driver developer.

In this example, netwlv64.sys implements DriverEntry, but ndis.sys implements AddDevice, Unload, and several dispatch functions. Netwlv64.sys is called an NDIS miniport driver, and ndis.sys is called the NDIS Library. Together, the two modules form an (NDIS miniport, NDIS Library) pair.

This diagram shows the device stack for the wireless network card. Notice that the driver pair (netwlv64.sys, ndis.sys) occupies only one level in the device stack and is associated with only one device object: the FDO.

Available driver pairs

The different technology-specific driver models use a variety of names for the specific and general pieces of a driver pair. In many cases, the specific portion of the pair has the prefix 'mini.' Here are some of (specific, general) pairs that are available:

• (display miniport driver, display port driver)
• (audio miniport driver, audio port driver)
• (storage miniport driver, storage port driver)
• (battery miniclass driver, battery class driver)
• (HID minidriver, HID class driver)
• (changer miniclass driver, changer port driver)
• (NDIS miniport driver, NDIS library)

Note As you can see in the list, several of the models use the term class driver for the general portion of a driver pair. This kind of class driver is different from a standalone class driver and different from a class filter driver.

Related topics

Download the latest WAN Miniport (PPPOE) driver for your computer's operating system. All downloads available on this website have been scanned by the latest anti-virus software and are guaranteed to be virus and malware-free.

Find All WAN Miniport (PPPOE) Drivers

Browse the list below to find the driver that meets your needs. To see more matches, use our custom search engine to find the exact driver.

Hp Miniport Driver Mac

Tech Tip: If you are having trouble deciding which is the right driver, try the Driver Update Utility for WAN Miniport (PPPOE). It is a software utility that will find the right driver for you - automatically.

DriverGuide maintains an extensive archive of Windows drivers available for free download. We employ a team from around the world. They add hundreds of new drivers to our site every day.

Having trouble finding the right driver? Try the Automatic Driver Update Utility, or you can request a driver and we will find it for you.

Popular Driver Updates for WAN Miniport (PPPOE)

Wan Miniport Driver Hp

WAN Miniport (PPPOE) Driver Update Utility Supported OS: Windows 10, Windows 8.1, Windows 7, Windows Vista, Windows XP File Version: Version 3.8.0 File Size: 269 KB File Name: DriverFinderInstall.exe Overall Rating:

PPPoE v0.92.0464.1 Driver Microsoft Device Type: Modem / ISDN Supported OS: All Win 2000 File Version: Version 0.92.0464.1 Release Date: 2000-02-06 File Size: 43.1 KB File Name: raspppoe.zip Overall Rating: (1 rating, 1 review) 891 Downloads Submitted Dec 4, 2003 by bruce pople (DG Member): 'BETA - PPPOE driver for win 2000 - DSL'

HFC-S PCI A 2BDSO ISDN CCD 9951E Driver Wisecom Device Type: Modem / ISDN Supported OS: Win XP Home, Win XP Pro Release Date: 2002-04-24 File Size: 594.4 KB File Name: pci_v326a_mexp.exe Overall Rating: (127 ratings, 154 reviews) 41,589 Downloads Submitted Sep 26, 2002 by T'Jaeckx Bjorn (DG Member): 'Works in Windows XP for chipset HFC-S PCI A 2BDSO ISDN CCD 9951E'

RASPPPOE Driver W-Link Device Type: Other Devices (Utility) Supported OS: Win Vista, Win Vista x64, Win 2003 Server, Win Server 2003 x64, Win XP Home, Win XP Pro, Win XP Pro x64, Win 2000 Workstation, Win 2000 Server, Win NT 4.0, Win NT 3.51, Win ME, Win 98SE, Win 98, Win 95, Win 3.11 File Version: Version 0.98.0720.0 Release Date: 2002-10-03 File Size: 333.3 KB File Name: RASPPPOE.zip Overall Rating: (9 ratings, 10 reviews) 720 Downloads Submitted Jun 19, 2006 by Sivaprakash (DG Staff Member): 'RASPPPOE - PPPoE Client Software Utility File.'

Mentor ADSL Full Rate PCI Modem Driver Other Companies Device Type: Modem / ISDN Supported OS: All Win 2000 File Size: 1.3 MB File Name: Wan.rar 55 Downloads Submitted Jan 3, 2004 by Fred (DG Member): 'Driver S/W Version 4012.099.040.000Mentor Full Rate ADSL PCI ModemThis driver supports the Conexant PCI ADSL reference board. This release contains WAN (RFC 2364/RFC 2516). Supported Operating Systems - Windows 98- Windows 2000 - Windows Me - Windows XPSupported ATM Protocols- PPP over ATM VCMUX (RFC ..'

BeWAN ADSL PCI & USB ST Driver BeWAN Device Type: Network Devices (Firmware) Supported OS: Win 2003 Server, Win XP Home, Win XP Pro, Win 2000 Workstation, Win 2000 Server, Win ME, Win 98 File Version: Version 1.9.0.10 Release Date: 2005-04-19 File Size: 1.2 MB File Name: bast19010.exe Overall Rating: (2 ratings, 2 reviews) 296 Downloads Submitted Oct 22, 2005 by Purushothaman (DG Staff Member): 'BeWAN ADSL PCI & USB ST - Network Firmware File'

Alcatel Speed Touch Home PSTN Driver Efficient Networks, Inc. Device Type: Modem / ISDN Supported OS: All Win 2000 File Size: 5.3 MB File Name: Enternet15b.zip Overall Rating: (13 ratings, 15 reviews) 2,102 Downloads Submitted Nov 28, 2002 by I. Stievenart (DG Member): 'Although for win95/98'

4002013A.exe Driver Digi International Device Type: Other Devices Supported OS: Win 2003 Server, Win XP Home, Win XP Pro, Win 2000 Workstation, Win 2000 Server, Win NT 4.0, Win NT 3.51, Win ME, Win 98SE, Win 98, Win 95, Win 3.11 File Size: 1.0 MB File Name: 4002013A.exe Overall Rating: (1 rating, 1 review) 32 Downloads Submitted Sep 9, 2003 by DriverGuide (DG Staff Member)

westell Driver Efficient Networks, Inc. Device Type: Modem / ISDN Supported OS: All Win 2000 File Size: 6.0 MB File Name: enternet300V141.exe Overall Rating: (9 ratings, 12 reviews) 1,595 Downloads Submitted Dec 13, 2001 by merlin (DG Member): 'hook up your dsl with this'

ALCATEL Speed Touch Home Driver Efficient Networks, Inc. Device Type: Network Devices Supported OS: Win 95 File Size: 6.8 MB File Name: EnterNet500v1.5rc1.exe Overall Rating: (20 ratings, 21 reviews) 1,366 Downloads Submitted Dec 5, 2003 by fja (DG Member): 'Speed touch Enternet driver for most MS-Windows OSLike it !!'

enternet300_v160.exe Driver Efficient Networks, Inc. Device Type: Network Devices Supported OS: Win 2003 Server, Win XP Home, Win XP Pro, Win 2000 Workstation, Win 2000 Server, Win NT 4.0, Win NT 3.51, Win ME, Win 98SE, Win 98, Win 95, Win 3.11 File Size: 7.2 MB File Name: enternet300_v160.exe Overall Rating: (16 ratings, 17 reviews) 2,438 Downloads Submitted Nov 4, 2003 by DriverGuide (DG Staff Member)