🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.next.software
Article #889

Communications packages (was: Using sz/rz on NeXT)

#889
From: Hugh Secker-Walker
Date: Fri, 06 Nov 1992 15:15
51 lines
3108 bytes
In article <72842@hydra.gatech.EDU> cc100aa@xray.gatech.edu (Ray Spalding) writes:

   In article <LOTTO.92Oct27065915@math.math.berkeley.edu> lotto@math.berkeley.edu (Ben Lotto) writes:
   >...trying to speed up our file downloads by installing zmodem programs sz
   >... but now we don't know
   >exactly how to use them.  We use kermit as our communications program.

   You might try using "tipx" instead of kermit; source code is available
   on ftp.uu.net.
   It's a version of "tip" that's been enhanced to interface with
   zmodem.  Has a nice curses-based progress display.
   It was apparently developed on a Sun; I've been ironing out some
   bugs that appear on NeXTs, and with the interface to my particular
   model of modem.

Is there a decent, basic comm package for the NeXT?
I just recently bought a used NeXTstation, and I'm still having
difficulty getting connected.  I'd like to have PPP, but the campus
network folks aren't being very responsive and I can't afford a third
party service, yet.  For the time being I'm stuck with traditional
modem communications.

I used IComm for a short while but found it very limited: fixed
size 24 x 80 window, no meta key, no 19200 or 38400 DTE (the
advertised 19200 doesn't work for me), only zmodem, progress shown
in an _attention_ panel.  Forget the shareware fee, and bypass the
recycler :-).  I found tip unusable because of all the in-band
escapes.  Haven't tried tipx.  I wrote a tiny program that let any
old terminal window communicate directly with the modem.  That
meant I could log into campus machines and have a 70 line emacs
window, etc, but no file transfers.  Yesterday I grabbed PComm1.2
from c.s.unix.archives, but couldn't get it to work.  So I tried
pcomm from orst.  This is an older version of PComm with a couple
of changes to make it work under NeXT's unix.  Once I learned how
to use it, it performed nicely.  I'm in the process of adding
38400 DTE capabilities and getting uucp setuid to work properly (I
think this was the trouble with PComm1.2).

Before I (and Ben Lotto) spend too much time reinventing the
wheel, could you let me know what you know about low-cost, basic,
decent communications packages for the NeXT?  Email me and I'll
summarize.

If the results are dismal I may write a basic comm application as
a first NeXTstep project.  Any suggestions, pointers, or insights
towards this end would be greatly appreciated.

Thanks.
--
Hugh Secker-Walker                    INTERNET:  hugh@ear-ache.mit.edu
MIT, Research Lab of Electronics      UUCP:      mit-eddie!mit-athena!hugh
Technical Details
Message-ID: <HUGH.92Nov6101517@ear.mit.edu>
Path: arc1-ca.pugleaf.net!sparky!uunet!snorkelwacker.mit.edu!bloom-picayune.mit.edu!news.mit.edu!hugh

Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.software
Path: arc1-ca.pugleaf.net!sparky!uunet!snorkelwacker.mit.edu!bloom-picayune.mit.edu!news.mit.edu!hugh
From: hugh@ear.mit.edu (Hugh Secker-Walker)
Subject: Communications packages (was: Using sz/rz on NeXT)
Message-ID: <HUGH.92Nov6101517@ear.mit.edu>
Sender: news@athena.mit.edu (News system)
Nntp-Posting-Host: ear.mit.edu
Reply-To: hugh@ear-ache.mit.edu
Organization: Massachusetts Institute of Technology
Date: Fri, 6 Nov 1992 15:15:17 GMT
Lines: 51