3Com 178400 Sportster Modem Problems!
Jason Sizemore
Hey yall!
I have 3COM/USR Sportster Voice Data Fax 56K Modem EXT (Model 178400)
and I'm having serious problems. First off, the modem always displays
the port speed instead of the connect speed. I've followed all the
directions at http://808hi.com to fix this problem and nothing works.
In fact, when I put the driver disk in for the modem (which has the
correct INF file - I've not changed INFs in a long time and the log
goes back to Nov and today's log is using the same INF) for Win98 to
load the driver for the Modem, it's list is blank in the "files that
are compatible" setting. Even when I install what I'm positive beyond
a doubt that I have the correct INF, Win98 says that the driver is not
made for my hardware.
I've un-installed and re-installed DUN to no avail.
Can anyone help me with this problem? Workarounds? Registry hacks?
A site that might have the firmware archived so I can re-flash?
Anything to save me a re-install of Win98 (which I'm really close to
doing any way but I'm nervous about it because I'd lose all my Y2K
updates from WindowsUpdate).
Hooda? Please share the knowledge wealth! =)
-----------== Posted via Newsfeeds.Com, Uncensored Usenet News ==----------
http://www.newsfeeds.com The Largest Usenet Servers in the World!
------== Over 73,000 Newsgroups - Including Dedicated Binaries Servers ==-----
Hooda Gest
Jason Sizemore wrote in message <38719971...@news.foxberry.net>...
>
>Hey yall!
>
>I have 3COM/USR Sportster Voice Data Fax 56K Modem EXT (Model 178400)
>and I'm having serious problems. First off, the modem always displays
>the port speed instead of the connect speed. I've followed all the
>directions at http://808hi.com to fix this problem and nothing works.
>
>In fact, when I put the driver disk in for the modem (which has the
>correct INF file - I've not changed INFs in a long time and the log
>goes back to Nov and today's log is using the same INF) for Win98 to
>load the driver for the Modem, it's list is blank in the "files that
>are compatible" setting. Even when I install what I'm positive beyond
>a doubt that I have the correct INF, Win98 says that the driver is not
>made for my hardware.
Never be "positive beyond a doubt" about anything. It usually results in a
red face and a stutter.
First, check the modem log (you may have to delete so it will restart) for
what DUN is using for an INF file. Then check the modem's connect report to
see what speed is being reported and compare that with what's in the .INF
file (INF files are just text files). If everything matches up, I'll be
truly amazed.
To properly install the correct .INF file, it sometimes takes deleting the
drvdata.bin and drvidx.bin from the Windows\Inf folder and
removing/re-installing the modem in software.
Since you have a Voice model, you need two .INF files, by the way.
Hooda
R Collins
"Jason Sizemore" <size...@foxberry.net> wrote in message
news:38719971...@news.foxberry.net...
>
> Hey yall!
>
> I have 3COM/USR Sportster Voice Data Fax 56K Modem EXT (Model
178400)
> and I'm having serious problems. First off, the modem always
displays
> the port speed instead of the connect speed. I've followed all the
> directions at http://808hi.com to fix this problem and nothing
works.
Here's a simple fact: 3Com modems _never_ report the port speed, they
_always_ report the modem to modem speed. If DUN is displaying the
port speed, the problem is (must be) with the .INF file that's being
used.
> In fact, when I put the driver disk in for the modem (which has the
> correct INF file - I've not changed INFs in a long time and the log
> goes back to Nov and today's log is using the same INF) for Win98 to
> load the driver for the Modem, it's list is blank in the "files that
> are compatible" setting. Even when I install what I'm positive
beyond
> a doubt that I have the correct INF, Win98 says that the driver is
not
> made for my hardware.
>
> I've un-installed and re-installed DUN to no avail.
Re-install the modem. Before you do so, rename the two files
DRVDATA.BIN and DRVINDX.BIN in Windows\ini to something else - like
DRVDATA.SAV and DRVINDX.SAV. When you re-install, _don't_ let Windows
find the modem, chose "I will select it from a list". When given the
option, select "Have Disk" and point to the media that has the .INF
file. You will _then_ be presented with a list of modems - those are
the modems that are supported by that .INF. Select the proper one.
The wizard should tell you "Building driver database" if you do all
this properly.
If you still have problems, download the latest .INF from the 3Com
site and _then_ follow the procedure above.
R Collins
> 01-04-2000 20:45:15.12 - Interpreted response: Ok
> 01-04-2000 20:45:15.12 - Send: AT&F&B1&A3E0Q0V1&D2&C1S0=0<cr>
> 01-04-2000 20:45:15.13 - Recv: AT&F&B1&A3E0Q0V1&D2&C1S0=0<cr>
> 01-04-2000 20:45:15.25 - Recv: <cr><lf>OK<cr><lf>
> 01-04-2000 20:45:15.25 - Interpreted response: Ok
> 01-04-2000 20:45:15.25 - Send:
ATS7=60S19=0L0M1&M4&K1&H1&R2&I0B0X3<cr>
> 01-04-2000 20:45:15.39 - Recv: <cr><lf>OK<cr><lf>
> 01-04-2000 20:45:15.39 - Interpreted response: Ok
> 01-04-2000 20:45:15.39 - Send: ATS11=50L0M3<cr>
> 01-04-2000 20:45:15.51 - Recv: <cr><lf>OK<cr><lf>
> 01-04-2000 20:45:15.51 - Interpreted response: Ok
> 01-04-2000 20:45:15.52 - Dialing.
> 01-04-2000 20:45:15.52 - Send: ATDT#######<cr>
> 01-04-2000 20:45:33.79 - Recv: <00><cr><lf>CONNECT
> 28800/ARQ/V34/LAPM/V42BIS<cr>
> 01-04-2000 20:45:33.79 - WARNING: Unrecognized response.
Retrying...
> 01-04-2000 20:45:33.79 - Connection established at 115200bps.
> 01-04-2000 20:45:33.79 - Error-control off or unknown.
> 01-04-2000 20:45:33.79 - Data compression off or unknown.
>
> Are you amazed yet? ;) Actually, the last two lines in this log have
> me worried because when I install the modem, the only extra settings
I
> use are ATS11=50L0M3.
Not amazed at all. The _modem_ is saying CONNECT
28800/ARQ/V34/LAPM.V42BIS which is the correct modem-modem speed,
using LAPM error correction and V.42bis data compression. The next 3
lines says DUN can't match that with anything in the .INF.
Re-install with the correct .INF, obtained from the 3Com site.
Jason Sizemore
wrote:
>Never be "positive beyond a doubt" about anything. It usually results in a
>red face and a stutter.
>
>First, check the modem log (you may have to delete so it will restart) for
>what DUN is using for an INF file. Then check the modem's connect report to
>see what speed is being reported and compare that with what's in the .INF
>file (INF files are just text files). If everything matches up, I'll be
>truly amazed.
Here a snip from the current Modem log.
01-04-2000 20:45:14.60 - 3com Sportster 56k Voice EXT in use.
01-04-2000 20:45:14.61 - Modem type: Sportster 56k Voice EXT
01-04-2000 20:45:14.61 - Modem inf path: 3COMCO~4.INF
01-04-2000 20:45:14.61 - Modem inf section: Modem5
01-04-2000 20:45:14.87 - 115200,N,8,1
01-04-2000 20:45:14.87 - 115200,N,8,1
01-04-2000 20:45:14.87 - Initializing modem.
01-04-2000 20:45:14.87 - Send: AT<cr>
01-04-2000 20:45:15.00 - Recv: <cr><lf>OK<cr><lf>
01-04-2000 20:45:15.00 - Interpreted response: Ok
01-04-2000 20:45:15.00 - Send: ATZ<cr>
01-04-2000 20:45:15.12 - Recv: <cr><lf>OK<cr><lf>
01-04-2000 20:45:15.12 - Interpreted response: Ok
01-04-2000 20:45:15.12 - Send: AT&F&B1&A3E0Q0V1&D2&C1S0=0<cr>
01-04-2000 20:45:15.13 - Recv: AT&F&B1&A3E0Q0V1&D2&C1S0=0<cr>
01-04-2000 20:45:15.25 - Recv: <cr><lf>OK<cr><lf>
01-04-2000 20:45:15.25 - Interpreted response: Ok
01-04-2000 20:45:15.25 - Send: ATS7=60S19=0L0M1&M4&K1&H1&R2&I0B0X3<cr>
01-04-2000 20:45:15.39 - Recv: <cr><lf>OK<cr><lf>
01-04-2000 20:45:15.39 - Interpreted response: Ok
01-04-2000 20:45:15.39 - Send: ATS11=50L0M3<cr>
01-04-2000 20:45:15.51 - Recv: <cr><lf>OK<cr><lf>
01-04-2000 20:45:15.51 - Interpreted response: Ok
01-04-2000 20:45:15.52 - Dialing.
01-04-2000 20:45:15.52 - Send: ATDT#######<cr>
01-04-2000 20:45:33.79 - Recv: <00><cr><lf>CONNECT
28800/ARQ/V34/LAPM/V42BIS<cr>
01-04-2000 20:45:33.79 - WARNING: Unrecognized response. Retrying...
01-04-2000 20:45:33.79 - Connection established at 115200bps.
01-04-2000 20:45:33.79 - Error-control off or unknown.
01-04-2000 20:45:33.79 - Data compression off or unknown.
Are you amazed yet? ;) Actually, the last two lines in this log have
me worried because when I install the modem, the only extra settings I
use are ATS11=50L0M3.
>To properly install the correct .INF file, it sometimes takes deleting the
>drvdata.bin and drvidx.bin from the Windows\Inf folder and
>removing/re-installing the modem in software.
>
>Since you have a Voice model, you need two .INF files, by the way.
Yeah, one for the modem itself and then the other for the Wave Device.
Got them. I'll try what you mentioned above though and see what
happens. One other thing: This modem used to be PnP but for some odd
reason, PnP does not find the modem even if I totally remove the modem
and reboot Win98. The hardware wizard does not pop up automactially
when Win98 reloads. Strange stuff...
>Hooda
Hooda Gest
Jason Sizemore wrote in message <3872b22...@news.foxberry.net>...
Someone (either you or one of your well-meaning friends) has hacked your
registry. The above init strings are incorrect for USR modems. It should
look something like this...
01-04-2000 12:32:53.70 - Initializing modem.
01-04-2000 12:32:53.70 - Send: AT<cr>
01-04-2000 12:32:53.74 - Recv: <cr><lf>OK<cr><lf>
01-04-2000 12:32:53.74 - Interpreted response: Ok
01-04-2000 12:32:53.74 - Send: AT&F1E0Q0V1&C1&D2S0=0<cr>
01-04-2000 12:32:53.79 - Recv: <cr><lf>OK<cr><lf>
01-04-2000 12:32:53.79 - Interpreted response: Ok
01-04-2000 12:32:53.79 - Send: ATS7=60S19=0L3&M4&K1&H1&R2&I0B0X4<cr>
Note the &F1 vs your &F. Also notice the AT rather than an ATZ
So my first suggestion is to correct your registry or completely uninstall
the modem and re-install it properly. Or Both.
>01-04-2000 20:45:15.39 - Recv: <cr><lf>OK<cr><lf>
>01-04-2000 20:45:15.39 - Interpreted response: Ok
>01-04-2000 20:45:15.39 - Send: ATS11=50L0M3<cr>
>01-04-2000 20:45:15.51 - Recv: <cr><lf>OK<cr><lf>
>01-04-2000 20:45:15.51 - Interpreted response: Ok
>01-04-2000 20:45:15.52 - Dialing.
>01-04-2000 20:45:15.52 - Send: ATDT#######<cr>
>01-04-2000 20:45:33.79 - Recv: <00><cr><lf>CONNECT
>28800/ARQ/V34/LAPM/V42BIS<cr>
>01-04-2000 20:45:33.79 - WARNING: Unrecognized response. Retrying...
>01-04-2000 20:45:33.79 - Connection established at 115200bps.
>01-04-2000 20:45:33.79 - Error-control off or unknown.
>01-04-2000 20:45:33.79 - Data compression off or unknown.
>
>Are you amazed yet? ;) Actually, the last two lines in this log have
>me worried because when I install the modem, the only extra settings I
>use are ATS11=50L0M3.
When you re-install the modem, use the correct .INF file. My bet is you have
the wrong one isntalled, perhaps one from before you upgraded it to V.90.
You can doublecheck that, as I said, by examining the .INF file.
>>To properly install the correct .INF file, it sometimes takes deleting the
>>drvdata.bin and drvidx.bin from the Windows\Inf folder and
>>removing/re-installing the modem in software.
>>
>>Since you have a Voice model, you need two .INF files, by the way.
>
>Yeah, one for the modem itself and then the other for the Wave Device.
>Got them. I'll try what you mentioned above though and see what
>happens. One other thing: This modem used to be PnP but for some odd
>reason, PnP does not find the modem even if I totally remove the modem
>and reboot Win98. The hardware wizard does not pop up automactially
>when Win98 reloads. Strange stuff...
A 3Com model (as opposed to the ones that come up as "U.S. Robotics" should
be PnP and work fine but try what I suggested and make sure you clean up
that Registry first.
Hooda
Pero Volarevic
>
> 28800/ARQ/V34/LAPM/V42BIS<cr>
> 01-04-2000 20:45:33.79 - WARNING: Unrecognized response. Retrying...
That extra <00> character is what makes response unrecognized.
You can hack the INF / registry, but real question is why that character
is there - it could be a modem or serial port problem.
--
Pero Volarevic
Hooda Gest
Pero Volarevic wrote in message <84vkri$tjc$1...@as102.tel.hr>...
Excellent point! I missed that <00> and I shouldn't have. This is similar to
the problem someone had with a Dell OEM Winmodem (made by 3Com/USR but
sold/supported by Dell). In that case, DUN couldn't report the speed
correctly either. We figured that to be the Dell firmware.
Interesting...
It would not be hard to edit the .INF file and update that for the modem...
Hooda
Jason Sizemore
wrote:
>Excellent point! I missed that <00> and I shouldn't have. This is similar to
>the problem someone had with a Dell OEM Winmodem (made by 3Com/USR but
>sold/supported by Dell). In that case, DUN couldn't report the speed
>correctly either. We figured that to be the Dell firmware.
>
>Interesting...
>
>It would not be hard to edit the .INF file and update that for the modem...
>
>Hooda
>
>
Thanks for the responses, folks!
I've found out what I believe caused the problem and it was a floppy
from my ISP. Every since I used that floppy, this problem happened. It
made additions to my registry that I didn't like and I hacked it out.
The INF I'm using now is one that displays "Sportster 56k Data Fax" in
the database menu. It still displayed my port speed after using this
INF (and all the others I've tried) but I fixed the problem by
disabling x2 and V.90. The ISP I'm with now is a V.90/KFlex ISP and I
just find it really wierd that with V.90/x2 disabled, the correct
speed is coming up.
Now to e-mail USR/3com and see if any groveling would help my chances
of getting the V.90 code for my model modem so I can re-flash this
thing. I believe this modem's BIOS was corrupted in some way over the
summer by a thunderstorm. It should've fried the modem but it's been
working fine except for a few problems like the AA light constantly on
when I power it up.
Anyway thanks for everything!
Hooda Gest
Jason Sizemore wrote in message <38746d83...@news.foxberry.net>...
>On Wed, 5 Jan 2000 19:31:11 -0500, "Hooda Gest" <be@one_with.com>
>wrote:
>
>>Excellent point! I missed that <00> and I shouldn't have. This is similar
to
>>the problem someone had with a Dell OEM Winmodem (made by 3Com/USR but
>>sold/supported by Dell). In that case, DUN couldn't report the speed
>>correctly either. We figured that to be the Dell firmware.
>>
>>Interesting...
>>
>>It would not be hard to edit the .INF file and update that for the
modem...
>>
>>Hooda
>>
>>
>
>Thanks for the responses, folks!
>
>I've found out what I believe caused the problem and it was a floppy
>from my ISP. Every since I used that floppy, this problem happened. It
>made additions to my registry that I didn't like and I hacked it out.
>
>The INF I'm using now is one that displays "Sportster 56k Data Fax" in
>the database menu. It still displayed my port speed after using this
>INF (and all the others I've tried) but I fixed the problem by
>disabling x2 and V.90. The ISP I'm with now is a V.90/KFlex ISP and I
>just find it really wierd that with V.90/x2 disabled, the correct
>speed is coming up.
The INF file you are using is either incorrect (as in old and doesn't cover
x2 or V.90) or has a fault in it (the speed you connect at in V.90 is not in
the file). The V.34 speeds are there so when in that mode will get the speed
reported properly by DUN.
>Now to e-mail USR/3com and see if any groveling would help my chances
>of getting the V.90 code for my model modem so I can re-flash this
>thing. I believe this modem's BIOS was corrupted in some way over the
>summer by a thunderstorm. It should've fried the modem but it's been
>working fine except for a few problems like the AA light constantly on
>when I power it up.
Give that a shot, it can't hurt. However, you also ought to consider making
sure you have the correct INF file for the modem.
The AA light coming on at power up is probably because you have S0=1 saved
and Dip switch 5 set to turn auto-answer on. But it is possible that a
thunderstorm caused some problems.
Hooda
Hooda Gest
Jason Sizemore wrote in message <3875421c...@news.foxberry.net>...
>On Thu, 6 Jan 2000 09:14:53 -0500, "Hooda Gest" <be@one_with.com>
>wrote:
>
>
>>The INF file you are using is either incorrect (as in old and doesn't
cover
>>x2 or V.90) or has a fault in it (the speed you connect at in V.90 is not
in
>>the file). The V.34 speeds are there so when in that mode will get the
speed
>>reported properly by DUN.
>
>and V90. Why Win98's DUN is reporting otherwise remains a mystery. No
>big deal since my phone lines suck and 28.8 is all I can muster.
Can I see a snippet of the modem log where the modem is identified and then
initialized?
I am curious about this...
>>>Now to e-mail USR/3com and see if any groveling would help my chances
>>>of getting the V.90 code for my model modem so I can re-flash this
>>>thing.
>>
>>Give that a shot, it can't hurt. However, you also ought to consider
making
>>sure you have the correct INF file for the modem.
>>
>>The AA light coming on at power up is probably because you have S0=1 saved
>>and Dip switch 5 set to turn auto-answer on. But it is possible that a
>>thunderstorm caused some problems.
>>
>>Hooda
>
>Actually, when this AA light upon power up problem reared its ugly
>head, I went into the modem's properties and performed some diagnostic
>test to see if this register was changed. The S0 register is at 0 for
>disabled. I even opened a direct connection to COM2 with Hyperterminal
>to see if I could manually turn it off and it never would. It does go
>off when the modem is itialized by DUN just before connecting to the
>internet, so that tells me the BIOS is slightly hoarked. If 3com
>doesn't send me the flash code, I'll just buy another modem and put
>this thing is a dark box in the corner of the closet. =)
What position is Dip switch 5 in? It should be OFF. You may be right about
the firmware being hosed. Or it may even be a hardware problem.
Hooda
Jason Sizemore
wrote:
>The INF file you are using is either incorrect (as in old and doesn't cover
>x2 or V.90) or has a fault in it (the speed you connect at in V.90 is not in
>the file). The V.34 speeds are there so when in that mode will get the speed
>reported properly by DUN.
I looked at the INF and it does include result code displays for x2
and V90. Why Win98's DUN is reporting otherwise remains a mystery. No
big deal since my phone lines suck and 28.8 is all I can muster.
>>Now to e-mail USR/3com and see if any groveling would help my chances
>>of getting the V.90 code for my model modem so I can re-flash this
>>thing.
>
>Give that a shot, it can't hurt. However, you also ought to consider making
>sure you have the correct INF file for the modem.
>
>The AA light coming on at power up is probably because you have S0=1 saved
>and Dip switch 5 set to turn auto-answer on. But it is possible that a
>thunderstorm caused some problems.
>
>Hooda
Actually, when this AA light upon power up problem reared its ugly
head, I went into the modem's properties and performed some diagnostic
test to see if this register was changed. The S0 register is at 0 for
disabled. I even opened a direct connection to COM2 with Hyperterminal
to see if I could manually turn it off and it never would. It does go
off when the modem is itialized by DUN just before connecting to the
internet, so that tells me the BIOS is slightly hoarked. If 3com
doesn't send me the flash code, I'll just buy another modem and put
this thing is a dark box in the corner of the closet. =)
-----------== Posted via Newsfeeds.Com, Uncensored Usenet News ==----------
Jason Sizemore
wrote:
>Can I see a snippet of the modem log where the modem is identified and then
>initialized?
>I am curious about this...
Here's a snippet of the modemlog from the initialization from DUN to
reporting the port speed as a connect rate.
01-04-2000 22:29:00.48 - Sportster 56k Data Fax in use.
01-04-2000 22:29:00.50 - Modem type: Sportster 56k Data Fax
01-04-2000 22:29:00.50 - Modem inf path: USROBO~1.INF
01-04-2000 22:29:00.50 - Modem inf section: Modem99
01-04-2000 22:29:00.73 - 115200,N,8,1
01-04-2000 22:29:00.73 - 115200,N,8,1
01-04-2000 22:29:00.73 - Initializing modem.
01-04-2000 22:29:00.73 - Send: ATE0Q0V1<cr>
01-04-2000 22:29:00.73 - Recv: ATE0Q0V1<cr>
01-04-2000 22:29:00.86 - Recv: <cr><lf>OK<cr><lf>
01-04-2000 22:29:00.86 - Interpreted response: Ok
01-04-2000 22:29:00.86 - Send: AT&F1E0Q0V1&C1&D2S0=0<cr>
01-04-2000 22:29:00.99 - Recv: <cr><lf>OK<cr><lf>
01-04-2000 22:29:00.99 - Interpreted response: Ok
01-04-2000 22:29:00.99 - Send: ATS7=60S19=0M1&M4&K1&H1&R2&I0B0X3<cr>
01-04-2000 22:29:01.12 - Recv: <cr><lf>OK<cr><lf>
01-04-2000 22:29:01.12 - Interpreted response: Ok
01-04-2000 22:29:01.12 - Send: ATS11=50L0M3<cr>
01-04-2000 22:29:01.25 - Recv: <cr><lf>OK<cr><lf>
01-04-2000 22:29:01.25 - Interpreted response: Ok
01-04-2000 22:29:01.25 - Dialing.
01-04-2000 22:29:01.25 - Send: ATDT#######<cr>
01-04-2000 22:29:19.61 - Recv: <00><cr><lf>CONNECT
28800/ARQ/V34/LAPM/V42BIS<cr>
01-04-2000 22:29:19.61 - WARNING: Unrecognized response. Retrying...
01-04-2000 22:29:19.61 - Connection established at 115200bps.
01-04-2000 22:29:19.61 - Error-control off or unknown.
01-04-2000 22:29:19.61 - Data compression off or unknown.
01-04-2000 22:29:33.56 - Hanging up the modem.
01-04-2000 22:29:33.56 - Hardware hangup by lowering DTR.
01-04-2000 22:29:33.82 - Recv: <cr><lf>NO CARRIER<cr><lf>
01-04-2000 22:29:33.82 - Interpreted response: No Carrier
01-04-2000 22:29:33.82 - Send: ATH<cr>
01-04-2000 22:29:33.94 - Recv: <cr><lf>OK<cr><lf>
01-04-2000 22:29:33.94 - Interpreted response: Ok
01-04-2000 22:29:33.94 - 115200,N,8,1
01-04-2000 22:29:33.94 - Session Statistics:
01-04-2000 22:29:33.94 - Reads : 753 bytes
01-04-2000 22:29:33.94 - Writes: 709 bytes
01-04-2000 22:29:33.94 - General Comm Errors: 1
01-04-2000 22:29:33.94 - Frame Errors: 1
01-04-2000 22:29:33.94 - Sportster 56k Data Fax closed.
And here's a snip of the modemlog displaying correctly...
01-04-2000 22:32:44.16 - Sportster 56k Data Fax in use.
01-04-2000 22:32:44.19 - Modem type: Sportster 56k Data Fax
01-04-2000 22:32:44.19 - Modem inf path: USROBO~1.INF
01-04-2000 22:32:44.19 - Modem inf section: Modem99
01-04-2000 22:32:44.44 - 115200,N,8,1
01-04-2000 22:32:44.44 - 115200,N,8,1
01-04-2000 22:32:44.44 - Initializing modem.
01-04-2000 22:32:44.44 - Send: ATE0Q0V1<cr>
01-04-2000 22:32:44.44 - Recv: ATE0Q0V1<cr>
01-04-2000 22:32:44.57 - Recv: <cr><lf>OK<cr><lf>
01-04-2000 22:32:44.57 - Interpreted response: Ok
01-04-2000 22:32:44.57 - Send: AT&F1E0Q0V1&C1&D2S0=0<cr>
01-04-2000 22:32:44.70 - Recv: <cr><lf>OK<cr><lf>
01-04-2000 22:32:44.70 - Interpreted response: Ok
01-04-2000 22:32:44.70 - Send: ATS7=60S19=0M1&M4&K1&H1&R2&I0B0X3<cr>
01-04-2000 22:32:44.83 - Recv: <cr><lf>OK<cr><lf>
01-04-2000 22:32:44.83 - Interpreted response: Ok
01-04-2000 22:32:44.83 - Send: ATS11=50L0M3S32=98<cr>
** Notice that I disabled V90 and x2 in the above line....
01-04-2000 22:32:44.96 - Recv: <cr><lf>OK<cr><lf>
01-04-2000 22:32:44.96 - Interpreted response: Ok
01-04-2000 22:32:44.96 - Dialing.
01-04-2000 22:32:44.96 - Send: ATDT#######<cr>
01-04-2000 22:33:01.46 - Recv: <cr><lf>CONNECT
28800/ARQ/V34/LAPM/V42BIS<cr><lf>
01-04-2000 22:33:01.46 - Interpreted response: Connect
01-04-2000 22:33:01.46 - Connection established at 28800bps.
01-04-2000 22:33:01.46 - Error-control on.
01-04-2000 22:33:01.46 - Data compression on.
01-04-2000 22:33:20.34 - Hanging up the modem.
01-04-2000 22:33:20.34 - Hardware hangup by lowering DTR.
01-04-2000 22:33:20.59 - Recv: <cr><lf>NO CARRIER<cr><lf>
01-04-2000 22:33:20.59 - Interpreted response: No Carrier
01-04-2000 22:33:20.59 - Send: ATH<cr>
01-04-2000 22:33:20.72 - Recv: <cr><lf>OK<cr><lf>
01-04-2000 22:33:20.72 - Interpreted response: Ok
01-04-2000 22:33:20.72 - 115200,N,8,1
01-04-2000 22:33:20.72 - Session Statistics:
01-04-2000 22:33:20.72 - Reads : 603 bytes
01-04-2000 22:33:20.72 - Writes: 609 bytes
01-04-2000 22:33:20.72 - Sportster 56k Data Fax closed.
>What position is Dip switch 5 in? It should be OFF. You may be right about
>the firmware being hosed. Or it may even be a hardware problem.
>
>Hooda
This is an external modem so there's no dipswitches to play with.
This is one strange case! =)
--Sy--
Hooda Gest
Jason Sizemore wrote in message <3876f0e2...@news.foxberry.net>...
The null character (the <00>) is what's causing the problem with the
unrecognized string.
The problem is that it only seems to happen when V.90 is enabled. That's
rather odd and I would agree that the problem is one of firmware. I don't
know if it's having an effect on your ability to do better than V.34 but you
do have a beef with 3Com. I am assuming the modem is a 3Com modem and not an
OEM version.
One other thing... this is a Voice model. I have to wonder if the modem is
being properly identified and, therefore, properly configured. I'd
doublecheck that also.
>>What position is Dip switch 5 in? It should be OFF. You may be right
about
>>the firmware being hosed. Or it may even be a hardware problem.
>>
>>Hooda
>
>This is an external modem so there's no dipswitches to play with.
There are dip switches on all my external USR modems. Since I don't have all
of the USR models, I can't say this is always true but I would suspect it is
from that model number.
Hooda
Art Jackson
> unrecognized string.
>
> The problem is that it only seems to happen when V.90 is enabled. That's
> rather odd and I would agree that the problem is one of firmware. I don't
> know if it's having an effect on your ability to do better than V.34 but you
> do have a beef with 3Com. I am assuming the modem is a 3Com modem and not an
> OEM version.
>
> One other thing... this is a Voice model. I have to wonder if the modem is
> being properly identified and, therefore, properly configured. I'd
> doublecheck that also.
>
> about
> >>the firmware being hosed. Or it may even be a hardware problem.
> >>
> >>Hooda
> >
> >This is an external modem so there's no dipswitches to play with.
>
> of the USR models, I can't say this is always true but I would suspect it is
> from that model number.
>
> Hooda
Also it appears that the modem is still installed with the old x2
.inf file as indicated by the "Sportster" name. When upgraded to
V.90 and using a V.90 .inf file, the modem is called "U S Robotics"
An upgraded x2 modem, can and will be installed as a "Sportster"
if the old x2 .inf file is left on your system after the upgrade.
Another strange indication is that it calls the modem a Data Fax
modem, while the 178400 model is a Voice modem but the log makes
no mention of that fact at all.
I'd recommend cleaning the system of any old .inf files, then
removing the modem and re-installing it with the latest .inf file.
If you have already downloaded the new .inf, put it on a floppy.
Then do Start|Find|Files or folders and enter *usr*.inf and
delete any files it finds, then do the same for *3co*.inf and
delete them too. Then in Control Panel, Remove your modem and
reboot. Plug n Pray should detect your modem and say it can install
it as a Standard modem. That indicates a clean system with no .inf
file that can properly install the modem. That is where you insert
the floppy with the latest .inf file, and browse to the A: drive
to find the new file to complete the installation. The .inf file(s)
you need is the mdm3comv.inf and 3comwave.inf from the link below.
If unsuccessful in getting a clean install still, delete the two
files DRVIDX.BIN and DRVDATA.BIN in the Windows/inf folder, then
try again. Good luck.
http://consumer.3com.com/voice/inf/index.html
Windows 95/98/NT 4.0 UNIMODEM/V and TAPI support for the USRobotics
voice and USRobotics Vi modems ONLY! This is NOT for USRobotics
Data/Fax modems.
3comwave.inf file size: 2401 bytes file data: 04-17-98
Windows 95/98/NT 4.0 driver for USRobotics Voice 33.6k and 56k modems
bought between January 1996 to present. Copy this file onto a blank
floppy disk. Remove all Sportster modems in Control Panel/Modems.
Shutdown and restart your computer. When prompted select "Change" or
"Have Disk" and point it to the floppy drive. Select the appropriate
model and then follow the prompts to finish modem installation.
NOTE: You will need to download the 3COMWAVE.INF to complete the
modem's installation.
mdm3comv.inf file size: 51105 bytes file data: 04-17-98
--
*************************** _______
| Art Jackson W4TOY | When all else | |
| Owensboro, Kentucky USA | fails. Read THE | HOLY |
| artj...@mindspring.com | Instruction Book. | BIBLE |
*************************** |_______|
Jason Sizemore
Sadly, Win98 and PnP *used* to detect this modem as a "Sportster 56k
Voice Fax Modem PnP", but after the "AA light always on at powerup"
problem arised, PnP seemingly never detected this modem again.
Thanks for the replies again, Art and Hooda.
I'll perform the INF dance again and try enabling/disabling V.90 and
x2 with them and see if I get the same results. I'm going to fire off
an E-mail to 3com as well and see if I can get the V.90 flash code on
a disk.
I'll post the log after everything on my end is done.
Jason Sizemore
Here's the lowdown.
I completely removed the anything related to Sportster modems in the
Windows98 driver database.
I then installed the correct INF which displays the modem as being a
"Sportster 56K Voice EXT".
Here are the results of the new modemlog.
01-09-2000 06:19:28.78 - U.S. Robotics 56K Voice EXT in use.
01-09-2000 06:19:28.80 - Modem type: U.S. Robotics 56K Voice EXT
01-09-2000 06:19:28.80 - Modem inf path: 3COMCO~1.INF
01-09-2000 06:19:28.80 - Modem inf section: ModemPCMVex
01-09-2000 06:19:29.03 - 115200,N,8,1
01-09-2000 06:19:29.03 - 115200,N,8,1
01-09-2000 06:19:29.03 - Initializing modem.
01-09-2000 06:19:29.03 - Send: AT#CLS=0<cr>
01-09-2000 06:19:29.03 - Recv: AT#CLS=0<cr>
01-09-2000 06:19:29.15 - Recv: <cr><lf>OK<cr><lf>
01-09-2000 06:19:29.15 - Interpreted response: Ok
01-09-2000 06:19:29.15 - Send: AT&F1E0Q0V1&C1&D2S0=0<cr>
01-09-2000 06:19:29.16 - Recv: AT&F1E0Q0V1&C1&D2S0=0<cr>
01-09-2000 06:19:29.28 - Recv: <cr><lf>OK<cr><lf>
01-09-2000 06:19:29.28 - Interpreted response: Ok
01-09-2000 06:19:29.28 - Send: ATS7=60S19=0M1&M4&K1&H1&R2&I0B0X3<cr>
01-09-2000 06:19:29.41 - Recv: <cr><lf>OK<cr><lf>
01-09-2000 06:19:29.41 - Interpreted response: Ok
01-09-2000 06:19:29.41 - Send: ATS11=50L0M3<cr>
01-09-2000 06:19:29.54 - Recv: <cr><lf>OK<cr><lf>
01-09-2000 06:19:29.54 - Interpreted response: Ok
01-09-2000 06:19:29.54 - Dialing.
01-09-2000 06:19:29.54 - Send: ATDT#######<cr>
01-09-2000 06:19:47.98 - Recv: <00><cr><lf>CONNECT
28800/ARQ/V34/LAPM/V42BIS<cr>
01-09-2000 06:19:47.98 - WARNING: Unrecognized response. Retrying...
01-09-2000 06:19:47.98 - Connection established at 115200bps.
01-09-2000 06:19:47.98 - Error-control off or unknown.
01-09-2000 06:19:47.98 - Data compression off or unknown.
01-09-2000 06:20:00.68 - Hanging up the modem.
01-09-2000 06:20:00.68 - Hardware hangup by lowering DTR.
01-09-2000 06:20:00.94 - Recv: <cr><lf>NO CARRIER<cr><lf>
01-09-2000 06:20:00.94 - Interpreted response: No Carrier
01-09-2000 06:20:00.94 - Send: ATH<cr>
01-09-2000 06:20:01.07 - Recv: <cr><lf>OK<cr><lf>
01-09-2000 06:20:01.07 - Interpreted response: Ok
01-09-2000 06:20:01.07 - 115200,N,8,1
01-09-2000 06:20:01.07 - Session Statistics:
01-09-2000 06:20:01.07 - Reads : 572 bytes
01-09-2000 06:20:01.07 - Writes: 580 bytes
01-09-2000 06:20:01.07 - General Comm Errors: 1
01-09-2000 06:20:01.07 - Frame Errors: 1
01-09-2000 06:20:01.07 - U.S. Robotics 56K Voice EXT closed.
This is with V.90 and x2 enabled. As I expected, that <00> null point
is back again and the port speed is used as connection rate.
Next, I disable V.90/x2 and reconnect.
01-09-2000 06:20:47.09 - U.S. Robotics 56K Voice EXT in use.
01-09-2000 06:20:47.11 - Modem type: U.S. Robotics 56K Voice EXT
01-09-2000 06:20:47.11 - Modem inf path: 3COMCO~1.INF
01-09-2000 06:20:47.11 - Modem inf section: ModemPCMVex
01-09-2000 06:20:47.36 - 115200,N,8,1
01-09-2000 06:20:47.36 - 115200,N,8,1
01-09-2000 06:20:47.36 - Initializing modem.
01-09-2000 06:20:47.36 - Send: AT#CLS=0<cr>
01-09-2000 06:20:47.36 - Recv: AT#CLS=0<cr>
01-09-2000 06:20:47.48 - Recv: <cr><lf>OK<cr><lf>
01-09-2000 06:20:47.48 - Interpreted response: Ok
01-09-2000 06:20:47.48 - Send: AT&F1E0Q0V1&C1&D2S0=0<cr>
01-09-2000 06:20:47.49 - Recv: AT&F1E0Q0V1&C1&D2S0=0<cr>
01-09-2000 06:20:47.61 - Recv: <cr><lf>OK<cr><lf>
01-09-2000 06:20:47.61 - Interpreted response: Ok
01-09-2000 06:20:47.61 - Send: ATS7=60S19=0M1&M4&K1&H1&R2&I0B0X3<cr>
01-09-2000 06:20:47.74 - Recv: <cr><lf>OK<cr><lf>
01-09-2000 06:20:47.74 - Interpreted response: Ok
01-09-2000 06:20:47.74 - Send: ATS11=50L0M3S32=98&N13<cr>
01-09-2000 06:20:47.87 - Recv: <cr><lf>OK<cr><lf>
01-09-2000 06:20:47.87 - Interpreted response: Ok
01-09-2000 06:20:47.87 - Dialing.
01-09-2000 06:20:47.87 - Send: ATDT#######<cr>
01-09-2000 06:21:05.11 - Recv: <cr><lf>CONNECT
26400/ARQ/V34/LAPM/V42BIS<cr><lf>
01-09-2000 06:21:05.11 - Interpreted response: Connect
01-09-2000 06:21:05.11 - Connection established at 26400bps.
01-09-2000 06:21:05.11 - Error-control on.
01-09-2000 06:21:05.11 - Data compression on.
Due to my sorry phone line quality, I limit my speed to 26,400. 28,800
connections are possible on my line, but ARQ goes completely nuts
during online gameplay and I usually get loss of carrier. Regardless,
the result code is interpreted properly.
This really smells like a firmware corruption. The modem is never
detected by PnP (I can remove the modem and reboot Windows and I still
have to manually install the modem. The "New Hardware Wizard" doesn't
pop up at all. Combine that with the AA light problem and this one
here, and the only thing plausible is the modem got a slight spike
last summer during a thunderstorm (and I remember the day because I
was at a mall when the surprize storm hit and I couldn't make it home
to pull the plug! I had hoped my brother in-law would've unplugged it
as I've asked him to in case storms appear and I either forget to do
it or not around. When I got home, the phone lines were still in the
wall.)
Time to contact 3com!!
Art Jackson
Probably so, at least now the modem is being properly identified
by the correct .inf file as shown in the modem log. I'm still a little
confused by your first statement about it still being called a
"Sportster" while the log clearly shows it as "U S Robotics"
Is the modem being installed twice, with different names?
Also I noticed the X3 in the second init string, do you have "Wait
for Dial Tone before dialing unchecked? Normally that is X4 which
enables all results codes. That shouldn't be a problem, but it does
look odd. The <00> coming out of the modem is the reason for the
failure and Warning message, and reporting of DTE speed. Maybe
Hooda can add some thoughts on this. Good luck.
Jack Carrigan
standard.....btw, I am new to init strings, & am just messing around.
When I first bought this modem, it said it was a USR 56k Sportster,
then I ran the flash update to v.90 that I got from the 3com site. I
gotta say, even though I SOMETIMES have to attempt to connect a few
times, I have never had a speedier, less likely to drop me modem in
the last 5 years....don't know if this helps anyone at all, but I
wanted to toss it in, to see if anyone could maybe see the reason that
I'd get the occasional trouble connecting, initially...BTW again, my
average download rate from my own ISP's ftp site with a zipped file is
in the 54Kbps range, which is by far the fastest I have ever gotten
over a modem....
01-15-2000 00:10:14.03 - U.S. Robotics 56K Win INT in use.
01-15-2000 00:10:14.06 - Modem type: U.S. Robotics 56K Win INT
01-15-2000 00:10:14.06 - Modem inf path: WINMODEM.INF
01-15-2000 00:10:14.06 - Modem inf section: Winmodem
01-15-2000 00:10:14.06 - 115200,N,8,1
01-15-2000 00:10:14.06 - 115200,N,8,1
01-15-2000 00:10:14.07 - Initializing modem.
01-15-2000 00:10:14.07 - Send: AT<cr>
01-15-2000 00:10:14.08 - Recv: AT<cr>
01-15-2000 00:10:14.08 - Recv: <cr><lf>OK<cr><lf>
01-15-2000 00:10:14.08 - Interpreted response: Ok
01-15-2000 00:10:14.08 - Send: AT&F1E0V1&C1&D2S0=0<cr>
01-15-2000 00:10:14.13 - Recv: AT&F1E0V1&C1&D2S0=0<cr>
01-15-2000 00:10:14.13 - Recv: <cr><lf>OK<cr><lf>
01-15-2000 00:10:14.13 - Interpreted response: Ok
01-15-2000 00:10:14.13 - Send: ATS7=60S19=0L3M1&M4&K1&H1&R2&I0B0X4<cr>
01-15-2000 00:10:14.18 - Recv: <cr><lf>OK<cr><lf>
01-15-2000 00:10:14.18 - Interpreted response: Ok
01-15-2000 00:10:14.18 - Send: AT&F1&B1&D2&H1&I0&K1&M4S7=60<cr>
01-15-2000 00:10:14.23 - Recv: <cr><lf>OK<cr><lf>
01-15-2000 00:10:14.23 - Interpreted response: Ok
01-15-2000 00:10:14.23 - Dialing.
01-15-2000 00:10:14.23 - Send: ATDT;<cr>
01-15-2000 00:10:14.30 - Recv: ATDT;<cr>
01-15-2000 00:10:15.90 - Recv: <cr><lf>OK<cr><lf>
01-15-2000 00:10:15.90 - Interpreted response: Ok
01-15-2000 00:10:15.90 - Dialing.
01-15-2000 00:10:15.90 - Send: ATDT*##,###########,,,<cr>
01-15-2000 00:10:15.91 - Recv: ATDT*70,12163771020,,,<cr>
01-15-2000 00:10:40.81 - Recv: <cr><lf>CONNECT
50666/ARQ/V90/LAPM/V42BIS<cr><lf>
01-15-2000 00:10:40.81 - Interpreted response: Connect
01-15-2000 00:10:40.81 - Connection established at 50666bps.
01-15-2000 00:10:40.81 - Error-control on.
01-15-2000 00:10:40.81 - Data compression on.
Art Jackson
Everything looks perfectly normal up to this point, where you have
entered in DUN's Extra settings, a lengthy init string that basically
wipes out the first properly entered string, then resets most of them
to the same value. The AT&F1 resets everything to factory defaults,
that results in E1 being turned on again, which is why you see the
dialed number being echoed from the modem. The other exception is
&B1 which sets a fixed DTE rate, the default is Variable DTE rate,
and should be used with the rate set at 115,200 which you have.
If you look at all the rest of the commands, you will see that they
had already been set properly in the above system init. string.
So, IMHO you have accomplished nothing with all those extra settings,
except maybe slowing down the dialing process, by initializing the
modem twice. I'd recommend removing all your Extra Settings and
letting the modem work the way it is supposed to work.
> 01-15-2000 00:10:14.18 - Send: AT&F1&B1&D2&H1&I0&K1&M4S7=60<cr>
> 01-15-2000 00:10:14.23 - Recv: <cr><lf>OK<cr><lf>
> 01-15-2000 00:10:14.23 - Interpreted response: Ok
> 01-15-2000 00:10:14.23 - Dialing.
> 01-15-2000 00:10:14.23 - Send: ATDT;<cr>
> 01-15-2000 00:10:14.30 - Recv: ATDT;<cr>
> 01-15-2000 00:10:15.90 - Recv: <cr><lf>OK<cr><lf>
> 01-15-2000 00:10:15.90 - Interpreted response: Ok
> 01-15-2000 00:10:15.90 - Dialing.
> 01-15-2000 00:10:15.90 - Send: ATDT*##,###########,,,<cr>
> 01-15-2000 00:10:15.91 - Recv: ATDT*70,12163771020,,,<cr>
Here you have added three commas after the number. All this does
is delay the start of handshaking, when the distant modem answers
in less than 6 seconds. IMHO, those are not necessary since most
ISP modems connect immediately, even on LD calls as above.
> 01-15-2000 00:10:40.81 - Recv: <cr><lf>CONNECT
> 50666/ARQ/V90/LAPM/V42BIS<cr><lf>
> 01-15-2000 00:10:40.81 - Interpreted response: Connect
> 01-15-2000 00:10:40.81 - Connection established at 50666bps.
> 01-15-2000 00:10:40.81 - Error-control on.
> 01-15-2000 00:10:40.81 - Data compression on.
That's a good connection, but I have a hunch it would be the same
without anything in the Extra Settings box. Good luck.
Hooda Gest
Art Jackson wrote in message <38809602...@mindspring.com>...
>Jack Carrigan wrote:
[trimmed]
>
>Everything looks perfectly normal up to this point, where you have
>entered in DUN's Extra settings, a lengthy init string that basically
>wipes out the first properly entered string, then resets most of them
>to the same value. The AT&F1 resets everything to factory defaults,
>that results in E1 being turned on again, which is why you see the
>dialed number being echoed from the modem. The other exception is
>&B1 which sets a fixed DTE rate, the default is Variable DTE rate,
>and should be used with the rate set at 115,200 which you have.
>If you look at all the rest of the commands, you will see that they
>had already been set properly in the above system init. string.
>So, IMHO you have accomplished nothing with all those extra settings,
>except maybe slowing down the dialing process, by initializing the
>modem twice. I'd recommend removing all your Extra Settings and
>letting the modem work the way it is supposed to work.
Good advice, Art. Only thing I can say is that you have the &Bn default
incorrect for &F1. The default is fixed DTE rate and that is &B1.
And you are definitely correct about the unnecessary string in the Extra
settings.
I'd like to see an ati6i11 after a session online of 15 or more minutes but
if he's happy with the performance, there's no real need.
Hooda
Jack Carrigan
Thanks for explaining to me about the extra strings I added, & what
they were doing, precisely. I will remove them. In my original post,
however, I stated that sometimes I have to try to connect like 3-4
times without success, which is what led me to try the commas & inits
in the first place. It seems that if I have the commas I only have to
attempt 2 times, or connect the first try. Is there any reason that
would be so? Is there anything in the default string that would cause
me to have intermitent connect troubles? Or, on the other hand, is
this a pretty normal thing for faster connecting modems? Just
something I have to live with? <I don't really mind; as I said, I
don't ever get disconnected or dropped, & have the fastest download
speed I've ever had anywhere, so occaisionally having to retry to
connect doesn't seem too terrible a price to pay, I'm just wondering
if theres anything I can tinker with & not have the trouble at all?>
On Sat, 15 Jan 2000 15:45:06 +0000, Art Jackson
<artj...@mindspring.com> wrote:
>Here you have added three commas after the number. All this does
>is delay the start of handshaking, when the distant modem answers
>in less than 6 seconds. IMHO, those are not necessary since most
>ISP modems connect immediately, even on LD calls as above.
>That's a good connection, but I have a hunch it would be the same
R Collins
"Art Jackson" <artj...@mindspring.com> wrote in message
news:38809602...@mindspring.com...
> Everything looks perfectly normal up to this point, where you have
> entered in DUN's Extra settings, a lengthy init string that
basically
> wipes out the first properly entered string, then resets most of
them
> to the same value. The AT&F1 resets everything to factory defaults,
> that results in E1 being turned on again, which is why you see the
> dialed number being echoed from the modem. The other exception is
> &B1 which sets a fixed DTE rate, the default is Variable DTE rate,
> and should be used with the rate set at 115,200 which you have.
Absolutely not. The _default_ is &B1, which sets a _fixed_ port rate.
Jack Carrigan
you the results. I do not think I ever get speed drops, or anything
like that, & would really like to know how to check.....I assume from
reading the other posts, you speak of connecting w hyperterminal <or
something similar>, & somehow getting a numeric value for line
quality? I use win98 at home, so If you could either post or email me
with instructions, I would really appreciate the help......I have
learned more in 2 days by reading this NG than 2 months of trying to
find this info on my own. <Which either says a LOT for you guys, or
not much for me, I am not sure> <g>. Thanks to all!!!
Jack
On Sat, 15 Jan 2000 12:32:55 -0500, "Hooda Gest" <be@one_with.com>
wrote:
Hooda Gest
Jack Carrigan wrote in message <3880f827...@news.nls.net>...
>If you would let me know how to do this, I would gladly do it & send
>you the results. I do not think I ever get speed drops, or anything
>like that, & would really like to know how to check.....I assume from
>reading the other posts, you speak of connecting w hyperterminal <or
>something similar>, & somehow getting a numeric value for line
>quality? I use win98 at home, so If you could either post or email me
>with instructions, I would really appreciate the help......I have
>learned more in 2 days by reading this NG than 2 months of trying to
>find this info on my own. <Which either says a LOT for you guys, or
>not much for me, I am not sure> <g>. Thanks to all!!!
>Jack
The USR/3Com modems don't provide a line quality value but do provide a lot
of information about the line quality in other ways.
Incidently, if the extra commas help you connect, go ahead and leave them
in... they won't cause you any harm.
Ok, prepare for boilerplate.... :)
Before you begin, go into Control Panel, open Modems and click on Properties
for your modem. Note the Com port used by your modem.
Open Hyperterminal, you will be prompted to create a New connection. If not,
select that from File. Provide a name for the connection (any name will do,
I use direct<port#> as in direct2) and select or accept an icon for the
connection. Next, you will be prompted for "Connect to" info; click on the
down arrow icon to the right of the modem name and select the port your
modem is emulating or is connected to. Click OK and you will be prompted for
port settings; you only need to increase the speed to 115200 (and that is
actually optional). Click OK and you are done. You can now talk to your
modem. You will not see your own commands being typed until you turn the
local echo on with E1 (as in ATE1). Save the connection info when you leave
and it will always be available.
Optional part begins...
You can create a shortcut to Hyperterminal which will automatically open
this connection when you click on it by going into the Hyperterm dir
(C:\Program Files\Accessories\HyperTerminal) and dragging the direct2.ht (or
whatever name you gave it)icon to the desktop. When you click on that
shortcut, Hyperterminal will automatically start up that connection and you
will ready to send commands to the modem.
The above will provide you with a way to query the modem after disconnects.
Hyperterminal allows you to copy data so you can paste it into a file. Then
you can insert (not attach) the file into a post.
Hooda
R Collins
You have to create a "direct to port" connection in Hyperterm. Open
Hyperterm. Select "New connection". Enter a name for it (Direct, for
example) and select an Icon. In the next dialogue, open the "Connect
Using" menu and select "Direct to Port <whatever>" - select the port
number your modem is connected to.
When you use that connection you will be placed in a terminal screen
where you can enter commands direct to the modem. Type ATE1 and press
<Enter>. This just ensures that the modem will echo the commands you
send so you can see them. You may not see the command as you enter
it. The modem will respond with "OK". From that point on, any
commands you type will appear on the screen.
To get what Hooda wants, type AT I6 I11 Y11 and press <Enter> _after_
you have disconnected from a browser session. The modem will display
the results of the last connection.
"Jack Carrigan" <jo...@nls.net> wrote in message
news:3880f827...@news.nls.net...
> If you would let me know how to do this, I would gladly do it & send
> you the results. I do not think I ever get speed drops, or anything
> like that, & would really like to know how to check.....I assume
from
> reading the other posts, you speak of connecting w hyperterminal <or
> something similar>, & somehow getting a numeric value for line
> quality? I use win98 at home, so If you could either post or email
me
> with instructions, I would really appreciate the help......I have
> learned more in 2 days by reading this NG than 2 months of trying to
> find this info on my own. <Which either says a LOT for you guys, or
> not much for me, I am not sure> <g>. Thanks to all!!!
> Jack
>
>
Art Jackson
You are correct. My bad. Anyway it's not needed in Extra Settings.
Jack Carrigan
wrote:
>The above will provide you with a way to query the modem after disconnects.
>Hyperterminal allows you to copy data so you can paste it into a file. Then
>you can insert (not attach) the file into a post.
I followed your instructions, & here are the results:
OK
AT I6 I11 Y11
U.S. Robotics 56K Win INT Link Diagnostics...
Chars sent 290 Chars Received 390
Chars lost 0
Octets sent 284008 Octets Received 489960
Blocks sent 5056 Blocks Received 5593
Blocks resent 7
Retrains Requested 0 Retrains Granted 0
REJs Received 1 Blers 7
Link Timeouts 1 Link Naks 1
Data Compression V42BIS 1024/32
Equalization Long
Fallback Enabled
Protocol LAPM
Speed 50666/31200
Last Call 00:22:20
Disconnect Reason is DTR dropped
U.S. Robotics 56K Win INT Link Diagnostics...
Modulation V.90
Carrier Freq (Hz) 1920/1920
Symbol Rate 8000/3200
Trellis Code OFF/64S-4D
Nonlinear Encoding ON/ON
Precoding ON/ON
Shaping ON/ON
Preemphasis (-dB) 2/6
Recv/Xmit Level (-dBm) 11/10
SNR (dB) 12747
Near Echo Loss (dB) 8
Far Echo Loss (dB) 78
Roundtrip Delay (msec) 19
Status uu,0,0N,0.0,-0,0N,0,0.0,0.0
Freq Level (dB)
300 27
450 25
600 20
750 3852
900 3137
1050 12741
1200 0
1350 24
1500 24
1650 24
1800 24
1950 24
2100 24
2250 24
2400 25
2550 25
2700 25
2850 25
3000 25
3150 25
3300 25
3450 25
3600 26
3750 29
OK
Now, what I wonder is this: Is there anything that you can see here
that could cause me to not be allowed to connect when I first attempt
about 1/4 of the time?
Also, (I am guessing here, but would like to hear some expert
opinions) I must have a pretty darned clean line, is this a correct
assumption? Are the 2 digit numbers at the end of the diagnostic
routine NOT related to line quality? Does anyone know a place online
where an output like the above would be broken down & explained, in
any sort of detail?
Also, I would like to thank both Hooda & R Collins for taking a look
at my posts, replying, & really helping a new guy understand just what
all these modem commands mean, & how init strings work.
Thank you both!
BTW, is there a posted FAQ for this NG anywhere?
Jack
Hooda Gest
Jack Carrigan wrote in message <38843450...@news.nls.net>...
You have a Dell (or some other vendor) provided OEM version of the USR
modem, don't you?
The line appears to be fairly good, by the way. You would do better if you
could limit the upper speed to 48000 or 49333 but, if it's a Dell unit, the
commands to do that won't work.
Try them anyway... place &U6&N32 in the Extra settings. This will limit the
top end to 48000.
It should help the modem connect and reduce errors to a very small number or
eliminate them altogether.... if it works.
>Now, what I wonder is this: Is there anything that you can see here
>that could cause me to not be allowed to connect when I first attempt
>about 1/4 of the time?
>
>Also, (I am guessing here, but would like to hear some expert
>opinions) I must have a pretty darned clean line, is this a correct
>assumption? Are the 2 digit numbers at the end of the diagnostic
>routine NOT related to line quality? Does anyone know a place online
>where an output like the above would be broken down & explained, in
>any sort of detail?
The 2 digit numbers you are refering to are the ones from the Status line?
Or the ones from the Freq and level table?
They're all related to line quality in one way or another.
Go to http://808hi.com/56k/diag3com.htm for a fairly good explanation of
the 3Com/USR diagnostic screens.
Hooda
>BTW, is there a posted FAQ for this NG anywhere?
No, no FAQ but there are several modem help sites which you will find
mentioned from time ot time.
Hooda
Hooda Gest
Jack Carrigan wrote in message <38860dda...@news.nls.net>...
>Well, I don't get it, Hooda....you are right, when I go into
>diagnostics, there is a mention of "Dell" in the list of
>AT....things.(I don't know the name of what I am looking at there) I
>do not know how this happened. I bought a 56k Sportster in a USR box
>in Feb 98 from a store, then flashed it to V.90 using the wizard from
>the following link:
>http://www.3com.com/56k/usr/upgrade/muw.html a few months ago.
Query the modem with ati7 and look at the product ID number (it may not be
there but look for it).
You should see something like this:
ati7
Configuration Profile...
Product type US/Canada External
Product ID: 00178600
Options V32bis,V.34+,x2,V.90
Fax Options Class 1/Class 2.0
Line Options Caller ID, Distinctive Ring
Clock Freq 92.0Mhz
Eprom 256k
Ram 32k
EPROM date 5/26/98
DSP date 5/26/98
EPROM rev 4.6.6
DSP rev 4.6.6
OK
... as you can see, the product ID is 00178600 for this unit. The first 2
zeros are important in determining whther this is an OEM or normal USR
product. If they are zeros then it is not an OEM unit.
>Now, You were ALSO correct in saying that the &U#&N# commands would
>not work. Is there any way that I could fix this, through use of
>different .inf files, or anything like that? Why do these standard
>3com speed-limiting commands no longer work?
Because of the firmware, not because of any hardware problems. If you
upgraded via USR's MUW then you might raise a little heck with USR/3Com
about the fact that the &Un&Nn commands do not function properly.
The INF files have no control over the AT command usage. The INF file is
simply a text file with data that is used by DUN to establish an init string
and to interpret responses from the modem.
>Thanks for sharing your knowledge again, & thanks for all the help.
>The way I figure it, somewhere in the standard init string, there is a
>bottom limit already set, & those rare times that I don't get
>connected on the first try, It means that I was not going to get that
>speed.....does that stand to logic? The thing is, when I look in the
>string being sent, I do not see the &U#&N# in there, so it must be
>using a different set of commands....does that sound right, also? I
>wonder where I could find the set of commands that WOULD work?
There are defaults for all command parameters and these are part of the
standard factory defaults (&F1 in your modem). The defaults for both &U and
&N is zero which equates to "Lowest link speed" and "Highest link speed",
respectively. They work as a pair to set an operating range. Used
separately, they function differently and almost unpredictably.
Here's what the manual says:
&Nn Sets connect speed. If connection
cannot be made at this speed, the
modem will hang up. When used in
conjunction with &Un and &Un is
greater than 0, &Nn sets the
ceiling connect speed. &Un sets
the floor connect speed (See also
the table in the &Un section.)
&Un Sets floor connect speed when set
above 0. If the connection cannot
be established above this speed,
the modem will hang up. When
&Un is used in conjunction with
&Nn and &Nn is greater than 0,
&Nn is the ceiling connect speed.
It's a little cryptic...
Hooda
>On Sun, 16 Jan 2000 09:12:54 -0500, "Hooda Gest" <be@one_with.com>
>wrote:
>
>
Jack Carrigan
diagnostics, there is a mention of "Dell" in the list of
AT....things.(I don't know the name of what I am looking at there) I
do not know how this happened. I bought a 56k Sportster in a USR box
in Feb 98 from a store, then flashed it to V.90 using the wizard from
the following link:
http://www.3com.com/56k/usr/upgrade/muw.html a few months ago.
not work. Is there any way that I could fix this, through use of
different .inf files, or anything like that? Why do these standard
3com speed-limiting commands no longer work?
The way I figure it, somewhere in the standard init string, there is a
bottom limit already set, & those rare times that I don't get
connected on the first try, It means that I was not going to get that
speed.....does that stand to logic? The thing is, when I look in the
string being sent, I do not see the &U#&N# in there, so it must be
using a different set of commands....does that sound right, also? I
wonder where I could find the set of commands that WOULD work?
On Sun, 16 Jan 2000 09:12:54 -0500, "Hooda Gest" <be@one_with.com>
Jack Carrigan
quite evident.
OK
ati7
Configuration Profile...
Product type US/Canada Internal
Product ID: 00178300
Options V32bis,V.34+,X2,V.90
Fax Options Class 1/Class 2.0
Line Options Distinctive Ring,Caller ID
DSP Freq 46.0Mhz
DSP Ram 32k
VXD date 04/09/98
VXD rev 2.60.003
OK
What should I do with this information? should I be pissed at 3com? I
absolutely DID get this firmware update through their site. I have
recently re-ran the MUW, & there is no more current update, it says I
am using the most current. This really surprises me, because I have
had nothing but success with their products. I bought them for my
family, as well as also recommending them to the customers of the ISP
I work for. I really wouldn't have thought they would advertise &
promote an update that disables portions of the modems capabilities.
Maybe it should not surprise me, but it does.
On a personal note, is there any way I could get you to send me an
email, so that I might ask you a few questions as they occur to me? I
am doing tech support for an all NT ISP using all digital V.90
Portmaster <Lucent> modem racks, & am really trying to learn
everything I can about modems & phone lines, their commands &
limitations. You seem to know quite a bit about this subject, as I
have been reading your posts for about a week now, & you have had the
correct answer in every response of yours that I have seen.I'm
actually cataloging your posts <g>. I've been doing support for about
6 months now, & there is a distinct lack of real hard knowledge among
the techs as far as modems, their commands, & the problem solving that
I see you do here every day. I would appreciate your trust & keep your
address confidential, of course. I'd also like to know how you come by
this knowledge. According to the posts I've read to this point, it was
all by reading the Manuals that used to come along with every new
modem, so I have spent the day today (while not answering calls)
tracking down manuals for the most popular modems that I run across in
my daily wanderings.
Anyway, let me know what you would do if you were in my situation, if
you wouldn't mind. I LOVE the performance of these V.90 3com modems,
but it'd be nice to be able to use the commands as they were
originally intended, just to tweak things a bit, so as to make
everything run as smoothly as I can, both for myself & for our
customers. Thanks, in advance.
Jack Carrigan
On Tue, 18 Jan 2000 20:52:33 -0500, "Hooda Gest" <be@one_with.com>
wrote:
>Query the modem with ati7 and look at the product ID number (it may not be
>there but look for it).
>
>... as you can see, the product ID is 00178600 for this unit. The first 2
>zeros are important in determining whther this is an OEM or normal USR
>product. If they are zeros then it is not an OEM unit.
>Because of the firmware, not because of any hardware problems. If you
Hooda Gest
Jack Carrigan wrote in message <3885230...@news.nls.net>...
>Here is the result of the query ati7. As you can see, the 2 zeros are
>quite evident.
>
>OK
>ati7
>Configuration Profile...
>
>Product type US/Canada Internal
>Product ID: 00178300
>Options V32bis,V.34+,X2,V.90
>Fax Options Class 1/Class 2.0
>Line Options Distinctive Ring,Caller ID
>DSP Freq 46.0Mhz
>DSP Ram 32k
>
>VXD date 04/09/98
>VXD rev 2.60.003
>
>OK
>
>What should I do with this information? should I be pissed at 3com? I
Yes, you should. This is what I would do...
I would use Hyperterminal to perform the following steps and collect the
data (record it all):
1. Reset the modem with at&f1
2. Send the modem ati4 to get the configuration.
3. Dial up your ISP using ATDT.... (don't log in)
4. Drop to command mode and issue an ati6
5. Disconnect if the modem has not been disconnected.
6. Reset the modem with at&f1
7. Send at&u6&n30
8. Perform steps 2, 3, and 4 again.
Contact 3Com, explain that the command does not work and you need to be able
to limit the top speed in order to get consistent connections and maintain a
stable one after connecting. Tell them the firmware is faulty, does not work
as it is supposed to, and you want it fixed or your money back so you can
buy a modem that does work properly. Offer them the data you collected.
>absolutely DID get this firmware update through their site. I have
>recently re-ran the MUW, & there is no more current update, it says I
>am using the most current. This really surprises me, because I have
>had nothing but success with their products. I bought them for my
>family, as well as also recommending them to the customers of the ISP
>I work for. I really wouldn't have thought they would advertise &
>promote an update that disables portions of the modems capabilities.
>Maybe it should not surprise me, but it does.
>
Thank you for telling me about this. I thought this was limited to Dell
versions but it appears that it isn't.
>On a personal note, is there any way I could get you to send me an
>email, so that I might ask you a few questions as they occur to me? I
Let me think about it. I value my privacy.
>am doing tech support for an all NT ISP using all digital V.90
>Portmaster <Lucent> modem racks, & am really trying to learn
>everything I can about modems & phone lines, their commands &
>limitations. You seem to know quite a bit about this subject, as I
>have been reading your posts for about a week now, & you have had the
>correct answer in every response of yours that I have seen.I'm
I am not familar with Portmasters nor any of the rack systems. Mostly what I
know has come from working with the modems, digging into web sites, and
reading the suggestions by some other very good people who post here (Rick
Collins, Chris Bolus, John Navas, Art Jackson, Bob Starnes, and others).
There are some good web sites out there which you may find helpful. I don't
have the list here with me (my home computer has most of my links) but
www.808hi.com/56k (for diagnosing and working around problems) and
www.56k.com for links to modem makers and manuals are two I use very
heavily.
>actually cataloging your posts <g>. I've been doing support for about
>6 months now, & there is a distinct lack of real hard knowledge among
>the techs as far as modems, their commands, & the problem solving that
>I see you do here every day. I would appreciate your trust & keep your
>address confidential, of course. I'd also like to know how you come by
>this knowledge. According to the posts I've read to this point, it was
>all by reading the Manuals that used to come along with every new
>modem, so I have spent the day today (while not answering calls)
>tracking down manuals for the most popular modems that I run across in
>my daily wanderings.
You've got it right about how I picked up the knowledge. In fact, you are
doing exactly what I did in the past and continue to do. I got an interest
in modems back in the late 70's when I had to hook up old Bell 202 modems
and make these circuits work as intended (always possible but usually not
the way the engineers laid out the circuit). Then I got a computer and
started dialing up BBS's in the 80's. By the end of the 80's, I was running
my own BBS and doing what I could to help people get their modems working
efficiently. Pretty much part of your job, I suspect. You'll learn best by
doing. That is, you pick up knowledge along the way, you make suggestions
that help and you get some feedback as to what worked and what didn't. If
your memory is good, you'll have on tap. If it isn't, make notes. :)
>Anyway, let me know what you would do if you were in my situation, if
>you wouldn't mind. I LOVE the performance of these V.90 3com modems,
>but it'd be nice to be able to use the commands as they were
>originally intended, just to tweak things a bit, so as to make
>everything run as smoothly as I can, both for myself & for our
>customers. Thanks, in advance.
I agree. I have a newer Winmodem (5683001) that works great. It actually
works better than an upgraded Courier that I have. The commands work
properly in this unit (as they do in the Courier and the Sportster I own) so
they should work in all versions. I limit my Sporter and Courier to 49333bps
at home and the Winmodem to 45333 at work. I'd have lots of problems if I
couldn't do this.
Let me know how things turn out with 3Com.
Hooda
Jack Carrigan
question: To whom to send the data? I was looking through 3coms site
tonight & do not seem to be able to locate an email address that
anyone other than a list-server will read....which maybe wouldn't help
my situation as much as I'd like <g>. Maybe I'll just call them, & ask
them who would like to see the data I've collected. Anyway, thanks
again for all you have been doing for me, & know that it's really
appreciated.
Jack
On Wed, 19 Jan 2000 09:21:20 -0500, "Hooda Gest" <be@one_with.com>
wrote:
Hooda Gest
Jack Carrigan wrote in message <38889aff...@news.nls.net>...
>Thanks a TON, Hooda. I will collect the data tonight. Now, the $65,000
>question: To whom to send the data? I was looking through 3coms site
>tonight & do not seem to be able to locate an email address that
>anyone other than a list-server will read....which maybe wouldn't help
>my situation as much as I'd like <g>. Maybe I'll just call them, & ask
>them who would like to see the data I've collected. Anyway, thanks
>again for all you have been doing for me, & know that it's really
>appreciated.
>Jack
>
http://www.3com.com/util/contact.html
You will probably get a canned response. I have seen reports that putting
"0000" in the Subject line will kick the email to a human and get you a real
response but cannot confirm this.
I would send the email to more than 1 department (you may choose a
department on that page) and I might consider calling the Sales number since
that's a toll free number.
Hooda
Jack Carrigan
commands as in at&u6&n30 it got a response, not an error message,
which is what happened before.(I had omitted the "at" at the
beginning) BUT, then a really strange thing happened. The modem
thought the com port was still open. even after rebooting, shutting
down for 10 minutes & everything. SO, I unplugged the box & let it sit
overnight. When I checked this morning, all was right again, but I
removed the string because that's what I was doing when everything
went freaky. can you think of any reason why this should happen?I know
I must have done something wrong, but don't know what it was.... here
was the procedure:
1: logoff my connection to my isp
2: open the direct link to port 2 using hyperterminal
3: at&f1 to reset
4: atdt <number for isp> get connected, but don't log in
5: at that point it just kept asking for a login, so I disconnected by
button at top of screen
6: again at&f1 to reset
7: at&u6&n30
8: atdt <number for isp> got connected at specified speed, figured all
was well.
9: logged off hyperterminal
10: entered at&u6&n30 in extra settings
11: it was at that point that everything got funky, & the modem would
no longer dial out. I tryed rebooting, shutting down, shutting down
for extended time, & still the modem wouldn't dial out, so I removed
the string from the extra settings, unplugged & went to bed. In the
morning, everyuthing was correct again.
I know somewhere in there I must've done something incorrectly, & I
think it was where after I initially dialed the isp, I was supposed to
"Drop to command mode and issue an ati6" I guess I wasn't sure how to
do this, since I was still connected to my isp at the time, & it was
just looking for a login name. Think you could straighten out this
mess I made? Sorry for the blunder on the "at" at the beginning of the
&u6&n30, but I had not known that it was supposed to go in there at
the time......
Jack
On Thu, 20 Jan 2000 09:10:06 -0500, "Hooda Gest" <be@one_with.com>
wrote:
Hooda Gest
Jack Carrigan wrote in message <3888dbbc...@news.nls.net>...
>Hooda, I think I goofed. When I did hyperterminal & cut & pasted your
>commands as in at&u6&n30 it got a response, not an error message,
>which is what happened before.(I had omitted the "at" at the
>beginning) BUT, then a really strange thing happened. The modem
>thought the com port was still open. even after rebooting, shutting
>down for 10 minutes & everything. SO, I unplugged the box & let it sit
>overnight. When I checked this morning, all was right again, but I
>removed the string because that's what I was doing when everything
>went freaky. can you think of any reason why this should happen?I know
>I must have done something wrong, but don't know what it was.... here
Ever think that Murphy is following you around? :)
>was the procedure:
>1: logoff my connection to my isp
>2: open the direct link to port 2 using hyperterminal
>3: at&f1 to reset
>4: atdt <number for isp> get connected, but don't log in
>5: at that point it just kept asking for a login, so I disconnected by
>button at top of screen
>6: again at&f1 to reset
>7: at&u6&n30
>8: atdt <number for isp> got connected at specified speed, figured all
>was well.
>9: logged off hyperterminal
Everything was fine to this point.
>10: entered at&u6&n30 in extra settings
>11: it was at that point that everything got funky, & the modem would
>no longer dial out. I tryed rebooting, shutting down, shutting down
>for extended time, & still the modem wouldn't dial out, so I removed
>the string from the extra settings, unplugged & went to bed. In the
>morning, everyuthing was correct again.
I can't think of a reason why things went strange on you here. You don't
need the "at" on the string you place in the Extra settings since DUN will
add the "at" automatically. That may have confused things but it really
shouldn't have. Examining your modem log might have offered a clue as to why
the modem wasn't dialing. If it got an ERROR response, for instance, that
will screw things up.
>I know somewhere in there I must've done something incorrectly, & I
>think it was where after I initially dialed the isp, I was supposed to
>"Drop to command mode and issue an ati6" I guess I wasn't sure how to
>do this, since I was still connected to my isp at the time, & it was
>just looking for a login name. Think you could straighten out this
>mess I made? Sorry for the blunder on the "at" at the beginning of the
>&u6&n30, but I had not known that it was supposed to go in there at
>the time......
To drop to command mode, all you need to do is pause for a second, type +++
and pause again for a second. You should then see an "OK" but you may also
see a "NO CARRIER" because some ISPs drop carrier when they see the triple +
come in as a security measure.
But you did everything right in testing the command. I would probably try
several different &n values to make sure it wasn't a fluke that the modem
used the command properly but that's probably a little overkill.
Hooda
Jack Carrigan
information just this week, & I really appreciate it. You never once
made me feel like an idiot for not knowing the answer, & I appreciate
that also....I think it's really cool you even bother to do this kind
of thing here.....it's not like you're getting paid, so...
Thanks!
Jack
On Fri, 21 Jan 2000 08:47:09 -0500, "Hooda Gest" <be@one_with.com>
wrote:
>But you did everything right in testing the command. I would probably try
Hooda Gest
Look at it this way...
You didn't act as if you knew it all.
You didn't automatically blame the modem (or an ISP or the telco).
You asked good questions (I do believe there are such things as stupid
questions).
You never got angry or defensive.
And, of course, you buttered me up every chance you got.
How could I not try to help? :)
Hooda
Jack Carrigan wrote in message <3888a9d6...@news.nls.net>...
Jack Carrigan
someone does you a good turn. I TRY to do a bit of learning on my own
before I start peppering ppl with questions like "You mean you have to
be connected to transmit email?". & I believe heartily in praising
those who hold out a hand to help someone else. What you call
buttering up, I call respect & good manners.
On Fri, 21 Jan 2000 14:17:19 -0500, "Hooda Gest" <be@one_with.com>
wrote:
>
Jack Carrigan
wrote:
>Ever think that Murphy is following you around? :)
I sometimes think Eddie is there, yes <G>
>I can't think of a reason why things went strange on you here. You don't
>need the "at" on the string you place in the Extra settings since DUN will
>add the "at" automatically. That may have confused things but it really
>shouldn't have. Examining your modem log might have offered a clue as to why
>the modem wasn't dialing. If it got an ERROR response, for instance, that
>will screw things up.
here is a cut a paste of a bit of the modem log, w me using various
&u#&n# values. Every time I tried one of these, I got the wondows
error message that the port was already open.....things are a little
screwy here in Modemville, aint they, Sheriff? :P
01-21-2000 18:30:38.48 - U.S. Robotics 56K Win INT in use.
01-21-2000 18:30:38.51 - Modem type: U.S. Robotics 56K Win INT
01-21-2000 18:30:38.51 - Modem inf path: WINMODEM.INF
01-21-2000 18:30:38.51 - Modem inf section: Winmodem
01-21-2000 18:30:38.51 - 115200,N,8,1
01-21-2000 18:30:38.51 - 115200,N,8,1
01-21-2000 18:30:38.51 - Initializing modem.
01-21-2000 18:30:38.51 - Send: AT<cr>
01-21-2000 18:30:38.57 - Recv: AT<cr>
01-21-2000 18:30:38.57 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:30:38.57 - Interpreted response: Ok
01-21-2000 18:30:38.57 - Send: AT&F1E0V1&C1&D2S0=0<cr>
01-21-2000 18:30:38.62 - Recv: AT&F1E0V1&C1&D2S0=0<cr>
01-21-2000 18:30:38.62 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:30:38.62 - Interpreted response: Ok
01-21-2000 18:30:38.62 - Send: ATS7=60S19=0L3M1&M4&K1&H1&R2&I0B0X4<cr>
01-21-2000 18:30:38.67 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:30:38.67 - Interpreted response: Ok
01-21-2000 18:30:38.67 - Send: at&u6&n33<cr>
01-21-2000 18:30:38.72 - Recv: <cr><lf>ERROR<cr><lf>
01-21-2000 18:30:38.72 - Interpreted response: Error
01-21-2000 18:30:38.72 - Hanging up the modem.
01-21-2000 18:30:55.23 - Session Statistics:
01-21-2000 18:30:55.23 - Reads : 50 bytes
01-21-2000 18:30:55.23 - Writes: 69 bytes
01-21-2000 18:30:55.23 - U.S. Robotics 56K Win INT closed.
01-21-2000 18:32:55.43 - U.S. Robotics 56K Win INT in use.
01-21-2000 18:32:55.46 - Modem type: U.S. Robotics 56K Win INT
01-21-2000 18:32:55.46 - Modem inf path: WINMODEM.INF
01-21-2000 18:32:55.46 - Modem inf section: Winmodem
01-21-2000 18:32:55.46 - 115200,N,8,1
01-21-2000 18:32:55.46 - 115200,N,8,1
01-21-2000 18:32:55.46 - Initializing modem.
01-21-2000 18:32:55.46 - Send: AT<cr>
01-21-2000 18:32:55.48 - Recv: AT<cr>
01-21-2000 18:32:55.48 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:32:55.48 - Interpreted response: Ok
01-21-2000 18:32:55.48 - Send: AT&F1E0V1&C1&D2S0=0<cr>
01-21-2000 18:32:55.53 - Recv: AT&F1E0V1&C1&D2S0=0<cr>
01-21-2000 18:32:55.53 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:32:55.53 - Interpreted response: Ok
01-21-2000 18:32:55.53 - Send: ATS7=60S19=0L3M1&M4&K1&H1&R2&I0B0X4<cr>
01-21-2000 18:32:55.58 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:32:55.58 - Interpreted response: Ok
01-21-2000 18:32:55.58 - Send: at&u6&n32<cr>
01-21-2000 18:32:55.63 - Recv: <cr><lf>ERROR<cr><lf>
01-21-2000 18:32:55.63 - Interpreted response: Error
01-21-2000 18:32:55.63 - Hanging up the modem.
01-21-2000 18:35:04.12 - Initializing modem.
01-21-2000 18:35:04.12 - Send: AT<cr>
01-21-2000 18:35:04.14 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:35:04.14 - Interpreted response: Ok
01-21-2000 18:35:04.14 - Send: AT&F1E0V1&C1&D2S0=0<cr>
01-21-2000 18:35:04.19 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:35:04.19 - Interpreted response: Ok
01-21-2000 18:35:04.19 - Send: ATS7=60S19=0L3M1&M4&K1&H1&R2&I0B0X4<cr>
01-21-2000 18:35:04.24 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:35:04.24 - Interpreted response: Ok
01-21-2000 18:35:04.24 - Send: at&u6&n31<cr>
01-21-2000 18:35:04.29 - Recv: <cr><lf>ERROR<cr><lf>
01-21-2000 18:35:04.29 - Interpreted response: Error
01-21-2000 18:35:04.29 - ERROR: Dial failed.
01-21-2000 18:35:04.29 - Hanging up the modem.
01-21-2000 18:35:19.15 - Session Statistics:
01-21-2000 18:35:19.15 - Reads : 77 bytes
01-21-2000 18:35:19.15 - Writes: 138 bytes
01-21-2000 18:35:19.15 - U.S. Robotics 56K Win INT closed.
01-21-2000 18:38:45.83 - U.S. Robotics 56K Win INT in use.
01-21-2000 18:38:45.86 - Modem type: U.S. Robotics 56K Win INT
01-21-2000 18:38:45.86 - Modem inf path: WINMODEM.INF
01-21-2000 18:38:45.86 - Modem inf section: Winmodem
01-21-2000 18:38:45.86 - 115200,N,8,1
01-21-2000 18:38:45.86 - 115200,N,8,1
01-21-2000 18:38:45.86 - Initializing modem.
01-21-2000 18:38:45.86 - Send: AT<cr>
01-21-2000 18:38:45.92 - Recv: AT<cr>
01-21-2000 18:38:45.92 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:38:45.92 - Interpreted response: Ok
01-21-2000 18:38:45.92 - Send: AT&F1E0V1&C1&D2S0=0<cr>
01-21-2000 18:38:45.97 - Recv: AT&F1E0V1&C1&D2S0=0<cr>
01-21-2000 18:38:45.97 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:38:45.97 - Interpreted response: Ok
01-21-2000 18:38:45.97 - Send: ATS7=60S19=0L3M1&M4&K1&H1&R2&I0B0X4<cr>
01-21-2000 18:38:46.02 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:38:46.02 - Interpreted response: Ok
01-21-2000 18:38:46.02 - Send: ATE1<cr>
01-21-2000 18:38:46.07 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:38:46.07 - Interpreted response: Ok
01-21-2000 18:38:46.07 - Dialing.
01-21-2000 18:38:46.07 - Send: ATDT;<cr>
01-21-2000 18:38:46.14 - Recv: ATDT;<cr>
01-21-2000 18:38:47.55 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:38:47.55 - Interpreted response: Ok
01-21-2000 18:38:47.55 - Dialing.
01-21-2000 18:38:47.55 - Send: ATDT*##,###########<cr>
01-21-2000 18:38:47.56 - Recv: ATDT*##,###########<cr> modified to
remove dialup number
01-21-2000 18:38:48.32 - Hanging up the modem.
01-21-2000 18:38:48.32 - Send: <cr>
01-21-2000 18:38:48.36 - Recv: <cr><lf>NO CARRIER<cr><lf>
01-21-2000 18:38:48.36 - Interpreted response: No Carrier
01-21-2000 18:38:48.36 - Send: ATH<cr>
01-21-2000 18:38:48.75 - Recv: ATH<cr>
01-21-2000 18:38:48.75 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:38:48.75 - Interpreted response: Ok
01-21-2000 18:38:48.75 - 115200,N,8,1
01-21-2000 18:38:49.77 - Session Statistics:
01-21-2000 18:38:49.77 - Reads : 103 bytes
01-21-2000 18:38:49.77 - Writes: 95 bytes
01-21-2000 18:38:49.77 - U.S. Robotics 56K Win INT closed.
01-21-2000 18:39:15.91 - U.S. Robotics 56K Win INT in use.
01-21-2000 18:39:15.93 - Modem type: U.S. Robotics 56K Win INT
01-21-2000 18:39:15.93 - Modem inf path: WINMODEM.INF
01-21-2000 18:39:15.93 - Modem inf section: Winmodem
01-21-2000 18:39:15.93 - 115200,N,8,1
01-21-2000 18:39:15.94 - 115200,N,8,1
01-21-2000 18:39:15.94 - Initializing modem.
01-21-2000 18:39:15.94 - Send: AT<cr>
01-21-2000 18:39:15.99 - Recv: AT<cr>
01-21-2000 18:39:15.99 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:39:15.99 - Interpreted response: Ok
01-21-2000 18:39:15.99 - Send: AT&F1E0V1&C1&D2S0=0<cr>
01-21-2000 18:39:16.04 - Recv: AT&F1E0V1&C1&D2S0=0<cr>
01-21-2000 18:39:16.04 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:39:16.04 - Interpreted response: Ok
01-21-2000 18:39:16.04 - Send: ATS7=60S19=0L3M1&M4&K1&H1&R2&I0B0X4<cr>
01-21-2000 18:39:16.09 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:39:16.09 - Interpreted response: Ok
01-21-2000 18:39:16.09 - Send: ATE1&n33<cr>
01-21-2000 18:39:16.14 - Recv: <cr><lf>ERROR<cr><lf>
01-21-2000 18:39:16.14 - Interpreted response: Error
01-21-2000 18:39:16.14 - Hanging up the modem.
01-21-2000 18:39:35.25 - Session Statistics:
01-21-2000 18:39:35.25 - Reads : 50 bytes
01-21-2000 18:39:35.25 - Writes: 68 bytes
01-21-2000 18:39:35.25 - U.S. Robotics 56K Win INT closed.
01-21-2000 18:42:40.17 - U.S. Robotics 56K Win INT in use.
01-21-2000 18:42:40.20 - Modem type: U.S. Robotics 56K Win INT
01-21-2000 18:42:40.20 - Modem inf path: WINMODEM.INF
01-21-2000 18:42:40.20 - Modem inf section: Winmodem
01-21-2000 18:42:40.20 - 115200,N,8,1
01-21-2000 18:42:40.20 - 115200,N,8,1
01-21-2000 18:45:30.09 - Initializing modem.
01-21-2000 18:45:30.09 - Send: AT<cr>
01-21-2000 18:45:30.09 - Recv: AT<cr>
01-21-2000 18:45:30.09 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:45:30.09 - Interpreted response: Ok
01-21-2000 18:45:30.09 - Send: AT&F1E0V1&C1&D2S0=0<cr>
01-21-2000 18:45:30.14 - Recv: AT&F1E0V1&C1&D2S0=0<cr>
01-21-2000 18:45:30.14 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:45:30.14 - Interpreted response: Ok
01-21-2000 18:45:30.14 - Send: ATS7=60S19=0L3M1&M4&K1&H1&R2&I0B0X4<cr>
01-21-2000 18:45:30.19 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:45:30.19 - Interpreted response: Ok
01-21-2000 18:45:30.19 - Send: ATE1&n33<cr>
01-21-2000 18:45:30.25 - Recv: <cr><lf>ERROR<cr><lf>
01-21-2000 18:45:30.25 - Interpreted response: Error
01-21-2000 18:45:30.25 - ERROR: Dial failed.
01-21-2000 18:45:30.25 - Hanging up the modem.
01-21-2000 18:45:47.74 - Initializing modem.
01-21-2000 18:45:47.74 - Send: AT<cr>
01-21-2000 18:45:47.78 - Recv: AT<cr>
01-21-2000 18:45:47.78 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:45:47.78 - Interpreted response: Ok
01-21-2000 18:45:47.78 - Send: AT&F1E0V1&C1&D2S0=0<cr>
01-21-2000 18:45:47.83 - Recv: AT&F1E0V1&C1&D2S0=0<cr>
01-21-2000 18:45:47.83 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:45:47.83 - Interpreted response: Ok
01-21-2000 18:45:47.83 - Send: ATS7=60S19=0L3M1&M4&K1&H1&R2&I0B0X4<cr>
01-21-2000 18:45:47.89 - Recv: <cr><lf>OK<cr><lf>
01-21-2000 18:45:47.89 - Interpreted response: Ok
01-21-2000 18:45:47.89 - Send: AT&U6&N30<cr>
01-21-2000 18:45:47.94 - Recv: <cr><lf>ERROR<cr><lf>
01-21-2000 18:45:47.94 - Interpreted response: Error
01-21-2000 18:45:47.94 - ERROR: Dial failed.
01-21-2000 18:45:47.94 - Hanging up the modem.
Hooda Gest
Jack Carrigan wrote in message <38909b7d...@news.nls.net>...
>On Fri, 21 Jan 2000 08:47:09 -0500, "Hooda Gest" <be@one_with.com>
>wrote:
>
>
>>Ever think that Murphy is following you around? :)
>I sometimes think Eddie is there, yes <G>
>
>>I can't think of a reason why things went strange on you here. You don't
>>need the "at" on the string you place in the Extra settings since DUN will
>>add the "at" automatically. That may have confused things but it really
>>shouldn't have. Examining your modem log might have offered a clue as to
why
>>the modem wasn't dialing. If it got an ERROR response, for instance, that
>>will screw things up.
>
>here is a cut a paste of a bit of the modem log, w me using various
>&u#&n# values. Every time I tried one of these, I got the wondows
>error message that the port was already open.....things are a little
>screwy here in Modemville, aint they, Sheriff? :P
The command is screwing things up. Even though it shouldn't...
It's the ERROR response to the command that is causing the dialing failure.
Here's what I want you to do...
Go into Hyperterminal and set up a direct to port connection to the port the
modem uses/emulates. Then try these commands and post the results (copy and
paste).
at&$
at&u10
at&U10
at&n33
at&N33
if you need some help with establishing the direct connection to the port,
here's a guide...
Before you begin, go into Control Panel, open Modems and click on Properties
for your modem. Note the Com port used by your modem.
Open Hyperterminal, you will be prompted to create a New connection. If not,
select that from File. Provide a name for the connection (any name will do,
I use direct<port#> as in direct2) and select or accept an icon for the
connection. Next, you will be prompted for "Connect to" info; click on the
down arrow icon to the right of the modem name and select the port your
modem is emulating or is connected to. Click OK and you will be prompted for
port settings; you only need to increase the speed to 115200 (and that is
actually optional). Click OK and you are done. You can now talk to your
modem. You will not see your own commands being typed until you turn the
local echo on with E1 (as in ATE1). Save the connection info when you leave
and it will always be available.
Optional part begins...
You can create a shortcut to Hyperterminal which will automatically open
this connection when you click on it by going into the Hyperterm dir
(C:\Program Files\Accessories\HyperTerminal) and dragging the direct2.ht (or
whatever name you gave it)icon to the desktop. When you click on that
shortcut, Hyperterminal will automatically start up that connection and you
will ready to send commands to the modem.
Hooda
Hooda Gest
Jack Carrigan wrote in message <388b9268...@news.nls.net>...
>On Sun, 23 Jan 2000 16:03:02 -0500, "Hooda Gest" <be@one_with.com>
>wrote:
>
>
>>Go into Hyperterminal and set up a direct to port connection to the port
the
>>modem uses/emulates. Then try these commands and post the results (copy
and
>>paste).
>>
>>at&$
>>at&u10
>>at&U10
>>at&n33
>>at&N33
>>
>>if you need some help with establishing the direct connection to the port,
>>here's a guide...
>have the shortcut, which sure speeds things up <g>.
>Heres the input/output:
>ate1
>OK
>at&$
>HELP, Ampersand Commands (CTRL-S to Stop, CTRL-C to Cancel)
>
>&An n=0 Disable /ARQ Result Codes &Pn n=0 N.American Pulse
[trimmed]
> n=13 26400 bps n=33 Minimum link rate: 49333
bps
I did a lot of trimming so I could point out the important parts. The above
shows that there is an "n" value of 33 for &N and &U as far as the command
help in the firmware are concerned.
[trimmed]
> n=25 38666 bps &Wn n=0 Store Configuration 0
> n=26 40000 bps n=1 Store Configuration 1
> n=27 41333 bps &Yn n=0 Destructive
> n=28 42666 bps n=1 Destructive/Expedited
> n=29 44000 bps n=2 Nondest./Expedited
> n=30 45333 bps n=3 Nondest./Unexpedited
> n=31 46666 bps &Zn=s Store Phone Number
> n=32 48000 bps &Zn? Query Phone Number
>The part I found interesting was the Destructive/expidited list,
>towards the bottom.....does this mean that these values have been
>suspended, somehow?
And, if the reformatting I did holds up, this shows that the &Yn was just in
its normal place in the help lists. The help list is two columns, where the
values for &N on the left and the values for &U on the right are not lined
up with each other. But they are all there and everything looks normal as
far as the Help function is concerned.
>OK
>at&u10
>OK
>at&U10
>OK
>at&n33
>ERROR
>at&N33
>ERROR
Now here is where there's a problem. You see the ERROR responses for either
form of &N? That shows a problem in firmware. The help says the command
works, the modem refuses to recognize it.
This is a non-OEM unit, I believe? If so, or if 3Com provided the firmware
update/upgrade through the MUW then they have a problem. It's a defect. Show
them the code version, show them the inability of the modem to recognize a
legal command and see what they do.
Hooda
R Collins
> The part I found interesting was the Destructive/expidited list,
> towards the bottom.....does this mean that these values have been
> suspended, somehow?
No- that's the definition for &Y1 - Destructive, expedited.
Jack Carrigan
wrote:
>Go into Hyperterminal and set up a direct to port connection to the port the
>modem uses/emulates. Then try these commands and post the results (copy and
>paste).
>
>at&$
>at&u10
>at&U10
>at&n33
>at&N33
>
>if you need some help with establishing the direct connection to the port,
>here's a guide...
Nah, this is one of the first things you taught me how to do.....even
have the shortcut, which sure speeds things up <g>.
Heres the input/output:
ate1
OK
at&$
HELP, Ampersand Commands (CTRL-S to Stop, CTRL-C to Cancel)
&An n=0 Disable /ARQ Result Codes &Pn n=0 N.American Pulse
Dial
n=1 Enable /ARQ Result Codes n=1 UK Pulse Dial
n=2 Enable /Modulation Codes &Rn n=1 Ignore RTS
n=3 Enable /Extra Result Codes n=2 RX to DTE/RTS high
&Bn n=0 Reserved &Sn n=0 DSR Always On
n=1 Fixed DTE Speed n=1 Modem Controls DSR
n=2 Reserved &Tn n=0 End Test
&Cn n=0 CD Always On n=1 Analog Loopback
(ALB)
n=1 Modem Controls CD n=3 Digital Loopback
(DLB)
&Dn n=0 Ignore DTR n=4 Grant Remote DLB
n=1 On-Line Command Mode n=5 Deny Remote DLB
n=2 DTE Controls DTR n=6 Remote Digital
Loopback
&Fn n=0 Load Factory Configuration n=7 Remote DLB With Self
Test
n=1 Hardware Flow Control Cnfg. n=8 ALB With Self Test
n=2 Software Flow Control Cnfg. &Un n=0 Variable link rate
floor
&Gn n=0 No Guard Tone n=1 Minimum link rate:
300 bps
n=1 550 Hz Guard Tone n=2 Minimum link rate:
1200 bps
n=2 1800 Hz Guard Tone n=3 Minimum link rate:
2400 bps
&Hn n=0 Disable TX Flow Control n=4 Minimum link rate:
4800 bps
n=1 CTS n=5 Minimum link rate:
7200 bps
n=2 Xon/Xoff n=6 Minimum link rate:
9600 bps
&In n=0 Disable RX Flow Control n=7 Minimum link rate:
12000 bps
n=1 Xon/Xoff n=8 Minimum link rate:
14400 bps
n=2 Xon/Xoff Chars Filtered n=9 Minimum link rate:
16800 bps
n=3 HP Enq/Ack Host Mode n=10 Minimum link rate:
19200 bps
n=4 HP Enq/Ack Terminal Mode n=11 Minimum link rate:
21600 bps
n=5 Xon/Xoff for non-ARQ Mode n=12 Minimum link rate:
24000 bps
&Kn n=0 Disable Data Compression n=13 Minimum link rate:
26400 bps
n=1 Auto Data Compression n=14 Minimum link rate:
28800 bps
n=2 Enable Data Compression n=15 Minimum link rate:
31200 bps
n=3 Selective Data Compression n=16 Minimum link rate:
33600 bps
&Mn n=0 Normal Mode n=17 Minimum link rate:
28000 bps
n=4 ARQ/Normal Mode n=18 Minimum link rate:
29333 bps
n=5 ARQ Mode n=19 Minimum link rate:
30666 bps
&Nn n=0 Highest Link Speed n=20 Minimum link rate:
32000 bps
n=1 300 bps n=21 Minimum link rate:
33333 bps
n=2 1200 bps n=22 Minimum link rate:
34666 bps
n=3 2400 bps n=23 Minimum link rate:
36000 bps
n=4 4800 bps n=24 Minimum link rate:
37333 bps
n=5 7200 bps n=25 Minimum link rate:
38666 bps
n=6 9600 bps n=26 Minimum link rate:
40000 bps
n=7 12000 bps n=27 Minimum link rate:
41333 bps
n=8 14400 bps n=28 Minimum link rate:
42666 bps
n=9 16800 bps n=29 Minimum link rate:
44000 bps
n=10 19200 bps n=30 Minimum link rate:
45333 bps
n=11 21600 bps n=31 Minimum link rate:
46666 bps
n=12 24000 bps n=32 Minimum link rate:
48000 bps
n=13 26400 bps n=33 Minimum link rate:
49333 bps
n=14 28800 bps n=34 Minimum link rate:
50666 bps
n=15 31200 bps n=35 Minimum link rate:
52000 bps
n=16 33600 bps n=36 Minimum link rate:
53333 bps
n=17 28000 bps n=37 Minimum link rate:
54666 bps
n=18 29333 bps n=38 Minimum link rate:
56000 bps
n=19 30666 bps n=39 Minimum link rate:
57333 bps
n=20 32000 bps n=40 Minimum link rate:
58666 bps
n=21 33333 bps n=41 Minimum link rate:
60000 bps
n=22 34666 bps n=42 Minimum link rate:
61333 bps
n=23 36000 bps n=43 Minimum link rate:
62666 bps
n=24 37333 bps n=44 Minimum link rate:
64000 bps
n=25 38666 bps &Wn n=0 Store Configuration
0
n=26 40000 bps n=1 Store Configuration
1
n=27 41333 bps &Yn n=0 Destructive
n=28 42666 bps n=1
Destructive/Expedited
n=29 44000 bps n=2 Nondest./Expedited
n=30 45333 bps n=3 Nondest./Unexpedited
n=31 46666 bps &Zn=s Store Phone Number
n=32 48000 bps &Zn? Query Phone Number
n=33 49333 bps
n=34 50666 bps
n=35 52000 bps
n=36 53333 bps
n=37 54666 bps
n=38 56000 bps
n=39 57333 bps
n=40 58666 bps
n=41 60000 bps
n=42 61333 bps
n=43 62666 bps
n=44 64000 bps
OK
at&u10
OK
at&U10
OK
at&n33
ERROR
at&N33
ERROR
Jack Carrigan
wrote:
>>OK
>>at&u10
>>OK
>>at&U10
>>OK
>>at&n33
>>ERROR
>>at&N33
>>ERROR
>
>
>Now here is where there's a problem. You see the ERROR responses for either
>form of &N? That shows a problem in firmware. The help says the command
>works, the modem refuses to recognize it.
>
>This is a non-OEM unit, I believe? If so, or if 3Com provided the firmware
>update/upgrade through the MUW then they have a problem. It's a defect. Show
>them the code version, show them the inability of the modem to recognize a
>legal command and see what they do.
>
>Hooda
>
>
Thanks a ton, Hooda. I will mail sup...@3com.com (?) with cut &
pastes of the above & see what they have to say. Your help has been
invaluable.
Jack
Hooda Gest
Jack Carrigan wrote in message <388ce5ce...@news.nls.net>...
>On Sun, 23 Jan 2000 19:27:51 -0500, "Hooda Gest" <be@one_with.com>
>wrote:
>
>
>>>OK
>>>at&u10
>>>OK
>>>at&U10
>>>OK
>>>at&n33
>>>ERROR
>>>at&N33
>>>ERROR
>>
>>
either
>>form of &N? That shows a problem in firmware. The help says the command
>>works, the modem refuses to recognize it.
>>
>>This is a non-OEM unit, I believe? If so, or if 3Com provided the firmware
>>update/upgrade through the MUW then they have a problem. It's a defect.
Show
>>them the code version, show them the inability of the modem to recognize a
>>legal command and see what they do.
>>
>>Hooda
>>
>>
>Thanks a ton, Hooda. I will mail sup...@3com.com (?) with cut &
>pastes of the above & see what they have to say. Your help has been
>invaluable.
I think that's technica...@3com.com or maybe at usr.com but you can do
this through the support pages at the 3Com web site. Try putting 0000 (4
zeros) in the Subject line. It's supposed to kick things over to a live
respondent.
Hooda
>Jack
Jason Sizemore
Well, I didn't have to whine to 3com. I found a utility that'll
flashes the modem firmware as well as firmware archives. So, I have a
copy of the v.90 and original firmware of this modem.
I performed the re-flash, removed the modem, restarted Windows.
Surprize - Win98's PnP found the modem as "U.S. Robotics 56K Voice Ext
PnP" and asked for the .inf. I installed the right .inf for the modem
and connected to the internet.
The result?
PORT SPEED AGAIN!!
When I disable v.90, it displays the actual connection speed and yes,
that damned <00> is back in the logs.
However, I know what is causing DUN to record this <00>.
At the end of the negotiation and a spilt second after the speaker
goes out, the RD light blinks once quickly then the CD light comes on
and DUN logs me in. It is at the point where the RD light blinks for
that split second before connection that I believe the <00> is being
recorded by DUN.
Thus, apparently the problem I'm having is software related (perhaps
something in the registry].
I'm going to install Kermit for DOS and try to connect to my shell
account with v.90 enabled. If that RD light does not blink for that
split second, then I know the problem is related to Win98 (either DUN
or the registry) and a re-install might be in order.
Hooda and Art, what are your thoughs?
--PsychoSy--
-----------== Posted via Newsfeeds.Com, Uncensored Usenet News ==----------
http://www.newsfeeds.com The Largest Usenet Servers in the World!
------== Over 73,000 Newsgroups - Including Dedicated Binaries Servers ==-----
Hooda Gest
Jason Sizemore wrote in message <388fce61...@news.foxberry.net>...
>
>Well, I didn't have to whine to 3com. I found a utility that'll
>flashes the modem firmware as well as firmware archives. So, I have a
>copy of the v.90 and original firmware of this modem.
>
>I performed the re-flash, removed the modem, restarted Windows.
>Surprize - Win98's PnP found the modem as "U.S. Robotics 56K Voice Ext
>PnP" and asked for the .inf. I installed the right .inf for the modem
>and connected to the internet.
>
>The result?
>
>PORT SPEED AGAIN!!
>
>When I disable v.90, it displays the actual connection speed and yes,
>that damned <00> is back in the logs.
>
>However, I know what is causing DUN to record this <00>.
The modem is putting out that Null character.
>At the end of the negotiation and a spilt second after the speaker
>goes out, the RD light blinks once quickly then the CD light comes on
>and DUN logs me in. It is at the point where the RD light blinks for
>that split second before connection that I believe the <00> is being
>recorded by DUN.
>
>Thus, apparently the problem I'm having is software related (perhaps
>something in the registry].
Nope, not likely.
>I'm going to install Kermit for DOS and try to connect to my shell
>account with v.90 enabled. If that RD light does not blink for that
>split second, then I know the problem is related to Win98 (either DUN
>or the registry) and a re-install might be in order.
I don't think so. Most comm programs don't care if the modem sends a Null
character back during the Connect report. DUN cares because it reads it in
raw mode (for who knows what reason). So, DUN will "see" it and the report
will not match anything in the .INF file and you end up with the port speed
instead of the Connect speed.
If the modem works otherwise, you can just live with it. If you need to know
connect speed, keep sysmon running and watch your throughput. The actual
connect speed is not all that important anyway, it's just the speed of the
modem at the moment of connection. It can, and often does, change at any
time after that moment.
Flashing your modem with an illegal flash program can cause you a problem
when you try to get a true modem problem corrected by 3Com. They may feel
you have voided your warranty.
Hooda
Forpurpose
experience) that real techs respond to these pretty fast (24-48hrs); even if
you don't get what you need. Replacing "winmodem" in the link with "voice"
gets you to the form for the other modems.
http://consumer.3com.com/winmodem/contactus/emailsupport.htm
If there isn't room in the "explanation" section to paste your entire problem
report you should probably mention that you'd like to get an email your
attachment.
plateshutoverlock
and I'm having serious problems. First off, the modem always displays
the port speed instead of the connect speed. I've followed all the
directions at http://808hi.com to fix this problem and nothing works."
The display would be something that's controlled by the AT string that the dialing software sends to the modem as an extended (non standard) part of the command set. You have to check your modem's manual to see what that command is.
Let's assume the software sends
ATDT5551212 to dial your ISP which has the phone number 5551212
and the display command for your modem is W with 0 showing the port speed and 1 showing the actual modem speed. You would add this to the dial up command the software sends to the modem:
ATDT5551212&W1
Of course, the "W" is just an example and you need to find out what the actual display command is, as well as the exact format of the string to be sent (not all modems are the same and even the & seperator might be a different character)