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

  Re: Re: zmodem
  By: Gryphon to Digital Man on Wed Aug 31 2005 11:07 am

 > DM>  > On 08-27-05, Digital Man said...
 > DM>  >
 > DM>  > DM>   Re:Re: zmodem
 > DM>  > DM>   By: Gryphon to Digital Man on Wed Aug 24 2005 01:53 pm
 > DM>  > DM>
 > DM>  > DM>  > DM>  > Well.. no.  Not about *this*issue
 > DM>  > DM>  > DM>
 > DM>  > DM> > DM> Would you care to?
 > DM>  > DM>  >
 > DM>  > DM>  >
 > 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, another test.  I tried to upload a file that 1218426 bytes.
 > DM>
 > DM> Where (i.e. what BBS running what BBS software and file trasnfer protoco
 > DM> driver) ?
 > 
 > This is all done from my BBS running Mystic/Linux, or on the linux command
 > line.

And does Mystic/Linux not display or log anything about the file transfer and
what went wrong?

 > DM>  > It got to
 > DM>  > 85376 bytes (7%) then it appeared to have no activity for several sec
 > DM> to
 > DM>  > almost a minute.
 > DM>
 > DM> Nothing in the file transfer progress window (see my previous post about
 > DM> log_level value).
 > 
 > I can't verify the log level value other than it is set to 'warning'.

It should be set to "info".

 > I also verified that the UL/DL paths are correct.

That's not the problem.

 > DM>  > I hit escape and the transfer window went away.  However
 > DM>  > that din't stop the upload process it would seem.  I get the hight-as
 > DM>  > gibberish again, and had to hang-up to get out of it.
 > DM>
 > DM> That would be the BBS echoing *back* to you the data it received after i
 > DM> aborted the file transfer. If this is *your* BBS, then knowing what was
 > DM> logged/displayed on the BBS-side could be helpful. It sounds like the BB
 > DM> is aborting the transfer.
 > 
 > You are likely correct in that the BBS aborted the transfer, where SyncTERM
 > continued the transfer.  However, I have never had this happen with mTelnet.

I'm just explaining what the "garbage" you're seeing is. Without more details
about *why* the BBS aborted the transfer, I can't guess what the problem is.
I'll try calling your BBS and see what I can reproduce.

 > Also, I know the version of SyncTERM is over a month old.  ST does not
 > display version info, but the filedate is July 11.

You should upgrade. :-)

                                                  digital man

Snapple "Real Fact" #108:
Licking a stamp burns 10 calories.


.