1. Download Proline Port Devices Driver Bits
2. Download Proline Port Devices Driver Installer
3. Download Proline Port Devices Driver Ed
4. Download Proline Port Devices Drivers
5. Download Proline Port Devices Driver Windows 7
6. Download Proline Port Devices Driver Updater

A library of over 250,000 device drivers, firmware, BIOS and utilities for Windows. A library of over 250,000 device drivers, firmware, BIOS and utilities for Windows.

-->

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.

Example of a driver pair

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)

Download Proline Port Devices Driver Bits

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

Click desired heading below to view topic and access downloads.

Element Instructions v1.03.10 and earlier:

1. Download appropriate firmware file
2. Connect Element to computer with USB cable. Element shows up as a drive
3. Copy firmware file to directory 'update' on the Element drive
4. Disconnect USB according to computer OS (Eject or Disconnect safely)
5. Turn Element on
6. Confirm question 'Update?' with the OK key
7. The Element goes through the update routine and then turns itself off

The firmware file remains in the 'update' folder after the update, but its ending changes from .upg to _pg. If you change the ending back to .upg, this file will be offered for installation again the next time you turn the Element on. If multiple files with the ending .upg exist in the 'update' directory, only the newest one will be offered for installation. Subsequent to installing the v1.04.13 below, Element Update utility is placed in the mass storage of the Element. Future firmware updates can be automatically installed by launching the utility and following the steps below.
Element v1.04.17
Element Instructions v1.03.10 and later:

Download Proline Port Devices Driver Installer

1. Connect Flytec Element to computer with USB cable - the Element shows up as a drive ELEMENT
2. Open the drive ELEMENT and open the utility Element Update
3. The programme connects to our server, checks to see if newer software is available. In that case, it downloads the update automatically and copies it to the 'update' folder on the Element drive
4. Disconnect USB (depending on operating system, chose 'eject' or 'disconnect safely')
5. Turn Element on
6. Confirm question 'Update?' with the OK key
7. The Element goes through the update routine and then turns itself off

SensBox Instructions:
Download new firmware (FSfc.xxxx.upg file) from this page and transfer to the System folder on the SensBox SD card (this can be done directly to the SD card or via the USB connection). To activate the new firmware, hold the OK button while short pressing the power button. The SensBox will turn ON and the display will show UPG with a moving segment to indicate the upgrade is in progress. After the firmware update is complete, the SensBox will automatically switch off. Warning: Only one firmware file is allowed in the system folder, otherwise an error message Err will appear when initiating the upgrade sequence above.
SensBox v3.02
This version combines flight and logger functionality into one firmware. With this version, press power key to start-up SensBox, chose between 'FLY' (flight mode) and 'LOG' (data logger mode) with ↑ or ↓ keys and confirm by pressing OK key. In flight mode the flight is recorded as an IGC file in the Tracks directory on the SD card. In logger mode, logging is started with a press of the Start key and stoped with a press of the Stop key (confirmed with a press of the OK key). This creates a CSV file in the Logs directory.

Download Proline Port Devices Driver Ed

SensBox v3.02
Release Notes
6000 series (Windows only)
Firmware for 6000 series includes built-in flasher utility. Click download and then click 'run' in the File Download window, click 'Run' in the Security Window, plug in the instrument (unit must be off), click 'Update' in the Flasher Window. NOTE: Appropriate USB driver (above) must be installed before attempting this update. If you installed FlyChart above, the USB driver should have automatically installed in your system.
Important: Prior to installing new firmware you should download and/or save any user data that you want to preserve (i.e., flights, waypoint/routes, airspace, instrument configuration). After installing new firmware it is recommended that you reinitialize the instrument.

6015 v1.3.07
After upgrading from firmware v1.1.xx to v1.2.02 (or later) it is essential that the 6015 flight memory be cleared (Menu>Flight Mem> Delete). Failure to to do this will result in problems downloading flights to FlyChart and other flight evaluation software.
Release Notes

6020 v5.00b
Release Notes

6030 v3.38m

Download Proline Port Devices Drivers

Important: Installing this version will erase the 6030 flight memory. Please download/save your flight data before proceeding with this update! If you have difficulty submitting an IGC file (e.g., date or signature error) please send an email to info@flytec.ch with the affected flight and the date on which it was flown. The IGC file will be repaired and returned.

Download Proline Port Devices Driver Windows 7

Release Notes

6030 v5.03b
Important: Installing this version will erase the 6030 flight memory. Please download/save your flight data before proceeding with this update! If you have difficulty submitting an IGC file (e.g., date or signature error) please send an email to info@flytec.ch with the affected flight and the date on which it was flown. The IGC file will be repaired and returned.
Release Notes
6040 v3.07a
Release Notes

5000 series (Windows only)
Updating firmware on the 5020/5030 requires the use of a firmware update tool above. The tools are specific so be certain to use the correct one for your instument. If your PC does not have a COM port you will need to use a serial to USB adapter. Adapters based on the Prolific PL2303 chipset are recommended. Make sure you load the correct driver from the manufacturer and not from Windows. The USB drivers above are from Prolific.
Important: Prior to installing new firmware you should download and/or save any user data that you want to preserve (i.e., flights, waypoint/routes, airspace, instrument configuration). After installing new firmware it is recommended that you reinitialize the instrument.
5020 v1.22
Release Notes
5030 v2.27
Release Notes
Updating firmware on the 5030 requires the use of the firmware update tool below. If your PC does not have a COM port you will need to use a serial to USB adapter. Adapters based on the Prolific PL2303 chipset are recommended. Make sure you load the correct driver from the manufacturer and not from Microsoft. Important: Prior to installing new firmware you should download and/or save any user data that you want to preserve (i.e., flights, waypoint/routes, airspace, instrument configuration). After installing new firmware,it is recommended that you reinitialize the instrument.
5030 Firmware Update Tool

Download Proline Port Devices Driver Updater