Paul, at 23:09 on Jan 28 1996, you wrote to All ...

PE> Hi folks, I have been given a USR Courier V34+ for trial for 
PE> 1 month.  1 week has passed already, and would like to know 
PE> if anyone has suggestions, which I can try in the course of 
PE> the next 3 weeks.  At this stage, I will not be touching the 
PE> USR Courier with a barge pole.  I had far less problems with
PE> my Spirit Thunder, which I knew for a fact was a load of
PE> rubbish.  At this stage I am looking at getting either a
PE> Netcomm or a Yum Cha V34 modem.

PE> Oh, my Spirit Thunder died in a lightning attack, which is
PE> the reason for the upgrade to V34.  Some of these problems
PE> should be able to be verified by anyone with a USR Courier,
PE> e.g. numbers 1 and 5.  For you to get the others you need
PE> to be called by the same people who are calling me.  I have
PE> sent the people who are getting the problems off to hassle
PE> some other USR Courier owners that I know of.  Note that I
PE> didn't have any of these problems with my Spirit Thunder.
PE> I had a different set of problems with it.



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

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


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

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

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

Could be your line or theirs . . . . No noticable problem here with NetComm 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.

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

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

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

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

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

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

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

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.

Haven't seen this

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.

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

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.

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

David
@EOT:

--- Msgedsq/2 3.10