Loadingcore455

SAMSUNGUSBDriverforMobilePhones.exe The USB Driver for Windows is available for download on this page. You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB. Usb driver download - Best answers Download usb driver - Best answers Spvd-012.1 usb driver for windows 10 - Forum - Drivers.

• August 22, 2019 2.9.8

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.8	Released August 22, 2019	Type ZIP	Filesize 3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 controller Graphics card with 24 or 32 bit Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added several internal interfaces for particular sensors (J003).

• January 25, 2019 2.9.6

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.6	Released January 25, 2019	Type ZIP	Filesize 3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 controller Graphics card with 24 or 32 bit Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added missing Tonemapping Auto property.

• May 4, 2018 2.9.5

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.5	Released May 4, 2018	Type ZIP	Filesize 3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 controller Graphics card with 24 or 32 bit Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Enabled tonemapping for 8bit video formats, e.g. Y800, RGB24 and RGB32.

• November 21, 2017 2.9.4

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.4	Released November 21, 2017	Type ZIP	Filesize 3.2MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Repaired not working J003 mono sensor pattern fix on particular video formats. This driver version is the last that works in Windows XP.

• January 9, 2017 2.9.3

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.3	Released January 9, 2017	Type ZIP	Filesize 3.2MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added a pattern fix for J003 mono sensors.

• January 9, 2017 2.9.1

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.1	Released January 9, 2017	Type ZIP	Filesize 3.2MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed the driver signature Code 52 error on new Windows 10 v1607 systems.

• January 15, 2016 2.8.9

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.9	Released January 15, 2016	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Changed certificates so that the driver can also be installed in Vista.

• November 9, 2015 2.8.7

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.7	Released November 9, 2015	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed an error which can appear when using sharpness on older CPUs.

• October 20, 2015 2.8.5

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.5	Released October 20, 2015	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed a bug which can appear on LivePause call.

• July 15, 2015 2.8.0

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.0	Released July 15, 2015	Type ZIP	Filesize 2.4MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Support of DFK ECU010-L34 with serial number property. Added tone mapping.

• February 17, 2015 2.7.33

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.33	Released February 17, 2015	Type ZIP	Filesize 2.4MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog The Auto Focus Onepush Running flag now resets correctly after the auto focus has finished.

• February 5, 2015 2.7.32

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.32	Released February 5, 2015	Type ZIP	Filesize 2.4MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Video format MJPG (2592x1944) of DFK AFU050-L34 camera can now be used.

• January 14, 2015 2.7.31

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.31	Released January 14, 2015	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Support for IMX236 based cameras. Support for RGB64 color formats. Several performance improvements.

• June 6, 2014 2.7.9.1152

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.9.1152	Released June 6, 2014	Type ZIP	Filesize 2.1MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added new properties: Brightness, sharpness, de-noise, saturation, hue and contrast. Added new property: Highlight reduction. Added new property: White balance temperature controls. Pixelfix for Y16 cameras now works as expected. VideoControl_ExternalTrigger (DirectShow property) can now be set as expected.

• January 1, 2014 2.6.5.1014

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.6.5.1014	Released January 1, 2014	Type ZIP	Filesize 1.9MB
  Requirements Intel Pentium IV or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed missing auto-gain for DFK AFU130. Fixed focus when start value is out of auto_focus_range. Fixed problem with AUTOFOCUS_ROI_RIGHT: minimum possibly wrong. Fixed auto focus ROI not working for 21*UC cameras. Fixed crash on load/connect with certain cameras 22/72xUC. Fixed previous exposure settings not being loaded on reconnect. Complete reworking of internal property system. Fixed Windows XP driver load crash. Fixed drop counter to be accessible from DirectShow. Fixed Windows 8 problem with certain video formats needing converters with standard DirectShow filters (e.g. Y800, capturing to an Y800 avi file was not possible). Fixed a problem with Windows 8 usbxhci driver not allowing transfers larger then 4 MB.

• February 26, 2013 2.4.14.851

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.4.14.851	Released February 26, 2013	Type ZIP	Filesize 1.9MB
  Requirements Intel Pentium IV or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit) DirectX 9.0c or higher
  Changelog WHQL certification.

3gstick USB Devices Driver

In this topic, you will learn about how a WinUSB device is recognized in Windows 8.

The information in this topic applies to you if you are an OEM or independent hardware vendor (IHV) developing a device for which you want to use Winusb.sys as the function driver and want to load the driver automatically without having to provide a custom INF.

• WinUSB Device
  • WinUSB device installation by using the in-box Winusb.inf

3g Usb Internet

What is a WinUSB device

A WinUSB device is a Universal Serial Bus (USB) device whose firmware defines certain Microsoft operating system (OS) feature descriptors that report the compatible ID as 'WINUSB'.

The purpose of a WinUSB device is to enable Windows to load Winusb.sys as the device's function driver without a custom INF file. For a WinUSB device, you are not required to distribute INF files for your device, making the driver installation process simple for end users. Conversely, if you need to provide a custom INF, you should not define your device as a WinUSB device and specify the hardware ID of the device in the INF.

Microsoft provides Winusb.inf that contains information required by to install Winusb.sys as the device driver for a USB device.

Before Windows 8, to load Winusb.sys as the function driver, you needed to provide a custom INF. The custom INF specifies the device-specific hardware ID and also includes sections from the in-box Winusb.inf. Those sections are required for instantiating the service, copying inbox binaries, and registering a device interface GUID that applications required to find the device and talk to it. For information about writing a custom INF, see WinUSB (Winusb.sys) Installation.

In Windows 8, the in-box Winusb.inf file has been updated to enable Windows to automatically match the INF with a WinUSB device.

WinUSB device installation by using the in-box Winusb.inf

In Windows 8, the in-box Winusb.inf file has been updated. The INF includes an install section that references a compatible ID called 'USBMS_COMP_WINUSB'.

The updated INF also includes a new setup class called 'USBDevice'.

The 'USBDevice' setup class is available for those devices for which Microsoft does not provide an in-box driver. Typically, such devices do not belong to well-defined USB classes such as Audio, Bluetooth, and so on, and require a custom driver. If your device is a WinUSB device, most likely, the device does not belong to a USB class. Therefore, your device must be installed under 'USBDevice' setup class. The updated Winusb.inf facilitates that requirement.

About using the USBDevice class:

Do not use the 'USB' setup class for unclassified devices. That class is reserved for installing controllers, hubs, and composite devices. Misusing the 'USB' class can lead to significant reliability and performance issues. For unclassified devices, use 'USBDevice'.

In Windows 8, to use 'USBDevice' device class, simply add this to your INF:

In Device Manager you will see a new node USB Universal Serial Bus devices and your device appears under that node.

In Windows 7, in addition to the preceding lines, you need to create these registry settings in the INF:

In Device Manager, you will see your device appear under USB Universal Serial Bus devices. However, the device class description is derived from the registry setting specified in your INF.

-Eliyas Yakub, Microsoft Windows USB Core Team

Note that the 'USBDevice' class is not limited to WinUSB. If you have a custom driver for your device, you can use the 'USBDevice' setup class in the custom INF.

3gstick Usb Devices Driver Updater

During device enumeration, the USB driver stack reads the compatible ID from the device. If the compatible ID is 'WINUSB', Windows uses it as the device identifier and finds a match in the updated in-box Winusb.inf, and then loads Winusb.sys as the device's function driver.

This image is for a single interface MUTT device that is defined as a WinUSB device and as a result Winusb.sys gets loaded as the function driver for the device.

For versions of Windows earlier than Windows 8, the updated Winusb.inf is available through Windows Update. If your computer is configured to get driver update automatically, WinUSB driver will get installed without any user intervention by using the new INF package.

How to change the device description for a WinUSB device

For a WinUSB device, Device Manager shows 'WinUsb Device' as the device description. That string is derived from Winusb.inf. If there are multiple WinUSB devices, all devices get the same device description.

To uniquely identify and differentiate the device in Device Manager, Windows 8 provides a new property on a device class that instructs the system to give precedence to the device description reported by the device (in its iProduct string descriptor) over the description in the INF. The 'USBDevice' class defined in Windows 8 sets this property. In other words, when a device is installed under 'USBDevice' class, system queries the device for a device description and sets the Device Manager string to whatever is retrieved in the query. In that case, the device description provided in the INF is ignored. Notice the device description strings: 'MUTT' in the preceding image. The string is provided by the USB device in its product string descriptor.

The new class property is not supported on earlier versions of Windows. To have a customized device description on an earlier version of Windows, you have to write your own custom INF.

How to configure a WinUSB device

To identify a USB device as a WinUSB device, the device firmware must have Microsoft OS Descriptors. For information about the descriptors, see the specifications described here: Microsoft OS Descriptors.

Supporting extended feature descriptors

In order for the USB driver stack to know that the device supports extended feature descriptors, the device must define an OS string descriptor that is stored at string index 0xEE. During enumeration, the driver stack queries for the string descriptor. If the descriptor is present, the driver stack assumes that the device contains one or more OS feature descriptors and the data that is required to retrieve those feature descriptors.

The retrieved string descriptor has a bMS_VendorCode field value. The value indicates the vendor code that the USB driver stack must use to retrieve the extended feature descriptor.

For information about how to define an OS string descriptor, see 'The OS String Descriptor' in the specifications described here: Microsoft OS Descriptors.

Setting the compatible ID

An extended compat ID OS feature descriptor that is required to match the in-box Winusb.inf and load the WinUSB driver module.

The extended compat ID OS feature descriptor includes a header section followed by one or more function sections depending on whether the device is a composite or non-composite device. The header section specifies the length of the entire descriptor, number of function sections, and version number. For a non-composite device, the header is followed by one function section associated with the device’s only interface. The compatibleID field of that section must specify 'WINUSB' as the field value. For a composite device, there are multiple function sections. The compatibleID field of each function section must specify 'WINUSB'.

Registering a device interface GUID

An extended properties OS feature descriptor that is required to register its device interface GUID. The GUID is required to find the device from an application or service, configure the device, and perform I/O operations.

In previous versions of Windows, device interface GUID registration is done through the custom INF. Starting in Windows 8, your device should report the interface GUID by using extended properties OS feature descriptor.

The extended properties OS feature descriptor includes a header section that is followed by one or more custom property sections. The header section describes the entire extended properties descriptor, including its total length, the version number, and the number of custom property sections. To register the device interface GUID, add a custom property section that sets the bPropertyName field to 'DeviceInterfaceGUID' and wPropertyNameLength to 40 bytes. Generate a unique device interface GUID by using a GUID generator and set the bPropertyData field to that GUID, such as '{8FE6D4D7-49DD-41E7-9486-49AFC6BFE475}'. Note that the GUID is specified as a Unicode string and the length of the string is 78 bytes (including the null terminator).

During device enumeration, The USB driver stack then retrieves the DeviceInterfaceGUID value from the extended properties OS feature descriptor and registers the device in the device's hardware key. An application can retrieve the value by using SetupDiXxx APIs (See SetupDiOpenDevRegKey). For more information, see How to Access a USB Device by Using WinUSB Functions.

Enabling or disabling WinUSB power management features

Before Windows 8, to configure power management features of WinUSB, you had to write registry entry values in the HW.AddReg section of your custom INF.

In Windows 8, you can specify power settings in device. You can report values through the extended properties OS feature descriptor that enable or disable features in WinUSB for that device. There are two features that we can be configured: selective suspend and system wake. Selective suspend allows the device to enter low-power state when it is idle. System wake refers to the ability to a device to wake up a system when the system is in low-power state.

For information about power management features of WinUSB, see WinUSB Power Management.

For example, to enable selective suspend on the device, add a custom property section that sets the bPropertyName field to a Unicode string, 'DeviceIdleEnabled' and wPropertyNameLength to 36 bytes. Set the bPropertyData field to '0x00000001'. The property values are stored as little-endian 32-bit integers.

3gstick Usb Devices Drivers

During enumeration, the USB driver stack reads the extended properties feature descriptors and creates registry entries under this key:

3gstick Usb Devices Driver Vga

HKEY_LOCAL_MACHINESystemCurrentControlSetEnumUSB<Device Identifier><Instance Identifier>Device Parameters

This image shows sample settings for a WinUSB device.

Usb Memory Stick For Iphone

For additional examples, see the specifications on Microsoft OS Descriptors.

Usb 3g Dongle

Related topics