---------------------------------------------------------------------------- Tivoli Management Environment (TME 10) Lightweight Client Framework (LCF)* for Novell NetWare 4.1x* --------------------------------------------------------------- TME 10 LCF is a lightweight client framework which allows limited invocation of methods within the Tivoli Framework. LCF consists of the LCFd NLM (a long running Unix-like daemon) and the LCF software development kit (a collection of libraries and headers for development of LCF methods). LCF DAEMON (LCFd): 1. AUTO LAUNCHING LCFd has been installed on your NetWare server. To complete the install, you must call the lcf.ncf file from your autoexec.ncf file. Doing this will allow LCFd to auto launch each time the server is re-started. You will find the lcf.ncf file in the SYSTEM directory on the server. To launch LCFd, run the lcf.ncf file. The lcf.ncf file loads the lcfutils.nlm library, then loads lcfd.nlm. NOTE: When lcfutils.nlm launches (netware 4.x only), the default context and tree is stored for use by the LCF system. To change this, edit the lcf.sys file in the SYSTEM directory and modify the NWDS_CONTEXT and NWDS_TREE entries to reflect your change. Additionally, you can reset these values by manually removing the lcf.sys file from the SYSTEM directory, then re-running the SETUP program. LCFd will launch with the the default configuration. To launch LCFd with a custom configuration, you may use command line switches or a launch configuration file. See the section entitled 'CUSTOMIZING LCFd' for more details. The first time LCFd launches it must perform an initial login. By default, LCFd transmits UDP broadcast packets on port 9494 in order to locate a gateway on the current subnet. If you configure your gateway on the current subnet to utilize a port other than 9494, use the -p option when launching LCFd for the first time. (i.e. If your gateway port is 1344, use the syntax; 'lcfd -p 1344') Once an initial login occurs, it is not necessary to use the -p option. LCFd on subsequent logins will direct connect to the gateway into which it initially logged. For initial deployments, it is recommended that a single gateway be deployed per subnet. There is no limit to the number of LCFd's that can subscribe (or belong) to that gateway. After analyzing network loading, you may decide to add additional gateways to those subnets which have a dense concentration of LCFd's. Important: If multiple gateways exist on the same subnet, each gateway must utilize a unique port on that subnet. Logging for the current Netware version of LCFd outputs to lcfd.log unless overridden on the command line or config file. Log messages from LCFd are displayed on the LCFd screen unless overridden on the command line or config file. Log messages from methods are not displayed on the LCFd screen. 2. CUSTOMIZING LCFd LCFd may be customized by launching with command line switches. The settings established by these switches is stored in the cfgout.dat file for re-loading on subsequent launches of LCFd. To restore settings to the programatic defaults, remove the cfgout.dat file before launching LCFd. If no switches are utilized, LCFd uses the following programatic defaults: logfile = lcfd.log located in root of SYS volume config output file = cfgout.dat located in root of SYS volume config input file = searches for lcfd.cfg in root of SYS volume gateway and lcfd port = uses the encoded port in the lcf.dat file lcfd port = uses the gateway port working directory = root of SYS volume The following command line switches are available for LCFd: -l log file -d set debug (logging) verbosity -c config file -p gateway and lcfd port -P lcfd port -s start as console app on Windows NT -i install lcfd as a service (Windows NT) -r remove lcfd service (Windows NT) -C working directory -D supports these keys and default values): lcfd_port=9495 gateway_port=9494 bcast_addr=255 log_threshold=2 start_timeout=10 run_timeout=20 logfile=lcfd.log config_path=lcfd.cfg run_dir=. cache_loc=cache debug_flags=0 log_size=1024000 log_queue_size=5120 lcs.machine_name=mmcdaniels lcs.machine_unique_id=<UNDEFINED MACHINE ID> lcs.crypt_mode=0 lcs.crypt_key= lcs.interp=w32-ix86 lcs.login_interfaces= lcs.gateway_address= Additionally, LCFd can be customized by setting keys in a configuration file which can be read at launching of LCFd. The following keys may be set in the configuration file: lcfd_port gateway_port bcast_addr log_threshold start_timeout run_timeout logfile config_path run_dir cache_loc debug_flags log_queue_size log_size lcs.machine_name lcs.machine_unique_id lcs.crypt_mode lcs.crypt_key lcs.interp lcs.login_interfaces lcs.gateway_address For more detailed information on configuration options, command line options, and the operation of LCFd on NetWare, consult the 'Lightweight Client Framework User's Guide." ---------------------------------------------------------------------------- * TME 10 and LCF are trademarks of Tivoli Systems, an IBM Company. NetWare is a trademark of Novell Corp. ----------------------------------------------------------------------------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.