Network TeleSyetems, Inc.
EnterNet 300 v1.4 for Windows 95x,Windows NT4.x and Windows 2k
(Release Candidate 1)
This file supplements the information in the EnterNet 300 Help utility.
It contains helpful information that either is not documented
elsewhere or requires emphasis. The following subjects are discussed:
1. Notes to Beta Testers
2. Installing EnterNet 300 for Windows
3. Dial-on-Demand
4. Technical Support
5. Release Notes
1. Notes to Testers
===================
Thank you for you willingness to assist NTS in it's efforts to deliver
high quality, well tested software. Your participation in this beta
test program is greatly appreciated.
If you have not yet registered with NTS as a beta tester, please do so
by sending an e-mail message with the words "BETA REGISTRATION" to
enternet@nts.com. Please copy the first three lines of this readme file
into the body of your e-mail message. This will insure that you receive
timely updates to the beta software.
During the course of the beta program you may periodically receive
via e-mail updates to the software that fix problems discovered during
the beta program, or add / change features or functionality. You may
also receive inquiries about your experiences. In order to insure rapid
conclusion of the beta program -- which ultimately benefits you --
please be sure to take the requested actions as promptly as possible.
As you install and use this software, please take note of, and report
to NTS, the following:
1. bugs: The software behaves in an unexpected manner, in a manner
inconsistent with the documentation, or interferes with the correct
functioning of the operating system or other programs.
2. Deficiencies: In your opinion, the software really needs a partic-
ular feature in order to do it's job correctly.
3. Documentation errors: Inaccuracies you may encounter in the soft-
ware's help file or in this readme file.
2. Installing EnterNet 300 for Windows
======================================
If you are installing EnterNet 300 from a CD, insert the CD into your
drive, locate the file named setup.exe in the root directory of the CD
and double-click it. Follow the on-screen instructions.
If you are installing EnterNet 300 from 3.5" disks, insert Disk 1 into
your drive, locate the file named setup.exe in the root directory of
Disk 1 and double-click it. Follow the on-screen instructions.
If you are installing EnterNet 300 from a "zip" file that you received
electronically, create a temporary folder on your computer's hard
drive and extract all the files from the EnterNet zip file to the
temporary folder. Navigate to the temporary folder and double-click
the file named setup.exe. Follow the on-screen instructions. The
temporary folder and its contents may be deleted after installation.
If you are installing EnterNet 300 from a self-extracting executable
file (a file named enternet300.exe) that you received electronically,
double-click the file and follow the on-screen instructions.
MS Windows CD
-------------
Your Microsoft Windows installation CD (or diskettes) may be needed
during installation, depending on your computer's configuration.
Installing on Windows NT
------------------------
If you are installing EnterNet 300 on a Windows NT computer, you must
install it from a Windows NT user account that possesses Administrator
privileges. EnterNet will be installed as an NT Service and will
thereafter be useable from NT use accounts that do not have Administra-
tor privileges.
"Dial-Up Networking is either not installed.." Message During Install
--------------------------------------------------------------------
If you install EnterNet 300 in the absence of MS DUN 1.2c, or if
MS DUN is not properly configured for use by EnterNet 300, the instal-
ler will inform you that "Dial-Up Networking is either not installed
or not configured properly." If you receive this message during instal-
lation, click the OK button on the dialog box and EnterNet 300 instal-
lation will continue. EnterNet 300 will function properly without MS
DUN, but Dial on Demand will not be available. See "Dial on Demand"
below for more information.
3. Dial on Demand
=================
GENERAL
-------
EnterNet 300 is compatible with the Windows Connection Wizard. This
means applications that are "Internet aware" and are thus able to use
Windows Connection Wizard to establish an on-demand Internet
connection will be able to do so through EnterNet 300. This EnterNet
300 feature is called Dial on demand.
If you wish to take advantage of EnterNet Dial on Demand, MS DUN
version 1.2c must be fully installed -- including the existence of at
least one DUN profile -- on your computer prior to installing EnterNet
300. During installation, EnterNet 300 will create an MS DUN profile
named "Autodial". it is important that you not delete this profile if
you wish to use EnterNet 300's Dial on Demand feature. The following
section contains more information about Dial on Demand.
CONFIGURING WINDOWS TO USE ENTERNET DIAL ON DEMAND
--------------------------------------------------
During installation, EnterNet 300 will silently attempt to create an MS
DUN connection profile named Autodial. This profile will be used by the
Windows Connection Wizard to launch EnterNet 300 as necessary.
NOTE: Do NOT delete the Autodial profile from MS DUN or EnterNet
Dial-on-Demand will no longer function.
To support EnterNet Dial on Demand, you must configure your Windows
DUN environment to automatically connect your computer to the Internet
via the DUN profile named "Autodial". The specific steps required to
properly configure Windows Connection Manager varies based on the
specific combination of Operating System (95, 98, NT 2000) and the
web browser you are using. In general, you will need to either launch
the Internet Options utility within the MS Control Panel (simply called
Internet in older Windows versions), or select Internet Options from
within MS Internet Explorer, and modify the settings available on the
Connections tab such that Windows will automatically "dial" the DUN
profile called "Autodial". Please refer to your Windows and/or Internet
Explorer help facilities for further information.
4. Technical Support
====================
Should you find yourself in need of assistance with EnterNet 300 you
should check the EnterNet 300 Help utility before calling your support
organization. To launch the Help utility, first start EnterNet 300
then select "Help Contents" from the Help menu. You may also wish to
review the Frequently Asked Questions (FAQs) section of the NTS web
page, by pointing your browser to the following URL:
http://www.nts.com/support/faq/index.html.
EnterNet 300 is purchased by ISPs and other companies to enable their
end-user customers or employees to access the Internet or to access
their private intranets and extranets. Should the EnterNet 300 Help
facilities not provide the assistance you need, you should contact the
organization from which you acquired EnterNet. Network TeleSystems
does not provide technical assistance directly to EnterNet 300 end
users.
EnterNet for Windows Realease Notes
===================================
EnterNet 300 v1.4 for Windows
=============================
This document lists the significant improvements that have been made to
EnterNet 300 for Windows to date. Unless otherwise noted, each successive
EnterNet build includes all changes from prior builds.
Improvements are listed in reverse chronological order. That is, the most
recent improvements are listed first. As you read through these release
notes, you will notice that the format of the notes has changed slightly
as the product has evolved. To maintain familiarity, the original format
of earlier notes has not been updated.
Release Candidate One
---------------------
INSTALLER IMPROVEMENTS
1. CHANGE TO SYSTEM FILE COPY PROCESS
When installing networking software, Windows typically attempts to
re-install files that already exist in either the Windows or the
Windows\ System folder. If the user installed Windows from a CD
(rather than from the hard drive as would typically be the case if
the user purchased a new computer with Windows pre-installed), then
Windows will typically ask the user to provide the Windows
installation CD, even though many of the files Windows seeks already
exist on the hard drive. To reduce the occurrence of users perhaps
unnecessarily providing their Windows installation CD during
EnterNet installation, the EnterNet installer was modified to
perform the following tasks:
* Copy files from the Windows and the Windows\System folders to the
Windows\INF folder on the local hard drive.
* Change the Setup SourcePath value in the Windows registry to point to
the Windows\INF folder.
* Complete the installation of EnterNet.
* Delete the files that were copied to the Windows\INF folder, leaving
the original files in place.
* Set the Windows Setup SourcePath value back to its original state.
In version 1.4 (this software), the installer only performs the
temporary file copy process if it determines that the Windows Setup
SourcePath is pointing to other than a local fixed drive, and the
system is already configured with a suitable network adapter (an
Ethernet adapter with a TCP/IP binding). For those Windows
installations that were performed from a local fixed drive, the file
copy process is not performed and the SourcePath is not redefined.
Instead, Windows is allowed to copy files from the designated
Windows Setup folder on the local fixed drive from which Windows was
installed.
2. ADAPTER AND TCP CHECK
On all Windows platforms, the EnterNet installer now checks the
system to determine if an appropriate network adapter, with a
TCP/IP binding, is present. If no such adapter is present, the user
is presented with a message indicating that EnterNet will install
correctly but will not work until an adapter is installed and bound
with TCP. (A keyword that suppresses this message has been added.
See below for details.)
3. New installer SETUP.INI parameters to improve installer flexibility:
AskNameAndPassword= If this value is set to true (1), then during
EnterNet installation the user will be prompted to provide a valid
User Name and Password. The default value is false (0).
AskNetworkName= If this value is set to true (1), then during
EnterNet installation the user will be prompted to provide a valid
Network name (typically domain.ext). The default value is false
(0).
SupressAdapterWarning= If this value is set to true (1), then the
user will not be warned if the EnterNet installer determines that
no suitable network adapter exists in their system. A suitable
adapter is an Ethernet adapter with a TCP binding.
4. Installer SETUP.INI parameter deleted:
The WinCDNeeded= keyword has been deleted because the improvement
described in 1 above has rendered it obsolete.
5. Clean option removes fragments after failed installation
A command line switch has been added that allows the installer to
climate all remnants of a failed installation attempt. The
following command runs the cleaner:
<Location Of EnterNet Installer>:\ setup.exe -aclean
6. APPLICATION IMPROVEMENTS
* Support for Windows ME Structured localization (language) support.
* Added Network field to Profile Wizard (controlled by ENTERNET.INI)
* Remove PPPoE Discovery panels (controlled by ENTERNET.INI)
* Remove Network Field control (controlled by ENTERNET.INI)
* Registration Icon in EnterNet folder (controlled by ENTERNET.INI)
* Launch ConnectionAnalyzer menu Item (controlled by ENTERNET.INI)
(ConnectionAnalyzer not yet present)
* Language selection Menu (controlled by ENTERNET.INI)
* Message numbers for errors
* Packet Logging now supported on Windows NT and Windows 2k
* Support for PADN (auto update or routes) Prevent "Launch at
startup" on Windows 2k (runs as a service)
* Fixed bug that occurred when programming the IP address on Win 2000
* Fixed bug that caused Dial-on-Demand to launch multiple instances of
EnterNet
* Fixed broken Help system links
* Activity indicator present when connecting to the BRAS.
* Fixed the PPP re-negotiation bug for Shasta 5000 compatibility.
* Fixed crash that occurred when using rawesr
* Improved Hibernate and standby mode behavior
* Removed the ParseCommandLine call from EnterNet folder
* Fix icon on desktop when creating a short cut.
* Resources are now in res.xxx.dll
* LCP Echo parameters externalized for fine tuning
* LCP Echo behavior fine-tuned
* Windows upgrade bug fix
* TAP driver bug fixed
7. NEW ENTERNET.INI APPLICATION PARAMATERS:
The following new keywords have been added to the [Configuration]
section of the ENTERNET.INI file:
Language= Determins the language. ENU (English), FRC (French), and
JPN (Japanese) are the presently supported values, others are being
created as independent updates.
WizardShowNetwork= causes the Profile Wizard to prompt for a
Network value
WizardSkipDiscovery= Caused the Profile Wizard to skip BRAS
discovery process. Instead, the user will be connected to the first
responding BRAS, or will be connected to the BRAS specified in the
Network= field in the Profile in use.
RegistrationIcon= Determines if the Registration Profile will be
displayed in the EnterNet folder. A value of 1 equates to yes, 0 to
no.
RegistrationDescription= Identifies a Profile within the
ENTERNET.INI file as being a Registration Profile. End users cannot
change the values associated with Registration Profiles.
Registration Profiles have a different appearance than do
Connection Profiles: they have a blue background. To define a
Profile as a Registration Profile, set this keyword equal to the
Session= value for the desired Profile.
ConnectionAnalyzer= This keyword controls weather or not the
Connection Analyzer menu item will be present.
The following new keywords are used within individual Connection
Profiles in the ENTERNET.INI file:
Network = Defines the network to which the User should connect,
typically expressed in the form network.ext
EnterNet 300 v1.34 for Windows
==============================
Added CheckAdapters= keyword to setup.ini file, which allows OEM
customers to suppress the installer’s check for appropriate adapters
with TCP/IP bindings.
UN-INSTALLER BUG FIX
As a result of changes made in build 9b, the uninstaller was
deleting from the registry the keyword that defines the path to the
Windows installation files. This build corrects that bug.
CHANGED ForceReboot VALUE
In the SETUP.INI file, changed the value for the ForceReboot keyword
from 1 to 0.
INSTALLER IMPROVEMENTS
In order to improve how EnterNet integrates into customer product
bundles, additional SETUP.INI parameters were added to the
[CustomOptions] section, as follows:
WinCDNeeded= When this parameter is set to 0, the EnterNet
installer temporarily copies files from the Windows and the
Windows\System folders to a location where Windows can find them
during instal-lation. The files are deleted after the installation
is complete. If this parameter is set to 1, the EnterNet does not
engage in this behaviour. Customers who are bundling EnterNet on
computer systems that have a Windows image on the hard drive should
set this value to 1. If this parameter is set to 1, and if the
Windows install files are not present on the user’s hard drive, the
user will likely be asked to provide a Windows installation CD.
ForceDefaultInstall= During EnterNet installation, if this
parameter is set to 0, the EnterNet installer will ask the user for
answers to installation related questions. If this parameter is set
to 1, then the EnterNet installer will automatically use the
default answers to any questions it might normally ask the user.
EXCEPTION: The user will be required to take action when EnterNet
installation is complete. See ForceReboot= for related information.
ForceReboot= During EnterNet installation, if this parameter is
set to 0, the EnterNet installer will advise the user that EnterNet
installation is complete, and will likely advise the user that a
re-boot is required before running EnterNet. This screen will
require acknowledgement from the user. If this parameter is set to
1, then the EnterNet installer will automatically perform a system
re-boot after EnterNet installation is complete, without requiring
user acknowledge-ment.
HELP SYSTEM IMPROVEMENTS
Added "Advanced Packet Log" and "Advanced Tap Information" topics
Corrected miscellaneous errors Corrected a faulty F1 links
FIXED BROKEN F1 LINKS IN HELP FILE
Some of the F1 links were not functioning correctly.
MISC HELP SYSTEM CONTENT IMPROVEMENTS
Corrected formatting problems with tables and numbered lists;
rewrote the section on EnterNet and ICS; deleted unused items.
"ADAPTER HELP" PANELS ARE NOW PROPERLY EXTERNALIZED
The "Adapter Help" panels were not set to reference external
branding data. This build corrects that problem. The changes in
this build affect only OEM customers who wish to private brand
EnterNet.
HELP SOURCES INCLUDED WITH ISP TOOL KIT
The Help source files were inadvertently removed from the ISP Tool
Kit.
IMPROVED THE INTERNET EXPLORER "TRY AGAIN" ERROR FIX
Public testing of Build 5 resulted in the recognition that an
additional registry key must be changed to work around the IE 5
"Try Again" error. This registry key change is included in this
build.
REQUIRES RE-BOOT AFTER UN-INSTALL ON W2K SYSTEMS
Although technically there is no need to re-boot the computer after
EnterNet is un-installed on Windows 2000 OSs, the software is
configured to force a re-boot. This is done because after
un-installing the software, certain deleted registry keys remain in
memory after EnterNet is un-installed. If a user were to uninstall
EnterNet and re-install without first re-booting, registry remnants
could interfere with proper re-installation.
CORRECTED INSTALLER DEFICIENCY ON W2K SYSTEMS
Version 1.34 Cycle 5 contained an installer deficiency wherein the
un-installation process on some Windows 2000 systems would result
in a system crash and incomplete software and / or driver removal.
This deficiency was related to the introduction of new code in
cycle 5 that presented a new "Please Wait" dialog. In cycle 6 this
dialog has been removed from the InstallShield code and placed into
the NTSETUP.EXE code.
NTSETUP.EXE CONVERTED TO WINDOWS NATIVE FORMAT
The NTS application named NTSETUP.EXE, which was created for the
sole purpose of installing and removing the NTS PPPoE driver on
Windows 2000 machines, has been changed from a console application
to a Windows native one. As a result, the installer / un-installer
no longer presents a DOS box during installation / removal of the
adapter on Windows 2000 machines.
NTSETUP.EXE NOW REMOVING THE PPPoE ADAPTER In cycle 5, there was
code in InstallShield installer that was responsible for the
removal of the NTS PPPoE adapter. This task is now being handled by
NTSETUP.EXE.
SYMETRIC MULTI-PROCESSOR SUPPORT
This release of EnterNet supports Symmetric Multi-Processor (SMP)
computers. There are no special installation considerations for SMP
support. Simply install EnterNet per the instructions above.
SYBERGEN SYGATE SUPPORT
Users of Sybergen’s SyGate product should review the following
online FAQ item to learn more about using SyGate with EnterNet:
http://www.nts.com/support/FaqEnterNetWindows.html#Sygate
INTERNET EXPLORER "TRY AGAIN" ERROR CORRECTED
EnterNet now modifies the Windows registry to correct a Microsoft
error that caused certain combinations of Windows / IE5 / EnterNet
to produce an error when Internet Explorer 5.x would attempt to
access the Internet. The error resulted in the user having to press
a "Try again" button in order to connect to the Internet.
ELIMINATED MANUAL RE-BOOT REQUIREMENT ON NT/2000
Users installing on Windows NT or Windows 2000 computers no longer
need to manually restart their computers after installation.
ADDED "QUICK INSTALL" OPTION
The EnterNet installer now presents the user with the option to
perform a either a "quick install" or to perform a "step-by-step"
install. If the quick install option is selected, EnterNet will be
installed with following default configuration parameters:
The application will be installed in the following folder:
<boot drive>:\program files\NTS\EnterNet 300
The installer will place an EnterNet icon on the desktop.
The installer will not activate EnterNet Dial-on-Demand.
"PLEASE WAIT" WINDOW NOW PRESENTED AT DRIVER INSTALL/UNINSTALL
On Windows NT / 2000 machines, during installation and removal of
NTS PPPoE driver, the user is presented with a message advising
that the process may take a few moments. This message is intended
to prevent users from interrupting the install/uninstall process
due to apparent inactivity.
IMPROVED THE PROFILE WIZARD
The Profile Wizard now checks all adapters to see if TCP is bound
to them, and provides the user with warnings and Help if there is a
problem with adapter selection or TCP bindings.
USER’S GUIDE NOW INCLUDED
During installation, the EnterNet installer now copies the EnterNet
User’s Guide to the \app subdirectory of the EnterNet installation
path.
KNOWN PROBLEMS IN THIS RELEASE
Until Microsoft releases a patch for Internet Explorer that solves
the "Try Again" error described above, some users may continue to
experience the IE5 "Try Again" error, in spite of NTS’ attempts to
work around it. EnterNet Dial-on-Demand does not work with Windows
2000 The "Adapters that can be used by EnterNet" and the "All
Adapters" views on the Profile Wizard’s "Adapter Help" utility do
not work correctly on Windows NT or Windows 2000. On Windows 2000
systems, on the Devices panel of the Profile Wizard, the "NTS
EnterNet P.P.P.o.E. Adapter" appears in the drop-down list of
selectable adapters, when in fact it should not. The user should
select the physical adapter to which their ISP’s service is
connected. The "Filter Driver" option is not available on Windows
NT and Windows 2000 systems. This option is normally selectable on
the Advanced Settings panel, which is accessed by clicking the
Advanced button on the Application Settings panel. In this build,
the application defaults to the Protocol Driver, which is usually
used only for multi-processor support. Running the Protocol Driver
will not degrade performance or otherwise impair EnterNet.
EnterNet 300 Version 1.31
=========================
New EnterNet Features
Customizable MTU size. EnterNet can now be packaged and delivered
to end users with a pre- defined MTU size.
Bug Fixes
EnterNet folder branding. A deficiency was corrected wherein the
EnterNet folder application did not correctly reflect private
branding data. Specifically, the customized application name and
customized company name were not being displayed on the EnterNet
folder title bar, or in the EnterNet folder About panel.
Memory Leak. The presence and source of a memory leak was confirmed
and corrected.
EnterNet 100/300 Version 1.3
============================
EnterNet version 1.3 contains graphical applications, Network MAC
drivers, and Operating TAP drivers to create and manage PPPoE sessions.
This document summarizes the main new features and bug fixes included in
the release.
New EnterNet Features
* Windows 2000 support
* Automatic Windows NT and Windows 2000 installation
* EnterNet as service under Windows NT
* Detailed Packet Logging Support and improved diagnostics
* Persistent Connections
* Improved underlying "TAP" kernel driver module (TPL)
* Compatibility with Windows 98 Release 2 Internet Connection Sharing
* Compatibility with IPSec VPN client software from Shiva,
CheckPoint, TimeStep and Nortel
* Improved performance
EnterNet Application as a Windows NT Service
This release contains a support for running EnterNet application as a
service. This provides connectivity to any user logged in to NT. The
older version of EnterNet forced user to login as administrator.
Internal TAP Driver Option
This release includes an option to use two different flavors of the
"TAP" driver. The TAP driver is used to easily add other plug-in
networking capabilities to Windows, including the EnterNet PPPoE driver.
The new option is called the "TPL" driver.
By default, application will use our "TAP" driver technology. The "TPL"
driver can be used in certain configurations to resolve compatibility
problems with other drivers.
Improved Performance
EnterNet has been optimized to improve network thruput possible to
nearly the same possible using a static IP connection.
Persistence Connection (EnterNet 300/500 only)
This release contains an option to let the client automatically retry to
connect to a PPPoE server. This option can be enabled by checking
Persistence Connections button under Application settings.
Network Health Monitoring (EnterNet 300/500 only)
This release upon connecting to a PPPoE server will ping all the DNS’s
and NBNS’s which are negotiated and present a visual indication of
reachability of these resources.
Routing Table (EnterNet 300/500 only)
Displays internal Windows IP routing table information through Advanced
menu option.
IP Interface (EnterNet 300/500 only)
Display IP addresses used and the statistical information for each
adapter in the system.
Fast Configure Option (EnterNet 300/500 only)
A new option allows selection between two different internal TCP/IP
configuration mechanisms, Private API or DHCP. The prior version was
relies on a private DHCP mechanism to set IP addresses and IP
configuration to the protocol stack bound to EnterNet PPPoE adapter.
Version 1.3 now includes a means to directly program the IP address and
configuration of the protocol stack. By default Windows 95/98/NT are now
set to use private API mechanism. However the DHCP options is available
fr backward compatibility with Shiva and TimeStep VPN clients and other
software that may also require DHCP mechanisms to properly function.
Show Services In Folder (EnterNet 300/500 Only)
When this new option is enabled the EnterNet folder is automatically
populated with icons representing all the servers and services
available.
EnterNet Bug Fixes
* Fixed an adapter selection problem where multiple adapters of same
type are installed.
* Fixed problem where adapter descriptions that included spaces did
not match the INI file.
* Fixed a bug that caused the EnterNet dialer to reload when dial on
demand was enabled.
* Fixed a bug from toggling the password checkbox.
* Fixed a bug in pressing the enter key on the folder will start the
highlighted dialer.
* Fixed a DHCP problem on Windows NT.
* Fixed a bug where the VPN adapter list was not displayed on
EnterNet 300.
* Fixed a bug caused by dragging and dropping a session profile to
the desktop.
* Fixed API to provide encryption type per connection.
* New OID support so the driver can be tested by Microsoft NDISTEST tools.
* Fixed a bug in RAWESR module which could cause a crash with more
than 4 PPPoE servers.
* Bug fix in for NT driver (NTSTAP1.SYS) which could crash when combined
with certain Ethernet cards.
* Fixed a compatibility bug with CheckPoint Software SecureRemote Client 4.0.
Enhanced and Undocumented Support Options
The following features have been added for use by professional support
staff working for service providers and authorized NTS partners.
Packet Logging
Packet logging is available for Windows 95 and Windows 98. The feature
can be enabled by adding a new keyword to ENTERNET.INI.
[configuration]
PACKETLOGGING=1
Once set, logged packets can be viewed by invoking Advanced menu option
which will contain an additional tab. The packet log can be viewed in
three different formats; preview, interpreted and raw hex data. Logging
supports PPPoE, PPTP, L2TP, DHCP, IP, UDP, and NTS control channel
packets.
Hide Profile
This release contains supports for hiding a specific session from
Enternet folder. This feature can be enabled by adding the following
keyword to the ENTERNET.INI file.
[configuration]
HIDEPROFILE=1
Set ETYPE PayLoad and Discovery
This release contains support non-standard values for ETYPEs used by
PPPoE discovery and payload frames. By default, the IETF standard 0x8863
and 0x8864 frames are used Discovery and Payload respectively. The
following keywords in ENTERNET.INI file replace the default:
[configuration]
ETYPEPAYLOAD=0xnnnn
ETYPEDISCOVERY=0xmmmm
Customizable MTU Size
EnterNet can now be packaged and delivered to end users with a pre-
defined MTU size.
©2000 Efficient Networks. 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.