Belcarra USBLAN for Windows  


1.0 Driver Overview

 1.2    Address management and discovery

 1.3    Composite Function

2.0 Evaluation - Demo Driver

3.0      Installation Kit

Belcarra provides OEM licensees with two USBLAN for Windows kits.

3.1    Microsoft DIF and DPINST

Microsoft has created the Driver Installation Framework (DIF) API and, in particular the binary executable DPinst.exe, to allow simple addition of a properly signed driver to the driver store.  This executable comes in 32-bit and 64-bit variants and is redistributable as part of the installation kit.

Belcarra USBLAN instal packages select versions of NDIS to match with the version of Windows. A simple wrapper batch file (setup.bat) determines which version of dpinst to run and which directory contains the best match for the running operating system.

3.2     Installation Scenarios

When a new device is connected, Windows first looks for a driver in the driver store.  
If DPInst was run earlier for a new driver, but no matching device had yet been connected, then we say that driver has been pre-installed (awaiting later use).

If a device has already been connected but no driver has been found for it, then DPInst can enlarge the search.  

3.1.1   Local Installation

Either of these possibilities can be triggered by a local installation, meaning that a kit is downloaded to the target machine, unpacked, and the setup.bat file is run

3.1.2   Windows Update

Alternatively, and much more convenient for end users, Windows can search on the internet (Microsoft Driver Distribution Service) for a driver. On the Windows side, this is known as Windows Update.

For Windows 10 USBLAN driver, availability from Windows Update is a standard elected deliverable.
For Windows 8.1 and Windows 7, USBLAN can be made available from Windows Update using a DUA (Driver Update Acceptable) procedure

3.1.3   Directed Install

The driver can be installed directly from a directory.

If Windows fails to find the driver (not in Windows Update, not found in the local driver store),  then it will mark the USB device as not installed.  Windows will create an entry for it in the device manager, but with a yellow triangle indicating that no driver was found.  The user can then direct the Device Manager to use a driver from a specific directory --- the location where the USBLAN ZIP file has been unpacked.  

Windows XP requires the user to navigate to the exact directory containing the matching driver.  Windows 7, Windows 8.1 and Windows 10 match on any directory containing a matching driver, i.e. the top-level directory of the extracted USBLAN ZIP archive.

Once a matching driver directory is found, Windows will then allow installation to proceed.   If the same driver has already been installed, then Windows will issue a message that no better driver is available.

Download for USBLAN 2.4.11

4.0  OEM Kit Customization

5.0  Driver Operation

6.0  Debug

Copyright ©2005 - 2016 Belcarra Technologies (2005) Corp