>The second way, is to use a program like Hyperterm, included with my
>copy of Win2K. That assumes a text session, like connecting to a BBS,
>and doesn't involve networking as such.
>One thing I noticed, is when I use Hyperterm to dialup Freenet, there
>was no connection speed message shown in the transaction. I'm still
>working on getting my Freenet session to record the connect speed.
ATQ0 = Quiet Mode Off - Displays result codes, user sees command
responses (e.g. OK, CONNECT)
ATQ1 = Quiet Mode On - Result codes are suppressed, user does not see
responses.
>I tried the Modemsite AD conversion test. In Hyperterm, to set up a
>dialup session, you select your "modem" from the menu. The modem is
>only listed if the modem has been installed. If you don't want to
>access the modem as a modem, then I use "COM1" from the menu, which
>means Hyperterm is simply sending text to COM1 and not dealing with
>the port as if there is a modem on it. By setting up a second
>Hyperterm shortcut (.ht) file, which accesses COM1 directly,
>I could send "ATY11" to the modem.
>
>http://www.modemsite.com/56k/x2-adconversion.asp
>
>This is what my modem recorded, when connected to Freenet. You have
>to use the ATY11 command on the modem, before the modem is reset, or
>the modem has attempted to dial out a second time.
>I also had trouble getting an "AT command set" for my modem. It is a 5686 from USR.
>They didn't have a manual for that exact modem (only a quick user guide). I had
>to use this one, which happens to document six different modems including my 5686.
>
>http://www.usr.com/support/5610b/561...5610b-user.pdf
>
> Paul
On Tue, 06 May 2008 06:10:50 -0500, just-me@myplace.com put finger to
keyboard and composed:
>I have a dialup ISP and the connection recently got very slow.
>Although I pay them a premium price for their service, their support
>is terrible. I have run every test on my computer and modem and
>everything seems fine. I had the phone company call me and say the
>phone line seems ok, although they said that they can not be sure
>without coming to my house and running tests, which would be costly
>for me.
You could retrieve the modem's last call report using Unimodem
Diagnostics.
Look for retrains (bad) and renegotiations (not so bad). Also check
the Rx/Tx error counts.
Note that the initial connect speed may be significantly more
optimistic than the final receive carrier rate.
A simple test you could do on your line is to lift your phone
receiver, break dialtone by dialing any digit, and then listen for
total silence. Any hiss or "static" indicates a problem.
To enable the modem's speaker for the whole of your dialup session,
add L3M2 (or L2M2 or L1M2 for lower volume) to the Extra Settings in
your DUN connectoid's properties.
You will then be able to hear what is going on. Short blips correspond
to rate renegotiations (eg 46667bps to 44000bps), whereas long 10-20
second negotiations similar to what you hear during the initial
connect phase represent retrains. Retrains are a sign that conditions
have become bad enough for the two modems to reassess the quality of
the phone line.
- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.