JS> Carey, I have seen this exact same oddity in the past, and can almost
JS> guaranteeyou that the problem is NOT within Telemate, but rather in the 
BBS
JS> software/setup of the host system that you are calling, or the file 
itself.
I've used Telemate with other systems (not extensivly though) and never
had a problem like that.  I figured that maybe the BBS uses a different
zmodem (such as the 'extended' ones that claim to offer compatable
zmodem) and that it has its timing set a bit differently or something.
And that Telemate has it's timing set just enough that it was effected
and the other one wasn't.  I don't know enough about Zmodem internals
though to be able to say.  I've asked the sysop what type of protocol
driver he runs but he hasn't gotten back to me yet.
I had this happen with two different files.  The ZIP and a mail packet,
so I don't think it had anything to do with the file itself.  There
wasn't any problem with the original ZIP.  After all, I did manage to
finally get it and I used the TEST command while on the board to test
its archive and it said it was fine.
JS> BTW, have you tried Telemate with other systems?  Even as far back in the
JS> Ozarks are you are, I'm sure there has to be a couple of systems within 
arm
JS> reach, aren't there?  :-))))
Oh,,, I think there might be one other.....   Actually there are more
than a dozen local boards, although I'm only on a few of them.  I've
been on other systems and I didn't have any problems like that before.
--- QScan/PCB v1.16b / 01-0162
---------------