This thread/posts have became a bit long so I though I would start
afresh
Excellent idea.
Anyway as an aside from our haggling over who is wrong and who is
right, it may well be both, as it turns out, depending on how the modem
is set-up! I have found out some intersting info.
Sorry, but you haven't been right about much, if anything, so far.
See this [old] URL:
http://www.nwfusion.com/archive/1995/95-04-03isdn-a.html
"When V.42 error control is not used, start and stop bits are sent
with each character. Thus, an eight-bit character would take 10 bits
to transmit. Top-speed V.34 modems use V.42 error control. When V.42
error control is used, no start or stop bits are sent over the line.
The asynchronous bytes are stored until a standard packet size is
reached or a timeout elapses. Then they're wrapped in V.42 - or Link
Access Protocol for Modems - headers and sent synchronously."
"Latency - When keystroking, the modem may wait to see if more
characters are forthcoming before sending or may just have slow
store-and-forward code."
"Overhead - Each block, which may potentially be as small as a single
character of payload, may be surrounded by leading flag, address byte,
command byte, two CRC bytes and trailing flag for big expansion. ...
If the V.42 block size is 256 bytes, you still have six overhead bytes
for each 256 bytes."
A few points:-
It seems my modem is set up without error correction or compression
(from my modem log)
07-07-2004 18:15:28.97 - Error-control off or unknown.
07-07-2004 18:15:28.97 - Data compression off or unknown
Highly unlikely. You snipped out the important data just prior to
these two lines. If the modem was installed properly, you would have
seen responses such as "PROTOCOL: LAP-M" or "COMPRESSION: V.42BIS".
The fact that DUN reports no EC or data compression does not
necessarily mean that these protocols are disabled, instead it means
that the INF file, and therefore the registry, did not contain the
aforementioned responses. If these responses do not appear under this
registry key ...
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Modem\000n\Responses
.... then DUN does not know how to interpret them and flags them as
"unknown".
Here's some useful info:
Understanding Your Modem Log
http://www.modemsite.com/56k/modemlog.asp
That modem utility doesn't seem to work too well for my modem
at the moment (more on that later), as I am fairly sure I am getting
better than 300BPS!!!!!
This looks like the AT&V1 output from a Conexant/Rockwell chipset. The
data are meaningless because DUN has reset them. You need to edit the
Reset parameter at this registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Modem\000n
Change the Reset command from "ATZ<cr>" to just a plain "AT<cr>".
In addition to AT&V1 there are more useful diagnostic commands such as
AT#UG or AT#UD. The output from the latter needs to be decoded.
===========================
HIGHEST RX rate............. 300 BPS
PROTOCOL.................... N/A
COMPRESSION................. N/A
Line QUALITY................ 255
Rx LEVEL.................... 214
Highest Rx State............ 00
Highest TX State............ 00
EQM Sum..................... FFFF
RBS Pattern................. FF
Rate Drop................... FF
Digital Loss................ FFFF
Local Rtrn Count............ 00
Remote Rtrn Count........... 00
V90
OK
==========================
This may well be because the modem was not set up with the
manufacturers .inf file, as you pointed out.
No, it's a problem with nearly every INF file.
See "Prevent Modem Reset":
http://www.modemsite.com/56k/x2-inf.asp
I did some googling on my modem, although I didn't have much
to go on as I think I have binned the box and I don't recall ever
having a manual for it (cannot find it anyway!). All I could find
on the modem itself was 560 DTV (data voice fax), fortunately
I did manage to track it down from just this info.
Nope, wrong chipset, wrong modem type. This is an *external* modem
using an Ambient/Intel/Cirrus Logic chipset. You stated elsewhere that
yours was an *internal*.
Identifying Your Chipset
http://www.modemsite.com/56k/chipset.asp
Who Manufactured My Modem?
http://www.modemsite.com/56k/whomadeit.asp
http://www.modulartech.com (from not sure if direct link will work)
So I have got all the relevant bumpf from there, including I think,
the correct .inf file.
Mine is the V90 so I should be able to upgrade it, see below.
If it's a Conexant chipset, then here are generic Conexant drivers:
http://www.conexant.com/support/md_driverassistance.html
Anyway I will not mess around with it for the moment as I am aware
I will destroy the modem if I screw-up up when updating its flash
memory. (Need to check with ISP too).
I suspect yours is an internal HSF (soft) or HCF (controllerless)
modem. If so, then it will have no flash memory. To prove this beyond
doubt, look for a chip with a part number containing 29xxxxx. No chip
means no flash.
I have the proper .inf file now I think, Mdmcir.inf
I doubt it. This is probably an INF for a Cirrus Logic chipset. Cirrus
Logic became Ambient, and then Ambient was absorbed by Intel.
(there is also a
Serwvcir.inf file too). I am not sure how to 'install' this though,
I was thinking I could just replace the contents of the existing .inf
file (although I forget its name (I am sure you or I mentioned it in this
thread somewhere?)) mdmcomm1.inf mdmcom1.inf??
No. You must uninstall the current modem and then install the new one.
The installation process loads driver files (*.vxd) and rewrites the
registry.
For the moment though I will 'leave well alone' I really don't want
risk losing my internet connection untill I am absolutely sure what
I am doing!! And I would want to research a new modem before
I attempt to 'flash' the modems memory so I can quickly nip down
to the a local computer shop if necessary.
I am not sure how worthwhile the v92 upgrade would be, a faster
connection would be nice but I doubt it would be much faster?
It takes about 22 seconds at the moment (I recently did something
to speed up the logging process).
I suspect you may have done this:
Slow to Logon
http://www.modemsite.com/56k/logon.asp
Here in Australia not many ISPs support V.92. In any case the benefits
are not substantial, especially if you can take advantage of software
compression.
Also I managed to 'silence'
my modem a while back (I forget how and how to restore it)
so I cannot hear how long each bit takes.
Does this help?
Can't Hear Modem - Modem Speaker On or Off
http://www.modemsite.com/56k/speaker.asp
"* Faster connection speeds to the same number (by
remembering the line characteristics from the previous
connection)"
I assume this is the bit where you hear the characteristic screeching
tones? as it tries higher and higher baud rates?
It's not trying higher "baud rates". The modems are sending different
frequencies down the phone line and assessing the line's frequency
response, among other things. You can see the response curve in the
post-call diagnostic report of USR/3Com modems, for example.
See
http://members.cruzio.com/~jeffl/aty11/aty11.htm and
http://groups.google.com/[email protected]&output=gplain
As for the other benefits:-
* Higher upload speeds (Max 44K instead of 33.6)
(don't really do much uploading)
* Apparently higher speed for display of web-pages
(using V.44 compression which is optimised for HTML)
(doubt I would notice the difference, it won't improve badly
designed sites, with their big pictures and fancy graphic etc...)
V.42bis has a typical compression ration for text of 2:1. This is
almost enough to saturate a 11.5 KB/s COM port if the modems are
connected at 5KB/s. V.44 has a claimed compression ratio of 3:1
(IIRC), which would be throttled back to 2:1 by the COM port anyway.
So unless you have a high speed COM port (eg 230400bps), or a soft or
controllerless internal modem, or perhaps a USB modem, then AFAICS you
will see little, if any, performance increase.
I will probably come back on some of the other points later as there
are too many 'unknows' about my connection at the moment.
I suspect I may be using some MPN 4 stuff but its hard to say for
sure untill I can 'interrogate' my modem properly!
No, the default is V.42 LAPM and V.42bis.
Also it can get a little complicated if, for example, you have to
resend packets of data as to what the correct line speed is.
Line speed is perhaps more of a variable than a constant,
depending on the line quality. If you have a good line it will be
more of a constant of course. A bit of a 'black art' really!!
Your post-call diagnostics will tell you the error rates and the
numbers of speedshifts and retrains (see my other post). If the error
rate is high, then you may achieve higher throughput by limiting your
initial connect speed.
Limiting CONNECT speed:
http://www.modemsite.com/56k/x2-linklimit.asp
Here is my favourite site for all things modem:
http://www.modemsite.com/56k/trouble.asp
There may be some useful tests here:
Test Your Modem Speed
http://www.modemsite.com/56k/speedtest.asp
Personally I think the best on-line tests involve transferring ZIP
files to and from your own webspace using FTP, or emailing ZIPs to
yourself. This is because there is less chance for network congestion.
- Franc Zabkar