TKOTOUCH - Touchscreen Driver
Current Version 1.23a
Copyright © 2004 TouchKO, Inc.
All rights reserved.
INSTALLATION/SETUP
FIRST STEP
The first step is to run 'setup.exe' in the provided archive.
After this has run you may connect the controller to either a COM
port (1-9) or to a USB port on the target computer.
(Multi-Monitor users should read the Multi-Monitor section
below before completing this step; only one install is necessary,
but the touch controllers should be connected one at a time.)
In addition, a power source should be connected to the
controller and the controller should be connected to the
touchscreen. Do not plug in the USB connector before
running the install program... if you have done so, you'll
need to unplug it, wait 15 seconds, then plug it back in
in order for the driver software to recognize it again.
During installation you will be prompted for the default
controller mode. TouchKO controllers can emulate both
ELO 2210 and MicroTouch MTS Tablet modes; the operating
modes can be changed at any time after installation via
the Advanced Settings screen. Normally we recommend the
MTS mode, since it has faster response. During install
you will be prompted for the default mode; this mode
is invoked via a '-e' command line parameter for ELO
default, or no '-e' switch for MTS default. This command
line is installed in the shortcut placed in your Startup
folder; if the program is run without using that shortcut,
the default will revert to MTS. This is important only
for the Setup mode, typically run only once, during
Installation. A new mode, TKO Fast Mode, is now available
to support our new resistive controller. This mode will
result in operation at 38Kbaud, with first touch response
at less than 2mS (CTR-N45 controller required).
USE SETUP MODE FOR EASY INSTALL
Once the install has run the Setup Screen will be displayed.
If the controller is plugged in and powered up, you should
go ahead and choose Setup. Follow the prompts to find and
configure your controller, calibrate, and save changes.
If you will be setting up multiple touchscreens on this
computer, read the MULTI-MONITOR section below.
If you plan on using another driver instead of TKOTouch you
must first complete Find Touch in order to set the controller mode.
Then you may set Controller Emulation to match your driver.
Then select Main/Exit in the top menu to exit this application,
then invoke your other driver. The controller will remember its
mode settings when powered down, there is no need to Save
Settings. You should remove the TKO shortcut from Programs/Startup,
since this will run the program at every computer restart.
Although our controller factory defaults to ELO mode, don't take
for granted that the software is telling you the controller
configuration; it is not. You should switch from ELO to MTS,
then back to ELO, to confirm that the controller is in ELO mode.
If you have a choice in the mode to be used, MTS is preferable
for speed and smoothness of response as well as for the amount
of options available. TKO Fast Mode is equivalent to MTS mode,
but requires the new controller for operation.
TOUCH PANEL CONNECTION REVERSED
During installation the driver software may find that the
connection to the touchscreen panel is reversed; if so, it
will automatically compensate for it (during calibration)
and post messages to the Advanced Settings TTY window.
You may continue to operate in the reversed mode with no
ill effects, but this may become a concern if you change
to a different controller brand or software driver.
NOTES FOR WINXP INSTALLATIONS
Due to a system concern within XP there will be no touch available
during the Login/Logout dialog. Contact TouchKO (www.touchKO.com)
about obtaining a kernel-mode driver if this is an issue.
NOTES FOR WIN98 INSTALLATIONS
Whenever Ctrl-Alt-Delete is pressed, touch will be disabled (as
it will on other Windows installations) but the touch commands
issued during this period are stored and executed when the
Close Program dialog closes. This is a quirk of Windows 98
and is unavoidable; it is recommended that you don't touch
the screen during the Close Program dialog.
NOTES FOR OLDER USB CONTROLLERS
Early TKO controllers used FTDI USB chips; these drivers
are no longer installed by default. Should the Cygnal
USB drivers not work for your installation, you may have
an older controller installed in your touch monitor.
Simply point the Found New Hardware wizard at the
directory "C:/Program Files/TouchKO, Inc./Touch Screen Driver/
USB Driver Files" and it will find the drivers necessary.
There are two drivers, so the wizard will come up twice;
give it the same info both times.
UNINSTALLATION
TOUCHKO
Should you find it necessary to un-install the driver, use the
Add/Remove Programs option in Control Panel. Find TouchKO
Touch Screen Driver and select Change/Remove. An InstallShield
wizard will start and guide you through the un-installation.
FTDI or CYGNAL
If you are un-installing a USB installation at some point you
will see the USB uninstaller application come up. This removes
the drivers and registry entries for the USB-to-Serial
Converter. Unplug the USB connector before selecting 'Continue'.
If you have another FTDI or Cygnal device installed, don't uninstall the
USB drivers when the option is given, or you'll be prompted to
re-install them.
ADVANCED SETTINGS
Advanced Settings may be disabled during install; if the button
is 'greyed out' then contact your support person for instructions.
MAIN
The Find Touch, Calibrate, and Save Settings button functions
(described below) are duplicated here. Exit will cause this
application to quit, removing the icon from the lower right
of the screen. Reset Install will delete the data file and
restart, behaving as a new installation (restores defaults).
Multi-Point Calibration will start a complete cal sequence
for a MP-capable controller, if installed (and enabled, contact
your Support person for details).
PORT
Connect or Disconnect the communication port selected in the
Port Combo box under Communication Controls. Flow Control and
Timeout (described below) settings are available here.
CALIBRATE
Calibrate opens a three point calibration window. The
touchscreen must be calibrated to align the touch X and Y
data to the video screen. This duplicates the Calibrate
button function (described below).
CONTROLLER EMULATION
ELO2210 forces connected TKO controller into EloTouch 2210
compatibility mode (10 byte data packets). MTS TABLET
forces connected TKO controller into MicroTouch tablet
format, stream mode (5 byte data packets). TKO Fast
mode is the same format as MTS, but puts both controller
and driver into 38.4kBaud mode. The Controller Emulation
is now available only via the Menu.
For these emulations to be set, FIND TOUCH must first be
completed successfully. These menu options also change
the software mode to match.
MULTI-MONITOR/MULTI-TOUCH
The Settings choice opens the Multi-Monitor Support dialog.
Multi-monitor support is enabled for expanded desktop mode only.
The left box is the Array setup; this is where you enter how
many monitors are in the horizontal and vertical axes of
your setup. The right box allows you to set the index
of this particular touchscreen; up to nine touchscreens
are allowed. When you select OK, the driver restarts and
implements the values you selected. Each monitor in
the array must have at least 640x480 resolution available.
If your multi-monitor setup is to have only one touchscreen
in the array, after configuration of Multi-Monitor you
are set; your touchscreen will have index 0 and will be
assignable to any monitor in the array. If you will be
using the USB method of connecting multiple touchscreens,
contact your supplier to obtain a set of touch controllers
programmed to allow multiple USB connections to a single machine.
The Alternative Monitor Setup is for installations that
will use asymmetrical monitors. This option gives the operator the
ability to take any contiguous piece of the extended desktop
and make it the touch area. This option would also work
for single-monitor setups that require touch
be limited to an area of the screen; you could choose to not
give access to the Start button and taskbar, for instance.
Simply check the Alternate Setup checkbox, then enter the top
left and bottom right coordinates of your desired touch rectangle
(on Windows systems, the top left corner is 0,0; the Y-axis positive
direction is down). Mouse Offset determines where the touch zone
starts, and Area Total gives the x/y area in mickeys (there are
normally 65535 mickeys per axis). For instance, if you have a two
monitor setup, with the leftmost (primary) monitor in landscape
mode and the second monitor in portrait mode, use the following
settings (assuming 1280x1024 resolution for both):
x y
Top Left 1280 0
Bottom Right 2304 1280
Mouse Offset 65535 0
Area Total 52428 81918
The offset and total numbers are necessarily like they are
because Windows keeps the same mickeys-per-pixel ratio across
asymmetric monitors in an expanded desktop... 52428 = 65535*(1024/1280)
and 81918 = 65535*(1280/1024). You must also use Rotate Touch for
the portrait-mode monitor, after having set it up in Windows.
Rotate Touch (main menu) takes the touch coordinates from the touchscreen
and rotates them 90 degrees clockwise, the normal default for
a rotated display.
For the same situation, but using the primary monitor as touch,
you will have to turn off Rotate Touch and use the following
settings:
x y
Top Left 0 0
Bottom Right 1280 1024
Mouse Offset 0 0
Area Total 65535 65535
Since the monitors are assymetrical, the desktop dimensions
reported by Windows are 2304 by 1280; without using the alternative
setup the first calibration target will appear off the bottom of
the screen.
When you select 'OK' the driver will save settings and restart using the new
coordinates; a recalibration will be necessary (save your changes
afterward).
SHORTCUTS
In order to fully implement a Multi-Touch system, you
will need to edit the shortcut installed in your Startup
Folder, typically in c:\Documents and Settings\All Users\
Start Menu\Programs\Startup for Win2K (the normal shortcut
will support multiple monitors with one touchscreen).
You will need to copy the shortcut to create multiple
shortcuts, changing the name of each in order to allow
multiple copies in the Startup directory. It is recommended
that the shortcuts be named "Touch Screen Driver1" through
"Touch Screen DriverX", up to the number of touch monitors
connected. Each monitor will have associated with it an
Index digit, provided via the command line from the shortcut.
This Index allows you to tell which touch driver icon (in
the system tray) is associated with which monitor.
Normal convention is to start numbering the monitors from
the top left... for a square 3x3 array, the top left would
be #1 and the bottom right would be #9.
A good procedure for this would be: select the shortcut
(turn it blue), hit Cntrl-C, select the shortcut again
(turn it blue with a box around it and a blinking cursor),
move the cursor to the end of the name and enter '1', then
click off the shortcut (to deselect it) and hit Cntrl-V
to paste another copy of the original shortcut. Continue
editing and pasting until you have the required number
of shortcuts (up to nine, for a 3x3 array).
Now right-click the #1 shorcut and choose Properties.
The shortcut 'target' field, typically "C:\Program Files\
TouchKO Inc.\Touch Screen Driver\tkotouch.exe", needs to have
a command line switch added *after* the last double-quote
to identify the index of the monitor; the resultant line
would appear in 'target' as:
"C:\Program Files\TouchKO Inc.\Touch Screen Driver\tkotouch.exe" -m1
for the first (upper/leftmost) monitor, if the default install
location was selected. Continue to edit the targets of
the shortcuts you have created until each shortcut is
prepared with the command line switch appropriate to its index.
You can't use a .bat file to start the multiple instances,
since the default directory will change to the root (C:\).
Without the '-m*' switch set, only one instance of Touch Driver
can be run at a time.
Reboot the machine and verify that each index has an icon
in the system tray.
Now each monitor index must be mapped to an x,y index setting.
Use Advanced Settings to configure the multi-monitor data
for each touchscreen before doing Find Touch/Calibrate.
For the above example, all of the drivers would have 3,3
set for the Axis data and the upper left monitor (#1) would have
1,1 set for the Index data; monitor 8 would have 2,3 for
indicies.
Once you reboot you will find as many icons in the System
tray as there are active touch sessions running; you can
'hover' the mouse over the icon to see which index it
corresponds to. You should now connect the touchscreen
controllers one at a time, starting with the first monitor,
in order to avoid confusion as to which monitor is connected
to which controller. After you connect the first serial/USB
connection, you should find the Touch(1) icon in the taskbar
and execute Setup from the Setup screen. Continue until all
touchscreens are configured and calibrated, with changes saved.
Each instance will save changes to a file called TKO122mX.dat,
with the 'X' corresponding to the index of the monitor.
HELP
HELP shows this file.
SUPPORT shows contact information should you have a question. The
supplier of this touchscreen should configure this information.
ABOUT shows program and operating system information.
COMMUNICATION CONTROLS
These settings should not be changed manually; it is possible
to have the driver and controller set to different baud rates
(communication would be interrupted). Use 'Find Touch' to
set these parameters.
PORT
Specifies the communication port at which the controller device
operates. Com ports are acquired from the Windows OS.
Options: Com1-9.
BAUD
Specifies the baud at which the communications device
operates. TKO controllers default to 9600. Options: 1200,
2400, 4800, 9600, 19200
DATA BITS
Specifies the byte length at which the communications device
operates. TKO controllers default to 8 Bits.
Options: 7, 8
PARITY
Specifies the parity scheme to be used. TKO controllers
default to None. Options: None, Even, Odd
STOP BITS
Specifies the number of stop bits to be used. TKO
controllers default to 1. Options: 1, 2
FLOW CONTROL
Opens a dialog window with Hard and Soft Flow controls. See
FLOW CONTROL below; TouchKO controllers do not support hardware
flow control at this time.
TIMEOUTS
Opens a dialog window with Communication Port Timeout
controls.
TOUCH/MOUSE CONTROLS
XY DATA ->
MOUSE to enable mouse cursor movement. TERMINAL to direct
touchscreen data directly to the text terminal, with no mouse
cursor movement. TERMINAL mode is useful for troubleshooting
controller/RS232 problems.
MOUSE CLICK
Displays the current mouse click mode... the mode is set via
Menu/Click Mode. Options are Click on Down (gives a down/up
when you touch down), Click on Up (down/up on touch Up) and
Click and Drag (basically follows your finger, down on down
and up on up). Click and Drag is the default.
DRIVER FORMAT
Displays the current driver packet format... this option is
set using Menu/Controller Mode.
Select ELO 2210 to enable program to receive EloTouch 2210
data packets (10 byte packet).
Select MTS TABLET to enable program to receive MicroTouch
format tablet data packets (5 byte packet). This format is
preferred as touch speed is faster and smoother. The controller
emulation mode will change to follow these settings, if touch
has been found (controller communication enabled).
Select TKO Fast Mode if you want the fastest touch response
possible; basically the same as Microtouch format, but at
38.4kBaud (packet rate limited to avoid swamping the CPU).
ARTIFICIAL CURSOR ON
In some instances no cursor is visible; this happens on certain
versions of Windows with no mouse plugged in. Although touch
operation can continue with no cursor, for those that need a
cursor on the screen we have included an Artificial Cursor.
You won't see it unless you have the mouse disconnected,
the normal system cursor is not displayed, and you have
your touch set to 'LIFTOFF' mode.
PING ON
Available only in MTS/TKO mode, without USB. This causes the software to
check for the presence of the controller once per second; if the controller
is not found, an error message is generated notifying the operator
that touch control is disabled. If another interface method (i.e.
keyboard or mouse) is available, this message can be 'OKed'
and work can continue on that machine. Another message will
be generated when touch control is returned to the operator.
If the connect method is USB, do not use the PING ON feature.
RIGHT CLICK BUTTON
Enables a touch-button that appears on top of all windows always.
When this touch-button is selected it enables the next touch
of the screen to perform a Right Click operation; the control
then defaults back to Left Click status. The button may be
re-positioned by either left clicking and dragging with the mouse or,
if TOUCH-DOWN is enabled, by dragging with left touch. Should
you need to re-position the button without performing a right click,
drag the button to its new position and touch it again or right click
with the mouse to go back to Next Touch Left Click status. The status of
the button is verified by a mouse graphic appearing on the button; the
blacked mouse button in the graphic is the operation to be performed next.
Should the button disappear due to a change in screen resolution,
it may be repositioned by either stopping and restarting the driver
application (i.e. reboot) or by turning the right click button off, then
on, via the Advanced Settings window. A SAVE SETTINGS operation
will cause the new position of the button to be stored.
RESOLUTION/POINTS PER SECOND
Controls discarding of continuous touch packets. This results in the
driver application processing fewer continuous-touch packets, resulting in
increased response of the application as well as a loss of resolution in
drawing applications. Touch-down and touch-up packets are not affected.
HIGH resolution discards no packets, LOW resolution discards %90
of continuous-touch packets. If you are running an older, slower
machine in a touch-selection-only mode, then a lower resolution
might decrease the system load of the touch driver. In all other
applications it is recommended to use HIGH resolution.
TOUCH NOISE DOWN/UP
The driver can be set to create a noise on touch down, touch up,
or both. To select a noise, scroll through them with the up/down
arrows to the right of the list box, then click the choice to select it.
The down and up noises are separately configurable between the
following options:
None = no noise
Beep = speaker beep (Win98) or default (Win2K)
Default = Windows default
Asterisk = Windows asterisk
Stop = Windows critical stop
Exclamation = Windows exclamation
Question = Windows question
Short Beep = speaker short beep (Win2K) or default (Win98)
These options are configurable in Windows via the Control
Panel/Sounds settings. This allows you to take any .wav file
and make it one of your touch noises. Touch Noise up/down
is independent of Mouseclick Liftoff/Touchdown setting
(described above). Sound card is necessary for Windows noises.
Speaker beep and speaker short beep use the small speaker
plugged into the motherboard.
RESET INSTALL
This button causes the .dat file to be deleted and the driver
to restart with factory defaults. It is useful if a situation
is encountered where non-functioning values have been put into
a parameter (port timeouts, for instance). A message box will
appear to verify that this is the desired action, if OK is
selected then the .dat file is deleted and the Introductory
Window appears, just as it did after installation. At this point
the Setup button should be pressed to initiate the find controller-
calibrate sequence.
BUTTON FUNCTIONS
TERMINAL WINDOW
This window gives the return information for commands sent
to the controller; it is automatically invoked when the
driver enters Terminal mode. Should you wish to see the
terminal output during Mouse mode, press the Terminal Window
button.
TOUCH POSITION
This button causes a window to appear that displays the current
touch position returned by the controller.
FIND TOUCH
Will scan though available COM ports and BAUD rates to try
to find TKO touch controller. If found the connection to
the com port will be enabled at the correct settings.
Calibration and Saving the settings will be necessary after
the controller is found the first time.
CALIBRATE
Calibrate opens a three-point calibration window. The
touchscreen must be calibrated to align the touch X and Y
data to the video screen. Should the screen resolution be
changed or the monitor XY position knob become changed then it
will be necessary to recalibrate the touch driver software.
SAVE SETTINGS
After configuration and calibration is accomplished click to
save all data to disk. The data file (TKOxxx.DAT) file will
be placed in the same directory that the driver executable
program is located. The xxx indicates revision level of the
mating driver .EXE file.
FLOW CONTROL
Flow control in serial communications provides a mechanism
for suspending communications while one of the devices is
busy or for some reason cannot do any communication. There
are traditionally two types of flow control: hardware and
software. The older TKOTouch controller uses either software
(XON/XOFF) or no flow control; hardware flow control is not
supported. The new controller will support any flow control
mode. The terms DTE (Data Terminal Equipment) and
DCE (Data Communications Equipment) correspond to
the host computer and touchscreen controller, repectively.
SOFTWARE FLOW CONTROL
Software flow control uses data in the communications stream
to control the transmission and reception of data. Because
software flow control uses two special characters, XOFF and
XON, binary transfers cannot use software flow control; the
XON or XOFF character may appear in the binary data and
would interfere with data transfer. Software flow control
befits text-based communications or data being transferred
that does not contain the XON and XOFF characters. This is
the default and preferred mode of communication.
XON/XOFF OUTPUT CONTROL
Specifies whether XON/XOFF flow control is used during
transmission. If SET, transmission stops when the XOFF
character is received and starts again when the XON
character is received. Default OFF.
XON/XOFF INPUT CONTROL
Specifies whether XON/XOFF flow control is used during
reception. If SET, the XOFF character is sent when the input
buffer comes within XoffLim bytes of being full, and the XON
character is sent when the input buffer comes within (XON
Limit) bytes of being empty. Default ON.
CONTINUE SENDING AFTER XOFF SENT
Specifies whether transmission stops when the input buffer
is full and the driver has transmitted the XOFF character.
If SET, transmission continues after the XOFF character has
been sent. If clear, transmission does not continue until
the input buffer is within (XON Limit) bytes of being empty
and the driver has transmitted the XON character. Default OFF.
XON LIMIT
Specifies the minimum number of bytes allowed in the input
buffer before the XON character is sent. Default 1.
XOFF LIMIT
Specifies the maximum number of bytes allowed in the input
buffer before the XOFF character is sent. The maximum number
of bytes allowed is calculated by subtracting this value
from the size, in bytes, of the input buffer. Default 14.
XON CHAR
Specifies the value of the XON character for both
transmission and reception. Default hex 11.
XOFF CHAR
Specifies the value of the XOFF character for both
transmission and reception. Default hex 13.
BEHAVIOUR OF DTE WHEN USING SOFTWARE FLOW CONTROL
XOFF RECEIVED BY DTE
DTE transmission is suspended until XON is received. DTE
reception continues. The (XON/XOFF Output Control) controls
this behavior.
XON RECEIVED BY DTE
If DTE transmission is suspended because of a previous XOFF
character being received, DTE transmission is resumed. The
(XON/XOFF Output Control) controls this behavior.
XOFF SENT FROM DTE
XOFF is automatically sent by the DTE when the receive
buffer approaches full. The actual limit is dictated by the
(XOFF Limit). The (XON/XOFF Input Control) controls this
behavior. DTE transmission is controlled by the (Continue
sending after XOFF sent) as described below.
XON SENT FROM DTE
XON is automatically sent by the DTE when the receive buffer
approaches empty. The actual limit is dictated by the (XON
Limit). The (XON/XOFF Input Control) controls this behavior.
If software flow control is enabled for input control, then
the (Continue sending after XOFF sent) takes effect. The
(Continue sending after XOFF sent) controls whether
transmission is suspended after the XOFF character is
automatically sent by the system. If (Continue sending after
XOFF sent) is SET, then transmission continues after the
XOFF is sent when the receive buffer is full. If (Continue
sending after XOFF sent) is FALSE, then transmission is
suspended until the system automatically sends the XON
character. DCE devices using software flow control will
suspend their sending after the XOFF character is received.
DAT FILE
The DAT file is created when the SAVE SETTINGS button is
clicked. This should occur only after all parameters have
been set such as com port, baud rate, emulation type, mouse
mode etc. The DAT file name will consist of TKO followed by
three digits indicating the major revision, followed by the .DAT
extension. This file will be stored in the same directory
as the executable. In the case of multi-touch installations
(where the '-m*' switch is used) the .DAT file will
have the 'm*' in the name, such as TKO122m3.dat. Hovering
over the icon in the system tray will show the number; this
is the same number that is displayed under 'Index' in both
the Setup and Advanced Settings screens.
*****************************************************************************************
CONTROLLER
Configuration Commands:
<Cntrl-A><F><E><S><CR> Sets controller to Elo 2210 output BINARY
format and 9600,N,8,1. Changes controller mode to Elo 2210 compatability
BYTE Description
1 ASCII 'U' (55h)
2 ASCII 'T' (54h)
3 Status Byte
4 XLOW
5 XHIGH
6 YLOW
7 YHIGH
8 ZLOW
9 ZHIGH
10 Chksum
<Cntrl-A><F><M><T><CR> Sets controller to MTS Tablet output BINARY
format 9600,N,8,1. Changes controller mode to MTS compatability
Bit Description
7 6 5 4 3 2 1 0
BYTE 1 1 S ? ? ? ? ? ? touch byte
2 0 X6 X5 X4 X3 X2 X1 X0 X low
3 0 X13 X12 X11 X10 X9 X8 X7 X high
4 0 Y6 Y5 Y4 Y3 Y2 Y1 Y0 Y low
5 0 Y13 Y12 Y11 Y10 Y9 Y8 Y7 Y high
S=1 Touched, S=0 No Touch, ?=Don't Care
TKO 345r3 CONNECTOR SPECIFICATION
J1 SERIAL CONNECTOR 2x5 (0.1” CENTER)
PIN#
J1 DB9 Description
1 1 5V INPUT if J6 jumper on (pin#1 and pin#2 connected)
2 6 5V INPUT if J6 jumper on (pin#1 and pin#2 connected)
3 2 TXD (controller source)
4 7 RTS (host source) NOT ENABLED IN FIRMWARE
5 3 RXD (host source)
6 8 CTS (controller source) JUMPERED ALWAYS +V
7 4 N/C
8 9 N/C or RESET if J14 jumper on (pulse low to reset)
9 5 GND
10 GND
J3 TOUCHSCREEN CONNECTOR 1x5 (0.1” CENTER) 4 or 5-WIRE
PIN# Description (5-Wire) Description (4-Wire)
1 HDRIVE (upper right corner) XHIGH DRIVE (right side)
2 XDRIVE (lower right corner) XLOW DRIVE (left side)
3 SENSE N/A
4 YDRIVE (upper left corner) YLOW DRIVE (bottom side)
5 LDRIVE (lower left corner) YHIGH DRIVE (top side)
J5 POWER CONNECTOR 1x2 (0.1” CENTER)
PIN# Description
1 +5V or VREG IN (7-15V) jumper selectable
2 GND
Microtouch® all rights reserved
ELO® all rights reserved
FTDI® all rights reserved
CYGNAL® all rights reserved
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.