Scribd
Upload
32 views5 pages

WCF Touch Input Installation Log V6220

The document is a logfile that summarizes the installation of a shared component setup. It details the steps taken such as initializing the setup, checking requirements, moving data, registering files, and updating the registry. The setup installed successfully and completed all planned steps without issues. Key information recorded includes the component name, version number, files registered, and registry entries added or updated.

Uploaded by

Jacqueline Taylor
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
32 views5 pages

WCF Touch Input Installation Log V6220

The document is a logfile that summarizes the installation of a shared component setup. It details the steps taken such as initializing the setup, checking requirements, moving data, registering files, and updating the registry. The setup installed successfully and completed all planned steps without issues. Key information recorded includes the component name, version number, files registered, and registry entries added or updated.

Uploaded by

Jacqueline Taylor
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

================================================================================ Logfile created/appended by setup-caller '[Link]' ...

[2012-12-11 18:13:1 3] CA: _ExitIfStandAlone [2012-12-11 18:13:13] Ext: - Nested: 1 - Deinst: -------------------------------------------------------------------------------*** START LOGFILE MSI - Shared Component Setup (IS V15) -------------------------------------------------------------------------------Filename: WCF_TouchInput_V6220.TXT Install start: 12-11-2012, 18:13:15 Frame Name: Component_Masterframe Frame Version: K04.00.01.01_15.01.00.01 Frame Date: 2009-05-05 Setup64: Logginglevel: 9 CA: IniC_StreamOutIniFiles START 18:13:15 -- MSI new installation assumed. REINSTALL: 0 Ini file will be: C:\DOCUME~1\User\LOCALS~1\Temp\{CCC03FDD-3A54-11D6-92A800A0245B3AC6}\[Link] CA: IniC_StreamOutIniFiles END 18:13:15 StreamOut files from 'C:\DOCUME~1\User\LOCALS~1\Temp\{CCC03FDD-3A54-11D6-92A 8-00A0245B3AC6}\'.. Streamed out: C:\DOCUME~1\User\LOCALS~1\Temp\{CCC03FDD-3A54-11D6-92A8-00A024 5B3AC6}\[Link] x32: [Link] CA: _StreamOutSteuerdatei END [18:13:15] CA: Comp_Initialize START 18:13:16 The SETUP is started from: F:\CD_2\WINCCFLEXIBLE\RTHF\Setup\TOUCHINPUTPC\ In function GetParamComLine_Comp set MSI Property 'COMLINEPARAMETER' to: INTERPRETED: Commandline parameter: INTERPRETED: In function ReadGlobalInfoFromIniFile_Comp Comparing with data of 'F:\CD_2\WINCCFLEXIBLE\RTHF\Setup\TOUCHINPUTPC\versio [Link]' . In function [Link] Release from '[Link]' is same as of internal release: K6.2.2.0_1.1.0.6 UnUseDLL successful: C:\DOCUME~1\User\LOCALS~1\Temp\{CCC03FDD-3A54-11D6-92A8 -00A0245B3AC6}\[Link] No MainProd found. Set default: STEP7 In function DetermineSetupLang_Comp Get operating system language from KERNEL: English ; B In function GetLanguageFromCompSetup Get SetupLanguage as input-parameter of client from Registry: B In function ChangeSetupLanguage The language is up to date. In function GetClient_Comp

CA: Comp_Initialize END 18:13:16 CA: _ADS_SetDirs BEGIN [18:13:16] Set classic startmenue= C:\Documents and Settings\All Users\Start Menu\ CA: _ADS_SetDirs END [18:13:16] CA: Comp_BeforeDataMove START 18:13:22 In function TestUpdateRulesAndClient_Comp In function CheckRequirements_Comp Test Operating System In function Sup_GetOSConditions MSI property SETUPINI read as: C:\DOCUME~1\User\LOCALS~1\Temp\{CCC03FDD-3A54 -11D6-92A8-00A0245B3AC6}\[Link] Found Operating System: MSI property VersionNT read as: 501 VersionNT = 501 ServicePackLevel = 3 NTProductType = 1 MSI Property OF_NO_OS_CHECK set to Allowable OS: Win2000&> In function Sup_WriteConditionString OperatingSystem condition string to check: ((VersionNT>=500)) In function GetCommonDestPath_Comp Main Path and Common Path determination: Common directory read Global SharedPath from registy: C:\Program Files\Common Files\Siemens Common Path exists: C:\Program Files\Common Files\Siemens In function GetMainDestPath_Comp Base Dir is Common Path: C:\Program Files\Common Files\Siemens\ Dirs: Dont use MAIN Path ! REINSTALL: 0 In function Clean_MS_SharedFiles MS_SharedFiles_Counter: Body entry: C:\WINDOWS\[Link]\Framework\v1.1.4322\[Link] Body entry: C:\WINDOWS\[Link]\Framework\v1.1.4322\[Link] [Link] Body entry: C:\WINDOWS\[Link]\Framework\v1.1.4322\[Link] Body entry: C:\WINDOWS\[Link]\Framework\v1.1.4322\[Link] Body entry: C:\WINDOWS\[Link]\Framework\v1.1.4322\[Link].t lb Body entry: C:\WINDOWS\[Link]\Framework\v1.0.3705\[Link] Body entry: C:\WINDOWS\[Link]\Framework\v1.0.3705\[Link].F [Link] Body entry: C:\WINDOWS\[Link]\Framework\v1.0.3705\[Link] [Link] Body entry: C:\WINDOWS\[Link]\Framework\v1.1.4322\[Link].F [Link] Body entry: C:\WINDOWS\[Link]\Framework\v1.0.3705\[Link] [Link] Body entry: C:\WINDOWS\[Link]\Framework\v1.0.3705\[Link]

b Body entry: C:\WINDOWS\[Link]\Framework\v1.0.3705\[Link].t lb Body entry: C:\WINDOWS\[Link]\Framework\v1.1.4322\[Link] [Link] Body entry: C:\WINDOWS\[Link]\Framework\v1.1.4322\[Link] b Body entry: C:\WINDOWS\[Link]\Framework\v1.0.3705\[Link] Body entry: C:\WINDOWS\[Link]\Framework\v1.0.3705\[Link] Body entry: C:\WINDOWS\[Link]\Framework\v1.1.4322\[Link] .[Link] Body entry: C:\WINDOWS\[Link]\Framework\v1.0.3705\[Link] .[Link] Body entry: C:\WINDOWS\system32\[Link] Body entry: C:\Program Files\Common Files\System\Ole Db\Resources\1028\MS [Link] Body entry: C:\Program Files\Common Files\System\Ole Db\Resources\1031\MS [Link] Body entry: C:\Program Files\Common Files\System\Ole Db\Resources\1034\MS [Link] Body entry: C:\Program Files\Common Files\System\Ole Db\Resources\1036\MS [Link] Body entry: C:\Program Files\Common Files\System\Ole Db\Resources\1040\MS [Link] Body entry: C:\Program Files\Common Files\System\Ole Db\Resources\1041\MS [Link] Body entry: C:\Program Files\Common Files\System\Ole Db\Resources\1042\MS [Link] Body entry: C:\Program Files\Common Files\System\Ole Db\Resources\1043\MS [Link] Body entry: C:\Program Files\Common Files\System\Ole Db\Resources\1046\MS [Link] Body entry: C:\Program Files\Common Files\System\Ole Db\Resources\1053\MS [Link] Body entry: C:\Program Files\Common Files\System\Ole Db\Resources\2052\MS [Link] MS_SharedFiles_Counter('C:\DOCUME~1\User\LOCALS~1\Temp\{CCC03FDD-3A54-11D6-9 2A8-00A0245B3AC6}') - Shared files in reg.: 2047 , bodys(Leichen):30 , cleaned: 0 In function STOP_Installation MSI Property OVERINSTALL read: In function TestRegistry In function TestOverWrite --- Test if Shared Component setup is new installation, overinstallation, up date, install for new client: In function IsComponentInstalled Test 8x2 Release ... In function IsComponentForClientInstalled How to install component: New installation! No 'CLIENTS' key has existed; OK. In function TestRegistry

In function DeleteRegKeys_Comp In function ProcessBeforeDataMove_Comp In function IncludeUninstDLL set MSI Property 'COMPPATH' to CA: Comp_BeforeDataMove END 18:13:23 CA: _ads_copyfiles BEGIN [18:13:25] CopyLockedFiles (RenameFilesAtReboot): Stream out: C:\DOCUME~1\User\LOCALS~1 \Temp\{CCC03FDD-3A54-11D6-92A8-00A0245B3AC6}\[Link] CopyLockedFiles (RenameFilesAtReboot): No files listed. CA: _ads_copyfiles END [18:13:25] CA: _ADS_CreateShortcuts BEGIN 18:13:25 Streamout MBShortcuts to: C:\DOCUME~1\User\LOCALS~1\Temp\{CCC03FDD-3A54-11D6 -92A8-00A0245B3AC6}\[Link] Startmenu language tested for shortcuts: 1033 Startmenu language used for shortcuts: 1033 CA: _ADS_CreateShortcuts END 18:13:25 CA: _ADS_WriteRegistryValues BEGIN [18:13:25] CA: _ADS_WriteRegistryValues END [18:13:25] CA: _ADS_RegisterFiles BEGIN [18:13:25] RegisterFiles: Regserver found (only used for .dll files etc.): C:\WINDOWS\system32\REGSVR3 [Link] ChangeWorkingDir to: C:\Program Files\Common Files\Siemens\PTTouchInput LaunchAppGetExitCode Start LaunchAppGetExitCode End, Return 0 Selfreg. result: 0 - C:\PROGRAM FILES\COMMON FILES\SIEMENS\PTTOUCHINPUT\TOUCHI [Link] (V602.200.101.6) CA: _ADS_RegisterFiles END [18:13:26] CA: Comp_AfterDataMove START 18:13:27 In function SetEnvironment In function TestRegistry In function RegistryActualPath In function TestRegistry In function TestRegistry In function RegistryActualPath deleting own key: Software\Siemens\Shared Tools\CompSetup\PTTouchInput In function TestRegistry In function UpdateSharedTools In function UpdateClient Add Client: } Write Version: Write Release: [Link] K6.2.2.0_1.1.0.6 HmiRTm_{B4938B26-C719-4AAF-A63C-15AF6AC210BE

Display Name Logfilename In function GoExit

SIMATIC HMI Touch Input C:\WINDOWS\WCF_TouchInput_V6220.TXT

Result parameters in registry: Write ComponentEntry: PTTouchInput Write Restart: 0 Write Logfilename: C:\WINDOWS\WCF_TouchInput_V6220.TXT Set Registry SetupSucceeded: 1 Write returncode first step: 1 CA: Comp_AfterDataMove END 18:13:27 CA: IniC_DeleteIniFiles START 18:13:29 IScript code finished. CA: IniC_DeleteIniFiles END 18:13:29 -------------------------------------------------------------------------------*** END LOGFILE MSI - Shared Component Setup (IS V15), 12-11-2012, 18:13:29 --------------------------------------------------------------------------------

Common questions

Powered by AI

The installation process uses registry checks and component testing to determine if a component is already installed or needs updating. It examines existing registry keys and compares the current installation's properties with those stored in the system to decide if a clean installation, upgrade, or no action is necessary .

Post-installation procedures include deleting .ini configuration files, ensuring shortcuts are correctly configured, and cleaning up registry entries related to installation. This comprehensive cleanup and configuration process ensures that the installation does not leave unnecessary files or registry keys, maintaining system stability and efficiency .

The function Comp_BeforeDataMove is responsible for preparing the system to move data necessary for completing the installation. It tests prerequisites like operating system conditions and path settings, and also makes adjustments or cleans up shared files, setting the stage for later steps such as file copying and registry manipulation .

The setup process manages file registration through the _ADS_RegisterFiles function, which uses commands like 'REGSVR32.EXE' to register necessary DLL files. This is crucial for ensuring all dependencies and components of the software are correctly registered in the system, allowing for proper operation and interaction with other system processes .

The setup process is detailed and involves multiple stages such as initializing components, setting directories, checking the operating system compatibility, and writing to the registry. It involves both testing registry conditions to determine if an installation is new or an upgrade and setting up necessary file and shortcut configurations, indicating a robust procedure for ensuring successful software installation .

Examining the COMLINEPARAMETER is crucial because it interprets command-line parameters necessary for guiding the installation process. These parameters might include language settings, software versioning, or special instructions for certain installation paths, ensuring the setup is configured correctly according to user specifications or automated setup scripts .

Logging detailed information like language settings and destination directories is critical because it aids in troubleshooting potential installation issues, provides a blueprint for rollback in case of errors, and ensures all setup parameters are verified and documented, benefitting both developers and end-users in managing software installations effectively .

The _ADS_CreateShortcuts function ensures that once the software is installed, the necessary shortcuts are created in the Start menu. This simplifies user access to the newly installed software by providing a direct link that is language-tested and set according to the installation parameters, improving user experience and software accessibility .

The installation process includes a step where it checks the operating system version and service pack level. This is evident where it notes the 'VersionNT' and 'ServicePackLevel' properties, and constructs a condition string to test if the operating system meets the minimum requirements ('VersionNT>=500'), ensuring that the software is only installed on systems it is compatible with .

The registry key 'HmiRTm_{B4938B26-C719-4AAF-A63C-15AF6AC210BE}' serves as an identifier for client additions during the setup process. It is used to store specific version and release information about the installed component, helping manage future updates or interactions by providing a record of what versions are currently installed .

You might also like