- USB-C Travel Dock with Power Pass-Through: DOCK412USZ. By downloading any of the files below, you acknowledge that you have read and accept the following agreements. RTL8153B Ethernet Driver (2.12.0) for Linux Kernal up to 4.15. RTL8153B Ethernet Driver (7.52) W7 Installation Program.
- Fix USB Drivers using Device manager. View our post on fixing USB Driver issues in Windows 8. Go to Menu Run; Type device manager in the text box; Select Device Manager; Find Universal Serial Bus controllers and expand the list; Right-click Unknown Device; Select Properties from the context-sensitive menu; Select Drivers; Click Update Driver.
Find compatible tech accessories for your laptop, tablet, & other devices. Search your device to find compatible docking stations, chargers, power tips, privacy screens and cable locks.
-->USB Device vendors use co-installers to update device firmware for devices that use inbox USB device drivers. However, co-installers are not supported by the new 'Universal INF' standard, which is a requirement on Windows 10. This poses a challenge to existing USB device firmware update process. This topic outlines a recommend way to update USB device firmware without a co-installer.
Requirements
The primary requirements from the USB device firmware update process are:
Seamless firmware update with no user interaction
Reliable recovery mechanism (for example, no bricking of devices)
Works on Windows 7 and later
Overview
USB devices like UVC cameras are released with in-field updatable firmware. There is no standard way to update the firmware today. One thing that is common to all existing update mechanism is that some custom software suite runs on the client and downloads the firmware to the device. Typically, as part of the device installation process, the firmware updating software suite is installed. The co-installer kick starts the firmware update process. The absence of co-installers on Windows 10 prevents device vendors from updating the firmware on these devices in the field.
The recommended way to circumvent the absence of a co-installer for the USB device firmware update scenario is to use a lower filter driver to the USB device that will kick start the firmware update process. During the AddDevice call, the filter driver will check the device firmware version and update the firmware if necessary.
Firmware update overview
When a USB device is plugged in to the system, the generic inbox driver is installed for the device. After the installation of the generic driver, the OS queries the Windows Update server for any vendor specific driver package availability and downloads it and installs the driver. The installed driver package will perform the firmware update.
There are two ways the firmware could be updated.
Firmware Update Filter Driver
- A vendor supplied lower filter driver that performs the firmware update.
Firmware Update Device Driver
A vendor supplied lower filter driver that puts the device in 'firmware update mode'.
The device enumerates as a firmware update device.
Vendor supplied firmware update driver will load against this device and updates the firmware.
Method 1: Firmware Update Filter Driver
In this method, a lower filter driver to the USB device driver will be installed as part of driver update process. This filter driver will perform the firmware update.
The driver update package on the Windows Update server will contain:
A firmware update WDF lower filter driver
An extension INF to install the firmware update WDF lower filter driver
The 'firmware.bin' file
While installing the driver update package, the firmware update WDF filter driver’s AddDevice routine will be called. From this routine, the WDF filter driver will get for the device firmware version from the device HW registry key. The device firmware should have placed the firmware version using the MSOS descriptor onto the device HW registry key.
If the device firmware version and the filter driver expected firmware version are different, or
The firmware version is not available in the device HW registry key
- Then, the filter driver will insert itself into the device stack by returning success to AddDevice callback.
Else, the filter driver will not insert itself into the device stack
- Because there is no necessity for updating the firmware as the device has the expected firmware.
When the EVT_WDF_DEVICE_D0_ENTRY callback of the WDF filter driver is called at a later point, the filter driver must register for device interface change notifications using CM_Register_Notification or IoRegisterPlugPlayNotification (UMDF or KMDF) to listen to the device interface class the USB device will register the device into. E.g. The firmware update filter driver for a RGB camera would register for KSCATEGORY_VIDEO_CAMERA. On receiving the notification, the filter driver should post a work-item that would perform the firmware update.
UMDF based firmware update drivers can use the device specific APIs or issue the control transfers directly to access the USB device to perform the firmware update. For example, the UMDF based filter driver for a camera would use Camera APIs to perform the firmware update.
KMDF based firmware update drivers can send the vendor specific commands to perform the firmware update.
On completion of flashing the firmware, the device must disconnect and reconnect to the bus. The device will be re-enumerated with new firmware.
The method of using a 'firmware update filter driver', is recommended for devices that have enough resources to hold two full firmware images (the update image and a backup image) on the device memory. The reason is if there were failures during downloading the updated firmware, the device can abandon the update and boot into its original firmware. Thus, not bricking the device.
Method 2: Firmware Update Device Driver
In this method, a lower filter driver to the USB device will be installed as part of the driver update process. This filter driver will send a command to the device to restart in firmware update mode, where the device exposes a firmware update interface. The driver for the firmware update interface will load and perform the firmware update.
The driver update package on Windows Update server for the device will contain:
A WDF lower filter driver that will place the device in firmware update mode
An extension INF to install the WDF lower filter driver
In addition to the driver update package, a separate Firmware Update Device Driver package will be present on Windows Update, with:
A WDF firmware update device driver and its INF, and
The 'firmware.bin' file.
While installing the driver update package, the WDF lower filter driver’s AddDevice routine will be called. From this routine, the filter driver will query for the device firmware version from the device HW registry key. The device firmware should have placed the 'firmware version', using the MSOS descriptor or the USB device’s extension INF, onto the device HW registry key.
If the device firmware version and the filter driver expected firmware versions are different or
The firmware version is not available in the device HW registry key
Then, the WDF filter driver will insert itself into the device stack.
Else, the WDF filter driver will not insert itself into the device stack
When the EVT_WDF_DEVICE_D0_ENTRY callback of the WDF filter driver is called at a later point, the filter driver will issue a vendor specific command to the device which will place it in firmware update mode. i.e. The device will disconnect and reconnect, exposing the firmware update interface.
The system will enumerate the firmware update device interface. A custom firmware update WDF driver supplied by the vendor, in the firmware update package, will be load for this firmware update interface. This driver will update the firmware.
When the EVT_WDF_DEVICE_D0_ENTRY callback of the WDF firmware update driver is called at a later point, the driver must post a work-item that would perform the firmware update.
On completion of flashing the firmware, the device must disconnect and reconnect to the bus. The device will be re-enumerated with new firmware.
This method is recommended for devices that cannot hold the updated and original firmware images due to shortage of memory on the device. The reason is if there were failures during downloading the updated firmware, the device can abandon the update and boot the device into its firmware update mode again and the firmware update can be retried. Thus, not bricking the device.
Recovery
The firmware update process can fail for various reasons. If that happens, when the device is enumerated again, the firmware update driver may try to update the firmware again and may fail again and this update process could end up in a loop. The firmware update driver must put an upper limit to the number of retries it can perform. When the firmware update retries gets beyond a threshold (for example, 3 retries) then the filter driver should not attempt to update the firmware again, until a new version of the driver is downloaded from WU. The firmware update driver may use the registry to persist the retry states.
At the end of device firmware update, we recommended the device reset itself and re-enumerate.
Both methods of firmware update, the device function must be stopped before performing the firmware update. This ensures there are no open handle to the device and avoids any OS restart requirement.
Sample INF
Updated 06/27/01
Warranty What is the Warranty on my USB Mobile Port Replicator?
Q. What is the Targus USB Mobile Port Replicator with Ethernet?
A. The Targus USB Mobile Port Replicator with Ethernet is the world’s smallest expansion hub that provides instant peripheral device attachment and Ethernet via a single USB connection to Windows 98/ME/2000 based computers.
Packaged in a small and attractive enclosure, the PA090U can fit any place on a desktop space.Add devices like mice, keyboards, joysticks, network, printers, PDAs, scanners, speakers, cameras, telephones and many more without rebooting your computer.
The PA090U features a self powered, stand alone USB hub (2 ports), Serial (DB-9) port, Parallel printer (DB-25) port, Mouse (PS/2) port, Keyboard (PS/2) port, Ethernet (10BaseT) port and power connection.An AC Adapter and software driver is included.
Q. Compatibility What are the System Requirements?
A. | Hardware: | Pentium Class CPU USB v1.1 Compliant Port |
| Operating System: | Windows 98 Windows ME Windows 2000 |
Drivers Argus Over Usb 3.0
Q. Installation I thought that USB was 'Plug & Play'. Why do I have to install drivers?
A. The USB and PS/2 ports on your USB Mobile Port Replicator with Ethernet are supported by the Windows 98, ME, and 2000 operating systems and do not require any additional drivers. However, drivers are required to recognize the Parallel, Serial and Ethernet ports and convert them to USB.
Q.Printer / Modem / Serial Device not recognized. How do I get my Printer, Modem or Serial Device to work?
A. Move the cursor to the My Computer icon and click the right mouse button. Click Properties to display the System Properties window. In Windows 98/ME, simply click the Device Manager tab. In Windows 2000, click on the Hardware tab and then click on the Device Manager box.
Check to see if there is a heading labeled 'Other Devices' . If so, follow the instructions below:
Highlight 'Targus Group Int'l USB Device' and click on the 'Remove' button.
Click the 'Refresh' button.
Windows will now begin the Add New Hardware Wizard. When prompted for a location for the drivers, insert the 'Targus USB Mobile Port Replicator with Ethernet' disk in your drive and Check the box next to 'Specify a Location' and enter the location as below:
For Windows 98/ME and 2000 users, type 'A:' (Where A: is the letter of your floppy drive)
Note: If there are two ports listed, you will need to repeat the steps above.
Q.Modem Connection My Modem still isn't recognized. How do I connect my modem?
A.When attaching a modem to the serial (RS232) port, verify that the port assigned to your modem matches the COM port assigned to the Serial Port on the Port Replicator. To check this: Go to Device Manager and check the COM port that is assigned to Serial on USB (COMx) under the heading Ports(COM&LPT), where 'x' is the COM port assignment. Device Manager can be reached by right-clicking on My Computer and choosing Properties. For Windows 98/ME users, simply click on the Device Manager tab. For Windows 2000 users, click on the Hardware tab and then click on the Device Manager box.
Q.Printer My Printer still isn't recognized. How do I get my printer to work?
A.If your printer is not recognized, click on Start, select Settings, then select Printers. Highlight your printer, right-click the mouse button and select Properties. If the assigned port is LPT1, in Windows 98/ME, change it to PB1284-1 (USB port). In Windows 2000, you will need to click the box next to USB001 Virtual printer port for USB.
Note: While the parallel port supports most printers, there are some older dot-matrix printers that will not work on the the USB Mobile Port Replicator. Also, some printers may not support Bi-Directional printing via the Mobile Port Replicator. To test this, highlight your printer, right-click the mouse button and select Properties. Click 'Details', 'Spool Settings' and click 'Disable Bi-Directional Support'. Click 'OK' a try to print again.
Q.Printer Port Can I connect Storage devices like my Zip drive or CD ROM to the Parallel port?
A. The Printer Port on the USB Mobile Port Replicator with Ethernet does not provide support for Storage devices.
Q.Printer Port Can I connect a scanner to the Parallel port?
A. The Parallel Port on the USB Mobile Port Replicator with Ethernet does not provide support for Parallel Scanners.
Q.Serial Port How do I connect my PDA to the Serial port?
A. When attaching a PDA cradle to the serial (RS232) port, verify that the port assigned to your HotSync and/or ActiveSync software is Serial USB (COMx).
The PA090 COM port assignment can be viewed by clicking START, SETTINGS, CONTROL PANEL, SYSTEM, clicking on the DEVICE MANAGER tab, clicking the '+' sign next to 'Ports (COM & LPT) and looking for a 'Serial on USB (COM#)' entry.
Palm Desktop Software: If you are having problems synching a Palm PDA, download and install the newest version of the Palm Desktop software, available at www.palm.com.
Q.General Troubleshooting Everything looks fine in my device manager, but a device is not recognized. What else can I do?
A.Step 1 - If a device attached to the expansion hub is not recognized, press and hold the Reset button until the lights flash. Verify that the device is now recognized. If not, proceed to step 2.
Step 2 - Detach all cables from the expansion hub. Plug in the AC Adapter. Connect the power cable to the power input jack. Plug in each device, one at a time. Verify that each device is recognized before plugging in the next one.
Step 3 - Plug the device into a different port on the expansion hub. If it is still not recognized, try plugging it into the USB port on your notebook computer.
Q.Can I attach other USB hubs to my USB Mobile Port Replicator with Ethernet?
A.Yes, as long as the other hubs have their own power supply.
Q.Do I need to carry the AC Adapter when I'm traveling?
A.We recommend using the AC Adapter to ensure trouble free use of all supported devices. The USB Mobile Port Replicator with Ethernet will supply up to 500Ma of power (total) to USB devices. This is enough to power most low power / low speed USB devices (like mice).
Q.Mouse The Screen scroller features of my mouse are not working properly, what's wrong?
A.If your mouse is attached to the PS/2 port, and the enhanced features are not working, you may need to disable the built-in mouse on your computer.
The PS/2 Port on the expansion hub is configured by the Operating System as a USB HID mouse. If your mouse software continues to look for the mouse on the computer's PS/2 port, the enhanced features may not be available and your mouse will function as a standard two button mouse.
If your mouse is attached to the serial port, the enhanced features (e.g. screen scrolling) may not be available. The mouse will function as a standard, two-button serial mouse.
Q.Green Question Marks I see green question marks next to some of the PA090U drivers in Windows ME when I check them in the Device Manager. Did something go wrong with the driver installation?
A.The PA090U is most likely working properly. The green question marks are a new addition in Windows ME and simply mean that Windows ME cannot verify that the best driver is installed for the device.
Q.Technical Support How can I get further assistance with the Targus USB Mobile Port Replicator with Ethernet?
A.
If you need additional assistance after reading the FAQ information:
Technical Support can be reached at www.targus.com/support or email: TechSupport@targus.com.
Or by phone at one of the numbers below:
North America: 8:00am to 6:00pm EST : 1-(800) 283-6325
Europe: Monday through Friday, 8 AM (08: 00) to 6 PM (18: 00) C. E. T.
Belgium + 32( 0) 02- 717- 2451
Denmark + 45( 0) 35- 25- 8751
France + 33( 0) 1- 64- 53- 9151
Germany + 49( 0) 21- 16- 579- 1151
Italy + 39( 0) 24- 827- 1151
Netherlands + 31( 0) 53- 484- 9470
Spain + 34( 0) 91- 745- 6221
Sweden + 46( 0) 8- 751- 4058
Switzerland + 41( 0) 1- 212- 0007
UK + 44( 0) 20- 7744- 0330
Eastern Europe and Others + 31( 0) 53- 484- 9479
Warranty
Targus warrants this product to be free from defects in materials and workmanship for one year. If your Targus USB Mobile Port Replicator with Ethernet is found to be defective within that time, Targus will repair or replace your Targus USB Mobile Port Replicator with Ethernet. This warranty does not cover damage from everyday wear and tear, or from transportation by a common carrier.
Under no conditions is Targus liable for any of the following: loss or damage to a computer; loss of, or damage to, programs, records, or data; and consequential or incidental damages, even if Targus is informed of their possibility.
Drivers Argus Over Usb Drivers
Warranty Registration at www.targus.com/product_registration.asp
Drivers Argus Over Usb Drive
Back to top