-=> Quoting Wes Newell to Richard Town <=-
 WN> Having lost many a nights sleep when I went to 14.4 with some of the
 WN> early Rockwell chipsets, I'd say the problem is probably in the Zoom.
 WN> Especially if the rom code is prior to 1.56 (I think that was the 1st
 WN> Zoom rom that fixed the negotiation problem)
 
 RT> Here's some log extracts to show.  First with the earlier symmetric
 RT> US Zoom 28k8 max code ver1.100a to a V34+ Courier:
 RT> ----------  Sat 01 Jul 95, FD 2.12.SW
 WN> Much deleted cause it has no meaning to the problem at hand, a
 WN> 14.4Kbps Rockwell chipset modem.
 RT> Why do you think that the "problem is probably in the Zoom"?
 WN> Because I went through at least 5 of the early 14.4's and lost
 WN> probably 100 hours of sleep trying to get the early Rockwell chipsets
 WN> working on my line, which  wasn't very good at all. The modem would
The point is that USR was late into the V32bis arena, preferring to try
and force their proprietary HST at 14k4 instead.  They tried it on with
V.FC, but that was a V42bis glitch if memory serves, after being late there
too preferring to hold on to their proprietary 21k6 and then go to V34
directly.  They, as I've proved, did do it at V34+/V34Plus, and have
definately definately done it in UK code at x2 denying any "foreign" V34
calls at all.
Add to this the decision to stay out of 56k Open Forum, go to fax
Class2.0 before ratification and not offer Class2, refuse to
recognise extended V42 commands...
... their lovelyness goes on and on
 WN> work fine from other locations, but I could barely hold a 4800bps
 WN> connect here. This was rom code 1.00 I think. Yes they were very early
 WN> v.32bis modems. They sucked to put it mildly. And it wasn't just Zoom.
There was a ver2.00 ROM update available for earlier Zoom
V32bis models but dunno what stock situation is now
rgdZ
Richard
--- FMail/386 1.02
---------------