readme
SCST中readme的翻译和fc的相关说明
使用SCST通过FC方式进行卷管理之前必须搭建测试环境：以下是搭建测试环境所需硬件及软件。
测试环境列表：服务器端(target)：服务器型号：NP370D2光纤卡：1块，型号QLA 2460内核版本：Linux 2.6.24所需软件包：scst-1.0.1.1(SCST core )scstadmin-1.0.6 (简化scst配置的工具软件)qla_isp-1.0.2(针对SCST core的FC卡驱动) 客户端(Initiator)：服务器型号：AS500N2光纤卡：1块，型号QLA2460内核版本：Red Hat 企业版5 (kernel 2.6.18)所需软件包：qlafc-linux-8.02.23-3 (FC卡驱动)standalone_sansurfer5.0.1b57_linux（FC卡管理软件）环境搭建详细过程：一．Target端配置以下是target端的配置方法：(1)首先配置target 端，给内核打补丁：Type: patch -p0 scst_exec_req_fifo-2.6.X.patchpatch -p0 io_context-2.6.X.patch内核必须关闭HIGHMEM（通过make menuconfig中配置），否则scst_user模块是无法加载上去的(2)编译和安装SCST模块进入到scst-1.0.1.1目录中Type: makemake install(3)加载SCST模块（scst.ko）Type: cd /lib/modules/2.6.18-92.e15/extramodprobe scst(4)加载所需要的device handlers模块测试实验中加载scst_vdisk.ko模块，所以可以用如下的命令进行加载：Type: cd /lib/modules/2.6.18-92.e15/extra/Devicehandlersmodprobe scst_vdisk（5）编译和安装qla_isp-1.0.1。
GitHub的最佳实践和使用方法
GitHub的最佳实践和使用方法GitHub是一个集代码托管、版本控制、协作开发于一体的在线平台，是程序员和开发者必不可少的工具之一。
本文将从GitHub的最佳实践、分支管理、提交规范和代码审查等方面为大家详细介绍如何有效地利用GitHub进行协作开发。
一、GitHub的最佳实践1. 创建README文件README文件是每个项目的门面，通过它可以让其他人快速了解项目的目的、功能、用法等信息。
尽量使README简单明了，文字清晰，不要出现错别字和语法错误。
2. 使用IssueIssue是GitHub提供的一种问题跟踪系统，可以方便地管理和解决问题。
通过Issue，你可以记录和追踪各种问题、任务和功能需求，同时也可以回答其他人的问题。
3. 善用WikiWiki是一个开源的协作式文档平台，可以帮助开发者创建和共享文档、指南和提示等。
它可以帮助你整理项目的结构、文档和规范，方便其他人了解项目的目的和用途。
二、分支管理1. 主分支主分支通常是master分支，用于对外发布可用的代码。
在任何时候，主分支都应该是稳定、可用、高质量的代码。
尽量不要在主分支上进行实验性的修改和提交。
2. 开发分支开发分支通常是develop分支，用于进行开发和测试。
在开发分支上进行实验性的修改和提交，只有当开发完成并经过测试后才能合并到主分支。
3. 功能分支功能分支通常是feature分支，用于对开发分支上的单个功能进行开发。
每个功能都应该有一个单独的功能分支，这样可以保持代码的可维护性和可测试性。
当功能开发完成并经过测试后，可以将其合并到开发分支。
三、提交规范1. 提交信息提交信息应当简单明了，推荐使用英文，包括提交的类型、句号、描述内容。
其中，“提交类型”应该是固定的，可以是feature、fix、docs、style、refactor、test、chore等类型。
2. 提交频率提交频率应该尽量高，并保持提交的代码尽可能小。
readme(客户端使用须知)
全国数模竞赛上传客户端的注意事项，约定及可能遇到的问题
注意事项:
1.本客户端是一个绿色软件，无需安装，下载的是一个压缩文件，但需要解压后使用，如因未解压造成使用造成不能上传或相关问题请自行负责
2.第一次登录客户端会与远程服务器进行绑定，然后会自动退出，请在退出后重新启动并登录使用即可
3.本客户端仅限于WINDOWS操作系统环境下使用，当前主流的WINDOWS版本(如win7/8/10/xp)均已测试运行正常，但不保证某些版本的情况中出现不能运行或异常情况
4.使用过程中如弹出现有提示框信息，请务必认真阅读，以免影响上传和其他操作
5.建议将本客户端解压到自己的移动硬盘中，或建立本参赛队专属的目录夹
6.一个参赛队，请勿同时使用多个客户端
7.如遇到问题,如已提交过MD5码成功但提交对应该MD5码的文件异常,或出现登录异常,可重新下载本客户端并”重新绑定”后继续尝试使用
一些约定:
1.允许上传的参赛作品文件格式为doc、docx、pdf、wps，支撑材料格式为rar、zip
2.允许上传的文件大小规定最大值为20M，即20971520字节
可能出现的问题：
1.如果出现COMDLG3
2.OCX报错(如下图)，比如在64位的操作系统上运行
解决方法一:请在本应用程序(全国数模竞赛上传客户端.exe)文件上右键点"属性"-"兼容性"-勾选"以兼容模式运行这个程序"进行设置.
解决方法二: 用管理员可以运行，即在本应用程序(全国数模竞赛上传客户端.exe)文件上右键点"以管理员身份运行".
2.遇到防火墙提示(如下图)，请允许，并可设置不再提醒.。
githubapi获取readme
githubapi获取readme使用GitHub API获取README文件是一个简单且常用的操作。
在以下步骤中，我们将使用Python编程语言来实现这个任务。
首先，我们需要先安装必需的库。
我们可以使用`pip`来安装`requests`库，它可以帮助我们发送HTTP请求并获取响应。
```pythonpip install requests```接下来，我们需要导入`requests`库并定义一个函数来获取README文件的内容。
```pythonimport requestsdef get_readme_content(owner, repo):url = f"/repos/{owner}/{repo}/readme"response = requests.get(url)response_json = response.json()readme_content = response_json["content"]return readme_content```上面的代码定义了一个名为`get_readme_content`的函数，它接受两个参数`owner`和`repo`，分别表示所有者和仓库的名称。
函数首先构造了一个API请求的URL，然后使用`requests.get`发送GET请求并获取响应JSON。
最后，我们从响应JSON中提取`content`字段，该字段包含了README文件的Base64编码内容。
使用这个函数，我们可以获取README文件的内容。
以下是一个示例：```pythonowner = "github_username"repo = "repository_name"readme_content = get_readme_content(owner, repo)print(readme_content)```在上面的代码中，将`github_username`替换为你的GitHub用户名，将`repository_name`替换为仓库的名称。
Readme(安装参考方法二)
8.打开License Server Administrator，启动服务。
FEATURE ArcView3 ARCGIS 10.0 01-jan-0000 2048 ADBC8EF1F28B9DC18F96 \
vendor_info=TXDH42L7EY6Z4X4JE221 ck=174
FEATURE ArcView31 ARCGIS 10.0 01-jan-0000 2048 FDCC4EB18017443D6297 \
vendor_info=H2T570H3D291F1TGH254 ck=55
FEATURE ArcReader ARCGIS 10.0 01-jan-0000 2048 0D9CBE710E5695C37E6E \
vendor_info=758Y1G82MC96F90LD184 ck=78
4.如果你只想授权几个功能就选择相应的功能按添加，每添加一个就增加一个功能的授权（按移除可以移除上一个授权，按清除可清除所有已添加的授权），如果你想授权所有功能，按所有即可。
5生成了许可文件内容后，全选框内的文字复制这些内容，新建一个文本文档，粘贴这些文字，另存文件为service.txt。
6.也可将下面上下------------之间内容copy至service.txt，就不用注册机了，这个是长久注册的，要修改“此处为计算机名”内容为你的计算机名
python的readme范例
以下是一个简单的Python项目的readme范例：markdown# My Python Project## AboutThis is a simple Python project that does something interesting. It demonstrates a basic structure for Python projects and provides a template for creating your own.## UsageTo use this project, you need to have Python installed on your computer. Once you have Python installed, you can follow these steps:1. Clone or download the project to your computer.2. Open a terminal or command prompt and navigate to the project directory.3. Run the `main.py` file to start using the project.## RequirementsTo run this project, you need to have the following dependencies installed:* Python 3.x* Some other dependencies that are listed in the `requirements.txt` file.## InstallationTo install the project, you can use the `pip` package manager to install the required dependencies. Run the following command in your terminal or command prompt:```shellpip install -r requirements.txtThis command will install all the required dependencies for the project. ContributingWe welcome contributions to this project! If you have an idea or bug report for the project, please create a pull request or issue on GitHub. We also welcome contributions from new developers who want to join our team and help make this project better.LicenseThis project is licensed under the MIT license, which means that you can use andmodify it for free, as long as you include the license header in any derivative works that you create. For more information about the license, please refer to the LICENSE file in the project's root directory.。
Gitee中README.md文件的编辑和使用
Gitee中README.md⽂件的编辑和使⽤最近对它的README.md⽂件颇为感兴趣。
便写下这贴，帮助更多的还不会编写README⽂件的同学们该⽂件⽤来测试和展⽰书写README的各种markdown语法。
开始编辑README当没有README⽂件的时候我们可以添加⼀个README.me⽂件关于标题规范的README⽂件开头都写上⼀个标题，这被称为⼤标题⽐⼤标题低⼀级的是中标题，也就是显⽰出来⽐⼤标题⼩点。
⼤标题===效果如图：在⽂本下⾯加上等于号 = ，那么上⽅的⽂本就变成了⼤标题。
等于号的个数⽆限制，但⼀定要⼤于0个哦。
⽐⼤标题低⼀级的是中标题，也就是显⽰出来⽐⼤标题⼩点中标题-------效果如图：在⽂本下⾯加上下划线 - ，那么上⽅的⽂本就变成了中标题，同样的下划线个数⽆限制。
除此之外，你也会发现⼤，中标题下⾯都有⼀条横线，没错这就是 = 和 - 的显⽰结果。
如果你只输⼊了等于号=，但其上⽅⽆⽂字，那么就只会显⽰⼀条直线。
如果上⽅有了⽂字，但你⼜只想显⽰⼀条横线，⽽不想把上⽅的⽂字转义成⼤标题的话，那么你就要在等于号=和⽂字直接补⼀个空⾏。
补空⾏：是很常⽤的⽤法，当你不想上下两个不同的布局⽅式交错到⼀起的时候，就要在两种布局之间补⼀个空⾏。
如果你只输⼊了短横线（减号）-，其上⽅⽆⽂字，那么要显⽰直线，必须要写三个减号以上。
不过与等于号的显⽰效果不同，它显⽰出来时虚线⽽不是实线。
同减号作⽤相同的还有星号*和下划线_，同样的这两者符号也要写三个以上才能显⽰⼀条虚横线。
除此以外，关于标题还有等级表⽰法，分为六个等级，显⽰的⽂本⼤⼩依次减⼩。
不同等级之间是以井号 # 的个数来标识的。
⼀级标题有⼀个 #，⼆级标题有两个# ，以此类推。
# ⼀级标题## ⼆级标题### 三级标题#### 四级标题##### 五级标题###### 六级标题效果如图：实际上，前⽂所述的⼤标题和中标题是分别和⼀级标题和⼆级标题对应的。
README_怎样编译升级固件_ATS2823
5. 升级固件，可以通过”Card product tool V2.03”生成卡量产固件。具体过 程请参考”US282A 软件开发指南”。
6. 升级固件，也可以使用 ATT 工具。 请先安装”Automated testing tools V1.01”.安装完成后，使用”脚本编 辑工具”,打开”US282A_BTBOX_DVB_ATS2823.atf”勾选”固件升级准备”和” 固件升级测试”，点击保存。
然后用”自动化测试工具”，升级固件。具体使用方法请参考工具上的帮助 文档。
ቤተ መጻሕፍቲ ባይዱ1. 进入..\case\fwpkg
2. 如果需要编译, 输入 make clean; make DVB_ATS2823.完成后就可以生成 US282A_BTBOX_DVB_ATS2823.FW.
3. 后续需要再次生成固件,可以通过 make build_DVB_ATS2823
4. 如果要修改某些模块的代码，可以直接指向对应目录，编译代码。再用上面 的方法生成固件。如：
README-step7 v5.4 安装说明
SIMATICSTEP 7 V5.4 Programming Software for SIMATIC S7 / M7 / C7Notes on Installation and UsageThese notes should be considered more up-to-date than the information in other documents. Read the notes carefully, because they contain information on installing and using STEP 7 V5.4.Note when printing the file that the left and right margins are set to a width of 25 millimeters for A4 portrait format.ContentsNotes on Installation1 Contents of the Consignment2 Hardware Requirements3 Software Requirements3.1 Operating Environment3.2 Memory Requirements3.3 Compatibility with Other Software Products3.3.1 Rational ClearCase3.3.2 Network Settings when Using other Software Products3.3.3 Interdependency with An Installed S7 Fault-tolerant System3.4 Online Documentation3.5 Upgrading from an earlier STEP 7 version and changing over from STEP 7Lite3.5.1 STEP 7 V5.4 Upgrade3.5.2 STEP 7 V5.4 PowerPack4 Installation4.1 Installing STEP 7 V5.44.2 License Key of STEP 7 V5.44.3 Uninstalling STEP 7 V5.44.4 Additional Notes on Installation4.4.1 Using a Wheel-Mouse4.4.2 Notes on using Communication Cards in PCs/ PGs4.4.3 Installing on foreign-language operating systemsNotes on Usage (Release Notes)1 New Features and Changes in the New Version2 Notes on Configuring and Operating the Software2.1 How STEP 7 Fulfills the IEC Standard2.2 General Notes2.3 Using Network Drives2.4 Multi-user Operation2.5 Multiprojects2.6 Swapping Different Versions of STEP 72.7 Libraries and Sample Projects2.8 SIMATIC Manager2.9 Password Protection2.10 Using Symbolic Names (Upper and Lower Case for Symbols)2.11 Hardware Configuration (Central)2.12 Hardware Configuration (PROFIBUS DP)2.13 Hardware Configuration (PROFINET IO)2.14 Redundant I/O: Channel-granular Redundancy2.15 Diagnosing Hardware2.16 Configuring Connections2.17 MPI / PROFIBUS Network Settings2.18 SIMATIC M72.19 Ladder Logic, Function Block Diagram, and Statement List, Reference Data 2.20 Message Configuration2.21 Translating Texts2.22 Managing Multilingual Texts2.23 S7-PDIAG2.24 Converting S5 Programs to S7 Programs2.25 Converting TI Programs to S7 Programs2.26 Fault-tolerant Systems2.27 Note on Using Foreign-Language Character Sets2.28 Note on the use of SIMATIC Logon3 Notes on DocumentationNotes on InstallationThe installation notes contain important information that you will require in order to install STEP 7 V5.4 Read these notes before installing the software.1 Contents of the ConsignmentThe two CDs in the content of consignment contain a complete version of STEP 7 V5.4.This version is in 5 languages and can be run using the operating systems listed underChapter 3.1.STEP 7 V5.4 is currently supplied on two CDs "STEP 7 V5.4 CD1/2" and "STEP 7 V5.4CD2/2" " in the contents of consignment with a floating, upgrade, rental or trial license:STEP 7 V5.4 (Floating License)Order number: 6ES7810-4CC08-0YA5The following items are included in this package:∙ 2 CDs STEP 7 (CD1/2 and CD2/2)∙ 1 License Key Disk∙ 1 Certificate of License∙ 1 Product InformationSTEP 7 V5.4 (Floating License) (V3/V4/V5.x > V5.4)Order number: 6ES7810-4CC08-0YE5The following items are included in this package:∙ 2 CDs STEP 7 (CD1/2 and CD2/2)∙ 1 License Key Disk∙ 1 Certificate of License∙ 2 Product InformationsSTEP 7 V5.4 PowerPack (Floating License)Order number: 6ES7810-4CC08-0YC5The following items are included in this package:∙ 2 CDs STEP 7 (CD1/2 and CD2/2)∙ 1 License Key Disk∙ 1 Certificate of License∙ 2 Product InformationsSTEP 7 V5.4 Rental License (50h)Order number: 6ES7810-4CC08-0YA6The following items are included in this package:∙ 2 CDs STEP 7 (CD1/2 and CD2/2)∙ License Key Disk∙ 1 Certificate of License∙ 1 Product InformationSTEP 7 V5.4 Trial License (14 days)Order number: 6ES7810-4CC08-0YA7The following items are included in this package:∙ 2 CDs STEP 7 (CD1/2 and CD2/2)Contents of the STEP 7 CDsCD1/2 (Installation CD)∙ STEP 7 V5.4∙ Converter for the conversion of TI405 and TI 505 programs∙ Automation License ManagerCD2/2∙ Shareware version of Acrobat Reader in five languages, with which you can view and print the supplied manuals∙ Product Notes: "What's New"∙ Product Notes: "New Modules"∙ Product Notes: "Central Installation"∙ Manual: "Getting Started: Working with STEP 7"∙ Manual: "Programming with STEP 7"∙ Manual: "Configuring Hardware and Communication Connections with STEP 7"∙ Manual: "System Modification in RUN Mode via CiR"∙ Manual: "Automation System S7-400H - Fault-Tolerant Systems"∙ Manuals: "NCM S7"∙ Manual: "From S5 to S7"∙ Manual: "Ladder Logic (LAD) for S7-300/400"∙ Manual: "Statement List (STL) for S7-300/400"∙ Manual: "Function Block Diagram (FBD) for S7-300/400"∙ Manual: "Standard and System Functions for S7-300/400"∙ Manual: "Standard and System Functions for TI STEP 7 Converter"∙ Manual: "PID Control"∙ Manual: "PID Temperature Control"∙ Compatibility List∙ SIMATIC iMap STEP 7 Addon∙ Description of the Command InterfaceThe manuals are available in an installable form on CD1/2 and are optionally available on your computer after STEP 7 has been installed. If you do not install the manuals, you can also view at any time on CD2/2.In order to work with the STEP 7 V5.4software, you need a programming device or a PC with the following minimum requirements for processor speed/performance, RAM and graphics capability:Operating System Minimum Requirements for:Processor RAM Graphics--------------------------------------------------------------------------------------------------------------------------∙ MS Windows 2000 Professional 600 Mhz 512 MB*) XGA 1024x78616 Bit color depth ∙ MS Windows XP Professional 600 Mhz 512 MB*) XGA 1024x78616 Bit color depth ∙ MS Windows Server 2003 2.4 GHz 1 GB XGA 1024x76816 Bit color depth *) A minimum RAM of 1 GB MB is recommendedUse a programming device or PC with the latest performance capabilities if you are editing extensive STEP 7 projects or working with hardware configurations containing several hundred modules (CPUs, slaves, I/O devices, etc.).In addition, you will need an external prommer for SIMATIC memory cards / MMC if you are using a PC and want to save your user programs to EPROMs and a SIMATIC NET interface if you want to use online functions to the PLC system with your personal computer.3.1 Operating EnvironmentOperating SystemsSTEP 7 V5.4 is a 32-bit application that is released for the following operating systems: Operating System Service Pack------------------------------------------------------------------------------------------------------------------------∙ MS Windows 2000 Professional SP4∙ MS Windows XP Professional SP 1 (or SP1a) or SP2∙ MS Windows Server 2003 with or without SP1 as a workstation computer (Exception: SIMATIC M7, refer to Notes on Usage, Chapter 2.17)You can find information about the operating systems on the Internet at Microsoft.STEP 7 V5.4 will not run in:∙ MS Windows 3.1∙ MS Windows for Workgroups 3.11∙ MS Windows XP HomeThe operating systems MS Windows 95, MS Windows 98SE, MS Windows Millenniumand MS Windows NT 4.0 are no longer supported since STEP 7 V5.3.Internet ExplorerAll operating systems must be using MS Internet Explorer 6.0 (or higher).User RightsRegarding user rights as of STEP 7 V5.3 incl. SP2, please observe the following:To be able to work with STEP 7 in MS Windows 2000/2003/XP, you must have loggedon at least as the user (not as a guest). You must possess administrator's rights forinstalling the STEP 7 software and also for setting up modules using the "Setting thePG/PC Interface" application. When using optional packages please observe the rightsrequired by the respective optional packages.If projects are saved on NTFS drives, the users must be granted full access here. Thisalso applies to the folders with the HSP updates (default: C:/HWUPDATES). Accesswithin S7PROJ is automatically granted to all users.Note:∙ The executability under user rights is only enabled for STEP 7 itself. Operation under user rights for optional packages is not guaranteed. Administrator or primary userrights may be required here.∙ After installing / uninstalling new hardware, the computer must be run at least once under administrator rights.File SystemsSTEP 7 achieves a slightly lower performance when operating on a MS Windows NTfile system (NTFS) as opposed to a FAT file system.Hibernation ModeShifting to hibernation mode is generally allowed by STEP 7. However, hibernationmust not be triggered if online connections are open or projects are being accessed bySTEP 7 applications via a network.In such case, online connections could be unintentionally terminated, and open projects on networks may experience data loss.For these reasons, the energy options for the operating system in the Windows ControlPanel should be set so that hibernation is not automatically triggered (by timer).Hibernation should not be triggered manually by the user in the cases mentionedabove.3.2 Memory RequirementsMemory Requirements for STEP 7Depending on your installation requirements and the number of languages installed,STEP 7 V5.4 requires between approx. 650 MB and 900 MB of memory on your harddisk. The exact value also depends on your operating system and on the file systemused on your programming device/personal computer.MS Windows Swap FileThe supported Windows operating systems also require additional free space on thehard disk (typically C:) for their swap files, depending on the memory configuration. Youshould keep at least double the value of the RAM free. (Example: If you have 512Mbytes of RAM, you will require another 1024 Mbytes of free space on the hard disk forthe swap file after STEP 7 has been installed.) Depending on the size of the project, itmay be necessary to have a larger swap file, for example, when copying an entireproject (twice the size of the project on the hard drive in addition). If the free memoryarea for the swap file is too small, errors may occur (the program could possibly crash).Additional Windows applications which run parallel to STEP 7 V5.4 (such as MicrosoftWord) also require additional hard disk space for the swap file.In order to ensure that the required memory for the swap file is really available, theminimum size for the swap file should be set to the above value. This can be set inWindows (for example, Windows XP Professional) in the taskbar in Start > Settings >Control Panel (in System > Advanced > System Performance > Settings > Advanced).You must make certain that you have enough free memory on the drive where theproject data are located. If there is not enough memory on the drive, the project datamay be destroyed during an operation (for example, when compiling an STL source fileinto blocks). We also recommend that you do not store the project data on the samedrive as the Windows swap file.3.3 Compatibility with Other Software Products3.3.1 Rational ClearCaseSTEP 7 projects must not be stored on ClearCase drives; that is, drives that are linkedto a ClearCase View (MVFS).3.3.2 Network Settings when Using other Software ProductsIf you are using other software products (for example, mail providers) on a programmingdevice or PC with STEP 7, observe the additional notes on network settings in thesection "Using Network Drives" (in Notes on Usage) in the second half of this READMEfile.3.3.3 Interdependency with An Installed S7 Fault-tolerant SystemThe configuration of fault-tolerant systems (H system) is integrated as of STEP 7 V5.3.If STEP 7 V5.4 is installed on a PC on which the S7 H Systems add-on package isinstalled, this is removed. Do not install the “S7 H Systems” optional package again. It isno longer required.3.4 Online DocumentationThe online help in STEP 7 V5.4 is split into two sections.You can find notes on the current context in the same way as with the standardWindows help.The general section of the online help is based on the HTML format.You can find more information on the structure of the documentation in Chapter 3 (inNotes on Usage) in the second half of this README file.3.5 Upgrading from an earlier STEP 7 version and changingover from STEP 7 Lite3.5.1 STEP 7 V5.4 UpgradeTo install the upgrade package, you must have a valid license for STEP 7 V3.x, V4.x,V5.0, V5.1, V5.2 or V5.3.--------------------------------------------------------------------------------------------------------------------------NoteTake into account that an upgrade may require the operating system to be replaced,because as of STEP 7 V5.3 older operating systems are no longer supported (refer toChapter 3.1). Further information on the upgrade is contained in the productinformation.The existing authorization / License Key with the AuthorsW / Automation LicenseManager program has to be saved to a floppy disk before the operating system isreplaced.--------------------------------------------------------------------------------------------------------------------------3.5.2 STEP 7 V5.4 PowerPackThe PowerPack is used to upgrade from a STEP 7 Lite V2.0 installation to STEP 7 V5.4.To install the PowerPack, you must have a valid license for STEP 7 Lite.--------------------------------------------------------------------------------------------------------------------------NoteTake into account that an upgrade may require the operating system to be replaced, because as of STEP 7 V5.3 older operating systems are no longer supported (refer to Chapter 3.1). Further information is contained in the product information.If STEP 7 Lite is installed on a PC running MS Windows XP Home, you will also have to upgrade the operating system since STEP 7 is not released for use on Windows XP Home.The existing authorization / License Key with the AuthorsW / Automation License Manager program has to be saved to a floppy disk before the operating system is replaced.--------------------------------------------------------------------------------------------------------------------------4 Installation4.1 Installing STEP 7 V5.4When installing STEP 7 V5.4, you can overwrite existing installations of STEP 7 V5.1,V5.2 or V5.3 whilst observing the authorized operating systems (refer to Chapter 3.1).You do not have to uninstall these STEP 7 versions and optional packages prior to theinstallation. However, you must uninstall older versions and their optional packagesbeforehand.In order to obtain the optimum display of the information during the Setup, you shouldset the color scheme in the control panel of your programming device/personalcomputer to at least 65536 colors.Before starting the Setup program, close all applications (such as Microsoft Word, etc.)and the "Control Panel" window, since you will need to restart Windows following theinstallation of STEP 7 V5.4so that all system variables can be entered completely.Insert the STEP 7 CD 1/2 in the drive. The setup program will guide you through theinstallation. The setup program starts automatically after the STEP 7 CD is inserted inthe drive. If you have disabled this function on your computer, start the setup programby double-clicking the SETUP.EXE program in the root directory.In the component selection box, select the Acrobat Reader, STEP 7, the AutomationLicense Manager, Acrobat Reader and any other components that you wish to install.If you would like to change the installation path suggested in the setup during the STEP7 installation, please note that you cannot install it directly to a root directory (e.g. D:) onyour computer. There has to be at least one higher-level folder such as "STEP7", forexample, D:\STEP7.These components will then be installed and entries will be made in Microsoft Windowsfiles.The following notes are intended to help you make the correct user entries requiredduring the Setup program:∙ The drive on which you install your STEP 7 V5.4system can be selected freely. On some PCs/programming devices, you will not be able to select the drive via theselection list. In this case, simply enter the drive with its path in the appropriate inputbox (for example, "e:\Siemens/Step7"). Note that all STEP 7 optional packages mustalso be installed on this drive, so there must be sufficient space available (see the"Memory Requirements" section). Avoid installing STEP 7 on a SUBST drive.∙ Before you use STEP 7 V5.4, Windows must be restarted. Only then do all of the Microsoft Windows entries become active. If you do not restart Windows, STEP 7V5.4cannot run properly and data may be lost. If the installation procedure isaborted, you will also need to restart Windows.∙ Refer to the tables in the S7KOMP_B.PDF file (the directory "Step7" following installation) for information on which versions of the optional packages can run withSTEP 7 V5.4 under the respective operating systems.∙ STEP 7 must not be installed in a directory the path of which includes characters that are not listed in the A SCII character set (refer to Chapter 2.26, section “Notes onUsage”).Contact your Siemens representative for more up-to-date information or check ourwebsite: http://www.ad.siemens.de/support.If the required version is not available on the computer, Acrobat Reader is automaticallysuggested for installation. When prompted, the STEP 7 CD2/2 must be inserted duringthe installation.--------------------------------------------------------------------------------------------------------------------------NoteSTEP 7 registers itself in the system files of the MS Windows operating system. Youcannot move or rename STEP 7 files or folders using Microsoft Windows utilities suchas the Explorer or modify STEP 7 data in the Microsoft Windows registry. The programmay no longer run properly after such modifications.--------------------------------------------------------------------------------------------------------------------------4.2 License Key of STEP 7 V5.4Before you can start working with STEP 7, you must transfer the license key from thelicense key diskette to the computer. There are two ways of doing this:∙ While you are installing STEP 7, the Setup program displays a message if there is no suitable license key installed on your computer. You can then decide whether youwant the license key to be installed by the “Setup” program or whether you want toinstall the license key manually at a later time using the “Automation LicenseManager” program.∙ If the license key cannot be installed during setup, continue the Setup program without installing the license key. Then boot the computer and install the license keyusing the taskbar in "Start > SIMATIC\License Simatic > License Management >Automation License Manger."To operate STEP 7 as of V5.3, you must make sure the Automation License Manager is installed.After the upgrade from V5.3 to V5.4, the License Key for V5.4 has to be used.-----------------------------------------------------------------------------------------------------------------NoteAs of STEP 7 V5.3, the authorization/the license key can be installed on all local drives.The Automation License Manger prevents the authorizations/license keys from beinginstalled on invalid drives or media such as RAM drives, diskettes or compressed drives(i.e. DBLSPACE). If the drive in a device is reported as being a "removable medium"and not, as usual, as a "hard drive", it will be treated as a CD, which means that nolicense key may be installed on it.In the case of compressed drives, you can install the authorization on the associatedhost drive.Read the notes on the Automation License Manager in the ALM README.WRI file onthe STEP 7 installation CD under "Automation License Manager\disk1\".Hidden files are stored in the folder "<Drive, on which the authorization/license key isinstalled>:\AX NF ZZ". These files and the folder must not be deleted, moved, or copied.They contain data required for the licensing of your software.If you do not adhere to these guidelines, the authorization/license key may beirretrievably lost.--------------------------------------------------------------------------------------------------------------------------Notes on error-free use of the license keys∙ The license key diskette must not be read-only. Because the license key diskette is to be used without write protection, there is a danger that a virus could betransferred from the hard disk to the diskette. You should therefore run a virus checkon your PC or programming device every time you install or remove a license key.∙ If you use an optimizing program that enables you to move fixed blocks of memory, only use this option once you have moved the license key from the hard disk back tothe license key diskette.∙ With the License Key a specially marked cluster is shown on the target drive. Some check programs display this cluster as "defective". Do not try to restore it.∙ Do not forget to transfer the license key to the license key diskette before formatting, compressing, or restoring your hard disk or before installing a new operating system.∙ If a backup copy of your hard disk contains copies of license keys, there is a danger that these copies may overwrite the valid installed license keys when you restoreyour backup data to the hard disk, thereby destroying the valid license keys. Toprevent a valid license key from being overwritten by a backup copy, you mustremove all license keys before you make a backup copy or exclude the license keysfrom the backup.Using the trial license:If no valid license key is installed for STEP 7 V5.4, a trial license key is used, which issupplied and installed by default together with STEP 7. However, STEP 7 can only beused for 14 days with this license key. When STEP 7 is started the first time without avalid license key, activation of the trial license key is offered.4.3 Uninstalling STEP 7 V5.4--------------------------------------------------------------------------------------------------------------------------NoteSoftware products must be uninstalled according to Microsoft Windows conventions.Use the Microsoft Windows application "Add/Remove Programs" (in the taskbar inStart > Settings > Control Panel > Add/Remove Programs) to remove your softwarepackage (for example, "STEP 7").As an alternative, you can use the setup program to uninstall a program.--------------------------------------------------------------------------------------------------------------------------If you uninstall an older version of STEP 7 in order to install STEP 7 V5.4, you mustfirst uninstall any existing optional packages for STEP 7 as well.When uninstalling the software, device drivers (for EPROM or communication interfaces) are not removed. If you have not installed any other products that require these driverson your computer, you should uninstall the drivers for the communication interface byopening the "Setting the PG/PC Interface" application (Start > SIMATIC > STEP 7 >Setting the PG/PC Interface and clicking the "Select" button) and uninstall the driverfor the EPROM interface with the "Configure Memory Card" option (Start > SIMATIC >STEP 7 > Configure Memory Card and clicking on "No EPROM driver").4.4 Additional Notes on Installation4.4.1 Using a Wheel-MouseWhen using a wheel mouse, be sure that the driver supplied by the manufacturer isinstalled. If this is not the case, STEP 7 will not always support the wheel feature of themouse.4.4.2 Notes on using Communication Cards in PCs/ PGsCP5611/ CP5611 Onboard (SIMATIC NET PROFIBUS Interface Via PCI Bus)In order to use the CP5611 card you require a PC or a programming device with PCIbus. You can then address SIMATIC stations via MPI or PROFIBUS (9.6 Kbps to 12Mbps).If you install STEP 7 after the CP has been inserted in the computer, the Plug and Playmechanism enters the CP5611 in the Device Manager of the Control Panel\System in"Other Devices". Therefore, the CP is sometimes not recognized when installing STEP7.In such cases, remove the CP5611 in the Device Manager after installing STEP 7 andreboot your computer.Observe the notes in the online help under "Setting the PG/PC Interface."CP5511 (SIMATIC NET PROFIBUS Interface Via PCMCIA)The card and socket services required to operate the card form part of MS 2000/XP.The CP5511 has plug-and-play facilities, meaning that the card is recognized by MSWindows 2000/XP and is integrated automatically into the system, provided yourPC/programming device has sufficient free resources (interrupt, address area).The CP 5511 cannot be operated in notebooks that are equipped with a PCMCIAcontroller of the type Omega Bridge II or TI 1130.Note:∙ The CP 551 does not support ACPI (Advanced Configuration and Power Interface) completely.∙ The CP 5511 is not supported under MS Windows Server 2003 .CP5512 (SIMATIC NET PROFIBUS Interface Via PC Card)A PC or a programming device with PC card slot is required to use the CP5512. Youcan then address SIMATIC stations via MPI or PROFIBUS (9.6 Kbps to 12 Mbps).MPI-ISA Card/ MPI-ISA OnboardThe MPI-ISA card and the MPI-ISA Onboard are no longer supported under MS Windows 2000 / XP and under MS Windows Server 2003.CP5411The CP5411 is not supported since STEP 7 V5.2.Hardnet ModulesIf you use the Industrial Ethernet network card CP1613 or the PROFIBUS cardsCP5613/14, you require the optional package SIMATIC NET PC additionally in a version compatible with STEP 7 V5.4 (see Compatibility List S7KOMP_A.PDF in the installation directory "STEP7").You require the SIMATIC-Net software as of V6.2 (CD 11/2003) to operate CP5613A2 and CP5614A2.General PC/Programming Device SettingsCommissioning Plug-and-Play Compliant ModulesTo commission the Plug-and-Play compliant modules (e.g. CP 5511, CP 5512 and CP 5611) in MS Windows 2000/XP/Server 2003, please proceed as follows:1. Install STEP 7. Close the dialog "Set PG/PC Interface" which appears at the end ofthe Setup without entering anything.2. Close MS Windows, shut down the PC and install the card. The CP 5511 or CP5512 can also be inserted in during operation.3. The communication module is installed automatically after the restart (or after CP5511 or CP 5512 has been inserted).4. Under Windows 2000, the message "New hardware found" is displayed. Confirm thismessage and all following dialogs (do not click on CANCEL).5. Under WinXP/Server2003, the Hardware Wizard is displayed. In the first dialogshown, select the option "No, not this time". Confirm all following dialogs (do not click on CANCEL).6. Then check the settings or select the desired interface configuration in "Set PG/PCInterface" (Start > SIMATIC > STEP 7>Set PG/PC Interface).If STEP 7 is installed after the plug-and-play compliant CPs (for example CP5611) on the computer, the CP is not recognized under MS Windows 2000/XP/Server 2003 when STEP 7 is installed.In this case remove the CP (network controller) after the STEP 7 has been installed in the device manager of the Control Panel\System under "Other components" and reboot your computer.Observe the information in the online help under "Set programming device/personal computer interface".When STEP 7 is installed on programming devices, the communication drivers are installed automatically and the default settings are accepted.The CP5611 has to be installed in the case of programming devices 7x0 PII / PIII,PG8x0 and PCs with onboard MPI interfaces.Setting of Interrupt and AddressMS Windows 2000/XP/Server 2003:。
readme viewer 使用
标题：深入理解和探索Readme Viewer的使用1.引言Readme Viewer是一个简单而强大的工具，它能够帮助用户轻松阅读、编辑和管理Markdown格式的Readme文件。
它的使用范围广泛，可以应用于软件开发、项目管理、团队协作等多个领域。
在本文中，我们将深入探讨Readme Viewer的使用方法和技巧，帮助您更全面地理解和运用这一工具。
2.Readme Viewer的基本功能在开始深入探讨Readme Viewer的使用之前，让我们先来了解一下它的基本功能。
Readme Viewer可以打开、编辑和保存Markdown 格式的Readme文件，支持实时预览和代码高亮显示。
它还具有自动转换格式、插入表格和图片等实用功能，是软件开发人员和项目经理不可或缺的工具之一。
3.如何使用Readme Viewer3.1 安装和启动要使用Readme Viewer，首先需要从官方全球信息湾或应用商店下载安装，并在电脑或手机上启动。
安装完成后，您可以双击图标或点击应用程序来打开Readme Viewer。
3.2 打开和编辑Readme文件在Readme Viewer的主界面上，您可以点击“打开”按钮来选择需要编辑的Readme文件，或者直接拖拽文件至界面中即可打开。
编辑功能非常简单，您可以直接在编辑框中进行文字修改，也可以插入信息、图片或表格等元素。
3.3 实时预览和保存Readme Viewer同时支持实时预览功能，您可以随时查看编辑后的效果。
编辑完成之后，记得点击“保存”按钮来保存您的修改，以确保不会丢失任何重要内容。
4.更高级的功能和技巧4.1 自动转换格式Readme Viewer可以自动转换Markdown格式的文本为HTML 格式，让您可以直观地查看和共享Readme文件的内容。
4.2 插入表格和图片除了基本的文字编辑之外，Readme Viewer还支持插入表格和图片的功能。
这可以让您更直观地展示和管理项目的相关信息。
pycharm的readme
pycharm的readme
PyCharm是一款功能强大的Python集成开发环境（IDE）。
它为开发者提供了一个高效、灵活且易于使用的平台，用于编写、测试和调试Python代码。
PyCharm具有许多强大的功能和工具，使开发者更加高效。
其中包括代码自动补全、语法高亮、代码导航、内置的调试器以及版本控制集成（如Git）等。
这些工具能够帮助开发者提高开发速度和质量，减少错误和调试时间。
PyCharm还内置了许多有用的功能，如内置终端、集成Python控制台和交互式Python shell等。
这些功能使开发者能够在一个环境中完成大部分工作，无需切换到其他工具。
PyCharm支持多种项目类型，如Django、Flask和科学计算等。
无论是Web开发还是数据科学，PyCharm都提供了丰富的工具和功能，帮助开发者更好地完成项目。
PyCharm还有一个强大的插件系统，允许开发者根据自己的需求扩展功能。
这意味着开发者可以根据项目的特定要求添加新的工具和功能，以提高开发效率和灵活性。
总而言之，PyCharm是一款功能强大且易于使用的Python开发工具，可以满足开发者在各种项目类型中的需求。
无论是初学者还是专业开发者，PyCharm都能提供一个高效且舒适的开发环境。
readme 描述 api 的模板
从 read me 描述 API 模板的角度来看，一份高质量的文章应该覆盖以下几个方面：1. 简要介绍: 在开篇，可以简要介绍什么是 API，以及它在软件开发中的重要性。
可以用一段引人入胜的故事或者案例来引出 API 的直观作用，让读者产生共鸣。
2. API 的基本结构和元素: 在这一部分，需要详细介绍一个标准的 API 的基本要素，比如端点、请求方法、参数、响应等。
可以用一些图表或者示例代码来说明这些概念，帮助读者更直观地理解。
3. Readme 描述 API 的重要性: 这一部分可以深入探讨为什么要在API 的文档中添加 Readme 描述，以及它能够为开发者带来怎样的便利。
可以从易用性、可维护性等角度来分析 Readme 描述的价值。
4. 如何写一个优秀的 Readme 描述: 在这一部分可以共享一些写作技巧和经验，比如清晰明了地描述每个端点的作用和输入输出，提供示例代码和使用方法，以及如何保持文档的实时性等。
5. 个人见解和理解: 作者可以共享对于 Readme 描述 API 的个人见解和理解，比如在实际开发中遇到的挑战和解决方案，以及未来对于API 文档的发展趋势等。
6. 总结: 可以对全文进行回顾性的总结，重点强调 Readme 描述 API的重要性和价值，鼓励读者在实际工作中多加关注和实践。
以上是对于《read me 描述 API 的模板》主题的一些思路和方向，希望有助于撰写一篇全面、深入和有价值的文章。
API（Application Programming Interface）是软件开发中非常重要的一部分，它提供了一种让不同软件系统或组件进行交互的方式，可以让不同的系统之间进行数据交换和功能调用。
而在 API 中，Readme 描述则是非常关键的一部分，它可以帮助开发者更好地理解和使用 API，提高开发效率和代码质量。
接下来，我们将深入探讨如何编写一份高质量的Readme 描述 API 文档，并共享一些实用的写作技巧和经验。
initialize repository with a readme
initialize repository with a readme 在软件开发中，初始化一个仓库是非常重要的一步。
一个好的仓库初始化可以帮助团队更好地协作，更快速地开展项目。
本文将介绍如何使用“initialize repository with a readme”这个功能来初始化一个仓库，并讲解初始化仓库的好处。
一、什么是“initialize repository with a readme”“initialize repository with a readme”是Github提供的一个功能，它可以帮助用户在创建新的仓库时，自动创建一个README.md 文件。
这个README.md文件可以包含一些项目的基本信息，例如项目的介绍、使用方法、贡献者等。
这个功能可以帮助用户快速创建一个基本的仓库，并且让其他人更好地了解这个仓库。
二、如何使用“initialize repository with a readme”使用“initialize repository with a readme”非常简单，只需要在创建仓库的时候勾选“initialize repository with a readme”即可。
具体步骤如下：1. 登录Github账号，进入仓库列表页面。
2. 点击“New”按钮，创建一个新的仓库。
3. 在创建仓库的页面中，找到“Initialize this repository with a README”选项，勾选上。
4. 填写仓库的名称、描述等信息，选择仓库的类型（公开或私有），然后点击“Create repository”按钮。
5. 完成上述步骤后，Github会自动创建一个README.md文件，并将其添加到仓库中。
三、初始化仓库的好处使用“initialize repository with a readme”可以带来以下好处：1. 提高项目的可读性README.md文件是一个项目的重要组成部分。
ReadMe_j141036-ed01
Subject: Green Light for the static patch j1.410.36 / Release R.10Hello,We have received the green light from R&D to install the j1.410.36 patch.The patch j1.410.36 is available on BPWS in Limited Availability.Patch alignment and Compatible DataBase version:Patch Patches Aligned DB version Compatilble tillg1 g1.503.35.k g1.503.h1 h1.301.50 h1.301.50i1 i1.605.29 i1.605.31Patches aligned : a correction in h1.301.50 is available in the Patch alignedDB version compatible : from h1.301.50, you can move to this version.Content of the patch j1.410.36========================================================Static binaries delivered in j1.410.36 from STATIC environmentAR0_STU AS0_STU CN0_STU CN1_STU CS0_STU DA0_STU DE0_STU DE1_STU DE2_STU EE0_STUEN0_STU ES0_STU ES1_STU ES3_STU Eva_tool FI0_STU FR0_STU FR1_STU FR2_STU GEA_STU GR0_STU HR0_STU HU0_STU IL0_STU IT0_STU IT1_STU JP0_STU KR0_STU LT0_STU LV0_STU MONITELmodNL0_STU NL1_STU NO0_STU PL0_STU PT0_STU PT1_STU Packages.dct RO0_STU RU0_STU SI0_STUSK0_STU SV0_STU TEL.SYM TR0_STU TRACEmod US0_STU WAIT.S YM YU0_STU _anti_loop accounting.mtcl agentmao applications.mtcl attr.cry attr.cry.Z bics boards.mtcl broadcast broadcast.SYM ccd.mtcl cfgUpdate checkinitrem chlog cmisd cmisd.SYM common.DE0 common.EN0 common.ES0 common.FR0 common.GEA common.IT0 common.NL1 common.PL0 common.PT0 common.PT1 0 confmem ctree cvmao cvnew cvnumtrans dbase.mgr dect.mtcl dis25 dis25.SYM dyn_id eqtmove.tbl etc feml fichges gd.mtcl gdump gdump.mtcl getnoeversion hwlist.sh incid_FR0.dcc incid_GEA.dcc incid_US0.dcc incidents.t xt index infocollect ipdomains.mtcl iplink iplink.SYM ipterms.mtcl lisX25 mao.mtcl maoagent maoagent.SYM motortracenetw_incid.mtcl object.cry object.cry.Z objects.DE0 objects.DE1 objects.DE2 objects.EN0 objects.ES0 objects.FR0 objects.GEA objects.IT0 objects.NL1 objects.PT0 objects.PT1 0 objects.dct objects.dct.Z objerr.DE0 objerr.DE1 objerr.DE2 objerr.EN0 objerr.ES0 objerr.FR0 objerr.GEA objerr.IT0 objerr.NL1 objerr.PT0 objerr.PT1 0 objerrh.DE0 objerrh.DE1 objerrh.DE2 objerrh.EN0 objerrh.ES0 objerrh.FR0 objerrh.GEA objerrh.IT0 objerrh.NL1 objerrh.PT0 objerrh.PT1 0 ops ops.mtcl pbmd pbmd.SYM pcs_logs remotesets.mtcl ressources.mtcl rlis rlis EA rlisX25 rma.txt sfx-infocollect.sh sip.mtcl sipmotor sipmotor.SYM sipregister sp_admin spadmin spadmin.dct sprecover sqlsrv sysinfo term.mtcl tftpd tool.SYM translate translate.tbl trunks.mtcl tuner twin twin_extra update.sh varlog version.mtcl voip.mtcl x25.mtcl========================================================Other binaries delivered in j1.410.36mg_appli_46.05 intip_16.04 noemipt8_r100_2.2.24 ioip_4.09 bootintip_6.11 mg3_3.37 intip3_3.37 noeip_4.31.20 noeipg_4.31.20========================================================WARNING: If you use encryption feature you have to install the patch sj1.410.36The Sj1.410.36 is available on BPWS with s pecial requestBinaries delivered in sj1.410.36noeipg_4.36.20, noeip_4.36.20, mg_appli_46.05, mg3_3.37, intip3_3.37, sm_3.3.06 (named 3.3.06 in mgr), lnxswinst_2.64.0WARNING : to connect from the CS to the active MSM, mandatory use option -b to indicate physical interface of CS: (example) :telnet -b '@_IP_Physical_CS' '@_IP_MSM'Please, send me an email after installing the version on site to have a feed-back.Best regards.M.Grosgeorge====================================================== Release Name : patch_j1.410.36Delivery date : Fri Sep 2 20:26:36 IST 2011======================================================crms00181557 internal NGP : Format of backtrace is bad.crms00216143 internal Notification icon won't be deleted after executing handset phone test on Ascom 8128. crms00327893 crms00248316 internal NOE Encapsulation in SIP : Release of registration neqt in Call control instead of Call Handlingcrms00248316 internal NOE Encapsulation in SIP : Release of registration neqt in Call control instead of Call Handlingcrms00257240 internal SOSM: No answer message for forwarded set during multi party conference.crms00259399 internal Defence case: manage a timer when sending UPDATE to sip. This in case of no response and to exit the waitevt.crms00264548 internal SOSM: Extra Answer message when forwarded set gets external call.crms00266826 internal SOSM: Wrong disconnection cause for conference master when it calls a busy external set. crms00267867 internal SOSM: Missing Service Message and Invalid Calling No for Immediate Forward over R1.5 Trunkcrms00268285 internal SOSM: Extra SOSM messages are generated in Call forwarding, when the destination set does not attend the call and call overflows to attendantcrms00271896 customer incoming H323 call NOK when 1st access declared in INTIPA board without daughter board is busycrms00272202 internal OXE: bad call flow when OXE set programs a forward to ICM set (No visible effect) crms00277339 internal Call gets disconnected when we manage multiple entries of a set in the CRG listcrms00277603 customer INTIPB standby can't connect on PCS / 1-114205613crms00283828 internal Ext . call transfer on ringing to VHE : No ring back tonecrms00286800 internal PER 358 : Attendant should display CRG group name when call is forwarded to CRG crms00289689 internal PER 358:Wrong call flow to a busy CRG set.crms00290895 customer Randomly permanent GD reboot with backtracecrms00293500 customer No Audio When the GSM calls are made from Remote nodecrms00293694 customer shelf not recovering after power outage IOIP INTOFcrms00294515 internal NOEinSIP, SIP-TLS, if last work mode is NOEinSIP (bypass environment), turn to full environemt, phone can't work at SIP-TLS modecrms00294920 internal SOSM: Wrong called number for monitored trunk during transfer scenariocrms00295817 customer One way speech sometimescrms00298826 customer Reboot GD with backtrace during T38 calls between two GD through MPLS link. crms00299180 customer Users cannot receive the complete voice messages when they retrive the voice mail / 1-117020021.crms00299944 internal Missed out part of solution for the issue 175114.crms00300015 internal SOSM: No messages for transfer scenario in mono-line set for second call and MCLs are blockedcrms00300023 internal SOSM: Command is executed when wrong values are given. MCL blockedcrms00301516 internal NOE Reject call is NOT OK when NOE set is associated with CRG.crms00301885 customer while doing a reset on a virtual GPA GD is going down for rebootalso.//1-117929921.crms00304838 customer T.38 fax server behind H323 trunk cannot fax to specific numbercrms00306911 internal Incoming call via SIP Trunk ISDN TLS to OXE local IPT Immediate forwarded to MEVO : IPT rung (?) & no transfer to mevocrms00310516 internal Sets' display aren't updated with current ringing number when calling a CRG through ABC-F (number of 1rt set stays) (bad ABC-F messages?)crms00310717 internal SOSM : Called number is filled wrong for the sets during a forward scenario via R1.5 trunk. crms00310726 internal SOSM : Call retrieve message is wrong after a broker call.crms00310792 internal BB : After device switching from BB to VHE, BB leg is not releasedcrms00312026 internal SOSM: Multiparty conference feature is working with errors.crms00312102 internal NOE in SIP TLS: Attendant 4059 IP with "noe in sip" set is blockedcrms00314073 internal BB4 fallback call to OP is failingcrms00316619 internal IPLINK counter display on one octet and not 2crms00316965 internal mgr -l FR0 help : text in English instead in Frenchcrms00317050 internal OXE J1:- NOE-SIP licenses, OPS files not updated on the spadmin whencs-mode=NOE-SIP.crms00318347 internal [ICER1.0] [OXE] : no ring back tone for 003XXXX external outgoing call - OK for 006xxxxxxxx callcrms00318860 internal Wrong value in the "Reason" parameter of the SIP History-Info Headercrms00319206 internal ICE 005.021, MyIC 5.0.022.005: Nomadic user can't hear sound under outgoing call crms00319226 internal OXE NGP I1:No backtrace uploaded on INTIP3crms00319371 internal PER46 & Network encryption: scrambled voice after transfer and overflow to voice mail. crms00319375 internal PER46 Call is cut after transfer in network and overflow on no reply to CRGcrms00319697 internal code review for Timezone_formatcrms00324203 internal New requirement: An attendant (Local/Network) call should be disconnected when CRG list is empty.crms00324500 customer BETA R10.0: mgr option "NAT_Support_for_FAX_T38" not accessable with dicocrms00324744 internal Wrong Behaviour seen after implementation of crms00324693 for network enquiry call crms00325053 customer No subsequent requests after switchover due to bad socket usecrms00325492 customer No voice and call on IMS loop scenariocrms00326401 internal ICE: OXE phones answer multiparty call in a mode with no voicecrms00327581 internal NGP GD3 : mark for code robustness modificationscrms00327877 internal OXE J2:SIP Diversion Header: Reason parameter is missing for FWD on busy/FWD on no answer via SIP ISDN trunk.crms00328026 internal Infocollect tool request for version 4.2crms00328188 internal Network Encryption - Noise while SEPLOS is supervised by network set.crms00328191 internal Network encryption - No ringback tone in SEPLOS set while transferred on ringing. crms00276519 crms00328264 internal Network encryption: STA RT_SRTP message (with keys) is not traced to be reported in J1 with few modifications because of TLScrms00328264 internal Network encryption : START_SRTP message (with keys) is not traced to be reported in J1 with few modifications because of TLScrms00328393 customer Database errors when upgrade from R8.0.1 to Release 9.1//1-123319303//crms00328796 internal PER46 wrong voice mail reached after transfer from A VST automated attendantcrms00329004 internal Regression: Not possible to make enquiry call.crms00331030 crms00329004 internal Regression: Not possible to make enquiry call.crms00329579 internal NOE Encapsulation in SIP : Keepalive mechanism modification (from CRLF to OPTIONS)crms00329919 internal PER 358:call gets disconnected with backtrace when SEPLOS transfer a call to CRG crms00329932 customer CUG not working if GFU index is different to 0crms00330739 internal [OXE] [HOTEL] Long calls with Bluetooth KO on some terminals (rather a session timer problem)crms00331007 internal DB Translation for J1.410.36crms00332953 internal Backtrace [Kb_Interro:Do_i_have_CRG_Set_on_HOLD] occurs for CRG Network/Trunk call.crms00333047 internal OXE J1:- NOE EE Sets are not coming to Service in NOE-SIP Modecrms00333668 internal PER 358:Removal of RSI-CRG interaction RAs crms00283683 and crms00313784crms00334756 internal PER 358:Call gets disconnected with backtrace [CHECK:how_many_free_lines] when manage Analog sets in CRG listcrms00056712 XTSce86891 internal Malicious call/trace-Softkey not displayingcrms00116976 internal No error thrown when adding a user associated to IP 4059 is added in hunt groupcrms00138751 internal No cause for error 6 in incident 624 while using incinfo tool & wrong translationcrms00184723 internal OXE:NGP: tool: "Compvisu sys" gives information about the feature that are restricted in NGPcrms00200151 customer Call not established and incident 4104, 4108, 287crms00202552 internal Substitution is not working after transfer via link.crms00205829 internal Can not retrieve external T2 call when call is established in DTMF mode.crms00210296 customer impossible to protect an INTIPA after "eqtmove" migration (CPU to AS)crms00210701 internal Audio Routing on Ascom Setscrms00217684 internal Audio Routing on Ascom sets - Key Ownership for Loudspeaker and Mutecrms00220286 internal oxe response the "?" to ASCOM MIPT when the MIPT press the "MUTE" key in idle mode.crms00221698 internal NOE: Display not updated after a call in a noe supervisor setcrms00223740 internal OXE J1-NRT : Attendant is in Conversation but Set is OnHold with Hold Tone when Attendant press OnHold Option and Retrieves itcrms00223862 customer No ringback on DECT set when calling to SIP external carrier //1-104287131// crms00224155 customer "Tractor" noise if CCD call is routed to multiple nodescrms00226971 internal Malicious option is missing when attend the supervision call.crms00229439 internal nomadic IP: DTMF not working in network when call SIP ICS voice mailcrms00231352 internal Set comes into conversation when hold softkey is pressed in Attendantcrms00231515 internal Attendant call makes unhold bad behaviourcrms00235571 internal OXE J1 : Backtrace occurred while doing robustness testing in OXEcrms00236004 internal Incoming call from operator by local T2 to 4008 Seplos: no sound on 4008 (randomly seen, no PB with 4018 Seplos)crms00238668 internal French translation not done for parameters- Burst size and Burst Delaycrms00239773 customer [BTIP] 3821: Polycom (SIP Extension mode) - Too many renegotiationscrms00242014 customer help in 4760 not translated in Frenchcrms00242015 customer character not displayed correctly on 4760 due to OXEcrms00244368 internal License in not working on the virtual machine OXE in J1.400.2.bcrms00245942 customer Stop rtp is not sent by the CPU to IPDSPcrms00249141 customer After creating ABCF IP trunk groups, the incident 2879 occurs veryoften//1-110123891//crms00258156 internal Sip Trunking: Diversion headercrms00262212 internal NRA-J1: CSTA:Called Device is missing in Delivered & Established Events.crms00264545 internal Problem in cryptview command when INTIPA is connected to MSM boxcrms00265970 customer After the trace command "tuner +at,neqt" system crash and reboot if the neqt length entered is more than 10 digits_//1-111615113//crms00266482 internal wrong information in cfnstat tool for A BCF-IP trunk callscrms00268422 customer RSI : blind transfer from attendant to agent (in a ABCF network) via RSI => no wrapup - no pausecrms00269462 internal Regression: Local call disconnects with backtracecrms00270058 customer Attendant blind transfer on a private ISDN call over A BCF linkdisconnects_//1-112406693crms00276519 internal Network encryption : STA RT_SRTP message (with keys) is not tracedcrms00277476 customer UPMC: System Doc R9.1 and mgr online help do not match for 'Routing on Immediat Forward'crms00277901 customer Issue with ring back tone on analog set_//1-113838491.crms00283091 customer Wrong display when consulting unanswered call list on Reflex set when called from NOE set with Cyrillic characters configured in UTF-8.//1-114682701.crms00283486 internal Display problem in A BCFIPTRUNKcrms00285219 customer dect fall done with lot of reset network 1367crms00285930 customer Agent is logged in, calls in queue not offered when using Prefix callpark.crms00287199 customer CSTA returning unknown characters when picking a call when the ACD line is ringingcrms00287578 internal French Translation not done for new parameters in IP and Fax parameterscrms00289630 customer No voice when making a blind transfer thru ABCF / 1-116038201crms00289899 internal French text translation for PER1440crms00290898 internal MGR - French translation missing for "Anti saturation device disable".crms00291646 customer callstate is wrong if TakeCall on a call from sip setcrms00294480 internal Alignment disturbed in compvisu sys in I1.605.25 and H1.301.50crms00294832 internal French translation not done for new parameters in SIPcrms00295066 internal Able to send text mail while ringing in networkcrms00295717 customer No dial tone on sets connected to Z 24-2 board.[ DSP board blocked after migration from R7.1 to R9.0 ]crms00295838 customer When we call the busy agent set, the conversation between the agent and external call get disconnected._//1-117169311.crms00297044 customer Many issues on IPT 4018 after upgrade to h1.301.50. Incident 0248 and backtrace "serv=0 --> depact" seen //1-117495901.crms00325422 crms00298547 internal OXE J1: Development PRS traces are observed in Runtel log in the patch J1.410.23.fcrms00298547 internal OXE J1: Development PRS traces are observed in Runtel log in the patch J1.410.23.f crms00299112 customer no fax carrier frequencies from SIP Fax Server for incoming T2 callcrms00299197 customer Unable to import wav-files as an announcement for Ubiquity Assistant-sets using Eva tool.//1-117149041//crms00299502 customer Unable to call external forwarded set if the associated calling set isOOS//1-117825401//crms00299727 customer Truncated calling number in TAXA files if A UTO DTMF is enabled in SIP I SDN trunk groups.//1-118093931.crms00299813 customer RSI overflow_CCD Backup forwarding to VM doesn't workcrms00300414 customer Diverting information is wrong when the call overflows to QSIG GF if attendant transfers //1-117783031//crms00300870 customer Unable to make/receive call after upgrading to patch 48 (CAC issue)crms00301601 internal Help menu is not translated for accounting parameters in Frenchcrms00301968 customer SIP forkinf call not work when more than 2 clientscrms00301981 customer Incident 2656 generated while deleting the IP touch user / 1-118568963.crms00302357 customer Blocked dialog in the DECT set screen in case of dial by namecrms00302757 customer Randomly UA Agent are not reachable / 1-118424753.crms00303034 customer RSI Global Callid changed during RSI forwardingcrms00303207 internal [SBD-OBS] Bad behaviour on call forward to NRIP servicecrms00304222 customer Master conference and pro-acdcrms00304731 customer VA D - New system timer to secure the transfer of outbound calls in case of no voice detectioncrms00304913 customer GA doesn't go in service if shelf number is equal or higher then 3 digits.crms00305268 customer MLA : "Reject incoming call on last line" does not work on UA virtual sets crms00305551 customer CLI is not sent to remote extension when calling through CAS trunk /1-118075525.crms00305729 internal Call overflow for out of service SIP sets (Air France) feature did not work with SIP device Thomson sets.crms00306202 customer MEET ME CONFERENCE ISSUES//1-119274791.crms00306731 customer The Mobile IP Touch is no forwarding the calls externally when there are out of range//1-118704241.crms00306940 customer If IPT is out of service, call does not overflow to associated set / 1-119503801. crms00306949 customer Call released during routing scenariocrms00308704 customer Issue with getnoeversioncrms00309090 customer Unexpected display on NOE set when using DISAcrms00309270 customer Problems with the CCivr channels stucked in OTCCPE environmentcrms00309783 customer unable to make external call from multiline DECT sets by accessing the pin number stored in the personal directory//1-119805091.crms00310016 customer When Deleting Pri MLA Key, Database Corruption created if Sec MLA's are not deleted 1st.crms00310066 customer CAC value not decreasing when call is released//1-119609821.crms00310121 customer REFER with Abbreviated number on Refer-to / 1-119735221.crms00311539 customer Unable to receive ringback tone on UA & IP sets using a QSIG BC when OXE connected with Cisco call manager / 1-119713995.crms00311663 customer QSIG: Call releasecrms00311926 customer CSTA : Enhancement of the Send DTMF CSTA servicecrms00312665 internal Oxe J1: NoeSIP set comes up only after a hard reset during set type change identification crms00314473 customer CSTA calling information not present if secret identity activatedcrms00314998 internal Reg: Call by name display order not okcrms00315746 internal Regression: Missing CSTA events for a set managed in the entity while calling entity prefix(crms00155964-delivered in I1.605.13 is not working)crms00315785 internal Display Problem in A BCFIP Trunkcrms00315842 internal Regression: Set shows Secret identity when calling to pilot if consult call mode on multi line + Falsecrms00316103 customer DTMF End to End Dialling not working if Key 33 is managed with SetSupervision and NoCall=Yescrms00316443 internal Agent cannot re-park the ACD-call while in its ringing state (only for NOE sets)crms00316758 customer SIP incoming call fails OXE rejects invite with timer required extensioncrms00316802 internal SEPLOS: Call disconnected with Backtracecrms00317206 internal OXE I1:Auto DTMF on Incoming Call is not working in ABCF IP/QSIG trunkcrms00318662 customer H323 incoming calls blocked with backtrace "sui_val_ra_invalide"crms00319122 customer No ringback tone when made a call to OXO from Avaya through OXE//1-117222608//crms00319272 internal REG: while doing intrusion on iplink call by local TDM set no voice communication and existing sets also disconnected with backtracescrms00324387 internal Regression: All the calls are disconnected when making enquiry call(link) from a new line while Consult call mode on multiline + TRUEcrms00325057 customer [beta-LSKN] : no supervision after switchover if registration is activatedcrms00328402 internal Oxe J1: Emergency Call to Attendant- Feature behaviour is NOK with 4068IP Attendant: Regressioncrms00329816 internal lab : TLS link can't established at start-up of TLS ServerDuplicatescrms00291557 crms00291557 internal OXE / ICE interworking : 2 steps transfer between OXE (non SIP), ESS and OXE (SIP Device) failedcrms00316503 crms00294515 internal NOEinSIP,SIP-TLS, if last work mode is NOEinSIP (bypass environment), turn to full environment, phone can't work at SIP-TLS modecrms00314317 crms00294515 internal NOEinSIP,SIP-TLS, if last work mode is NOEinSIP (bypass environment), turn to full environment, phone can't work at SIP-TLS modecrms00266104 crms00294920 internal SOSM:Wrong called number for monitored trunk during transfer scenariocrms00319387 crms00310726 internal SOSM : Call retrieve message is wrong after a broker call.crms00329990 crms00310792 internal BB : After device switching from BB to VHE, BB leg is not released crms00318173 crms00310792 customer BB : After device switching from BB to VHE, BB leg is not releasedcrms00328445 crms00310792 internal BB : After device switching from BB to VHE, BB leg is not released crms00309047 crms00312102 internal NOE in SIP TLS: Attendant 4059 IP with "noe in sip" set is blocked crms00314593 crms00312102 internal NOE in SIP TLS: Attendant 4059 IP with "noe in sip" set is blocked crms00309377 crms00312102 internal NOE in SIP TLS: Attendant 4059 IP with "noe in sip" set is blocked crms00291557 crms00314073 internal BB4 fallback call to OP is failingcrms00329296 crms00314073 internal BB4 fallback call to OP is failingcrms00325020 crms00318347 internal [ICER1.0] [OXE] : no ring back tone for 003XXXX external outgoing call - OK for 0 06xxxxxxxx callcrms00325714 crms00318347 internal [ICER1.0] [OXE] : no ring back tone for 003XXXX external outgoing call - OK for 0 06xxxxxxxx callcrms00328463 crms00318347 customer [ICER1.0] [OXE] : no ring back tone for 003XXXX external outgoing call - OK for 0 06xxxxxxxx callcrms00326836 crms00319206 internal ICE 005.021, MyIC 5.0.022.005: Nomadic user can't hear sound under outgoing callcrms00326919 crms00324500 internal BETA R10.0: mgr option "NAT_Support_for_FAX_T38" not accessible with dicocrms00314123 crms00325057 customer no supervision after switchover if registration is activated crms00331206 crms00326401 internal ICE: OXE phones answer multiparty call in a mode with no voicecrms00328344 crms00326401 internal ICE: OXE phones answer multiparty call in a mode with no voicecrms00334654 crms00326401 internal ICE: OXE phones answer multiparty call in a mode with no voicecrms00330561 crms00326401 internal ICE: OXE phones answer multiparty call in a mode with no voicecrms00329046 crms00326401 internal ICE: OXE phones answer multiparty call in a mode with no voicecrms00329686 crms00326401 internal ICE: OXE phones answer multiparty call in a mode with no voicecrms00332832 crms00330739 customer [OXE] [HOTEL] Long calls with Bluetooth KO on some terminals (rather a session timer problem)New binariesintip3_3.37ioip_4.09noemipt8_r100_2.2.24mg3_3.37noeipg_4.31.20mg_appli_46.05crms00299944 crms00290895 crms00247643 crms00298826 crms00293694noeip_4.31.20bootintip_6.11intip_16.04crms00299944 crms00271896 crms00290895 crms00298826 crms00277603 crms00293694==================================================REMINDER :======================================================Release Name : patch_j1.410.35Delivery date : Mon Aug 1 14:39:02 IST 2011======================================================crms00207914 customer The feature C ACoverrun doesn't workcrms00274936 internal One way calls and crossed lines - eZ32crms00280273 customer backtrace terminates ou tgoing calls from TA-S0crms00288490 internal Lot of incidents 2198 on ABCF-IP tru nk Group "PH: ABCF_IP sig link, error in synch frame"crms00292052 internal OXE J1:Arrow mark displayed in noe set when immediately calls another noe after external callcrms00294613 internal PER 358:Display does not change on called set(external/Network) when attendant does transfer (CRG rotation happens)crms00301884 customer Can’t Migrate from g1503.31 to i1605crms00317317 crms00302379 internal TUI LS OXE : callback via voicemail to user forwarded to voicemail : sender is unknown, voicemail number is given as sendercrms00304844 internal Apache server and Web tools featurecrms00306176 internal NOE in SIP TLS : incident de securite 441 (& sometimes FR EETEL) at the end of the init (IN SERVICE) of IPT setcrms00310550 internal OXE J1: NOE-SIP Traffic: Lot of backtraces during traffic with 200 noe-sip userscrms00313471 internal 4059EE Overflow to LDAP not working MAO partcrms00314447 internal NRA-J1:CC D:Backtrace occu rs for RSI blind transfer (etat_post).crms00315722 customer cannot get C PU_id on blade server HS22crms00315862 internal CallBack: Interop: Call completion on OXE busy caller rand omly failscrms00316839 internal Network Encryption: code optimisation direct call from IP to OTUC -noise via transit nodescrms00316878 internal CSTA events missing in case monitored user is reached by entity call prefix.crms00317653 internal ICE 005.010, ACS: MyTWK calls are terminated if contact forwards his calls to another phonecrms00317748 internal ICE: when a call is sent from ice to oxe, the call is not attached to an external gatewaycrms00317749 internal VHE :transfer on ringing an external call to oxe set immediate forward to Voice mail : call failedcrms00318106 internal PER 358: Wrong display on called set(network) when attendant does transfer on ringing to a CRG set which has forward on no answercrms00318328 internal SIP external gateway HS when using FQDN in outb ound proxycrms00319072 internal OXE Session Timer: In 200 OK, OXE pu t refresher=uas in every casescrms00319136 internal Oxe J1: Memory Leaks in SIP Stack and SIP motorcrms00321942 internal NOE IN SIP TLS: lot of SIPM backtrace at start of node 7 and IpTouch EE are "Ou tOfService"crms00322193 internal PER 46 C all is cu t when an attendant transfers an external call to a set immediately forwarded to CRGcrms00296160 crms00324263 internal sip replication: some subscriptions succeed in sipmotor backtracescrms00324263 internal sip replication: some subscriptions succeed in sipmotor backtracescrms00324652 internal J1.410.34.d : Calls are disconnected with backtrace when multi-line set makes enquiry call to Analog set and tries to navigate between the screens.crms00324693 internal COS dependency to be removed from UPMC46 Voice mail Overflowcrms00325042 internal Impossible to manage "100rel for incoming call" parametercrms00325762 internal REGRESSION-Exceptions in RUNTEL-2:4352=Initrem : Instance exception, table SIPEXTGW instance 0 infos -1 -1 -1crms00325990 internal Regression: Du plicate Entry for IP Agent/supervisor sets during creation in *.pcf file.(crms240353)crms00326810 internal Associated call is disconnected with backtracecrms00328415 internal OXE J1:- Unable to C reate SIP External Gateway through mgrcrms00157882 internal Secret Identity SoftKey is not working when dial the Private Substitution Prefix.crms00166843 internal I1: Table Error while creating Empty database for Austria countrycrms00172751 internal NGP : OXE DHC P Server C onfiguration files list include RGD but not INTIP3 or GD3 path.crms00181301 customer tru nkg rou p counter >R1% issuecrms00187698 internal Loss of call on C PU switchovercrms00192229 internal English translation not done rstcpl tool.crms00193457 customer 4 seconds of silence in first 10 seconds of IP call.crms00194443 internal default ipview.cfg corrupt - field 6 not displayedcrms00200336 internal Updating required in C ompvisu sys toolcrms00200594 internal Display not OK after enabling callback through DPNSS in secondary MLA set.crms00201220 internal external gateway redundancy : unexpected INVITE retransmissioncrms00201491 customer PCS status incoherent on cpu during network failure //SR 1-102457601crms00202586 customer No information on websoftphone when IP touch is made ou t of service.crms00203637 internal SIP Trunking: Supported header from SIP ISDN TG should not contains replaces valuecrms00203709 customer Sip Device Call Back issue when Sip Device Country localisation is different that the Syst em One.crms00205020 customer Roaming issue between R7.1 and R9.0, Applicative-Error-Backtrace, PC=0x0934e0e3:154460387, serv=2 --> Kb_Interrocrms00211993 customer bad "rollback" on remanent if creation of hyb rid acces withou t sig refused as no more fictiv trunkscrms00215448 customer after resetting intip board, trunks stay Out of Service on the Stdby C PUcrms00215631 internal User in mgr disappeared after bad management in the external voicemail nu mber//1-105436824crms00217712 internal NR T NG P : C ompressor value is wrong for GD3 while converting GD to GD3 .crms00217728 internal OXE J1 :Incoming call indication with led glowing when there is a single call which is on holdcrms00219829 customer Web tools can not show all trunks in when click for display tru nk inTru nk Group //1-106054541crms00220535 customer Unable to send DTMF from IPTouch to Audio codes using programmable key, no issues with TDM set//1-105704666//crms00222693 customer CSTA Failed scenario interworking B/S feature and RSI CSTA routing.crms00225060 internal OXE J1-NR T : 4068 Attendant still displays "Set is Free" withou t any option and Set get Hanged through Link crms00226037 customer No RB T when 4059 blind transfer a call to SIP devicecrms00226572 internal Take call softkey is missing and double tabs occur while releasing the first callcrms00226767 customer GD reset due to SIG_L: Enqueue(30) full queue similar to crms00222236//1-107165171//crms00228514 customer VG Guide Start B oolean not taken in account for IPTouchcrms00228699 customer Problems with intercom server when Loop Station UA link disconnected and connected quicklycrms00229525 internal Reserved by Attendant tab reveals wrong informationcrms00233001 internal Releasing the first call after attendant intrusion leads to an excess tab and incorrect displaycrms00234540 customer Call disconnect via H323 if the end user is GSM who is in roaming.//1-107457993//crms00234807 internal French language display shows English for Non Monitor Conferencecrms00235507 internal On hold display with retrieve call softkey appears when sets are in conversationcrms00236560 customer Backtrace and task in loop when calling a dect set ou t of servicecrms00237017 internal NO R TP direct after su pervised transfer between carrier and S T2030crms00237207 customer Display appel non repondu in network in UTF8crms00237493 internal OXE J1:Backtrace occurs when SIP request URI info length is greater than 30crms00238851 customer NO RB T for broker call on 4068 attendant through H323crms00239001 internal ICE/OXE : Transfer on conversation: audio discontinued with topo O-I-I (call_identity is limited to 4 digits) crms00239632 internal SIP/TLS: reset of standby C PU with many simultaneous commcrms00239692 customer Exception 0x0832ab78 error after 9.1 upgradecrms00239937 customer Polycom ou tgoing call impossible if PIN code neededcrms00240244 internal OXE J1-NR T : NO Information ab out SIP Device in 4068 Attendant when it makes Enquiry to SIP Device crms00240353 internal OXE:NR A-J1:New Entry for IP Agent/supervisor sets during creation in *.pcf file.crms00241661 internal PB when access from ICM multi device to 4645 mevo remote to declaration nodecrms00241819 internal sip duplication: data invalid on standby cpu。
npm学习（九）之README.md文件
如何更新 ReadMe文件
除非发布包的新版本，否则不会更新站点上显示的自述文件，因此需要运行npm version patch和npm publish来更新站点上显.md文件
包括文档 (readme.md)
npm建议您包含一个readme文件来记录您的包。自述文件必须有文件名readme.md。文件扩展名.md表示该文件是一个标记(markdown)文 件。当有人发现您的包时，该文件将出现在npm网站上。在开始之前，请查看一些包页面，了解可以添加到readme文件中的信息，并了解 为什么这一点如此重要。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
license的feature在list.txt中，可以自行添加。
sedatools\lib\rpc.sflmserverd\8.0.3.R\x86-nt
替换原来的文件。
3、在快捷方式中运行Start Server
确保下面的系统服务启动：
Standard Floating License Manager (SFLMSERVERD)
会要你设密码，随便写一个就行。
4、通过IE http://127.0.0.1:3162进入SFLM设置,通过SFLM在线获取该电脑的SFLM_ID。
可能得到的格式如下：0SSMID12345678，也可能是比这个复杂多的形式
5、修改Silvaco.lic中下面的一行，替换为4中你申请到的SFLM_ID。
LM_HOSTIDS XXX
6、拷贝修改后的Silvaco.lic到下面路径：
sedatools\etc\license
7、通过SFLM Access，正常选择安装Silvaco.lic。
8、检查license状态，所有license现在应该正常可用了。
9、设置局域网其他用户到该PC的ip地址获取license。
license安装步骤： 1、安装TCAD 2007.04，如果作为LICENSE服务器，请选择安装SFLM server。然后在系统服务里停止：
Standard Floating License Manager (SFLMSERVERD)，如果有这个服务的话。
2、把rpc.sflmserverd.exe拷贝到下面的路径（我亲自破解的哦）：