Date: Tue, 24 Oct 1995 20:41:55 -0700 (PDT) From: John-Mark Gurney <gurney_j@nike.efn.org> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: "Serge A. Babkin" <babkin@hq.icb.chel.su>, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG, ache@FreeBSD.ORG Subject: Re: startslip isn't just broken - it's EVIL! Message-ID: <Pine.NEB.3.91.951024204057.6685E-100000@nike.efn.org> In-Reply-To: <11667.814539479@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 24 Oct 1995, Jordan K. Hubbard wrote: > > > > > > > Guys! Use slattach and chat, and save yourselves the stress 8) > > > > > > I've never managed to get that combo to work! Chat just dies > > > immediately.. :-( > > > > I got it working under 2.0. There were some strange problems but in > > common it worked. I remember that chat does not understand the dial-up > > string in the command line, it needs a file with it. > > No, that's not the problem here - I have my chat script in a file and > that very same chat script works just fine with chat if I *don't run > it from slattach*. When run from slattach, chat blows up when it > first tries to talk to the port. I don't know what's wrong, but > slattach clearly isn't setting up things correctly before invoking the > external script. I tried for quite a few days to get this to work > and finally gave up in disgust. did you put in a sleep before calling the chat script? It looks like you have to sleep 2 before you call the chat script to let the line settle down after slattach dropped and raised dtr on the modem... this might help... TTYL.. John-Mark gurney_j@efn.org Modem/FAX: (503) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.91.951024204057.6685E-100000>