Altair USB Devices Driver
- Altair USB Devices Driver
- What Is A Usb Devices
- Best Usb Devices
- Kinds Of Usb Devices
- Altair Usb Devices Driver Updater
- Altair Usb Devices Driver Adapter
- Intel Android device USB driver, free download. Adds functionality in Windows for management of Android phone and tablet devices with an Intel Atom CPU chip installed. Includes tests and PC download for 32-bit/64-bit systems.
- PC Matic Pro is a set of revolutionary technologies that is empowering customers and businesses to secure and optimize the performance of their devices. Learn More Free Tools.
The Download Center provides a selection of Vimicro PC Camera drivers for download. Since different PC Camera manufacturers design their products differently, the Download Center can not guarantee to provide drivers for all products. Update the device driver. In the search box on the taskbar, enter device manager, then select Device Manager. Select a category to see names of devices, then right-click (or press and hold) the one you’d like to update. Select Search automatically for updated driver software. Select Update Driver. Reinstall the drivers for the device. Uninstalling and then reinstalling the drivers for the device is a likely solution to a Code 10 error. If a USB device is generating the Code 10 error, uninstall every device under the Universal Serial Bus controllers hardware category in Device Manager as part of the driver reinstall.
This section describes the generic WinUSB driver (Winusb.sys) and its user-mode component (Winusb.dll) provided by Microsoft for all USB devices.
In versions of Windows earlier than Windows XP with Service Pack 2 (SP2), all USB device drivers were required to operate in kernel mode. If you created a USB device for which the operating system did not have a native class driver, you had to write a kernel-mode device driver for your device.
Windows USB (WinUSB) is a generic driver for USB devices that was developed concurrently with the Windows Driver Frameworks (WDF) for Windows XP with SP2. The WinUSB architecture consists of a kernel-mode driver (Winusb.sys) and a user-mode dynamic link library (Winusb.dll) that exposes WinUSB functions. By using these functions, you can manage USB devices with user-mode software.
Winusb.sys is also a key part of the link between a UMDF function driver and the associated device. Winusb.sys is installed in the device's kernel-mode stack as an upper filter driver. An application communicates with the device's UMDF function driver to issue read, write, or device I/O control requests. The driver interacts with the framework, which passes the request to Winusb.sys. Winusb.sys then processes the request and passes it to the protocol drivers and ultimately to the device. Any response returns by the reverse path. Winusb.sys also serves as the device stack's Plug and Play and power owner.
Note WinUSB functions require Windows XP or later. You can use these functions in your C/C++ application to communicate with your USB device. Microsoft does not provide a managed API for WinUSB.
This section describes how to use WinUSB to communicate with your USB devices. The topics in this section provide guidelines about choosing the correct driver for your device, information about installing Winusb.sys as a USB device's function driver, and a detailed walkthrough with code examples that show how applications and USB devices communicate with each other.
This section includes the following topics:
Windows Support for WinUSB
The following table summarizes WinUSB support in different versions of Windows.
Windows Version | WinUSB support |
---|---|
Windows 10 and later | Yes² |
Windows 7 | Yes¹ |
Windows Server 2008 | Yes² |
Windows Vista | Yes² |
Windows Server 2003 | No |
Windows XP | Yes³ |
Windows 2000 | No |
Note Yes¹: All SKUs of this version of Windows support WinUSB on x86-based, x64-based, and Itanium-based systems.
Yes²: All SKUs of this version of Windows support WinUSB on x86-based and x64-based systems.
Yes³: All client SKUs of Windows XP with SP2 service packs support WinUSB. WinUSB is not native to Windows XP; it must be installed with the WinUSB co-installer.
No: WinUSB is not supported in this version of Windows.
USB Features Supported by WinUSB
The following table shows the high-level USB features that are supported by WinUSB in different versions of Windows.
Feature | Windows 8.1 and later | Windows 7/Vista/XP |
---|---|---|
Device I/O control requests | Supported | Supported |
Isochronous transfers | Supported | Not Supported |
Bulk, control, and interrupt transfers | Supported | Supported |
Selective suspend | Supported | Supported |
Remote wake | Supported | Supported |
Related topics
Installing the winusb drivers for the Topfield PVR
(Henry Haselgrove, 5/2/2011)This page describes the procedure for installing the winusb drivers for the Topfield PVR (standard definition models). For the context, please see the Antares homepage.
Method #1 -- Using the utility z4t (simplest method)
Download and run z4t.exe.
Depending on your version of windows, you might see a warning similar to the following. Click 'yes' to continue.
You'll see the following window appear:
Plug in your Topfield, if you haven't already, then click 'Install Driver'.
Depending on your version of windows, you might then see a window similar to the following. Click 'Install this driver software anyway' to continue.
When the installation is complete, the following window will appear. Click Close, then close the program completely. You can delete z4t.exe from your computer if you wish.
All done! You may now run Altair (providing you have Altair_1.250.exe and Aldarin's dll in the same folder), or Antares.
Method #2 -- Manually install the drivers
If you are comfortable manually installing device drivers, you can do it that way instead.Download and unzip the drivers : topfield-libusb-winusb.zip. Then, follow the procedure that is applicable to your version of Windows for manually installing drivers from a particular location.
Note that as a result of unzipping the file topfield-libusb-winusb.zip, a folder 'drivers' will be created. You need to specify this particular folder when you are installing the drivers. Don't select one of the inner directories, 'x86' or 'amd64'. The one appropriate for your machine will be installed automatically when you just specify the 'drivers' directory.