Newsgroups: comp.binaries.ibm.pc.d
Path: utzoo!utgpu!cunews!bnrgate!bigsur!bcars53!mussar
From: mussar@bcars53.uucp (G. Mussar)
Subject: Re: RZSZ.TLB - VMS ZMODEM send/rcve prg & doc (Text LIB file)
Message-ID: <1990Nov18.214535.27363@bigsur.uucp>
Sender: news@bigsur.uucp
Organization: Bell-Northern Research, Ottawa, Canada
References: <1990Nov17.062459.9537@nas.nasa.gov>
Date: Sun, 18 Nov 90 21:45:35 GMT

In article <1990Nov17.062459.9537@nas.nasa.gov> roelofs@amelia.nas.nasa.gov writes:
>wilker@descartes.math.purdue.edu.UUCP (Clarence Wilkerson) writes:
>or what have you.  The reason is that rz/sz, like most mainframe comm
>protocols, send data by writing it to the screen and receive it by read-
>ing from the "keyboard" (i.e., stdin).  It is the PC end of things which 
>controls the phone line and either "types" the data out the phone line 
>or intercepts it before it gets to your screen (depending on whether
>you're uploading or downloading, respectively).  The mainframe packages 
>have no way to associate themselves with a communications port, much less 
>dial out and deal with the initial connections, logging in, and other 
>stuff.
>
>But don't take MY word for it...from Forsberg's rz documentation (version
>3.03 / 25 May 1989, but still applicable, presumably; the sz documentation
>has the same disclaimer):
>
>	Rz is not intended be called from cu(1), or other communica-
>	tions   programs.    Unix   flavors   of  Omen  Technology's
>	Professional-YAM communications software are  available  for
>	dial-out applications.
Yes, I know Chuck Forsberg said rz/sz are not intended to be called from cu(1)
or other comm packages, but, I regularly call rz/sz from tip and it works fine.
I'm sure he would be much happier if you bough his Pro-YAMM package to do the
same thing...

--
-------------------------------------------------------------------------------
Gary Mussar  |Bitnet:  mussar@bnr.ca                  |  Phone: (613) 763-4937
BNR Ltd.     |  UUCP:  ..uunet!bnrgate!bcars53!mussar |  FAX:   (613) 763-2626