>On 22 Jun 1997 11:50:55 GMT, "Andy Taylor"
>>Heres an odd one, before X2 my connection reported correctly the connection
>>i.e 31,200 or 33,600
>>since upgrading my sf to X2 and using the new number it now seems to report
>>the serial speed, i get 115,200bps every time.
>>Anybody now how to get this to reflect the correct and more relevent
>>I am confused
>>Any help would be appreciated.
>I am looking for this also. It is either S15, S33, or S27. I was
Actually, the problem is with Win95, not the modem. See,
Win95 likes to take a perfectly good result code and it tries to
interput it. When Win95 fails to interput this result code, instead
of just showing it to you so that you might be able to get something
from it, it just spews out worthless info telling you your DTE rate.
>getting actual connect speed until I put this string into the registry
>&F1&K0&I0S33=32S15=128S27=64 (recommended by USR)
Hmm, &F1 sets the modem to the factory defaults, that's a good
place to start. &K0 disables data compression, that's sorta a bad
thing, more on this later. &I0 disables software flow control, which
is redundant since this is set by &F1. S33=32 disables the 3429
symbol rate, which can help if you're having problems with v.34, but
since the 3429 symbol rate is never used with X2, this command isn't
doing much. S15=128 disables LAP-M and uses MNP error control
instead, this is the only really important command in the whole
string. S27=64 is reserved according to my manual, dunno what that
does (if anything).
Anyway, as I mentioned, disabling LAP-M is about the only
important thing that USR suggested. It seems that USR X2 modems are
having a few little troubles with LAP-M, not only when it comes to
interoperability, but also when connecting to other USR X2 modems.
Disabling LAP-M may help these problems. Unfortunately, depending on
how poorly USR wrote their drivers, it may also be the reason why
Win95's stupidity is showing through. I heard that USR has an updated
version of their .INF files for their X2 modems, I'd suggest you try
Now, one more thing to note is about disabling compression
with the &K0 string. Normally you want v.42bis compression enabled,
since it will speed up data transfers. Unfortunately, since we're
using MNP error control instead of LAP-M, we're stuck with MNP5
compression instead of v.42bis (while v.42bis over MNP4 error control
is possible, it's not implemented on USR products). MNP5 data
compression can speed up things when you're transfering compressible
data (eg text), but it can also slow things down when you're
transfering data that is not compressible (eg .zip files, .jpg, .gif,
most sound and video formats, etc.), so in this case it's a good idea
to turn off data comrpession. That being said, USR included a nice
little command which will disable MNP5 data compression, but leave
v.42bis on for when it's usuable. The command to do this is &K3,
which is what I'd recommend using instead of &K0.
Quote:>BTW, people have reported connect speeds of 52000 using this string.
The init string has very little to do with your connect rate.
Anthony Hill | My opinions are those of the small