Paul, at 09:13 on Feb 01 1996, you wrote to David Drummond ...

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).

PE> American date format or Australian?

American it seems.

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 
DD>> last AT command when an incoming call appears(?) This is 
DD>> documented in the manual - that is the way it works.

PE> Nope, it is not documented that it sends responses to AT 
PE> commands at the same speed I sent them, yet sends the RINGs 
PE> 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 
DD>> here with NetComm modems.

PE> Could be the modem too.  Russell has basically said just 
PE> 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 
PE>> for a retrain on every single bloody call.  Yet the ATI6 
PE>> does not show that a retrain was requested.

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

PE> 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.

PE> That is correct.  He has a 14400 bps modem.

Would you expect it to connect at better than 14,400 then?

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 
DD>> "bad" load of the SDL.

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

I wonder if the later ROM has the default at 16 then?  What is the setting
after the July05/July05 SDL is loaded?

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

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

PE> He gets the varying connect rates without touching his 
PE> 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

PE> I've only had it happen the once so far (that I've seen 
PE> 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)

PE> I can't give you the number to call either!  Ain't that 
PE> 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 
DD>> stable connects.

PE> May have been fixed with the new ROMs.  The next 2.5 weeks
PE> will tell.  BFN.  Paul.

After that, see if the owner will allow it to be sent up here for a while,
where I could test it on my "perfect' phone lines.

David
@EOT:

--- Msgedsq/2 3.10