
Technical Notes |
|
Removing Reflection software packages results in the loss of end-user settings for those components that store this information in the registry. This technical note describes how to save customized settings in Reflection before you uninstall, and how to restore your settings once you install Reflection 14.x.
For information about saving customized settings before installing Reflection evaluation software, see Technical Note 1601.
In this technical note:
Reflection uses the Microsoft Windows Installer (MSI) technology. When you uninstall Reflection, any customized settings stored in the registry are removed. If you want to restore your customized settings, you must save them prior to uninstalling the product.
Warning: Before you work with the Windows registry, you should back up the registry on your PC.
Use the Windows Registry Editor (Regedit.exe) or another full backup program to back up your Windows registry. For information about the Windows registry, see the Microsoft Knowledge Base Article 256986 at:
http://support.microsoft.com/default.aspx?scid=
The process of saving and restoring your customized settings is specific to each Reflection product.
Most Reflection settings are stored in a settings file; however, some settings are stored in the registry. In addition to saving your Reflection settings files, you must manually save the registry-only settings to restore customized settings.
Follow the steps below to manually save the registry-only settings. These settings are needed to restore your Reflection installation
If upgrading from Reflection 14.x:
If upgrading from an earlier version of Reflection:
Note: This hidden feature does not hide the keyboard and mouse mappings as it hides all other non-registry settings. You do not need to record setting changes that begin with Keystroke: or Mousechord:; these settings are saved in your settings file..
After you reinstall Reflection, you must manually restore the settings information in the registry. Use the View Settings dialog box to restore the settings values.
Reflection Secure Shell settings are stored in a file named config. A config file is created when a user changes a setting to a non-default value in the Reflection Secure Shell Settings dialog box and clicks OK. (To open Secure Shell Settings, click Connection > Connection Setup, enter a host name, and click the Security button.)
If you are upgrading from Reflection version 12.0 or earlier and using Reflection Secure Shell (SSH), make a copy of the config file before upgrading. (Typically, this file was located at C:\Documents and Settings\<username>\My Documents\Reflection\.ssh.)
Reflection for IBM stores almost all settings files in the user's directory. These files will be accessible to the user after Reflection is reinstalled.
The only exception is SNA engine settings. If you have SNA settings, save the Windows\system32\Wrqsna.rlf file before you uninstall Reflection for IBM.
Be sure to review this entire Reflection X section before you uninstall and reinstall the product. Most Reflection X settings are stored in the registry. In addition to saving your Reflection X registry settings, you may also need to manually save some customized files to restore the customized settings.
Note: Before you begin, create a folder in which to save your customized Reflection X files, for example, C:\Rxcustom. You must save the files prior to uninstalling Reflection X.
Beginning in Reflection version 14.0, certain folders are in different locations. If you are upgrading from an earlier version, Reflection continues to use the pre-14.0 folder locations. Use this list as a reference.
Reflection X settings are stored in the registry. Use the Reflection X registry utility (Regconv.exe) to save Reflection X settings by converting them into an initialization (INI) file. You can also use the utility to convert INI files to registry entries.
Follow these steps to convert Reflection X settings that are stored in the Windows registry into an INI file.
On the Registry menu, click Export to INI.
Convert configuration data from 'HKEY_CURRENT_USER\Software\WRQReflection\Rx\config' to 'C:\Rxcustom\Reg_contents.ini'?If the file Reg_contents.ini exists, you are prompted to overwrite it:
Overwrite configuration destination 'C:\Rxcustom\Reg_contents.ini'?After you reinstall Reflection, you must manually restore the settings information in the registry by importing the INI file you created in the preceding section, for example, Reg_contents.ini. To import your settings, follow these steps:
On the Registry menu, click Import from INI.
This process converts configuration data from the INI file to registry settings.
If extra fonts were added, save the fonts folders, including the Fonts.ali and Fonts.dir, to the RXCustom folder. After you reinstall Reflection move the fonts folders to Program Files\Reflection\X\Fonts.
Verify that the "Subdirectories and font servers" information is correct by clicking Fonts on the Settings menu in the Reflection X Manager.
If Reflection X was profiled, save the Rx.ini file to the Rxcustom folder. Once you reinstall Reflection 14.x, move the Rx.ini file to a folder of your choice. At run-time, Reflection X searches for the profile in the following order of precedence:
If any of the following files were customized, save them to the Rxcustom folder: Rwmrc<lang>.txt, Rgb.txt, Xhosts.txt, and Xrdb.txt.
After you reinstall Reflection X, move the files to the All Users\Templates\Attachmate \Reflection\X folder.
Save customized keyboard mapping files (*.kmp) to the Rxcustom folder. Once you reinstall Reflection, move the files to the All Users\Templates\Attachmate\Reflection\X folder..x). Saving Reflection Secure Shell Settings
Reflection Secure Shell settings are stored in a file named config. A config file is created when a user changes a setting to a non-default value in the Reflection Secure Shell Settings dialog box and clicks OK. (To open Secure Shell Settings, click Connection > Connection Setup, enter a host name, and click the Security button.)
The Reflection FTP Client automatically saves your custom FTP site and configuration settings in *.rfw settings files.
Note: Beginning in Reflection 13.0, FTP settings are saved in *.rfw settings files. ( In versions 12.0 and earlier, these settings are stored in the Windows registry.)
You can use the Saveftp utility to export the site and configuration information from your Windows registry. Save this information in a separate folder. Once you have installed Reflection, you can import the information to restore your custom settings.
Note: Reflection FTP client user names and passwords are exported along with the connection information. The passwords, however, are encoded in both the registry and the exported registry file.
Follow these steps to save and restore your Reflection FTP 14.x settings.
User settings are specific to individual users. When User Settings is selected, the following information is included:
Follow these steps for Reflection FTP Client versions prior to 14.x.
Attachmate provides a utility named Saveftp.exe to export the registry settings for your Reflection FTP sessions. Follow the steps below to obtain and run the Saveftp utility. Note: You must have a zip utility to perform this process.
Follow the steps below to import the saved Ftpsettings.reg file to restore your installation.
Note: Before importing the settings, Reflection FTP Client must already be installed on the PC.
Warning: Make sure that you have backed up the registry before you import the new settings. Existing registry values that have the same connection names as the ones you are importing will be overwritten when you perform the next step.
If you have multiple user accounts on a single Windows NT machine, you will need to repeat this step after each user logs in.
In the Reflection for Secure IT Windows Client version 6.0 or higher, your Reflection and SSH settings are stored in the Reflection folder. These settings do not need to be saved separately before installing evaluation software.
For more information about these settings files, see the "New User Folder Location" section of Technical Note 2277. And for administrators who deploy system-wide settings, additional information about managing settings is available in Technical Note 1894.