Non-GR Platform With or Without an InTouch Application

• Computer with 2 GHz or faster processor (32/64 bit). Multi-core processor is strongly recommended. Intel Itanium 2 processor is not supported.
• 1 GB of memory minimum, 4 GB or greater recommended
• At least 30 GB of available disk space for 32-bit OS, 40 GB for 64-bit OS
• Super VGA (1024 × 768) or higher-resolution video adapter and monitor
• Network interface card
• CD-ROM or DVD drive for installation
• Keyboard
• Mouse or compatible pointing device

< top of document >

Wonderware® InTouch® HMI Version 10.1 Service Pack 2 Readme

Last revision: 12/20/2009

About This Readme

• InTouch version 10.1.200 (SP2)
• InTouch version 10.1 (No Patch) 

1. If you are using managed InTouch applications with ArchestrA® symbols from Application Server 3.0, before installing Wonderware Application Server 3.1, run the ArchestrA Symbol Analysis and Repair Utility and ensure all issues reported by the utility are addressed.
2. If InTouch 10.0x and Application Server 3.0x are installed on the same node, they both must be upgraded to Application Server 3.1 and InTouch 10.1, or Application Server 3.1 SP2 and InTouch 10.1 SP2.
3. If your version of Wonderware Application Server is older than version 3.0, you must upgrade it to Application Server 3.1 or Application Server 3.1 SP2 before upgrading to InTouch 10.1 or InTouch 10.1 SP2, respectively. 
4. Galaxies with ArchestrA Symbols or InTouchViewApp Objects containing ArchestrA Symbols that leverage the Runtime Language Switching functionality, must always be modified on the same language operating system and InTouch language version on which it was initially developed. Attempts to modify these components in a different language operating system, or a different InTouch language version may result in unexpected behavior and is not presently supported. Published applications running in an operating system language different from the originally developed language are supported. Refer to Known Issues CRs L00088974, L00088993, and L00088998.
5. Review the  Antivirus Software Exclusions list.
6. Review the Known Issues - OnShow Symbol Script Issue section.
7. Windows 2008 Considerations – Windows 2008 does not support the /console switch. As such, applications such as InTouch that may depend to run in the console session may not behave as expected if launched from a remote session. This may also impact alarm provider and query behavior. Click this Windows 2008 Restrictions link for further information about Windows Server 2008 and terminal services behavior changes.
8. Launching the ArchestrA Licensing Utility from an existing License CD may not work on a 64-bit operating system. Launch the utility from the installed shortcut instead.

4. If you have more than two NICs, make sure all connected NICs are configured with an IP address.

   Windows 2008 Restrictions

   • If a computer runs Windows 2008 as part of an InTouch system, it cannot be configured to be both an InTouch and ArchestrA alarm provider. The computer running Windows Vista can be either an InTouch or ArchestrA alarm provider, but not both simultaneously. 
   • Windows 2008 does not support NetDDE for InTouchView applications. By design, an InTouchView application does not serve data to any other source, including InTouch itself. When WindowViewer starts, it verifies if the application is an InTouchView application. When WindowViewer detects an InTouchView application, it does not register to become a DDE server.   ArchestrA Symbols make use of the client layer when accessing InTouch tags, and appear as a third-party client trying to access WindowViewer as a data server. As a result, ArchestrA Symbols cannot communicate with InTouch tags when used with an InTouchView license. Windows Server 2003 and Windows XP Pro still support NetDDE.
   • InTouch HMI cannot be configured to run as a Windows 2008 service. Windows 2008 security prevents started Windows services from interacting with desktop objects. When the InTouch HMI is installed on a computer running Windows Vista, scripts do not run correctly if they include the InTouch ActivateApp() and SendKeys() functions. These functions interact with desktop objects by starting Windows programs and sending keystrokes to these programs.
   • Windows 2008 configured as a terminal server has limitations that may impact applications running in that environment. The terminal session /console switch has been deprecated. Users connecting remotely to the terminal server can no longer connect remotely as the console. Any remote connection to the server, even as an /admin, is treated as a remote connection. InTouch applications traditionally running as a console application may be affected by this change. Users connected remotely to the terminal server will not be able to launch /console applications. You must login at the physical machine to be considered a console session and for the application to run within the console.

   Terminal Services Behavior

   Modify terminal services behavior in Windows 2008 for proper operation of the software. Wonderware software detects when an application is running in the console. Windows Server 2008 treats all remote connections as a remote RDP session regardless of /console or /admin switches in the mstsc connection.

   To disable the ability to switch users through the Group Policy interface

   1. Click Start and enter gpedit.msc. Click OK. The Group Policy dialog box appears.
   2. Go to the following location: Local Computer Policy -> Administrative Templates -> System -> Logon.
   3. Set Hide Entry Points for Fast User Switching to Enabled.  Enabling this policy hides the Switch User option in the Logon interface, the Start menu, and the Task Manager.
   4. On the File menu, click Exit to close the Group Policy editor.
   Certain editions of Windows Vista do not have the Group Policy editor. Alternatively, configure the switch users settings through the registry.

   To disable the ability to switch users through the Registry Editor

   1. Click Start and enter regedit.exe. Click OK. The Registry Editor dialog box appears.
   2. Go to the following location: HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> Windows -> CurrentVersion -> Policies -> System.
   3. Right-click and select DWORD (32-bit) Value. Name it HideFastUserSwitching.
   4. Set the HideFastUserSwitching data value to 1.
   5. On the File menu, click Exit to close the Registry Editor.

   Terminal Server Restrictions for Windows 2008

   In a Terminal Server environment that has a managed application deployed to it, the following behavior applies to references in the InTouch application to the InTouchViewApp object:
   
   ArchestrA Symbols referencing InTouchViewApp_001.Tag1
           Running on the Console – Refers to the tag value of the application running on the console.
           Running in a Session – Refers to the tag value of the application running on the console.
   Restarting the Window Viewer application running on the console causes references from the terminal session to disconnect and then reconnect.
   
   InTouch Graphic referencing Tag1  
           Running on the Console – Refers to the tag value of the application running on the console.
           Running in a Session – Refers to the tag value of the application running in the session.
   
   ArchestrA Graphic referencing InTouch:Tag1  
           Running on the Console – Refers to the tag value of the application running on the console.
           Running in a Session – Refers to the tag value of the application running in the session.
   
   InTouch Graphic referencing Galaxy:InTouchViewApp_001.Tag1  
           Running on the Console – Refers to the tag value of the application running on the console. 
           Running in a Session – Refers to the tag value of the application running on the console. 

   Using Multiple Network Interface Cards with Windows Server 2008

   The behavior of Windows Vista with multiple NICs configured has carried forward to Windows Server 2008. If you are using multiple network interface cards (NICs) with Windows Server 2008 SP2, you must configure settings so that the firewall does not block remote node access to the Galaxy Repository. See Using Multiple Network Interface Cards with Windows Vista for further information and procedures applicable to Windows Vista and also to Windows Server 2008.

   Other Software Requirements

   The following list describes other third-party software required for InTouch HMI version 10.1 SP2.
   • Microsoft .NET Framework 3.5 must be installed on every computer that hosts an InTouch version 10.1 component. The InTouch installation program stops if .NET Framework 3.5 is not installed on the target computer. A dialog box appears, requesting the installation of .NET Framework 3.5. If you click Install Prerequisites , the installation program automatically installs .NET Framework 3.5. 
   • Microsoft SQL Server 2005 Microsoft SQL Server 2005 SP1 or SP2 database must be installed on the same computer as the ArchestrA Galaxy Repository.  

   < top of document >
   

   ---

   Product Compatibility

   In some cases, Wonderware InTouch HMI Version 10.1 SP2 is supported in newer environments than a compatible product. Wonderware InTouch HMI Version 10.1 SP2 has been tested for compatibility with a listed product only in the environments that are supported by that particular product. Wonderware InTouch HMI Version 10.1 SP2 is compatible and can co-exist with the following products:

   • Wonderware Application Server 3.1 SP2
   • ActiveFactory 9.2
   • InTouch CE 10.1
   • Wonderware Historian Server 10.0
   • Performance Software 3.5
   • Wonderware Information Server 3.1
   • InControl 7.11 SP2 P01
   • Manufacturing Execution Module 1.0
   • InBatch 9.0
   • QI Analyst 8.0 SP1 P01
   • SCADAlarm 6.0 SP2 P01

   < top of document >
   

   ---

   Resolved Issues in Wonderware® InTouch HMI Version 10.1 Service Pack 2 

   Wonderware® InTouch HMI Version 10.1 SP2 resolves the following issues. The issues are listed by their Change Request number:
   
   

   L00074936, L00092104	Right-clicking on a button with a Show Symbol animation locks the button and disables the ability to left-click. (See SR 15010803 and SR 38610014)
   L00079422, L00089689	If there exists any ArchestrA graphics on a window at run-time and an object includes an OnKeyDown script that hides the current window and shows another window, its behavior reverts back to the default for Wonderware® InTouch HMI Version 10.0. As a result, the UseLegacyOnKeyUp setting in the InTouch.ini file will not trigger OnKeyUp. (See SR 19815365 and SR 15314624)
   L00085383	If RTR items that are binded to a symbol's public custom properties are requested by ArchestrA Symbols, they are not deactivated in DASserver.(See SR 23516834)
   L00085745	A translated tooltip does not show in run-time unless WindowViewer is maximized or moved to the left side of the screen. (See SR 24410903)
   L00086169	An ArchestrA graphic window with analog input displays to the foreground each time an input is changed. The last opened graphic with a Show Symbol animation does not have the focus. (See SR 10415127)
   L00086708	An ArchestrA graphic window with analog input displays to the foreground each time an input is changed. The last opened graphic with ShowSymbol animation does not have the focus. (See SR 10415127)
   L00087233	The item list in DASserver's DDE/SuiteLink PlugIn continues to grow when the same items are requested from ArchestrA graphic properties. (See SR 19416681)
   L00087461	$ApplicationVersion does not get updated on the NAD Client after the NAD Master performs the Notify Clients operation. (See SR 15314757)
   L00088127	The order of the Data Change script execution is different when triggered from a button or from a condition script. (See SR 24513829)
   L00088110	An ArchestrA graphic's analog animation does not update from an ArchestrA object's UDA and shows "#####". (See SR 103114586)
   L00088683	Replacing tags with the IOSetRemoteReference function call results in duplicate handles, eventually exhausting available handles. (See SR 15314822)
   L00088786	In a Galaxy with OS Group security and an InTouch application with ArchestrA-based security,  AttemptInvisibleLogon() fails if the username has an expired password or requires a change in password upon initial login. (See SR 23517329)
   L00088859	ArchestrA Symbol expressions do not properly evaluate input sources set to "---". (See SR 15616286)
   L00089072	When AlarmDbLogger is configured to run as a service, a warning appears stating "The Wonderware Alarm Logger Service service has reported an invalid current state 0". (See SR 37510057)
   L00089288	The screen shows graphics problems when a window with a combination box is overlapped over another window. (See SR 23517321)
   L00089357	Dividing by zero results in storing messages to the ArchestrA Logger, but a DMP file is not generated. (See SR 16310081)
   L00090015, L00090390	The previously-entered value is shown when you use the keypad to enter a value.(See SR 10415307)
   L00090252	WindowViewer does not always generate a dump file from View.exe for an access violation exception. (See SR 15314624)
   L00090590	The Access Name button shows the wrong access name. The tag is pointing to the wrong data source. (See SR 20113078)
   L00090595	When the WindowViewer memory option is not "Always load windows from disk", the popup symbols opened from a window do not close when the window closes.  (See SR 15616174)
   L00091110	Memory leak occurs if you switch windows that have ArchestrA graphics even when "Always load from disk" is unchecked. (See SR 33810854)
   L00091736	If you log in with an incorrect password immediately after logging in with the correct password, the AttemptInvisibleLogon() function will accept the wrong password. (See SR 37510162)
   L00092149	The InTouch HMI freezes when showing an ArchestrA popup symbol using the Show Symbol animation or Show function from a window with thousands of other ArchestrA Symbols. (See SR 103115490, HF 1368)
   L00092594	Refreshing WindowMaker SmartSymbols on a wide screen monitor or a resolution greater than 1280 pixels by 1024 pixels causes repainting and "ghosting" of moved objects. (See SR 38910016)
   L00092938	When you upgrade from Application Server 3.0 Patch 02 to Application Server 3.1, the application freezes because there is not enough memory to display a bitmap image. You must log off to recover from the error. (See SR 12912080)
   L00093086	WindowViewer crashes after you upgrade from InTouch HMI version 10.0 Patch 03 to InTouch HMI version 10.0 Service Pack 2 and make repeated asynchronous QuickFunction calls. The errors shown are "VarAPI_GetValue : An entry in Script Frame is missing" and "VarAPI_SetArgRealValue : type -1 not handled". (See SR 103115821)
   L00094203	The "Active on Demand" feature was disabled for InTouch HMI version 10.1 but some points are not de-activated and causing critical issues. (See SR 103115892)
   L00094229	In a single node system platform license with a keyless license, the Error Key does not enable WindowViewer despite checking InTouchViewApp under the Special option. (See SR 24514142 and SR 23517958)
   L00094569	Crashes occur when you use View.exe version 1412.466.0.0. This version is not in the InTouch HMI 10.1 Service Pack 2. (See SR 24514168, SR 24514150, and SR 20113127)
   L00094994	PrintScreen and PrintWindow functions do not work when WindowViewer is running as a service. (See SR 19417084 and SR 1950336)
   L00095489	An access violation error occurs when a query exceeds 1 kilobyte in length. (See SR 12610609 and SR 103114053)
   L00096961	After installing HotFix HF 1440, WindowViewer crashes after a few hours when using a blink animation link because the GDI continues to increase to the defined limit specified in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Current Version\Windows. (See SR 33811098)

   < top of document >

   ---

   Known Issues in Wonderware® InTouch HMI Version 10.1 Service Pack 2

   This section describes all known issues in Wonderware® InTouch HMI Version 10.1 SP2. The issues are listed by their Change Request number: 

   L00092171	When starting AlarmDbLoggerManager, the Settings, Stop, and Start buttons remain disabled.
   L00092204	SPCPro is not supported on all versions of the Windows Vista, Windows 7, Windows Server 2008, Windows Server 2008 R2, and later operating systems, resulting in inconsistent run-time behavior for SPC DDE items (e.g. autocollection, startcollection).
   L00092635	IDE imports files in Galaxy_XXX_localeID_Alarm_Comments_Untranslated.txt. InTouch cannot import files in that format. The InTouch HMI imports files in Galaxy_XXX_localeID_Alarm_Comments.txt format and the header information.
   L00092766	On Windows Vista, the following help files cannot launch:  ddeshrnt.hlp, ddeshrnt.hlp, ddeshrnt.hlp, ddeshrnt.hlp, Hdmerge.hlp and testprot.hlp. Microsoft WinHlp32.exe is required to display 32-bit Help files that have the ".hlp" file name extension. To view .hlp files on Windows Vista, you need to install this application.
   L00092774, L00096793	The alarm hot backup pair does not work on Windows Vista or Windows 2008 for the query \\Machinename:ipaddress\intouch!$system using mstsc/console since no IP address required for remote logins. In this case, InTouch is the only provider.
   L00092964	WindowViewer reports low memory upon startup regardless if the system has enough memory available.
   L00093253	If you open a symbol with ShowSymbol animation and the symbol contains one or more expressions involving datapoints that are repeated across thousands of expressions already displayed in InTouch windows, the viewer freezes while all the datapoints are evaluated/updated. (Reference CRs L00092235 and L00092236. See SR 103115490; HotFix 1404.)
   L00093388	On Windows Vista, the following help files cannot launch:  ddeshrnt.hlp, ddeshrnt.hlp, ddeshrnt.hlp, ddeshrnt.hlp, Hdmerge.hlp and testprot.hlp. Microsoft WinHlp32.exe is required to display 32-bit Help files that have the ".hlp" file name extension. To view .hlp files on Windows Vista, you need to install this application.
   L00093559	The calendar control in the graphic editor is drawn with different size fonts on different operating systems. For example, the sizes shown are different on Windows Server 2003 and 2008 operating systems. The size of the calendar control does not change when you change the font on the Windows Vista operating system. If a symbol with calendar control is saved in a Windows Server 2003 system and then opened in a Windows Server 2008 system, the size changes after export and import. This affects the symbol layout as well. As a workaround, ensure that your operating system themes are consistent in screen resolution, DPI, icon size, and font size settings.
   L00094181	In a Windows 2008 Server computer hosting an InTouch application that is an alarm provider, the alarm query for retrieving alarms from a remote machine does not work if the application is not running within the console. See Windows 2008 Restrictions for details.
   L00096097	Changes on InTouch CE (Windows 2008 64-bit) are not recognized by the validation process and display "Validation is already done".
   L00096310	Terminal Servers have at least 20% higher CPU usage on Windows 2008 (32-bit and 64-bit).
   L00096790	Help for the Annotate Layout function in InTouch states that it is supported only on an XP Tablet PC. Windows Vista is also supported.
   L00096840	On Windows 2008, the TseQueryRunningOnConsole() and TseQueryRunningOnClient() functions return incorrect values from a remote logon when using the same InTouch View opened from a console.
   L00099595	If you install InTouch with the Application Server auto-install checkbox selected, the Application Server installation location cannot be on a mapped network drive. This limitation occurs only on Windows 2008 (32/64-bit) and Windows Vista (32/64-bit) operating systems. You can use the following procedure as workaround: Cancel the AutoAppServerLaunch and manually navigate to the network install folder to launch the Application Server install, or install both InTouch and Application Server using the installation CDs.

   OnShow Symbol Script Issue

   When the OnShow Symbol Script contains external references, the data may not be available at run time due to a timing issue. Application Server 3.1 SP2 has enabled a configurable OnShow Symbol Script timeout to allow external references to resolve. The symbol will be drawn disabled and all scripts will be delayed. Once the data is available, the symbol will be enabled and the OnShow Symbol Script will execute first, followed by the rest of the scripts. If the external data does not become available within the configured timeout, the OnShow script will still execute but will place a message in the Logger that not all references have been resolved. Because named scripts will be blocked until OnShow executes, some events may be missed. For example, the named script OnDataChange will not run during the time OnShow is delayed even if the data point is changing. .

   < top of document >

   ---

   InTouch Documentation Issues

   The following table lists all documentation corrections to InTouch 10.1 documentation.

   Item	Location of Change	Existing Documentation	Change
   1	Creating and Managing ArchestrA Graphics User’s Guide (aaGraphics.pdf), "String Substitutions and Language Switching" section, page 426	n/a	Add the following text after the first paragraph: If you perform a first-time string substitution on an embedded symbol in the primary language, that substitution is shown in the secondary languages. You can then perform a substitution in the secondary language to create a string substitution specific to the secondary language.
   2	Application Server Help (IDE.chm), "String Substitutions and Language Switching" topic	n/a	If you perform a first-time string substitution on an embedded symbol in a secondary language, the substitution is also applied to the primary language, because the translated string that previously existed for the primary language is no longer valid.  Because the primary language value is changed in the symbol, this string applies to all secondary languages configured.  You can then perform a second substitution in the primary language, which will apply to all secondary languages except the ones that have had a specific substitution set. If you perform a string substitution in a secondary language with an existing string substitution in the primary language, the new substitution is applied to the secondary language only.

   < top of document >    
   

   ---

   
    

   Wonderware® InTouch® HMI Version 10.1 Readme

   
   
   Last revision: 01/30/2009

   About This Release

   Version 10.1 of Wonderware® InTouch HMI includes the following enhancements and new features:

   Language Switching for ArchestrA Symbols

   You can switch to localized strings for ArchestrA Symbols. This includes any configuration-time changes to support the extracting and importing of text strings. You can localize the following strings: 
   • Text constant custom properties
   • Text graphics
   • Text overrides of custom properties in WindowMaker 
   You can also add, edit, and remove the locale data from the Symbol Editor.

   Licensing

   InTouch licensing now accounts for Terminal Service sessions. The licensing system now enforces per session licensing to prevent running unlicensed copies of InTouch within Terminal Server Sessions. 

   Non-Administrator Interactive User

   At a high level, this feature allows InTouch run-time functionality to be run by users who do not have administrative rights on the computer. It does not provide this support for configuration operations. Functionality is available for the following operating systems:
   • Windows XP SP3 (Power user)
   • Windows 2003 SP2, R2 + SP2 (Power user)
   • Windows Vista SP1 (Standard user with the UAC enabled)

   Well-known Client Control Support

   The Symbol Editor has been extended to allow new Graphic Objects to appear in the Symbol Editor tool palette.

   Printing Enhancements   

   Several printing features are added to the InTouch HMI:  
   • Saving and Printing a Tag Cross-Reference List
   • Printing Scripts
   • Printing Information about WindowMaker Objects
   • Printing Information about InTouch Windows
   • Printing Window Information from a Command Prompt

   Deployed File Management

   You can add additional files in a managed InTouch application so they are deployed and available at run time.

   < top of document >

   ---

   Antivirus Software Exclusions

   Configure your antivirus software to prevent archive files from being scanned. Also, antivirus software should not scan files in the following ArchestrA folders (ensure subfolders of the listed directories are also excluded): C:\Program Files\ArchestrA\
   C:\Program Files\Common files\ArchestrA\
   C:\Program Files\FactorySuite\ (may not exist in newer installations)
   C:\Program Files\Wonderware\
   C:\InSQL\Data\
   C:\Documents and Settings\All Users\Application Data\ArchestrA From Application Server Platform objects:
   • History Store Forward directory: (if not default)
   From Application Server Engine objects:
   • Checkpoint directory location (if not default)
   <InTouch Application folder path> including: 
   C:\Documents and Settings\All Users\Application Data\ArchestrA\ <SMCLoggerStoragefilepath>. The default is:
   C:\Documents and Settings\All Users\Application Data\ArchestrA\LogFiles\ SQL Server database files of type:
   • .mdf
   • .ldf 

   < top of document >

   ---

   System Requirements

   This section describes the hardware and software requirements to install Wonderware® InTouch HMI Version 10.1.

   • Hardware Requirements
   • Software Requirements
   • Other Software Requirements
   
   

   Hardware Requirements

   The following lists show the recommended specifications to install Wonderware® InTouch HMI Version 10.1. These recommendations are for development systems. Run-time requirements may be different, depending on the InTouch application and other factors.

   • Computer with 1.2 gigahertz (GHz) or faster processor
   • 512 MB of memory minimum, 1 gigabyte (GB) or greater recommended
   • At least 4 GB of available disk space
   • Super VGA (1024 × 768) or higher-resolution video adapter and monitor
   • CD-ROM or DVD drive for installation
   • Keyboard
   • Mouse or compatible pointing device
   
   

   Software Requirements

   The following table lists the supported operating systems that can be installed on computers that run InTouch server and client components.

   Operating Systems	Product Name Components
   	WindowMaker	WindowViewer	ArchestrA IDE	ArchestrA Run Time	Galaxy Repository
   Windows Vista Business (See Vista Restrictions)	•	•	•	•	•
   Windows Vista Business SP1 (See Vista Restrictions)	•	•	•	•	•
   Windows Vista Enterprise (See Vista Restrictions)	•	•	•	•	•
   Windows Vista Enterprise SP1 (See Vista Restrictions)	•	•	•	•	•
   Windows Vista Ultimate (See Vista Restrictions)	•	•	•	•	•
   Windows Vista Ultimate SP1 (See Vista Restrictions)	•	•	•	•	•
   Windows 2003 Standard Server R2	•	•	•	•	•
   Windows 2003 Standard Server SP2	•	•	•	•	•
   Windows 2003 Enterprise Server R2	•	•	•	•	•
   Windows 2003 Enterprise Server SP2	•	•	•	•	•
   Windows XP Professional SP3	•	•	•	•
   Windows XP Tablet	•	•		•

   Note:

   • InTouch HMI version 10.1 does not support any version of the Microsoft Windows 2000 operating system. If you attempt to install or upgrade the InTouch HMI on a computer running Microsoft Windows 2000, an error dialog box appears during the installation procedure.
   • Microsoft Windows 2003 Standard Server R2 is the recommended operating system to run InTouch server components. 
   • Microsoft Windows XP Professional SP3 is the recommended operating system to run InTouch client components.

   Vista Restrictions

   • InTouch HMI version 10 or later can run under Windows Vista Enterprise, Windows Vista Business, or Windows Vista Ultimate. The Windows Vista Home Basic and Home Premium editions are not supported. 
   • You can run InTouch only on computers running a 32-bit operating system. You cannot run InTouch on a computer running a 64-bit operating system.  
   • Windows Vista does not support a dedicated single-node server configuration that runs one or more databases for an InTouch HMI system. 
   • If a computer runs Windows Vista as part of an InTouch system, it cannot be configured to be both an InTouch and ArchestrA alarm provider. The computer running Windows Vista can be either an InTouch or ArchestrA alarm provider, but not both simultaneously. 
   • Windows Vista does not support NetDDE for InTouchView applications. By design, an InTouchView application does not serve data to any other source, including InTouch itself. When WindowViewer starts, it verifies if the application is an InTouchView application. When WindowViewer detects an InTouchView application, it does not register to become a DDE server.   ArchestrA graphics make use of the client layer when accessing InTouch tags, and appear as a third-party client trying to access WindowViewer as a data server. As a result, ArchestrA symbols cannot communicate with InTouch tags when used with an InTouchView license. Windows Server 2003 and Windows XP Pro still support NetDDE. 
   • InTouch HMI cannot be configured to run as a Windows Vista service. Windows Vista security prevents started Windows services from interacting with desktop objects. When the InTouch HMI is installed on a computer running Windows Vista, scripts do not run correctly if they include the InTouch ActivateApp() and SendKeys() functions. These functions interact with desktop objects by starting Windows programs and sending keystrokes to these programs.
     

    Other Software Requirements

   The following list describes other third-party software required for Application Server version 3.1.
   • Microsoft .NET Framework 3.5 Microsoft .NET Framework 3.5 must be installed on every computer that hosts an InTouch version 10.1 component. The InTouch installation program stops if .NET Framework 3.5 is not installed on the target computer. A dialog box appears requesting that you install .NET Framework 3.5. If you click Install Prerequisites, the installation program automatically installs .NET Framework 3.5. 
   • Microsoft SQL Server 2005 Microsoft SQL Server 2005 SP1 or SP2 database must be installed on the same computer as the ArchestrA Galaxy Repository.  

   < top of document >
   

   ---

   Resolved Issues in Wonderware® InTouch HMI Version 10.1

   Wonderware® InTouch HMI Version 10.1 resolves the following issues. The issues are listed by their Change Request number:

   L00034858:	For an action script, double-clicking text within the double quotes selects additional text beyond the double-quotes, when a colon (:) follows the text. (See SR 1036163)
   L00037488:	You can instantiate a SmartSymbol that references a tag that does not exist. (See SR#2351687)
   L00039308:	The InfoAppTitle function does work with non-administrator user rights. (See SR 1036792)
   L00041099:	Printscreen and Printwindow functions do not work if WindowViewer is running as service.
   L00048778	Placing an apostrophe (single quote) in the comment text box of a discrete alarm tag (OnMsg) causes the Alarm DB Logger to fail to log an alarm.
   L00067243:	Control label text is scrambled when created using the Wizard Graphics and saved as a SmartSymbol. (See SR 23514920)
   L00071647:	The OnShow script in an ArchestrA Symbol appears to run, but the script does not set an attribute. (See SR 14811879)
   L00072300:	When a client control is deleted and a new version of the client control is imported from a remote IDE, an ArchestrA Symbol referencing the client control will show Version 1 on the remote IDE and Version 2 on the Galaxy Repository IDE. This is a mismatch of versions. (See SR 103112086)
   L00073550:	The graphic element reference list is incomplete, or it is corrupted. The error message "Failed to get Graphic element reference list" appears in the SMC logger. (See SR 23515471)
   L00075206:	Customized graphic text is lost after group change. (See SR14811926)
   L00075269:	The RegisterEngine number decreases when a new connection is made using remote desktop (TSE) to the Application Server. (See SR 16310052)
   L00075763:	Custom property links for ArchestrA symbols do not accept the following special characters that can be used in InTouch tag names:  _(underscore), -(hyphen), $(dollar), %(percent), and &(ampersand).
   L00075800:	MX References do not start in scripting; .InputSource in ArchestrA Symbols does not start in scripting. The MX References do work on display the link and in a custom property. (See SR 15010810)
   L00076011:	Graphic symbol custom property overrides are lost after group change. (See SR 14811926)
   L00076900:	Warning "Could not find embedded graphics" appears after a template and its instances of a Galaxy are exported as an aaPKG file, and are then re-imported into a new Galaxy. (See SR 33430263)
   L00081430:	License enforcement of Terminal Service Edition does not work. Too many WindowViewer sessions are permitted to open.
   L00081739:	The Graphic toolbox pop-up window and the Graphics tab preview window thumbnails show "not found" when an application object instance containing symbols with date time picker is imported in a new Galaxy.
   L00083495:	SPC Pro does not work when WindowViewer is started up directly on a computer with a  standard user login.
   L00085207:	If you are using the SPC Control Chart on the Windows Vista operating system, you need to specify a System Data Source Name (DSN) and make sure that all application users can write to the folder in which the database file resides. 1) The ODBC data source needs to be created as a System DSN and not as a User DSN. As application creator must be admin/power-user and application user can be standard user, it is likely these will be different users. A User DSN won't work for standard user and gives errors in the SMC. 2) If you are using a database file (such as a Microsoft Access MDB file), then application creator must ensure that the application user can write to the folder in which the database file resides. Writing is required for database access (for example, adding sample points in the database). By default, most folders are not write-enabled.

   < top of document >

   ---

   Known Issues in Wonderware® InTouch HMI Version 10.1

   This section describes all known issues in Wonderware® InTouch HMI Version 10.1. The issues are listed by their Change Request number: 

   L00077445:	Touch push button animations do not work on client controls.
   L00078446:	The Symbol Editor stops responding when you edit the "format string" property of the “checked list box” client control.
   L00081354:	Windows do not print if the window name contains special characters. Rename the directory path and the filename to remove all special characters.
   L00082814:	WindowViewer does not start when configured to start as a service. An error message appears “Access denied.” The user win.ini and the MS Windows system win.ini are not in sync. See http://support.microsoft.com/kb/832048 to pick up the correct system win.ini file.
   L00083270:	Spaces are not imported as part of the translation for the selected language.
   L00083636:	Terminal Server sessions crash when a ViewApp is changed and then redeployed while WindowViewer is running in a 100-terminal session configuration across 10 Terminal Servers. For certain applications and systems, you need to adjust the restart delay time by adding "ViewManagedRestartWaitPeriod" to the "Intouch" section in the Win.ini file. The default delay time is 5-seconds.
   L00083828:	There are inconsistencies between the selected language and the strings that are shown.
   L00083847:	After you click "NO" in the Network Application Development properties dialog box, WindowViewer does not ask you to "restart" and "load" changes.
   L00083909:	InTouch applications receive quality status and locale information from the deployed Galaxy. InTouch applications cannot receive data from an undeployed Galaxy.
   L00084010:	Translations are not loading after embedding a primitive from a different Galaxy employing a different language. Only the default English strings are shown.
   L00084834:	The Annotation window stops responding if you use standard Windows cut, copy, and paste shortcuts. Microsoft provides a Microsoft.Ink.dll CLR2.0 Update. See the following link to download the update. http://www.microsoft.com/downloads/details.aspx?FamilyID=84bbefa4-7047-41df-8583-e3bdbf9d805f&DisplayLang=en
   L00086229:	Running the AlarmDBLogger Manager as a Windows service is not working. Disable this option for Vista.
   L00088095:	If you are a Terminal Server user and you do not have "Administrator" privileges, you must be either a "Power User," or a "Remote Desktop User" to access the license. Otherwise, you receive a licensing error message. It is not obvious that you are missing rights and privileges necessary to successfully login.
   L00088673:	Non-English locale animation static "text" strings are not propagated to default (English) locale static "text" strings.
   L00088871:	Exporting the language dictionary using Microsoft Vista may result in not being able to retrieve the dictionary file as a standard user. When running WindowMaker as a standard user elevated to administrator rights as a different user than logged onto the Desktop, exporting  the Language dictionary opens a default path that is not accessible by the standard user. It is recommend that you change the path to a public folder location.
   L00088974:	When an ArchestrA Symbol is exported from an application developed with an English version of InTouch and imported into an application developed in a different InTouch Language, like French, the strings of the ArchestrA Symbol cannot be substituted in WindowMaker.
   L00088993:	An ArchestrA Symbol with string substitutions is not showing the string substitutions in WindowMaker when the Galaxy Primary language is not English.
   L00088998:	InTouch Applications, which are configured to support runtime language switching and contain ArchestrA Symbols and native InTouch animations, initially show mixed language strings, if executed in an operating system language different from the one in which it was originally developed.
   L00089000:	The EnableDisableKeys function does not work in a Vista operating system, if the user is configured as a Standard User. Use the runtime environment configuration options in WindowMaker in addition to the operating system security policies to lock the application from access to the desktop.

   < top of document >

   ---

   InTouch Documentation Issues

   The following table lists all documentation corrections to InTouch 10.1 documentation.

   Item	Location of Change	Existing Documentation	Change
   1	Creating and Managing ArchestrA Graphics User’s Guide (aaGraphics.pdf), "String Substitutions and Language Switching" section, page 426 Application Server Help (IDE.chm), "String Substitutions and Language Switching" topic	n/a	Add the following text after the first paragraph: If you perform a first-time string substitution on an embedded symbol in the primary language, that substitution is shown in the secondary languages. You can then perform a substitution in the secondary language to create a string substitution specific to the secondary language. If you perform a first-time string substitution on an embedded symbol in a secondary language, the substitution is also applied to the primary language, because the translated string that previously existed for the primary language is no longer valid.  Because the primary language value is changed in the symbol, this string applies to all secondary languages configured.  You can then perform a second substitution in the primary language, which will apply to all secondary languages except the ones that have had a specific substitution set. If you perform a string substitution in a secondary language with an existing string substitution in the primary language, the new substitution is applied to the secondary language only.
   2	InTouch® HMI Documentation Addendum (ITAddendum.pdf), ".CVS Format for Printing Windows" topic, page 25	The current screen capture shows "Conveyor, Main, Reactor display, Menu"	The screen capture should show "Conveyor,Main,Reactor display,Menu"

   < top of document >

   ---

   InTouch Documentation

   The InTouch product library consists of a set of Portable Document Files ( PDF) located in the UserDocs folder of the InTouch installation CD. You need Adobe Reader installed on your computer to view InTouch documentation. You can download the latest version of Adobe Reader from the Adobe Corporation web site: http://www.adobe.com/products/acrobat/readstep2.html After installing Adobe Reader, double-click on a PDF file with your pointing device to view the book with Adobe Reader. You can also open a book with the Adobe Reader Open command from the File menu. InTouch installation instructions are located in the root folder of the InTouch installation CD as an online help file. You can view these instructions by clicking Help as you complete the InTouch installation procedure. Context-sensitive documentation is also available with InTouch online help. Select Help for information about the current InTouch window that you have open on your computer.

   Searching InTouch Books with Adobe Reader

   The InTouch version 10 books are delivered as an Adobe PDF package, which provides a master index of all books. Using Adobe Reader, you can simultaneously search for a specific topic across all books that belong to the InTouch product library.

   To search for information across all InTouch books simultaneously

   1. Open Adobe Reader.
   2. Press CTRL+SHIFT+F or select Search from the Edit menu. The Search dialog box appears.
   3. Type the word or phrase that you want to search for in the InTouch books.
   4. In the Where would you like to search area, select the option to search all PDF books.
   5. If necessary, locate the InTouch version 10 PDF package located on your Wonderware CD or on a network folder containing copies of the InTouch PDF book files.
   6. Click Search. Adobe Reader lists the InTouch books containing information that matches your search criteria.
   7. Click on the links to open the InTouch book to the topic containing the information that meets your search criteria.

   < top of document >

   ---

   © 2010 Invensys Systems, Inc. All Rights Reserved.