In TinyTERM’s Session Properties, configure a script to launch at Post session start. It starts while the splash graphic is still displayed. For many scripts this is not a problem, but if the script has a te.read() command or something similar, the script pauses at that point waiting for input. Since the splash is still on the screen, the user can’t see the prompt, and TinyTERM is effectively hung before it has finished loading.

This isn’t a problem for the second session and beyond. If you launch tt.exe with multiple .tpx files, and the first does not have a post-session start script defined, there is no problem.

This is due to a timing error. Commands like te.read() require an active TE object. That loads much later in the process, and forms the main screen of TinyTERM. For multiple sessions, the second and subsequent do not load until the first is finished, bypassing the timing problem. It was fixed in TinyTERM 4.30.

CR 346

This entry was posted on Friday, April 20th, 2007 at 10:19 am and is filed under CScript. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.