Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!umich!vela!parker From: parker@vela.acs.oakland.edu (Jeff Parker) Newsgroups: comp.sys.amiga.datacomm Subject: Re: sz is buggy Message-ID: <7478@vela.acs.oakland.edu> Date: 24 Jun 91 01:40:01 GMT References: <231b3678.677569364@fergvax> <1991Jun23.001334.16257@menudo.uh.edu> Organization: Oakland University, Rochester MI. Lines: 39 honp9@menudo.uh.edu (Jason L. Tibbitts III) writes: >In article <231b3678.677569364@fergvax> 231b3678@fergvax.unl.edu (Phil Dietz) writes: >>The problem is not with jrcomm, but with sz. >> I agree. I have never used jrcomm but have the exact same problem with VLT and XPRZmodem v2.10. >>If you didn't know, sz source tries to include as many UNIX versions as >>it can (like BSD, SYS V, etc.) Before our VAX got a new system upgrade, >>sz ran perfectly fine under ULTRIX 3.x. Now with ULTRIX 4.1, sz has >>the same problem as many of you-- send only one file out of a list. >> Once again, I agree. My problems only appeared once we upgraded to Ultrix 4.1. >SZ works fine on our Ultrix machine. I FTP'd and brought up the latest >version without a hitch. Here's the version string: >3.11 02-26-91 for V7/BSD by Chuck Forsberg, Omen Technology INC As Phil was trying to point out, it isn't just the version of sz but the interaction of sz and Ultrix 4.1. I have been living with it by writing shell scripts to send the files I want one at a time or writing VLT scripts to get the ones I want. However, the problem doesn't show up every time, only about 70% of the time. Now that I know there are others out there with problems, I plan on contacting the systems group and seeing if they know what the heck is going on. Maybe we can figure this one out soon. I miss typing sz *. Jeff P. -- Jeffrey D. Parker | Men always want to be a woman's first love, INET: parker@vela.acs.oakland.edu | women like to be a man's last romance. BITNET: PARKER@OAKLAND | UUCP:...!umich!vela!amiga1!fanatic | Samuel Butler