Adding your own preferred Terminal Emulator to the TermEm.ini

From TDiWiki

This hint assumes that you have already installed the ConsoleWorks Client kit, called CWCLIent, on your Windows PC. If you haven't yet, then see the CWCLIent User Guide (http://www.tditx.com/support_doc_dwld.asp) for installation and usage instructions.

In a large environment you may have many users that want to use the same Terminal Emulator instead of the included Java Terminal Emulator, or JTE, that comes with ConsoleWorks. Then you find that your Terminal Emulator is not a "Known" application. You COULD use the "Custom Application" and the appropriate "Application Parameters" and share that information with your co-workers. A screen shot might look like this:

However if you prefer, you can add this application and its parameters to the TermEm.ini. This file is found in C:\Program Files\TDi\ConsoleWorks Client\Bin when the default installation values are used.

Following is a screenshot of the TermEm.ini with PuTTy and Exceed Version 13.00 added to the bottom. Neither of these applications are shipped in the standard TermEm.ini. Once you've added YOUR values, you can then share this file with your co-workers using the above path when the default is used, or the appropriate location when a custom ConsoleWorks Client Kit installation is performed.

As to determining the "Application Parameters", this is most often a process of elimination. You need to find what program is used to start your Terminal Emulator. Usually, you can find this information in the Shortcut that is created when the program is installed. Then go to the cmd prompt in Windows via >Start, Run, type CMD and press enter. Go to the installation directory for your emulator and type the exe you found in the shortcut. If the program starts normally, then try it with the <host name>:<port_num> or <IP address>:<port_num> and see if it "does the right thing"... If so, then you should be able to subsitute our %h:%p for host and port. Do know the colon is important! If it doesn't "do the right thing", you will need to do a bit of research within the program's documentation. Searching for "command line" often returns favorable results. Once you do have the appropriate values, the next test is to try your values with CWTProx, as shown in the first screenshot above. When you have that working, simply add it to the TermEm.ini using the same syntax as found for a previously defined terminal emulator.

Since PuTTy is widely used, the example below may be used for cutting and pasting. Just make sure YOUR path is used if it does not match what we have here.

Example: [PuTTy] Type=Path Path="c:\program files\putty\putty.exe" Parm="-telnet -P %p localhost"

Feel free to share with us what you may learn so that we may add more Terminal Emulators to our "Known Applications" within CWTProx!