Important Information about Intel(R) Server Control v3.1.1 March 6, 2001 Important Notes A. System Requirements B. Install C. Additional Instrumentation Setup D. Uninstall E. Enterprise Management Console Information F. Direct Platform Control G. Client System Setup Utility H. Independent Hardware Vendor (IHV) Instrumentation I. LanAlert Viewer J. Documentation K. Platform Instrumentation Control L. Platform Instrumentation M. Stand-alone Console NOTE: Known issues with the ISC software are documented in a file called EnuErrata.txt. Please review that file for any known product issues. ********************************************************************** Information in this document is provided in connection with Intel products. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. Except as provided in Intel's Terms and Conditions of Sale for such products, Intel assumes no liability whatsoever, and Intel disclaims any express or implied warranty, relating to sale and/or use of Intel products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. (Intel makes no representations or warranties and specifically disclaims all liability as to the sufficiency, reliability, accuracy, completeness or usefulness of information in this file or in the ISC software). Intel products are not intended for use in medical, life saving, or life sustaining applications. Intel may make changes to the information contained in this file and/or the ISC Software, specifications, and product descriptions at any time, without notice, (however, Intel has no obligation to provide modifications, updates or support for same.) (Copyright c Intel Corporation 2000). *Other product and corporate names may be trademarks or registered trademarks of other companies, and are used only for explanation and to the owners' benefit, without intent to infringe. ********************************************************************** ********************************************************************** A. System Requirements: ********************************************************************** 1. The following is the operating systems supported for the managed server for Intel Server Control server instrumentation software: Server Operating Systems: - Microsoft Windows 2000 Advanced Server SP1 - Microsoft Windows NT 4.0 Server SP6a - Novell NetWare 5.1 - SCO UnixWare 7.1.1 - Red Hat Linux 6.2 SBE 2 (System Builder Edition 2) (not supported for SRPL8 baseboard). Console Operating Systems: - Microsoft Windows 98 Second Edition - Microsoft Windows 2000 Advanced Server SP1 - Microsoft Windows 2000 Professional SP1 - Microsoft Windows NT 4.0 Server SP6a - Microsoft Windows NT 4.0 Workstation SP6a 2. For a list of supported features on each platform, please reference ISC Installation Guide under Platform Compatibility Matrix. 3. For Windows 98 consoles, ISC setup requires that the following software components be installed: - Remote Registry Service The Remote Registry Service can be found on the Windows 98 Resource Kit. Other software applications may also require this software component, so it may already be installed on your system. Before installing ISC, install this software component and then reboot the system. To install the Remote Registry Service the user must be running Windows 98 and have the Resource kit in the CDROM drive then: 1. Access the control panel via "Start" 2. Double click on Network Icon 3. Access the "Configuration" tab 4. Select "service" 5. Press the Add button 6. Press the "Have Disk" button 7. Press the "Browse" button 8. Locate the drive containing the Resource Kit 9. Access the NetAdmin directory 10. Access the Remotreg Directory 11. Highlight "regsrv.inf" file 12. Press the "OK" button on the "Open" screen 13. Press the "OK" button on the "Install from disk" screen 14. Press the "OK" button on the "Select Network Service" screen Remote Registry service should have installed. Check the Configurations in the "Configuration" window and Remote Registry Service should be listed. Note: If the Remote Registry service is not installed on Win98 you get the following error message after manually typing in the system destination: Intel Server Control Setup A dynamic link library (DLL) initialization routine failed. 4. For Windows NT 4.0 consoles, DPC setup requires that the following software components be installed: - Service Pack 6a or above. - RAS (Remote Access Service, if connectivity will use a modem. See Windows Help for RAS installation instructions. 5. Netware Client Services For Windows 98 and Windows NT Microsoft Netware Client Services on Window 98 DO NOT support DS (directory services) for Netware systems. Consequently, if a NW server is configured not as a tree root, but rather as part of an existing tree it cannot be accessed remotely. However, Novell Netware Client supports both Bindary and DS services. As a result, remote connection on Windows 98 and Windows NT systems is made possible for all NW servers. To summarize, if you are using a Windows 98 or Windows NT console to install remotely to a NW server that has been configured as a subtree, you need to install Novell Netware Client Services. Additionally, you must log on as the administrator/supervisor of the network, not just as a user with admin/supervisor rights for authentication on the remote server for the ISC Install. If you are not logged in as the administrator/supervisor or the network, ISC can not install to the remote server in a NW 5.0 tree. 6. ISC running in a LANDesk Server Manager v3.0 (LDSM) environment requires the following LDSM patch releases from Intel: SR1, SR2, and SR3 The patch releases can be downloaded from the Intel support web site http://support.intel.com. ISC running in a LANDesk Server Manager v6.1 environment does not require these patches. 7. Customers using the Intel EtherExpress(TM) Pro/100b LAN Adapter should download and install the most current driver from the following Intel web site prior to installing ISC software. "http://support.intel.com/support/etherexpress/ pro100/software.htm" Customers using the Intel LAN Adapters should download and install the most current driver from the following Intel web site prior to installing ISC software. "http://support.intel.com/support/network/adapter/pro100/index.htm" 8. UnixWare 7.1.1 Requirements UnixWare installations must be installed with multi-processor support (osmp module) during installation or later. For information on adding the osmp package to UnixWare, see: http://www.sco.com/cgi-bin/ssl_reference?110311 The minimum recommended patch list for UnixWare 7.1.1 should also be applied. It can be located at: http://www.sco.com/support/toolbox/patch.html Please also install the VisionFS* package on the UnixWare server. 9. Intel Server Control supports servers with the following Intel baseboards: Intel(R) SRPL8 Intel(R) L440GX Intel(R) SPKA4 Intel(R) SRKA4 Intel(R) SBT2 Intel(R) STL2 10. Windows 98 SE consoles require that Dial-Up Adapter and TCP-IP->Dial-Up Adapter protocol services be installed. To verify that they are installed: 1. Right-click the Network Neighborhood. 2. Click Properties. 3. Verify that Dial-Up Adapter and TCP/IP->Dial-Up Adapter are listed on the Configuration tab list. 4. If they are not installed: a. Click the Add button, select Adapter, and Dial-Up Adapter. b. Click OK. c. Click the Add button, select Protocol, and TCP/IP->Adapter. d. Click OK. 11. Intel network driver requirement for SPKA4 server: For the Intel SPKA4 server platform, user must install a separate network driver which could be downloaded from the following URL: http://support.intel.com/support/network/adapter/pro100/pro100dp/software.htm The following are the versions to be used for each OS Red Hat Linux 6.2 SBE 2 e100-1.1.1.tar.gz Version 1.1.1 Novel Network 5.1 ce100b.lan Version 1.67 Windows NT 4.0 SP6a e100bnt4.sys Version 4.02.25 Windows 2000 Advance Server e100bnt5.sys Version 4.02.27 UnixWare 7.1.1(in 7.1.1 CD) eeE.pkg Version 1.3.9 Except UnixWare 7.1.1, the network driver that comes with the OS CD-ROM causes problem(s) and should not be used. ********************************************************************** B. Install ********************************************************************** 1. The Setup utility will only enable the Local Console install if a supported EMC (Enterprise Management Console) environment is detected on the installation machine. Supported EMCs are: LDSM - LANDesk(R) Server Manager v6.1 with Service Release 2 HPNNM - HP OpenView* Network Node Manager v6.1 with patch release NNM_0085 CA Unicenter TNG Framework V2.2 2. The ISC services on a managed server may take a few minutes to completely initialize. The exact amount of time will vary depending on the speed of the server and the software installed. If an ISC console is started in order to manage the server, prior to all the services being initialized, then ISC may display incomplete information. This may also be reflected in sluggish response from the console, or not all the sensor folders being displayed, or on rare occasions, it is possible for the former console (LSC) to be displayed due to the length of initialization of network protocols. 3. We recommend that you reboot your system (console or server) after installing any ISC component. 4. SCO UnixWare v7.1.1 system have DMI access set to read-only by default. This will prohibit ISC from changing thresholds, enabling the watchdog timer, Console login and various other functions. In order for ISC to perform properly, the write permission for DMI service provider must be enabled. To do so on UnixWare v7.1.1, log in as 'root' and perform the following steps: 1. Stop the DMI Service Provider (dmi stop) 2. Edit the file S89dmi (in the directory /etc/rc2.d) 3. Change the line that says '$DMI_PATH $@' to '$DMI_PATH $@ -w' 4. Save the file and restart the service provider (dmi start will start the SP) Once this change is made to S89dmi file it is valid for all future sessions. 5. Silent install A. Silent install will work best, if ISC is installed on one server at a time. B. To install remotely to a Win2k or WinNT system, you must use the same user ID and password in the configuration file as the one you have used to login to the Win2k or WinNT system. C. If the current setting of Windows NT only accepts encrypted passwords then the user would not be able to connect to a SCO UnixWare server running SCO VisionFS. Setup will only modify the Windows setting during an interactive install session so that Windows NT can connect to SCO UnixWare server running VisionFS. For Silent install the user must set the registry settings himself as follow: 1- Locate HKLM\System\CurrentControlSet\Services\Rdr\Parameters 2- Create a string value = "EnablePlainTextPassword" 3- Set the data for the above string created to 1 (DWORD) 4- Reboot the system Important: Netware and Unixware servers must manually be rebooted after silent install is completed. 6. LANDESK integration will be done automatically if LANDESK is present on the system on which ISC is installed. ********************************************************************** C. Additional Instrumentation Setup: ********************************************************************** 1. Depending on the baseboard type, the Intel Server Control software installs third party instrumentation (e.g., SCSI, NIC). The enabled/disabled status of the instrumentation varies depending on the server OS. See the Intel Server Control Installation and User's Guide. 2. On supported baseboards ISC uses the Event Logging feature of the BIOS. To enable this feature, boot from your server's System Setup Utility (SSU), or BIOS setup utility (F2) and set the following options under System Management Options: For Intel(R) SRPL8 MP server System Event Logging: Enabled For Intel(R) LA440GX DP server System Event Logging: Enabled For Intel(R) SPKA4 MP Server: System Event Logging = Enable For Intel(R) SRKA4 MP Server: System Event Logging = Enable For Intel(R) SBT2 DP Server: System Event Logging = Enable For Intel(R) STL2 DP Server: System Event Logging = Enable 3. The broadcast action of ISC applies to all active connection(s). In Windows NT or Windows 2000, even if the connection to a server is persistent, the operating system might use lazy connection algorithm. That is the connection might not be actually made until there is a need for it (such as when a user click on the drive to expand the content). In those instances, the broadcast would not applies to those non-active connection. 4. By default, the ISC ICMB daemon/service does not start automatically. The ISC ICMB daemon/service needs to be started in order for the ICMB support to be enabled. The following describe how to start the ICMB daemon/service manually: Under Windows NT4, launch the services applet under control panel, manually start the "Intel EIF Agent" service. Under Windows 2000 Advance Server. launch the services applet under Administrative tools, manually start the "Intel EIF Agent" service. Under NetWare 5.1, edit the SYS:\SYSTEM\AUTOEXEC.NCF file to uncomment the line "rem load eif" so that it reads "load eif" instead. Under UnixWare 7.1.1, /etc/init.d/isc script with "start-icmb" or "stop-icmb" option. The is no ICMB support on Red Hat Linux 6.2 SBE2. ********************************************************************** D. Uninstall: ********************************************************************** 1. Several files may not be removed due to services that may be running during the ISC uninstall. These are documented in the errata.txt file, along with possible workarounds. 2. We recommend that you reboot your system (console or server) after uninstalling any ISC component. ********************************************************************** E. Enterprise Management Console Information: ********************************************************************** 1. If ISC was operating via LDSM and LDSM continues to run while a remote server goes through a reboot cycle, then the handle information that LDSM is maintaining so that ISC can access that server is no longer valid after the server goes down. If LDSM attempts to launch ISC using the old information then it will fail. You can refresh the LDSM information by using the 'Apply' button from the launch window or select another area of LDSM and then reselect ISC, and then try to launch. 2. In order for the DMI-SNMP Translator traps to be displayed in the HP OpenView event windows, users need to use the EVENT CONFIGURATION menu item, pick the eEventGenerationXXX entry (where XXX is a DMI group name) in the "Enterprises" window, and then double click each trap under "Events for Enterprise eEventGenerationXXX" window. A "Modify Event" window will be displayed. Then go to the "Event Message" page and choose the "Log and Display in Category" radio button and choose the event category in which the users want the traps to display. 3. If the LDSM snap-in is only installed on the server you are connecting to with LDSM, an Intel Server Control component will still appear in the snap-in folder. This indicates that the snap-in is supported by the server. If the snap-in is also supported on the client, an icon will appear next to the snap-in, identifying that it is ready to launch. 4. Multiple copies of Intel Server Control components may appear in LDSM if the newest patches are not installed. Patches or support exist for LDSM version 6.04 and greater. The patch releases can be downloaded from the Intel support website. http://support.intel.com/support/landesk/servermgrpro/software.htm 5. Intel Server Control components may not appear in LDSM if the newest patches are not installed. Patches or support exist for LDSM version 6.04 and greater. The patch releases can be downloaded from the Intel support website. http://support.intel.com/support/landesk/servermgrpro/software.htm 6. Intel Server Control's AMS alert configuration support requires the LDSM components to be loaded before ISC components. If LDSM is loaded after ISC, an attempt to configure AMS alert actions wil result in a message stating that the application is not registered with AMS. This can happen with NetWare servers if the SM_AUTO.NCF is run manually after the ISC support is already running. The best way to avoid this issue is to edit the 'REM Sm_auto.ncf' line that LDSM places in the AUTOEXEC.NCF by removing the 'REM'. Also, make sure that the 'Sm_auto.ncf' line precedes the 'ISC_ON.NCF' line. This will ensure that LDSM support is loaded before ISC support. 7. Customers using HP Openview should not load/install it on a server with LDSM. The HP Openview installation replaces the standard SNMP service handlers with its own, which do not currently handle an SNMP agent with multiple OIDs. This results in an SNMP query not working on the server where HP Openview is installed. Events will continue to be generated correctly, but an SNMP console will no longer be able to query for component information from the affected server. HP Openview should be installed on separate console computer. 8. The DMI Service Provider Database does not relinquish space from expired and deleted registrations. This space is not reused by the Service Provider and causes the Database to continually grow. This issue can also be seen if components and groups are deleted from the Service Provider Database. Hewlett Packard proactively has announced an update to Network Node Manager* v5.02, patch release NNM_0085, which addresses the issue with the DMI 2.0 Service Provider. Hewlett Packard will post the update to NNM v5.02 on the world wide web at: http://www.hp.com/go/openview. From this page select "support" and then "patches". Download the update and follow the instructions for installation. This problem has not been seen with Network Node Manager* v6.1. ********************************************************************** F. Direct Platform Control: ********************************************************************** 1. Direct Platform Control (DPC) Console provides emergency management of servers remotely. DPC Console provides capabilities to power on or power off a server remotely, or help diagnose a problem on a server. DPC Console is independent of the Operating System installed on the server. DPC Console provides detailed information about the hardware components on the server. For more information, see the DPC Users Guide, ENUDPCUG.pdf, located in the installation directory. For the supported DPC features on each server, see ISC Installation Guide under Platform Compatibility Matrix. 2. Server-side modems are configured differently depending on the implementation of the EMP features in the firmware. The following modem configuration setting are required for the following servers: Modem Config Server List AUTO-ANSWER = ON nightshade through saber DTR = NORMAL Modem Config Server List AUTO-ANSWER = OFF Koa, Lion, Tiger DTR = ALWAYS_ON 3. Total Cost of Ownership (TCO) port traffic provides a conduit for DPC LAN connectivity. If the SKA4 initially released onboard NIC drivers are used, it may cause Direct Platform Control (DPC) over a LAN connection to timeout on Red Hat Linux 6.2 SBE2, NetWare 4.2/5.1, during system reset. This occurs because the network adapter drivers for SRKA4, SPKA4, ISP4400 based system's TCO port is overloaded. In addition, all NIC connections regardless of the operating system, will see decreased network performance when DPC over LAN is operating. The TCO port driver patches found at: http://support.intel.com/support/motherboards/server/isc/software.htm are required on Linux and NetWare based systems. For consistency, it is also recommended that SKA4 based systems also upgrade to the Windows patch listed at the same site. ********************************************************************** G. Client System Setup Utility: ********************************************************************** 1. The Client System Setup Utility (CSSU) provides a way for users to configure system settings and view the system error log, sensor data records, and field replaceable unit information. When establishing a connection to a server using CSSU, the server is rebooted to a service partition that is located on a hard drive on the server. Depending on where the hard drive containing the service partition is located on the server, it can take a fair amount of time for the CSSU to be ready to accept user input. Note that there may be problems with files on the service partition that could prevent the service partition software from booting correctly. If this is the case the service partition may need to reinstalled. For the supported CSSU features on each server, see ISC Installation Guide under Platform Compatibility matrix. ********************************************************************** H. Independent Hardware Vendor (IHV) Instrumentation: ********************************************************************** 1. When the Symbios NTSDMS.EXE is started, it begins a discovery process by scanning the Windows NT SCSI registry entries. However, Windows NT treats all ATAPI drives as if they were SCSI devices. The following Windows NT APIs are called by the Symbios service in order to determine whether the SCSI port registered with Windows NT is a Symbios controller: RegOpenKeyEx RegEnumKeyEx RegQueryValueEx In the case of some CD-ROMs, JAZZ* or Zip* drives, these drives may be present, but without media they will cause check conditions. The miniport driver for these types of devices report "No Disk in Drive x:". For a JAZZ or Zip drive and some CD-Roms this is a valid response and it fulfills the needs of the discovery process by providing information for identifying the device. For this reason the error message is ignored during the discovery process, the drive is 'discovered' and entered into the database of active and available peripherals and processing continues without any attention to the error message, "No disk in drive x: ." As such, this is a artifact of discovery and does not indicate a problem. The status is reconciled later during device polling when the 'discovered' devices are queried for their media status. 2. If the server is configured to use IDE instead of SCSI drives, there should be no negative impact leaving the installed SCSI IHV instrumentation executing. If system resources are an issue, the SCSI instrumentation may easily be prevented from executing the next time ISC starts as detailed below for each operating system. Windows NT and Windows 2000: 1. Open Control Panel, click on Services. 2. For each service to disable, double click on the service, select Startup Type, and set it to Manual. For servers using Adaptec* SCSI controllers, the services to set to manual start are CIO Array Management Service, and Adaptec CIODMI. For servers using LSI Logic SCSI controllers, the service to set to manual start is LSI SCSI Service. For servers using QLogic SCSI controllers, the service to set to manual start is QLogic SCSI Utility Service. NetWare: 1. Edit the ISC_ON.NCF file. 2. For servers using Adaptec SCSI controllers, ensure that the remark indicator, "rem", begins the lines which would load nwaspi, iomgr and ciodmi. For servers using LSI Logic SCSI controllers, ensure that the remark indicator, "rem", begins the line which would load symcinw2. There is currently no SCSI instrumentation for NetWare for servers using QLogic SCSI controllers. 3. Save ISC_ON.NCF. UnixWare: 1. For servers using Adaptec SCSI controllers, move the files iomgrd and ciodmi from the /intel/isc directory to another directory. 2. For servers using LSI Logic SCSI controllers, move the file symciuw from the /intel/isc directory to another directory. 3. There is currently no SCSI instrumentation for UnixWare for servers using QLogic SCSI controllers. 3. When a Windows NT or Windows 2000 Advanced Server using an Adaptec SCSI controller boots, there may be numerous informational events titled CI/O Event for a Storage Device. These events correspond to SMART being enabled on each SMART capable SCSI drive in the configuration. ********************************************************************** I. LanAlert Viewer: ********************************************************************** 1. The ISC LanAlert Viewer only works on English/German/Spanish Windows platforms right now. Chinese will be supported in later releases. 2, In order for the LanAlert Viewer to run properly, the minimum display setting has to be 256 colors with resolution at 800*600 or higher. 3. In order for LanAlert Viewer to work properly, it is required to have the SNMP trap service installed. The service can be installed from the Windows NT resource kit CD or the Windows 2000 CD. 4. The Java Runtime Environment needs to be configured to load the Chinese font file when running in a Chinese Windows environment. The Chinese font file is located at c:\Program Files\JavaSoft\Jre\1.3\lib\font.properties.zh (assuming JRE is installed in the c:\Program Files folder). The file needs to be renamed to replace the default fone file (font.properties) before launching the LanAlert Viewer. ********************************************************************** J. Documentation: ********************************************************************** 1. On-line documentation for Intel Server Control is available in Adobe Acrobat* format (.PDF). The documentation is installed with the ISC software during installation into the %ISC_PATH%\DOCS directory. Adobe Acrobat* Reader version 4.0 or higher is needed to read these files. You can obtain Adobe Acrobat* Reader v4.0 or higher, at the following location: http://www.adobe.com/products/acrobat/readstep.html ********************************************************************** K. Platform Instrumentation Control ********************************************************************** 1. After updating the FRU component on a server with ISC 3.1 Instrumenta- tion installed, the password used for user authentication when launching Platform Instrumentation Control will change to the default supplied with the FRU update. Any previously stored password for that server that the user may have used to access Platform Instrumentation control will have been invalidated upon updating the FRU component. ********************************************************************** L. Platform Instrumentation ********************************************************************** 1. The DMI database (sldb.dmi) could grow over time as MIF files are installed and un-installed. The DMI database does not reclaim or reuse the space when a MIF file is un-installed, so the database will grow even if the same MIF file is un-installed and then re-installed. If the size of the sldb.dmi file is a concern, the solution for reducing its size is to delete the file and rebuild the DMI database, keeping in mind that you will lose any threshold settings that are different from the default settings. To delete the DMI database, follow these steps: 1a. On an NT server, use 'Control Panel - Services' to stop the Win32 Service Provider (win32sl). 1b. On a NetWare server, unload the NetWare Service Provider (nwsl.nlm). Other nlm's that depend on nwsl will need to be unloaded also. 2. Delete the DMI database file (sldb.dmi) from the following two locations: For NT: a. %WIN32DMIPATH%\mifs b. %WIN32DMIPATH%\mifs\backup For NetWare: a. SYS:SYSTEM\dmi\netware\mifs b. SYS:SYSTEM\dmi\netware\mifs\backup 3. Any MIF files in the ...\mifs\backup directory that are no longer applicable to this server may be deleted also. 4a. On an NT server, move all MIF files except the service provider MIF, Win32sl.mif, from the %WIN32DMIPATH%\mifs\backup directory to the %WIN32DMIPATH%\mifs directory. 4b. On a NetWare server, move all MIF files except the service provider MIF, nwsl.mif, from the SYS:SYSTEM\dmi\netware\mifs\backup directory to the SYS:SYSTEM\dmi\ netware\mifs directory. 5. Re-boot the server. During the boot process, the DMI database will be rebuilt using the MIF files found in the ...\mifs directory. NOTE: When MIFs are un-installed and re-installed, the characteristics of the most recently installed MIF will be used for event generation. 2. The first time the server instrumentation runs after installation, all records of the System Event Log (SEL) are read and processed. The server instrumentation will start from the first record of the SEL and return a DMI indication for each record in the SEL. If SNMP services are enabled, then the server instrumentation will also generate a SNMP trap for each indication. All default LRA actions associated with each indication will occur (i.e., log to disk, popup messages, broadcast messages, write to LCD). These events will happen regardless of the date and time when the actual event happened that caused the SEL entry to occur. After the SEL file has been processed once, only new entries to the SEL will generate DMI indications and SNMP traps. For this reason, if the SEL has many entries, it takes ISC GUI long time to initialize when first time ISC is launched after the installation. The GUI keeps refreshing the screen for each entry in SEL. If the old SEL entries are no longer needed, to avoid this long delay in the ISC initialization, SEL log could be cleared before launching the ISC (by running BIOS setup - hitting F2 at system boot up, select Server management, then enable the entry for clearing the SEL). ********************************************************************** M. Stand-alone Console ********************************************************************** 1. The ISC discovery process could be very slow on Win98. When the ISC stand-alone console is started on a Win98 system, the process can be very slow (compared to NT) when trying to discover the entire subnet (0 ~ 255). The system is slowed down by the number of threads being started to run ISC discovery on all of the servers. Win98 does not handle large number of threads as well as NT and probably lowers priority on most of the discovery threads, which causes the ISC servers being added to the console in a slow manner. A work-around is to start each ISC discovery on a smaller range of IP addresses. Tests show reasonable performance on 128 ISC discovery threads (depending on available system resources), so a discovery on IP address range 0 ~ 255 can be split into two discoveries, 0 ~ 127 and 128 ~ 255. 2. ISC stand-alone is implemented as an ActiveX* control and can run in "container" applications that support ActiveX . Example "container" applications are: Microsoft Internet Explorer* (IE) Netscape Navigator* with plug-in that supports ActiveX controls such as: ScriptActive* by NCompass Labs Inc or Esker Plus 3.0* by Esker US Inc. or Microsoft Management Console (MMC). MMC requires IE v4.0 or higher. Note: (*)Third-party brands and names are the property of their respective owners. ********************************************************************** End of readme file **********************************************************************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.