#AutoPilot Help
10-Apr-94 04:27:13
Sb: #AutoPilot Help
Fm: Michael Schumacher 100340,1740
To: Betty Clay/SYSOP 76702,337
Ok, I've got another one for you. Today, when I downloaded the messages
from AmigaVendor, AP started looping, however snapped out of it after a
short while. It is the first time it happened to me, and I don't know if
it is of the same kind like you and others are experiencing recently.I was
connected at 14.400, so I didn't notice that it was looping. I only
noticed what had happened when I read through the messages offline and
suddenly messages turned up which I read before. AP greated me with a
requester which read:
<<A message header is invalid>>
<<The message is appended here>>
The loop had started at message #78548. AP must have then snapped out of
the loop and continued the mission.
I loaded the whole message file into AE (PPage) and checked the headers.
and came across a crippled header, which had only 4 digits of the message
number, followed by the message text without a space in between.
Example of first occurence: #: 7872indows because it needs a 32 bit…
" " second occurence: #: 787 indows because it needs a 32 bit…
then out of the loop, maybe because the message number was with spaces
before and after, then again into a second loop:
Example of third occuence: #: 787Bindows because it needs a 32 bit… and
so on, always arriving again at the uncomplete header without spaces
between the digits and characters, in all 10 loops downloading 15 messages
each, and then the crippled header again, three digits of the message
number on their own, loop finished, and AP went on to the next forum and
continued as normal.
I don't know anything about the internal works of AP, buy I suspect that
because AP expects a number in the message field, it tries to download the
same messages again from the point where the error occured. The header of
the corrupted message which AP receives was always slightly different from
the previous ones, 787indows, 787lindows, 787indows etc., only when 787
windows… came up, the program stopped looping.
Hopefully this might provide a clou as to why this looping problem occurs,
but it's just a guess, I'm new to CIS and comms, so I'm not quite sure
that I know what I'm talking about.
By the way, in the message menu the first item 'Show all messages' has
remained ghosted after receiving the binary message. According to the AP
manual it should be available, or did I overlook something? Also, I was
expecting that I would be able to read messages kept in the correspondents
and thread files in the message reader, because they don't seem different
from the history files. Is this possible with AP?
Michael Schumacher
Formula 1 on Autopilot