automate tasks with Import registry action
Specify a file containing registry keys, values and data to be imported into the registry.
Import registry Action. Registry properties.
| Registry properties | Description |
| File | Specify a file containing registry entries to be imported into the registry. |
| Browse file |  Use Browse button to specify particular file or folder on disk, on LAN (local area network) shares, etc. |
| Variable Wizard |  Use Variable Wizard button to specify more advanced input, such as, taking parameters from file, associated Trigger or other Action. |
- Previous import registry property (On Error properties)
- Next import registry property (Options properties)
- Import registry 1 of 4
Return to origin
Additional notes:
- The difference between running Automation Workshop 32-bit and 64-bit versions on 64-bit Windows is that some of Windows registry calls by 32-bit Automation Workshop are transparently redirected to locations under
\Wow6432Node. The calls to the same registry locations by 64-bit Automation Workshop can access the specified registry location directly.
For example, if a registry call is made to accessHKEY_LOCAL_MACHINE\Softwareregistry path, Automation Workshop 32-bit is redirected toHKEY_LOCAL_MACHINE\Software\Wow6432Nodelocation, while Automation Workshop 64-bit accessesHKEY_LOCAL_MACHINE\Softwaredirectly.
Furthermore, if%ProgramFiles%and%commonprogramfiles%environmental variables are written into REG_SZ or REG_EXPAND_SZ registry key by 32-bit Automation Workshop, WOW64 (Windows 32-bit on Windows 64-bit) automatically replaces them with%ProgramFiles(x86)%and%commonprogramfiles(x86)%, respectively.
Links
Copyright © 2001-2013 Febooti Software. All rights reserved. Last updated: March 15, 2012