[comp.sys.mac.comm] ZTerm .85 & unix sz question

peter@hari.VIEWlogic.com (Peter Colby) (08/24/90)

        I have been using ZTerm 0.85 along with sz on the unix side on
and off for a while now to transfer files from a Sun workstation at work
to my Mac+ at home. My modem speed is 2400 (though I have the same problem
at 1200). The problem I am having is twofold.
        1) I have never been able to transfer multiple files successfully.
           The first file comes across OK but after that I lose every other
           file, or hang.
        2) When transfering a single file; once the file is complete, ZTerm
           indicates a successfull transfer... But there is frequently "junk"
           from the sz (unix) side that is left in the command line for the
           shell to interpret with the next command entered. In other words,
           it appears that ZTerm stops receiving before sz is totally finished
           and the remainder of the output from sz ends up on stdin for some
           reason.

        Am I doing something wrong or is this a known problem with ZTerm/sz?

        Do I need a different version of the UNIX side sz (if so, where do I
pick up sucha working version... I do have internet ftp access).

        Aside from all that, ZTerm seems to have trouble completing a partial
download. Also, exactly WHAT do I do with a "ZTerm binary file", the file
type created from a binary transfer of a NON-MACBINARY file?

        Thanks for any help I can get!

        Peter C


      (O)(O)(O)(O)(O)(O)(O)(O)(O)     (O)(O)(O)(O)(O)(O)(O)(O)(O)
      (O) !the doctor is out! (O)     (0) peter@viewlogic.com (0)
      (O)(O)(O)(O)(O)(O)(O)(O)(O)     (O)(O)(O)(O)(O)(O)(O)(O)(O)

ins_apw@jhunix.HCF.JHU.EDU (Philip Wong) (08/25/90)

Hmm, i've been using sz and zterm for a while...the batcdh transfer is great!
I have never had any problems...I can start a multiple file transfer, leave
and come back with the job done.  Looks like the problem is with your unix,
vax, or whetever you're hooked onto.

ins_apw@jhunix.hcf.jhu.edu

wiseman@tellabs.com (Jeff Wiseman) (08/28/90)

In article <1990Aug24.144316.16617@viewlogic.com> peter@hari.VIEWlogic.com (Peter Colby) writes:
>
>        2) When transfering a single file; once the file is complete, ZTerm
>           indicates a successfull transfer... But there is frequently "junk"
>           from the sz (unix) side that is left in the command line for the

I have seen this too although I just hit return and it goes away! It never
affected the ability to transfer files, though. I predominantly use sb (ymodem)
though since I go through a network to get to the computer.

Sounds like you have two distinct problems. The "garbage" at the end of a
transfer (on the zterm window) has never affected my batch transfers, either.


--
Jeff Wiseman:	....uunet!tellab5!wiseman OR wiseman@TELLABS.COM

ckd@cs.bu.edu (Christopher Davis) (08/28/90)

Peter> On 24 Aug 90 14:43:16 GMT, peter@hari.VIEWlogic.com (Peter Colby) said:

Peter>         I have been using ZTerm 0.85 along with sz on the unix side
Peter> on and off for a while now to transfer files from a Sun workstation
Peter> at work to my Mac+ at home. My modem speed is 2400 (though I have
Peter> the same problem at 1200). The problem I am having is twofold.

Peter>         1) I have never been able to transfer multiple files
Peter> successfully.  The first file comes across OK but after that I lose
Peter> every other file, or hang.  2) When transfering a single file; once
Peter> the file is complete, ZTerm indicates a successfull transfer... But
Peter> there is frequently "junk" from the sz (unix) side that is left in
Peter> the command line for the shell to interpret with the next command
Peter> entered. In other words, it appears that ZTerm stops receiving
Peter> before sz is totally finished and the remainder of the output from
Peter> sz ends up on stdin for some reason.

Peter> Am I doing something wrong or is this a known problem with ZTerm/sz?

Peter>         Thanks for any help I can get!

I have had similar problems.  I believe they are due to telnet having escape
character problems... try rlogin or a direct serial connection if you can.

--Chris
--
   Christopher Davis, BU SMG '90  <ckd@cs.bu.edu> <...!bu.edu!cs.bu.edu!ckd>
     "Dammit, we're all going to die, let's die doing something *useful*!"
	 --Hal Clement on comments that space exploration is dangerous