Regardless of protocol (RNDIS or CDC-ECM) you will need to have an INF file somewhere on your Windows system. This INF file can be installed seamlessly from Windows Update (the driver repository part of Windows Update), or it can be copied onto the system by the end user as part of a driver install package. The process is actually identical in both cases. In one case Windows Plug-n-Play support is looking for and downloading the driver installation kit and using it directly while in the other the user downloads the driver installation kit and tells Windows Plug-n-Play where the kit is unpacked.
Whether the RNDIS / USBLAN for Windows driver is from an OEM website download, from a CD, or from Windows Update, the contents of the driver installation kit will be almost identical, namely an INF file, one or more SYS files and a Catalog file (contains the signatures for the INF and .sys files). [The CD / website zip file may optionally have an additional README and possibly a setup.bat to run DPInst.exe.]
USBLAN from Windows Update Installs Seamlessly
Whether the RNDIS / USBLAN for Windows driver is from an OEM website download, from a CD, or from Windows Update, the contents of the driver installation kit will be almost identical, namely an INF file, one or more SYS files and a Catalog file (contains the signatures for the INF and .sys files). [The CD / website zip file may optionally have an additional README and possibly a setup.bat to run DPInst.exe.]
USBLAN from Windows Update Installs Seamlessly
For 99% of Windows 7 users who go with the Microsoft default OS setup and have an active internet connection (and a legal, activated copy of Windows!) Plug-N-Play will automatically find and install the Belcarra USBLAN driver. The user will see a small 'New Hardware Found' applet icon in the toolbar. This can be clicked on and will tell that Windows Update is being searched, etc.. No other user interaction should be required
The only time the user would need to interact with the system is:
• no Internet connection is available to the Windows host
• administrative policy set to dis-allow installation of drivers
• administrative policy set to dis-allow access to Windows Update
These are normal situations with installation of any device driver in Windows.
Belcarra Technologies’ USBLAN for Windows solution has been available from Windows Update since 2009. Device drivers cannot be published in Windows Update unless they have met the Windows Logo Program requirements, submitted to and signed by Microsoft. The phrase "silent install" refers to avoiding the "nag" screen Windows dialogue box scenario that will pop up if you attempt to install un-signed drivers or drivers not signed by Microsoft.
The only time the user would need to interact with the system is:
• no Internet connection is available to the Windows host
• administrative policy set to dis-allow installation of drivers
• administrative policy set to dis-allow access to Windows Update
These are normal situations with installation of any device driver in Windows.
Belcarra Technologies’ USBLAN for Windows solution has been available from Windows Update since 2009. Device drivers cannot be published in Windows Update unless they have met the Windows Logo Program requirements, submitted to and signed by Microsoft. The phrase "silent install" refers to avoiding the "nag" screen Windows dialogue box scenario that will pop up if you attempt to install un-signed drivers or drivers not signed by Microsoft.
