Having a problem with TouchTerm or TouchTerm Pro?

First, we'd appreciate it if you take moment to see if your problem is among the following list of known issues with the current release:

TouchTerm Pro 1.1

• Bug: The font choices are not properly localized (i.e., showing configParam.customFont.param.Courier, instead of just "Courier").
  Cause: Our fault -- we missed a few localization strings.
  Fix: This will be fixed in the TT Pro 1.1.1 update.
  
• Bug: Directory Navigation Mode can fail when using a large directory and a prompt which includes the full path to the pwd.
  Cause: Our command processor is confused by line-wrapping control characters sent by the shell.
  Workaround: If possible, use a prompt that doesn't include the full "pwd" when using Directory Navigation Mode.
  Fix: We're working on a fix, and will hopefully be able to include it in the TT Pro 1.1.1 update; at the very latest this will be fixed for the 1.2 update.
  
• Bug: When a server's host key has changed (for example when reinstalling the OS on a server), TT notifies but then hangs without allowing the connection to proceed.
  Workaround: You can work around this issue by using the "Reset Host Keys" Action (under Misc. Actions) to delete TT's host key list, which will prevent the warning from coming up on the next connection attempt.
  Fix: This is fixed in our test builds, and will be included in the next TT Pro update.
  

TouchTerm 2.3

• Bug: When a server's host key has changed (for example when reinstalling the OS on a server), TT notifies but then hangs without allowing the connection to proceed.
  Workaround: You can work around this issue by using the "Reset Host Keys" Action (under Misc. Actions) to delete TT's host key list, which will prevent the warning from coming up on the next connection attempt.
  Fix: This is fixed in our test builds, and will be included in the next TouchTerm update.
  

If your issue is not addressed above, please use the following e-mail template to submit a bug report. Provide as much detail as possible when describing your problem, so that we can more easily diagnose the cause of the problem and determine potential fixes and workarounds. If you are having connection issues, please be sure to attach the complete debugging information reported by TouchTerm.

You can paste the following text into an email message and send it to:

fogbugz at jbrink.net

or, use this link to copy the template into your E-Mail client.

Application: Version: Describe in detail the steps required to reproduce the problem: 1. 2. 3. etc...

We will make every effort to respond to all bug reports as quickly as possible.