Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!apple!oliveb!pyramid!leadsv!oetl!alan
From: alan@oetl.UUCP (Alan Strassberg)
Newsgroups: comp.dcom.modems
Subject: Re: using TB+ modem to call slow and PEP sites
Keywords: telebit modem
Message-ID: <418@oetl1.oetl.UUCP>
Date: 20 Feb 89 18:39:24 GMT
References: <822@vicorp.UUCP>
Reply-To: alan@oetl.UUCP (Alan Strassberg)
Organization: Lockheed Missiles & Space Co., Santa Cruz, CA.
Lines: 26

In article <822@vicorp.UUCP> dale@vicorp.UUCP (Dale Nielsen) writes:
>I have a TB+ modem that I'm using to connect to several different
>uucp sites.  One of them has a TB+ modem, while the others just
>have 2400 baud modems.  The problem is that when I call the PEP site
>their modem answers at 2400 baud before it tries PEP high speed mode,
>so I end up hooking up at 2400 rather than PEP.  If I set the modem

	This problem is solved by setting S50=255 and S7=60
	in your modem initialization string. This 'locks' the 
	modem at 9600. Since you may not want this all the time
	you could define two types of modems in your L-devices
	with different init strings.

	In response to the other person whose modem stays at
	2400 after answering at 2400, posted to the net was
	a package called 'modem' which esentially respawns
	the modem getty and sends an initialization string.
	This would reset the modem to default parameters.
	This is esentially the same as 'uugetty' also posted.

				alan
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Alan Strassberg	      	     UUCP: alan@oetl   ..{leadsv,pyramid}!oetl!alan
Lockheed, Santa Cruz, Ca.    work (408) 425-6126   	
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-