#TAG-BBS
Larry,
I think it's something stranger than that. TAG thought it had received the
file after only 17 blocks in one case (Aterm, at just under 50k is approx 380
blocks long…). Something in the transmitted data has to be doing something
to TAG, which would indicate that it's not a completely properly implemented
Xmodem. However, as I mentioned, everything BUT Aterm has uploaded properly.
But that hasn't stopped us…we locally uploaded Aterm, and it downloads just
fine. Just seems perplexing that TAG won't completely accept it. We once got
it to accept all but the last 10 blocks, and then it quit. The interesting
thing is that TAG never thinks an error has occured, it always tries to send
out 'Transfer Successful' which the remote end never sees as it's still trying
to send the file. As we don't have the source to TAG, is rather questionable
how much diddling with Aterm will help solve the problem. If nothing else,
it's a _feature_ (dare I use the term? <grin>) of Aterm, one that makes it
UNIQUE! <big smile!>. Should TAG ever completely accept Aterm without cutting
off early, we'll be sure to let you know.
Ewan