# | README file for | | ELSA WINNER Windows disk containing Windows NT 4.00 build 1381. | | Copyright (c) 1993-97 ELSA GmbH, Aachen (Germany) | | Subsidary: | ELSA GmbH ELSA Inc. | Sonnenweg 11 2150 Trade Zone Blvd. | D-52070 Aachen Suite 101 | Germany San Jose, CA 95131 | USA | | Phone : +49-241-9177-0 Phone: +1-408-935-0350 | Support Fax: +49-241-9177-213 Phone: 1-800-272-ELSA | BBS (modem): +49-241-9177-981 Fax : +1-408-935-0370 | BBS (ISDN) : +49-241-9177-7800 BBS : +1-408-935-0380 | CompuServe : GO ELSA CIS : GO ELSA | WWW : http://www.elsa.de WWW : http://www.elsa.com | | February, 13th 1997, FNicklis Table of Contents: 1 Introduction 2 Installation 3 Changing the resolution after installation 4 Additional Configuration Options 5 Known Problems ------------------------------------------------------------------------ 1 Introduction This file explains how to install and configure an ELSA graphics driver for Windows NT. 1.1 List of files The directory with the ELSA graphics driver for Windows NT contains the following files: TXTSETUP.OEM Script file for setup at boot time ELSA.INF Script file for Microsoft setup program README.TXT The file you are reading LIESMICH.TXT German version of the file README.TXT DISK1 Identifier for the first disk DISK2 Identifier for the second disk DISK2 Identifier for the third disk For machine-dependent files there are different directories named I386\ for Intel-x86-CPUs. WINNER.SYS Miniport driver WINNER.DLL Display driver WINNERMB.DLL Multi-Display driver ELSAOGL.DLL OpenGL driver MONCTRL.CPL Display control application MONCTDEU.DLL Language extensions for MONCTRL MONCTENG.DLL Language extensions for MONCTRL GLSET.DLL GLoria Settings property page GLSETRAY.EXE GLoria Settings Tray utility DXCTRL.DLL DirectX Control VIDEOCTR.EXE Video Control Common files are stored in the folder named COMMON\ GLSET.REG Registry file for GLoria Settings GLSET.TEX Data file for GLoria Settings GLSETENG.HLP English help file for GLoria Settings GLSETDEU.HLP German help file for GLoria Settings ELSA.HLP ELSA help file 24H96.TIM Sample Timing file for ELSA ECOMO 24H96 GLOBE.PPM Data file for DirectX Control RAST1.PPM Data file for DirectX Control CYLINDER.X Data file for DirectX Control DXCTRL.REG Registry file for DirectX Control ELSA2.PPM Data file for DirectX Control SPHERE3.X Data file for DirectX Control 1.2 How to determine the driver's version number There are a few posibilities to get the version number for an ELSA NT graphics driver. 1.2.1 Using the Control Panel Start the control panel (CONTROL.EXE) and select the icon "Display". There, click the button "Change Display Type". In the following dialog the version number is displayed in the box driver information. NOTE The driver has to be installed to use this feature! NOTE Due to a non-ELSA problem the version number is only displayed in an US-english installation if Windows NT. 1.2.2 Using MonCtrl Choose the Icon "ELSA MonCtrl" in the control panel. Above the exit-buttons the version number is displayed. NOTE The driver has to be installed to use this feature! 1.2.3 Using the Explorer Use the Explorer to watch the file properties for either one of the files WINNER.SYS, WINNER.DLL or WINNERMB.DLL. The files can be found in the directory System32\Drivers and System32 of your Windows NT. ------------------------------------------------------------------------ 2 Installation NOTE This graphics driver will only work correct under Windows NT 4.0! If you install Windows NT with an ELSA graphic adapter plugged in, it's recommended to use the procedure described in paragraph 2.1. If not you may run into trouble! If you change your graphic adapter to a ELSA board use the procedure described in chapter 2.2. It is recommended to first install the driver, then shut down the computer and then change the cards! Alternatively you can change the graphic adapter and the boot in the save VGA-Mode to install the corresponding ELSA driver. If you want to update your display driver use the procedure described in chapter 2.2. NOTE To install the ELSA drivers, we use the typical installation procedure as described in the Microsoft Windows NT manual. 2.1 Installation during system installation NOTE It is possible to install the display driver later as described in 2.2. We recommend to define a driver during the installation of NT to run into a defined state. During the first or a new customized installation of Windows NT you will be asked to accept the hard- and software components Windows NT has determined. In this text screen titled "Windows NT Workstation Setup" don't accept the highlight "The above list matches my computer". Use the arrow keys to move highlight to the item after "Display:" and press ENTER. NOTE You cannot install from CD. You have to create installation disks first (see 2.2) or continue as described in 2.1.2 (recommended). 2.1.1 Installationdisks available To change the type of display to be installed select "Other (Requires disk provided by a hardware manufacturer)". You will be asked to insert a disk into drive A:. Insert disk 1, and select one of the entries matching your system: - ELSA i386 for Intel-based machines, - ELSA Alpha for computers with DEC-Alpha-processor, - ELSA PPC for PowerPCs. Now accept the list, if it matches your computer. Continue the installation following all instructions. Later on you will be asked to change the diskettes. During the installation you have to restart your computer. It is now bootet in graphics mode. Later on the dialog "Display settings" enables you to change the default resolution. Read chapter 3. NOTE It may be necessary to install the driver again when Windows NT is running to setup the ELSA OpenGL 3D-extension (GLoria-boards) which not possible here! 2.1.2 No installation disks available, installation from CD-ROM It's not possible to install the display drivers from CD-ROM or harddisk at this time. If you accept the hard- and software components Windows has detected it may result in an instable System. So don't select the "VGA or compatible" entry. You have to choose the item "Standard VGA (640x480, 16 colors)". Now you can confirm the List and continue the installation as preferred. The first time Windows NT comes up you will have a VGA resolution of 640x480 in 16 colors. When NT is running you may change to the ELSA graphics driver as described in paragraph 2.2. 2.2 Later installation Use the taskbar to select "Start" button/ "Settings" / "Control Panel" and there the icon "Display". You also can do a click on the desktop with the right mouse button to open a popup and select "Properties". In the window "Display Properties" you have to choose the the item "Settings". Click on "Display Type..." and select "Change..." in the upcoming "Display Type" dialog. A "Change Display" dialog appears where you can see the already available device drivers. NOTE The entry "ELSA"-"ELSA Winner 1000" in this listbox will install the general purpose S3 driver designed by Microsoft and NOT the ELSA drivers! Choose "Have Disk..." to install the ELSA drivers. Windows NT prompts you to enter a path where it can find the drivers. Change the default "A:\" to the path where to find the driver files e.g. "D:\WINNER\2000PROX\WINNT40\" or to the corresponding directory select the corrct dirver and confirm with "OK". You want to install a third-party driver so click on "Yes". The driver will now be installed. Close all display settings windows. NOTE With Windows NT 4.0 graphic drivers cannot be loaded dynamically. This is not an ELSA limitation. To activate the ELSA driver, the computer has to be restarted so please press "Yes" in the corresponding dialog. When you've selected to restart, the system will reboot and the initial installation is finished. NOTE Windows NT 4.0 will now restart in a resolution of 640*480 pixel at 256 colors and 60Hz refresh. To change this resolution use the "Display" application (refer also the following chapter "4. Changing the resolution after installation"). NOTE The OpenGL driver is automatically installed with the Windows NT 4.0 driver. 2.3 How to create installation diskettes If you don't have any installation disks, you can create these using your CD-ROM or a downloaded file. There is not enough space for all files on one disk so you have take three empty disks labeled "ELSA Windows NT 4.0 DISC 1", "ELSA Windows NT 4.0 DISC 2" and "ELSA Windows NT 4.0 DISC 3". Now copy the following files from your CD-ROM to: - Disk 1 ("ELSA Windows NT 4.0 DISC 1"): DISK1 ELSA.INF LIESMICH.TXT README.TXT TXTSETUP.OEM I386\WINNER.SYS I386\WINNER.DLL I386\WINNERMB.DLL - Disk 2 ("ELSA Windows NT 4.0 DISC 2"): DISK2 ELSA.INF TXTSETUP.OEM I386\ELSAOGL.DLL I386\WONCTRL.CPL I386\MONCTDEU.DLL I386\WONCTENG.DLL I386\GLSET.DLL I386\GLSETRAY.EXE COMMON\GLSET.REG COMMON\GLSET.TEX COMMON\24H96.TIM - Disk 2 ("ELSA Windows NT 4.0 DISC 3"): DISK3 I386\VIDEOCTR.EXE I386\DXCTRL.DLL COMMON\GLSETENG.HLP COMMON\GLSETDEU.HLP COMMON\ELSA.HLP COMMON\GLOBE.PPM COMMON\RAST1.PPM COMMON\CYLINDER.X COMMON\DXCTRL.REG COMMON\ELSA2.PPM COMMON\SPHERE3.X For Alpha- or PowerPC-Installation disks you have to replace the I386\-folder by the ALPHA\- or PPC\-folder with containing files from your CD-ROM. 2.4 Installing from CD-ROM or harddisk When installing the driver from CD-ROM, a harddrive or from a network-drive, all files described in 2.3 have to stay in one single directory containing the machine-dependend sub-folders. When asked for a path during installation you have to insert the full path to where the file ELSA.INF is stored. 2.5 Problems after Installation 2.5.1 No mouse-cursor You haven't selected a ELSA-Driver. The driver installed seems to be a Microsoft S3-Treiber which is nearly compatible. Temporary you may select an animated mouse-cursor in the Control Panel until you have installed the ELSA-driver. 2.5.2 You have choosen "VGA or compatible" in 2.1.2 If the installation of Windows NT isn't finished yet you may select the cancel button in the "Display-Setting"-Dialog that is shown after NT has rebooted to continue the installation in graphics mode. NT will take the standard VGA driver now. If the installation is already finished and you have no or a damaged display, try to reboot "blindly" or wait several minutes before you reset the computer. In the boot menu now select the save VGA mode. Now install the correct ELSA driver! 2.5.3 The board is not recognized Try another PCI slot. Some board manufacuters have implemented PCI slots that are not PCI compliant. ------------------------------------------------------------------------ 3 Changing the resolution after installation Start the "Display" dialog, it's "Display Settings" gives you the chance to adjust 4 parameters. - The "Color Palette" contents selections from "256 Colors" to "True Color" depending on the "Desktop Area". - The "Desktop Area" depends on the "Refresh Frequency" and the "Color Palette". - The "Refresh Frequency" allows you to select various refresh rates. - The "Font Size" lets you select large or small fonts. NOTE The "Font Size" selection appears only when you have installed Windows NT with "american" language settings. After selecting a new graphic mode you can check this mode for 5 seconds. If the test screen is OK, then select "YES" and "OK" to take the settings. Otherwise select "No" and make another selection. Windows NT 4.0 allows you to change the display settings dynamicaly without any reboot. ------------------------------------------------------------------------ 4 Additional Configuration Options 4.1 How to configure the driver In the following the settings of an ELSA graphics driver for Windows NT and the corresponding entries in the registry database will be explained. Changes can be done with the ELSA utilies MonCtrl, GLoria Settings or manually with the registry editor. NOTE Unexperienced users should not make any changes in the registry directly! Use the utilities! 4.1.1 Registry Editor Windows NT stores its configuration information in a database that is organized in a tree type format. Registry Editor enables you to inspect and modify the Registry. To run Registry Editor, run REGEDT32.EXE (in the SYSTEM32 directory). You can also use the menu "Tools"/"Registry Editor" in the application "Windows NT Diagnostics" found in the "Administrative Tools"- program group. To edit a value, simply double-click on it to invoke an edit dialog. The entries for the ELSA WINNER graphics driver are placed in the window HKEY_LOCAL_MACHINE in the path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WINNER\. 4.1.2 MonCtrl utility Start the ELSA MonCtrl utility doubleclicking the "ELSA MonCtrl" icon found in the Control Panel. Changes in MonCtrl will affect the entries in the registry. 4.1.3 GLoria Settings The ELSA GLoria Settings property page allows you to cnfigure the 3D options on ELSA GLoria graphic adapters. 4.1.4 DirectX Settings On graphic adapters that support Direct Draw the ELSA DirectX settings property page allows you to configure Direct Draw options. Direct 3D is not supported with Windows NT until now. 4.1.5 Video Control The ELSA Video Control utility allows to configure the video output on graphic adapters with Trio64V2-DX oder Virge-DX. 4.2 Multi Screen Options Some ELSA graphics adapters can be used in a multi screen mode. Two or more adapter cards and just as much monitors are driven from one computer. This will result in an enlarged desktop. A list with graphics adapters that support multi screen is found in 4.2.3. 4.2.1 Installing multi screen There is no special multi screen installation. After you have placed a second ELSA graphics adapter into your computer the Control Panel offers you new extended resolution in the "Display" utility. NOTE There is no special information that multi screen is enabled. You can only see this in the extended resolutions. 4.2.2 Configuration of the multi screen mode The entries "DesktopOnMaximize" and "ReverseScreenOrder" in the registry database influence the multi screen operation. NOTE Look for the frame "Multi Screen Options" in the MonCtrl utility. 4.2.2.1 DesktopOnMaximize This switch adjusts how dialogues and windows are displayed on the N screens. NOTE Look for "Maximize on all screens" in the MonCtrl utility. 0x0: When maximizing a window it be displayed only on the left screen. Dialogues will appear on the left screen. Advantage: Dialogues and windows aren't split by screen borders. Disadvantage: Dialogues always appear left, even if the application runs on the right screen. Position settings of MDI-applications (e.g. Microstation) will be lost after a restart of the program. 0x1: When maximizing a window it fills out all N screens. Advantage: Position settings of MDI-applications (e.g. Microstation) will be restored after a restart. Disadvantage: Dialogues and windows may be displayed on screen borders. 4.2.2.2 ReverseScreenOrder This entry exchanges the order of the N screens. NOTE "Reverse screen order" in the MonCtrl utility. 0x0: The order of the adapters is 1, 2, ..., N 0x1: The order of the adapters is N, ..., 2, 1 4.2.3 Supported graphic adapters Until now only combinations of equal ELSA graphics adapters from the following list are supported: GLORIA 4 GLORIA 8 GLORIA M GLORIA L WINNER 1000 AVI WINNER 2000 Pro/X NOTE You can only use adapters with the same memory equipment. 4.3 Monitor Timings With timing files made for your monitor you may: - Install new resolutions for a better usage of the possibilities supported by your monitor. - Modify new timings for a given resolution. NOTE Look at the frame "Monitor timings for:" in the MonCtrl utility. 4.3.1 Configuring the monitor timings The registry entries belonging to the monitor timings are placed in the subfolder WINNER\DeviceX\. 4.3.1.1 Monitor.Select This entry selects how the timing file shall be used. Ignore: All entries in the timing file will be ignored. Prefere: Resolutions listed in the timing file will be favored. If the driver supports the same resolution as listed in the timing file, the timings of the file will be prefered. Driver resolutions without correspondence in the timing file are not affected and displayed. Exclusive: All standard resolutions of the driver are thrown away. Only the new timings of the timing file are offered in the "Display"-Tool. 4.3.1.2 Monitor.Name In Monitor.Name a string to identify the timing entries is stored. This should be an identifier for ypur monitor, e.g.: ELSA GDM-17E40T 4.3.1.3 Monitor.Timings This entry containes binary data with the monitor timings taken from the timing file. These values are written by the MonCtrl utility. 4.3.2 TIM file format A file with timing entries has the extension ".TIM". It has to be placed in the SYSTEM32 folder of your Windows NT. The files containes lines with ASCII text and can be modified with every editor (e.g. NOTEPAD.EXE). The first line names the timing list (e.g. "ELSA GDM-17E40T"). This is the string displayed in MonCtrl an stored in Monitor.Name. In each of the following lines one timing is defined. Every line containes 14 comma separated values. The meaning of the values is (in correct order): - xRes: Number of pixels in X direction (e.g. 1024). - yRes: Number of lines in Y direction (e.g. 768). - Bpp: Number of bits for each pixel, for colors (e.g. 16). - Hz: Refresh frequency in Hertz (e.g. 79). - PxClk: Pixel clock in kHz (z.B. 95455). - Ht: Horizontal total in pixels (e.g. 1312). - Hfp: Horizontal frontporch in pixels (e.g. 16). - Hsw: Horizontal sync-width in pixels (e.g. 96). - Hbp: Horizontal backporch in pixels (e.g. 176). - Vt: Vertical total in lines (e.g. 800). - Vfp: Vertical frontporch in lines (e.g. 1). - Vsw: Vertical sync-width in lines (e.g. 3). - Vbp: Vertical backporch in lines (e.g. 28). - If: Interlaced flag (should allway be 0). With the given examples the file would look as follows: ELSA GDM-17E40T 1024,768,16,79, 95455, 1312,16,96,176, 800,1,3,28, 0 1024,768,32,... NOTE On the ELSA drivers CD-ROM there is a DOS utility (WINSETUP.EXE) to find out the timings for your monitor. 4.4 Gloria/OpenGL settings The following descriptions are only meant for the ELSA Gloria 4/8 graphic adapters. They belong to the 3D extensions supported by the OpenGL graphics interface. NOTE For all entries there is a correspondence in the GLoria Settings utility in the frame "GLoria Options" 4.4.1 ICD extensions The following parameters of the Installable Client Driver (ICD) affect the behaviour of the 3D functions on the Gloria. 4.4.1.1 ICDInterface.Disable This switch enables or disables the OpenGL support by the ICD driver. NOTE "Disable 3D-Extensions" in GLoria Settings. 0x0: OpenGL will be supported by the Gloria (default). 0x1: Software-OpenGL (no GLint) or OpenGL using 3D-DDI 4.4.1.2 ICDInterface.ExportAlpha Allows the hardware to use the softwares alpha channel. With Programs which don't use the alpha channel this may cause an performance loss up to 25 %. NOTE "Use alpha channels" in GLoria Settings. 0x0: The driver doesn't export an alpha channel (default). 0x1: The driver exports an alpha channel. 4.4.1.3 ICDInterface.NumberOfDisplayBuffers This switch enables and disables DoubleBuffering. The entry stands for the number of buffers. NOTE "OpenGL buffers" in GLoria Settings. 0x1: Only one display buffer is used; no DoubleBuffering. 0x2: DoubleBuffering enabled (default). 4.4.1.4 ICDInterface.SizeOfBuffer This is used to control the size in longs of the shared memory block allocated to each individual rendering context. This buffer is used when DMA is disabled or the entire DMA buffer is in use. After the next restart this change will take effect. NOTE "Interface buffer size" in GLoria Settings. Valid values: 0x100 to 0x10000, the default is 0x10000 (64 kB). 4.4.1.5 ICDInterface.SupportSingleBufferedGDI This flag decides how GDI and OpenGL commands are handled in the same window in the front buffer. NOTE "GDI in single buffered modes" in GLoria Settings. 0x0: GDI commands cannot be drawn in OpenGL windows. 0x1: OpenGL and GDI can simultaneously use the front buffer (default). 4.4.1.6 ICDInterface.SupportDoubleBufferedGDI Lets OpenGL export the ability to let OpenGL and GDI draw in the back buffer. NOTE "GDI in double buffered modes" in GLoria Settings. 0x0: GDI commands cannot be drawn in OpenGL windows (default). 0x1: OpenGL and GDI can simultaneously use the back buffer. (recommended for 3D Studio MAX) NOTE It exports the flag but all GDI calls are drawn in the front buffer! 4.4.1.7 ICDInterface.SupportOverlayPlanes This switch enables the driver to support overlay planes, which are e.g. used by Softimage. NOTE "Support Overlay Planes" in GLoria Settings. 0x0: No support for overlay planes (default). 0x1: Overlay planes are supported. 4.4.2 GLint-DMA settings The parameters of the GLintDMA group configure the DMA capabilities of the GLint. 4.4.2.1 GLintDMA.NumberOfBuffers This is used to determine the number of individual DMA buffers that can be in use at any one time. After the next restart this change will take effect. NOTE "DMA buffers" in GLoria Settings. Valid values: 0x0 to 0x4, the default is 0x4. 4.4.2.2 GLintDMA.NumberOfSubBuffers Used to control the ICD drivers subdivision of the DMA buffer. NOTE "DMA subbuffers" in GLoria Settings. Valid values: 0x0 to 0x9, the default is 0x5. 4.4.2.3 GLintDMA.SizeOfBuffer This is the total size of the DMA buffer which is devided up amongst the individual processes that use DMA. After the next restart this change will take effect. NOTE "DMA buffer size" in GLoria Settings. Valid values: 0x100 to 0x10000, the default is 0x8000 (32 kB). 4.4.2.4 GLintDMA.CachedBuffers This switch enables the driver to cache GLint data in the processors cache. Though the GLint reads all date from the main memory, differences between memory and cache may appear. After the next restart this change will take effect. NOTE "Cached DMA" in GLoria Settings. 0x0: forces uncached DMA 0x1: forces cached DMA 0x2: let the driver decide whether it uses cached or non cached DMA (default). 4.4.3 OpenGL.UseFastClear This value affects the usage of fast clear planes. When running multi-threaded applications it may be necessary to disable the useen of the fast clear planes. After the next restart this change will take effect. NOTE "Use Fast Clear Pages" in GLoria Settings. 0x0: Fast clear planes disabled. 0x1: Fast clear planes enabled NOTE For MicroStation this switch has to be set! 4.4.4 OpenGL.UseHiQualityTexture This switch affects the precision and resolution for texture mapping. 0x0: Normal precision and resolution 0x1: High precision and resolution 4.4.5 OpenGL.SupportSoftimage This switch fixes corrupted menue and window borders in Softimage 3.01. Use this switch only when running Softimage 3.01! NOTE "Support Softimage" in GLoria Settings. 0x0: Softimage fix not activated (default) 0x1: Softimage fix is active. 4.4.6 OpenGL.SupportSoftimage351 This switch enables functions especially to support Softimage 3.51. Use this switch only when running Softimage 3.51! NOTE "Support Softimage 3.51" in GLoria Settings. 0x0: Softimage 3.51 fix not activated (default) 0x1: Softimage 3.51 fix is active. 4.4.7 OpenGL.DisableMipMaps This switch allows the user to force rendering performance when using textures by disabling the mipmaping. This overrules every applications OpenGL command for texture filtering. At the same time you will lose accuracy. NOTE Slider "Texture Quality" in GLoria Settings. 0x0: Mip-Maping is enabled 0x1: Mip-Maping is disabled 4.4.8 OpenGL.TextureCompression This value is used to reduce the texture size actually downloaded to the texture memory on the graphics board by simply shrinking the texture. This will enhance the rendering performance. At the same time you will lose accuracy. NOTE Slider "Texture Quality" in GLoria Settings. 0x0: No texture compression 0x1: Texture compression by 1/4 0x2: Texture compression by 1/16 0x3: Texture compression by 1/64 4.5 Other settings 4.5.1 3DDDI.Disable This switch enables or disables the drivers support for 3D-DDI. NOTE "Disable 3D-DDI" in GLoria Settings. 0x0: 3D-DDI is enabled 0x1: 3D-DDI is disabled (default) NOTE 3D-DDI will not be supported in further versions though Microsoft will stop all developements on 3D-DDI. 4.6 DCI The driver supports primary surfaces. In Windows NT 4.0 this support will be dropped. 4.7 ELSA POWERlib ELSA offers optional for the programmer the toolkit POWERlib for creating your own applications using the ELSA graphics board for graphical output. This tool is available for Windows NT. ------------------------------------------------------------------------ 5 Known Problems - If the application under OpenGL requests "Double Buffering" and the GLoria cannot realize it anymore (1024x768x32 bpp), software emulation will be automatically installed. To force hardware OpenGL you have to disable double buffering in your application! - The driver cannot run on a system where a COM4 port is installed. - Changing the display resolution while an OpenGL app. is running crashes the system - Booting the system last too long. - Don't use the standard S3 display driver. While setup detects your computers hardware choose cancel to avoid the installation of the S3 driver. - For 3D Studio MAX GDI in double buffered modes is recommended. - When running an OpenGL application and switching from DOS box to DOS fullscreen and back, the system crashes. When changing the graphic modes Windows NT restarts the graphics driver. Because of this reinitialization the driver loses all information about running OpenGL tasks. - The system can crash when using DirectDraw Video Acceleration while changing display resolution or switching to fullscreen DOS or while logging off. The problem occurs on WINNER 3000 S/M/L, WINNER 2000 AVI/S3D, WINNER 1000 T2D, VICTORY 3D/3DX and TRIO V cards with ELSA Vision, but not ActiveMovie. This problem will be fixed until next driver release. - Don't use software cursor (animated cursors too). ------------------------------------------------------------------------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.