Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!wuarchive!uunet!aplcomm!capd.jhuapl.edu!waltrip From: waltrip@capd.jhuapl.edu Newsgroups: comp.sys.next Subject: Re: notes for people installing NeXT SLIP Message-ID: <1991Jun27.100914.1@capd.jhuapl.edu> Date: 27 Jun 91 15:09:14 GMT References: <1991Jun27.071351.17884@milton.u.washington.edu> Sender: news@aplcomm.JHUAPL.EDU Organization: CAPVAX, JHU/APL Lines: 39 In article <1991Jun27.071351.17884@milton.u.washington.edu>, mrc@cac.washington.edu > (Mark Crispin) writes: > > I recently got Louis Mamakos' port of Dial-UP IP for the NeXT > working between my office cube and home slab. > > Here are a few notes that may be useful for someone else: [...note 1 deleted...] > 2) Your modems *must* be hardware flow controlled. This means no > Mac modem cables. If you haven't done so already, call NeXTConnection > (1-800-800-NeXT) and order a pair of NeXT modem cables from them. At > $15/each, that's cheaper than most places sell Mac modem cables. > NeXTConnection is pricey in most of their other stuff but this is a > good deal. > > I made the mistake of thinking I could win with Mac modem cables > and disabling XON/XOFF. I had amazing problems which were clearly due > to buffer overruns. NeXT modem cables and using /dev/cufa /dev/ttydfa > cured the lossage. > Do you think this might be related to characteristics of the machines you were connecting to? I am planning to try to connect to VAX/VMS systems running TGV Multinet which I would expect to support XON/XOFF (since that is the standard VAX/VMS mode). I don't believe I would be able to make it all work together if I have XON/XOFF flow control on the VAX side and hardware RTS/CTS flow control on the NeXT side (or vice versa). Did the systems you were trying to connect to support XON/XOFF? [...notes 3 and 4 deleted...] Thanks for sharing this info. c.f.waltrip Internet: Opinions expressed are my own.