Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucselx!crash!hrlaser
From: hrlaser@crash.cts.com (Harv Laser)
Newsgroups: comp.sys.amiga
Subject: Re: JRComm doesn't like my Modem
Message-ID: <6016@crash.cts.com>
Date: 1 Dec 90 15:07:26 GMT
References: <36319@cup.portal.com>
Organization: Crash TimeSharing, El Cajon, CA
Lines: 28

In article <36319@cup.portal.com> Lee_Robert_Willis@cup.portal.com writes:
>
>I've read a lot of good things about JRComm from this group, so I decided
>to give it a try.  PROBLEM: JRComm doesn't talk to my Modem.  When I try to
>dial a number, nothing happens.   I have a SupraModem 2400, which works
>just fine with every other comm program I've tried.   I've looked through
>the JRComm docs and my Modem docs, and I have no idea what the problem is.
>Anybody got a helpful suggestion?
>
>Lee		Lee_Robert_Willis@cup.portal.com

I ran into another guy on Plink recently who described the same problem
you did. Turns out when he downloaded, unpacked, and installed JRComm
(1.01) he never checked the baud rate setting.  It came setup/defaulted
to 9600 so of course he couldn't send any commands, including his
first attempt at a dialing command, to his 2400 baud modem. Soon as he
changed the baud rate to 2400, all was fine and the program functioned
well for him.  Many terminal programs look at the Preferences setting
for baud rate and inherit it... this has caused many people using such
programs to set and save their preferences baud rate to 2400. If those
same people then download and try to start using JRComm, which fires
up the first time set to 9600, it's not going to work. Could that be
the cause of the problem you were having?



Harv Laser                                      {anywhere}!crash!hrlaser
"Park and lock it.  Not responsible."           People/Link: CBM*HARV