VAOneReleaseNotes_v2006.1

合集下载

Sun ONE Web Server 6.1 用户指南说明书

Administrator’s GuideSun™ ONE Web Server Version 6.1819-0130-10September 2004Sun Microsystems, Inc.4150 Network CircleSanta Clara, CA 95054 U.S.A.Copyright 2004 Sun Microsystems, Inc. All rights reserved.Sun, Sun Microsystems, the Sun logo, Java, Solaris, Sun ONE, iPlanet, and all Sun, Java, and Sun ONE based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.UNIX is a registered trademark in the United States and other countries, exclusively licensed through X/Open Company, Ltd. Adobe GoLive is a trademark or registered trademark of Adobe Systems Incorporated in the United States and other countries. Macromedia DreamWeaver is a trademark or registered trademark of Macromedia, Inc. in the United States and other countries. Netscape is a trademark or registered trademark of Netscape Communications Corporation in the United States and other countries. Federal Acquisitions: Commercial Software—Government Users Subject to Standard License Terms and ConditionsThe product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation. No part of the product or this document may be reproduced in any form by any means without prior written authorization of Sun Microsystems, Inc. and its licensors, if any.THIS DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.________________________________________________________________________________________Copyright 2004 Sun Microsystems, Inc. Tous droits réservés.Sun, Sun Microsystems, le logo Sun, Java, Solaris, Sun ONE, et iPlanet sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et d’autre pays.UNIX est une marque enregistree aux Etats-Unis et dans d'autres pays et licenciée exclusivement par X/Open Company Ltd. Adobe GoLive est une marque enregistree de Adobe Systems Incorporated, Inc aux Etats-Unis et dans d'autres pays.Macromedia DreamWeaver est une marque enregistree de Macromedia, Inc aux Etats-Unis et dans d'autres pays.Netscape est une marque de Netscape Communications Corporation aux Etats-Unis et dans d'autres pays.Le produit décrit dans ce document est distribué selon des conditions de licence qui en restreignent l'utilisation, la copie, la distribution et la décompilation. Aucune partie de ce produit ni de ce document ne peut être reproduite sous quelque forme ou par quelque moyen que ce soit sans l’autorisation écrite préalable de Sun Microsystems, Inc. et, le cas échéant, de ses bailleurs de licence. CETTE DOCUMENTATION EST FOURNIE “EN L'ÉTAT”, ET TOUTES CONDITIONS EXPRESSES OU IMPLICITES, TOUTES REPRÉSENTATIONS ET TOUTES GARANTIES, Y COMPRIS TOUTE GARANTIE IMPLICITE D'APTITUDE À LA VENTE, OU À UN BUT PARTICULIER OU DE NON CONTREFAÇON SONT EXCLUES, EXCEPTÉ DANS LA MESURE OÙ DE TELLES EXCLUSIONS SERAIENT CONTRAIRES À LA LOI.ContentsAbout This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 What’s In This Guide? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 How This Guide Is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Part I: Server Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Part II: Using the Administration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Part III: Configuring and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Part IV: Managing Virtual Servers and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Part V: Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Using the Sun ONE Web Server Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Part1 Server Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Chapter1Introduction to Sun ONE Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Sun ONE Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 What’s New in Sun ONE Web Server 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Java Servlet 2.3 and JavaServer Pages (JSP) 1.2 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32JDK 1.4.1_03 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32WebDAV Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32NSAPI Filters Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33HTTP Compression Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33New Search Engine Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Enhanced Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34JNDI Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343JDBC Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Sun ONE Studio 5 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34NSS 3.3.5 and NSPR 4.1.5 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35PHP Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Enhanced Hardware Accelerator Encryption Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Start on Boot Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Additional Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Administering and Managing Sun ONE Web Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Sun ONE Web Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Administration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Server Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Class Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Virtual Server Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Using the Resource Picker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Wildcards Used in the Resource Picker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Chapter2Administering Sun ONE Web Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Starting the Administration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 UNIX/Linux Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Windows Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Running Multiple Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Virtual Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Installing Multiple Instances of the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Removing a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Migrating a Server From a Previous Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Part2 Using the Administration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Chapter3Managing Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Accessing Information About Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 About Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 Types of Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Configuring a Directory Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Understanding Distinguished Names (DNs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Using LDIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Creating Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Creating a New User in an LDAP-based Authentication Database . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Guidelines for Creating LDAP-based User Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58How to Create a New User Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Directory Server User Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Creating a New User in a Key File Authentication Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 4Sun ONE Web Server 6.1•Administrator’s Guide•September 2004Creating a New User in a Digest File Authentication Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Finding User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Building Custom Search Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Editing User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Managing a User’s Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Renaming Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Removing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Creating Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Static Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Guidelines for Creating Static Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 To Create a Static Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Dynamic Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 How Sun ONE Web Server Implements Dynamic Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Groups Can Be Static and Dynamic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Dynamic Group Impact on Server Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Guidelines for Creating Dynamic Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 To Create a Dynamic Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Managing Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Finding Group Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 The “Find all groups whose” Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Editing Group Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Adding Group Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Adding Groups to the Group Members List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Removing Entries from the Group Members List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Managing Owners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Managing See Alsos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Removing Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Renaming Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Creating Organizational Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Managing Organizational Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Finding Organizational Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 The “Find all units whose” Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Editing Organizational Unit Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Renaming Organizational Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Deleting Organizational Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Chapter4J2EE-based Security for Web Container and Web Applications . . . . . . . . . . . . . . 83 About Sun ONE Web Server Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Overview of ACL-based Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Overview of J2EE/Servlet-based Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Realm-based Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Realm-based User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885LDAP realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88File realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Solaris realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Certificate realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Custom Realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Native Realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Role-based Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Mapping Roles to Restricted Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Defining Access Control by Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 How to Configure a Realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Using the Administration Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Editing the server.xml File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Configuring the Native Realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Specifying the Default Realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Using Programmatic Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Deciding When to Use the J2EE/Servlet Authentication Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Chapter5Setting Administration Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Shutting Down the Administration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Editing Listen Socket Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Changing the User Account (UNIX/Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Changing the Superuser Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Allowing Multiple Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Specifying Log File Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Viewing Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 The Access Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103The Error Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Archiving Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Using schedulerd Control-based Log Rotation (UNIX/Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Configuring Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Restricting Server Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Chapter6Using Certificates and Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Certificate-based Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Using Certificates for Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Server Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Client Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Virtual Server Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Creating a Trust Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Creating a Trust Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Using password.conf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 Start an SSL-enabled Server Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 6Sun ONE Web Server 6.1•Administrator’s Guide•September 2004Requesting and Installing a VeriSign Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Requesting a VeriSign Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Installing a VeriSign Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Requesting and Installing Other Server Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Required CA Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Requesting Other Server Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Installing Other Server Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Installing a Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Migrating Certificates When You Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Using the Built-in Root Certificate Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Managing Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Installing and Managing CRLs and CKLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Installing a CRL or CKL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Managing CRLs and CKLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Setting Security Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 SSL and TLS Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Using SSL to Communicate with LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Enabling Security for Listen Sockets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Turning Security On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Selecting a Server Certificate for a Listen Socket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Selecting Ciphers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 Configuring Security Globally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 SSLSessionTimeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 SSLCacheEntries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 SSL3SessionTimeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Using External Encryption Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Installing the PKCS#11Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Using modutil to Install a PKCS#11 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Using pk12util . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Selecting the Certificate Name for a Listen Socket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 FIPS-140 Standard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Setting Client Security Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Requiring Client Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 To Require Client Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Mapping Client Certificates to LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Using the certmap.conf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Creating Custom Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Sample Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143 Setting Stronger Ciphers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Considering Additional Security Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Limit Physical Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Limit Administration Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Choosing Solid Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1487。

ReleaseNotes_EnterpriseHomeScreen_v3.1_chinese说明书

发行说明 - Enterprise Home Screen v3.1目录·重要新闻·以前的公告·简介·说明·设备兼容性·安装要求·安装说明·使用说明·已知问题·部件号和发布日期重要新闻Android 支持：EHS 3.1 现在支持Android 8.1.0 (Oreo) 和 Android 7.1.2 (Nougat)。

针对运行 Android 6.0.1 (Marshmallow) 的设备的 EHS 支持结束了 - EHS v3.1 仅支持Nougat 和 Oreo 设备。

EHS v3.0 是支持 Android Marshmallow 设备的最后一个版本。

支持门户上仍然提供 EHS v3.0 及更早版本，供在 Marshmallow 设备上使用。

以前的公告从Android Nougat/Marshmallow 升级到Oreo：将设备从Android Nougat/Marshmallow 升级到 Oreo 之后，必须卸载现有 EHS 版本，并且必须在原处安装EHS_03XXXX_B.apk。

来自以前 EHS 安装的配置会保留下来并自动应用。

这不适用于现有版本为类型 B 的 EHS 3.X (EHS_03XXXX_B.apk) 的设备绕过锁屏功能已弃用。

安全模式功能已弃用。

已终止针对所有 Lollipop (Android 5.x) 设备的 EHS 支持 - 从 EHS v3.0 开始，仅支持Marshmallow 及更高版本设备。

EHS v2.8 是支持 Android Lollipop 设备的最后一个版本。

支持门户上仍然提供 EHS v2.8 及更早版本，供在 Lollipop 设备上使用。

从版本 2.8 开始，简体中文语言支持在 EHS 中可用从 EHS 版本 2.7 开始，在支持门户中提供两个独立的 APK（EHS_XXXXXX_A.apk 和EHS_XXXXXX_B.apk），供用户根据所使用的 Zebra 设备进行选择。

ReleaseNotes

-------------
CP210x Windows XP/2003/Vista(32/64)/7(32/64) Driver v6.3a - February 1, 2011
CP210x Windows Driver Revision History
--------------------------------------
-------------------------
Created IO queueing mechanism so that multiple reads, writes, etc. can be queued and
waited on
version 5.4.29
Corrections
to the queue
Corrected a condition which would blue screen on cancelling write request that hasn't been
fully sent out USB
Corrected the Capabilites return value, which incorrectly reported that timeouts are not supported
Corrected a problem where an IO reqest would sometimes return a busy status to
user mode, instead the queue is restarted if necessary before adding an IO request
* x64 directory

AADEBUG2003 XXX1 Instrumenting self-modifying code

AADEBUG2003XXX1 Instrumentingself-modifying codeJonas Maebe∗,Koen De Bosschere∗,1∗ELIS,Ghent University,Sint-Pietersnieuwstraat41,9000Gent,BelgiumABSTRACTAdding small code snippets at key points to existing code fragments is called instrumentation.It is an estab-lished technique to debug certain otherwise hard to solve faults,such as memory management issues and data races.Dynamic instrumentation can already be used to analyse code which is loaded or even generated at run time.With the advent of environments such as the Java Virtual Machine with optimizing Just-In-Time compilers,a new obstacle arises:self-modifying code.In order to instrument this kind of code correctly,one must be able to detect modiﬁcations and adapt the instrumentation code accordingly,preferably without incurring a high penalty speedwise.In this paper we propose an innovative technique that uses the hard-ware page protection mechanism of modern processors to detect such modiﬁcations.We also show how an instrumentor can adapt the instrumented version depending on the kind of modiﬁciations as well as an experimental evaluation of said techniques.KEYWORDS:dynamic instrumentation;instrumenting self-modifying code1IntroductionInstrumentation is a technique whereby existing code is modiﬁed in order to observe or modify its behaviour.It has a lot of different applications,such as proﬁling,coverage analysis and cache simu-lations.One of its most interesting features is however the ability to perform automatic debugging, or at least assist in debugging complex programs.After all,instrumentation code can intervene in the execution at any point and examine the current state,record it,compare it to previously recorded information and even modify it.Debugging challenges that are extremely suitable for analysis through instrumentation include data race detection[RDB99,RDB01]and memory management checking[Sew02].These are typically problems that are very hard to solve manually.However,since they can be described perfectly using a set of rules(e.g.the memory must be allocated before it is accessed,or no two threads must write to the same memory location without synchronising),they are perfect candidates for automatic veriﬁ-cation.Instrumentation provides the necessary means to insert this veriﬁcation code with little effort on the side of the developer.The instrumentation can occcur at different stages of the compilation or execution process.When performed prior to the execution,the instrumentation results in changes in the object code on disk, which makes them a property of a program or library.This is called static instrumentation.If the addition of instrumentation code is postponed until the program is loaded in memory,it becomes a property of an execution.In this case,we call it dynamic instrumentation.Examples of stages where static instrumentation can be performed are directly in the source code[Par96],in the assembler output of the compiler[EKKL90],in the compiled objects or programs 1E-mail:{jmaebe,kdb}@elis.UGent.beXXX2JONAS MAEBE,KOEN DE BOSSCHERE (e.g.EEL[LS96],ATOM[SE94],alto[DBD96]).The big advantage of static instrumentation is that it must be done only once,after which one can perform several executions without having to reinstru-ment the code every time.This means that the cost of instrumenting the code can be relatively high without making such a tool practically unusable.The larges disadvantage of static instrumentation is that it requires a complex analysis of the tar-get application to detect all possible execution paths,which is not always possible.Additionally,the user of a static instrumentation tool must know which libraries are loaded at run time by programs he wants to observe,so that he can provide instrumented versions of those.Finally,every time a new type of instrumentation is desired,the application and its libraries must be reinstrumented.Most of the negative points of static instrumentation are solved in its dynamic counterpart.In this case,the instrumentation is not performed in advance,but gradually at run time as more code is executed.Since the instrumentation can continue while the program is running,no prior analysis of all possible execution paths is required.It obviously does mean that the instrumentation must be redone every time the program is executed.This is somewhat offset by having to instrument only the part of the application and its libraries that is covered by a particular execution though.One can even apply dynamic optimization techniques[BDA01]to further reduce this overhead.When using dynamic instrumentation,the code on disk is never modiﬁed.This means that a single uninstrumented copy of an application and its libraries sufﬁces when using this technique,no matter how many different types of instrumentation one wants to perform.Another consequence is that the code even does not have to exist on disk.Indeed,since the original code is read from memory and can be instrumented just before it is executed,even dynamically loaded and generated code pose no problems.However,when the program starts modifying this code,the detection and handling of these modiﬁcations is not possible using current instrumentation techniques.Yet,being able to instrument self-modifying code becomes increasingly interesting as run time systems that exhibit such behaviour gain more and more popularity.Examples include Java Virtual Machines, environment and emulators with embedded Just-in-Time compilers in general. These environments often employ dynamic optimizing compilers which continuously change the code in memory,mainly for performance reasons.Instrumenting the programs running in such an environment is often very easy.After all,the dynamic compiler or interpreter that processes said programs can do the necessary instrumentation most of the time.On the other hand,observing the interaction of the environments themselves with the applications on top and with the underlying operating system is much more difﬁcult.Never-theless,this ability is of paramount importance when analysing the total workload of a system and debugging and enhancing these virtual machines.Even when starting from a system that can already instrument code on theﬂy,supporting self-modifying code is a quite complex undertaking.First of all,the original program code must not be changed by the instrumentor,since otherwise program’s own modiﬁcations may conﬂict with these changes later on.Secondly,the instrumentor must be able to detect changes performed by the pro-gram before the modiﬁed code is executed,so that it can reinstrument this code in a timely manner. Finally,the reinstrumentation itself must take into account that an instruction may be changed using multiple write operations,so it could be invalid at certain points in time.In this paper we propose a novel technique that can be used to dynamically instrument self-modifying code with an acceptable overhead.We do this by using the hardware page protection facilities of the processor to mark pages that contain code which has been instrumented as read-only.When the program later on attempts to modify instrumented code,we catch the resulting pro-tection faults which enables us to detect those changes and act accordingly.The described method has been experimentally evaluated using the DIOTA(Dynamic Instrumentation,Optimization and Transformation of Applications[MRDB02])framework on the Linux/x86platform by instrumenting a number of JavaGrande[Gro]benchmarks running in the Sun1.4.0Java Virtual Machine.The paper now proceeds with an overview of dynamic instrumentation in general and DIOTA in particular.Next,we show how the detection of modiﬁed code is performed and how to reinstru-ment this code.We then present some experimental results of our implementation of the describedINSTRUMENTING SELF-MODIFYING CODE XXX3Figure1:Dynamic instrumentation the DIOTA waytechniques and wrap up with the conclusions and our future plans.2Dynamic instrumentation2.1OverviewDynamic instrumentation can be be done in two ways.One way is modifying the existing code,e.g. by replacing instructions with jumps to routines which contain both instrumentation code and the replaced instruction[MCC+95].This technique is not very usable on systems with variable-length instructions however,as the jump may require more space than the single instruction one wants to replace.If the program later on transfers control to the second instruction that has been replaced, it will end up in the middle of this jump instruction.The technique also wreaks havoc in cases of data-in-code or code-in-data,as modifying the code will cause modiﬁcations to the data as well.The other approach is copying the original code into a separate memory block(this is often called cloning)and adding instrumentation code to this copy[BDA01,SKV+03,MRDB02].This requires special handling of control-ﬂow instructions with absolute target addresses,since these addresses must be relocated to the instrumented version of the code.On the positive side,data accesses still occur correctly without any special handling,even in data-in-code situations.The reason is that when the code is executed in the clone,only the program counter(PC)has a different value in an instrumented execution compared to a normal one.This means that when a program uses non-PC-relative addressing modes for data access,these addresses still refer to the original,unmodiﬁed copy of the program or data.PC-relative data accesses can be handled at in-strumentation time,as the instrumentor always knows the address of the instruction it is currently instrumenting.This way,it can replace PC-relative memory accesses with absolute memory accesses based on the value the PC would have at that time in a uninstrumented execution.2.2DIOTADIOTA uses the cloning technique together with a cache that keeps track of already translated in-struction blocks.It is implemented as a shared library and thus resides in the same address space as the program it instruments.By making use of the LD_PRELOAD environment variable under Linux, the dynamic linker(ld.so)can be forced to load this library,even though an application is not ex-plicitly linked to it.The init routines of all shared libraries are executed before the program itself is started,providing DIOTA an opportunity to get in control.As shown in Figure1,the instrumentation of a program is performed gradually.First,the instruc-tions at the start of the program are analysed and then copied,along with the desired instrumentation code,to the clone(a block of memory reserved at startup time,also residing in the program’s address space).During this process,direct jumps and calls are followed to their destination.The instrumenta-tion stops when an instruction is encountered of which the destination address cannot be determined unequivocally,such as an indirect jump.XXX4JONAS MAEBE,KOEN DE BOSSCHERECloneOriginal programInstrumentedcodeMarkertableInstrumentedcodeMarkerFigure2:Data structures used by DIOTAAt this point,a trampoline is inserted in the clone.This is a small piece of code which will pass the actual target address to DIOTA every time the corresponding original instruction would be executed. For example,in case of a jump with the target address stored in a register,the trampoline will pass the value of that speciﬁc register to DIOTA every time it is executed.When DIOTA is entered via such a trampoline,it will check whether the code at the passed address has already been instrumented.If that is not the case,it is instrumented at that point.Next,the instrumented version is executed.Figure2shows how DIOTA keeps track of which instructions it has already instrumented and where the instrumented version can be found.A marker consisting of illegal opcodes is placed after every block of instrumented code(aligned to a4-byte boundary),followed by the translation table. Such a translation table starts with two32bit addresses:the start of the block in the original code and its counterpart in the clone.Next,pairs of8bit offsets between two successive instructions in the respective blocks are stored,with an escape code to handle cases where the offset is larger than255 bytes(this can occur because we follow direct calls and jumps to their destination).In addition to those tables,an AVL tree is constructed.The keys of its elements are the start and stop addresses of the blocks of original code that have been instrumented.The values are the start addresses of the translation tables of the corresponding instrumented versions.Every instruction is instrumented at most once,so the keys never overlap.This means thatﬁnding the instrumented version of an instruction boils down toﬁrst searching for its address in the AVL tree and if found, walking the appropriate translation table.To speed up this process,a small hash table is used which keeps the results of the latest queries.A very useful property of this system is that it also works in reverse:given the address of an instrumented instruction,it is trivial toﬁnd the address of corresponding original instruction.First, the illegal opcodes marker is sought starting from the queried address and next the table is walked just like before until the appropriate pair is found.This ability of doing two-way translations is indispensable for the self-modifying code support and proper exception handling.Since the execution is followed as it progresses,code-in-data and code loaded or generated at run time can be handled without any problems.When a trampoline passes an address to DIOTA of code it has not yet instrumented,it will simply instrument it at that time.It is irrelevant where this code is located,when it appeared in memory and whether or not it doubles as dataDIOTA has several modes of operation,each of which can be used separately,but most can be combined as well.Through the use of so-called backends,the different instrumentation modes can be activated and the instrumentation parameters can be modiﬁed.These backends are shared libraries that link against DIOTA and which can ask to intercept calls to arbitrary dynamically linked routines based on name or address,to have a handler called whenever a memory access occurs,when a basic block completes or when a system call is performed(both before and after the system call,with the ability to modify its parameters or return value).Several backends can be used at the same time.INSTRUMENTING SELF-MODIFYING CODE XXX5 Other features of the DIOTA framework include the ability to handle most extensions to the80x86 ISA(such as MMX,3DNow!and SSE)and an extensible and modular design that allows easy im-plementation of additional backends and support for newly introduced instructions.This paper de-scribes the support for instrumenting self-modifying code in DIOTA.For other technical details about DIOTA we refer to[MRDB02].2.3Exception handlingAn aspect that is of paramount importance to the way we handle self-modifying code,is the handling of exceptions(also called signals under Linux).The next section will describe in more detail how we handle the self-modifying code,but since it is based on marking the pages containing code that has been instrumented as read-only,it is clear that every attempt to modify such code will cause a protection fault(or segmentation fault)exception.These exceptions and those caused by other operations must be properly distinguished,in order to make sure that the program still receives signals which are part of the normal program execution while not noticing the other ones.This is especially important since the Java Virtual Machine that we used to evaluate our implementation uses signals for inter-thread communication.When a program starts up,each signal gets a default handler from the operating system.If a program wants to do something different when it receives a certain signal,it can install a signal handler by performing a system call.This system call gets the signal number and the address of the new handler as arguments.Since we want to instrument these user-installed handlers,we have to intercept these system calls.This can be achieved by registering a system call analyser routine with DIOTA.This instructs DIOTA to insert a call to this routine after every system call in the instrumented version of the pro-gram.If such a system call successfully installed a new signal handler,the analyser records this handler and then installs a DIOTA handler instead.Next,when a signal is raised,DIOTA’s handler is activated.One of the arguments passed to a signal handler contains the contents of all processor registers at the time the signal occurred,in-cluding those of the instruction pointer register.Since the program must not be able to notice it is being instrumented by looking at at that value,it is translated from a clone address to an original program address using the translation tables described previously.Finally,the handler is executed under control of DIOTA like any other code fragment.Once the execution arrives at the sig_return or sig_rt_return system call that ends this signal’s execution,DIOTA replaces the instruction pointer in the signal context again.If the code at that address is not yet instrumented,the instruction pointer value in the context is replaced with the address of a trampoline which will transfer control back to DIOTA when returning from the signal’s execution.Otherwise,the clone address corresponding to the already instrumented version is used. 3Detecting modiﬁcationsDynamically generated and loaded code can already be handled by a number of existing instrumen-tors[BDA01,MRDB02].The extra difﬁculty of handling self-modifying code is that the instrumen-tation engine must be able to detect modiﬁcations to the code,so that it can reinstrument the new code.Even the reinstrumenting itself is not trivial,since a program may modify an instruction by performing two write operations,which means the intermediate result could be invalid.There are two possible approaches for dealing with code changes.One is to detect the changes as they are made,the other is to check whether code has been modiﬁed every time it is executed.Given the fact that in general code is modiﬁed far less than it is executed,theﬁrst approach was chosen.The hardware page protection facilities of the processor are used to detect the changes made page.Once a page contains code that has been instrumented,it will be write-protected.The consequence is thatXXX6JONAS MAEBE,KOEN DE BOSSCHEREFigure3:Exception handling in the context of self-modifying code supportany attempt to modify such code will result in a segmentation fault.An exception handler installed by DIOTA will intercept these signals and take the appropriate action.Since segmentation faults must always be caught when using our technique to support self-modifying code,DIOTA installs a dummy handler at startup time and whenever a program installs the default system handler for this signal(which simply terminates the process if such a signal is raised),or when it tries to ignore it.Apart from that,no changes to the exception handling support of DIOTA have been made,as shown in Figure3.Whenever a protection fault occurs due to the program trying to modify some previously in-strumented code,a naive implementation could unprotect the relevant page,perform the required changes to the instrumented code inside the signal handler,reprotect the page and continue the pro-gram at the next instruction.There are several problems with this approach however:•On a CISC architecture,most instructions can access memory,so decoding the instruction that caused the protection fault(to perform the change that caused the segmentation fault in the handler)can be quite complex.•It is possible that an instruction is modiﬁed by means of more than one memory write opera-tion.Trying to reinstrument after theﬁrst write operation may result in encountering an invalid instruction.•In the context of a JiT-compiler,generally more than one write operation occurs to a particular page.An example is when a page was already partiallyﬁlled with code which was then exe-cuted and thus instrumented,after which new code is generated and placed on that page as well.A better way is to make a copy of the accessed page,then mark it writable again and let the program resume its execution.This way,it can perform the changes it wanted to do itself.After a while,the instrumentor can compare the contents of the unprotected page and the the buffered copy toﬁnd the changes.So the question then becomes:when is this page checked for changes,how long will it be kept unprotected and how many pages will be kept unprotected at the same time.INSTRUMENTING SELF-MODIFYING CODE XXX7 All parameters are important for performance,since keeping pages unprotected and checking them for changes requires both processing and memory resources.The when-factor is also important for correctness,as the modiﬁcations must be incorporated in the clone code before it is executed again.On architectures with a weakly consistent memory model(such as the SPARC and PowerPC), the program must make its code changes permanent by using an instruction that synchronizes the instruction caches of all processors with the current memory contents.These instructions can be intercepted by the instrumentation engine and trigger a comparison of the current contents of a page with the previously buffered contents.On other architectures,heuristics have be used depending on the target application that one wants to instrument to get acceptable performance.For example,when using the Sun JVM1.4.0running on a80x86machine under Linux,we com-pare the previously buffered contents of a page to the current contents whenever the thread that caused the protection fault does one of the following:•It performs a kill system call.This means the modiﬁer thread is sending a signal to another thread,which may indicate that it hasﬁnished modifying the code and that it tells the other thread that it can continue.•It executes a ret or other instruction that requires a lookup toﬁnd the appropriate instru-mentation code.This is due to the fact that sometimes the modifying and executing threads synchronise using a spinlock.The assumption here is that before the modifying thread clears the spinlock,it will return from the modiﬁcation routine,thus triggering aﬂush.Although this method is by no means a guarantee for correct behaviour in the general case,in our experience it always performs correctly in the context of instrumenting code generated by the Sun JVM1.4.0.The unprotected page is protected again when it has been checked N successive times without any changes having been made to it,or when another page has to be unprotected due to a protection fault.Note that this optimisation only really pays off in combination with only checking the page contents in the thread that caused the initial protection fault.The reason is that this ensures that the checking limit is not reached prematurely.Otherwise,the page is protected again too soon and a lot of extra page faults occur,nullifying any potential gains.Finally,it is possible to vary the number of pages that are being kept unprotected at the same time.Possible strategies are keeping just one page unprotected for the whole program in order to minimize resources spent on buffering and comparing contents,keeping one page unprotected per thread,or keeping several pages unprotected per thread to reduce the amount of protection faults. Which strategy performs best depends on the cost of a page fault and the time necessary to do a page compare.4Handling modiﬁcationsDifferent code fragments in the clone are often interconnected by direct jumps.For example,when –while instrumenting–we arrive at an instruction which was already instrumented before,we generate a direct jump to this previously instrumented version instead of instrumenting that code again.This not only improves efﬁciency,but it also makes the instrumentation of modiﬁed code much easier,since there is only one location in the clone we have to adapt in case of a code modiﬁcation.Because of these direct jump interconnections,merely generating an instrumented version of the modiﬁed code at a different location in the clone is not enough.Even if every lookup for the in-strumented version of the code in that fragment returns one of the new addresses in the clone,the old code is still reachable via de direct jumps from other fragments.Removing the direct jumps and replacing them with lookups results in a severe slowdown.Another solution would be keeping track of to which other fragments each fragment refers and adapting the direct jumps in case of changes.This requires a lot of bookkeeping however,and chang-XXX8JONAS MAEBE,KOEN DE BOSSCHERE Program Normal Instrumented Slowdown Relative#of Relative# name execution(s)execution(s)protection faults of lookups FFT40.2895.86 2.382305409609 MolDyn22.0365.57 2.985105423174 SparseMatmult24.2991.09 3.753751874669 HeapSort 5.2541.037.82147791700553 LUFact 4.5338.178.43174021655753 SearchBench23.92429.1017.9481446337596 Crypt8.91175.1519.66128456696704 RayTraceBench28.87652.1122.5966118026878Table1:Test results for a number of sequential JavaGrande2.0benchmarksing one fragment may result in a cascade effect,requiring a lot of additional changes elsewhere in the clone.For these reasons,we opted for the following three-part strategy.The optimal way to handle the modiﬁcations,is to reinstrument the code in-place.This means that the previously instrumented version of the instructions in the clone are simply replaced by the new ones.This only works if the new code has the same length as(or is shorter than)the old code however,which is not always the case.A second way to handle modiﬁcations can be applied when the instrumented version of the previous instruction at that location was larger than the size of an immediate jump.In this case,it is possible to overwrite the previous instrumented version with a jump to the new version.At the end of this new code,another jump can transfer control back to rest of the original instrumentation code.Finally,if there is not enough room for an immediate jump,the last resort isﬁlling the room originally occupied by the instrumented code with breakpoints.The instrumented version of the new code will simply be placed somewhere else in the code.Whenever the program then arrives at such a breakpoint,DIOTA’s exception handler is entered.This exception handler has access to the address where the breakpoint exception occurred,so it can use the translation table at the end of the block to look up the corresponding original program address.Next,it can lookup where the latest instrumented version of the code at that address is located and transfer control there.5Experimental evaluation5.1General observationsWe evaluated the described techniques by implementing them in the DIOTA framework.The perfor-mance and correctness were veriﬁed using a number of tests from the JavaGrande[Gro]benchmark, running under the Sun JVM1.4.0on a machine with two Intel Celeron processors clocked at500MHz. The operating system was Redhat Linux7.3with version2.4.19of the Linux kernel.Several practical implementation issues were encountered.The stock kernel that comes with Red-hat Linux7.3,which is based on version2.4.9of the Linux kernel,contains a number ofﬂaws in the exception handling that cause it to lock up or reboot at random times when a lot of page protection exceptions occur.Another problem is that threads in general only have limited stack space and al-though DIOTA does not require very much,the exception frames together with DIOTA’s overhead were sometimes large enough to overﬂow the default stacks reserved by the instrumented programs. Therefore,at the start of the main program and at the start of every thread,we now instruct the kernel to execute signal handlers on an alternate stack.DIOTA’s instrumentation engine is not re-entrant and as such is protected by locks.Since a thread can send a signal to another thread at any time,another problem we experienced was that sometimes a thread got a signal while it held the instrumentation lock.If the triggered signal handler was not。

ReleaseNote

*** Topaz Adjust™ for Windows V4.1 Release Notes ***Contents1. Installation2. Running Topaz Adjust3. Registration4. System requirements5. Program Features6. More information1. InstallationTopaz Adjust 4.1™ is a plug-in for Adobe Photoshop and other photo-editing / imaging software programs (called host programs) that support Photoshop plug-ins. It has been tested with:Adobe Photoshop 7/CS/CS2/CS3/CS4/CS5Adobe Photoshop Elements 1-9Paint Shop ProPainter X/11 (preview zoom is not supported)PhotoImpactIrfanview (freeware)The installer will automatically detect and install the plug-in for Adobe Photoshop7/CSx and Elements users. However, if you are using another host program, you will need to take some additional steps.In Paint Shop Pro / PhotoImpact: You will need to specify the Topaz Adjust 4 Plug-ins folder as an additional plug-ins folder to using menu File \ Preference \ Folder and then add Topaz Adjust “Plug-ins” folder, usually located at “C:\Program Files \ Topaz Labs \ Topaz Adjust \ Plugins”In Irfanview, Make sure you’ve downloaded and installed the 8BF plug-in add-on, available on the Irfanview webpage. Go to menu \ Image \ Effects \Adobe 8BF filters and add Topaz Adjust 4 “Plug-ins” folder.For other host programs, you may need to copy “Topaz Adjust 4” “Plug-in”folder to the required location of that host program. Make sure you do notmove the “Presets” folder, however.2. Running Topaz AdjustTopaz Adjust is a Photoshop plug-in, not a stand alone program, which means that you are not able to run it directly. To use Topaz Adjust, open up an image in Photoshop (or your other compatible image-editing software). Topaz Adjust will be located in the “Filters -> Topaz Labs” menu. (You will need to open or create a new image in order to access the filters menu).3. RegistrationWhen you first install the plug-ins, Topaz Adjust will be in demo mode. All functions are available except the ability to save the processed image. In order to save your processed image, you will need to enter either a purchased license key or a 30-day fully functional trial key, which you can obtain here:/downloadsYou may purchase the product online through our secure ordering system at:/storeTo enter your key, open Topaz Adjust, click the Menu… button and then select Enter Key…. You can then copy & paste or type your key in.4. System RequirementsIt is recommended that you have at least 1 GB of RAM. Topaz Adjust is very computationally intensive and you'll need a fast computer to run it at acceptable speeds. Topaz Adjust supports multi-core CPUs, which increases rendering speed substantially.This installer is for Windows only. For the Mac version please visit our website at: /downloads5. Program FeaturesTopaz Adjust has many valuable tools to help make your photos pop.New Adjust V4 Features:•Auto Updater. Get software updates instantly.•New user interface. Includes the ability to easily expand and collapseside panelsand parameter tabs for an adjustable workspace.•Snap / Recall buttons. Save up to 99 snapshot settings for comparison.•Preset enable / disable option. Option to enable or disable the presetpreview processing at program startup.•New presets layout. The new preset format features its own preview。

ReleaseNotes

Mapmatrix部分1.目前断面编辑只是提供显示、查看断面效果，不提供编辑功能，其程序总是默认将断面显示模型的最左侧，可以使用键盘中的<和>进行操作，即逗号和句点键。

2.dom修补中修补效果和生成效果偶有不一致的现象，主要是由于修补的区域是采用双线型插值生成影像，而生成的dom时使用的双三次卷积方式生成的，只要在生成的时候将双三次修改为双线型插值即可。

3.重启系统后，启动液晶立体勾选且进程也已经开启了，但是开启立体时依然会黑屏，通常只需手工关闭StereoBuddyWnd进程，再重新将启动液晶立体勾选即可。

4.英文系统下安装的英文版本程序，“启动液晶立体”功能暂无法正常启动。

5.多模型进行实时核线编辑DEM，出现立体来回切换,立体上有时有块区域被其它方块区域覆盖显示,无法刷新，只需要将立体缩小到025倍时即可。

6.使用工具中的DEM格式转换，如果线将一nsdtf格式的DEM转换为tif格式（32位），再将该32位tifDEM转换为nsdtf格式，发现坐标发生了大概半个格网距离的偏移。

这个是由于DEM与TIFF起点不同导致，TIFF格式起点的在像素中心，如果可能的话也可以手工将转换后的DEM起点坐标进行修改。

7.DEM编辑中实时核线立体使用"切换立体"功能时,有的数据切换立体显示不对，通常是自动切换是正常的,用标记定位到其它立体也正常，建议实时核线不要使用手动切换。

8.南半球数据支持，由于手中无相关数据验证，所以如果有问题希望及时反馈。

9.数码相机校正功能扩展支持jpg等常用格式目前该功能输出格式只支持tif，没有提供输出jpg的功能，如果一定要输出jpg文件的话，需要手工在影像列表中双击影像，在弹出的界面中将文件后缀手工修改为jpg即可，所有的影像都需要一个个手工进行修改。

10.ADS40模型裁切里“合并ads”, “合并并且裁切”，“可视化选模型”三个按钮不要使用。

ReleaseNote模板

Revision History阅读说明：蓝色字为注释，范例，或者说明，黑色字为必须要的条目TABLE OF CONTENTS1.INTRODUCTION 32.RELEASE CONTENT 3 2.1S OURCE CODE DEPOSITORY3 2.2D IRECTORY STRUCTURE3 2.3L ABEL INFO4 2.4G ET THE INFORMATION FOR LABEL4 2.5B UILD ENVIRONMENT(编译环境) 4 2.6U SER PROFILE ENVIRONMENT (用户环境变量) 42.6.1wacos user profile 42.7B UILD PROCESS(编译过程介绍)43.TARGET ENVIRONMENT(部署环境需求) 5 3.1H ARDWARE REQUIREMENTS（硬件需求）5 3.2S OFTWARE REQUIREMENT（软件需求）5 3.3R UNNING CMS（启动须知，说明启动脚步的含义）53.3.1单机版53.3.2分布式53.4L IMITATION(局限性说明) 54.CONFIGURATION OF CMS(项目配置文件说明) 5 4.1配置文件54.1.1cms.properties55.EXECUTION OF DB SCRIPT(数据库脚步执行说明) 6 1.INTRODUCTION(主要简略介绍工程实现的功能，或者修复的bug)2.RELEASE CONTENT2.1Source code depositoryThe source code of software is stored in the SVN2.2Directory structureThe cms(子项目) application for FollowGood Platform is organized as a tree depicted below: the tar package is cms_demo1.tar.Z(包), uncompress it , the dir is :/opt/wacos/server /cms|-----bin|-----home|-----logs|-----tools|-----tomcat6|-----lib|-----datadb|-----metadata|-----metadatatmp|-----webapps2.3Label infoCMS_DEMO2.4Get the information for labelYou can get the information byhttp://host:8080/cms/version.htmlThe history for label(主要介绍以往版本主要功能，修复bug清单，以及解决的问题等，尽量详细，按版本倒序排列，最新版本放前面)●CMS_DEMO2因地方分类中部分省份页面变更，更新解析配置以正确解析内容●CMS_DEMO2修复BugList :Software003:解决空指针异常问题Softeare009:解决用户名没有校验问题(此部分内容为追加内容，以往的版本信息都要保留)2.5Build environment(编译环境)2.6User profile environment (用户环境变量)2.6.1wacos user profileAdd these lines in wacos user profileJAVA_HOME=$HOME/tools/ jdk1.6.0export JAVA_HOME;Notice: wacos should be the owner of “/opt/wacos/server”The Tomcat’s version is 6.02.7Build process(编译过程介绍)Now , cms only support ANT’s Compile.3.TARGET ENVIRONMENT(部署环境需求)3.1Hardware requirements（硬件需求）-Sun Ultra 10 workstation or above3.2Software requirement（软件需求）-Java Developemnt Kit(JDK) 1.6.03.3Running CMS（启动须知，说明启动脚步的含义）3.3.1单机版$cd /opt/wacos/server/cms$chmod +x *// Start CMS as root$./start.sh// Stop CMS$./stop.sh3.3.2分布式$cd /opt/wacos/server/cms$chmod +x *// Start CMS as root$./start-all.sh// Stop CMS$./stop-all.sh3.4Limitation(局限性说明)1.Now only support JDK 1.6.0 or above2.Now support above Tomcat 6.04.CONFIGURATION OF CMS(项目配置文件说明) 4.1配置文件4.1.1cms.properties目录：/opt/wacos/server/cms/home/WEB-INF/classes内容：crawl.startTime=08:00 ----爬虫开始时间crawl.intervalHour=24 ----爬虫周期crawl.depth=3 ----爬虫深度crawl.threadNum=10 ----爬虫并发线程数crawl.topNum=100 ----爬虫抓取记录数crawl.targetDir=d:/spiderdata/datadb ----爬虫数据存放目录parse.tmpDir=d:/spiderdata/metadatatmp ----xml数据临时目录index.disable.mode=0 ----爬虫程序是否要进行索引操作5.EXECUTION OF DB SCRIPT(数据库脚步执行说明)。

nextpad release note

各位，大家下午好。

欢迎各位百忙之中来现场参加这次在线的产品发布会活动，虽然这里说的是一个“产品”的发布会，但是按照产品的定义而言，下面要公布的也不能算是一个产品，因为它是没有价格的，也就是终生免费的一个产品（360？……）。

首先为了防止有人还不知道我是谁，我先自我介绍一下，我的GSDzone ID ， sataco ，目前担任 GSDzone 网站的主要负责人以及泛华测控院校产品部的负责人。

因此，从今年开始，我会在试图在中国工程教育这个领域做一些事情，希望能够真正实质性地助力培养更多未来的卓越工程师。

在本次产品发布会期间，你都可以回帖进行提问或者单纯的顶或踩，在发布会结束时会进行最后的抽奖活动，大奖将是一个以前从来没有发过的奖品，而且不是 GSDzone 的奖品，而是 next 的奖品，尽请期待。

下面，我将用类似意识流的方式给大家阐述一下这个产品 nextpad 的概念是如何形成的。

为了真正助力中国工程教育，我思考了很久，之后想到了有三个方向也许是我以后会奋斗的目标：一个就是在教学方面，目前在工程知识的教学上尚存在着很大的提升空间，很多概念和知识，现在还是通过老一套的纯公式推导或者板书的形式来进行教授，这种方式不利于学生能够真正理解透彻知识点，而且不生动，引不起学生的兴趣和求学欲望；第二个方向就是实验，图腾中那条白色的线指的是理论中所得到的结果，而黄色的线代表的是在实际情况中所得到的结果，你可以明显看出两条线是不一样的，这也代表着也许你理论学得很好，但是作为一个优秀的工程师，你必不可少地要和实际的系统或环境打交道，所以掌握你的理论知识的同时，你更需要的是通过实验来将理论与实践联系在一起，真正做到工程。

第三个方向就是创新，这个图腾也很好理解，每一个框代表的是一门学科，那么在这个方向，是要求同学们能够灵活地将各个学科的知识综合起来解决实际问题，例如你在大一大二可能学习了电工电子、机械原理等基础课程，那么在大三大四甚至研究生时就应该能够将这些基础学科综合起来，从而解决真正的问题。

Agile e6.0.1升级指南从e6.0到e6.0.1说明书

6
Software Upgrade
6
Database Dump Upgrade
7
LogiView Upgrade
9
Chapter 3 Additional Upgrade Information
10
Workflow Upgrade
11
Favorites Upgrade
11
Chapter 4 Appendix
Copy the whole installation directory Save the database (save a dump, save your configuration) Oracle 10.1.0.4 incl. SQL*PLUS must be installed on the machine At least 50 MB hard disk space must be available for the EP_ROOT application home directory, and additional 50 MB for the log files Minimum 512 MB RAM have to be available to run the database dump upgradeΒιβλιοθήκη 12Log Files
12
iii
Chapter 1
Prerequisites
Before upgrading to Agile e6.0.1 check all listed items.
General
Please make sure that all Agile services are stopped before applying the upgrade from e6.0 to e6.0.1 Stop all running 'Web Presentation Service' environments (use the admin server) Stop running 'Business Service' in all environments (use the admin server) Stop other manually started Agile e6.0 services Save your existing installation, including the database, after you have stopped all services

Release Notes

##############################################Macintosh device driver Release Notes##############################################Release1.0.0.5, Date 10th July 2008 :++++++++++++++++++++++++++++This version supports MacOS 10.5.x. Supports Serial, Parallel functionality. Fixed:+++++1) Printer pauses automatically. Printer detection is inconsistent in MacOSx10.5.x.Tested:++++++MacOSX 10.5.5.Note: Please refer Read me document before testing the driver.===== 0 =====Release1.0.0.4, Date 10th July 2008 :++++++++++++++++++++++++++++This version supports MacOS10.4.x and MacOS 10.5.x. Supports Serial and Parallel functionality.Fixed:+++++1) Support for MacOS 10.5Tested:++++++MacOSX 10.4.9 and MacOSX 10.5.===== 0 =====Release1.0.0.3, Date 4th July 2008 :++++++++++++++++++++++++++++This version supports Serial as well as parallel printer port functionality. Fixed:+++++1) Ports detection is not in sequence.Tested:++++++MacOSX 10.4.9.===== 0 =====Release1.0.0.2, Date 12th Mar 2008 :++++++++++++++++++++++++++++This version supports Serial as well as parallel printer port functionality. Note:------1) This package contains drivers as well as backend to be used CUPS.2) Tested on MacOSX 10.4.9.3) Tested with Epson Stylus C87.===== 0 =====Release1.0.0.1, Date 21th Feb 2008 :++++++++++++++++++++++++++++This version supports both internal and external serial functionality.Note:------1) Tested on MacOSX 10.4.7 and MacOSX 10.4.9.2) Tested with ZTerm application of version V1.1beta7.3) ZTerm require minimum window limit(ZTerm->Settings->ZModem Options) of 512 to avoid retries.4) Uncheck FlowControl Xon/Xoff (ZTerm->Settings->Connection).5) Parallel ports are not supported in this driver version.===== 0 =====Steps for printer configuration-------------------------------------------1) From the Desktop Finder window, locate and check the file PCIeParallel, found at /usr/libexec/cups/backend ( Type this location in Finder Menu-> Go-> Go to Folder ) 2) If present open Printer setup utility from Desktop Finderwindow->Applications->Utilities3) Click Add from the Toolbar, to open printer browser window.4) Go for default browser in the printer browser window and wait till search completes for latest drivers for the printer.5) Check the printers connected to PCIeParallel6) Click on the Printer Name and find the appropriate driver below and add the printer device to the printer setup utility.(Note: Install latest Gutenprint package available at192.168.200.231/software/MacOS/Mac Os X Utilities & Downloads)Checking for Serial Ports.1. Open Applications/Terminal2. Type > 'ls /dev'3. Find the number of PCI-Serial Ports createdOR1. Applications/SystemPreferences/Network2. Click on '+' button at the bottom of the Network Interface list.3. You can find the Interface list as combo list with labeled Interface.4. Find the number of PCI Serial Adaptors if created and its serial number as suffix. Testing Serial Ports1) Tested with ZTerm application of version V1.1beta7.2) ZTerm require minimum window limit(ZTerm->Settings->ZModem Options) of 512 to avoid retries.3) To select Serial port, ZTerm->Settings->Modem Options.4) Uncheck FlowControl Xon/Xoff (ZTerm->Settings->Connection).5) To store the received file in the selected folder selected ZTerm->Settings->Receive Folder.Uninstall Procedure1.Go to folder /System/ExtensionsDelete two .kext filesi.PCIeSerial.kextii.PCIeISASerial.kext2.Go to folder /Library/ReceiptsDelete three packagesi.PCIeISA-Serial.pkgii.PCIeParallelDskInstall.pkgiii.PCIeSerial.pkg3.Go to folder /usr/libexec/cups/backend/Delete executable Filei.PCIeParallel4.Please reboot to uninstall successfully.===== END =====。

VPOS Touch All-in-one Card Reader with Touch Scree

VPOS Touch© Property of NayaxAll rights reservedFor more information contact us at *****************Table of ContentsGeneral Information (3)Organization of the Manual (3)Device Overview (4)Device Summary (4)Device Specifications (5)Device Components (7)Device Serial Number (8)Device Cables (9)Device Connector Scheme (40-Pin) (10)Additional Accessories (Included in Box) (10)Getting Started (12)Installation (12)Device Dismantling (12)Operating and Testing (12)Configure VPOS Touch Settings in NayaxVend (13)Technician Mode (14)Appendix 1 – Tests Prior to Repair (15)Appendix 2 - FCC & IC Regulations (17)Safety and Handling Instructions (19)Environmental Guidelines (19)Warranty and Liability (19)Cleaning Instructions (19)General InformationThis section explains the classification of the manual and the purpose for which it is intended. Organization of the ManualThe user manual consists of six sections namely General Information, Device Overview, Getting Started, Appendix 1 – Tests Prior to Repair, Appendix 2 – FCC & IC Regulations and Safety & Handling Instructions.General Information section explains the purpose for which the manual is intended.Device Overview section provides an overview of the device. The summary outlines the uses of the hardware and software requirements, device configuration, and device behavior in case of any contingencies.Getting Started section explains the first steps to start using the device.Appendix 1 – Tests Prior to Repair section describes how to resolve the most frequent issues experienced prior to sending the device to the Nayax Laboratory.Appendix 2 – FCC & ICC Regulations lists all the production regulations and guidelines.Lastly, the Safety and Handling section provides guidelines on how to clean and maintain the device.Device OverviewDevice Overview section provides an overview of the device, feature highlights, device specifications and much more.Device SummaryVPOS Touch is a complete telemetry and cashless payment solution, ideally suitable for the unattended machines’ market.VPOS Touch accepts all modes of cashless payments and transmits data in real-time. The different modes of payment accepted are:▪Debit and credit cards▪Mobile and NFC payments▪Prepaid cards▪Swipe, contact and contactless cardsThe advantages of using the device are enabling easy installation, monitoring machines in real-time and a complete management solution. Our complete management solution consists of:▪Inventory Management▪Machine Management▪Transaction Monitor▪Alerts and Event System▪Reports Suite▪BI SystemFeature Highlights▪ARM, Cortex 32-bits (M4 + M7)▪High Security Encryption System: AES / DES▪External flash 64 MB, SD Card 4 GB, SD RAM 16 MB▪Anti-vandal with Dragontrail glass▪Shock and tilt detector▪Monitoring and alert of Power Down▪Decorative LED for Contact Smart Card slotDevice SpecificationsDevice ComponentsFront PanelFront Panel Color - Yellow / BlackRear SideM4 x 5 mm Typical HoleLANSIMSpeakerSAM SD CardCable ConnectorAntennaMagnetic stripe Contact slot stripeTouch buttonsContactless display touch screen Status display LEDDevice 2D SchemeDevice Serial NumberSerial number logic: PPMAPOWWYYSSSSSSDevice CablesNayax provides different configuration cables to suit different machines. The below table refers to each cable and its configurationDevice Connector Scheme (40-Pin) ArrayAdditional Accessories (Included in Box)Additional Accessories (Optional)Getting StartedGetting Started section briefly explains how to install the device on the machine, the operating and testing process and the different screens.InstallationThe latest Installation Guide version is currently available and can also be downloaded from NayaxVend. The VPOS Touch Quick Guide has been included in your box for your quick reference.Device DismantlingTo unplug the VPOS Touch connector, you must press both sides of the releasing bridge at the same time to avoid damaging the releasing bridge.Operating and Testing1.Turn on the machine.2. Once the VPOS Touch is powered-up, a Self-Test is automatically initiated that performs a SIM cardand Server Connectivity check.Note: If the device is not installed correctly, you may see an error message3.Once the VPOS Touch is fully initialized, carry out the following trial purchasesa.Cash /Credit Purchaseb.E-money (E.g. A prepaid card transaction)Once all purchases are successfully completed, the unit is fully installed and ready for use!Configure VPOS Touch Settings in NayaxVend▪Refer to the below attributes used to configure the VPOS Touch device in the NayaxVend system.▪Payment Methods - Controls the type of payments that are displayed on the Welcome screen (VISA, Mastercard, Apple Pay, Samsung Pay, etc.)▪Support WEB - Displays the website that is visible under the Menu - Contact Us function. ▪Support Phone Number - Displays the phone number that is visible under the Menu -Contact Us function.▪Technician Code - Controls the pin code to access the Technician mode screen.▪Menu Timeout - Controls the timeframe (in seconds) for the unit to return to the Welcome screen after the menu button is pressed.▪Menu Functions - Controls the options to be displayed when the Menu button is pressed. It is possible to disable the Menu button entirely or display only the selected features such as:I.Technician ModeII.Report a ProblemIII.Contact UsIV.Device InfoV.Nutrition FactsnguagesTechnician ModeTechnician Mode CommandsUnder the technician mode, three different screens are visible.The first screen consists of two buttons that are configured by logging into the Management Suite – NayaxVend DCS.The next two screens consist of a pre-defined collection of options that are listed below:Appendix 1 – Tests Prior to RepairThe below procedure needs to be carried out by the Operator before sending the device to be fixed at the Nayax laboratory.1.Connect the VPOS Touch Cable Connector to get power from the machine – Refer tobelow Image 1.2.Once the device starts to load, the following initiation messages are displayed:I.FW OKII.Init mdmIII.RSSI 99 - In this case there are three options to proceed:a.RSSI 99 - Check the External Antenna Adapter connected to the board- Refer to Image 2b.(SIM) / RST– This could refer to a SIM issue. In that case, confirm that the Simsocket is closed securely and if required, try to replace the SIM card - Refer toImage 3c.RSSI => 10– This is normal, and you can proceed to the next step.IV.Mobile operatorV.Init GPRSVI.TCPIP OKVII.Gloader Test –In case you need to install a new Firmware Version it will run:a.Gloader x.x.x TCPIP OKb.Running FW … TCPIP OKVIII.NayaxIX.Ready3.Test the following payment cards:I.Magnetic Card – In case of an error, check the Magnetic Head connection to theboard – Refer to Image 4.II.Contact Card & Contactless Card - In case of an error, send it to the Nayax LaboratoryIII.In case the speaker is not functional, check the Speaker Connection to the board –Refer to ImageAppendix 2 - FCC & IC RegulationsThis device complies with part 15 of the FCC Rules. The operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.Note: This equipment has been tested and found to comply with the limits for a Class B digitaldevice, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:▪Reorient or relocate the receiving antenna.▪Increase the separation between the equipment and receiver.▪Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.▪Consult the dealer or an experienced radio/TV technician for help.Note: The manufacturer is not responsible for any radio or TV interference caused by unauthorized modifications to this equipment. such modifications could void the user’s authority to operate this equipmentChanges or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.This device complies with Industry Canada RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation of the device.Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorisée aux deux conditions suivantes:(1) il ne doit pas produire de brouillage et(2) l’ utilisateur du dispositif doit étre prêt à accepter tout brouillage radioélectrique reçu, même si ce brouillage est susceptible de compromettre le fomctionnement du dispositif.The VPOS Touch IDs are:▪FCC ID: 2AK6L-VPOST▪IC: 10840A-VPOSTThe VPOS Touch device is available with two cellular modules. These are the two options:▪Contain FCC ID: RI7LE910NAV2, Contains IC: 5131A-LE910SNAV2 ▪Contain FCC ID: RI7LE910SVL, Contains IC: 5131A-LE910SVLSafety and Handling InstructionsIt is advised to read the manual carefully before attempting to use the device. Environmental GuidelinesIt is recommended to avoid installing the device in direct sunlight to prevent any risk of burnouts. Make sure not to expose the product to any corrosive gas or liquid. It is important to deploy the device in non-condensing conditions.Warranty and LiabilityThank you for choosing Nayax. Read the Nayax 24 months Limited Warranty Terms and Limitations included in your contract. In the unlikely event that your device needs repair service or for additional information, please contact us at *****************.Your warranty shall be void in case the device is damaged due to vandalism and/or any corrosion issues.Cleaning InstructionsYou can use a soft, dry cloth for cleaning purposes. In case your device is extremely dirty, use a small amount of alcohol. Make sure not to use organic solvents such as thinner and benzene.。

ICPReleaseNotes

RELEASE NOTESIVI Compliance Package Version 4.4These release notes contain installation and uninstallation instructions anda list of installed components for the IVI Compliance Package 4.4.Note If you are upgrading from IVI software versions earlier than IVI Compliance Package 3.0, refer to the IVI Compliance Package 3.0 Release Notes for upgradeinformation. You can download a copy of the release notes from the National Instruments Web site at /info . Enter the Info Code icp3rn .IntroductionThe IVI Compliance Package is a software package that contains IVIclass drivers and support libraries necessary to develop and useapplications that leverage IVI instrument interchangeability. TheIVI Compliance Package also is based on and is compliant with thelatest version of the instrument programming specifications definedby the IVI Foundation. You can use the IVI class drivers in theIVI Compliance Package with IVI specific drivers.IVI class drivers implement functions and attributes for controlling aninstrument within a specified class, as defined by the IVI Foundation.The IVI Compliance Package provides IVI class drivers for the followingspecifications:•IviACPwr •IviCounter •IviDCPwr •IviDigitizer •IviDmm •IviDownconverter •IviFgen •IviPwrMeter™•IviRFSigGen•IviScope•IviSpecAn•IviSwtch•IviUpconverterIVI specific drivers are drivers for the most popular instruments from allof the currently defined IVI Foundation classes and from the largestinstrument manufacturers including National Instruments, AgilentTechnologies, and Tektronix. You can create IVI specific driversyourself,or download them from /idnet. InstallationNational Instruments recommends that you close all other applicationsbefore you install the IVI Compliance Package.For system requirements, refer to the NI IVI Compliance Package Readme,which you can access by selecting Start»All Programs»NationalInstruments»IVI»IVI Compliance Package Readme.The IVI Compliance Package is included with various NationalInstruments distributions, such as National Instruments Device Drivers,Switch Executive, and Calibration Executive. You also can obtain theIVI Compliance Package as a stand-alone Web-only distribution.If you install a product that is dependent on the IVI Compliance Package,such as Switch Executive, you do not need to install this separateIVI Compliance Package because it is already included in the productinstallation.To install the IVI Compliance Package from the National InstrumentsDevice Drivers media, insert the media and follow the installationsteps.When prompted with feature selections, enable theIVI Compliance Package.To install the stand-alone, Web-only IVI Compliance Package 4.4,complete the following steps:1.Download the IVI Compliance Package 4.4 self-extracting archivefrom /downloads by navigating through the Drivers andUpdates link.2.Double-click the self-extracting archive to launch the installer.3.Click OK to begin installation.4.Follow the directions that appear on the screen.IVI Compliance Package Release © National Instruments Corporation 3IVI Compliance Package Release NotesNoteThe IVI Compliance Package Web distribution does not install NI IO Trace,formerly called NI Spy, or Measurement & Automation Explorer (MAX). NI IO Trace tracks the calls your application makes to National Instruments test and measurement drivers, such as NI-VXI and NI-VISA. You can use MAX for IVI configuration support. You can use IVI software without these components, but you will not have the features these products supply unless you install them. If you have installed other NationalInstruments products, such as the National Instruments Device Drivers media, you might already have NI IO Trace and MAX installed.If you install a National Instruments product that installs MAX after installing the Web distribution of the IVI Compliance Package, you must reinstall theIVI Compliance Package to be able to use the updated IVI configuration userinterface in MAX. You must have MAX 4.2.1 or later installed to use the IVI configuration utility in MAX.Installed ComponentsDepending on the software support you select when you install theIVI Compliance Package, the installation includes one or more of thefollowing components:•IVI class drivers •IVI class driver LabWindows ™/CVI ™ support •IVI class driver wrappers for supported versions of LabVIEW •IVI class simulation drivers •IVI-COM adapters (32-bit only)•IVI class driver examples for LabWindows/CVI, LabVIEW, and Measurement Studio •IVI Shared Components 2.2•IVI configuration plug-in for MAX 4.2.1 and later •Online helpUninstallationIf you no longer want to use IVI software components, complete thefollowing steps to uninstall them.Note If you installed the IVI Compliance Package as part of another distribution that depends on the IVI Compliance Package, you cannot uninstall theIVI Compliance Package without uninstalling the dependent product.1.Select Start»Control Panel»Add or Remove Programs.CVI, LabVIEW, National Instruments, NI, , the National Instruments corporate logo, and theEagle logo are trademarks of National Instruments Corporation. Refer to the Trademark Information at/trademarks for other National Instruments trademarks. The mark LabWindows is usedunder a license from Microsoft Corporation. Windows is a registered trademark of MicrosoftCorporation in the United States and other countries. Other product and company names mentionedherein are trademarks or trade names of their respective companies. For patents coveringNational Instruments products/technology, refer to the appropriate location: Help»Patents in yoursoftware, the patents.txt file on your media, or the National Instruments Patent Noticeat /patents . Refer to the Export Compliance Information at /legal/export-compliance for the National Instruments global trade compliance policy.© 2003–2011 National Instruments Corporation. All rights reserved.370733G-01Aug112.Select National Instruments Software and click Change/Remove .3.Select NI IVI Compliance Package 4.4 and click Remove .Note After you uninstall the IVI Compliance Package, IVI Shared Components remain on your computer. To remove the remaining components, select Start»Control Panel»Add or Remove Programs , select IVI Shared Components 2.2, and click Change/Remove .LabWindows/CVI Version SupportThe IVI Compliance Package provides support only for the latest versionof LabWindows/CVI installed on your computer. If you install the IVICompliance Package with LabWindows/CVI installed and then upgrade toa later version of LabWindows/CVI, complete the following steps tomodify the IVI Compliance Package installation to get IVI support for thelater version of LabWindows/CVI:1.Select Start»Control Panel»Add or Remove Programs .2.Select National Instruments Software and click Change/Remove .3.Select NI IVI Compliance Package 4.4 and click Modify .4.For the LabWindows/CVI Support feature under IVI Class Drivers , select Remove this feature and complete the installation.5.Repeat steps 1–3.6.For theLabWindows/CVI Support feature under IVI Class Drivers ,select Install this feature to a local drive and complete theinstallation.This process removes IVI class driver support for the previous version ofLabWindows/CVI and adds this support for the later version ofLabWindows/CVI.。

Release Notes

Oracle® TimesTen In-Memory DatabaseRelease NotesRelease 11.2.1E13080-19November 2010This document provides late-breaking information for TimesTen release 11.2.1.7.0, aswell as information that is not yet part of the formal documentation. The latest versionof this document is the readme.html file in your installation directory. Release notesmay also be updated from time to time in the documentation library at/technetwork/database/timesten/documentation/Information about TimesTen 11.2.1 releases before 11.2.1.6.0 can be found at/technetwork/database/timesten/documentation/1121-historic-183693.htmlTo install the Oracle TimesTen In-Memory Database, run setup from the installationmedia pack. For installation information, see Oracle TimesTen In-Memory DatabaseInstallation Guide. This guide can be accessed from install_dir/doc/ at the root ofthe installation media pack.This document contains the following sections:■Changes in this release■Platforms■Software requirements■Deliverables■Advance notice■Known problems and limitations■Contacting support■Documentation Accessibility1Changes in this releaseThis section lists changes between releases:■Changes for Release 11.2.1.7.0 from Release 11.2.1.6.6■Changes for Release 11.2.1.6.6 from Release 11.2.1.6.5■Changes for Release 11.2.1.6.5 from Release 11.2.1.6.4■Changes for Release 11.2.1.6.4 from Release 11.2.1.6.3■Changes for Release 11.2.1.6.3 from Release 11.2.1.6.1■Changes for Release 11.2.1.6.1 from Release 11.2.1.6.0■Changes for Release 11.2.1.6.0 from Release 11.2.1.5.21.1Changes for Release 11.2.1.7.0 from Release 11.2.1.6.6The behaviorchanges.txt file is no longer included in the installation directory. Behavior changes are included in this document.1.1.1Behavior changes in Release 11.2.1.7.0■Previous behavior: If SUBSTR() result is longer than the target column, the result is silently truncated and an insert or update succeeds with the truncated string.New behavior: If the result of SUBSTR() is longer than the target column in an insert or update statement, the operation fails with error 982: "Stringexceeds column width". For example, if column x is of type CHAR(4), SET x=SUBSTR('abcdefg',2) results in error 982. SUBSTRB() in a multibytecharacter set continues to silently truncate the string, and insert or updatecontinues to succeed with the truncated string.1.1.2New features and changes in Release 11.2.1.7.0See the "What's New" prefaces in the documentation to see the new featuresdocumented in a specific guide.■You can create an explicitly loaded global cache group in a cache grid. If the cache tables on the local grid member do not contain data that satisfies a query, then thecache instance is transferred from other grid members to the local grid member in a grid data transfer operation. If the grid does not contain the cache instance that satisfies the query, data is not loaded from the Oracle tables and the query returns no results. See Oracle In-Memory Database Cache User's Guide .■Oracle Data Provider for .NET 11.1.0.7.110 is available for Oracle TimesTen In-Memory Database. It enables fast data access for .NET applications using. This data provider supports TimesTen release 11.2.1.6.1 or later onMicrosoft Windows 32-bit and 64-bit platforms. It supports the .NET 2.0, 3.0 and3.5 frameworks with Microsoft Visual Studio 2005 or later, and .NET4.0 withVisual Studio 2010. The Oracle Data Provider for .NET is available for download on Oracle Technology Network:/technetwork/database/timesten/downloads For more information, see Oracle Data Provider for .NET Oracle TimesTen In-Memory Database Support User's Guide .■Tables with aging are not supported with track-based parallel replication. In this release, TimesTen prevents the user from including a table with aging from beingpart of a replication scheme when ReplicationApplyOrdering=1.■TimesTen is supported for SUSE 11 on Linux x86-64.■The default value for the -maxsupportlogsize daemon option has been changed from 1 to 10 MB. See Oracle TimesTen In-Memory Database Operations Guide .Note:Oracle Data Provider for .NET 11.1.0.7.110 supports OracleTimesTen In-Memory Database only. A future release of OracleDatabase Provider for .NET will support both Oracle Database andOracle TimesTen In-Memory Database.■Aging statistics have been added to the SYS.SYSTEMSTATS system table. See Oracle TimesTen In-Memory Database System Tables and Limits Reference.■Using TimesTen with IBM Java SDK 1.6 for 32-bit and 64-bit on Linux x86 is supported. To use this Java SDK, a fix from IBM is required, published as APAR IZ76406, which is included in Java 6 SR8 FP1.■The ScriptInstallDir attribute is not required to configure Oracle Clusterware with TimesTen. The attribute is deprecated in this release.1.1.3Bug fixes in Release 11.2.1.7.0■The ttMigrate utility returns exit codes. See Oracle TimesTen In-Memory Database Reference. (BugDB 8637795)■In previous releases, ttBulkCp failures returned an incorrect code. This problem has been fixed. (BugDB 9414206)■In previous releases, the -showdate daemon option was not enabled for the Server process. This problem has been fixed. (BugDB 9722055)■ A CREATE VIEW statement fails if the view definition contains a union, and one side of the union is a query that selects from a derived table that is a join. In this release, TimesTen returns an error message that describes the problem. (BugDB 9864076)■Create cache group checks if the user has the appropriate Oracle privilege. For example, it checks if the user has SELECT ON privileges on each table in the cache group. In the 11.2.1.7.0 release, the code checks for individual privileges, as well as those granted through a role. In earlier releases, it was not checking against role privileges. (BugDB 9873532)■When grid failed to allocate memory a message will be logged to the daemon log to indicate this fact. The message will have the following format: Member'memberName'failed to allocate temp space, errorcode='errNo' - 'errMessage'. (BugDB 9893472)■Public access to TimesTen objects in the Oracle database that are used for cache operations is no longer allowed. (BugDB 9957021)■In previous releases, the fractional second field of an Oracle TIMESTAMP value contained in a PL/SQL variable buffer was inadvertently modified when it was prepared for conversion into the TimesTen TT_TIMESTAMP format. This problem has been fixed. (BugDB 9903966)■SQL operations executed internally by PL/SQL may generate warnings, for example, because of low memory or replication failures. In previous releases these warnings could cause ORA-0600 errors to be emitted. In this release ORA-0600 errors do not result from these temporary warning conditions. (BugDB 9916812)■In a client/server configuration, errors in starting child server processes resulted in an "unexpected server exit" and no additional information. Now startup errors are reported. (BugDB 9934387)■Internal trace buffers are now flushed when the database is loaded into memory.Previously, trace data left over from a prior load of the database could interfere with new traces, causing errors that could result in database invalidation. (BugDB 9939628)■In previous releases, a call to the ttOptEstimateStats built-in procedure could result in an assertion when a concurrent transaction committed after deleting alarge number of rows. In this release, TimesTen returns an error if TimesTen cannot perform the estimate. The new error has the form: "Estimate statistics on owner.table failed due to too some concurrent operation; try again." (BugDB 9954300)■In previous releases, altering a cache group could cause a core dump when the TimesTen configuration tables on the Oracle database were empty. This problem has been fixed. (BugDB 9956288)■The message for error 6226 has been changed to replace the obsolete LogBuffSize connection attribute name with LogBufMB. (BugDB 9961676)■The stability of TimesTen PL/SQL after unexpected application failures is improved. (BugDB 10011855)■In previous releases, a master-master replication scheme with two-safe enabled could create a backlog of replication records that were never sent to a subscriber database. This problem has been fixed. (BugDB 10029655)■In previous releases, calls to the ttOptSetFlag built-in procedure incorrectly reset the values set by the ttOptUseIndex built-in procedure. This problem has been fixed. (BugDB 10034510)■Dynamic load operations use the SQL command cache more efficiently than in previous releases. (Bug DB 10036720)■Dynamic load operations no longer cause a round trip to the Oracle database when the parent row is already in the IMDB Cache. (BugDB 10036751)■The mit.file.reads statistic in the SYS.SYSTEMSTATS system table.keeps track of how often TimesTen reads from the file system during commitprocessing. In previous releases, this statistic was higher than log.file.reads, which keeps track of total file system reads. The mit.file.readsstatistic is now calculated correctly. (BugDB 10134912)■In previous releases, a replication agent or an XLA application could encounter an assertion failure blklen <= startIdMap->offset in thesbLogBufLRNextLocate function. This problem has been fixed. (BugDB10145152, 10194728 and 10196227)■ A problem has been fixed where an assertion could occur while executing SELECT statement through a procedure from a JDBC application. (BugDB 10167873)■In previous releases, the replication agent could crash and invalidate the database when the replication agent was reading close to the end of the in-memory logs.This problem could occur when the value of the connection attributeLogBufParallelism was greater than 1. In that case, one particular log record could cause a log strand reader to block and cause other strand-readers to read records in an incorrect order. This problem has been fixed. (BugDB 10174319 and 10176689)■In previous releases, a bad pointer caused an assertion in thesblogCtnWrapComplete function. This problem has been fixed. (BugDB10176825)■ A problem has been fixed where timing issues after a ttCWAdmin -init operation could generate false positives. (BugDB 10208113)■In previous releases, global dynamic AWT cache groups checked the Oracle tables for unique primary keys when inserts were performed on the TimesTen cachetables. This uniqueness check no longer occurs, which enables inserts to take placein TimesTen cache tables when the Oracle database is not available. (BugDB10211940)■In previous releases, when a direct-linked application was terminated abnormally, other active connections or subsequent connections could cause databaseinvalidation. This problem has been fixed. (BugDB 10008657 and 10214446)■An assertion could occur when parallel replication was enabled. The transmitter would crash when reading close to the end of the log, causing an incorrect check that failed when a connection changed its replication track number. This problem has been fixed. (BugDB 10218953)■ A problem has been fixed where parallel replication would hang while running ttrepadmin -dsn DSN-receiver list. (BugDB 10223328)1.2Changes for Release 11.2.1.6.6 from Release 11.2.1.6.5■ A problem has been fixed where, if a secondary group was chosen during the installation and the TimesTen daemon is started by the root user, the daemon would run under the primary group rather than the intended group. (BugDB9968811)■For AIX on POWER systems, a problem has been fixed in which a misplaced memory barrier could lead to an assertion failure insbLogStrandGetNextRecord. (BugDB 10008972)■ A problem has been fixed where information about the group that owned the database was incorrectly removed from the database when duplicating orrestoring the database. This caused subsequently created log files to have incorrect ownership, group, and/or permissions. (BugDB 10020189)■ A problem has been fixed where the delete of the dummy row generated for concurrency control might be incorrectly treated as a deferred delete of AWT cache group. This might cause an error to be returned when the member attempted to reload the instance after it had been transferred or unloaded. (BugDB 10023143)■ A problem has been fixed where a mutex used for cache grid concurrency control might be released by a process other than the process that acquired the mutex.This problem could cause an assertion failure. (BugDB 10049032)1.3Changes for Release 11.2.1.6.5 from Release 11.2.1.6.4■You can use the ttRepStateGet built-in procedure to return the grid state as well as the database role after failover in an active standby pair grid member. See Oracle TimesTen In-Memory Database Reference for details.■ A problem has been fixed where tracing could cause a database to become invalidated. (BugDB 9088582 and 9940513)■ A problem has been fixed where a FIRST N in a SELECT query with a SET MINUS operator and many joins would choose a bad plan, consume a largeamount of temporary space and not execute. (BugDB 9867351)■ A problem has been fixed where an assertion failure could occur when the allocated buffer to store the foreign key of a dynamic load was too small. (BugDB 9924227)■Concurrent operations on detail tables of a materialized view could sometimes cause the materialized view to get out of sync. (BugDB 9977046)■In previous releases, durable commits could continue after the recovery of a failed standby master node in an active standby pair with RETURN TWOSAFE DURABLE COMMITS specified. This problem is fixed. (BugDB 9296545)■ A warning message is now included in the ttmesg.log when an error occurs with the configuration of HugePages on Linux systems. (BugDB 9582712)■Array binds to PL/SQL are not supported in TimesTen. In previous releases, attempts to bind an array would not return an error message, in some cases. Now the error message ORA-1335 "feature not supported" is returned when the calling program tries to specify an array (of more than one element) to a PL/SQLprocedure call. (BugDB 9645256)■ A problem has been fixed where a multi-table query with a LIKE predicate that passed a string whose length exceeded the width of the target column did nothave optimal performance and would take longer to complete than expected.(BugDB 9647431)■ A problem has been fixed where the ttbackupstatus built-in procedure would return the name of a backup file, even after a the ttBackup operation had been terminated before completing the backup. (BugDB 9658978)■Previously, the selectivity of the LIKE predicate with patterns ending in the wildcard character (e.g. "starts_with_this%") was underestimated, causing the optimizer to pick suboptimal plans for queries with an AND condition. (BugDB 9741326)■ A problem has been fixed where a ttMigrate operation would fail when attempting to migrate a PL/SQL package that contained multibyte character set comments. (BugDB 9747278)■In previous releases, SQLFetch and SQLFreeStmt(hstmt, SQL_CLOSE) could, in some circumstances, return the underlying error code (846 or 994) rather than trigger a failover. In this release, a failover notification is returned. (BugDB 9795626)■In previous releases, when permanent space was exhausted, a cache grid assertion failure could occur. This problem has been fixed. (BugDB 9871235)■ A problem has been fixed where the status report that is displayed when a user calls ttRepAdmin -showstatus would incorrectly show fewer receivers than transmitters. This problem occurred when using parallel replication. (BugDB9837882)■ A problem has been fixed where applications that use PL/SQL procedures could consume a lot of memory. (BugDB 9846145)■ A problem has been fixed where receiver thread information would continue to appear in the status report that is displayed when a user calls ttRepAdmin-showstatus even after the receiver had been disconnected. This problemoccurred when using parallel replication. (BugDB 9850072)■In previous TimesTen 11.x releases, if the database was created group restricted, and there was a failure to change group ownership of a log file, it could cause the database to become invalidated. This has been fixed. TimesTen now retrieschanging group ownership and returns more details about the operating system error if a failure occurs. (BugDB #9891312)■In previous 11.2.1 releases, use of an unreplicated XLA bookmark on a standby database in an active standby pair scheme could stop replication between theactive and standby stores and also lead to high CPU usage. This problem has been fixed. (BugDB 9800186)1.6Changes for Release 11.2.1.6.1 from Release 11.2.1.6.0■In previous releases, on AIX systems, the user had to call setsockopt at the kernel level to get the benefits of the TCP_RFC1323 option. It is no longernecessary for the user to make this call. TimesTen makes the call by default.(BugDB 6800684)■ A problem has been fixed where a disconnect from a standby store in an active standby pair with cache grid could hang. (BugDB 9538780)■In previous releases, creating many joins in a large materialized view could hang.This problem has been fixed. (BugDB 9581951)■TimesTen now returns ODBC error S1000: Unable to load NLS initialization data from /bogus/nls/data if the TimesTen clientdriver cannot find or load NLS files. (BugDB 9595956)■In previous releases, a replication agent could fail with this assertion failure: eolCnt + eofCnt == logc->strandCnt. This bug has been fixed. (Bug9644085).■During an upgrade from previous 11.2.1 releases to 11.2.1.6.0, the replication agent could fail to start due to error TT2211: Referenced column P.TRACK_ID not found>. This problem is fixed. (BugDB 9733793)1.7Changes for Release 11.2.1.6.0 from Release 11.2.1.5.21.7.1Behavior changes in Release 11.2.1.6.0■New behavior: The results for addition and subtraction with DATE and TIMESTAMP types for INTERVAL MONTH are not closed. For example, adding 12 months to the DATE or TIMESTAMP of '2004-02-29' results in a date arithmetic error (TimesTen error message 2787) because February 29, 2005 does not exist.(2005 is not a leap year.) Adding INTERVAL '1' MONTH to DATE'2005-01-30' results in the same error because February never has 30 days.This behavior is documented in Oracle TimesTen In-Memory Database SQL Reference, but the code did not return an error previously.Previous behavior: If the date is the last day of the month or if the resulting month has fewer days than the day component of DATE, then the result is the last day of the resulting month. Otherwise, the result has the same day component as DATE.Use the ADD_MONTHS function to get the old behavior. For example,ADD_MONTHS(DATE '2004-02-29',12) gives the result as DATE'2005-02-28', the last day of the month. ADD_MONTHS(DATE'2005-01-30',1) results in DATE '2005-2-28', the last day of the month.■The SELECT privilege has been granted to PUBLIC on theSYS.SYSTEM_PRIVILEGE_MAP and SYS.TABLE_PRIVILEGE_MAP systemtables. Public synonyms have also been created for these two tables.■JDBC client/server driver does not validate the index parameter in PreparedStatement.set XXX() calls. Validation occurs duringPreparedStatement.execute() calls.1.7.2New features and changes in Release 11.2.1.6.0See the "What's New" prefaces in the documentation to see the new features documented in a specific guide.■You can perform a global query on cache tables and noncache tables across all nodes in a cache grid. You can also unload a cache group on all grid members by specifying a global unload operation. Use the GlobalProcessing optimizer flag.For a detailed description, see the Oracle In-Memory Database Cache User's Guide.■TTClasses now supports PL/SQL IN, OUT and IN OUT parameters and REF CURSORs.■User-defined parallel replication can be configured for applications that have predictable transactional dependencies and do not require the commit order on the source database to be the same as the commit order on the target database.User-defined parallel replication is available for replication schemes that are not active standby pairs. See Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for more information. This feature includes:- New database attributes ReplicationParallelism andReplicationApplyOrdering and the connection attributeReplicationTrack.-New SQL SET REPLICATION_TRACK clause of the ALTER SESSION statement.-The new TT_REPLICATION_TRACK ODBC connection option for the SQLSetConnectOption ODBC function.-The new setReplicationTrack() method of the TimesTenConnection JDBC classThe ALTER E INDEX operation is not permitted when user-defined parallel replication is used and replication agent is running.■Oracle Clusterware can be configured with a cache grid by setting the GridPort attribute in the cluster.oracle.ini file. See Oracle TimesTen In-MemoryDatabase TimesTen to TimesTen Replication Guide.1.7.3Bug fixes in Release 11.2.1.6.0■In previous releases, if you did a client-only install into a root directory, TimesTen would fail to find TimesTen servers during a Client DSN setup. This problem has been fixed. (BugDB 9261243)■ A problem has been fixed where a flush cache group operation would hold row locks on child tables. This problem could block an update statement that touched the child table. (BugDB 9359437)■In previous releases, executing a query against multiple outer joins with the set operators UNION, MINUS or INTERSECT could result in abnormal termination.This problem has been fixed. (BugDB 9382127)■ A problem has been fixed where the cache agent would not start if the ORA_NLS, ORA_NLS10 and ORA_NLS33 variables were set in the environment of theTimesTen main daemon. (BugDB 9382534)■ A deadlock or lock timeout error that could be encountered during a parallel ttMigrate restore operation has been fixed. (BugDB 9388441)■In previous releases, an autorefresh polling query incorrectly used a full table scan.In this release, the query uses an index. (BugDB 9434677)■An assertion failure that resulted from an inconsistency in TimesTen internal lock structures has been fixed in this release. (BugDB 9436967)■In previous releases, an assertion could occur if the total number of rows for a single value needed more than 65K pages in a bitmap index and subsequent fast recoveries would hang. This has been fixed. (BugDB 9445235)■In previous TimesTen 11.2.1. releases, replication would fail during an ALTER REPLICATION operation when replicating from a TimesTen 11.2.1.x release to a pre-11.2.1 release. This has been fixed. (BugDB 9447493)■ A problem has been fixed for Windows systems where Shared Memory IPC client server connections would fail sometimes. (BugDB 9478491)■The SQL command ID is included as output to ttXactAdmin. This ID is helpful as input for the built-in procedure ttSQLCmdCacheInfo to associate the SQL statement with the ID. (BugDB 9496444)■ A problem has been fixed where a TimesTen daemon disconnect would fail with an error -8 in the StopManaging function if a process had exited ungracefully.(BugDB 9499437)■ A problem has been fixed where projected constants in a JOIN of tables and views could create duplicate result column names. (BugDB 9503696)■In previous releases, when timestamp based aging is used, rows with date values in the future could be aged out. This problem has been fixed.(BugDB 9541351)■ A problem has been fixed where PL/SQL procedures could be stored incorrectly in the database. Any attempt to use these procedures would result in a crash.(BugDB 9542428)■In previous releases, when the value of the LogBufParallelism attribute was greater than 1, it could cause the transmitter in the replication agent to crash. This problem has been fixed. (BugDB9588242)2PlatformsEnvironment32-bit64-bit Compiler notesMicrosoft Windows 2000, Windows XP, Windows Vista and Windows Server 2003 and 2008 for Intel IA-32 and EM64T and AMD64 CPUs.Yes Yes Compiled and tested withIntel 8.VS .NET 2003, VS 2005 andVS 2008 are also supported.To use the TimesTen debuglibrary, you must use VS.NET 2003.Asianux 2.0 and 3.0 for Intel IA-32 and EM64T and AMD64 CPUs.Yes Yes Compiled and tested withIntel 9.1.gcc 3.4.6 and 4.1.0 are alsosupported.TimesTen is supported on Oracle VM guest x86 and x86-64 operating systems on Oracle Linux 4 and 5 or Red Hat Enterprise Linux 4 and 5 systems.Solaris 9 and 10 for UltraSparc CPUs.Yes Yes Compiled with Sun Studio 11.Shipped with a TimesTen client library compiled with gcc 3.2.3.Solaris 10 for x86-64.No Yes Compiled with Sun Studio 10. Tested on AMD64 CPUs.SUSE Linux Enterprise Server 10 for Intel IA-32 and EM64T and AMD64 CPUs.Yes Yes Compiled and tested with Intel 9.1.gcc 3.4.6 and 4.1.0 are also supported.SUSE Linux Enterprise Server 10 for Itanium2 CPUs.No Yes Compiled and tested with Intel 9.1.gcc 3.4.5 and 4.1.0 are also supported.SUSE Linux Enterprise Server 11 for Linux x86-84No Yes gcc 4.3Red Hat Enterprise Linux 4 and 5 for Intel Itanium2 CPUs.No Yes Compiled and tested with Intel 9.1.gcc 3.4.5 and 4.1.0 are also supported.Red Hat Enterprise Linux 4 and 5 for Intel IA-32 and EM64T and AMD64 CPUs.Yes Yes Compiled and tested with Intel 9.1.gcc 3.4.6 and 4.1.0 are also supported.Oracle Linux 4 and 5 for Intel IA-32 and EM64T and AMD64 CPUs.Yes Yes Compiled and tested with Intel 9.1.gcc 3.4.6 and 4.1.0 are also supported.Monta Vista Linux Carrier Grade Edition Release 4.0 and 5.0 for Intel IA-32, EM64T and AMD64 CPUs.Yes Yes Compiled and tested with Intel 9.1.gcc 3.4.6 and 4.1.0 are also supported.HP-UX 11i v2 and 11iv3 for PA-RISC.Yes Yes Compiled and tested with the HP compiler.HP-UX 11i v2 and 11iv3 for Itanium2.Yes Yes Compiled and tested with the HP compiler.AIX 5L 5.3 and 6.1 for POWER CPUs.Yes Yes Compiled and tested with the AIX compiler.Mac OS X 10.6Yes No Compiled and tested with gcc 4.2.1.Environment32-bit 64-bit Compiler notes3Software requirementsFor software requirements, refer to Oracle TimesTen In-Memory Database Installation Guide.4DeliverablesYou should receive the following with your copy of the Oracle TimesTen In-Memory Database:■Release Notes. This document (which you are now reading) covers late-breaking information not included in the formal documentation.■Oracle TimesTen Media Pack. The media pack includes the Oracle TimesTen libraries and executables, demo programs, utilities and online documentation. The documentation included on the media pack consists of:-Oracle TimesTen In-Memory Database Release Notes (Part Number E13080).See the description above.-Oracle TimesTen In-Memory Database Installation Guide (Part Number E13063). See the description above.-Oracle In-Memory Database Cache Introduction (Part Number E14261). This guide describes the features of Oracle In-Memory Database Cache andprovides information to help developers plan an IMDB Cache application.-Oracle TimesTen In-Memory Database Operations Guide (Part Number E13065). This guide provides information about configuring TimesTen andusing the ttIsql utility to manage a database. It also provides a basic tutorial for TimesTen.-Oracle TimesTen In-Memory Database C Developer's Guide (Part Number E13066). This guide describes how to compile and link your C applicationwith Oracle TimesTen and how to set up and work with Oracle TimesTendatabases. It covers topics that include error handling, event management and performance tuning. It also provides a reference for C language-specific APIs.-Oracle TimesTen In-Memory Database Java Developer's Guide (Part Number E13068). This guide describes how to compile and link your Javaapplication with Oracle TimesTen and how to set up and work with OracleTimesTen databases. It covers topics that include error handling, eventmanagement and performance tuning. It also provides a reference for Javalanguage-specific APIs.-Oracle TimesTen In-Memory Database TTClasses Guide (Part Number E13074). This guide describes the Oracle TimesTen C++ Interface Classeslibrary. The library provides wrappers around the most common ODBCfunctionality.-Oracle TimesTen In-Memory Database PL/SQL Developer's Guide (Part Number E13076). This guide describes and explains how to use PL/SQL in the TimesTen database. It is intended for anyone developing PL/SQL-basedapplications for the Oracle TimesTen In-Memory Database.-Oracle TimesTen In-Memory Database PL/SQL Packages Reference (Part Number E14000). This guide provides a reference to all PL/SQL packagesavailable for use with the TimesTen database. It is intended for anyonedeveloping PL/SQL-based applications for the Oracle TimesTen In-MemoryDatabase.。

ESI VA ONE安装说明初版的进一步安装说明

1）如果你即将安装ESI软件，包括VAOne，需要将所有license file 里面的feature进行合并，注意删除里面重复的Server Definition 行，下载文件里面的license file已经被合并过了；
2）注意各软件的版本高低，应该先安装高版本ESI软件里面的License Server，后面的软件就可以不用再安装License Server了；3）系统变量只要一个即可，PAM_LMD_LICENSE_FILE=<port no>@<computer name>；
4）flexlm文件夹通常由安装程序自动生成在C盘根目录下；
5）node-locked license里面的features也是可以被Flexnet License Server读出的，只要你合并进了所有的features；
6）flexlm文件夹里面的那个Registration Entries文件是安装别的ESI软件生成的，安装VAOne不是必需的；
7）下载的flexlm文件夹里面那个*.log文件就是license server 使用的log文件，不需要新建额外的log文件了；
8）为了方便，需要勾选License Server配置页面的Use Services 和Start Server at Power Up这两个参数，同时注意lmtools的32bit 和64bit的区别，ESI软件用32bit的；
9）下图是我电脑（Windows 7 Ultimate SP1 64bit）里面所有的ESI 软件，都能共存并正常运行；
10）License File里面的Server行，Network card no的输入不是必需的。

Hao007网站 jackie.lee。

SINUMERIK和SIMODRIVE配置器（NCSD 2006-1a）说明书

ReadmeNCSD2006-1aE1.doc:SINUMERIK and SIMODRIVE Configurator (NCSD 2006-1a)1. Important Configuration Notes1.1 The NCSD Configurator is a selection aid and does not replace the project configuration!W e do not assume any responsibility for the correctness and completeness of the configuration.P lease check if the configuration complies with the currently applicable project configurationguidelines!1.2 Be aware of the selection predefined under “Global Settings“.S IMODRIVE 611 analog and 1FT5 AC servo motors are no longer included in NCSD 2003-2 or l ater. Older projects still including SIMODRIVE 611 analog and 1FT5 motors cannot therefore be loaded into NCSD 2006-1a.1.3 If direct absolute measuring systems are used on SIMODRIVE 611 universal/digital controllerswith a second measuring system input, additional electronic points are to be considered for this absolute encoder.1.4 Be also aware that the NCSD Configurator does not include all connecting cables. This mainlyrelates to the PROFIBUS DP cables and connections! For more information, please refer to the wiring diagrams of the corresponding component of the NC 60-2004 catalog or NC 60-2006.2. Important General Notes2.1 Compared to the NCSD version 2005-2a, the SINUMERIK and SIMODRIVE Configurator2006-1a has been developed further (see 3).2.2 The NCSD language versions English/French/Italian/Spanish/Chinese are updated in parallelto the German version. From the NCSD version 2005-1d, two further languages are incorporated: Russian and Czech. From the NCSD version 2005-2a, one further language is incorporated: Swedish. With NCSD 2006-1a or later, the Configurator is also available in Polish.2.3 The current versions 2001-2MMC and 2001-3PCU of the SINUMERIK and SIMODRIVEConfigurator used so far still exist and the components used up to now (MMCs, OPs, NCUs) can still be ordered in the new business.2.4 The NCSD 2006-1a Configurator can be executed on a PC under the operating systemsWindows NT 4.0 (service pack 3 or later), Windows 2000 or Windows XP.The executability under Windows 95, Windows 98 and Windows ME has not been tested.2.5 Due to the structural extension of the Configurator with regard to the control-converter interfaces(PROFIBUS/drive bus) e.g. for POSMO drives and 840 Di as well as due to new operator components instead of the components used so far, the new version is NOT downwardcompatible with older MMC versions such as the NCSD Configurator 12/99, 2000-1, 2001-1 and 2001-2 or to the SimoPro, SinuKonf predecessor programs.This means that existing project files from these systems CANNOT be loaded and edited with the present version of the Configurator! If components - which are no longer included in new NCSD Configurators - are deleted in project files used so far, these project files can also be loaded in later NCSD Configurators and edited with these Configurators.2.6 Selection and assignment of power units and control modules for the individual motor:When selecting a motor, first of all a suitable power unit with control (SIMODRIVE 611 digital High Performance) is assigned automatically. The control module can be adjusted manually to the individual motor under screen form “Drive module”.When changing motor data - e.g. by selecting and setting reduced motor data or changed motor over-temperature - a suitable power unit with control (SIMODRIVE 611 digital High Performance) is assigned again automatically. Please note that the control module may need manualadjustment.3. Extensions/Modifications Compared to the NCSD 2005-2a Version3.1 Controllers: + 802C base line: SIMODRIVE base line A replaces SIMODRIVE base line+ 840D Safety Integrated: offset “with DMP compact modules“+ PCU 50.3 added+ New electronic handwheels+ Handheld unit also with 3-wire converters3.2 Drives: + SIMODRIVE base line A replaces SIMODRIVE base line:New converter, the 1FK7 motors are no longer permanently assigned tothe converters, 1FK7 motors only with multi-pole resolvers+ 1FT6 105-8AF7.-…. motor only with 10 mm2 power cable(6 mm2 power cable discarded)+ Series reactor for 1FE1 052-4HD.0-…./1FE1 052-4HG.1-…./1FE1 053-4HH.1-…. motors automatically entered in the parts list+ 17 new 1FE1 motors:1FE1084-6WX.1-1B../…. 091-6WS.0-1B../041-6WM.0-1BA./….092-6WR.0-1B../….115-6WT.1-1BC../…. 144-8WL.1-1BA../….147-8WQ.1-1BC.145-8WQ.1-1BC./….….…. 072-4WL.1-1BA./…. 073-4WT.1-1BA./…. 084-4WP.1-1BA./092-4WV.1-1BA./…. 093-4WM.1-1BA./….084-4WT.1-1BA./….…. 094-4WU.1-1BA./…. 106-4WR.1-1BA./…. 106-4WS.1-1BA.+ modified 1PH7 options3.3 General: + New language: Polish4. Modifications in NCSD 2006-1a Compared to the NCSD 2006-1 Version- Correct module design SINUMERIK with PCU 50.3- Correct order number in PROFIsafe with IM 151 HF- Mini handheld unit now again with cable distributerFor information on how to install the Configurator NCSD 2006-1a,please refer to "InstallNCSD2006-1aE1.doc".file.。

VAOne资料

Use VA One for prediction of environments in launch vehicles and spacecraft and prediction of response due to random vibro-acoustic environments.
VA One space customers : NASA, Lockheed, Boeing, Northrop, EADS CASA, ESA and many others
Quickscript Matlab toolbox C/C++ developers kit
Use for customization and productivity enhancements
Example SEA models
Typical VA One aircraft models
Use VA One for interior noise modeling and “sound package” design
Example SEA models
Typical VA One marine models
Use VA One for shipboard and underwater radiated noise modeling
Exampll VA One spacecraft models
VA One
Main Extension modules
Foam Module
Use for advanced Foam/Fiber models
Stress Module
Use for failure analysis
Periodic Module

Notes客户端配置说明(R8新版)-1

Notes客户端配置说明(R8新版)-11．安装前的准备1.备份原有的用户ID将Notes安装目录Data子目录下的当前用户 ID文件（如betjadm 用户的ID文件“betjadm.id”）拷贝到其它目录下备用。

2.备份本地邮件数据库文件如果在本地进行过邮件数据库设置，还应备份本地邮件数据库文件，即“用户名.nsf”文件。

该文件在Notes安装目录的Data子目录下。

备份此文件的目的是保留用户在本地的个人邮件。

另外用户应备份Notes安装目录的Data子目录下的names.nsf文件。

备份此文件的目的是保留用户已经设置的个人通讯录等设置。

若Notes安装目录的Data子目录下没有该文件，请跳过此步。

3.卸载原先安装的Notes R5.0版本的客户端软件卸载完成后，应将原安装目录改名或者删除。

4.h osts文件的检查在命令行运行notepadC:\WINDOWS\system32\drivers\etc\hosts，打开hosts文件，检查Domino服务器IP 地址及主机名是否在其中，如果不在则添加，我校以前安装过Notes的用户不需要添加。

如需要请将以下加入hosts文件：10.128.65.16 nuist2．安装Notes R8.0.2客户端首先从校办主页下载客户端，然后双击C1MA9SC.exe，进入安装界面，如图1所示，单击“下一步”继续安装。

图1 安装向导界面如下图，安装文件解压的路径可以通过“更改”按钮来改变，使用默认路径直接单击“下一步”继续。

图2 解压文件保存界面完成了上图的操作后，进入图3所示的界面，显示解压文件进度。

图3 文件解压进度界面解压完成后安装程序自动执行，显示安装界面，如图4。

图4 准备安装界面单击“下一步”继续安装图5 安装界面选择“我接受该许可协议中的条款”，并单击“下一步”，继续安装，如下图所示。

图6 许可证协议界面在用户姓名和单位处分别填写用户的相关信息，如“huangxl”和“nuist”，并单击“下一步”，如图7图7 填写用户信息界面如下图，选择程序安装路径，默认情况安装在C盘下，用户可以点击“更改”来改变程序安装路径，点击“下一步”继续程序的安装。

VA2000 Series VA1000 Series User's Guide

VA2000 Series VA1000 Series User's GuideCopyrightCopyright ? 1999 by AOpen Inc. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, without the prior written permission of this company.DisclaimerAOpen Inc. makes no representations or warranties, either expressed or implied, with respect to the contents hereof and specifically disclaims any warranties, merchantability or fitness for any particular purpose. Any software described in this manual is sold or licensed "as is". Should the programs prove defective following their purchase, the buyer (and not this company, its distributor, or its dealer) assumes the entire cost of all necessary servicing, repair, and any incidental or consequential damages resulting from any defect in the software. Further, this company reserves the right to revise this publication and to make changes from time to time in the contents hereof without obligation to notify any person of such revision or changes.All brands or product names mentioned in this manual are trademarks or registered trademarks of their respective companies.CHAPTER 1-KEY FEATURES................................................................................................- 1 -1.1K EY F EATURES. (1)CHAPTER 2-AOPEN VA2000 / VA1000 SERIES SETTING.............................................- 3 -2.1VA2000/VA1000S ERIES L AYOUT V IEW. (3)2.2P ACKAGE C ONTENTS (3)2.3S YSTEM R EQUIREMENTS (4)2.4H ARDWARE I NSTALLATION (4)CHAPTER 3-DRIVER INSTALLATION (WINDOWS 98 SE/2000/ME)............................- 7 -3.1D RIVER I NSTALLATION FOR W INDOWS 98SE/2000/XP.. (7)3.2D RIVER I NSTALLATION FOR W INDOWS M E (9)3.2C OMPONENT C HECK-OUT (10)CHAPTER 4-OPENREMOTE.................................................................................................- 11 -4.1I NSTALL O PEN R EMOTE.. (11)4.2G ETTING S TARTED (11)4.3H OW TO USE O PEN R EMOTE (12)CHAPTER 5-AOPEN DRIVER LIVE UPDATE...................................................................- 14 -Chapter 1-Key FeaturesWelcome to the world of AOpen Video Station VA2000 / VA1000 Series. With this multimedia product, you can use it as a convenient tool for multiple purposes including video conferencing, video editing, class presentation, or even entertainment. The jumperless design and PnP (Plug & Play) implementation simplify the tedious installation process.1.1 Key FeaturesReceive TV broadcasts: 125 channel cable/antenna-ready TV tunerExternal inputs for video capture: AV and S-video inputs for external video resources like cameras and VCRs.Wireless remote control included: Channels up/down, Volume up/down.Full motion video captureStill frame video captureExternal interface: 75 ohm IEC coaxial input (cable TV), composite (RCA) input,S-Video (SVHS) input, audio input, and line audio outputWDM Capture Driver SupportWindows 98SEWindows MEWindows 2000Windows XPModel Comparison tableYes Yes Yes Yes Yes VA2000 MAX-SNT6 ConexantCX23416No Yes Yes Yes Yes VA2000 MAX-NT6 ConexantCX23416Yes Yes Yes Yes Yes VA1000 MAX-NT1 ConexantCX23881VA1000SAA7133 No Yes Yes Yes Yes POWER-NT3VA1000 MAX SAA7130 No Yes Yes Yes Yes VA1000 Lite2 SAA7130 No Yes - Yes YesChapter 2-AOpen VA2000 / VA1000 Series Setting2.1 VA2000 / VA1000 Series Layout ViewVA2000 SeriesVA1000 Series2.2 Package ContentsVideo Station VA2000 / VA1000 Series CardRemote Control and Receiver CableCD of VA2000 / VA1000 Series Drivers2.3 System RequirementsIBM PC or compatiblePentium III 600MHz CPU or better processorMinimum 128 MB memoryOne free PCI slot and IRQVGA and with DirectDraw driver supporting 15 bit color or higherMicrosoft Windows 98SE/2000/Me/XPTV antenna or cable from CATVSound cardSpeakers for audio outputCD-ROM drive2.4 Hardware InstallationCaution:Static electricity can severely damage electronic parts, Take these precautions: Before touching any electronic part, drain the static electricity from your body. You can do this by touching the internal metal frame of your computer while it's unplugged.Don't remove a card from the anti-static container until you are ready to install it. When you remove a card from your computer, place it back in its container.Don't let your clothes touch any electronic parts.When handling a card, hold it by its edges, and avoid touching its circuitry.2.4.1 Please follow the steps shown below to install the card into yourcomputer:1. Turn off all your computer power and any peripherals.2. Select an available PCI slot and remove the slot cover, screw, etc.3. Put the Video Station VA2000 / VA1000 SERIE S card firmly into the PCI slot until itsnaps in place and secure the card by replacing the screw you remove from step 2. 4. Plug the TV cable into the antenna adapter input of Video Station VA2000 / VA1000SERIES.2.4.2 For TV watch on your PCConnect the TV antenna or cable with the antenna input.Connection between the “Speak out” or “Line out” connector of your sound card and the speaker.Connector of remote control sensor cable.2.4.3 For External video sources such as VCR, VCD/DVD player, orcamcorderConnector of the AV cable / S-Video for Video equipments.Connection between the audio output of card and the “Line in” of your sound card.Connection between the “Speak out” or “Line out” connector of your sound card and the speaker.VA2000 SeriesVA1000 SeriesChapter 3-Driver Installation Chapter 3-Driver Installation(Windows 98 SE/2000/ME)Prior to installation, it is highly recommended that all application programs should be disabled such as anti-virus software and system monitoring applications.3.1 Driver Installation for Windows 98SE/2000/XPOnce your system is done booting, Windows will detect new hardware and started with the “Add New Hardware Wizard”. Please Click “Cancel” to continue. All you have to do now is follow the steps described below one by one to finish the installation.For the driver installation steps of VA2000 / VA1000 Series driver1. Start Windows and insert the AOpen Installation CD disc into the CD-ROM drive.2. The AOpen Installation Wizard will appear, please select “D river” to continue.3. Please Click “Install”, now start installing the driver.for VA2000 / VA1000 SERIES. Click “OK” to end up driver installation.5. For Windows98 SE, must to restart your system. Please Click “Yes” to restart yourcomputer.(Windows98SE)3.2 Driver Installation for Windows MeOnce your system is done booting, Windows will detect new hardware and started with the “Add New Hardware Wizard”.1. Please select “Specify the location of the driver (Advanced)” and Click “Next” tocontinue.2. Please Deselect “Removable Mdeia” and “Specify a location” and Click “Next” tocontinue.3. Click “Finish” to continue.4. Please keep going install driver. The step the same as Section 3.1?Step 13.2 Component Check-outGo to | Start | Setting | Control Panel | System | and double click System icon.Go to Device Manager to check out if the driver has been installed.VA2000 SeriesYou can found “AOpen VA2000 Video Encoder”component in “Sound, video and game controllers”VA1000 SeriesCapture chipset is Philips SAA713x:You can found “AOpen VA1000” and “AOpen WDM TV Tuner” component in“Sound, video and game controllers”Capture chipset is Conexant CX23881:You can found “AOpen VA1000 Capture”, “AOpen VA1000 Crossbar” and “AOpenVA1000 TV Tuner” component in “Sound, video and game controllers”Chapter 4-OpenRemoteIntroductionWelcome to use AOpen OpenRemote. With this tool, you can easy for use remote controller to remote your application. You can define any button of remote controller to mapping keyboard button for any application. You are able to enjoy a convenient remote function. 4.1 Install OpenRemote1. Start Windows and insert the AOpen Installation CD disc into CD-ROM drive.2. Please click the OpenRemote to run the program.4.2 Getting StartedWhen you finished install OpenRemote, A tray icon will show in right-down corner.Receive a remote controller button4.3 How to use Open Remote 1. Press Function UP/DOWN buttonof remote controller to select anitem what you want to remote. Orclick Open Remote tray icon andclick UP/DOWN/ITEM icon toselect an item what you want toremote.2. Select an item and Press OKbutton of remote controller. Andpress remote controller button toremote your AP.D. How to use Remote UtilityYou can use Open Remote Utility tosetting any remote controller button to mapping any AP.Run Open Remote Utility.[Start-->Programs-->OpenRemote-->Utility] .Up/Down: Move up/downremote item.Add: Added a remote item.Delete: Delete a remote item.Modify: Modify selectedremote item (Shown on asfollowing.)Exit: Exit Remote UtilityFile Name: Specify an AP path for you want to be remote. Press Power button of remote controller will launch this AP.Remote Button: Define remote controller to mapping any key for yourspecify an AP.Chapter 5-AOpen Driver Live UpdateLive Update wizard is AOpen driver instant service. It can support:Auto detects TV tuner driver version.Auto link to AOpen driver FTP web service.Auto check AOpen web driver information.Auto downloads newer driver from AOpen web.1. Start Windows and insert the AOpen Installation CD disc into CD-ROM drive.2. Please click the AOpen Driver Live Update to run the program.3. If your driver same with the latest version AOpen currently provide, then Live Updatewills info you.4. If Live Update found any new driver exist. It will show information about your driverversions. And click OK to continue.5. Please select an FTP server to download it.6. During download process, the Live Update banner will share information about newAOpen products with you. You may click the banner to get more information.。

1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。

UPGRADING Instructions
VA One 2006.1
3
RELEASE NOTES
© 2007 ESI Group
(released: Feb-07)
4. Ensure that there is a license file for VA One saved locally on the computer (for example c:\Program Files\ESI Software\vaone.lic)
5. From the Control Panel select the Environment Variables button on the Advanced tab of the System utility dialog to define the environment variable PAM_LMD_LICENSE_FILE. Set the environment variable to the location of the license file (e.g. c:\Program Files\ESI Software\vaone.lic)
Advanced Solve Options for Optimizing Memory Use within VA One. ------- 6
General ------------------------------------------------------------------------------------- 8
CORRECTIONS
13
General----------------------------------------------------------------------------------- 13
FE/BEM ---------------------------------------------------------------------------------- 14
Optimizing use of In-core Memory when Working with FE Structural
and FE Acoustic Modal Data ---------------------------------------------------------- 6
- IBM-compatible PC with Intel Pentium 4 processor - Minimum of 512 MB RAM
1 GB recommended for 32bit version 2 GB recommended for 64bit version - Minimum of 100 MB available disk space - 3D graphic acceleration card supporting OpenGL - Ethernet network interface card - 17-inch monitor capable of 16-bit/Hi-color display at 1024x768 resolution - Internet Explorer 6.0 or better - Mouse and Keyboard
VA One 2006.1
RELEASE NOTES
VA One 2006.1
RELEASE NOTES
The documents and related know-how herein provided by ESI Group subject to contractual conditions are to remain confidential. The CLIENT shall not disclose the documentation and/or related know-how in whole or in part to any third party
CONTENTS
VA One 2006.1
1
RELEASE NOTES
© 2007 ESI Group
(released: Feb-07)
UPGRADING
INFORMATION
Installation Requirements
- Windows 2000 (SP4 or later), Windows XP Professional (SP2), or Windows XP x64 Edition
1. Install VA One 2006.1 by inserting your installation CD in the computer’s CD ROM disk drive. The installer for the 32-bit version will run automatically.
2. The VA One installer will launch an installer for Microsoft Visual C++ Runtime, as shown in the figure below. This installer is required and must be allowed to proceed for a proper installation of VA One.
- Binary model files (*.va1) saved with VA One 2006 can be reopened by VA One 2006.1.
- XML neutral files (*.xml) exported by previous versions of VA One and AutoSEA2 can be imported by VA One 2006.1.
without the prior written permission of ESI Group. © 2007 ESI Group. All rights reserved.
January 2007
UM/VA1_/06/13/00/A
VA One 2006.1
i
RELEASE NOTES
© 2007 ESI Group
Scripts ------------------------------------------------------------------------------------ 10
Optional Modules ---------------------------------------------------------------------- 11
6. See the VA One 2006 Licensing and Installation Guide for additional information.
Floating Licenses
1. Install VA One 2006.1 by inserting your installation CD in the computer’s CD ROM disk drive. The installer for the 32-bit version will run automatically.
Instructions --------------------------------------------------------------------------------2
Upgrading from VA One 2005.x, 2006 or AutoSEA2 2005.x-------------------- 2
Installation Folder -------------------------------------------------------------------------- 1
Model File Compatibility ------------------------------------------------------------------ 1
Model File Compatibility
- Binary model files (*.va2) saved with AutoSEA2 cannot be reopened by VA One 2006.1.
- Binary model files (*.va1) saved with VA One 2005 and 2005.1 cannot be reopened by VA One 2006.1.
(released: Feb-07)
CONTENTS
UPGRADING
1
Information --------------------------------------------------------------------------------1
Installation Requirements ---------------------------------------------------------------- 1
3. After the Microsoft Visual C++ Runtime is installed, the VA One installer will proceed. Please read each installer window thoroughly and follow the instructions.
IMPROVEMENTS
5
64-Bit Version of VA One --------------------------------------------------------------5