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 

RB> I wondered why I saw you poke your nose into the USR_Modems Conf.
RB> (It's not like you )

It's not like me to tag the USR_MODEMS echo just to snoop?  How
would you know?

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

RB> The only thing wrong with a USR Courier is that is connects (SOLIDLY, I 
RB> might
RB> Add) at 26400 to most cheap generic Rockwells, instead of 28800.
RB> Most of the better named ones should connect at 28800.

David Begley's is one of these you-beaut flashrom Netcomms.
26400 every single time.  Paul Markham's is a PCMCIA Netcomm
(no further info yet), which was connecting at a large range
of speeds, but since the ROM upgrade has connected twice, both
at 28800.

RB> Things should be better when 33600 is ratified and Rockwell start making 
RB> chips
RB> I suppose, They are the ones with the bad interpretation of V.FC & V.34.
RB> When they make he new chips, they might fix the Aggressive negotiation and
RB> Subsequent fall back garbage.

Then again, if these VERY COMMON Rockwell modems are connecting
fine to other Rockwell modems, that means it is fixable in the
USR.  Certainly the very least USR should be doing is having an
*option* to do Rockwell-style negotiation.

RB> And Oh! the other problem might be that your modem is the Austel Nobbled
RB> Version.  I did not get very good results when testing one of these either.
RB> I am sticking to the Domestic version. Far superior in my tests, and it
RB> does not seem to mind connecting to David Drummonds Austel Courier at full
RB> steam (33600/33600). 

I also have connected with DD at 33600/33600.  You say below that
I am using the Austel Nobbled Version.  I am happy to change ROMs
again.  Tell me the name and location of a decent set of ROMs and
I'll FREQ it.

PE> rubbish.  At this stage I am looking at getting either a
PE> Netcomm or a Yum Cha V34 modem.

RB> The best Rockwell based modem to buy (non Austel, which means you are 
RB> naturally not interested ) is the SupraFaxModem V.34 series (Best 
RB> connectivity, bang for buck and features.

And the best Austel?  And don't say USR.  Of if you do say USR, then
tell me the second best.

RB> With all the troubles you discribe, It must be setup or BAD lines.
RB> It can't all be blamed on the modem.

I think it can.

RB> 99% of connectivity problems are solved with the ATS27=32 or ATS27=48

32 disables LAPM?  I want LAPM.  I might be happy to disable the
detection phase though, since I don't know what that is, so I'll
try ATS27=48.

RB> Plug it back in and do an +++ and ATY11 while on line to a 28800 modem
RB> Give us a dump of ATi6 ATI11 & ATY11. 

Ok, will post later.  Need to stuff around to get +++ to work.

RB> How can you expect the gods to smile on you when they have seen you Bag
RB> USR grossly in the past.

I haven't actually (before I got this loaner).  I used to think
it really was the best.

PE>               Problems with USR Courier V34+
PE>               
PE> Note: Supervisor Date = 1995-07-18 < Austels hack of the July 5 code
PE>       DSP Date        = 1995-07-05

RB> I am using the Domestic 1 Nov 95 code and It will soon be Hacked and 
RB> released
RB> as the Austel Code no Doubt, But you cant wait that long , can you.

What is "Domestic"?  Do you mean US code?  I can't load US code
on my modem apparently.

RB> The 1 Nov code lets you disable the TX level Deviation (letting you lock it 
RB> at 
RB> -10dB, if you want) and that is what the Austel model lacks.

RB> Can you post us your typical Recv/TX level figures, please 

To who?  I'll post the last connect to Dave Hatch's USR...

# 01 Feb 06:53:41.85   Recv/Xmit Level (-dB)    25/15

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

RB> This is how you set the Baud rate on setting up the modem originally.
RB> Start your comms prog up and set the comms prog to the baud rate you desire
RB> then do AT&W and it will then stay at the rate you want.

Yes, that is a workaround.  It is still a bug though.  I have to
rewrite the NVRAM instead of just letting the modem auto-detect
on the "AT" command.

RB> Or are you using it as a fax receiver as well (Bink & BGFax) and
want it to 
RB> change rates for faxing.

No, I don't have that technology.

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

RB> You should get very good 28800 connects to the  Netcomm's at Canon Aust's
RB> BBS in Sydney, I do from Brisbane, Try them.

Which are what sort of Netcomms, so that I can compare with
David Begleys?  Also, there may be a difference as to when
the USR is answering or originating.

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

RB> Yes but if it was granted, then it is the other end doing the requesting.
RB> If it ATI6 says requested then IT is doing the requesting, I believe.
RB> Clear this up with Joe F. in the USR_Modems echo. You should get some 
RB> quick, straight answers. 

The USR reports 0 requested and 0 granted.

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

RB> Is this Rod's, What Chip revision is it.

Yes.  Hopefully he will answer.

PE> 5. AT&F1 sets S56 equal to 16 instead of the default of 0 listed
PE> in the manual.
RB> Are you looking at ATI4 (Defaults) or ATI5 (NVram settings)

ATI4 is not defaults, it is current settings.  I am looking at
current settings after typing in AT&F1.

RB> So, it has to be a faulty modem or one that someone has loaded (or tried to
RB> load another country's SDL into. Have you tried loading a US/Canada 
RB> domestic
RB> SDL into it at some stage (or somone before you got it)

No, the previous person (the owner) thought that it was not
possible to load anything other than the Australian code, and
never attempted to do so.  I thought it was possible, but 
checked with Bill Grimsley first, and he told me it was not
possible, so I never tried either.

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

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

RB> Someone has severely stuffed around with your modem.
RB> Get another one for trial

That's what they said about my Spirit.  Got the whole board
replaced.  It was a bug.  I don't have any other USRs to
trial.  Also, Rod Speed has already gone and proven two of
the faults on other USR's modems.

RB> Do you have the On Disk version of the Manual. Get Bill to send it to you.

No, not yet.

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

RB> Use S27=48 for any modem that hangs up on answering.

Ok, will try it next time the Hayes is online, assuming the new
ROMs haven't fixed it.

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

RB> What is your number. Put the Courier on line and tell me when. 
RB> I will try to connect from here (Far North QLD)
RB> With my lines up here I should get 33600/33600 to you.

The courier will be online for the next 2.5 weeks, and then I
have to make a decision.  My number is 02-436-1785.  BFN.  Paul.
@EOT:

---