> Mike Rosenberg <mikePOSTTOGROUP.invalid> wrote:
> > John Wain <johndisneyland.com> wrote:
> > > If A tries to dial while B is connected, we would expect A to get a busy
> > > signal and its call simply to abort with a message from Remote Access.
> > That's not what you should expect at all. Pretend you're talking about
> > a voice line instead. Person B is on the phone already. Person A picks
> > up another phone and doesn't even dial, hearing that the phone is
> > already in use. If person A tries to dial anyway, he doesn't get a busy
> > signal, because the call can't go through at all.
> Yes, of course. Silly me!
> > It sounds like the
> > Modem control panel is set to ignore dial tone. (Or is this in Remote
> > Access? I'm running OS X right now and these control panels aren't
> > supported in Classic.) If you change it to NOT ignore dial tone, when
> > B is using the phone line, A won't get a dial tone, won't attempt to dial,
> > and B's connection will be maintained.
> It's true that ONE of the dialers was set to ignore dial tone. I
> suddenly remembered that we had to set it that way because that modem
> did not recognise our line's dial tone. Since then the line quality
> having changed as far as other experiences tell me, I might be able to
> revert to the default setting.
> However, the problem of interrupting the ongoing communication occurs on
> both machines. It seems that just listening for the tone is enough to
> trip the other modem, just as is often the case if someone picks up an
> extension handpiece.
> Now there is a secondary problem. Suppose A wants to dial while B is
> already on line, and all goes as it should: no dial tone. I haven't done
> extensive testing of this on system 8.6 (which is the one used on my
> LAN), but I seem to recall Remote Access hanging forever on some
> occasions, probably waiting for a tone. And when this happened I
> actually had to crash the machine to get out of Remote Access.
> This behaviour is in any case what I get on my 3rd machine (ibook not
> networked running OS 9.2.2). I think the whole communication software in
> 9.2.2 is buggy. RA worked every other blue moon when I tried to dial for
> internet, until I imagine the kludge of sending a whole string of AT
> commands to the modem each time I get RA to dial. (No problem at all
> with the modem when I am booted in system X.) Before that, when RA
> failed to dial there was no way of regaining control apart from a hard
> reset of the machine.
> Now I would very much like to know if there is a way to set a timeout on
> RA itself.