home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.modems
- Path: sparky!uunet!indetech!wetware!wsrcc!wolfgang
- From: wolfgang@wsrcc.com (Wolfgang S. Rupprecht)
- Subject: Re: Worldblazer not autobauding correctly at 38400
- Message-ID: <BzIvEF.E9@wsrcc.com>
- Organization: W S Rupprecht Computer Consulting, Fremont CA
- References: <1992Dec15.053712.2492@clarinet.com> <1992Dec19.091753.18781@netcom.com> <1992Dec19.104747.8823@clarinet.com>
- Date: Sat, 19 Dec 1992 19:56:38 GMT
- Lines: 31
-
- brad@clarinet.com (Brad Templeton) writes:
- >Sorry for making you type such a long message, but I of course have the
- >modem set in &D3 mode, and have always set my modems that way for years.
- >I can't imagine setting a modem any other way and feeling safe.
- >And yes, DTR is definitely dropping, for a full second, before the new
- >getty takes over, and then, as far as I know, nobody is talking to the
- >modem before the call comes in.
-
- On a TB+ I noticed reset problems with exactly the same setup. I
- wonder how much of the TB code the WB inherited.
-
- Two things that I found helped a lot:
-
- 1) configure the kernel to keep DTR low for much more than 1 second.
- The TB just didn't reset reliably even at 3 seconds. I finally
- picked 7 seconds as a good compromised between resetting and dying
- of boredom on a tip(1) redial.
-
- 2) *Never* let anyone use the manual disconnect switch on the modem.
- This thing causes the DTR reset to be totally ignored.
-
- 3) Don't let anyone that doesn't have a trailblazer call in. ;-) My
- biggest problems were the modem being stuck in PEP mode w.
- uucp-spoofing on after a uucp call out. The next call, if it was a
- plain-jane 2400 baud modem couldn't connect.
-
- -wolfgang
-
- --
- Wolfgang Rupprecht wolfgang@wsrcc.com (or) decwrl!wsrcc!wolfgang
- Snail Mail: 39469 Gallaudet Drive, Fremont, CA 94538-4511
-