PE> Problems with USR Courier V34+
PE>               
PE> Note: Supervisor Date = 1995-07-18
PE> DSP Date        = 1995-07-05

DD> I'm still using the 07/05/95 version (both dates).

American date format or Australian?

PE> 1. After receiving an "AT" command at a particular baud 
PE> rate, the modem does not adjust to that baud rate, and 
PE> instead stays at the rate at the time of last "AT&W".

DD> You mean the port rate doen not change to the speed of the last AT command 
DD> when an incoming call appears(?) This is documented in the manual - that is 
DD> the way it works.

Nope, it is not documented that it sends responses to AT commands
at the same speed I sent them, yet sends the RINGs at the speed
of last &W.

PE> 2. Regularly getting 26400 connects with a Netcomm instead 
PE> of 28800.

DD> Could be your line or theirs . . . . No noticable problem here with NetComm 
DD> modems.

Could be the modem too.  Russell has basically said just that,
at least with the "cheaper" modems.

PE> 3. Modem is initiating a retrain straight after each 
PE> connect, even with V32bis modems.  I would expect that the 
PE> initial negotiation would have figured that out, no need for 
PE> a retrain on every single bloody call.  Yet the ATI6 does not 
PE> show that a retrain was requested.

DD> Dunno about this one - that is I don't know if that happens here or not.

It does.

PE> 4. Having problems talking to a Supra modem, 50% dropouts 
PE> where previously there were none (with a Spirit Thunder 
PE> modem).

DD> Mr Speed's Supra can only manage to connect here at 14,400.

That is correct.  He has a 14400 bps modem.

PE> 5. AT&F1 sets S56 equal to 16 instead of the default of 0 
PE> listed in the manual.

DD> Definitely sets it to 0 (zero) here.  Pehaps you have a
"bad" load of the 
DD> SDL.

Me, Dave Hatch, and most likely Poe Lim also must have a bad load.
The reason I mention Poe is because Dave says he got the settings
from Poe, and S56=0 was one of the things you had to do after &F1.
I wondered why, when that was supposed to be the default.

PE> 6. A Spirit Thunder is getting connects with me at 2400 bps 
PE> far more often than 19200.  1200 bps connects too.

DD> You user has modem illiteracy ptoblems.  He is setting Telix to swap 
DD> baudrates.

He gets the varying connect rates without touching his setup.

PE> 7. USR to USR connect failed due to a retrain failure.  
PE> Also, USR to USR is showing 21600/2400 as the connect rate.

DD> Haven't seen this

I've only had it happen the once so far (that I've seen anyway).

PE> 8. Failed to connect to Hayes modem at all.  Very weird 
PE> sounds coming out.  No problem when I was using a Spirit.  
PE> This actually happened with an older revision of the ROMs, 
PE> and cannot confirm at this stage whether it still exists 
PE> because the modem was taken offline so that I could 
PE> connect.

DD> Don't have any Hayes modems calling me (that I know of)

I can't give you the number to call either!  Ain't that right,
Dave?  :-)

PE> 9. A Netcomm modem (PCMCIA or something) gets connects of 
PE> 1200, 2400, 14400 and 28800 with me.  This also happened 
PE> with the older ROMs, and the caller has not called since I 
PE> changed ROMs, so cannot confirm the continued existance of 
PE> this problem.

DD> The only PCMCIA modem I know of that calls here gets 28,800 stable 
DD> connects.

May have been fixed with the new ROMs.  The next 2.5 weeks
will tell.  BFN.  Paul.
@EOT:

---