Forum unknown
· Text, SIG
#FLIBM1
3 messages in this thread
Phil; Most of the problems I have had with program are my fault. For example I
try to send a file before I set up the 200, or my connecting cable pulls away
from the 200. Sorry about using teh wrong ppn. Thank,
Mike, I've managed to simulate the Hang-up. It happens if you don't have the
Model 100/200 in the receive mode when the IBM starts to send. At least, that's
how I made it happen. And you have to have already sent a file to have this
happen. Of course, if you don't make a mistake, all is ok!
Here's what I think happens. There is a test for an XOFF at the IBM input port
as part of the send routine. If there is one, the program waits until it sees
and XON. Apparently the previous file send results in an XOFF being seen at
the start of the second send. If the lap computer is set up to receive, it
send an XON and all is ok. Otherwise, it waits forever.
When I get some time I will try to add an escape hatch within all such loops —
to provide more graceful recovery.
By the way, does your experience of problems on the second (but not the first)
send agree with my assessment?
Phil
Mike, I've managed to simulate the Hang-up. It happens if you don't have the
Model 100/200 in the receive mode when the IBM starts to send. At least, that's
how I made it happen. And you have to have already sent a file to have this
happen. Of course, if you don't make a mistake, all is ok!
Here's what I think happens. There is a test for an XOFF at the IBM input port
as part of the send routine. If there is one, the program waits until it sees
and XON. Apparently the previous file send results in an XOFF being seen at
the start of the second send. If the lap computer is set up to receive, it
send an XON and all is ok. Otherwise, it waits forever.
When I get some time I will try to add an escape hatch within all such loops —
to provide more graceful recovery.
By the way, does your experience of problems on the second (but not the first)
send agree with my assessment?
Phil