Paul, at 13:23 on Jan 28 1996, you wrote to Bill Grimsley...

BG> the fact that nobody else has EVER described the problem would indicate to 
BG> me that the problem is not with the modem, but the manner in which it's 
BG> being used.  

PE> I was the first person to document the Spirit double-sending bug,
PE> the first person to encounter it with a Maestro SE 9600, the 
PE> first person to find their modem spewing garbage at them at
PE> 38400 bps when the caller had long pissed off.  No thanks, Bill.

Please yourself then.  I'm trying to help, but you appear to have a
completely negative attitude towards anything I say or suggest.  And I
don't believe that you were the first to see those S2 bugs anyway, unless
you've been in constant contact with every S2 owner in the world (which
just happens to be slightly bigger than Paul's lounge-room).

PE> Yes, if I save at 57600, and then run my comm port at 57600, everything is 
PE> hunky dory. 

Then what the fuck are you complaining about?  Why anybody would want to
run a modem capable of transferring COMPRESSED files at over 4000cps, on a
serial port restricted to no more than 3840cps is completely beyond me.

PE> What I want to do is save my config at 57600, run my com port at 38400, and 
PE> then get the modem to switch the RINGs to 38400 as soon as it gets an AT 
PE> command from me. 

Why?  What possible reason could you have to want to do that?  As far as
callers are concerned, it makes absolutely NO difference to them at what
speed your serial port is locked.  None at all.

I've given you the solution.  It's up to you to use it.

Regards, Bill

--- Msgedsq/2 3.20