#SmartLink 2400
3 messages in this thread
Is anybody else using a SmartLink 2400 modem from Hololink (once Link)
Technologies?
I've been using it for a little over a year, and it's fine in every respect
except when trying to autoredial and therefore Scripts) from Access! For some
reason the extended message set messes up the connect signal so that the minute
you get a connection it locks the line up.
I can avoid this by killing the extended set (ATX1) but this also shuts out any
redial or 'cause it never get's a BUSY message.
The versions of Access! before 1.40 did not have this effect .. the redial
worked perefectly.
Anybody got any ideas?
Art,
This problem was only recently brought to my attention… I think I know
_what_ is happening, but am trying to gather a bit more info on it.
Some modems have (as part of the extended result codes) a 'RINGING' result
is this what yours has? Some modems also let you select the 'extent' of the
extended result codes <grin>, is there an 'ATX2' or similar that would set your
modem to give you the 'BUSY' but not the 'RINGING' ?
Now to the problem… _if_ you are getting the 'RINGING' result, Access!
doesn't have any provision for it and defaults to thinking that the call failed
for some reason so it will try to dial again (which, in effect, hangs up your
modem just as you maybe getting connected). There are a few things that you
might try (none of which are pretty, just work-arounds)…
1) if your modem does _not_ echo the 'ATDT1234567' back to you when you dial,
then you could NewZap the "AT" in Access! (where I ignore the number being
echoed back) and change it to "RI". (If you think this way will work, I
can give you more details in the conference or something).
2) if the number you are dialing normally connects on the first ring, you
might get away with a short delay after the number… so that the redialer
doesn't see the "RINGING" until after you are connected. You can add a
delay by adding as many '\w' to the end of your number as you can fit
(Access! will process the '\w' as a "wait for x seconds" and you can
define 'x' using (of all things) the macro keys… see Access!me for
details).
There might be a few other work-arounds, or you might just wait until I
release the next version… it will have some provision for other "to be
ignored " codes.
Sorry for the inconvieniance,
– Keith
Don't you NEVER apologize for the INCONVENIENCE of something in that program
AGAIN! You've got what in the opinion of most of the Amiga Community is the
BEST!!!!! (Notice I did NOT exclude commerical stuff).
There's no way you can cover ALL the bases.
Yep. My modem does report RINGING, and it doesn't seem to interfere except
on redial.
Not sure if there's an X2 option, I'll check that posibility out.
I'll also try the delay and see if that work.
The Zap/change idea sounds interesting, if nothing else works I'll get
back to and see if we can CO about it.
Again, thanks for a GREAT program and always being around to help!
Art