home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!The-Star.honeywell.com!umn.edu!lynx!lynx.unm.edu!jwaters
- From: jwaters@deepthought.unm.edu (Joe Waters)
- Subject: Re: Good comm program?
- Message-ID: <JWATERS.92Jul22170028@deepthought.unm.edu>
- Date: Thu, 23 Jul 92 00:00:28 GMT
- Organization: The University of New Mexico, Albuquerque, NM
- In-Reply-To: smp@myamig2.myamiga.mixcom.com's message of 20 Jul 92 18:16:32 GMT
- References: <arumble.711622204@extro.ucc.su.OZ.AU> <9207201343@myamig2.myamiga.mixcom.com>
- Lines: 33
-
- In article <9207201343@myamig2.myamiga.mixcom.com> smp@myamig2.myamiga.mixcom.com (Steve Palm) writes:
-
- > arumble@extro.ucc.su.OZ.AU (Anthony Rumble) writes:
- > :
- > : If *SOMONE* could post a *GOOD* port of Minicom (One that works) we
- > : might just have a good Comms package..
-
- > Before I post . . .
-
- > I have Minicom working just great. It only has ONE problem on my system.
-
- > For up/downloads, it opens a window to show status. It's opening a pipe
- > to capture the output of the transfer command, and sending that to the
- > input of the window...
-
- > Are pipes buffered? Because output to that window is only updated after
- > quite some stuff has flowed through, making it useless as a status box.
-
- > If this doesn't bother anyone, I'll put it up somewhere.
-
- Uhh, I uploaded a completely working version of minicom, along with a
- port of the newest version of sz/rz (with zmodem recover, etc) to tsx-11. It's
- sitting in /incoming and should be up in a few days. I guess I'll go throw a
- copy up on banjo in /pun/Linux/Incoming as well after I catch up news. Look
- for it in a couple hours :-)
-
- Joe
- --
- Joe Waters ("Falc") [jwaters@deepthought.unm.edu]
- "If brute force can't fix the problem, it means you're not using enough."
- Linux is better.
-
-
-