jfh@rpp386.UUCP (John F. Haugh II) (07/23/88)
In article <273@mjbtn.UUCP> root@mjbtn.UUCP (Mark J. Bailey) writes: >Hello, > >I am having an annoying problem that some of you may have also experienced. > >I have 1) Mitsuba 2400 Internal Hayes compat. modem and 2) Prometheus 2400P >External Modem and my Tandy 4000 '386 system running SCO Xenix 2.2.2. I have >my modems set to answer at 2400 baud and then cycle to 1200 on a CR and then >back to 2400. They are supposed to reset to 2400 baud at logoff, aren't >they? Well, what is happening is that on initial setup, they answer the >first calls just fine, and then when the user logs off, they answer the >next call properly at 2400 baud ... sometimes. At other times, they seems >to get "stuck" in a 1200 baud mode, and that is where they stay, regardless >of getty sending at 2400 (supposedly), they still answer at 1200 baud. this seems to be a very common problem with 2400 baud hayes compatible modems, hence the posting. the problem arises whenever a connection is received at 1200 baud and the modem is not reset. some of the modems have a setting which allows the modem to be reset whenever DTR drops. i'm unfortunate enough to not fall in that catagory, so i know of what i speak ;-( if you modem does not have a command option to reset the modem on hangup, and you are equally unfortunate to have the 1200 baud problem, there is nothing you can do outside of resetting the modem on each hangup. the simple fix is to write a wrapper around getty and have it reset the modem on each invocation. just a word to the wise, you have to fork a child to do the actual talking to the tty port because the process group will get messed up. not enough room to explain it here, just trust me. if you are unfortunate enough to be stuck with micropoor unix and its perverse getty, you are in real trouble. i understand installing your own version of getty is very difficult. you know what they say, "surf sco or go home" (sorry eric) - john. -- John F. Haugh II +--------- Cute Chocolate Quote --------- HASA, "S" Division | "USENET should not be confused with UUCP: killer!rpp386!jfh | something that matters, like CHOCOLATE" DOMAIN: jfh@rpp386.uucp | -- with my apologizes
root@ozdaltx.UUCP (root) (07/23/88)
I have the same problem with an Incomm 2400b modem, too.
The Incomm people says I have to send the modem a command to
reset it to 2400 after the last close.
I too, would be interested in answers.
--
Scotty
AIDS INFORMATION EXCHANGE BBS (214) 247-2367/247-5609
"Education is the best weapon"
{ames,mit-eddie,rutgers,osu-cis,lll-winken,texsun,smu}!killer!ozdaltx!sysop mikej@dasys1.UUCP (Mike Johnston) (07/24/88)
In article <273@mjbtn.UUCP> root@mjbtn.UUCP (Mark J. Bailey) writes: >I am having an annoying problem that some of you may have also experienced. >my modems set to answer at 2400 baud and then cycle to 1200 on a CR and then >back to 2400. They are supposed to reset to 2400 baud at logoff, aren't >they? Well, what is happening is that on initial setup, they answer the >first calls just fine, and then when the user logs off, they answer the >next call properly at 2400 baud ... sometimes. At other times, they seems >to get "stuck" in a 1200 baud mode, and that is where they stay, regardless I have had similar problems. A partial victory might be achieved by setting your modems to reset on a dtr change. I.E. ATD0 I believe. Thus, when the getty drops the line (dtr low) the modem performs an ATZ on itself and resets back to 2400 baud. This has worked somewhat well on my machine but sometimes the modem just loops on itself and continually resets for hours until someone turns it off. I am using a Hayes 2400 external on an Altos 2086 running Xenix. If someone else has a more elegant solution I'd sure like to hear it. +-----------------------------------------------------------------------------+ |Michael R. Johnston / cpmain!mrj | |Franchise Data Specialist ....cmcl2!phri!dasys1! | |Career Employment Services Inc. \ mikej | | ".......but it was working just yesterday.........." | +-----------------------------------------------------------------------------+
mikej@dasys1.UUCP (Mike Johnston) (07/25/88)
iThe command to accomplish this is AT&D3. Send it to the modem and save it with an AT&W. +-----------------------------------------------------------------------------+ |Michael R. Johnston / cpmain!mikej| |Career Employment Services Inc. \ mikej | | ".......but it was working just yesterday.........." | +-----------------------------------------------------------------------------+
jfh@rpp386.UUCP (John F. Haugh II) (07/28/88)
In article <5716@dasys1.UUCP> mikej@dasys1.UUCP (Mike Johnston) writes: |In article <273@mjbtn.UUCP> root@mjbtn.UUCP (Mark J. Bailey) writes: |>I am having an annoying problem that some of you may have also experienced. |>my modems set to answer at 2400 baud and then cycle to 1200 on a CR and then |>back to 2400. They are supposed to reset to 2400 baud at logoff, aren't |>they? | |I have had similar problems. A partial victory might be achieved by setting |your modems to reset on a dtr change. I.E. ATD0 I believe. Thus, when the |getty drops the line (dtr low) the modem performs an ATZ on itself and |resets back to 2400 baud. this has the nasty side effect for non-hayes modems of possibly resetting the D0 flag after the reset, which causes the next hangup to NOT reset the modem. for hayes modems you must remember to store the command into non-volatile memory so that the reset will not turn off that option. - john. -- John F. Haugh II +--------- Cute Chocolate Quote --------- HASA, "S" Division | "USENET should not be confused with UUCP: killer!rpp386!jfh | something that matters, like CHOCOLATE" DOMAIN: jfh@rpp386.uucp | -- with my apologizes