Testing this against several other Telnet tools, and I'm having problems getting the keymapping to work as indicated. Have configured as a 'vt100' emulation, and using same in TERM setting on Solaris 2.6... Function keys do not work, and we have an alternative that we can send a 'Ctrl-F' followed by the number 6 key, and the system takes it as an 'F6' key press. Cannot get the 'Ctrl-F' to work. Have used the '\\x066', but it only put a 'F' on the screen instead of sending the 'Ctrl-F6' as expected... Similarly with any of the other's I've tried.
Admit I'm not seeing how 'CMD-uparrow' and all that actually gets used in the keymapping...
AbsoluteTelnet seems to be broken in this respect. It's looking at \\x066 as HEX 66, which is the character 'f'.
I'll look into this some more and get back to you.
Brian
trc, I've got an update for you to try:
<old link removed. Go to downloads for the latest version>
Let me know how it goes
Brian,
Thanks for posting the fix. It appears to act as indicated.
The application is nicely arranged, and has many nice features, but I was not able to find anything about scripting a session or in any way doing automated control of the application, connecting, sending control characters and strings, waiting for response, taking action based on received information, subroutining, starting and stopping capturing of received data to a file, etc..
Although there is a way to send control characters and such, having to use Hex to do so is a bit bothersome. I understand that it is an easy way to implement the code, but is cumbersome on the user.
Other products we're looking are STerm, Commnet, Procomm Plus, and yours.
Sure.
There is no scripting capability in AbsoluteTelnet right now. I've got some ideas, but nothing's even started.
AbsoluteTelnet was never really designed to be an automation tool. It's an interactive window to the host, so it's primary design focus is on the accuracy of the emulations and features that make interaction with the host easier.
If I want something automated, I usually write a shell script on the UNIX sever itself, then schedule it through cron. What kind of automation and scripting are you doing inside of the telnet client that made you choose the client as the best place to facilitate those processes?
