IS>> makes of modem, thus are setting their BER / line rate selection policy
LE>> implementor. *However* you are not likely to see modems
LE>> which use Rockwell firmware diddling with that sort of
IS> Mmm.  Most of the more 'generic' Rockwell kit doesn't seem to have this 
IS> problem, so much anyway.  Surely the V.42 negotiation period timeout is 
IS> adjustable?

Not with ConfigurACE that I've seen, though I may not have looked right 8-)
ConfigurACE is the same sort of product as the great "Kid's
Painter" (or whatever it was called) cartridge for the VIC-20. This
put a half-dozen UDGs on the screen and let you "paint" a face by
changing the nose, ears, hair and eyes using the f-keys.

BTW, there is no good reason to set the BER/link rate correlation at too
optimistic a value. I would guess that there is no simple ratio used, but
rather a table of thresholds which are used to determine the optimum symbol
rate for the connection. E.g. "97-100% error-free = 3429, 93-97%
error-free = 3200", etc. As such there is NO FIELD TESTING required to
get the best table, simply a little arithmetic.

LE>> So I would not expect to see E-series NetComms deviate from
LE>> Rockwell defaults, but I *would* expect the M-series
IS> Well, I mentioned firstly the M34s, which seem to consistently respond that
IS> way (as Bill mentions, the easiest way around for many people is to

God knows then. There are at least two motherboards for the M34F, and half
a dozen or more publicly available firmware releases. It's easy enough to
hack, why not give it a try ! 8-) The last set of SmartModem firmware I
disassembled was 2.56b or something for the M11F, it took me nearly a week
to do using Turbo C 2.0 (to write a program to byte-swap the ROM image
file), GoldMon (an Amiga 680x0 disassembler/debugger), and K-Seka (an Amiga
assembler). It would take longer now because the new ROMs are twice the
size, though most of the space is probably empty - I've never looked.

IS> than anything else), however the symptoms seem so far to be the same for a 
IS> local Roadstar 33600 job, which I'd imagine to be more an 'E' series type 
IS> of implementation, perhaps - that could be partly due to pilot error 
I haven't peeked inside a Roadster but by all accounts they are Bad News;
I've never heard anyone say he was happy with one. Also note (if it means
anything) the Roadster will be using the 288DPL low-power version of the
datapump, I don't know if there are DSP code differences.

IS> Thanks for that, glad to see you're paying attention :)
The magic of grep.

-- Lewin A.R.W. Edwards [Team OS/2]  Tel 0419320415 * 0412809805 * 0414927056
@EOT:

--- MsgedSQ/2 3.35