Poor ol' Jimbo still can't get the modem going...
> Sadly, I fear that the root of my actual problem here has more to do
> with my init strings as suggested by Tim Jackson. I'm using a Pace 56k
> external modem with the string *AT&F&D2. *I read the Pace manual which
> says that AT&F alone should be sufficient, but then it didn't work at
I know this wont be terribly useful, but I may as well say it..
I have a Pace 56K External modem just the same, I got it when I bought
NC2 some while back. I tried all sorts of init strings with it since
at the the time the Modem Expert (Neil B.) was being rather
forthcoming with the info. After all that I decided that the best
init was to just leave it at the defaults, ie: send "AT&F\r" as init,
"ATDT" to dial, and just "\r" as dial suffix. It has worked perfectly
here for many months. And yes, I'm with UKOnline too.
Things which did screw it up which I found out about...
- Setting the comms compter<->modem at anything in *between* 33600 and
115200. I currently use 115200 with a SurfSquirrel.
- Reducing the "Command Delay" in Genesis->Modem/TAs->Commands to less
than about 15.
Someone asked what the "\r" was - modems are terminal based thingies,
it means linefeed.
Hmm... Update... I just found your original description of your
problem. Something occurs to me! I found AmTerm crashed every time
until I updated my Squirrel drivers. Maybe its related. They are
(were?) somewhere on the Hisoft site. If you can't find them, mail me
privately and I'll send them to you. I'm using:
squirrelserial.device 37.565, surfsquirrel.library 40.45
Hoping it will help,
Ian
===
