Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!daver!zorch!xanthian From: xanthian@zorch.SF-Bay.ORG (Kent Paul Dolan) Newsgroups: comp.sys.amiga.introduction Subject: Re: Modem Woes Message-ID: <1991Apr9.143800.10810@zorch.SF-Bay.ORG> Date: 9 Apr 91 14:38:00 GMT References: <1991Apr5.122933.1@watt.ccs.tuns.ca> <8718@ucdavis.ucdavis.edu> Organization: SF-Bay Public-Access Unix Lines: 19 In addition to the steps Dan recommends, Hayes modems (and, presumably, the compatibles as well) require a significant effort of setup programming before you can use them for communications, among other things to make sure that you are talking the same bit and byte "language" that the modem is currently expecting. Some of the "quasi-compatibles" do part or all of this programming by "dip switches" (physical hardware), rather than by software-to-stable-memory controls. Special things to look for are that your emulator program is set up to talk the right symbol size (seven or eight bit), parity (even, odd, mark, or none), stop bits (2, 1 or 0), and speed (300, 1200, 2400, 4800, 9600, etc. baud) as your modem is expecting at initial program setup time, or corresponding to the way you have the dip switches set, as appropriate for your modem. Problems in any of these areas can make the modem seem broken when in fact there is just a misunderstanding about protocol between your terminal emulation software and your modem software/hardware. Kent, the man from xanth.