********************************************************************************
* *
* INTEL CORPORATION PROPRIETARY INFORMATION *
* This software is supplied under the terms of a license agreement or *
* nondisclosure agreement with Intel Corporation and may not be copied *
* or disclosed except in accordance with the terms of that agreement. *
* Copyright (c) 1999, 2000 Intel Corporation. All Rights Reserved. *
* *
********************************************************************************
Alert on LAN** Software Release 2.5/Build 6
============================================
SUMMARY
This document discusses what is provided with this release,
how the directory structure is organized, and instructions on
how to use the provided content.
Please see the file relnotes.txt for documentation on
known errata and a summary of changes from the previous
release.
SOFTWARE CONTENT DESCRIPTION
This release contains the Alert on LAN software
release 2.5/Build 6 executables and sample source
code.
TABLE OF CONTENTS
ALERT ON LAN 2 PROXY
- TRAPS FORMATS GENERATED BY ALERT ON LAN 2 SNMP EXTENSION AGENT:
ALERT PROXY SERVER SETUP
- RUNNING THE ALERT PROXY SERVER/SNMP ALERTER ON MICROSOFT WINDOWS 95
- ALERT PROXY SERVER/SNMP ALERTER INSTALLATION
- ALERT PROXY SERVER/SNMP ALERTER INSTALLATION (SILENT MODE INSTALL)
- RUNNING THE ALERT PROXY SERVER/SNMP ALERTER ON MICROSOFT WINDOWS NT* 4.0 AND WINDOWS 2000
- RUNNING THE ALERT PROXY SERVER/SNMP ALERTER ON MICROSOFT WINDOWS 95
- UPGRADE NOTES
SAMPLE ALERT ON LAN PROXY SHIM APPLICATION (AOLNAPP)
- GENERAL DESCRIPTION
- INSTALLATION AND BUILD NOTES
- USAGE NOTES
ALERT ON LAN CLIENT MANAGEMENT AGENT CONFIGURATION NOTES
- SPECIAL NOTES REGARDING BASIC ALERT ON LAN SYSTEMS
- AGENT ERROR, WARNING AND INFORMATIONAL CODES
ALERT ON LAN CLIENT MANAGEMENT AGENT SETUP
- RUNNING THE ALERT ON LAN AGENT ON MICROSOFT WINDOWS* 95
- ALERT ON LAN CLIENT MANAGEMENT AGENT INSTALLATION
- ALERT ON LAN CLIENT MANAGEMENT AGENT INSTALLATION (SILENT MODE INSTALL)
- UPGRADE NOTES
ALERT ON LAN CLIENT CONFIGURATION CONSOLE
- INSTALLING AND RUNNING THE CONSOLE
- CONSOLE HELP FILE
- BUILDING THE CONSOLE
SAMPLE ALERT ON LAN AGENT CLIENT
- INSTALLATION REQUIREMENTS
- USAGE
DOS AGENT CONFIG
- INSTALLATION REQUIREMENTS
- USAGE
AOLEDIT APPLICATION
- GENERAL DESCRIPTION
- USAGE AND NOTES
ALERT ON LAN CLIENT MANAGEMENT DRIVERS
- NETALRT DRIVER
- PLATALRT DRIVER
ALERT ON LAN V2.5 BIOS SDK
- BASIC ALERT ON LAN (ICH) BIOS SAMPLE
- BASIC ALERT ON LAN (ICH2) BIOS SAMPLE
- ALERT ON LAN 2 (ADVANCED ALERT ON LAN ASIC -- CAPE LOOKOUT) BIOS SAMPLE
- ALERT ON LAN 2 (82550 INTEGRATED ADVANCED ALERT ON LAN - GCL) BIOS SAMPLE
- ALERT ON LAN 2 COMBINED ICH/CAPE LOOKOUT BIOS SAMPLE
================================================================================
== ALERT ON LAN 2 PROXY
================================================================================
Alert on LAN 2 Proxy ships with three binaries and resource DLLs for
english and other languages. It includes a set of files for installing and
uninstalling Alert on LAN Proxy server and SNMP extension DLLs.
TRAPS FORMATS GENERATED BY ALERT ON LAN 2 SNMP EXTENSION AGENT:
---------------------------------------------------------------
Alert on LAN 2 SNMP extension agent has the capability to generate SNMP traps
in two different formats; Platform Event Trap (PET) and Alert on LAN SNMP
trap format. One can choose the SNMP trap format via registry settings.
By default, the Alert on LAN 2 SNMP extension agent generates SNMP traps in PET
format. One can configure the extension agent to generate traps in
Alert on LAN SNMP Trap format by changing the registry variable
HKLM\SOFTWARE\Intel\Alert on LAN\Proxy\PET Format Traps to '0'.
1 is the default value and configures extension agent to generate SNMP traps
in PET format.
================================================================================
== ALERT PROXY SERVER SETUP
================================================================================
RUNNING THE ALERT PROXY SERVER/SNMP ALERTER ON MICROSOFT WINDOWS 95
-------------------------------------------------------------------
The Alert on LAN Proxy requires newer versions of COM DLLs than those found
on Windows 95 retail version (SR1). These DLLs are found on standard
Windows 95 OSR2.5 installations, however OSR2.5 is only readily available
to OEMs, not to end-customers.
This issue can be resolved by installing the Microsoft DCOM patch 'DCOM95
version 1.2' . This is available (as of 01-28-99) from the Microsoft
website at:
http://www.microsoft.com/com/dcom/dcom1_2/dcom1_2.asp
The Alert on LAN Alert Proxy requires newer versions of SNMP support files
than those found on Windows 95 retail version (SR1). A recommended method to resolve this issue involves installing the Microsoft Windows 95 Sockets 2 Update available from the Microsoft website at:
http://www.microsoft.com/Windows95/downloads/contents/WUAdminTools/S_WUNetworkingTools/W95Sockets2/Default.asp
ALERT PROXY SERVER/SNMP ALERTER INSTALLATION
--------------------------------------------
Prior to installation, the Microsoft SNMP agent must be installed. Also,
the Alert Proxy Server may require installation of operating system
patches. See below for operating system specific instructions about SNMP
Agent installation.
To install the Alert Proxy Server, run "setup.exe" from the root directory
of the installation media found under proxy\install\snmp.
The setup program will prompt whether to install the SNMP shim in addition
to proxy binaries. The Alert on LAN Proxy's SNMP shim install requires the
Windows SNMP agent be installed before the SNMP shim is installed. If the
SNMP install does not find the SNMP agent registry keys, the SNMP shim
install fails with a warning, and the rest of the proxy installation
continues. If the Microsoft SNMP Agent is not installed, install the
Microsoft SNMP Agent and restart the Alert Proxy Server the installation.
By default, the Alert Proxy Server listens for Alert on LAN alerts on port
number 5500. If this port number conflicts with existing applications, the
user can edit the following registry key with a new port number:
HKLM\SOFTWARE\Intel\Alert on LAN\Proxy\Default IP port Number
After setup is complete, please reboot the system.
Uninstallation is handled via the Control Panel's Add/Remove Programs
utility.
ALERT PROXY SERVER/SNMP ALERTER INSTALLATION (SILENT MODE INSTALL)
------------------------------------------------------------------
Command line usage for installation:
setup "key" "value" -s
By default, the silent-mode install does not install support to enable SNMP
trap forwarding. To install the SNMP shim in addition to the proxy
binaries:
setup "key" "value" "snmp" -s
"key" A string which will be used to create a new unique
registry key.
"value" A string which will be used as the new registry
key's value.
-s This parameter forces silent mode.
The double quotes around the key, value, and SNMP parameters are required.
Sample command line for install invocation:
setup "foobar" "c:\program files\intel\foobar\foobar.exe" -s
Sample command line for SNMP shim install invocation:
setup "foobar" "c:\program files\intel\foobar\foobar.exe" "snmp" -s
Uninstall can be invoked silently using Apuninst.exe which is copied to the Alert on LAN install directory during installation. For best results, Apuninst.exe should be copied to another directory (outside of the Alert on LAN install directory) and invoked from that other directory. If left in the Alert on LAN install directory, Apuninst.exe makes a best-effort attempt to delete itself during the uninstall process, but due to system-specific timing issues, the executable and directories in which it resides may not be deleted following an uninstallation.
Command line usage for uninstallation:
apuninst "key" "value"
"key" A string which will be used to locate the
unique registry key used for installation. This
string must be an exact match for the string
used in the installation command line invocation
or the uninstall will not be successfully
invoked. The string is case-sensitive.
"value" A string which will be used to verify as a
match for the unique registry key's value. This
string must be an exact match for the string
used in the installation command line invocation
or the uninstall will not be successfully
invoked.
The double quotes around the key, value, and SNMP parameters are required.
The recommended value for key is name of calling application. The
recommended value for value is calling application's path.
Sample command line for uninstall invocation:
c:\program files\intel\foobar\apuninst.exe "foobar" "c:\program files\intel\foobar\foobar.exe"
ISSUES WHICH SHOULD BE ADDRESSED IF USING SILENT MODE INSTALL:
The Alert on LAN Proxy's SNMP shim install requires the Windows SNMP agent
be installed before the SNMP shim is installed. If the SNMP install does
not find the SNMP agent registry keys, the SNMP shim install silently
fails, and the rest of the proxy installation continues.
The calling application's install for e.g. LANDesk* Client Manager (LDCM)
install may want to explicitly ask the user if the SNMP shim needs to be installed.
The SNMP shim requires the Microsoft SNMP Agent to be installed (which is
not part of a standard installation). At install time if the Microsoft
SNMP Agent/Service is not present on the system it would be nice if the
calling application's install for e.g. LDCM install popped a dialog box
informing the user that in order for SNMP to be operational, the Microsoft SNMP
Agent needs to be installed.
As noted above, SNMP support on Microsoft Windows 95 requires downloading
the Microsoft Windows 95 Sockets 2 Update. This needs to be conveyed to
the user.
After setup is complete, the system should be reboot.
RUNNING THE ALERT PROXY SERVER/SNMP ALERTER ON MICROSOFT WINDOWS NT* 4.0 AND WINDOWS 2000
-----------------------------------------------------------------------------------------
To install the Microsoft SNMP agent:
o Open the Network Control Panel and select the "Services" property tab.
o If "SNMP Service" is not already installed, click the "Add..." button and
select the "SNMP Service" option. Follow the onscreen prompts to complete
installation of the SNMP Agent.
The SNMP Alert Proxy Server requires Service Pack 3 or later be applied to
the system. Please note if the Microsoft SNMP Agent is installed from the
original Windows NT 4.0 CDROM after Service Pack 3 is applied, Service Pack
3 must be reapplied to update several SNMP related libraries.
RUNNING THE ALERT PROXY SERVER/SNMP ALERTER ON MICROSOFT WINDOWS 95
-------------------------------------------------------------------
To install the Microsoft SNMP agent:
o Open the Network Control Panel and select the "Configuration" property tab.
o If "Microsoft SNMP Agent" is not already installed, click the "Add..."
button and select the "Service" option. When prompted for a
Manufacturer and Network Service, choose "Microsoft" and "Microsoft SNMP
Agent". If "Microsoft SNMP Agent" does not appear in the "Network
Services" pane, click "Have Disk..." and enter the path to the SNMP
Agent on the Windows 95 CDROM. The path is generally
[WINDOWS95]:\Admin\Nettools\Snmp
o Follow the onscreen prompts to complete installation of the SNMP Agent.
The Alert on LAN Alert Proxy requires newer versions of SNMP support files
than those found on Windows 95 retail version (SR1).
The following is recommended method to resolve this issue:
Install the Microsoft Windows 95 Sockets 2 Update. This is available from
the Microsoft website at:
http://www.microsoft.com/windows/downloads/contents/updates/w95sockets2/default.asp
The Alert on LAN Proxy requires newer versions of COM DLLs than those found
on Windows 95 retail version (SR1). These DLLs can be found on standard
Windows 95 OSR2.5 installations, however OSR2.5 is only readily available
to OEMs, not to end-customers.
The following is recommended method to resolve this issue:
Install the Microsoft DCOM95 version 1.2 patch for windows 95. This patch
can be downloaded from the Microsoft website at:
http://www.microsoft.com/com/dcom/dcom1_2/dcom1_2.asp
Note: Using any earlier versions of DCOM95 patch will cause Windows 95
(with Alert on LAN SNMP Alerter installed) to hang when it tries to
'Restart in MS-DOS mode'.
UPGRADE NOTES
-------------
Upgrading the Alert Proxy Server installed with LANDesk Client Manager
Version 3.31 and later versions to the Alert on LAN SNMP Alerter.
Prior to installation of the Alert on LAN SNMP Alerter package, all running
programs using the Alert Proxy Server (including LDCM and related services)
must be stopped. Once all programs have been stopped, older installations
of the Alert Proxy Server need to be removed.
SPECIAL UPGRADE NOTES FOR LDCM USERS
For LANDesk Client Manager running on Microsoft Windows NT
o Open the Services control panel, and stop the Intel LDCM Notification
Monitor service.
o Locate the executable apuninst.exe which usually can be found in
the C:\Program Files\Intel\LDCM directory.
o From the command line, or the Start->Run menu, execute:
[path to apuninst]\apuninst.exe "ldcm"
o Now locate and run setup.exe which shipped with the Alert on LAN SNMP
Alerter install and run the install.
o The install recommends a reboot. Upon reboot, the Intel LDCM
Notification Monitor will automatically restart.
For LANDesk Client Manager running on Windows 95 and Windows 98
o Find the program DMIStart.exe and rename it to DMIStart.bak.
o Reboot the machine. Upon the next reboot, Windows will display a dialog
indicating it could not start DMIStart. You can safely ignore this
message.
o Locate the executable apuninst.exe which usually can be found in
the C:\Program Files\Intel\LDCM directory.
o From the command line, or the Start->Run menu, execute:
[path to apuninst]\apuninst.exe "ldcm"
o Locate and run setup.exe which shipped with the Alert on LAN SNMP
Alerter and run the install.
o The install recommends a reboot. In this case decline immediately
rebooting the system. Instead, rename DMIStart.bak back to
DMIStart.exe. Then reboot your machine.
================================================================================
== SAMPLE ALERT ON LAN PROXY SHIM APPLICATION (AOLNAPP)
================================================================================
GENERAL DESCRIPTION
-------------------
The Proxy shim sample application has been developed to give an application
developer an example of a proxy shim.
The AOLNAPP application demonstrates the use of the Intel_AProxy COM class
and two of the interfaces implemented by that class, IAProxy and
IAOLClientControl.
INSTALLATION AND BUILD NOTES
----------------------------
The sample application should be copied from the Alert on LAN product CD to a
hard drive on the development machine. Some of the files used in the
development of the application, particularly the Class Wizard files, must be
writable for the application to build without warnings.
The sample application should be built using Microsoft Visual C++ 5.0 with
Service Pack 3 applied or later. The sample application has not been build or
tested with other environments.
USAGE NOTES
-----------
To use the sample application run the output file AOLNAPP.EXE. Select Proxy
from the menu, then Load. Fill in the TCP/IP port number such that it
matches the port the Alert on LAN Agents will be sending to.
To update the list of discovered Agent machines select the Proxy->Update menu
selection.
To get a list of the enabled client control functions right-click on the
desired Agent in the Agent Tree View. If the Agent machine support any
client control functions the functions will be shown in a pop-menu when the
right-click is done. Left-clicking on a control operation in the popup menu
will cause the a message requesting the operation be performed to be sent to
the Agent.
To close the AOLNAPP application select the Proxy->Exit menu selection.
================================================================================
== ALERT ON LAN CLIENT MANAGEMENT AGENT CONFIGURATION NOTES
================================================================================
The Alert on LAN Client Management Agent configures the Alert on LAN
hardware to detect events and notify remote applications of events.
You can use the provided sample console application to enable event
detection, specify network parameters, enable receive capabilities if the
hardware supports it, and configure various hardware timers.
NOTE: The Alert on LAN Agent does not support Regional IME settings. The Alert on LAN Agent runs as a service, and as such uses the 'system-wide' locale setting specified when the operating system was installed. The net effect is although other Windows applications may display strings in one locale, the Alert on LAN Agent possibly could enumerates event and function descriptions in another (the 'system locale').
SPECIAL NOTES REGARDING BASIC ALERT ON LAN SYSTEMS
--------------------------------------------------
After enabling or disabling 'Basic Alert on LAN' on 'Intel PRO/100+
with Alert on LAN' Adapters, you must reboot the system for the
changes to take effect.
AGENT ERROR, WARNING AND INFORMATIONAL CODES
--------------------------------------------
The agent reports configuration changes to parameters and configuration
errors under HKLM\SOFTWARE\Intel\Alert on LAN\Agent in the
'AgentInfo.ConfigHistory' registry value. The value is a list of semicolon
delimited property names and associated information codes. These
information codes can reveal possible causes of configuration failures.
101 'Specified packet is larger than hardware is capable.'
102 'Unknown or unsupported network protocol specified.'
103 'Unknown or unsupported hardware detected.'
104 'A hardware error was encountered during initialization.'
105 'The BIOS has disabled Alert on LAN functionality.'
106 'The configuration console has enabled Alert on LAN functionality.'
107 'Mismatch between protocol and hardware.'
108 'Agent truncated packet to fit into hardware.'
109 'Agent adjusted the retransmit count to nearest supported value.'
10A 'Agent adjusted the retransmit timer to nearest supported value.'
10B 'Hardware does not support alert acknowledge function.'
10C 'Hardware does not support raw UDP packets.'
10D 'Adjusted protocol to TCOv3.'
10E 'Adjusted SOS retry count to 255 because infinite
retries enabled but alert acknowledge was disabled.'
110 'The supplied raw UDP packet offsets point outside the bounds
of the given packet.'
111 'Global enable setting not a supported value.'
202 'No configuration found for detected system id.'
203 'Memory allocation failed.'
204 'An error was detected with configuration entry(ies) for this platform.'
205 'Unknown, unrecognized or missing hardware.'
301 'Attempt to access the hardware exclusively failed.'
302 'Encountered an error retrieving adapter configuration data
from configuration file.'
303 'INF0: Updated Global.AlertAck property.'
401 'Hardware interface device mutex handle is invalid'
402 'Hardware interface exclusive lock request timed out'
403 'Requested action failed because of missing device'
404 'An invalid parameter was specified when accessing the device'
405 'An NDIS OID query failed'
406 'An error was encountered opening a network adapter instance'
407 'An error was encountered closing a network adapter instance'
501 'A property could not be validated because a dependent property
could not be validated'
502 'An unsupported protocol has been specified'
503 'Could not validate property because of an error during initialization'
504 'Encountered a system error during validation'
505 'An invalid configuration has been specified'
601 'Could not spawn a window message loop thread'
602 'Encountered an error while accessing the device'
603 'Failed to create a window'
604 'Failed to gain exclusive access to the hardware'
700 'Call to WSAStartup() failed'
701 'Invalid proxy address specified'
702 'Failed to initialize the ICMP dynamic link library'
703 'Failed to ping resolved proxy address'
704 'Failed to find route to proxy address'
705 'Close of ICMP library handle failed'
706 'Failed to load INETMIB1 dynamic link library'
707 'Failed to initialize INETMIB1 dynamic link library'
708 'Failed on query to INETMIB1 dynamic link library'
709 'Detected change to network configuration settings'
70A 'Local MAC address validation pending'
70B 'Local IP address validation pending'
70C 'Updated the management server network address'
70D 'Updated the router MAC address'
70E 'Updated the local adapter MAC address'
70F 'Updated the local system name'
710 'Updated the local adapter IP address'
711 'Retrying resolution of management server address'
800 'Configuration cycles halted due to failed agent property'
801 'Configuration cycles halted due to maximum config cycle count exceeded'
802 'Error because configuration cycle currently in progress'
901 'Adjusted polling frequency up to minimum allowed'
902 'Attempted to enable an unsupported event'
903 'Failed to generate an indication message'
905 'Failed to retrieve System ID'
906 'Failed to allocate necessary memory'
907 'Event configuration problem in INI file'
908 'No configuration found for detected system ID'
909 'Found unsupported or unknown hardware'
A01 'Adjusted interval to minimum frequency'
A02 'Encountered error attempting to exclusively access the hardware'
A03 'Missing or damaged hardware encountered'
B01 'Failed to create a socket to listen for RMCP messages'
C00 'Gave up trying to resolve management server network address'
C01 'Gave up trying to resolve router MAC address'
C02 'Gave up trying to resolve local network address'
C03 'Gave up trying to resolve local MAC address'
C04 'Network protocol not specified'
C05 'Defaulting destination port to 162'
C06 'Created NULL network PDU'
================================================================================
== ALERT ON LAN CLIENT MANAGEMENT AGENT SETUP
================================================================================
RUNNING THE ALERT ON LAN AGENT ON MICROSOFT WINDOWS* 95
-------------------------------------------------------
The "Alert on LAN 2 Agent" requires newer versions of COM DLLs than those found
on Windows 95 retail version (SR1). One method to resolve this issue is to install the Microsoft DCOM95 version 1.2 patch for Windows 95. This patch is available for download from the Microsoft website at:
http://www.microsoft.com/com/dcom/dcom1_2/dcom1_2.asp
ALERT ON LAN CLIENT MANAGEMENT AGENT INSTALLATION
-------------------------------------------------
To install the Alert on LAN Client Management Agent, double-click on the
setup program found under 'agent\install'.
The setup program no longer supports installation of SMBus drivers.
SMBus drivers are required for proper functioning of the Alert on LAN
'Netalrt' driver. However, the system may have an pre-existing, installed
SMBus drivers, or it may be desirable to install custom SMBus drivers.
Install programs incorporating this agent install program must use a
standalone SMBus driver install program. This allows install programs the
maximum flexibility to incorporate updated or different SMBus drivers.
The SMBus drivers are required for all installations except the Basic
Alert on LAN configuration. The Basic Alert on LAN configuration
includes the Intel 810, 820 or 840 chipset in combination with an Intel
PRO/100+ LAN Adapter with SMBus support. Thus without the SMBus
driver, the Alert on LAN software will be limited to Basic Alert
on LAN configurations. And with the SMBus driver, the Alert on
LAN software will be able to detect and use all possible hardware
combinations.
The agent requires the Release 3.1.1 or later of the Intel PRO/100+ LAN
Adapter drivers.
After setup is complete, please reboot the system.
Uninstallation is handled via the Control Panel's Add/Remove Programs
utility.
ALERT ON LAN CLIENT MANAGEMENT AGENT INSTALLATION (SILENT MODE INSTALL)
-----------------------------------------------------------------------
Command line usage for installation:
setup "key" "value" -s
The silent-mode install does not install SMBus drivers required for
the Alert on LAN 'Netalrt' drivers to function. Install programs
incorporating this agent install program must use a standalone SMBus
driver install program. The command line parameter "smbus" is no longer
supported and is ignored on the command line. Pre-existing install
programs that incorporate this agent install should not be adversely
affected by the usage of the "smbus" parameter since it is ignored.
setup "key" "value" "smbus" -s
"key" A string which will be used to create a new
unique registry key.
"value" A string which will be used as the new registry
key's value.
-s This parameter forces silent mode.
The double quotes around the key, value, and SMBUS parameters are required.
Sample command line for install invocation:
setup "foobar" "c:\program files\intel\foobar\foobar.exe" -s
Sample command line for SMBUS driver install invocation:
setup "foobar" "c:\program files\intel\foobar\foobar.exe" "smbus" -s
Uninstall can be invoked silently using Apuninst.exe which is copied to the Alert on LAN install directory during installation. For best results, Apuninst.exe should be copied to another directory (outside of the Alert on LAN install directory) and invoked from that other directory. If left in the Alert on LAN install directory, Apuninst.exe makes a best-effort attempt to delete itself during the uninstall process, but due to system-specific timing issues, the executable and directories in which it resides may not be deleted following an uninstallation.
Command line usage for uninstallation:
apuninst "key" "value"
"key" A string which will be used to locate the
unique registry key used for installation.
This string must be an exact match for the
string used in the installation command
line invocation or the uninstall will not
be successfully invoked. The string is
case-sensitive.
"value" A string which will be used to verify as a
match for the unique registry key's value.
This string must be an exact match for the
string used in the installation command
line invocation or the uninstall will not
be successfully invoked.
The double quotes around the key, value, and SMBUS parameters are required.
Sample command line for uninstall invocation:
c:\program files\intel\foobar\apuninst.exe "foobar" "c:\program files\intel\foobar\foobar.exe"
UPGRADE NOTES
-------------
Prior to installation of the Agent install package, all running programs using
the Alert on LAN Agent must be stopped. Once all programs have been stopped,
older installations of the Agent need to be removed.
================================================================================
== ALERT ON LAN CLIENT CONFIGURATION CONSOLE
================================================================================
This program is used to configure the Agent on the client system. It consists
of three files: CONSOLE.EXE, CONSOLE.DLL, and CONSOLE.CHM; the bulk of
functioning code is in CONSOLE.DLL.
INSTALLING AND RUNNING THE CONSOLE
----------------------------------
Place all three files in the same directory and run the command:
CONSOLE.EXE
The Console requires version 4.70 (or later) of the COMMCTRL.DLL file. This
file can be obtained by installing Microsoft Internet Explorer version 3.0 or
greater.
CONSOLE HELP FILE
-----------------
The help file provided with the console is in Microsoft HTML Help format. While
this format has many features not found in the WinHelp format, it is newer and
not implemented consistently across all Win32 systems. You may experience
difficulty launching the file on computers that do not have Internet Explorer
5.0 installed.
BUILDING THE CONSOLE
--------------------
The Console is built using Microsoft Visual C++ 6.0 with ATL 3.0. The
HTML Help file is built using HTML Workshop 1.2; which is freely available at
the Microsoft web site.
================================================================================
== SAMPLE ALERT ON LAN AGENT CLIENT
================================================================================
The SmplAOLClientSim provides the Graphical User Interface to allow
users to configure the Alert On LAN 2 Agent. This Utility program
runs on the machines where the Alert On LAN 2 Agent software is
installed.
INSTALLATION REQUIREMENTS
-------------------------
The SmplAOLClientSim.exe should be installed in the same directory as
the other Agent Binaries (i.e. AOLAgt.exe, AOLAgtps.dll etc.).
This Program can run on the WinNT 4.0 (Server/Workstation) and Win9X
OSes.
USAGE
-----
The User can run this program from the Command prompt by simply
typing the executable name at the Command prompt.
C:\Program Files\Intel\Alert On LAN\Win95\Agent\SmplAOLClientSim.exe
Or the User can use the File explorer to start the program.
Once the SmplAOLClientSim is started, the user needs to select the
the "AOL Agent"-->"Initialize" menu option first. After successfully
selecting the "Initialize" menu, user needs to select the
"AOL Agent"-->"Display AOL Applet" menu option. This menu selection
will bring up the Tabbed dialog box. This Dialog box will contain the
Following property pages.
Client Information:
This Page displays the Static information about the Client machine.
For example: MAC Address, System ID, Unique ID and NetBIOS Name and
IP Address.
Proxy Information:
This Page allows users to configure the Event destination
information. For example: Proxy IP Address, Port Number , Retransmit
Count and Interval.
Configure Events:
This Page allows users to enable/disable the Supported events.
Subscribe Event:
This Page allows users to subscribe/unsubscribe the Enabled events.
Notifications:
The User can register for the Events by clicking on this page. This
page also allows users to clear an event if the "AutoClear Event"
feature is disabled.
Configure Client Control Functions:
This Page allows users to enable/disable the Supported Client Control
functions.
Client Control Functions:
This Page allows users to execute the Client Control function from
the list of Enabled functions.
Timers:
The User can enable/disable the Watchdog and Heartbeat timers.
Furthermore user can set the values for the both timers.
Note: If the Agent is running in the SafeMode, this Program
will display an error message when user selects the
"AOL Agent"-->"Display AOL Applet" menu option. The Error message
will also contain the list of properties, responsible for the
Safemode. The User needs to give valid values to these properties
to run the Agent normally.
================================================================================
== DOS AGENT CONFIG
================================================================================
The AOLConfig allows user to configure the Alert On LAN 2 Agent
with the help of command-line parameters. This Utility program
runs on the machines where the Alert On LAN 2 Agent software is
installed.
INSTALLATION REQUIREMENTS
-------------------------
The AOLConfig.exe should be installed in the same directory as
the other Agent Binaries (i.e. AOLAgt.exe, AOLAgtps.dll etc.).
The AOLConfig.exe can run on the Windows NT 4.0 (Server/Workstation)
and Windows 95 and Windows 98 OSes.
USAGE
-----
The User can run the AOLConfig.exe at the Command prompt.
e.g. C:\Program Files\Intel\Alert On LAN\Win95\Agent\AOLConfig.exe
The User can run the program without any parameters to look at the
usage and the list of available command-line parameters. The User
can provide any combination of the Command-line parameters from the
Following list.
/ProxyAddr= IP Address of the Proxy machine.
/Port= Port# on which the Proxy is listening.
/RetransPktCnt= Retransmit Packet Count.
/RetransInterval= Retransmit Interval.
/HeartbeatEnable= HeartbeatEnable flag set or clear(1/0).
/HeartbeatInterval= Heartbeat Interval.
/WatchdogEnable= WatchdogEnable flag set or clear(1/0).
/WatchdogInterval= Watchdog Interval.
/GlobalEnable= GlobalEnable flag set or clear(1/0).
/AutoClearEnable= AutoClearEnable flag set or clear(1/0).
/PollInterval= Event Polling Interval.
/SNMPPktInfoFilePath= Fullpath to the File containing SNMP Packet
information.
================================================================================
== AOLEDIT APPLICATION
================================================================================
GENERAL DESCRIPTION
-------------------
Aoledit application is a tool developed to help in adding platform/
system configuration information to the aolan.ini needed by both
AOL Proxy and agent.
USAGE AND NOTES
---------------
To use aoledit tool, run the output file aoledit.exe. Select File->Open
and give the location of the aolan.ini file. Select File->Open and select
Resource DLL from menu and give the location of the resource DLL. To get
the list of all system info currently in aolan.ini, select "System" on the
tree on the left and traverse the tree and its nodes. Same applies for
Default Maps, Event Descriptions, Function Descriptions and Language Map.
================================================================================
== ALERT ON LAN CLIENT MANAGEMENT DRIVERS
================================================================================
NETALRT DRIVER
--------------
The Platalrt and Netlart drivers will now support the prepending of custom binary data to the BIOS data This data will be prepended along with the BIOS data and returned when the driver is requested to read BIOS data.
This Binary data is read from the registry key:
for VXD's on Windows 95 and Windows 98
HKLM\SYSTEM\CurrentControlSet\Services\VxD\[Netalrt][Platalrt]\Parameters\SMBiosOverrides
for SYS files on Windows NT and Windows 2000
HKLM\SYSTEM\CurrentControlSet\Services\[Netalrt][Platalrt]\Parameters\SMBiosOverrides
The Netalrt driver supports the "Alert on LAN" and "Advanced Alert on LAN"
SMBus-based system management ASICs. This driver is used by the Alert on
LAN Client Management Agent to configure and control the management devices.
The driver requires an SMBus host bus adapter driver to function. The
Alert on LAN Client Management Agent install includes a version of
an SMBus driver which supports the PIIX4 and ICH SMBus controllers.
SPECIFYING PARAMETERS TO THE NETALRT DRIVER
Under Microsoft Windows* 95, configuration parameters to the Netalrt driver
appear under the following registry key:
HKLM\SYSTEM\CurrentControlSet\Services\VxD\Netalrt\Parameters
Under Microsoft Windows* NT, configuration parameters to the Netalrt driver
appear under the following registry key:
HKLM\SYSTEM\CurrentControlSet\Services\Netalrt\Parameters
The following values are used to configure the Netalrt driver:
SMBHi DWORD Highest SMBus address driver should attempt to use
SMBLo DWORD Starting SMBus address driver should begin device scan from.
SMBAddr DWORD Current SMBus address driver detected for 'Alert on LAN' device
DevType DWORD FFFFFFFF - no 'Alert on LAN' devices detected
00000000 - detected 'Alert on LAN 1' device
00000001 - detected 'Alert on LAN 2' device
KrnlWatchdog DWORD
00000000 - disable kernel-mode watchdog timer
00000001 - enable kernel-mode watchdog timer
AdapterName
STRING Specifies SMBus host bus adapter driver to
attach to. Used on Windows NT only
By varying the SMBLo and SMBHi parameters, it is possible to constrain the
netalrt driver to locate a particular device if multiple are present. For
example, if 'Alert on LAN' and 'Advanced Alert on LAN' devices are both present,
you can set SMBHi to 0x67 and SMBLo to 0x60 to find only the 'Alert on LAN 2'
device.
PLATALRT DRIVER
---------------
The Platalrt driver supports the "PRO/100 Management Adapter with Alert on LAN"
PCI-based system management ASICs. This driver is used by the Alert on
LAN Client Management Agent to configure and control the management devices.
SPECIFYING PARAMETERS TO THE PLATALRT DRIVER
Under Windows 95, configuration parameters to the PLATALRT driver appear under
the following registry key:
HKLM\SYSTEM\CurrentControlSet\Services\VxD\PLATALRT\Parameters
Under Windows NT, configuration parameters to the PLATALRT driver appear under
the following registry key:
HKLM\SYSTEM\CurrentControlSet\Services\PLATALRT\Parameters
The following values are used to configure the PLATALRT driver:
DevType DWORD
FFFFFFFF - no 'Alert on LAN' devices detected
00000002 - detected 'Basic Alert on LAN' device
KrnlWatchdog DWORD
00000000 - disable kernel-mode watchdog timer
00000001 - enable kernel-mode watchdog timer
TxEnable DWORD
00000001 - enable the Alertbus function of the management feature.
00000000 - disable the Alertbus function of the management feature.
================================================================================
== ALERT ON LAN V2.5 BIOS SDK
================================================================================
The Alert on LAN v2.5 SDK is based on the generic Alert on LAN BIOS model
described in the Alert on LAN 2 Software Developer's Manual. Each sample
implementation includes test procedures written in assembler which exercise
the target Alert on LAN platform hardware and provide reference code to
simulate BIOS functionality.
BASIC ALERT ON LAN (ICH) BIOS SAMPLE
------------------------------------
Reference source code is provided in the BIOS\ICH directory which helps to
create an ICH Alert on LAN-enabled BIOS. For a implementation details of the
source code, please refer to the Alert on LAN Software Developer's Manual.
The sample source code exists in the BIOS\ICH directory and will generate
the executable BIOS\ICH\ICHBIOS.EXE.
BASIC ALERT ON LAN (ICH2) BIOS SAMPLE
-------------------------------------
Reference source code is provided in the BIOS\ICH2 directory which helps to
create an ICH2 Alert on LAN-enabled BIOS. For a implementation details of the
source code, please refer to the Alert on LAN Software Developer's Manual.
The sample source code exists in the BIOS\ICH2 directory and will generate
the executable BIOS\ICH2\ICH2BIOS.EXE.
ALERT ON LAN 2 (ADVANCED ALERT ON LAN ASIC -- CAPE LOOKOUT) BIOS SAMPLE
-----------------------------------------------------------------------
Reference source code is provided in the BIOS\CL directory which helps to
create an Cape Lookout-enabled BIOS. For a implementation details of the
source code, please refer to the Alert on LAN Software Developer's Manual.
The sample source code exists in the BIOS\CL directory and will generate
the executable BIOS\CL\CLBIOS.EXE.
ALERT ON LAN 2 (82550 INTEGRATED ADVANCED ALERT ON LAN - GCL) BIOS SAMPLE
-------------------------------------------------------------------------
Reference source code is provided in the BIOS\CL directory which helps to
create an GCL-enabled BIOS. For a implementation details of the
source code, please refer to the Alert on LAN Software Developer's Manual.
The sample source code exists in the BIOS\GCL directory and will generate
the executable BIOS\GCL\GCLBIOS.EXE.
ALERT ON LAN 2 COMBINED ICH/CAPE LOOKOUT BIOS SAMPLE
----------------------------------------------------
Reference source code is provided in the BIOS\COMBINED directory which helps
to create a combined ICH/Cape Lookout-enabled BIOS. For a implementation
details of the source code, please refer to the Alert on LAN Software
Developer's Manual.
The sample source code exists in the BIOS\COMBINED directory and will
generate the executable BIOS\COMBINED\AOLBIOS.EXE.
_____
* Third-party trademarks are the property of their respective owners.
** "Alert on LAN" is a result of the Intel-IBM Advanced Manageability
Alliance and a trademark of IBM.
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.