Install
- 格式:doc
- 大小:18.50 KB
- 文档页数:3
npm install用法npm install是Node.js中的一个命令,用于安装和管理Node.js模块。
它可以完成以下几个任务:①安装模块:使用npm install <package> 命令可以安装指定的模块。
例如,如果要安装lodash模块,可以使用npm install lodash 命令。
使用npm install <package>@<version> 命令可以安装指定版本的模块,将<version> 替换为具体的版本号。
②安装模块并保存到package.json 文件中:使用npm install <package> --save 命令可以将安装的模块信息保存到package.json 文件中,方便项目管理。
③升级模块:使用npm update <package> 命令可以升级指定的模块。
例如,如果要升级lodash模块,可以使用npm update lodash 命令。
④卸载模块:使用npm uninstall <package> 命令可以卸载指定的模块。
例如,如果要卸载lodash模块,可以使用npm uninstall lodash 命令。
⑤安装开发依赖模块:使用npm install <package> --save-dev 命令可以将安装的模块信息保存到package.json 文件的devDependencies 中,用于开发环境中的依赖管理。
例如,如果要安装mocha模块,可以使用npm install mocha --save-dev 命令。
⑥全局安装模块:使用npm install -g <package> 命令可以全局安装指定的模块。
例如,如果要全局安装nodemon模块,可以使用npm install -g nodemon 命令。
adb常用的几个命令 adbinstall ADB(Android Debug Bridge)是Android开发工具包(SDK)中的一个命令行工具,用于与Android设备进行通信和调试。
ADB常用的几个命令如下:1. adb devices:用于列出当前连接的Android设备列表。
当设备连接到计算机时,可以使用该命令来验证设备是否成功连接。
2. adb shell:用于在设备的shell环境下执行命令。
通过该命令可以获取设备的root权限,以便执行一些需要root权限的操作。
3. adb install:用于将应用程序安装到连接的Android设备上。
命令格式为“adb install <path_to_apk_file>”,其中<path_to_apk_file>为待安装的APK文件的路径。
4. adb uninstall:用于从连接的Android设备中卸载应用程序。
命令格式为“adb uninstall <package_name>”,其中<package_name>为待卸载应用程序的包名。
5. adb push:用于将文件从计算机复制到连接的Android设备中。
命令格式为“adb push <local_file> <device_path>”,其中<local_file>为计算机上的文件路径,<device_path>为目标设备中的路径。
6. adb pull:用于将文件从连接的Android设备中复制到计算机上。
命令格式为“adb pull <device_file> <local_path>”,其中<device_file>为设备上的文件路径,<local_path>为目标计算机上的路径。
7. adb logcat:用于查看设备的日志信息。
npm install 常见参数摘要:1.npm install 命令简介2.常见参数及其作用a.-g:全局安装b.-o:安装最新版c.--save:将依赖项保存到package.json 文件d.--save-dev:将依赖项保存到package.json 文件的devDependencies 部分e.--no-save:不将依赖项保存到package.json 文件f.--save-exact:将依赖项精确地保存到package.json 文件g.--dry-run:模拟安装过程,不实际安装任何内容h.--production:仅在生产环境中安装依赖项i.--development:仅在开发环境中安装依赖项j.--script-mode:允许在package.json 文件中使用脚本安装k.--ignore-scripts:忽略package.json 文件中的脚本安装正文:pm install 是Node.js 包管理工具npm 的常用命令之一,用于安装Node.js 项目所需的依赖项。
在实际使用过程中,我们可以通过添加不同的参数来实现不同的功能。
下面我们将详细介绍npm install 常见参数及其作用。
1.npm install 命令简介pm install 命令用于安装项目所需的依赖项。
它会读取package.json 文件中的依赖项信息,然后从npm registry 下载相应的软件包并安装到项目中。
此外,npm install 还可以接收一系列参数,以实现更丰富的功能。
2.常见参数及其作用以下是一些常见的npm install 参数及其作用:a.-g:全局安装使用-g 参数可以将依赖项安装到全局作用域,而非项目内部。
这使得该依赖项可以在任何Node.js 项目中使用,而不仅仅是当前项目。
例如:`npm install -g express`。
b.-o:安装最新版使用-o 参数可以安装依赖项的最新版本。
"make install"是一条在Unix和Linux系统中常用的命令,主要用于安装已经编译好的程序。
具体来说,这条命令将复制编译生成的文件树中的文件到指定的位置。
在使用"make install"之前,通常需要先进行编译,也就是执行"make"命令。
如果编译过程中出现错误,需要记下错误代码并尝试解决,这可能包括向开发者提交bug报告,或者检查系统是否缺少某些依赖库。
一旦编译成功,"make install"命令就可以将编译好的程序安装到系统中。
请注意,这个过程通常需要具有root权限,因为安装过程可能涉及到向系统写入文件。
此外,还有一些与"make install"相关的命令,如"make uninstall",用于卸载已经安装的程序;"make clean",用于删除由"make"命令产生的文件;以及"make distclean",用于删除由"./configure"产生的文件等。
DC21X4 NDIS 5.0 miniport driver for Intel Windows 2000 [tm]Version v5.0526-Dec-19991. Copyright Notice:First Edition, April 1994Updated, December 1994Updated, February 1996Updated, April 1996**************************************************************************** **** I N T E L P R O P R I E T A R Y **** **** COPYRIGHT (c) 1998 BY INTEL CORPORATION. ALL RIGHTS **** RESERVED. NO PART OF THIS PROGRAM OR PUBLICATION MAY **** BE REPRODUCED, TRANSMITTED, TRANSCRIBED, STORED IN A **** RETRIEVAL SYSTEM, OR TRANSLATED INTO ANY LANGUAGE OR COMPUTER **** LANGUAGE IN ANY FORM OR BY ANY MEANS, ELECTRONIC, MECHANICAL, **** MAGNETIC, OPTICAL, CHEMICAL, MANUAL, OR OTHERWISE, WITHOUT **** THE PRIOR WRITTEN PERMISSION OF : **** **** INTEL CORPORATION **** **** 2200 MISSION COLLEGE BLVD **** **** SANTA CLARA, CALIFORNIA 95052-8119 **** **************************************************************************** Copyright (c) 1998 Intel CorporationDo not redistribute the driver files.Windows, Windows NT, Windows 2000, windows95 and Windows98 are trademarks of Microsoft Corporation.Microsoft, MS, MS-DOS are registered trademarks ofMicrosoft Corporation.All other trademarks and registered trademarks are theproperty of their respective holders.2. Overview:The driver is currently supported for motherboards and optionboards based on the Intel 2104x/2114x 10/100 mbpsEthernet Controller.3. Requirements:A. Hardware Requirements:Intel 2104x/2114x 10/100 mbps Ethernet ControllerB. Software Revision Requirements:Windows NT Version 4.0 or Windows 20004. Files and directories:---------------------------------------------------------------------INSTALL.DOC This file.--------------------------------------------------- OEMSETUP.INF The driver's setup file for Windows NT 3.51/4.0orNET21X4.INF The driver's setup file for Windows 2000--------------------------------------------------- DC21X4.SYS The driver's executable--------------------------------------------------- DC21X4.DBG The driver's symbol table--------------------------------------------------- !DEC4250.CFG The configuration file used by the DE425 Ethernetboard EISA configuration utility (ECU)---------------------------------------------------------------------5. Installing the Hardware Boards:A. Installing the Intel's 2104x/2114x Evaluation Boards:Refer to the Intel 2104x/2114x Evaluation BoardUser's Guide.B. Installing the Digital's 21040 EISA Adapter Card (DE425):1. Plug the board in an EISA slot2. Run the EISA System Configuration Utility(ECU)3. In the EISA System Configuration,select the [Configure computer] option4. Insert a floppy with the DE425 EISA configurationfile !DEC4250.CFG5. In the main menu, select the [Save and exit] option to complete the initialization.The options for the DE425 in the !DEC4250.CFG file are:1. For interrupt:o Edge-Triggered Interrupt (default)o Level-Triggered Interrupt (no sharing)o Level-Triggered Interrupt (sharing)2. Supported interrupt numbers are:o 5o 9o 10o 113. For cable types:o AutoSense/AutoDetection (default) o 10BaseT (TP)o 10BaseT (TP) - Full Duplexo 10BaseT (TP) - No Link Testo 10Base2 (BNC)o 10Base5 (AUI)6. Installing the DC21X4 Driver on Windows NT/Windows 2000:1. From the Windows NT/Windows 2000 Main Menu, select the Control Panel icon.2. From the Control Panel menu select the Network icon.If a dialog box asks you "Do you want to install NTNetwork?" select YES and Continue. Then placethe Windows NT/Windows 2000 CDROM in the CD-ROM reader.Select the drive that matches the configuration of your systemand complete the install.3. You will see several messages. To add a network adapter, select Yesand then Continue4. For each additional message, select continue.5. From the Add Network Adapter dialog box, scroll through the menu toselect Other.6. When the Insert Diskettes menu prompts you for a disk, insert theDC21X4 driver installation diskette for Windows NT/Windows 2000 into drive A.Then select OK.7. Select your option[Intel 21040 based Ethernet Controller][Intel 21041 based Ethernet Controller][Intel 21140 based 10/100 mbps Ethernet Controller][Intel 21142 based 10/100 mbps Ethernet Controller][Intel 21143 based 10/100 mbps Ethernet Controller][Intel EB40 21040 based Evaluation Board][Intel EB41 21041 based Evaluation Board][Intel EB140 21140 based Evaluation Board][Intel EB142 21142 based Evaluation Board][Intel EB143 21143 based Evaluation Board]from the Select OEM Option box, then select OK.8. Modify the default distribution path in the Windows NT/Windows 2000Setup box to point to the correct drive and path, then clickon [Continue]9. For PCI options, a Dialog box pops up to select the:ConnectionType:------------------------------------------------------------------------ Intel 21040 based Ethernet Controller-------------------------------------------------------------------------o AutoDetect In AutoDetect mode the driverchecks first the Twisted Pair port. If the Link Test fails the driverchecks the BNC port. If no carrier is detected the driver switches to the AUI port.o 10BaseT (TP)o 10BaseT (TP) Full Duplex To connect to Full Duplex hubso 10Base2 (BNC) BNC connectoro 10Base5 (AUI) 15_pin connector------------------------------------------------------------------------ Intel 21041 based Ethernet Controller-------------------------------------------------------------------------o AutoSense Senses dynamically the media portssupported by the adapter. The precedenceis TP,BNC and AUI.o 10BaseT (TP)o 10BaseT (TP) Full Duplex To connect to Full Duplex hubso 10Base2 (BNC) BNC connectoro 10Base5 (AUI) 15_pin connector------------------------------------------------------------------------ Intel 2114x based 10/100 mbps Ethernet Controller-------------------------------------------------------------------------o AutoSense Senses dynamically the media portso 10BaseT (TP) To connect 10BaseT Ethernet hubso 10BaseT (TP) Full Duplex To connect 10BaseT Full Duplex hubso 10Base2 (BNC) BNC connectoro 10Base5 (AUI) 15_pin connectoro 100BaseTx (TP 100) To connect 100BaseTx Ethernet hubso 100BaseTx (TP 100) FDx To connect 100BaseTx Full Duplex hubso 100BaseT4 To connect 100BaseT4 Ethernet hubso 100BaseFx To connect 100BaseFx Ethernet hubs10. Upon completion, the selected adapter is added to theInstalled Adapter Cards list of the Network Setting box(the number prefixing the adapter is the adapter number).11. Click on [Close] to complete the Network Settinginitialization.12. If needed, modify the values in the registry (see section 7 below).13. Shutdown and reboot the system.7. ParametersTo overwrite the initial values set by the EISA ConfigurationUtility (ECU) or overwrite the driver's default values,add or edit the following values in the RegistryDC21X4<adapter_number> Parameters subtree:CacheLineSize = REG_DWORD { 32 | 64 | 128 }32 bytes (default)64 bytes128 bytesExtraReceiveBuffers = REG_DWORD {value} (default: 16)Number of buffers allocated by thedriver in the Receive look_aside list.ExtraReceivePackets = REG_DWORD {value} (default: 100)Number of packets preallocated by thedriver.InterruptMitigation = REG_DWORD {0 | 1} (21140,21143/2)0 Disabled (default)1 EnabledEnable/disable the Interrupt Mitigationalgorithm.InterruptThreshold = REG_DWORD {value} (default: 500)Maximum number of interrupt/second allowed beforethe Receive and Transmit interrupts get masked.Meaningfull only when InterruptMitigation is enabled. FrameThreshold = REG_DWORD {value} (default: 400)Minimum number of processed frame/second allowedbefore the Receive and Transmit interrupts getunmasked.Meaningfull only when InterruptMitigation is enabled. EXT_MRM = REG_DWORD { 0 | 1 } (21142,2143 only)0 Disabled1 Enabled (default)Enable/disable PCI Memory Read Multiple command.MRM should be enabled when the DC21X4 is connectedto the TI1130 PCI/CardBus bridge.EXT_MRL = REG_DWORD { 0 | 1 } (21142,2143 only)0 Disabled1 Enabled (default)Enable/disable PCI Memory Read Line command.EXT_MWI = REG_DWORD { 0 | 1 } (21142,2143 only)0 Disabled1 Enabled (default)Enable/disable PCI Memory Write and Invalidate command.Due to incompatibility problems with certain PCI host bridgesand PCI-to-PCI bridges, the driver currently does not enablethe Memory Write Invalidate (MWI) and Memory Read Line (MRL) commands simultaneously. The driver will only enable one of the two commands; by default, MRL will be enabled.NwayProtocol = REG_DWORD { 0 | 1 } (21041 and21142 Rev1.0,1.1 only)0 Disabled1 Enabled (default)Enable/disable the 10BT/10BT_FD Autonegotiationmedium in Autosense mode.ReceiveBuffers = REG_DWORD {8..64} (default: 32)Number of buffers allocated by thedriver in the Receive ring.SoftwareCRC = REG_DWORD { 0 | 1 } (DC21040 rev 1.x, 2.0 & 2.2 only)0 The CRC is generated by the adapter1 (default) The CRC is generated by software fortransmit packets bigger than the transmit threshold.NOTE: This option affects performances and could bedisabled if the adapter does not report transmit underruns in its statistic countersUnderrunRetry = REG_DWORD number_of_retries (default=2)Maximun number of retransmission attempts ofan underrun packet.UnderrunThreshold = REG_DWORD number_of_underruns (default=10) (21140 and 21143/2 only)Maximun number of underrun occurences before thecontroller switches to the next threshold value.The following values allow to overwrite the DC21X4 default setting.Refer to the Intel 2104x/2114x 10/100 mbps Ethernet ControllerEngineering specifications for detailed description:BackPressure = REG_DWORD { 0 | 1 } (not DC21040 rev1)CSR6<BP> 0 Disabled (default)1 EnabledBurstLength = REG_DWORD { 0 | 1 | 2 | 4 | 8 | 16 | 32 }CSR0<PBL> 0 unlimited (default) - (not 21040, 21041 & 21140 rev1)1 doubleword2 doublewords4 doublewords8 doublewords16 doublewords (default for 21040, 21041 & 21140 rev1)32 doublewords (not 21040 & 21041)CaptureEffect = REG_DWORD { 0 | 1 } (not 21040 rev1)CSR6<CA> 0 Disabled (Default)1 EnabledFifoArbitration = REG_DWORD { 0 | 1 }CSR0<BAR> 0 Rcv/Txm Arbitration (default)1 Round_RobinSnoozeMode = REG_DWORD { 0 | 1 }CFDA<SM> 0 Disabled (default)1 EnabledStopBackoffCounter = REG_DWORD { 0 | 1 } (not 21040 rev1)CSR6<SB> 0 Disabled (Default)1 EnabledStoreAndForward = REG_DWORD { 0 | 1 } (21140, 21143/2 only)Select the StoreAndForward mode if highPCI latencies causes 100Mbps Transmit UnderrunsCSR6<SF> 1 Enabled0 Disabled (default)TransmitThreshold = REG_DWORD { 72 | 96 | 128 | 160 }Transmit Threshold values for 10Mbps media.CSR6<TTM,TR> 72 bytes96 bytes (default)128 bytes160 bytesTransmitThreshold100 = REG_DWORD { 128 | 256 | 512 | 1024 } (21140, 21143/2 only)Transmit Threshold values for 100Mbps media.Meaningless when StoreAndForward is setCSR6<TTM,TR> 128 bytes256 bytes512 bytes (default)1024 bytesProcessTransmitFirst = {Enabled | Disabled}Causes the interrupt handler to process the transmit queue first.0 Disabled (default)1 EnabledThese Registry values can be edited interactively through the Registry editor (winnt\system32\regedt32.exe) or by invoking the regini command Edit an DC21X4.ini file as described below, then invoke the command:regini DC21X4.iniDC21X4.ini format:\Registry\MachineSystemCurrentControlSetServicesDC21x4{adapter_number}Parameters{valuename} = {type}{value}8. Driver Revision numberTo retrieve the driver revision number eitherselect the file DC21X4.SYS and open the File Properties appletorquery the Registry:HKEY_LOCAL_MACHINE\Software\Intel\DC21X4\CurrentVersionMajorVersionMinorVersion9. Error messagesThe error messages are logged in the Entry Log and can be seen using the Entry Log Viewer (in WNT's Administration Tools group).Each error message has a standard Ndis error code and an driver's additional code.The additional codes are:DC21X4_ERRMSG_REGISTRY 0x01DC21X4_ERRMSG_ALLOC_MEMORY 0x02DC21X4_ERRMSG_SROM 0x03DC21X4_ERRMSG_MEDIA 0x04DC21X4_ERRMSG_LOAD_CAM 0x05DC21X4_ERRMSG_SYSTEM_ERROR 0x06DC21X4_ERRMSG_TXM_JABBER_TIMEOUT 0x079.1 Driver initialization errors:o NDIS_ERROR_CODE_UNSUPPORTED_CONFIGURATIONDC21X4_ERRMSG_REGISTRYThe AdapterType Registry's key is missing or its value isunsupported by the adapter boardo NDIS_ERROR_CODE_ADAPTER_NOT_FOUNDNo board matching the AdapterCFID Registry's key value was foundplugged into the PCI bus or in the slot specified in the Registryo NDIS_ERROR_CODE_OUT_OF_RESOURCESDC21X4_ERRMSG_ALLOC_MEMORYNot enough memory to allocate space for the Adapter data blocko NDIS_ERROR_CODE_INVALID_VALUE_FROM_ADAPTERDC21X4_ERRMSG_SROMInvalid data read from the adapter's serial ROMo NDIS_ERROR_CODE_NETWORK_ADDRESSNo readable burnt_in or software configured station addresso NDIS_ERROR_CODE_UNSUPPORTED_CONFIGURATIONDC21X4_ERRMSG_MEDIAThe selected media port is not supported by the board. o NDIS_ERROR_CODE_INTERRUPT_CONNECTInterrupt initialization failedo NDIS_ERROR_CODE_TIMEOUTDC21X4_ERRMSG_LOAD_CAMDC21X4 CAM initialization failed9.2 Driver run time errors:o NDIS_ERROR_CODE_HARDWARE_FAILUREDC21X4_ERRMSG_SYSTEM_ERRORSystem_Error interrupt (bus parity error)o NDIS_ERROR_CODE_HARDWARE_FAILUREDC21X4_ERRMSG_TXM_JABBER_TIMEOUTTransmit Jabber timer expired10. Important NoticeAs of May 17, 1998, Digital Equipment Corporation's StrongARM,PCI Bridge, and Networking component businesses, along with the chipfabrication facility in Hudson, Massachusetts, were acquired byIntel Corporation and transferred to Intel Massachusetts, Inc.As a result of this transaction, certain references to web sites,telephone numbers, and fax numbers have changed in the documentation.This information will be updated in the next version of this manual.Copies of documents that have an ordering number and are referencedin this document, or other Intel literature may be obtained by calling1-800-332-2717 or by visiting Intel's website for developers at:The Intel Massachusetts Customer Technology Center continues toservice Network Product technical inquiries. Please use thefollowing information lines for support:For documentation and general information:Intel Massachusetts Information LineUnited States: 1-800-332-2717Outside United States: +1-303-675-2148Electronic mail address: techdoc@For technical support:Intel Massachusetts Customer Technology CenterPhone (U.S. and international): 1-978-568-7474Fax: 1-978-568-6698Electronic mail address: techsup@Upgrading DriversSee the components page available on the Intel World Wide WebInternet site at:/design/network/new21/download/dsc-software-nc.htm。
pip install的用法pip是Python的包管理器,用于安装和管理Python软件包。
它是Python 官方推荐的包管理工具,能够帮助开发者快速、方便地获取和安装第三方库。
本文将介绍pip install的用法,并且详细说明每个步骤的操作过程。
一、安装pip要使用pip,首先需要安装它。
根据操作系统的不同,可以选择不同的安装方式。
下面分别介绍Windows、Linux和Mac OS中安装pip的方法。
1. 在Windows上安装pip在Windows上安装pip的方法有两种:一是使用Python自带的安装程序,二是使用官方提供的get-pip.py脚本文件。
a. 使用Python自带的安装程序Python 2.7.9及之后的版本以及Python 3.4及之后的版本已经内置了pip,因此只需确保Python已正确安装即可。
b. 使用get-pip.py脚本文件首先,需要下载get-pip.py脚本文件,可以从python get-pip.py2. 在Linux上安装pip在Linux系统中,可以通过包管理器来安装pip。
下面分别介绍在Debian 和Red Hat系列的Linux发行版上安装pip的方法。
a. 在Debian系列中安装pip使用以下命令安装pip:sudo apt-get install python-pipb. 在Red Hat系列中安装pip使用以下命令安装pip:sudo yum install python-pip3. 在Mac OS上安装pip在Mac OS中安装pip与在Linux系统中安装pip类似。
首先,需要打开终端,然后使用以下命令安装pip:sudo easy_install pip二、使用pip安装完pip后,就可以开始使用它来安装第三方库了。
下面将详细介绍pip install的用法,并分步骤进行操作。
1. 查找包在安装包之前,可以使用pip search命令来查找特定的包。
--azure云背景没有自动发送email短信报警功能azure云上的linux vm没有自动发送email短信报警服务,所以准备用开源的zabbix来实现,原来用nagios,但是听说zabbix有自动识别的功能,不需要nagios配置那么多东西,zabbix更加人性化,所以准备用用zabbix。
1,准备安装环境参考安装文档地址:https:///documentation/3.0/manual/installation/install_from_packages#red_ha t_enterprise_linuxcentos清空原来的缓存:安装新的zabbix yum源,由于版本更新,这个连接地址可能会失效,需要自己去zabbix官安装文档地址:https:///documentation/3.0/下载地址:/zabbix/3.0/rhel/6/x86_64/2,Yum安装开始yum安装zabbix-server:PS:犹豫rhel系统(centos系统不存在问题)缺少php-bcmath和php-mbstring这两个包,会导致Web页面的安装提示缺少组件,所以可以在centos源中下载这2个包安装即可。
3,准备mysql数据库安装mysql数据库:/mchdba/article/details/51138063创建zabbix的数据库:PS:字符集要设置为utf8mb4,防止界面切换到中文的时候乱码。
导入create.sql.gz文件,建立zabbix-server的数据库(ps,以前的版本可能叫啥schema.sql 之类的):4,开始配置数据库5,启动zabbix进程服务6,安装apache7,关闭selinux安装web源:8,Zabbix管理界面打开失败。
如1.png所示:D:\study\zabbix\1.png问题来了,rpm包安装方式中的zabbix web打开的工程在哪里?是如何和httpd配合一起工作的?官方rpm安装文档里面没有相应的记录,或者在别的地方有但是我没有找到它吧,不过这个rpm的方式安装,只能暂时搁浅放弃了,等待下次有空继续研究下其中流程和原理。
Conductor NT 1.0 Generic Demo (1997 October 8)The Generic Demo consists of console configuration files (GenDem3a, GenDem3b, GenDem3c), an MFP blockware file (13330.cfg), archived data files (GenDemA1, GenDemA2, GenDemA3, GenDemA4, GenDemA5, and GenDemHB), a simulation script (gendemo.txt), a simulation description (Simulate.doc), a wallpaper bitmap (symbg_dd.bmp), and display bitmaps (*.bmp).The MFP blockware can be loaded into an MFP02, MFP03, MFP04, or MFP05 but is too large to fit into an MFP01. The MFP must be initialized for Superloop support, before the blockware is loaded. The MFP address is Loop 1, PCU Node 33, Module 30.The console configuration contains graphics, symbols, spreadsheets, summary displays, trend displays, trend list, area names, mini-alarm format, a tag database, event bits, operator accounts, and several other configuration items. Click on raised areas (touchpoints) in graphics, button, and sight level indicators in vessels to activate popup controls.The demo is usable but omits many of the capabilities of Conductor NT. Current deficiencies are: 1.The tag database is only partially configured. Most fields, in tag definitions, have default valuesincluding blank alarm comments. Many tags lack tag descriptions;2.The displays look good, but apparently do not show realistic process systems;3.The current simulation script, gendemo.txt, only simulates tags found on the Chemicalsdisplays, a subset of the full Generic Demo. You can modify this simulation script following the procedure described in the Conductor NT notes supplied on the Conductor NT installation CD (see also, Simulate.doc). INFI 90 hardware (ICI, PCU, and MFP) is required to run the full demo using blockware;4.There is no tour guide describing the contents of the Generic Demo.There are a few custom process displays for each application area:1.Six for Pulp and Paper (using tags whose names begin with "GP-")2.Five for Mining and Metals (using tags whose names begin with "GM-")3.Four for Chemicals (using tags whose names begin with "GC-")4.Four for Waste Water (using tags whose names begin with "GW-", the largest tag group)5.Four for Power Utilities (using tags whose names begin with "GU-")6.Two for Refineries (using tags whose names begin with "GR-")Generic Demo Assumptions:1.The host computer's name is "CONDUCTOR-NT".2.The Conductor NT console is identified as: Con32.3.The Conductor NT licensed features include "con90", "i90SRVR", "hdb", and "log".4.Microsoft Excel 7.0 (Excel 95) or Excel 97 is on the same hard drive partition as the ConductorNT spreadsheets.5.@aGlance client software (version 3.0 or version 3.1) has been installed (required only for the@aGlanceSample95, @aGlanceSample97, and Real_Trend97 spreadsheets).6.Update 1 for Conductor NT 1.0 has been installed;7.Service Pack 3 for Windows NT 4.0 has been installed.If assumption (1) was invalid (i.e. the host computer's name is not "Conductor-NT"):a)Run the program "DbUtils".b)Use "Set Host Name…" from the Tools menu.c)Open the file "\Program Files\INFI-90 Server\database\TAGDATA.mdb".d)Respond "OK" to accept the change of host name.If assumption (2) was invalid (i.e. the console node number is not 32):When restoring the console configuration file GenDem3a, specify that the node name "Con32' be translated to your console's node name (for example, "Con8"). Click on the question mark Helpsymbol if you require instructions. If you omit this step and there is no console named "Con32", the historical database (trending) and printer assignments will be invalid.To load the current version of Generic Demo:1.Copy the self-extracting WinZip files: Bitmaps1.EXE, Bitmaps2.Exe, Bitmaps3.Exe, andDocument.EXE to the hard drive partition that contains your Conductor NT graphic files.2.Double-click on each of the above self-extracting WinZip files, in turn, to extract the contents.3.Restore the console configuration files, GenDem3a, GenDem3b, and GenDem3c, as describedin the Conductor NT Operation Instruction Manual (see Conductor NT Utilities: RestoreUtility);4.Restore the archived trend data files, GenDemA1, GenDemA2, GenDemA3, GenDemA4,GenDemA5, and GenDemHB, as described in the Conductor NT Operation Instruction (see Conductor NT Utilities: Restore Archival Data);5.Follow the instructions given in \GenericDemo\Simulate.doc or use INFI 90 hardware asdescribed below.To run the Generic Demo in hardware mode (i.e. with an Infinet Computer Interface):1.Click on the name button of the INFI-Server in the System Status display of an OperatorWindow;2.Select "Server Configuration";3.Edit the tag "INFI-Server";4.On the "Server" tab, change the Server Type to "INFI 90 Scanner", and click on the "OK" button;5.Exit the Server Configuration application;6.Shutdown Conductor NT and reboot the console.To run the Generic Demo in simulation mode:1.Click on the Window NT taskbar's "Start" button, select "Run", type "RegEdit", and click on the"OK" button'2.Expand the registry tree by clicking on the plus signs beside these yellow folders:"\\HKEY_LOCAL_MACHINE", "SOFTWARE", "ElsagBailey", and "Conductor NT"3.Right-click (click with the right mouse button) on the yellow folder "Servers";4.Select "New", then select "Key", and type "Generic/Demo" for the key's name;5.Right-click on the yellow folder "Generic/Demo", select "New", select "String Value", and typethe path to the script file: "\GenericDemo\gendemo.txt";6.Exit the Windows NT Registry Editor and reboot the computer.NOTE: Block Details and Module Status are not handled by the simulation script and will report the server is unavailable.The operator accounts are:"Operator1", "Operator2", "Operator3", "Engineer1", "Engineer2", "Engineer3","Supervisor1", "Supervisor2", and "Supervisor3":∙Each uses the password "ebailey"∙Each has a privilege level matching the user name"JaneDoe" and "JohnDoe":∙Each uses the password "hello"∙Each has Supervisor 3 privileges, a login context, and Quick Keys "Demo User" (the blank space is part of the name):∙Uses the password "hello"∙Has Operator 3 privileges"AAG":∙provided only for the @aGlance interface to write values to Tag.Atoms∙do not login as this user∙Operator 3 privilegesWallpaper Bitmap:This is not required for the Generic Demo. However, if Conductor NT 1.0 is being demonstrated as part of the Symphony product line, use the symbg_dd.bmp bitmap as the desktop wallpaper. Testing:The current Generic Demo configuration was tested on a standalone computer running Microsoft Windows NT 4.0 Workstation with Service Pack 3, Internet Explorer 3.02, @aGlance Client 3.0 (32-bit for Windows 95 and Windows NT), and Conductor NT 1.0 with Update 1. The video controllers were set to 1024 pixels by 768 lines using 65536 colors. Two disk partitions were used. One partition had the above software with Excel 7.0 (from Microsoft Office 95) and the other partition had the same software with Excel 97. The simulation script was tested first, followed by use of the MFP02. The test printer was a Hewlett-Packard 1200C Deskjet with Postscript support.。