Subj : Re: zmodem
To   : Gryphon
From : Digital Man
Date : Wed Aug 31 2005 02:28 pm

  Re: Re: zmodem
  By: Gryphon to Digital Man on Wed Aug 31 2005 10:43 am

 > DM>  > DM>  > Ok, disregard my last message.  I tried it right after that me
 > DM>
 > DM>  > DM>  > was able to download a file just fine.  However, I tried uploa
 > DM> a
 > DM>  > DM>  > nothing happend with SyncTERM.  I had to wait for zmodem to ti
 > DM>
 > DM>  > DM>  > BBS.
 > DM>  > DM>
 > DM>  > DM> Did you hit Alt-U to start the upload?
 > DM>  >
 > DM>  > Ok, I reran the tests.  The results were inconsistant.  I tried to UL
 > DM>  > file. Hit Alt-U, and the transfer window came up.  It went to 100%, a
 > DM> just
 > DM>  > sat there.
 > DM>
 > DM> When the file transfer is complete, you have to hit a key (it should say
 > DM> a
 > DM> key to continue" in the file transfer log box). If it's not displaying
 > DM> anything
 > DM> in the main box of the file transfer window, then you probably have the
 > DM> log_level set to 0 (which is a common bug in SyncTerm).
 > 
 > I did not get any such prompt. I will have to check the log level.
 > 
 > DM>  > After waiting several seconds for it to go away on it's own, I
 > DM>  > hit ESC.  Then I got a bunch of high-ascii gargage on the screen.
 > DM>
 > DM> And what was displayed on the BBS/server side at this time? It sounds li
 > DM> BBS side aborted the transfer.
 > 
 > The only thing displayed is the high-ascii garbage. 

You don't have a log or status or something on the BBS/server side that says
what's going on?

 > It seems to me that the
 > BBS did NOT abort the transfer, as that high-ascii is really the data being
 > sent to the screen.

If SyncTerm is displaying the high-ascii data, that means it's *receiving* it
from the BBS. Which means the BBS is echoing it back, which means the BBS-side
stopped the transfer prematurely.

                                                  digital man

Snapple "Real Fact" #107:
You burn more calories sleeping than watching TV.

.