Anthony, at 15:49 on Sat, May 28 1994, you wrote to Bill Grimsley ...

BG> imports (I bet the USR never barfs at your dialtones),

AM> Almost never.  It gets and ATZ^M for it's pains if it does. ;)

Interesting that although our tones are completely different, they're still
recognised exactly for what they are by the Sportster.

AM> I really can't see what the problem is.  The sportster sounds 
AM> very sure of itself.  For instance, it always waits for at least 
AM> three beeps of an engaged signal to make sure that it's still not 
AM> the two beeps of a weird ring tone, and almost always identifies 
AM> it by the end of the third.

Yep, exactly the same here, except mine recognises BUSY after it has heard
just two complete beeps. It also recognises the long single faulty tone as
BUSY as well, after about 3 seconds. I was most impressed (and still am).

AM> The Maestro 2400 needed about 5 busy beeps and hung up in the middle 
AM> of the next.  Pathetic. 

Worse than that, it's almost unforgiveable in a locally made modem.

AM> If there's one thing that the Sportster is a bit nasty with, it's 
AM> how long it defaults to waiting for a dial tone.  I can't remember if 
AM> there is an override S variable for that?  Not usually a problem for 
AM> me on an AXE exchange though.

Not if you're using X2 or X4, I'm afraid, although blind-dialling with X1
or X3 will allow you to specify the wait-for-dialtone time with S6
(defaults to 2 seconds).

BG> given the paltry amount of files I download, 14k4 will do me for a 
BG> while yet.

AM> 90% of my modem calls are for mail, and who cares if it takes about 
AM> 4min/day instead of 2min with a V34? 

Yep, my sentiments exactly.

AM> Same reason I have a 386DX40 instead of a 486DX33 - too little 
AM> benefit except for Intel. Might as well wait till I feel like 
AM> splurging on a super-duper 486...

Buy a house first.  ;-)

Regards, Bill

--- Squish/32 OS/2