Modem connection speed

N

Noozer

When I asked BT about my bad line they always asked how many
devices were connected to it, I suppose the less things you have connected
the less chance you have of one of them being faulty? Also I think a battery
at the exchange provides power for the phone(s)? maybe there is a limit as
to
how many devices you can have connected?


Definately
 
F

Franc Zabkar

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
 
H

half_pint

Zotin Khuma said:
~38k
when in
our

Just remembered something else!

I have been informed that if there are several communications devices
connected sharing the same line (eg. PC, phone, fax) then by
disconnecting all others when your PC's modem is being used, this can
apparently improve connection speeds.

Try it!

I don't know the exact reason why this should work, but I'm guessing
it may be something to do with the other devices having to process
(and ignore) the noise generated by the modem signal.

Living in a remote corner of India, I thought almost everyone in the
more advanced countries would be using at least >128Kb/s cable/DSL.[/QUOTE]

Well I live in the UK and most people still use dial-up 56k modems
although broadband is available if you are willing to pay more
( the prices are set by British Telecom (BT) which is a virtual monopoly so
basically they can charge what they like, there are some cable
companies but they are just as expensive)


Here's my 2 cents worth from an end-user's POV.

My phone company is also my ISP and I happen to live less than 200
metres from their building, though the actual line length is probably
about twice that. I've used several different modems and never
bothered to use anything other than the generic Windows drivers. Max
connection speed setting is limited to 115K, and I often manage to
connect at that speed, though it's sometimes at 33k or even lower.

The connecting speed doesn't seem to greatly determine the actual
download speed. I may connect at 115k and still have to wait for ages
for web pages to open, or connect at 33k another time and have the
same website move at relatively blazing speeds.

File download speeds as shown by IE or Download Accelerator vary from
less than 0.1 kiloBYTES/s to about 4.5kB/s on a very good day.

I usually can get about 4.4 is the site is not busy, you might as well have
56k dial-up as your max speed is no better than mine. no real point if you
are paing more for ISDN and getting a dial-up speed. (Actually I am unsure
what you have and you may have dial-up, your "connect at 115k maybe
misleaeding you (computer to modem speed, not modem to modem speed?)
These
are sustained speeds, not burst speeds which sometimes shoot up to
20kB/s at the start of a file download. The primarily cause of the
large variation in speed does not seem to be the state of my phone
line (though this must certainly be a factor), but rather from the
server since friends in other parts of the town usually experience
corresponding variations at the same time.

Well I expect your line is perfect and you are hitting the local
internet 'rush-hour' where everyone wants a slice of your
ISP's available bandwith, obviously it had not bought
enough bandwith to cope at peak times. (I had an ISP
whhich did this and it was very slow at peak times).
Another factor that took some time to track down was one particular
computer's PSU. It caused connection problems, random disconnections,
etc., but ONLY when my phone line was unusually noisy. Replacing the
PSU cured it completely. It never posed any problem in off-line
computing.

Your PSU may have been interferring with with your phone line,
it might have been creating a lot of electrical 'noise' which could
affect your line, especially if it had some poor connections etc..
BTW, one of the "advantages" of living in a less developed region is
that the phone company doesn't seem to mind if I repair or tweak my
own line. Twice in the past 10 years or so, I've bought phone cable
from a store and completely replaced the overhead lines from their
junction box.

I doubt BT has touched my line in the 30 years it has been in exixtance!!!
Personally I doubt your line is the problem, the best way to test it is
to pick up the phone and listen. If they used the correct cable in the
first place I cannot see why you would be getting a problem.
I thought I had a bad line and it turned out to be moisture
in a socket, all the while I was looking at the cable around my house
and thinking "I bet thats all corroded inside!!"


Fibre-optic has not completely replaced metal here.

Nor here, I expect BT will be using the same copper
wires for the next 20 years or so.
 
H

half_pint

Franc Zabkar said:
Excellent idea.


Sorry, but you haven't been right about much, if anything, so far.

In your opinion.
You don't now how my modem is configured, so basically you are clutching at
straws. You are talking about error correction and protocols when you don't
know how my modem or the OP's is configured.
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."


Not relevant unless you know the modens config.
Highly unlikely. You snipped out the important data just prior to
these two lines.

Wrong I snipped out nothing important, see the log at the end of file.
If the modem was installed properly, you would have
seen responses such as "PROTOCOL: LAP-M" or "COMPRESSION: V.42BIS".

Only if it was set up a particular fashion.My modem works well
enough it has connected me to the internet for
several years. To suggest it is not installed properly is a bit of
a stretch.
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\Respon
ses

... then DUN does not know how to interpret them and flags them as
"unknown".

Well there seems to a load of stuff in there.

Connect 28000 = 02 00 80 70 00 00 00 00 00 00
( for example)
OR
PROTOCOL LAPM = 00 02 00 00 00 00 00 00 00 00
Here's some useful info:

Understanding Your Modem Log
http://www.modemsite.com/56k/modemlog.asp


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.


No, it's a problem with nearly every INF file.

See "Prevent Modem Reset":
http://www.modemsite.com/56k/x2-inf.asp



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*.

If I did do that (I don't recall) I did it in error, its the correct modem
alright.
I am fairly sure of that, (maybe a different case), they only do a few
modems.

Identifying Your Chipset
http://www.modemsite.com/56k/chipset.asp

Who Manufactured My Modem?
http://www.modemsite.com/56k/whomadeit.asp


If it's a Conexant chipset, then here are generic Conexant drivers:
http://www.conexant.com/support/md_driverassistance.html


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 doubt it. This is probably an INF for a Cirrus Logic chipset. Cirrus
Logic became Ambient, and then Ambient was absorbed by Intel.

No its the right one. Mine is an old modem.
Definately the right one.
No. You must uninstall the current modem and then install the new one.
The installation process loads driver files (*.vxd) and rewrites the
registry.

Can't I have several modems?
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.


Does this help?

Can't Hear Modem - Modem Speaker On or Off
http://www.modemsite.com/56k/speaker.asp


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.

Well basically the same thing, finding the best baud rate to use
"trying higher baud rates"
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

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.


No, the default is V.42 LAPM and V.42bis.

Whatever. The default doen't matter too much, what matters is how the modem
is configured. Which is what I am trying to find out.
Your post-call diagnostics will tell you the error rates and the
numbers of speedshifts and retrains (see my other post).

Which one? the reason i am doing this is because I cannot
see such data in the first place!!
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


Modem log.

07-01-2004 21:45:26.89 - Recv: ATE0V1<cr>
07-01-2004 21:45:26.89 - Recv: <cr><lf>OK<cr><lf>
07-01-2004 21:45:26.89 - Interpreted response: Ok
07-01-2004 21:45:26.89 - Send: ATX4<cr>
07-01-2004 21:45:26.89 - Recv: <cr><lf>OK<cr><lf>
07-01-2004 21:45:26.89 - Interpreted response: Ok
07-01-2004 21:45:26.90 - Dialing.
07-01-2004 21:45:26.90 - Send: ATDT###########<cr>
07-01-2004 21:45:48.27 - Recv: <cr>
07-01-2004 21:45:48.27 - Interpreted response: Informative
07-01-2004 21:45:48.27 - Recv: <lf>
07-01-2004 21:45:48.27 - Interpreted response: Informative
07-01-2004 21:45:48.28 - Recv: CONNECT 57600
07-01-2004 21:45:48.28 - Interpreted response: Connect
07-01-2004 21:45:48.28 - Connection established at 57600bps.
07-01-2004 21:45:48.28 - Error-control off or unknown.
07-01-2004 21:45:48.28 - Data compression off or unknown.
07-01-2004 22:12:16.92 - Hanging up the modem.
07-01-2004 22:12:16.92 - Hardware hangup by lowering DTR.
07-01-2004 22:12:17.68 - Recv: <cr><lf>NO CARRIER<cr><lf>
07-01-2004 22:12:17.68 - Interpreted response: No Carrier
07-01-2004 22:12:17.68 - Send: ATH<cr>
07-01-2004 22:12:17.68 - Recv: <cr><lf>OK<cr><lf>
07-01-2004 22:12:17.68 - Interpreted response: Ok
07-01-2004 22:12:17.68 - 57600,N,8,1
07-01-2004 22:12:17.69 - Session Statistics:
07-01-2004 22:12:17.69 - Reads : 215484 bytes
07-01-2004 22:12:17.69 - Writes: 25019 bytes
 
F

Franc Zabkar

In your opinion.

Usenet is full of opinions and disinformation. That's why I support my
statements with authoritative references wherever possible. Even so,
I'm prepared to be proven wrong. Show me your data.
You don't now how my modem is configured, so basically you are clutching at
straws. You are talking about error correction and protocols when you don't
know how my modem or the OP's is configured.

Until a few days ago you hadn't even heard of error correction and
data compression, yet now you are offering opinions on same.
Wrong I snipped out nothing important, see the log at the end of file.

The log shows that you do not understand how to properly configure a
modem.
If I did do that (I don't recall) I did it in error, its the correct modem
alright.

You *did* do that. It's in the Google archives. In any case, unless
the Ambient AT command documentation is incorrect, the AT&V1 results
you posted are *not* those of an Ambient modem. Rather, they look like
Conexant/Rockwell data. In fact the data are very similar to that
produced by my own Rockwell modem, after it has been reset.

at&v1
TERMINATION REASON.......... NONE
LAST TX rate................ N/A
HIGHEST TX rate............. 300 BPS
LAST RX rate................ N/A
HIGHEST RX rate............. 300 BPS
PROTOCOL.................... N/A
COMPRESSION................. N/A
Line QUALITY................ 255
Rx LEVEL.................... 215
Highest Rx State............ 00
Highest TX State............ 00
EQM Sum..................... FFFF
RBS Pattern................. FF
Rate Drop................... FF
Digital Loss................ None
Local Rtrn Count............ 00
Remote Rtrn Count........... 00
Flex fail

OK
I am fairly sure of that, (maybe a different case), they only do a few
modems.

Follow the next two links and you will find out exactly which modem(s)
you have. In the meantime go to Control Panel -> Diagnostics -> More
Info and capture the ATIn responses. ATI6 and ATI3 identify
Rockwell/Conexant chipsets and firmware revisions.
No its the right one. Mine is an old modem.
Definately the right one.

External modems will probably still "work" with the "wrong" INF file,
they just may not work optimally.
Can't I have several modems?

Yes, you can. But you can't just overwrite an INF file and expect it
to change anything. An INF file is only used during the installation
process - it can be deleted after the modem has been installed. DUN
never looks at it again.
Well basically the same thing, finding the best baud rate to use
"trying higher baud rates"

You are mangling the terminology. Do a Google search on "baud rate" to
see what the term really means.
Whatever. The default doen't matter too much, what matters is how the modem
is configured. Which is what I am trying to find out.

There is nothing in your modemlog to say that the modem is configured
with anything other than default parameters. Post the full modemlog so
we can see the init strings.
Which one? the reason i am doing this is because I cannot
see such data in the first place!!

Follow the links I gave you. Once again, DUN is resetting your modem's
diagnostic data. You need to edit the Reset parameter in your
registry. Try the AT&V1, AT&V2, AT#UG, AT#UD, ATI6, ATI11, ATY11
diagnostic commands. One or more should apply to your modem, the
others will return an ERROR.
Modem log.

There are some missing lines here. They show the name of your modem's
INF file, and also the init strings.
07-01-2004 21:45:26.89 - Recv: ATE0V1<cr>
07-01-2004 21:45:26.89 - Recv: <cr><lf>OK<cr><lf>
07-01-2004 21:45:26.89 - Interpreted response: Ok
07-01-2004 21:45:26.89 - Send: ATX4<cr>
07-01-2004 21:45:26.89 - Recv: <cr><lf>OK<cr><lf>
07-01-2004 21:45:26.89 - Interpreted response: Ok
07-01-2004 21:45:26.90 - Dialing.
07-01-2004 21:45:26.90 - Send: ATDT###########<cr>
07-01-2004 21:45:48.27 - Recv: <cr>
07-01-2004 21:45:48.27 - Interpreted response: Informative
07-01-2004 21:45:48.27 - Recv: <lf>
07-01-2004 21:45:48.27 - Interpreted response: Informative
07-01-2004 21:45:48.28 - Recv: CONNECT 57600

Your modem is configured to report the DTE rate rather than the DCE
rate. This information is basically useless because it tells you
nothing about the speed of your connection. Worse still, setting the
DTE rate to such a low value limits your transfer rate to 5.76KB/s.
This means that you will never realise the full benefits of hardware
compression. I don't know where you got your claimed throughput
figures of 6.2KB/s, 35KB/s, and 25.4KB/s, unless you have accidentally
enabled software compression, assuming your ISP supports this feature.
Or were those figures achieved with another modem?
07-01-2004 21:45:48.28 - Interpreted response: Connect
07-01-2004 21:45:48.28 - Connection established at 57600bps.
07-01-2004 21:45:48.28 - Error-control off or unknown.
07-01-2004 21:45:48.28 - Data compression off or unknown.

If you have a Rockwell/Conexant chipset, add S95=45 to DUN's Extra
Settings. This will enable CONNECT, CARRIER, PROTOCOL, and COMPRESSION
reports.

And set the port rate to 115200bps.


- Franc Zabkar
 
H

half_pint

Franc Zabkar said:
Usenet is full of opinions and disinformation. That's why I support my
statements with authoritative references wherever possible. Even so,
I'm prepared to be proven wrong. Show me your data.


Until a few days ago you hadn't even heard of error correction and
data compression, yet now you are offering opinions on same.

No, a few days ago you made that assumption, along with several other
assumptions which were incorrect.
The log shows that you do not understand how to properly configure a
modem.

No it doesn't all it shows it what was written to it.
Anyway I didnt configure my modem as it happens it was preconfigured.

You *did* do that. It's in the Google archives.
Which you conviently have 'lost'?

In any case, unless
the Ambient AT command documentation is incorrect, the AT&V1 results
you posted are *not* those of an Ambient modem. Rather, they look like
Conexant/Rockwell data. In fact the data are very similar to that
produced by my own Rockwell modem, after it has been reset.

at&v1
TERMINATION REASON.......... NONE
LAST TX rate................ N/A
HIGHEST TX rate............. 300 BPS
LAST RX rate................ N/A
HIGHEST RX rate............. 300 BPS
PROTOCOL.................... N/A
COMPRESSION................. N/A
Line QUALITY................ 255
Rx LEVEL.................... 215
Highest Rx State............ 00
Highest TX State............ 00
EQM Sum..................... FFFF
RBS Pattern................. FF
Rate Drop................... FF
Digital Loss................ None
Local Rtrn Count............ 00
Remote Rtrn Count........... 00
Flex fail

OK


Follow the next two links and you will find out exactly which modem(s)
you have. In the meantime go to Control Panel -> Diagnostics -> More
Info and capture the ATIn responses. ATI6 and ATI3 identify
Rockwell/Conexant chipsets and firmware revisions.


I know which modem I have thank you very much, I dont fancy a wild goose cha
se.
External modems will probably still "work" with the "wrong" INF file,
they just may not work optimally.


Modems will work most of the time as I have found, I have
configured my modem as several different types and it still works
(33k 56k flex) (it runs 6.2 KB at 33k).
The basic stuff will work, the 'fancy' unnecessary stuff might not, but
who cares?
Yes, you can. But you can't just overwrite an INF file and expect it
to change anything. An INF file is only used during the installation
process - it can be deleted after the modem has been installed. DUN
never looks at it again.

Well I have 3 modems set up alreaaaady anyway.
You are mangling the terminology. Do a Google search on "baud rate" to
see what the term really means.


I know what it means, do a google search on 'intelligence'.

There is nothing in your modemlog to say that the modem is configured
with anything other than default parameters. Post the full modemlog so
we can see the init strings.

I posted it all, anymore would just be repeations of the same info.
Follow the links I gave you. Once again, DUN is resetting your modem's
diagnostic data. You need to edit the Reset parameter in your
registry. Try the AT&V1, AT&V2, AT#UG, AT#UD, ATI6, ATI11, ATY11
diagnostic commands. One or more should apply to your modem, the
others will return an ERROR.

I tried them all and they dont produce anything useful.
There are some missing lines here. They show the name of your modem's
INF file, and also the init strings.

No your're wrong there.
Your modem is configured to report the DTE rate rather than the DCE
rate. This information is basically useless because it tells you
nothing about the speed of your connection. Worse still, setting the
DTE rate to such a low value limits your transfer rate to 5.76KB/s.
This means that you will never realise the full benefits of hardware
compression. I don't know where you got your claimed throughput
figures of 6.2KB/s, 35KB/s, and 25.4KB/s, unless you have accidentally
enabled software compression, assuming your ISP supports this feature.
Or were those figures achieved with another modem?

No obviously not, maybe you do not understand how these figures
were calculated? Anyway I am receiving compressed data in the first
place, it wont compress any futher.
If you have a Rockwell/Conexant chipset, add S95=45 to DUN's Extra
Settings. This will enable CONNECT, CARRIER, PROTOCOL, and COMPRESSION
reports.

And set the port rate to 115200bps.

I set it to that ages ago.
 
F

Franc Zabkar

.... a whole lotta ignorant drivel.

It's clear that you're too stupid and too arrogant to take on board
any new information. You can't comprehend simple arithmetic, you can't
follow instructions, you don't even know what kind or how many modems
you have. BTW, "internal" means "inside" the box, "external" is
"outside".

Here are some thoughts to ponder as you grow up and prepare to enter
the real world.

"Take the attitude of a student. Never be too big to ask questions.
Never know too much to learn something new."

- Og Mandino (1923- )

"A man should never be ashamed to own he has been in the wrong, which
is but saying, in other words, that he is wiser today than he was
yesterday."

- Alexander Pope (1688-1744)

<your ignorant drivel snipped>


- Franc Zabkar
 
H

half_pint

Franc Zabkar said:
... a whole lotta ignorant drivel.

It's clear that you're too stupid and too arrogant to take on board
any new information. You can't comprehend simple arithmetic, you can't
follow instructions, you don't even know what kind or how many modems
you have. BTW, "internal" means "inside" the box, "external" is
"outside".

Here are some thoughts to ponder as you grow up and prepare to enter
the real world.

"Take the attitude of a student. Never be too big to ask questions.
Never know too much to learn something new."

- Og Mandino (1923- )

"A man should never be ashamed to own he has been in the wrong, which
is but saying, in other words, that he is wiser today than he was
yesterday."

- Alexander Pope (1688-1744)

<your ignorant drivel snipped>


And here is one for you

"Try not to be a sore loser" - Anon (10/07/2004 10:50PM GMT.).
 
F

Franc Zabkar

And here is one for you

"Try not to be a sore loser" - Anon (10/07/2004 10:50PM GMT.).

Unlike you, I don't see Usenet as an ego trip. In fact I don't have
any problem admitting to error, even when the other party is someone I
detest.

To remove any such doubt, see this post ...

http://groups.google.com/[email protected]&output=gplain

.... in which I state ...

"I may not like you [an antagonist who is prone to profanity and
racial slurs], but that does not prevent me from acknowledging
you when you are right. I have no ego to protect, and I in no way feel
diminished when I confess my ignorance, especially if I can learn
something in the process."

BTW, the difference between ignorance and stupidity is that the former
can be remedied through education. The latter requires surgery.


- Franc Zabkar
 
H

half_pint

Franc Zabkar said:
And here is one for you

"Try not to be a sore loser" - Anon (10/07/2004 10:50PM GMT.).

Unlike you, I don't see Usenet as an ego trip. In fact I don't have
any problem admitting to error, even when the other party is someone I
detest.

To remove any such doubt, see this post ...

http://groups.google.com/[email protected]&output=gplain

... in which I state ...

"I may not like you [an antagonist who is prone to profanity and
racial slurs], but that does not prevent me from acknowledging
you when you are right. I have no ego to protect, and I in no way feel
diminished when I confess my ignorance, especially if I can learn
something in the process."

BTW, the difference between ignorance and stupidity is that the former
can be remedied through education. The latter requires surgery.


No lets face it, you said I was wrong, but I wasn't Stop and start bits
are sent.

Good luck with the surgery.
 
F

Franc Zabkar

No lets face it, you said I was wrong, but I wasn't Stop and start bits
are sent.

Good luck with the surgery.

You have the intelligence of a gnat. What is it about the following
that you don't understand?

http://www.nwfusion.com/archive/1995/95-04-03isdn-a.html

"Top-speed V.34 modems use V.42 error control. When V.42 error control
is used [which is *all* the time unless something is seriously wrong],
NO START OR STOP BITS ARE SENT over the line."


- Franc Zabkar
 
H

half_pint

Franc Zabkar said:
No lets face it, you said I was wrong, but I wasn't Stop and start bits
are sent.

Good luck with the surgery.

You have the intelligence of a gnat. What is it about the following
that you don't understand?

http://www.nwfusion.com/archive/1995/95-04-03isdn-a.html

"Top-speed V.34 modems use V.42 error control. When V.42 error control
is used [which is *all* the time unless something is seriously wrong],
NO START OR STOP BITS ARE SENT over the line."


They are still sent from the DTE to the DCE though. At least according
to the setting in IE, microsoft could have made an error there of course,
but if they did then you really have to take all their other settings with
a pinch of salt.
So if I am wrong then I am in good company (well maybe not if it is
microsoft).

You are also making assumptions about the protocol used, but that
is a minor point given the above

Do you know mine and the OP's settings?
I can't find out what mine are at the monent anyhow.
 
F

Franc Zabkar

What is it about the following
that you don't understand?

http://www.nwfusion.com/archive/1995/95-04-03isdn-a.html

"Top-speed V.34 modems use V.42 error control. When V.42 error control
is used [which is *all* the time unless something is seriously wrong],
NO START OR STOP BITS ARE SENT over the line."


They are still sent from the DTE to the DCE though.

Of course they are, at least for external serial (non-USB) modems. But
these extra bits have no impact upon the modem's connect speed, nor do
they affect the throughput for incompressible data, if the port rate
has been configured correctly. And therein lies the reason for your
fixation regarding this issue. If your more recent posts are any
guide, then it is clear that you have been restricting yourself to a
DTE rate of only 57600bps since the first day you installed your
modem. This would have limited you to a max throughput of only
5.76kB/s, which would mean that your COM port is throttling your
modem's performance. At 5.76kB/s and 8.20 bits/byte (according to my
testing), this amounts to only 47232bps. OTOH, a COM port that is
correctly configured for 115200bps would be subject to no such
limitations, even at a theoretical maximum DCE rate of 56000bps. In
any case, there is nothing to prevent a modem from *connecting* at a
DCE rate higher than its DTE rate.

This post demonstrates why it is silly to limit your port rate to
57600bps as you have done:
http://groups.google.com/groups?sel...nsc04-news.ops.worldnet.att.net&output=gplain

At least according
to the setting in IE,

Your browser has absolutely no control over your modem settings. You
can access these via DUN or via Control Panel -> Modems or via Device
Manager.
microsoft could have made an error there of course,

No errors, just a very basic, no frills, generic, chipset based INF
file.
but if they did then you really have to take all their other settings with
a pinch of salt.
So if I am wrong then I am in good company (well maybe not if it is
microsoft).

You are also making assumptions about the protocol used, but that
is a minor point given the above

No. Your modemlog shows that you have added nothing to your modem's
Extra Settings. You have also stated that your EC and compression
check boxes were greyed out. This proves that your modem is operating
with its default settings. These defaults include V.90, V.42, and
V.42bis.
Do you know mine and the OP's settings?

I know enough about your settings to know that they are far from
optimal. At the very least you should increase your port rate to
115200bps, for performance reasons. You would also benefit from
knowing your actual connect speed, eg 44000bps, rather than having DUN
tell you what you already know, ie that you port rate is 57600bps.
I can't find out what mine are at the monent anyhow.

I've shown you how, but you appear to be unable and unwilling to
follow instructions.

Follow my links to modemsite.com and learn something about your modem,
as I have done. You could also post your questions to comp.dcom.modems
where there are a lot more knowledgeable people than you or I.


- Franc Zabkar
 
H

half_pint

Franc Zabkar said:
What is it about the following
that you don't understand?

http://www.nwfusion.com/archive/1995/95-04-03isdn-a.html

"Top-speed V.34 modems use V.42 error control. When V.42 error control
is used [which is *all* the time unless something is seriously wrong],
NO START OR STOP BITS ARE SENT over the line."


They are still sent from the DTE to the DCE though.

Of course they are, at least for external serial (non-USB) modems. But
these extra bits have no impact upon the modem's connect speed, nor do
they affect the throughput for incompressible data, if the port rate
has been configured correctly. And therein lies the reason for your
fixation regarding this issue. If your more recent posts are any
guide, then it is clear that you have been restricting yourself to a
DTE rate of only 57600bps since the first day you installed your
modem.

Wrong firstly I didn't install my modem it was pre installed.
Secondly there is no ability to set the DTE setting, I can set the
modem to run at its correct rated speed 57600bps of course.

Actually I may well be wrong about the above as I have found
the setting for comm1, my modem port and it was actually
set to 9600. (control panel - system - devivce manager).
Not that that low setting appeared to throttle my modem
which makes most of the folling bumf irrelevant.

Do you recommend trying to run modems at twice their rated speeds?
This would have limited you to a max throughput of only
5.76kB/s, which would mean that your COM port is throttling your
modem's performance. At 5.76kB/s and 8.20 bits/byte (according to my
testing), this amounts to only 47232bps. OTOH, a COM port that is
correctly configured for 115200bps would be subject to no such
limitations, even at a theoretical maximum DCE rate of 56000bps. In
any case, there is nothing to prevent a modem from *connecting* at a
DCE rate higher than its DTE rate.

This post demonstrates why it is silly to limit your port rate to
57600bps as you have done:

Those were are modem settings.

http://groups.google.com/groups?sel...nsc04-news.ops.worldnet.att.net&output=gplain

Your browser has absolutely no control over your modem settings.

Internet options etc....
You
can access these via DUN or via Control Panel -> Modems or via Device
Manager.


No errors, just a very basic, no frills, generic, chipset based INF
file.


No. Your modemlog shows that you have added nothing to your modem's
Extra Settings. You have also stated that your EC and compression
check boxes were greyed out. This proves that your modem is operating
with its default settings. These defaults include V.90, V.42, and
V.42bis.

No all it proves it that they are blanked out.
I know enough about your settings to know that they are far from
optimal. At the very least you should increase your port rate to
115200bps, for performance reasons.

My modem is 56k I have increased my comm1 port setting to 115200
however I dont think it really cares what you set it to.
You would also benefit from
knowing your actual connect speed, eg 44000bps, rather than having DUN
tell you what you already know, ie that you port rate is 57600bps.


I've shown you how, but you appear to be unable and unwilling to
follow instructions.

Nobody tell me what to do, not unless you are paying a decent hourly rate.
You instructuions failed anyhow.
Follow my links to modemsite.com and learn something about your modem,
as I have done.

I dont take orders.
 
H

half_pint

No. Your modemlog shows that you have added nothing to your modem's
Extra Settings. You have also stated that your EC and compression
check boxes were greyed out. This proves that your modem is operating
with its default settings. These defaults include V.90, V.42, and
V.42bis.

I actually have a disc which was supplied with my computer, which has some
sort of modem upgrade on it (v90 upgrade) however it is not a very good
disc (scratches or dirt) and I have great difficulty reading it.

I have however managed to recover some of the data off it (about 1/3 so far)
(sometimes my computer wont read it at all) anyway



=================
\N Error Correction Operating Mode

Parameter: \N0: Standard operation (non error-corrected, buffered data).
\N1: Direct operation (non error-corrected, data not buffered).
\N2: Reliable operation (MNP). If the modem fails to negotiate a
reliable connection it will drop the call.
\N3: Auto-Reliable operation (V.42 or MNP). If the modem fails to negotiate
a reliable connection it will adopt a standard connection as fallback.
\N4: Enable MNP error correction only.
\N5: Enable LAP-M error correction only.

Default: \N3

Purpose: To specify which error correction negotiation will occur after
carrier is established.
===============

So it is not too clear what is happening as N0 is standard and N3 is
default, i suspect N3
but as I cannot get meaningful data from my modem I canot be 100%.

Actually I did manage to install it (or something), I selected the
american english (as opposed to english english) instalation and
it went through and installed something called supervoice.
When I tried the english version I got 'cannot open file' errors.

However I don't think it installed the 'upgrade', but I managed
to copy off the the files in upgrade\external which is what I want
I think. When I try to get upgrade\internal it tends to lock my computer
up but I should not need anything in there anyway.
There is a setup.bat and a v90wiz.exe in the external folder so hopefully
I have enough files copied off to do it.

Anyway I will try the upgrade later. If I cannot get back on line
(wouldn't that be nice eh?) you will know why and obviously
be delighted!!!

Mind up even if it does install I doubt I will notice any difference
whatsoever. I can currently down load about 20megs an hour
on a good day (of compressed data and i doubt I will see any
improvement on that!
 
H

half_pint

half_pint said:
I actually have a disc which was supplied with my computer, which has some
sort of modem upgrade on it (v90 upgrade) however it is not a very good
disc (scratches or dirt) and I have great difficulty reading it.

I have however managed to recover some of the data off it (about 1/3 so far)
(sometimes my computer wont read it at all) anyway



=================
\N Error Correction Operating Mode

Parameter: \N0: Standard operation (non error-corrected, buffered data).
\N1: Direct operation (non error-corrected, data not buffered).
\N2: Reliable operation (MNP). If the modem fails to negotiate a
reliable connection it will drop the call.
\N3: Auto-Reliable operation (V.42 or MNP). If the modem fails to negotiate
a reliable connection it will adopt a standard connection as fallback.
\N4: Enable MNP error correction only.
\N5: Enable LAP-M error correction only.

Default: \N3

Purpose: To specify which error correction negotiation will occur after
carrier is established.
===============

So it is not too clear what is happening as N0 is standard and N3 is
default, i suspect N3
but as I cannot get meaningful data from my modem I canot be 100%.

Actually I did manage to install it (or something), I selected the
american english (as opposed to english english) instalation and
it went through and installed something called supervoice.
When I tried the english version I got 'cannot open file' errors.

However I don't think it installed the 'upgrade', but I managed
to copy off the the files in upgrade\external which is what I want
I think. When I try to get upgrade\internal it tends to lock my computer
up but I should not need anything in there anyway.
There is a setup.bat and a v90wiz.exe in the external folder so hopefully
I have enough files copied off to do it.

Anyway I will try the upgrade later. If I cannot get back on line
(wouldn't that be nice eh?) you will know why and obviously
be delighted!!!

Tried that but it doesn't recognise the modem. Maybe the modem
doesn't need it.
 
F

Franc Zabkar

Franc Zabkar said:
What is it about the following
that you don't understand?

http://www.nwfusion.com/archive/1995/95-04-03isdn-a.html

"Top-speed V.34 modems use V.42 error control. When V.42 error control
is used [which is *all* the time unless something is seriously wrong],
NO START OR STOP BITS ARE SENT over the line."


They are still sent from the DTE to the DCE though.

Of course they are, at least for external serial (non-USB) modems. But
these extra bits have no impact upon the modem's connect speed, nor do
they affect the throughput for incompressible data, if the port rate
has been configured correctly. And therein lies the reason for your
fixation regarding this issue. If your more recent posts are any
guide, then it is clear that you have been restricting yourself to a
DTE rate of only 57600bps since the first day you installed your
modem.

Wrong firstly I didn't install my modem it was pre installed.

Then the person who installed it is just as ignorant as yourself.
Secondly there is no ability to set the DTE setting,

Millions of people have achieved this impossible task. With a little
knowledge and effort you can too.
I can set the
modem to run at its correct rated speed 57600bps of course.

The max "rated" DCE speed of a 56K modem is only 56000bps. OTOH, the
maximum rated DTE speed of hardware modems is at least 115200bps, and
can be as high as 230400bps. Soft modems can do even better. My own
hardware modem will report CONNECT 230400 when I configure it to
report the DTE speed, and it will have a throughput to match (for
highly compressible data). Yours will report CONNECT 115200 if you do
nothing more than select a port rate of 115200bps. Just look in the
INF file (assuming you have the correct one), or check the responses
at this registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Modem\000n\Responses

But please, whatever you do, DON'T do the following. Don't go to My
Computer -> Dial-Up Networking -> don't right click your ISP -> don't
select Properties -> Configure -> General -> Maximum speed. Instead,
just keep farting around with COM port Properties in Device Manager.
Actually I may well be wrong about the above as I have found
the setting for comm1, my modem port and it was actually
set to 9600. (control panel - system - devivce manager).
Not that that low setting appeared to throttle my modem
which makes most of the folling bumf irrelevant.

What this proves is that you have no idea what you are doing or what
you are talking about. A COM port is a COM port, it is not a modem.
For example, I have one COM port to which I can attach any of four
serial devices via a switchbox. One is an external modem configured
for 115200bps, another is an old digital camera, a third is a DCC
connection to another PC, and the fourth is a Casio organizer running
at 9600bps. In each case it is not Device Manager that determines the
port speed, rather it is set by the application that takes control of
the COM port. All Device Manager does is to set some initial default
value.
Do you recommend trying to run modems at twice their rated speeds?

You can't run a modem at twice its "rated speed", so the question is
pointless. Overclocking is for motherboards, not modems.
Those were are modem settings.

No, as I've explained to you elsewhere, you set up the COM port, and
the modem "autobauds" to these settings. So in effect you are
configuring the modem as a *consequence* of configuring the port. BTW,
I'm talking about configuring the COM port in the Modem Properties of
the DUN connectoid, not in Device Manager.

OK, I'll grant you that one, but strictly speaking it isn't IE that
modifies your connection parameters, it's Dial-Up Networking. IE
merely delegates the job to a Control Panel applet (Internet Options),
which in turn delegates it to DUN. A more direct route would be to go
to My Computer -> Dial-Up Networking. You can also access the Control
Panel applet by going to Start -> Run and typing "control
inetcpl.cpl".

The flow is something like this:

IE -> Control Panel -> Internet Options -> inetcpl.cpl -> DUN -> Modem
Properties

If you delete or rename the inetcpl.cpl file, then the only way to get
to Modem Properties is via DUN directly.
No all it proves it that they are blanked out.

A device will operate at its default power-on settings unless
configured otherwise. That is the meaning of the word "default". Now,
as the configuration is performed by DUN, and as the modemlog is a
record of commands issued by DUN, an absence of configuration commands
proves that there was no change to the default settings. But whatever
you do, please don't do *anything* that could possibly prove you are
wrong. Please don't capture a post-call diagnostic report, please
don't post the missing lines of your modemlog, and please don't add
any commands to your Extra Settings that could possibly damage your
fragile ego. And above all, please don't go to Control Panel -> Modems
-> Diagnostics -> More Info in case we find out what modem you really
have.
My modem is 56k I have increased my comm1 port setting to 115200

Irrelevant if you have done it from Device Manager.
however I dont think it really cares what you set it to.

You will double your throughput for compressible files, unless
software compression is enabled. If your modem connects at 48000bps or
better, and if it can maintain this speed, then you should see a
slight improvement in throughput for incompressible files as well.
Nobody tell me what to do, not unless you are paying a decent hourly rate.

Someone who is unable to follow simple instructions is unemployable.
You instructuions failed anyhow.

Tell Richard Gamberg, author of modemsite.com. Most of the
instructions are his, not mine. Maybe he has more patience than I.
I dont take orders.

Not yet, but if you ever enter the workforce that's all you'll be fit
for. Would you like fries with that?


- Franc Zabkar
 
H

half_pint

Franc Zabkar said:
Franc Zabkar said:
What is it about the following
that you don't understand?

http://www.nwfusion.com/archive/1995/95-04-03isdn-a.html

"Top-speed V.34 modems use V.42 error control. When V.42 error control
is used [which is *all* the time unless something is seriously wrong],
NO START OR STOP BITS ARE SENT over the line."


They are still sent from the DTE to the DCE though.

Of course they are, at least for external serial (non-USB) modems. But
these extra bits have no impact upon the modem's connect speed, nor do
they affect the throughput for incompressible data, if the port rate
has been configured correctly. And therein lies the reason for your
fixation regarding this issue. If your more recent posts are any
guide, then it is clear that you have been restricting yourself to a
DTE rate of only 57600bps since the first day you installed your
modem.

Wrong firstly I didn't install my modem it was pre installed.

Then the person who installed it is just as ignorant as yourself.

Well my modem works fine so at least he is not as ignorant as you.
Millions of people have achieved this impossible task. With a little
knowledge and effort you can too.

Well they wasted their time as the values set in windows are ignored,
anyway I told you in an earlier post how to set it the DTE setting as you
were barking up the wrong tree.
The max "rated" DCE speed of a 56K modem is only 56000bps. OTOH, the
maximum rated DTE speed of hardware modems is at least 115200bps, and
can be as high as 230400bps. Soft modems can do even better. My own
hardware modem will report CONNECT 230400 when I configure it to
report the DTE speed, and it will have a throughput to match (for
highly compressible data). Yours will report CONNECT 115200 if you do
nothing more than select a port rate of 115200bps. Just look in the
INF file (assuming you have the correct one), or check the responses
at this registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Modem\000n\Respon
ses

But please, whatever you do, DON'T do the following. Don't go to My
Computer -> Dial-Up Networking -> don't right click your ISP -> don't
select Properties -> Configure -> General -> Maximum speed. Instead,
just keep farting around with COM port Properties in Device Manager.


What this proves is that you have no idea what you are doing or what
you are talking about. A COM port is a COM port, it is not a modem.
For example, I have one COM port to which I can attach any of four
serial devices via a switchbox. One is an external modem configured
for 115200bps, another is an old digital camera, a third is a DCC
connection to another PC, and the fourth is a Casio organizer running
at 9600bps. In each case it is not Device Manager that determines the
port speed, rather it is set by the application that takes control of
the COM port. All Device Manager does is to set some initial default
value.


You can't run a modem at twice its "rated speed", so the question is
pointless. Overclocking is for motherboards, not modems.


LOL you though that was a genuine question!!!! Your are obviously
far denser than I originally thought.
No, as I've explained to you elsewhere, you set up the COM port, and
the modem "autobauds" to these settings. So in effect you are
configuring the modem as a *consequence* of configuring the port. BTW,
I'm talking about configuring the COM port in the Modem Properties of
the DUN connectoid, not in Device Manager.

They are clearly marked as modem properties, take it up with Microsoft
http://groups.google.com/groups?selm=VKjW9.1855$zF6.155226@bgtnsc04-new s.ops.worldnet.att.net&output=gplain

OK, I'll grant you that one, but strictly speaking it isn't IE that
modifies your connection parameters, it's Dial-Up Networking. IE
merely delegates the job to a Control Panel applet (Internet Options),
which in turn delegates it to DUN. A more direct route would be to go
to My Computer -> Dial-Up Networking. You can also access the Control
Panel applet by going to Start -> Run and typing "control
inetcpl.cpl".

The flow is something like this:

IE -> Control Panel -> Internet Options -> inetcpl.cpl -> DUN -> Modem
Properties

If you delete or rename the inetcpl.cpl file, then the only way to get
to Modem Properties is via DUN directly.


A device will operate at its default power-on settings unless
configured otherwise.

Wrong. Not my modem anyway.
That is the meaning of the word "default".
Wrong.

Now,
as the configuration is performed by DUN, and as the modemlog is a
record of commands issued by DUN, an absence of configuration commands
proves that there was no change to the default settings.
Wrong.
But whatever
you do, please don't do *anything* that could possibly prove you are
wrong. Please don't capture a post-call diagnostic report, please
don't post the missing lines of your modemlog, and please don't add
any commands to your Extra Settings that could possibly damage your
fragile ego. And above all, please don't go to Control Panel -> Modems
-> Diagnostics -> More Info in case we find out what modem you really
have.

That won't tell me which modem I have all it will tell me is which one I
selected from the settings, my modem is not even listed there anyway.
I could probably choose any old modem and it would work.
Irrelevant if you have done it from Device Manager.


You will double your throughput for compressible files, unless
software compression is enabled. If your modem connects at 48000bps or
better, and if it can maintain this speed, then you should see a
slight improvement in throughput for incompressible files as well.

Anyone who live in the real world knows that no significant ammount of
data is sent uncompressed, it's a non-started


rate.

Someone who is unable to follow simple instructions is unemployable.

Well you may have been employed as a brainless moron in you time but
I am employed because I have a brain of my own, not to carry out
instructions like a brainless moron.
Tell Richard Gamberg, author of modemsite.com. Most of the
instructions are his, not mine. Maybe he has more patience than I.

You tell him you pompous git.
Not yet, but if you ever enter the workforce that's all you'll be fit
for. Would you like fries with that?

I doubt an McDonalds would employ an idiot like you.
It would probably take you a week to grill one burger and
even then it would be burnt to a cinder.
 
H

half_pint

Anyway I have got a good program called net medic which is
very useful for isatance.

Using standard modem I get connection speed 115200,
moden baud rate 28000 and connection time 21 seconds

However with standard 56k flex modem I get connection speed 115200,
moden baud rate 56000 and connection time 19 seconds.

In the former case I still get a full baud rate (not the
28000, as I can see I am obviously faster). But I
do get a 2 seconds knocked of my connection thime which is nice.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top