Reflection Desktop Pro
Reflection Desktop for X
Reflection Desktop for IBM
Reflection Desktop for UNIX and OpenVMS
This technical note lists legacy file types supported by Reflection Desktop products. These include files created using legacy Reflection products (version 14.x and earlier), Extra!, KEA!, and several third party products.Note: For Reflection 2014 or 2011, see KB 7021495 instead.
Enabling Support for Legacy Files
In the Reflection Desktop installers, all legacy Reflection, Extra!, and Rumba compatibility features are enabled by default.
Figure 1: Reflection Desktop feature selection.
Supported Reflection Legacy Files
The following Reflection legacy files are supported:
||Reflection for UNIX and OpenVMS Settings File
||Reflection for Secure IT Settings File
||Reflection for REGIS Graphics Settings File
||Reflection for IBM Settings
||VBA Macro File
||FTP Settings File
||Mainframe Transfer Request File
||AS/400 Transfer Request File
||Reflection Command Language Scripting File
||Reflection Basic Scripting Files
||Reflection Macro File
Supported Extra! Legacy Files
||Extra! Toolbars (read only)
||Extra! Display Session
||Extra! Keyboard Map
(.ekm files can now be browsed for in the keyboard map file picker)
||Extra! File Transfer Schemes
||Extra! Layout Files *
||Extra! Basic Macros
||Extra! Basic Header
|.etl||Extra! 3270 & 5250 File Transfer List (beginning in version 2011 R2)|
||Extra! 5250 File Transfer Scheme (beginning in version 16.0)
*Extra! layout files are one type of Extra! macro. To run Extra! layout files in Reflection, you must create a file association with the .elf file extension. Follow these steps:
- Copy your .edp and .elf files to \Documents\Micro Focus\Reflection.
- Double-click an .elf file in the \Documents\Micro Focus\Reflection folder.
- Windows will prompt you for a file association.
- Browse to the Reflection install directory and select ebrun.exe.
- Select the check box to always use this program to open this type of file.
Supported KEA! Legacy Files
The following KEA! file type is supported.
||KEA! configuration file
Supported Third Party Macro/Script Files
You can run a majority of macros created by the following products. The macros run directly without conversion.
||OpenText/Hummingbird HostExplorer - Hummingbird Basic macro
||Brandon Systems/Jolly Giant QWS 3270 macro
||Micro Focus Rumba macro
||IBM Personal Communications macro
||IBM Personal Communications VBScript
For more information about running macros, see https://www.attachmate.com/documentation/reflection-desktop-v16/rdesktop-guide/data/macro_legacy_ov.htm.
All trademarks, trade names, and company names referenced herein are used for identification only and are the property of their respective owners.
Troubleshooting Legacy Files
If you have problems with your legacy files, review the following issues.
If your Extra! .edp files are stored in Program Files\Attachmate\EXTRA! (and not in \My Documents), and you open the .edp files in Reflection , then an error displays: "Unable to open because it is not in a trusted location." To resolve this error, add the .edp file location (path) to Reflection's Trusted Locations (specified in Reflection Workspace Settings).
Custom Configuration File Location
If you open an .edp file that refers to other custom configuration files (for example, a custom keyboard map file), the custom configuration file must be in either:
- The âschemesâ subfolder in the âDefault legacy EXTRA! directoryâ (configured in Reflection Workspace Settings), typically My Documents\Attachmate\EXTRA!\schemes, OR
- The same location as the .edp file
If no custom configuration file is found, Reflection will use a default file, and you may think that the Extra! custom configuration settings have been lost.
In Reflection Desktop, when an .edp session file is opened and a custom keyboard map is found, a new .xkb file is created. To determine if Reflection Desktop found the custom keyboard map, open the Manage Keyboard Maps dialog and look at the filename being used (.ekm or .xkb). If Reflection cannot find the keyboard map file, defaults are used.
Legacy KB ID
This document was originally published as Attachmate Technical Note 2807.