MortScriptV4.2用户手册(中文版)
AutoDock 4.2 官方使用教程中文版(Bioms小组翻译)AutoDock4.2
兼容性：我们确保在 AutoDock4.0 中可用的对接文件同样可在 AutoDock4.2 中使用。
软件技术支持 AutoDock 是免费软件，但是由于支持经费有限，我们不能对安装和使用中出现的具体问题进行快速的响应。虽 然这里有一份 AutoDock 使用教程，但是同样需要用户具有一些 Unix 的基本知识。如果你还需要一些帮助的 话： 1. 找你当地懂 Unix 的人帮忙 2. 登录 AutoDock 的 FAQ 网站： /faqs-help 3. 如果你不能找到你问题的答案，把你的问题提交到 AutoDock 的 List (ADL)或者 AutoDock 的论坛上。那里有 很多计算化学软件使用高手和一些可能知道你问题答案的 AutoDock 的用户。你可以在下列网址找到 ADL 的更 多信息: /mailman/listinfo/autodock AutoDock 的论坛网站为：/forum 4. 如果以上的方法你尝试了都不行，请给 goodsell@ 发邮件询问 AutoGrid 或者 AutoDock 的相关问题，或 者给 rhuey@ 发邮件询问 AutoDockTools 的相关问题。
扩展的原子类型：系统添加了卤素原子和常见的金属离子类型，并为其生成了对应的参数文件。 去溶剂化模型：去溶剂化模型现已支持系统所有的原子类型，而不像以前只支持碳原子。因此，AutoGrid 已不 再使用 constant 函数，因为极性原子的去溶剂化已经可以处理。新的模型需要用 AutoGrid 计算生成一个新的 map 文件，这一文件包含了基于电荷的去溶剂化信息。
未结合态：有一些模型可用于估算未结合态体系的能量，包含了一个扩展的模型和一个将未结合态作为类似于 蛋白结合态处理的模型。
AutoDock4.2 针对于 Autodock4.0 的更新：
MorphMagic中文使用手册
New Wire
平面 (Guide Plane) 定義對話框
Z
New Shape
X
Y
Fit Contour (保持曲線輪廓邊界線,其設變曲面依新輪廓曲線,保持順滑建立曲面 )
New Contour
Old Contour
Old Faces
曲面 舊曲線 新曲線 緩衝區 邊界線
New Faces
Top Gauge (在保持邊牆厚度情況下,置換鞋模3D模口線)
Parting Line Fix Boundary
拔模方向 (Draft Direction) 定義對話框
兩點定義方向
By Control Points (指定曲面設變造型線,其曲面依新的造型線自動設變)
物件 舊曲線 新曲線 邊界線 平面 緩衝區 1 緩衝區 2
Old Styling Surface
Pattern Project To Faces
物件 投影曲面 包覆曲面 邊界線
By Spin
Wrap To Faces
此範例選擇的花紋(Pattern)為3D 花紋
Wrap Surface
功功能能表表 Wire (複合線)
Edge (曲線)
曲線連結
分解 (Wire分解出Edge) 方向 邊界 複合曲線轉換單一曲線
Reverse (曲線方向設定)
選擇曲線
重設 轉向
取消
Join Wire (連結複合曲線)
選擇曲線 公差設定
析出 (析出曲面邊界曲線) 合併 (合併曲線) 修剪
功功能能表表 Assembly (組合)
物件 舊模口線(左) 舊模口線(左) 新模口線(左) 新模口線(右)
New Gauge L.H New Gauge R.H
德马格中文操作说明书
液压顶出 后退 / 前进
气阀 1-4 打开
中子 抽芯 / 进芯
自动安全门 打开 / 关闭
Rotary table index bolt move in / move out
模厚调整 增加 / 减小
旋转模板 逆时针 /顺时针
提示 “模厚调整”按钮只针对曲轴式机床。“自动安全门”和“气阀 1－4”按钮只有当这些功 能配置以后才起作用。“Rotary table latches”, Rotary table index bolt” and “旋转模板”应 用于带转转模板的多色注塑 。
Sfu服EnRc务tVio页InC面Egr功oup 能组
Afu报LnAc警tRio功Mn能Sgr组oup
Fig. 2: 功能选择键
1.2 手动功能键
在手动和点动模式下可通过下面的按钮（见Fig. 3 和 Fig. 4）进行相应的操作。 Fig. 3: 手动模具装置功能
模具 打开 / 闭合
Rotary table latches move in / move out
4.4
帮助功能键和专家系统 .......................................................................................................19
5
频幕 ..........................................................................................................20
Pfu程RnOc序tGio功Rn能AgrM组oSup
Process 过Pfu程RnOc控tCio制EnS功gSr能oCu组pONTROL
环球插件机中文编程资料2版
优化产品并安排分配头 显示插件路径位置（可选）为单板创建新产品达到目标给定板，学员将： 1. 命名产品并创建单板 2. 选择工装板夹具（单体机）. 3. 向板上放元件4. 定义BEC 校核位置（可选）5. 为元件安排分配头（有排序部分的机器）.6. 优化产品并显示插件路径.7. 保存产品并拷贝到磁盘上参考手册IM-UPS 参考手册在这个模块，将创建程序并告诉机器，在板上何处、怎样、何时放置 元件，创建的程序作为产品来参考。
介绍产品创建步骤下图表明如何用单板来创建单板产品命名产品并创建板介绍必须为机器编程以使元件在希望的位置插入，在 IM-UPS 中，此程序被 参考作为产品。
对于那些熟悉 PPU 编程的人来说，一个产品就象旧的.PUT 、.MAG 、以及.ERV 程序的组合。
将会看到，新的编程方法 IM-UPS 与旧的编程方法PPU 有很多区别，在进行这个模块时将提到。
创建板在创建产品之前，首先必须定义为其写程序的板的尺寸，这是 IM-UPS与PPU 的一个主要区别。
因为IM-UPS 是图形界面，所以首先必须定义一个 图形区域”来与计算机相联系。
例如，如果想在3” x3的板上插入元件，就必须向计算机输 入这一数据，负责计算机将不知道这些元件应该去哪里。
一个好的分析 方法是，当你想画一个上面有元件的完整的 PCB 时，你首先需要有一页 纸。
产品编辑器中的板就是你想画元件的那页纸。
注意：贯穿整个产品编辑器，可以用F4功能键返回前一动作，这非常有用，因为我们都会 犯错误！1. 我们将手动创建板，PC 板是方形的（实际上是正方形）。
在IM-UPS 主屏上，点击 Product Editor Icon .产品编辑器图标练习： 创建板最新资料推荐1从菜单栏选择Board （板），然后选择Create/Edit.（创建/编辑）2. 在图框内输入板的长度和宽度，长度 （千分之一英寸单位）测量沿着 机器的X 轴，宽度沿着丫轴。
Virtual Iron Version 4.2 软件发布说明书
Virtual Iron® Version 4.2Virtual Iron® Software Release Notes ®Copyright (c) 2008 Virtual Iron Software, Inc.000012808R1This information is the intellectual property of Virtual Iron Software, Inc. This content is for your personal use only, subject to Terms and Conditions. No redistribution allowed.Contents Enterprise Edition Upgrade Instructions (3)Single Server Edition Upgrade Instructions (3)New in this Release (4)Fixed in this Release (5)Open Issues in this Release (6)Product Documentation (14)Contacting Virtual Iron Support (14)E NTERPRISE E DITION U PGRADE I NSTRUCTIONSIf you are running an earlier version of Virtual Iron® EE or XEE, use this link and fol-low the instructions to upgrade to the current version of the product. Install the newVS Tools onto each of your Virtual Servers./services/virtual-iron-42-upgrade.cfmS INGLE S ERVER E DITION U PGRADE I NSTRUCTIONSIf you are running an earlier version of Virtual Iron® SSE, use this link and followthe instructions to upgrade to the current version of the product./services/virtual-iron-ss-42-upgrade.cfmRelease 4.2 includes the following major enhancements:•VS Tools support for the following additional operating systems: - SUSE Linux Enterprise Server 10 32-bit and 64-bit- Red Hat Enterprise Linux 5 32-bit and 64-bit•The addition of RPM and tar source kits for building and installing VS Tools natively on a guest operating system.•Multi-pathing for virtual server Ethernet and Fibre Channel networks to support business continuity and redundancy.•Substantial improvements to disk performance.•LiveSnapshot TM, which provides logical disk and virtual server snapshots for hot backup and patch management. These capabilities enable off-loaded, space efficient, and no-downtime backups on live virtual machines running in produc-tion and development environments.•The ability to reboot virtual servers without the Virtualization Manager running.•Support for NDB CD ROM .iso files, which can now be used as data disks in addition to boot disks.•The packaging of VSTools as an ISO, which appears to the administrator as a virtual CD ROM, to further simplify deployments and upgrades.• A significant reduction in node boot and discovery times when there are large numbers of iSCSI physical disks.•Increased storage on demand with support for the dynamic addition of physical disks to a disk group, which can also now contain more than one physical disk.Number Fixed in This Release458CTRL-ESCAPE, ALT-ESCAPE AND ALT-TAB WERE NOT FUNCTIONALCtrl-Escape, Alt-Escape, and Alt-Tab in the pull-down menu entitledCommands in the Virtual Server Console window, were not functioning.1504 4159THE VIRTUALIZATION MANAGER USER INTERFACE RAN SLOWLY IF ANTI-VIRUS SOFTWARE WAS RUNNING ON THE MANAGEMENT SERVER HOST.Some anti-virus software inspects Java applications, which had the potential of reducing Virtualization Manager client performance.3803D EDICATED MANAGEMENT NETWORKS MUST USE A C LASS C ADDRESSFor management networks, the requirement to use Class C addresses only isno longer necessary.O PEN I SSUES IN THIS R ELEASEFollowing are known issues related to this release.ReferenceOpen in This ReleaseNumber29LINUX TIMER ISSUEOccasionally during Linux boot or kernel calibration issues, the following errorwill appear and the operating system will crash:MP-BIOS bug: 8254 timer not connected to IO-APIC Kernel panic - not syncing:IO-APIC + timer doesn't work! Try using 'noapic'Please report crashes to Virtual Iron Technical Support. See Contacting VirtualIron Support.172QL OGIC HBA S NOT REPORTING PERFORMANCE INFORMATIONNodes with QLogic HBAs will not report disk performance data in the VirtualServer Performance chart.355JBOD SAN DISKS ARE NOT RECOMMENDED AS VIRTUAL SERVER STORAGEDEVICESJBODs can be used for storage devices for Virtual Servers, but they are notrecommended. If JBOD disks go off-line and then back on-line while con-nected to managed nodes, the node will go into an error state that requires anode reboot. Use SAN disks connected via a SAN controller.537KEYBOARD INPUT INTO VIRTUAL CONSOLE OCCASIONALLY RESULTS IN REPEATEDCHARACTERSWhen you type into a virtual console that contains an X windows display, occa-sionally the keyboard output will be repeated. For example if you type ls into aterminal window in X, you may see lllllssss output in the virtual console. Theworkaround is to disable the keyboard repeat function.619VIRTUALIZATION MANAGER SHUTDOWN CAUSES VS S BOOTED FROM A NETWORKBOOT DEVICE TO HANGStopping or Restarting the management server takes down the NBD server.This takes down all VSs booted using NBD. To resolve this issue, restart themanagement server. Then, perform a hard reset on each impacted VS.723POOR NETWORK PERFORMANCE ON 3COM NIC SPoor network performance has been observed on 3COM NICs. This mayimpact the performance of virtual server network operations.892APPLICATIONS THAT ATTEMPT TO COMMUNICATE DIRECTLY TO AN HBA ARE NOT SUPPORTEDKernel-level management applications or agents (such as Emulex HBAny-where, QLogic SANSurfer) in a guest operating system that communicatedirectly to an HBA or directly to other specific devices are not supported. Run-ning these types of applications may cause virtual servers to become unre-sponsive.1122A FTER A R ED H AT INSTALL, THE VCONSOLE IS BLANK WHEN VIRTUAL SERVER BOOTS TO RUN L EVEL 5The first time Red Hat boots after an OS installation, the virtual console may beblank when the system goes into run level 5.Workaround: Remove rhgb from the boot line in /boot/grub/menu.lst.1189 2278 3006ADDING OR REMOVING LUN S COULD REQUIRE A NODE REBOOTWhen adding or removing LUNs to the system to modify storage capacity, it is sometimes necessary to reboot the nodes to accurately display the LUN con-figuration. If a LUN is removed or offline and the Virtualization Manager shows it as online, errors could result if a user attempts to perform operations on that LUN, such as creating virtual hard disks.First, LiveMigrate all virtual servers off the node, then reboot the node. You can then LiveMigrate servers back onto the node.1816VIRTUALIZATION MANAGER INSTALL FAILS WITH BONDED ETHERNETThe Virtualization Manager installer does not handle bonded Ethernet control-lers. Make sure the network controller on the node that will be running themanagement server is not bonded before starting the installation.1962D ATA C ORE THIN PROVISIONING CONFIGURATION REQUIREMENTSDataCore LUNs used for logical volume groups must have sufficient backingstorage for the size of the Virtual Iron volume group. Set the Datacore NMVchunk size to be 4 MB.2028RH3-U8 C ONSOLE K EYBOARD N OT W ORKING WITH K UDZUIf RedHat 3 is installed while the virtual server is configured in the VirtualizationManager with a USB mouse (for example, RHEL4 LINUX) instead of a PS2mouse, you will be in Kudzu after you boot with a PS2 mouse configuration.Kudzu can not use the mouse or keyboard at that point and will time-out. Thesystem will continue to boot.Workaround: Configure the virtual server properly in the Virtualization Managerprior to installing.If the problem does occur, correct the Virtualization Manager virtual serverconfiguration. Then, boot the virtual server and manually invoke Kudzu from aconsole window. Remove the USB drive when you are prompted to do so.2244THE ADMINISTRATION MANAGER IS NOT COMPATIBLE WITH JAVA BUILD1.5.0_06_B05.Virtual Iron® recommends running the latest Java Version 1.5.0 (build1.5.0_10-b03 or later) on the system that is running the Administration Man-ager client.2549DYNAMIC RESIZING OF LUN SUse the following procedure if you have to resize a LUN.1.Cause the LUN you wish to resize to go offline, which is depicted in theManagement Server Hardware view as offline.2.Delete that LUN from the Management Server Hardware view.3.Resize the LUN to your needs.4.Rediscover the LUN in your Management Server Hardware view with theNode--> Rediscover option or the Node--> Rescan SAN Port s option. 2763IPV6 N ETWORKS ARE NOT SUPPORTED.IPV6 networks are not supported for dedicated management networks, iSCSInetworks, or networks used by virtual servers.2884VS S HUTDOWN DOES NOT WORK IF YOU ARE NOT LOGGED INTO THE CONSOLEFor a Windows 2003 server, if the login popup is visible in the console window,you cannot shut down the virtual server via the management server.2978R ED H AT 3 V IRTUAL S ERVER T OOLS HAVE SEPARATE RPM S FOR I NTEL AND AMD PROCESSORSVS Tools for RH3 have separate RPMs for Intel and AMD processors. TheRPM you install in a virtual server must match the processor type (Intel orAMD) of the node (physical server) on which the virtual server is installed.Name these virtual servers, since they will only run on that processor type fromthat point forward.AMD: virtualiron-2.4.21-47.ELsmp-4.1.*.athlon.rpmIntel: virtualiron-2.4.21-47.ELsmp-4.1.*.i686.rpmUse the standard rpm -Uvh to install the proper VS Tools as described in theVirtualization Manager Administrator Guide, Creating and Configuring VirtualServers.3006S EE 1189.3045W INDOWS MOUSE LOSES CONNECTIVITY UPON FIRST BOOT AFTER V IRTUAL I RON UPGRADE F ROM V3.X TO V4.XWhen Virtual Iron is upgraded, the first time each existing Windows virtualserver is booted, the mouse loses connectivity. You may see the hardware wiz-ard notification that a PCI device cannot be found and that a new device is dis-covered.Workaround: Please go through the hardware wizard as it is connecting thenew virtual mouse hardware. The mouse will function correctly once you com-plete the steps in the hardware wizard.3445V IRTUAL I RON AND M ICROSOFT RISWhen using Windows RIS to install Windows into virtual servers, note thatWindows 2000 RIS Server is unsupported; Windows 2000 does not provideRealTek NIC driver support. (Windows 2003 Server and RIS is supported.)Workaround: Configure the Windows DHCP server to use options 66 (bootserver host name) and 67 (boot file name). Set DHCP option 67 to point to thelocation of your . This causes the DHCP and PXE boot process toboot the RIS kernel. Refer to figure below.For additional information, refer to:/kb/244036/3466W INDOWS RE-ACTIVATION MAY BE REQUIRED WHEN UPGRADING FROM VI V3.X TO V4.XVirtual Iron v4.x presents a significantly different virtual motherboard to virtualservers than v3.x. In some cases, these differences may be enough to triggera Windows request to reactivate the virtual server’s copy of Windows withMicrosoft.3494W INDOWS 2000 MAY REPORT AN UNKNOWN PCI DEVICEWhen a Windows 2000 virtual server boots, you may see an unknown PCIdevice reported as found. This is an innocuous message, and this PCI deviceshould be disabled. This device is the HPET timer which is not used in the VIvirtual environment.3831U PGRADING TO V4.X FROM V3.X CAUSES W INDOWS VIRTUAL SERVERS TO LOSE STATIC NETWORK CONFIGURATION INFORMATIONWhen a Virtual Iron installation is upgraded to v4.x from v3.x, any Windows vir-tual servers will lose any static IP address assignments they may have whenthey are first booted without VSTools, and then again when they are firstbooted with the 4.x VSTools.To restore network connectivity, manually re-enter the static network configura-tion for the Virtualization Manager. This does not affect Windows VMs that useDHCP to auto-configure network settings.3839L EFT H AND N ETWORKS I SCSI S ERVERS ONLY SUPPORT 90 I SCSI D ISKSDuring qualification testing of LeftHand Networks (LHN) iSCSI servers, it wasfound that LeftHand Networks iSCSI Servers support a maximum of 90 iSCSIdisks.If you need more than 90 disks with LHN iSCSI storage, you can use the Vir-tual Iron virtual disk management features to partition raw iSCSI disks into mul-tiple logical disks.4172VNIC S DO NOT PRESENTLY SUPPORT DYNAMICALLY CHANGING THE MAC ADDRESSThis attribute is used by Windows Network Load Balancing (NLB). RemovingNLB and the secondary IP and then rebooting restores connectivity.4317/ 4330B ONDED E THERNET NIC S SHOULD BE CONFIGURED TO SEPARATE SWITCHESIf you configure bonded Ethernet NICs to the same switch, you can experience up to 60 seconds of connection failure when a port fails. Outgoing data traffic experiences no issues.It is recommended to configure bonded Ethernet NICs to separate switches, creating a fully-redundant topology, and no incoming connection failure win-dow.4333C LONING L OGICAL D ISKS WITH SAN-BASED C ONTROLLERSIf physical disks that contain logical disks are cloned by a SAN-based storagecontroller, the resultant cloned logical disks will have identical IDs to the mas-ters. This creates naming issues within the managed node. Logical disksshould only be cloned via the Virtualization Manager.Raw physical disks that do not contain logical disks can be cloned by SAN-based storage controllers without issue.4577W INDOWS V IRTUAL S ERVERS CREATED IN V3.X NEED TO CHANGE HAL S TO RUN SMP IN V4.XWindows virtual servers created in Virtual Iron v3.x were created with a uni-processor Hardware Abstraction Layer (HAL). In order to run these virtualservers as SMP virtual servers in v4.x, replace the uni-processor HAL with amultiprocessor HAL. Please consult Microsoft’s knowledge base (#299340) forthe procedure to replace the HAL.4779H IGH CPU USAGE ON MANAGEMENT SERVER AFTER UPGRADEWhen performing an upgrade to the Virtualization Manager, you must insurethat the Virtualization Manager is completely stopped and that there are no cli-ents running and connected to the server. Once you have ensured that every-thing has been stopped, you may proceed with the upgrade.4781I F U PGRADE LOCATION IS ON A DISK PATH WITH SPACES IN THE FOLDERS, UPGRADE FAILSOn a Linux system, ensure that there are no spaces in the installation path sothat you can later upgrade the product. For example, if you attempt to upgradeyour Virtualization Manager originally installed into/opt/Virtual Iron/it will fail in the upgrade script.4803T RYING TO INSTALL VST OOLS ON SLES 10 64-B IT RETURNS ERRORInstalling VSTools on SLES 10 64-bit returns the following error:linux-sl9o:~ # rpm -ivh virtualiron-2.6.16.46-0.12-smp-4.2.8-13.x86_64.rpmerror: Failed dependencies:xen-kmp conflicts with virtualiron-2.6.16.46-0.12-smp-4.2.8-13.x86_64linux-sl9o:~ # uname -aLinux linux-sl9o 2.6.16.46-0.12-smp #1 SMP Thu May 17 14:00:09 UTC 2007x86_64x86_64 x86_64 GNU/LinuxThe XEN kernel packages should not be installed inside a virtual server. If theyhave been installed, remove them:1. Start up YaST.2. Select Software Management.3. Under the Filter option, select Search.4. Search for xen, and remove all packages related to xen.4807 F OURTH LUN (<1TB) FROM MD3000 (I SCSI) SHOWS OFFLINEWhen allocating LUNs to managed nodes, some storage array managersassign LUNs to controllers as they are created. In dual controller configura-tions, this can be a problem if only one controller is in use. The LUNs assignedto the preferred path will show up online in Virtualization Manager and theLUNs assigned to the non-preferred (or not used) path will show up offline inthe virtual machines.The solution is to assign all LUNs to the preferred path when only one control-ler is in use; the virtual machines will display all LUNs as online.4843U PGRADE ERROR FROM 4.1 TO 4.2 VST OOLSVirtual Iron recommends installing with the 32- or 64-bit Setup.exe file in yourmanagement server’s VSTools directory. If you use the MSI to install, save thefile first to your local server. This error occurs when MSI is not in the samelocation as it was when originally installed.When this error occurs, first try to remove the existing VSTools with the Win-dows Add or Remove programs in the Control Panel. After the reboot, try toinstall the new VSTools. If this is not successful, use the following from a com-mand prompt:msiexec /i VSTools.msi /L*V VSTools.log REINSTALLMODE=voums REINSTALL=ALL The VSTools will then be installed.4874SSE INSTALL PANIC ON DL360/DL365'SIf you Install Virtual Iron SSE on HP DL36x G5 series machines configuredwith 2GB of memory or less, you will encounter the following error when itstarts to partition the hard drive:-kernel panic- not syncing:PCI-DMAYou can get around this problem by entering a new boot option, “altboot”, atthe boot splash screen. You will only have to do this the first time Virtual IronSSE is installed.4936W INDOWS V IRTUALIZATION M ANAGER DHCP SERVER PROCESS SOMETIMES DOES NOT START AFTER UPGRADING TO V4.2It is possible, that in some circumstances, after the Virtualization Managerupgrade the dhcpd process fails to start when the Virtualization Manager isrestarted. This is caused by an incorrect setting of file permissions (ACLs) onthe following file during the upgrade:VirtualIron\VirtualizationManager\system\bin\cygwin1.dllTo work around the problem, set the permissions on that file to:SYSTEM(Local Acct) – read, execute, writeN ONE SAN M ULTIPATH S UPPORTSAN multipath for fibre channel-based SAN has been tested on limited config-urations in Virtual Iron. Please see the Virtual Iron HCL for complete multipathsupport information:/products/servers.cfmSAN multipath for iSCSI-based SAN will be tested and supported in a futurerelease.P RODUCT D OCUMENTATIONThe following documents are also available online:•Virtualization Manager™ Administrator Guide - Explains how to configure andmanage virtual data centers and virtual servers.•Virtualization Manager™ Getting Started Guide - Guides you through the pro-cess of getting a virtual server up and running•Virtual Iron Tutorial - Guides you through installation, and storage, boot, andmemory configuration options of a virtual server.C ONTACTING V IRTUAL I RON S UPPORTUse this information to reach Virtual Iron® customer support.Phone: 1-800-314-9872 (Select option 2)Mail: ***********************Web: /services/support_login.cfm。
Meta trader 4使用手册.
开始使用客户端是在线交易系统的一部分。
此终端软件安装在交易者的电脑上，具有如下功能：:▪获得实时的报价和新闻；▪准备和执行交易指令；▪监控和管理开仓头寸和挂单指令。
▪进行技术分析；▪创建智能交易系统、用户自定义技术指标和MQL 4语言脚本；▪交易策略的测试和优化。
交易者为了决定在金融市场上是否进行交易，需要实时和可靠的信息。
正因为如此，此终端软件具有接收在线实时报价和新闻功能。
实时报价服务和使用技术分析指标是分析市场的基础，终端软件上的智能交易系统能够自动的监视市场状态和个人的头寸。
此外，可设置多种类型指令灵活地管理头寸。
此程序能在Microsoft Windows 98/ME/2000/XP/2003下运行，硬件需求由操作系统决定。
终端安装对于安装客户终端需下载相应的程序并开启它。
选择文件目录进行安装。
终端安装完成后将会自行运作。
终端开始程序安装完成后，客户端的程序会在"开始"菜单中创建，程序的快捷方式会添加显示在桌面上。
方便客户端的使用。
注意:客户端不能够在一个目录里同时运行两个复本。
要同时运行几个终端，需要在不同的目录内安装相应的程序。
终端的运作可以从命令栏开始，中心参数已经被指定。
账户数字和数据图表可以作为参数应用。
如果账户数字作为指定参数，验明账户后将会开始程序。
如果数据图表作为指定参数，它将会被自动下载。
例如，terminal.exe "123456-'British Pound'"是"123456"账户数字，British Pound数据图表名称。
如果在命令栏中遇到空白(在数据图表名称上方，必须作双重报价标记。
如果没有空白，无需作双重报价标记。
例如， terminal.exe 123456-'GBPUSD'。
数据图表只有在正常登陆后才可以运作。
终端同样可以应用范围设定开始。
详细请内容查看"配置开启"和"Datacenter.ini"部分。
MortScript使用教程
[技术]MortScript使用教程(4.3b11BETA版)一、MortScript概述：Mort：批量；Script：脚本；MortScript：批处理脚本；（故为顺序逐条执行）它是一种解释程序，就象Visual Basic的即时解释环境一样。
所以，它不生成EXE等可执行程序，而是由MortScript.exe来运行*.mscr或*.mortrun的脚本文件。
当然，如果进行了安装，或设置了文件关联，则可直接点击脚本文件运行。
二、mscr脚本概述：*.mortrun格式为MortScript的前身MortRunner的兼容脚本。
*.mscr格式可用任意文本编辑器来编写脚本，如windows自带的记事本，保存格式推荐ANSI，当然，它还兼容UNICODE格式。
文件名及内容均不区分大小写。
脚本里的空格、制表符、换行连接符：空格和制表占位符可放在命令、函数名、括号、参数、运算符、选项的前、后等位置，但均被忽略，字符串中需要使用空格则应放在引号内。
换行连接符采用\符，放置于所在行的行末。
未指定路径则默认当前脚本所在路径。
注释行则是以#开头的行。
在INI文件中，则使用；进行注释。
结束以:Exit，退出和结束脚本。
三、MortScript功能：1、运行、激活，隐藏，关闭应用程序。
2、根据指定条件，执行或延时执行程序、脚本。
3、模拟键盘、鼠标、触笔操作。
4、复制、重命名、移动、删除文件或文件夹，创建文件夹，以及创建快捷方式。
5、支持ZIP格式压缩包。
6、读、写文本文件。
7、读、改注册表。
8、下载、创建、关闭链接。
9、做判断、循环操作。
10、部分系统的旋屏、音量、背光、重启操作。
四、MortScript安装包结构解读：pc:分别适用WM、CE、SP、win2000、XP、vista系统设备绿色使用。
setup:分别适用WM、CE、SP系统设备，通过PC连接设备同步安装。
cab:分别适用WM、CE、SP系统设备直接安装。
MortScriptV4.2用户手册(中文版)
用户手册
整理：Kawvin 二〇一〇年十月十三日
目
1 2 3
录
4ห้องสมุดไป่ตู้
5
6
7
8
MorScript 是什么?/使用许可 ......................................................................................................................................1 功能范围.......................................................................................................................................................................1 安装...............................................................................................................................................................................1 3.1 不同的 MortScript 版本 ...................................................................................................................................1 3.2 PC 安装 .............................