ljz@fxgrp.UUCP (Lloyd Zusman) (06/23/88)
I'm brand new to this newsgroup and relatively inexperienced at HyperCard.
I'm posting this for someone who has no net access and who is perhaps
only slightly more experienced than I at HyperCard.
He's using a PD thingie called HyperTerm to access his communications
port. In his HyperCard application, he makes use of the various XCMD's
that HyperTerm makes available to him for this purpose.
He has two possibly related problems:
1) His communications buffer overflows. The frequency of this is
related to baud rate: the faster the baud rate, the quicker
the buffer overflows. Even at 300 baud it eventually will overflow.
Either there is no flow control available under this operating
scenario, or else he just doesn't know how to properly manage
flow control here. Can someone explain how flow control works
when using HyperTerm and HyperCard?
2) He is accessing his HyperTerm XCMD routines during the ON IDLE
condition. This is painfully slow, as apparently it takes a while
for the HyperCard application to cycle through all of the tasks
in its prrocessing loop and reach the IDLE state. Is there any way
to ...
... configure HyperCard so that the IDLE state is reached
more frequently than once around its processing loop (even
as frequently as after each task in the main processing loop)?
... cause HyperCard to execute its various tasks more quickly
(perhaps through some sort of compilation or by reorganizing
the stacks)?
These two problems may be related because flow control might not be
absolutely essential if the IDLE state can be reached frequently
enough for the HyperTerm XCMD stuff to empty the communications
buffer before it overflows.
But even with flow control, the speed problem remains.
Any suggestions?
Either email or net replies would be acceptable.
--
Lloyd Zusman UUCP: ...!ames!fxgrp!ljz
Master Byte Software Internet: ljz%fx.com@ames.arc.nasa.gov
Los Gatos, California or try: fxgrp!ljz@ames.arc.nasa.gov
"We take things well in hand."