Path: utzoo!utgpu!water!watmath!uunet!labrea!agate!eos!ames!zorch!pacbell!att!mtunx!mtune!ethos!pcid!gizzmo!fthood!egray From: egray@fthood.UUCP Newsgroups: unix-pc.general Subject: Re: Using PCOMM Message-ID: <10900006@fthood> Date: 24 Jun 88 13:31:00 GMT References: <417@kosman.UUCP> Lines: 40 Nf-ID: #R:kosman.UUCP:417:fthood:10900006:000:1649 Nf-From: fthood.UUCP!egray Jun 24 08:31:00 1988 Reference: getting Pcomm to work with trailblazer Pcomm has a "feature" that is a blessing for some, and a curse for others. It has to do with the ability to automatically sync the TTY to a different baud rate. Here is what I intended: 1) You can't remember if a remote system has 2400 baud or 1200 baud modems, so you pick 2400 baud to call them. 2) Your TTY (and modem) are set to 2400 baud to place the call. 3) Lo and behold, they only have 1200 baud modems and you get the "CONNECT 1200" message. 4) At this point, your modem has sync'ed at 1200 baud, the remote system's modem has sync'ed at 1200 baud, BUT THE TTY IS STILL AT 2400 BAUD! 5) Pcomm will check the return message from the modem (ie. the "CONNECT 1200") and determine that the baud rate to the TTY should be changed. For you guys with trailblazers locked at 9600 baud, this is definately not what you want. You need to disable the "autobaud detect" feature of Pcomm. The way to do this, is to change all the connect strings to "CONNECT". Pcomm checks to see if the connect strings are the same; if they are, it skips the autobaud stuff. Also, if the trailblazer is locked at 9600 baud, shouldn't all the dialing directory entries have the baud rate set to 9600 rather than the speed at which they answer??? I'm gonna have to get me one and play with it a few days... Emmet P. Gray US Army, HQ III Corps & Fort Hood ...!uunet!uiucuxc!fthood!egray Attn: AFZF-DE-ENV Directorate of Engineering & Housing Environmental Management Office Fort Hood, TX 76544-5057