> I already looked at TnScript 2-3 minutes, but I think this only works if
> the Telnet session is designed like this:
>
> Step 1 - Step 2 - Step 3... so each step is a screen completely
> different from each other.
TTnScript associate events to strings detected in the data flow no matter
how it
> Francois replied:
>
> I think TTnScript is the way to go. You can dynamically add/remove events
> according to which "screen" you detect. If you don't use TTnScript, has a
> look at his source code to understand how to get hand on the input stream to
> chack for data.
>
> I also uploaded a modi
ernet Component Suite, freeware)
Author of MidWare (Multi-tier framework, freeware)
http://www.overbyte.be
- Original Message -
From: "Humm, Markus" <[EMAIL PROTECTED]>
To:
Sent: Friday, November 17, 2006 11:46 AM
Subject: [twsocket] Telnet problems
> Hello,
>
>
Hello,
I've some big problems with the telnet components, the biggest one being
the lack of documentation.
What I want to do is the following:
1. start a telnet session (that one works)
2. have a list of commands
3. loop through the list and carry out one command after the other
4. display th
