1. Drivers Atel Usb Devices Wireless Adapter
2. Drivers Atel Usb Devices Adapter

Locate Universal Serial Bus Controllers Apple Mobile Device USB Driver. It is also possible the device may show under Imaging Devices, Portable Devices, Other Devices or as an MTB USB Device. Right-click and select Update Driver Software. Select the “Let me pick from a list of device drivers on my computer” option. Select “Show All Devices” in the drop-down menu. Click on “Have Disk” option. Enter the storage location for the Google USB driver. Click on “Android ADB Interface” from the list. Confirm the Android USB driver installation by pressing the “Yes. Unlock your device and connect to a PC using a USB cable (you may use the cable attached to your LG charger). Once connected, you may be prompted on your phone to select a USB connection type, select Media sync (MTP) or File Transfer. 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. If Windows doesn't find a new driver, you can try looking for one on the device manufacturer's website and follow their instructions. Reinstall the device driver.

Unpacking the .zip archive:

You will need to unzip the downloaded file in the location you have chosen to hold the executable files (perhaps somewhere like bin). I would NOT put them in Program Files, since spaces in directory or file names and command line environments are a very bad mix, and will cause you endless problems. The archive will create a top level directory Argyll_VX.X.X, where X.X.X is the version number, and the executables will be in Argyll_VX.X.Xbin.

Making the tools accessible:

You should also configure your %PATH% environment variable to give access to the executables from your command line environment.
For Windows 8, 8.1 & 10, look in
Desktop -> Settings -> Control Panel -> System And Security -> System -> Advanced System Settings -> Environment Variables
For Windows 7, look in
Start Menu -> Control Panel -> System And Security -> System -> Change Settings -> Advanced -> Environment Variables
For Vista, look in
Start Menu -> Control Panel -> System And Maintenance -> System -> Change Settings -> Advanced -> Environment Variables
For XP and 2000 look in
Start->Settings->Control Panel->System->Advanced->Environment Variables
For NT 4 look in
Start->Settings->Control Panel->System->Environment
You want to add the directory you've chosen to your %PATH%, which is a System Variable. Normally you would add this to the end of the current setting, separated by a ';'.
So if the current value of PATH is '%SystemRoot%system32;%SystemRoot%' and you unpacked Argyll version 1.8.0 in d:bin, then you would modify PATH to be '%SystemRoot%system32;%SystemRoot%;d:binArgyll_V1.8.0bin', - i.e. you append the path to the Argyll binaries to your PATH, separated by the ';' character. The change will take effect when you start a new command shell, which you start from Start Menu->Accessories->Command Prompt, or Start Menu->Programs->Accessories->Command Prompt. You can check that the environment variable has been set by running the command 'echo %PATH%' in the command shell.
The .zip file also contains several useful reference files (such as scanner chart recognition templates, sample illumination spectrum etc.) in the ref sub-directory, all the current documentation in a doc sub-directory, and instrument USB drivers in the usb directory.
NOTE: Vista 64/Windows 7, 8,8.1 & 10 64 bit and Beep prompt: Microsoft (in its infinite wisdom) has removed the built in speaker driver, and now relies on systems having a sound card and speakers's installed and turned on to hear system beeps. So if you're wondering where the beeps have gone when using chartread, now you know.
NOTE: Microsofts generic VGA Driver does not appear to support setting the display VideoLUTs. You will need to install a display driver for your specific display hardware to enable this. Note that it is possible in many cases to use Windows 7 video drivers on Windows 8 systems.

NOTE that if you wish to use Argyll tools (dispwin) to control display calibration, that you will have to disable any other display calibration loader programs.
There are other programs that will interfere with calibration loading, such as igfxpers.exe that gets installed with nVidia 'Optimus' technology.
You may have to disable both the igfx tray module (c:windowssystem32igfxtray.exe) and the igfxpph Module (c:windowssystem32igfxpph.dll) in addition to the persistence Module (c:windowssystem32igfxpers.exe).
A good tool for this is AutoRuns. Note that the igfxpph module may exist in several locations and you have to disable all of them. Reboot after changing settings.

Serial Instruments:

If you are using a serial connected instrument, then there is nothing special to do to enable this.

USB Instruments:

If you are using a USB connected instrument, then suitable USB system drivers may need to be installed.

Note that the Huey, i1 Display Pro, ColorMunki Display and ColorHug colorimeter appears as an HID (USB Human Interface Device Class) device, and hence will be assigned to the default MSWindows HID driver. You therefore don't need to install an Argyll usb system driver for these instruments, although it is possible to select the libusb0.sys driver as an alternative to the default HID driver.
If you are using the JETI specbos 1211, 1201, 1511, 1501 and the Klien K10A then you may need to install the FTDI Virtual COM Port Drivers (VCP), if they are not already on your system. You may have to update to the latest FTDI driver to work with the FTDI FT231XS chip that the JETI specbos 1511, 1501 use.
Jump to your operating system version:
Windows 8, 8.1 & 10
Windows 7
Windows Vista
Windows XP
Windows 2000
Windows 8, 8.1 & 10
Fresh Install of Instrument USB driver:
If you currently don't have any applications that talk to your instrument using USB, then it is relatively simple to use the drivers provided with Argyll, since you don't have to deal with the instrument already having an assigned driver.
Windows 8/8.1/10 does not automatically pop up a 'New Hardware' dialog, so you will have to open the Device Manager manually, and you will also have to temporarily disable UBS driver .inf signature enforcement.
Please NOTE that on some versions of Windows 10, you may have to temporarily disable secure boot in your UEFI BIOS to be able to Disable Driver Signature Enforcement.
To install the Argyll driver for the first instrument:
Settings -> Power -> Hold Shift Key down and click 'Restart' -> Troubleshoot -> Advanced Options -> Startup Settings -> Restart ->
(After Reboot) -> 'Disable Driver Signature Enforcement' (number 7 on the list)
(After system starts, Plug in instrument)
Desktop -> Settings -> Control Panel -> Hardware and Sound -> Device Manager ->
Other Devices -> <instrument being installed> -> right click -> Update Driver Software... -> Browse my computer for driver software -> Browse...
-> argyllusb folder -> Next -> Install this driver software anyway -> Close
On subsequent installation of other supported instrument types:
Simply plug the instrument in. The Argyll driver will be automatically selected.
Using Argyll drivers with existing OEM drivers:
If you currently have applications other than Argyll accessing your USB connected instrument, then you will have to manually install the Argyll driver, and then switch back and forth between the Argyll and other drivers if you want to switch between applications.
To install the Argyll Driver:
Settings -> Power -> Hold Shift Key down and click 'Restart' -> Troubleshoot -> Advanced Options -> Startup Settings -> Restart ->
(After Reboot) -> Disable Driver Signature Enforcement' (number 7 on the list)
(After system starts, Plug in instrument)
Desktop -> Settings -> Control Panel -> Hardware and Sound -> Device Manager
(Locate the instrument in the device list. It may be underneath one of the top level items.)
Right click on instrument -> Update Driver Software... -> let me pick from a list of device drivers on my computer -> Have disk... -> Browse...
-> argyllusb folder -> select ArgyllCMS.inf -> Open -> OK -> Install this driver software anyway -> Close
To switch between drivers:
(Plug in the instrument)
Desktop -> Settings -> Control Panel -> Hardware and Sound -> Device Manager
(Locate the instrument in the device list. It may be underneath one of the top level items.)
Right click on instrument -> Update Driver Software... -> let me pick from a list of device drivers on my computer
(Choose either the Argyll driver or another driver from the list)
-> Next -> Close
Un-installing Argyll driver:
If you are updating to a new version of Argyll which adds support for a new instrument that you want to use, then it may be necessary to uninstall all the existing Argyll USB driver and do a fresh re-install to update the relevant libusb system driver and .inf file. (This is true for updating to Argyll Version 2.0.0).
(Plug in the instrument)
Desktop -> Settings -> Control Panel -> Hardware and Sound -> Device Manager
(Locate the instrument in the device list. It will be underneath the Argyll LibUSB-win32 devices top level item.)
Right click on instrument -> Uninstall -> click 'Delete the driver software for this device' -> OK
Proceed then with either Fresh Install of Argyll USB driver or Adding Argyll drivers to existing drivers above.
Windows Vista & Windows 7
Fresh Install of Instrument USB driver:
If you currently don't have any applications that talk to your instrument using USB, then it is relatively simple to use the drivers provided with Argyll since you don't have to deal with the instrument already having an assigned driver.
To install the Argyll driver for the first instrument:
(Plug in instrument)
(Wait for the 'Found New Hardware' or 'Installing new device driver software - Device driver software was not successfully installed' popup and dismiss it)
Start -> Control Panel -> Hardware and Sound -> Device Manager ->
Other Devices -> <instrument being installed> -> right click -> Update Driver Software... -> Browse my computer for driver software -> Browse...
-> argyllusb folder -> Next -> Install this driver software anyway -> Close
On subsequent installation of other instrument types:
Simply plug the instrument in. The Argyll driver will be automatically installed.
Using Argyll drivers with existing OEM drivers:
If you currently have applications other than Argyll accessing your USB connected instrument, then you will have to manually install the Argyll driver, and then switch back and forth between the Argyll and other drivers if you want to switch between applications.
To install the Argyll Driver:
(Plug in instrument)
Start -> Control Panel -> Hardware and Sound -> Device Manager
(Locate the instrument in the device list. It may be underneath one of the top level items.)
Right click on instrument -> Update Driver Software... -> let me pick from a list of device drivers on my computer -> Have disk... -> Browse...
-> argyllusb folder -> select ArgyllCMS.inf -> Open -> OK -> Install this driver software anyway -> Close
To switch between drivers:
(Plug in the instrument)
Start -> Control Panel -> Hardware and Sound -> Device Manager
(Locate the instrument in the device list. It may be underneath one of the top level items.)
Right click on instrument -> Update Driver Software... -> let me pick from a list of device drivers on my computer
(Choose either the Argyll driver or another driver from the list)

Drivers Atel Usb Devices Wireless Adapter

-> Next -> Close
Un-installing Argyll driver:
If you are updating to a new version of Argyll which adds support for a new instrument that you want to use, then it may be necessary to uninstall all the existing Argyll USB driver and do a fresh re-install to update the relevant libusb system driver and .inf file. (This is true for updating to Argyll Version 2.0.0).
(Plug in the instrument)
Start -> Control Panel -> Hardware and Sound -> Device Manager
(Locate the instrument in the device list. It will be underneath the Argyll LibUSB-win32 devices top level item.)
Right click on instrument -> Uninstall -> click 'Delete the driver software for this device' -> OK
Proceed then with either Fresh Install of Argyll USB driver or Adding Argyll drivers to existing drivers above.
Windows XP
Fresh Install of Instrument USB driver:
If you currently don't have any applications that talk to your instrument using USB, then it is relatively simple to use the drivers provided with Argyll since you don't have to deal with the instrument already having an assigned driver.
To install the Argyll driver for the first instrument:
(Plug in instrument)
(Wait for the 'Welcome to the Found New Hardware Wizard' popups and dismiss it)
My Computer, Right Click -> Manage -> Device Manager
Other Devices -> <instrument being installed> -> right click -> Update Driver... -> No, not this time -> Next
->Install from a list or specific location (Advanced) -> Next -> Don't search. I will choose the driver to install -> Next
-> Have Disk... -> Browse -> argyllusb folder -> ArgyllCMS.inf -> Open -> OK -> Next -> Finish
On subsequent installation of other instrument types:
(Plug the instrument in, and wait for the 'Welcome to the Found New Hardware Wizard' to pop up.)
No, not this time -> Install the software automatically (Recommended) -> Next -> Finish
Using Argyll drivers with existing OEM drivers:
If you currently have applications other than Argyll accessing your USB connected instrument, then you will have to manually install the Argyll driver, and then switch back and forth between the Argyll and other drivers if you want to switch between applications.
To install the Argyll Driver:
(Plug in instrument)
My Computer, Right Click -> Manage -> Device Manager
(Locate the instrument in the device list. It may be underneath one of the top level items.)
Right click on instrument -> right click -> Update Driver... -> No, not this time -> Next
->Install from a list or specific location (Advanced) -> Next -> Don't search. I will choose the driver to install -> Next
-> Have Disk... -> Browse -> argyllusb folder -> ArgyllCMS.inf -> Open -> OK -> Next -> Finish
To switch between drivers:
(Plug in the instrument)
My Computer, Right Click -> Manage -> Device Manager
(Locate the instrument in the device list. It may be underneath one of the top level items.)
Right click on instrument -> Update Driver... -> No, not this time -> Next
->Install from a list or specific location (Advanced) -> Next -> Don't search. I will choose the driver to install -> Next
->let me pick from a list of device drivers on my computer

Drivers Atel Usb Devices Adapter

(Choose either the Argyll driver or another driver from the list)
-> Next -> Finish
Un-installing Argyll driver:
If you are updating to a new version of Argyll which adds support for a new instrument that you want to use, then it may be necessary to uninstall all the existing Argyll USB driver and do a fresh re-install to update the relevant libusb system driver and .inf file. (This is true for updating to Argyll Version 2.0.0).
(Plug in the instrument)
My Computer, Right Click -> Manage -> Device Manager
(Locate the instrument in the device list. It will be underneath the Argyll LibUSB-win32 devices top level item.)
Right click on instrument -> Uninstall -> click 'Delete the driver software for this device' -> OK
Then you will have to delete the cached copy of the old Argyll driver .inf files, that MSWindows keeps.
cd to where Windows keeps it's cached driver information files, ie:
c:
cd windowsinf
identify all the system copies of the Argyll .inf files:
find /I 'ArgyllCMS' oem*.inf
then delete just the files that contain 'ArgyllCMS':
del /F oemXXX.inf
del /F oemXXY.inf
etc.
Proceed then with either Fresh Install of Argyll USB driver or Adding Argyll drivers to existing drivers above.
Windows 2000
Fresh Install of Instrument USB driver:
If you currently don't have any applications that talk to your instrument using USB, then it is relatively simple to use the drivers provided with Argyll since you don't have to deal with the instrument already having an assigned driver.
To install the Argyll driver for the first instrument:
(Plug in instrument)
(Wait for the 'Welcome to the Found New Hardware Wizard' pops up) -> Next
-> Search for a suitable driver for my device (recommended) -> Next -> Specify a location -> Next
-> Browse -> argyllusb folder -> ArgyllCMS.inf -> Open -> OK -> Next -> Finish
On subsequent installation of other instrument types:
Simply plug the instrument in. The Argyll driver will be automatically installed.
Using Argyll drivers with existing OEM drivers:
If you currently have applications other than Argyll accessing your USB connected instrument, then you will have to manually install the Argyll driver, and then switch back and forth between the Argyll and other drivers if you want to switch between applications.
To install the Argyll Driver:
(Plug in instrument)
My Computer, Right Click -> Manage -> Device Manager
(Locate the instrument in the device list. It may be underneath one of the top level items.)
Right click on instrument -> Properties -> Driver -> Update Driver this time
-> 'Welcome to the Found New Hardware Wizard' -> Next -> Display a list of known drivers for this device so that I can choose a specific driver -> Next
-> Have Disk -> Browse -> argyllusb folder -> ArgyllCMS.inf -> Open -> OK -> Next -> Next -> Finish
To switch between drivers:
(Plug in instrument)
My Computer, Right Click -> Manage -> Device Manager
(Locate the instrument in the device list. It may be underneath one of the top level items.)
Right click on instrument -> Properties -> Driver -> Update Driver... -> Next
-> Display a list of known drivers for this device so that I can choose a specific driver -> Next
(Choose either the Argyll driver or another driver from the list)
-> Next -> Next -> Finish
Un-installing Argyll driver:
If you are updating to a new version of Argyll which adds support for a new instrument that you want to use, then it may be necessary to uninstall all the existing Argyll USB driver and do a fresh re-install to update the relevant libusb system driver and .inf file. (This is true for updating to Argyll Version 2.0.0).
(Plug in the instrument)
My Computer, Right Click -> Manage -> Device Manager
(Locate the instrument in the device list. It may be underneath one of the top level items.)
Right click on instrument -> Uninstall -> OK
Then you will have to delete the cached copy of the old Argyll driver .inf files, that MSWindows keeps.
cd to where Windows keeps it's cached driver information files, ie:
c:
cd winntinf
identify all the system copies of the Argyll .inf files:
find /I 'ArgyllCMS' oem*.inf
then delete just the files that contain 'ArgyllCMS':
del /F oemXXX.inf
del /F oemXXY.inf
etc.
Proceed then with either Fresh Install of Argyll USB driver or Adding Argyll drivers to existing drivers above.

• 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.