To configure an emulator, configure Terminal Launcher and then write an emulator script
The steps for a generic emulator and an advanced generic emulator are mostly the same. The one difference is in Step 5, where you configure output IDs, input IDs, and other parameters.
Run Terminal Launcher (tlaunch.exe).
Either use the shortcuts placed on the Start menu by the installation program, or manually execute C:\Program Files\Protocom\SecureLogin\TLaunch.exe.
At Terminal Launcher's main screen, click Edit Available Emulators.
At the Available Emulators screen, click New.
Enter a name for the emulator, select the Type, then click OK.
For a normal generic emulator, select Generic. For an advanced generic emulator, select Advanced Generic.
Configure the emulator.
To configure a normal generic emulator, set the following parameters:
This is the directory path and executable filename of the emulator. Either type the path or use the Browse button located to the right of the text box. Occasionally, configurations will not work if the Emulator Path does not follow the 8.3 filename format.
In the example, the Emulator Path is C:\Pctcp\WTNVT.EXE.
This is the IP address, host name, or emulator session file you want Terminal Launcher to connect to or load. Occasionally, emulators require command line switches before they accept connection commands at startup. If so, put the switches in the Host Name text box.
Scenario for Including a Command Line Switch: An emulator requires the /h switch so that the emulator can accept an IP address at startup. Henri types /h 192.168.130.222 in the Host Name text box:
Because the example emulator does not need switches, the Host Name in the example is 192.168.130.222.
The Output IDs are the Select All and Copy function IDs that were found earlier using Microsoft Spy++. Type them in the text box, using the following syntax:
xxx,xxx
For this example, you would type 209,205. The Select All ID is followed by a comma (no space) and then the Copy ID.
This is where you use a keyboard simulation alternative, if necessary.
The Input ID is the Paste function ID that was found earlier using Microsoft Spy++. Type it in the text box.
For this example, you would type 207.
This is also where you use a keyboard simulation alternative, if necessary.
Check this check box if the emulator is a 16-bit program.
The WndClass text box only becomes available if the emulator is a 16-bit program. To find the window class, use the Window Finder tool, which is supplied with SecureLogin.
Right-click and drag the SecureLogin icon onto the title bar of the emulator. The Window Class is displayed in the third text box from the top. Copy and paste text from the Window Class text box into the WndClass text box in Terminal Launcher.
The following figure illustrates the complete Terminal Launcher configuration for this example (Window Telnet VT v3.1 emulator):
To configure an advanced generic emulator, set the following parameters:
The emulator path is the directory path and executable filename of the emulator. Either type the path or use the Browse button located to the right of the text box. Occasionally, configurations won't work if the Emulator Path does not follow the 8.3 filename format.
In the example, the Emulator Path is C:\PCTCP\WTNVT.EXE.
The Host Name is the IP address, host name, or emulator session file you want Terminal Launcher to connect to or load. Occasionally, emulators require command line switches before they will accept connection commands at startup. If so, put the required switches in the Host Name text box.
Scenario for Including a Command Line Switch: An emulator requires the /h switch so that the emulator can accept an IP address at startup. Henri configures the advanced generic emulator by typing /h 192.168.130.222 in the Host Name text box.
Because the example emulator does not need switches, the Host Name in the example is 192.168.130.222.
The Output ID is the Copy function Control ID that was found earlier using Microsoft Spy++. Type this ID in the text box.
For this example, you would type 205.
This is where you use a keyboard simulation alternative, if necessary.
This is the Paste function Control ID that was found earlier using Microsoft Spy++. Type it in the text box.
For this example, you would type 207.
This is also where you use a keyboard simulation alternative, if necessary.
An Input ID is not always required. Most emulators allow Terminal Launcher to type text directly into them.
For Terminal Launcher to select the text on the screen without a Select All function, Terminal Launcher needs to use the mouse to click and drag the cursor over the entire emulator screen to select all the text.
For Terminal Launcher to do this correctly, it needs to be told how much space to allow for the toolbar (or other items) when it starts the drag. This is what the Output Offset is. It tells Terminal Launcher where to start the click and drag process.
The Output Offset is a set of two numbers, separated with a comma and no space. The numbers can be from zero up to tens of thousands. However, 10,000 is generally the highest number that is needed.
Finding the Output Offset generally takes a bit of trial and error, and gets easier with experience. Start with high numbers (for example, 10000,10000) and work your way down.
The first number is the horizontal offset. The second number is the vertical offset. Notice where the mouse starts with the click and drag, and lower the numbers until it clicks in the top left corner of the emulator screen.
Normally, the Output Offset number is somewhere around 500,7000 or lower.
For this example, the Output Offset is 500,7000.
Startup IDs are the Control ID numbers of any functions or buttons that you want Terminal Launcher to select before attempting to log in. For example, if the emulator does not automatically connect, provide a control ID for a Connect button.
If several functions or buttons are needed, separate them with a comma.
This example does not require startup IDs.
The Window Class setting is used to assist Terminal Launcher in detecting the emulator window. If no window class is specified, Terminal Launcher might not detect the emulator opening.
To find the window class, use the Window Finder tool. Load the Window Finder and then right-click and drag the SecureLogin icon to the title bar of the emulator.
The window class that is used for an advanced generic configuration is displayed in the Class Name text box, as indicated in the following figure.
Copy and paste the window class exactly as it is displayed. Copy it into the Window Class text box of the Terminal Launcher configuration. Window Class text boxes are case-sensitive.
In this example, the window class is TNVT.
A Child ID is given to each "child" window that the main application launches. The following figure illustrates a child window:
Enter a Child ID into the Terminal Launcher configuration only if it is necessary to interact with a child window.
This example does not require a Child ID.
The Window Title setting is used to assist Terminal Launcher in detecting the emulator window. If no Window Title text is specified, Terminal Launcher might not detect the emulator opening.
The window title is found by using Window Finder.
Some emulators hide the real window title. For example, the title bar of the PCTCP emulator displays the text shown in the Window Text text box. However, the real window title is displayed in the Window Title text box.
No rule describes which text you should type into the Terminal Launcher configuration. (The text you need depends on how it is hidden by the emulator). First, try using the configuration without any text in the Window Title text box. If that doesn't work, try typing the text that is actually displayed in the title bar of the emulator. If that doesn't work either, try typing the text found in the Window Title text box.
This example doesn't require Window Title text.
Click OK, then click Done.
After you configure Terminal Launcher, write a script that Terminal Launcher will use to launch and log in to the emulator.
Right-click the SecureLogin system tray icon, click Manage Logins, then click New.
Select New Application, then enter a name for the emulator script
Select Terminal Launcher as the type, then click Create.
The new script appears in the Application pane.
Double-click the script, then click the Script tab.
Enter a script for the emulator.
For scripting assistance, see Administering Scripts in the Novell SecureLogin Administration Guide and Script Commands.
Click OK, then click OK.