ITK Telekommunikation AG
PO box 500450
D-44204 Dortmund
Tel.: +49 (0) 231 9747 - 250
Fax.: +49 (0) 231 9747 - 777
e-mail: service@itk.de
WWW: http://www.itk.de
Current product information - Addendum to the printed documentation
=====================================================================
Table of contents
==================
0. Structure of this file
1. General
2. System Requirements
3. CAPI2.0 / CAPI1.1 / CAPI1plus
4. X.25 Support
5 Network Protocol Variants
5.1 US Network Protocol Support
6. Leased Lines
7. Operating System specific properties
7.1 WinNT
7.2. Win95
7.3 NetWare
7.4 SCO OpenServer
7.5 DOS
7.6 Windows 3.x
8. Certification
9. Problems / Remarks / History
0. Structure of this file
==========================
This "readme" universally applies for the ix1-basic board
and for all operating systems named above. Items which depend on the
respective operating system are mentioned in the specific section (7.x).
1. General
===========
This version includes the ISDN download software
V3.10 for ix1-basic board 1MB (ISA/PCI/MCA) and 4MB (ISA).
Following Operating Systems are supported: - Win95
- WinNT
- NetWare
- SCO OpenServer
- DOS
- Windows 3.x
The manual "ix1 Installation and Interfaces" belongs to this software.
Bus interface
============
The ix1-basic boards support the ISA-, PCI and MCA-Bus .
MCA is supported only for DOS and Win 3.x drivers.
NOTE ! ! !
Please make sure that the ix1-basic board for MCA-Bus has been
configured for the MCA-Bus before you use it.
It is also possible to configure the ix1-basic ISA board for the EISA-Bus.
NOTE ! ! !
In EISA-Bus systems it is possible to share IRQs. ix1 boards in your
system should share one IRQ to save resources. For more details to
configure ix1 boards for the EISA-Bus look the manual
"ix1 Installation and Interfaces".
Please make sure that the ix1-basic board for EISA-Bus has been
configured for the EISA-Bus before you use it.
PCI support
===========
This version of the ix1-basic download software supports the
ix1-basic PCI board. There is no need to adjust IRQ or IO base.
Please make sure during the installation that the IRQ is not occupied.
The easiest way is to enable the automatic IRQ grant for PCI adapters
in the system BIOS.
Fax/Modem operation
===================
With a Fax/Modem expansion, a Fax- and Modem operation of up to 14400 bit/s
via CAPI is supported.
With a 4MB ix1-basic board it is possible to handle Fax-and/or Modem
connections at the same time.
With a 1MB ix1-basic board you have to choose between the Fax- or Modem-
driver.
For this under CAPI1.1 (CAPI1plus) the B2-protocol modem (0x0c) has to be
adjusted.
2. System Requirements
======================
Following system requirements must be met in order to run an ix1-basic board:
-----------------------------------------------------------------------------
PC/AT compatible computer (>=80386) with one of above named operating
systems
for ix1-basic ISA/MCA:
----------------------
1 free 16 bit ISA/EISA/MCA slot for the ix1-basic/ISA board
1 free interrupt (IRQ)
1 successive free i/o port addresses, selectable from following ranges:
-----------------------------------------------------------------------
- 0x380-0x387
- 0x388-0x38F
- 0x390-0x397
- 0x398-0x39F
- 0x3A0-0x3A7 (Hardware Version 1.2 or later)
- 0x3A8-0x3AF (Hardware Version 1.2 or later)
for ix1-basic PCI:
------------------
1 free PCI slot for the ix1-basic/PCI
1 free interrupt (IRQ)
3. CAPI2.0 / CAPI1.1 / CAPI1plus
=================================
The ISDN download software V3.10 for ix1-basic board supports CAPI1.1,
CAPI2.0 and CAPI1plus applications at the same time.
Specific operating system drivers support only CAPI2.0 applications.
Look respective operating systems sections below.
The B channel protocols bit transparent, HDLC transparent, T.30, X.75,
Modem, V.110, T.70NL, T.90NL, ISO 8208, are supported according to CAPI1.1.
The B channel protocols bit transparent, HDLC transparent, T.30, X.75,
Modem, V.110, LAPD for D-Channel X.25, T.90NL, ISO 8208, are supported
according to CAPI2.0.
4. X.25 Support
===============
This software supports the following X.25 methods:
-----------------------------------------------
B channel: X.31 case A (no bit rate adaptation)
X.31 case B
D Channel: X.31 case B
5. Network Protocol Variants
============================
Following Network Protocols belong to the standard scope of delivery
of the board software:
- DSS1-Protokoll (incl. respective country/PBX DSS1 variations)
- 1TR6(Germany)
- VN2 (France)
- VN3 (France)
- Q.931 (CCITT blue book)
- Cornet N
- Cornet T
- National ISDN 1
- 5ESS
- ECMA Q.SIG
- DMS-100
- TS013
- INS64 (without redial)
If the protocol variant VN4 (France) is to be used, Q.931 has to be set.
The ix1-basic board is adjusted by default to the D channel protocol
Euro-ISDN (DSS-1).
5.1 US Network Protocol Support
===============================
This version of the driver is able to make use of US Network protocols
as National ISDN 1 (NI-1), DMS-100 or 5ESS.
Please consider that one or two SPID from the Service-Provider are assigned to
each ISDN-Interface for these D channel protocols.
N O T E ! ! ! N O T E ! ! ! N O T E ! ! ! N O T E ! ! !
This software supports every SINGLE SPID only with ONE Phone/Directory number.
6. Leased Lines
===============
The ix1 software for the ix1-basic board supports the following leased lines
within the area of the Deutsche Telekom
a) D64S (0 D channel, 1 B channel)
(is currently supported with CAPI1plus only)
b) DS01/TS01 (1 D channel, 1 B channel)
c) DS02/TS02 (1 D channel, 2 B channels)
7. Operating System specific properties
=======================================
7.1 WinNT
===========
7.1.1 Installation/configuration
--------------------------------
The WinNT 3.51 Service-Pack 4 is not supported.
We suggest Service-Pack 3 using Windows NT 4.0
This version of the Windows NT driver supports the application interface
"Capi2032.dll" and "Capi20.dll". Capi2032.dll includes ITK specific
extensions. It complies the calling conventions for CAPI version 2.0
to send or receive CAPI-Version 1.1- and CAPI-Plus-message from or to the
driver.
The driver interface is a multi CAPI interface also. This means the
support of CAPI2.0, CAPI1.1 and CAPI1plus.
The Windows NT driver could add to system via the network configuration:
Properties of Network Neighbourhood (right mouse button)->Adapters->Add->
Have a Disk (put in the path where the hardware driver could be found)
say "OK" and select the driver for the ix1-basic board.
7.1.2 ix1-basic PCI support
----------------------------
If you want to install the ix1-basic board in a multiple PCI bus motherboard
(NOTE: NOT PCI slots !!!) you have to register the bus
(where the ix1-basic board is installed) in the registry.
In the next version of the ix1-basic download software the PCI bus is
detected automatically.
7.1.3 Adjusting Network Protocol- and Leased Lines-Variants
------------------------------------------------------------
This version of the ix1-basic download software supports driver configuration via
tabs. After adding the ix1-basic board to the system via the network
configuration, you can configure some items within the driver's property tabs
like Network Protocol- and Leased Lines-Variants in the "line tab".
For further details look the manual "ix1 Installation and Interfaces".
7.1.4 NDIS WAN Miniport
------------------------
This version of the Windows NT driver set contains the NDIS WAN Miniport
for an installation only on Windows NT 4.0. For this reason the installation
process slightly differs from the installation originally described in the
manual "ix1 Installation and Interfaces".
After adding the ix1-basic board to the system via the network configuration,
you can configure some items within the driver's property tabs.
The "Wan Miniport" tab has been added to the ISDN board's properties.
In this tab settings that apply to remote access connections in general can
be made:
- B-Channel protocol: "HDLC Transparent" is needed for standard PPP
connections; the option "X.75" can only be used
for connections to certain destinations - it
introduces error correction mechanisms
- Own MSN: contains the multiple subscriber number that
is used on outgoing calls as calling party number;
the definition of this number is only needed for
some particular ISDN PBXs or switches
default: empty
- Accepted MSN: contains the multiple subscriber number RAS should
react to on incoming calls; the configuration of
this number becomes necessary if you want
multiple data transmitting terminal equipment to
operate on the same ISDN bus or multiple data
traffic handling applications to operate within
the same PC.
default: disabled
- Accept all MSNs: Check this option if you want RAS to accept all
incoming calls regardless of the actual called
party number
default: checked
After making all settings within the ix1-basic properties, close this
dialogue with OK. A message box will appear, telling you that you now must
add the new RAS ports to the Remote Access Service. Proceed as follows:
(1) Close the message box with OK.
(2) Switch to the "Services" tab within the network configuration
(3) If the "Remote Access Service" is already installed select it from the
list of services and click on "Properties...". If it is not yet
installed proceed with step (5)
RAS service is already installed:
(4) Click on "Add..." in the RAS setup dialogue - proceed with step (8)
RAS service is not yet installed:
(5) Click on "Add..."
(6) Choose "Remote Access Service" from the list of services and click OK
(7) Windows NT installs the RAS components now from the Windows NT CD;
finally you will enter the Add dialogue within RAS
(8) Select the first offered ISDN port and click OK
(9) In the RAS setup dialogue click on "Add..." (again) and select the
second ISDN port; confirm with OK.
(10) Now you can configure the just added RAS ports. Select the first
ISDN port and click "Configure..."
(11) If you want to accept incoming calls you have to select "Receive
calls only" or "Dial out and receive calls" - click OK.
(12) Only if you are running Windows NT Server you will be allowed to
configure more than one RAS port for incoming calls. In this case
proceed for the second ISDN line like explained in steps (10) and (11).
If you are running a Windows NT Workstation as RAS server you must make
sure that the first ISDN port is configured for dial-in, not the second.
If the second was configured for dial-in by mistake, due to a
conceptual problem within Microsoft's RAS management you might get
into problems on incoming calls.
(13) Now click on "Network...". Configure all necessary network items
for RAS client and server. Refer to your Windows NT manual for more
detailed information.
(14) Close the RAS setup dialogue by pressing "continue". If you have not
entered the RAS Network screen(s), yet, all concerned configuration
screens will be opened successively, now. You will get the opportunity
to change the default settings.
(15) Finally close the network configuration with "Close". Windows NT now
updates all bindings and in the end prompts for reboot of the
system. Confirm this by pressing OK.
After restarting Windows NT the new RAS ports will be available for dial-out
within the "Dial-up Networking" program. For details concerning dial-up
networking review your Windows NT documentation.
The above mentioned ISDN ports are tight to an ISDN line device each. From the
devices' names it is possible to obtain a backward reference to the respective
ISDN adapter. The ISDN device names are build the following way:
Wan<AdapterNumber><BoardName>
<AdapterNumber> means the number of the network adapter, to be found in
brackets in front of the respective adapter on the adapter tab.
<BoardName> stands for the name of the ISDN board, e.g. ix1basic, ix1primary.
If for instance you have one ix1-basic and one ix1-primary board in your
system the ISDN device names could be:
Wan2ix1basic
Wan7ix1primary
If you are using the dial-up network in conjunction with call-back, you
ought to make sure that the "RAS Server Service" is not running. Otherwise
the ISDN port that has previously been used by a call-back connection won't be
released by RAS again (RAS problem). If you run into this problem, you can
stop the RAS Server Service within Control Panel - Services. Then the ISDN
port becomes available again.
How to disable the NDIS WAN driver
----------------------------------
This is needed
1. to restart the card driver without rebooting the PC
2. to disable unused drivers
The NDIS WAN Miniport driver can be turned off by either of two ways:
- run the "Services" applet from NT's ControlPanel;
select the "Remote Access Server" and stop it - by setting the "Startup..."
option to "manual" the RAS server won't start after the next NT boot.
- run Start/Programs/Administrative Tools (Common)/Remote Access Admin. The RAS
server can be stopped by selecting "Stop Remote Access Service" from the "Server"
pull-down menu.
7.1.5 Adjusting compression
----------------------------
The data compression for reliable data connections is automatically active.
If there is a compatible software at the connection partner, the best
possible compression method is chosen for this connection. If you want to
stop the automatic compression negotiation, you are able to define the
compression method manually in the WindowsNT registry.
In a specific folder of the registry you have to register the compression.
To open the registry do: "START"->Run->regedt32. Via HKEY_LOCAL_MACHINE->
System->CurrentControlSet->Services->ix1basic(No.)->Parameters->Line1 you
reach the parameter "CompressionType". This parameter could take one of the
compression type values mentioned below:
compression types:
------------------
value: meaning:
------ --------
1 no compression (disable any compression)
2 V.42bis
3 ITK_COMP (ITK compression)
4 optional compression (board offers V.42bis and ITK compression)
5 CAPI1plus defined
For further details look the manual "ix1 Installation and Interfaces".
7.1.6 MSN-Mapping
------------------
The MSN-Mapping could be modified via the registry also.
In a specific folder of the registry you have to register the MSN-Mapping.
To open the registry do: "START"->Run->regedt32. Via HKEY_LOCAL_MACHINE->
System->CurrentControlSet->Services->ix1basic(No.)->Parameters->Line1 you
reach the parameter "EAZMappingTable". If you select this parameter, a window
appears where you can write a multi string. In this window the numerals "0"
to "9" are one below the other. Every single numeral stands for the respective
EAZ. For example, if you want to map EAZ "1" with MSN "12345", please erase
the numeral "1" and edit the MSN "12345" just at this place .
7.2 Win95
===========
7.2.1 Installation/configuration
---------------------------------
This version of the Win95 driver supports exclusively CAPI 2.0
at the application interface "Capi2032.dll".
This version of the Win95 driver is a "single card version".
This means that only one ix1-card is supported in the system.
The Win95 driver could add to system via the network configuration:
Properties of Network Neighbourhood (right mouse button)->Adapters->Add->
Have a Disk (put in the path where the hardware driver could be found)
say "OK" and select the driver for the ix1-basic board.
7.2.2 ix1-basic PCI support
----------------------------
If the ix1-basic PCI board is detected for the first time, but should not
be installed, you are reminded that the board is registered in the device
manager as unknown hardware device. If you want to install the board later,
first you have to delete the "unknown hardware device" in the device manager.
Even at the next restart of the system it is possible to detect the
ix1-basic board as new PCI hardware device. If you have followed the advice
to install the PCI hardware device to the end you MUST restart the system.
Even at this point of time the ix1-basic board has been added correctly.
7.2.3 Adjusting Network Protocol- and Leased Lines-Variants
------------------------------------------------------------
This version of the ix1-basic download software supports driver configuration via
tabs. After adding the ix1-basic board to the system via the network
configuration, you can configure some items within the driver's property tabs
like Network Protocol- and Leased Lines-Variants in the "line tab".
The procedure to adjust Network Protocol- and Leased Lines-Variants is the
same as under WinNT. For further details look the manual
"ix1 Installation and Interfaces".
7.2.4 Adjusting compression
----------------------------
The data compression for reliable data connections is automatically active.
If there is a compatible software at the connection partner, the best
possible compression method is chosen for this connection. If you want to
stop the automatic compression negotiation, you are able to define the
compression method manually in the Windows95 registry.
To open the registry do: "START"->"Run"->"regedit". The registry editor
displays the system configuration in an explorer like way.
Browse to following 'key': "HKEY_LOCAL_MACHINE"->"System"->"CurrentControlSet"
->"Services"->"Class"->"Net"->"00xx"->"Line1". (There are possibly more 'keys'
in "Net" - 00xx is the 'key' where you find the string "AdapterName CSSBASIC".)
Now you are able to create (if the string 'CompressionType' doesn't exist) a
new entry in this 'key' with "Edit"->"New"->"String Value". Call this new entry
'CompressionType'. Mark this entry and change the value with "Edit"->"Modify".
You could choose one of the compression type values mentioned below:
compression types:
------------------
value: meaning:
------ --------
1 no compression
2 V.42bis
3 ITK_COMP (ITK compression)
4 optional compression (board offers V.42bis and ITK compression)
5 CAPI1plus defined
7.3 NetWare
=============
7.3.1 System pre-condition
---------------------------
For a correct mode of operation of the software following Novell patch sets
MUST be installed:
NetWare 3.12: 312ptb.exe (or higher)
NetWare 4.10: 410pt7.exe (or higher)
There is no patch needed for IntraNetWare (4.11).
7.3.2 Installation/configuration
---------------------------------
Please insert install disk and call: "load install".
Select from the menu "Installation Options" "Product Options -
other optional installation items" and press <enter>.
From the menu "Other Installation Actions" select the item
"Install a product not listed" and press <enter>.
If "Install to server" appears, select the server and press <enter>.
Please confirm "Start Installation" and "Insert disk" with <enter>.
After this you can add the ix1-basic board by calling "load ixinstal /n".
The command line switch "/n" creates automatically an ASCII file "IX1.INI"
which contains default ISDN board parameters. If you do not want to use this
default parameters you could configure it by modifying this file with any
text editor.
NOTE: Do NOT use the Novell NetWare 3.12 system editor EDIT, because
==== this tool can not handle large files.
Reading the actual ISDN parameter configuration from your ITK board
call "load ixrdconf".
The tool 'IXINSTAL' got a new command line switch: "/u".
Use this switch to update a changed hardware configuration, i.e. after
you had add or delete an ix1 board.
For further details look the manual "ix1 Installation and Interfaces".
7.3.3 Adjusting parameter in the configuration file "ix1.ini"
--------------------------------------------------------------
To adjust Network Protocol- and Leased Lines-Variants, compression or
MSN-Mapping you have to modify the parameter in the configuration file
"ix1.ini".
For further details look the manual "ix1 Installation and Interfaces".
NOTE ! ! !
After any change in the file "ix1.ini", the CAPI driver "ixcapi.nlm"
has to be reloaded !
7.4 SCO OpenServer
====================
7.4.1 CAPI-Features
--------------------
* CAPI version 1.1 and CAPI-Plus(ITK) support with following restrictions:
Use the calling conventions for CAPI version 2.0 to send or receive
CAPI-Version 1.1- and CAPI-Plus-message from or to the driver.
The device is called /dev/capi20.
* Full CAPI version 2.0 support.
7.4.2 Adjusting parameter in the configuration file "ix1.ini"
--------------------------------------------------------------
To adjust Network Protocol- and Leased Lines-Variants, compression or
MSN-Mapping you have to modify the parameter in the configuration file
"ix1.ini". For further details look the manual
"ix1 Installation and Interfaces".
7.5 DOS
========
7.5.1 Installation/configuration
--------------------------------
To install the ix1-basic board under DOS, please call the Batch-File
"INSTALL.BAT". If you do not pass a path like "INSTALL.BAT c:\mydirectory"
all used files are copied into the default directory "c:\ix1".
After all files have been copied you can call the Batch-File CAPI.BAT
with following parameters:
CAPI <RETURN> load the ix1-basic board and the CAPI PC-driver
or
CAPI -D <RETURN> unload the CAPI PC-driver (IXCAPI.COM)
or
CAPI ? <RETURN> Displays help screen for CAPI.BAT
There is no hint in the manual "ix1 Installation and Interfaces" to this
additional parameter.
7.5.2 Adjusting Network Protocol- and Leased Lines-Variants
------------------------------------------------------------
If the ix1 board is to be operated with another D channel protocol, it has to
be configured appropriately with the utility 'SETLINE'. The use of SETLINE is
described in the manual "ix1 Installation and Interfaces".
Especially for several TK-systems that do not support the information element
"Sending Complete" in setup, there is now the protocol DSS1-TK.
In the following some examples for the possible settings:
SETLINE -D 0 <RETURN> selects 1TR6
or
SETLINE -D 3 <RETURN> selects VN3 (France)
As you know with this version of download software the US network protocol
variants National ISDN 1 (NI-1), DMS-100 and 5ESS are supported.
After every download SPID and Directory Number(DN) have to be configured
with the utility 'SETCOMP' on the board. Please note that for any
ISDN Interface in 5ESS a SPID has to be set, and in NI-1 two SPIDs and two
DNs have to be set.
In the following some examples for the settings:
------------------------------------------------
SETCOMP -S 1234,56,7890,57 configures SPID and DN for NI-1
TWO-SPID-VARIATION:
SPID1=1234,DN1=56;SPID2=7890,DN2=57
or
SETCOMP -S 1234 configures SPID for 5ESS
ONE-SPID-VARIATION:
SPID1=1234,DN1=58
For the different types the following line settings are to be done with
-----------------------------------------------------------------------
the utility SETLINE:
--------------------
a) D64S (0 D channel, 1 B channel)
Since no D channel is available, the settings referring to NT-TE
side are ignored. For the bandwidth, bit 3 is set to 2x64 Kbit.
Hence, for LineAccess the resulting value is
10111=23 (decimal) (setline -l 23)
b) DS01/TS01 (1 D Channel, 1 B Channel)
For regular operation the two subscribers (A and B) of the leased line
have to be configured differently. Bit 2 has to be set on NT-side for A,
and on TE-side for B.
For the bandwidth, bit 3 is set on 2x64 Kbit.
Hence, the resulting values for LineAccess are
A (NT) = 00111 = 7 (setline -d 0 -l 7)
B (TE) = 00011 = 3 (setline -d 0 -l 3)
c) DS02/TS02 (1 D channel, 2 B channels)
For regular operation the two subscribers (A and B) of the leased line
have to be configured differently. Bit 2 has to be set on NT-side for A,
and on TE-side for B.
For the bandwidth, bit 3 is set on 2x128 Kbit, that means that the two
B channels are bundled.
Hence, the resulting values for LineAccess are
A (NT) = 01111 = 15 (decimal) (setline -d 0 -l 15)
B (TE) = 01011 = 11 (decimal) (setline -d 0 -l 11)
7.5.3 Adjusting compression
----------------------------
With the utility 'SETCOMP' the utilised way of compression can be preoccupied.
The following variants are supported:
-------------------------------------
setcomp -c 0 switches off compression
setcomp -c 1 V.42bis according to standard
setcomp -c 2 ITK compression (better in partly compressed data)
(default setting)
setcomp -c 3 optional compression (board offers V.42bis and
ITK compression). The called subscriber can then
determine the method. If both have chosen optional,
ITK compression is used.
setcomp -c 4 The compression can be determined through the CAPI1plus
application, by the ITK MPR for example.
7.5.4 MSN-Mapping
------------------
For the CAPI1.1 interface a MSN-Mapping is supported. The table has to be
configured with the utility 'SETCOMP' after any download.
7.6 Windows 3.x
===============
7.6.1 Installation/configuration
--------------------------------
Since the operating of the ix1-basic board under Windows 3.x is based on
the DOS-driver there is the same procedure to install it like under DOS.
Please look at item 7.5.1.
To be able to use the T-Online Decoder from the Deutsche Telekom under
Windows 3.x you have to add the following lines in your AUTOEXEC.BAT file:
cd \ix1
call capi
Now the CAPI is started completely.
7.6.2 Adjusting Network Protocol- and Leased Lines-Variants
------------------------------------------------------------
Since the operating of the ix1-basic board under Windows 3.x is based on
the DOS-driver there is the same procedure to adjust Network Protocol- and
Leased Lines-Variants, compression or MSN-Mapping under Windows 3.x as under
DOS. Please look item 7.5.2. (Adjusting Network Protocol- and Leased Lines-
Variants), item 7.5.3 (Adjusting compression) and item 7.5.4 (MSN-Mapping).
8. Certification
================
ix1-boards with ISA- and PCI-Bus are admitted by the
"Bundesamt für Zulassungen in der Telekommunikation" (BZT) under the
numbers A103702C and D128251H.
The ix1-basic ISA board was admitted under the CE-number CE 0167X
in Belgium, Denmark, UK, Finland, Ireland, Italy, Luxembourg,
the Netherlands, Norway, Austria, Portugal, Spain, and Sweden.
The ix1-basic PCI board was admitted in the countries mentioned above under
the number CE 0560X.
In France the ix1-basic ISA board have the admission number 95231B and
in Switzerland the admission number 95.0488.I.N.
In France the ix1-basic PCI board have the admission number 96434B and
in Switzerland the admission number 96.0.600.I.N.
The admissions were given for Point-to-Multipoint-, Point-to-Point- (NT1-)
connections and for leased lines.
Further information can be inquired at our product support (-250).
9. Problems / Remarks / History
================================
a) The ix1-basic board does NOT work with Fax-Piggy modules of the
hardware version 1.3.
There are no problems known with Fax-Piggy modules of the hardware
versions 1.4 or 2.1.
b) Referring to the compression, the present version is NOT compatible with
versions before version 3.00 ! Data connections between the current version
and an older version work uncompressed.
Dortmund, February 4th, 1998
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.