XP won't recognize my US Robotics modem

[KyAriel67]

My pc was recently upgraded from W98 to XP Professional. When my IT
guy came in he did the installation. Anyway- before he upgraded me I
had a US Robotics fax modem installed on my pc and it worded great.
The only thing that has changed now is my operating system. XP doesn't
acknowledge that there is a modem connected at all. If I force the
installation when I try to do a query to the modem it can't 'talk' to
it. Any hints on what I can do to fix this?

 

[PaulM]

Have you tried Google?


http://www.google.com/search?hl=en&q=US+Robotics+fax+modem+xp+drivers

 

[Harry Ohrn]

This is not unusual. You should do a search for XP drivers for your specific
modem's brand and model. If there are no XP specific drivers try Windows
2000 drivers. Once installed you might need to reboot.

 

[Chuck]

My first inclination would be to get the "IT Guy" to come back and finish
the install properly.
That aside--
Is the modem an internal (most likely) or external one?
What is the model number?
Updated software seems to be needed. It may (usually) be obtained from USR
http://www.usr.com/support/s-windows.asp
Lists the win2K & XP compatabe models.

 

[KyAriel67]

External Modem. model 5686d. I did go to the US robotics sight and
download the drivers and even installed it. But upon 'querying' the
modem it just doesn't 'see' it. I know something is happening as the
lights flash.

The updated drivers are for 5686e but it says it's part of that so I am
at a loss for why this just isn't happening.

Yesterday I ordered an internal modem that shows being supported for
XP. So keeping my fingers crossed.

 

[Chuck]

An external modem makes things much simpler, and generally works better than
an internal one. (Assuming that the serial port works properly.) You can
use device manager install new hardware, hardware connected, select standard
56k modem from a list, and go from there if your exact modem is not listed.
USR went at least two different ways with how modems get selected.
Unfortunately, some of the modems just don't get recognized properly, due to
conflicts between the various detection methods and modem ID's. I have
patched things in the past by finding out what the modem ID string is,
searching for it in inf files, and making the necessary changes. In some
cases, USR has revised inf files available on the web site. If the 5686E has
a different ID string than the 5686D, it may not be recognized properly.
Actually, after looking at my external modem, there was a V92UPG for this
modem that changed it from a D to an E.
The 5686E modem is fully compatable, and will work properly with XP. Mine is
currently not in use, since I use a broadband connection.

I did have it installed, simply to use it to get windows fax to install and
operate properly. At the time, the install package for a brother all in one
evidently expected windows fax to be installed before it would work
properly. (a classic case of you cannot get there from here)

The below is from my modem log file. It shows the modem ID as reported to
windows, and the inf file used.

File: C:\WINDOWS\System32\tapisrv.dll, Version 5.1.2600
File: C:\WINDOWS\System32\unimdm.tsp, Version 5.1.2600
File: C:\WINDOWS\System32\unimdmat.dll, Version 5.1.2600
File: C:\WINDOWS\System32\uniplat.dll, Version 5.1.2600
File: C:\WINDOWS\System32\drivers\modem.sys, Version 5.1.2600
File: C:\WINDOWS\System32\modemui.dll, Version 5.1.2600
File: C:\WINDOWS\System32\mdminst.dll, Version 5.1.2600
Modem type: U.S. Robotics 56K FAX EXT
Modem inf path: mdmusrgl.inf
Modem inf section: ModemUSR2082
Matching hardware ID: serenum\usr2082
115200,8,N,1, ctsfl=1, rtsctl=2
Initializing modem.
AT<cr>
Recv: <cr><lf>OK<cr><lf>
Interpreted response: OK
Send: AT&F&D2V1Q0E0S0=0&C1<cr>
Recv: <cr><lf>OK<cr><lf>
Interpreted response: OK
Send: AT&A3X4&B1<cr>
Recv: <cr><lf>OK<cr><lf>
Interpreted response: OK
Send: AT&A0<cr>
Recv: <cr><lf>OK<cr><lf>
Interpreted response: OK
Send: ATS7=60S19=0M1&M4&K1&H1&R2&I0B0X4<cr>
Recv: <cr><lf>OK<cr><lf>
Interpreted response: OK
Dialing.

 

[Chuck]

An external modem makes things much simpler, and generally works better than
an internal one. (Assuming that the serial port works properly.) You can
use device manager install new hardware, hardware connected, select standard
56k modem from a list, and go from there if your exact modem is not listed.
USR went at least two different ways with how modems get selected.
Unfortunately, some of the modems just don't get recognized properly, due to
conflicts between the various detection methods and modem ID's. I have
patched things in the past by finding out what the modem ID string is,
searching for it in inf files, and making the necessary changes. In some
cases, USR has revised inf files available on the web site. If the 5686E has
a different ID string than the 5686D, it may not be recognized properly.
Actually, after looking at my external modem, there was a V92UPG for this
modem that changed it from a D to an E.
The 5686E modem is fully compatable, and will work properly with XP. Mine is
currently not in use, since I use a broadband connection.

I did have it installed, simply to use it to get windows fax to install and
operate properly. At the time, the install package for a brother all in one
evidently expected windows fax to be installed before it would work
properly. (a classic case of you cannot get there from here)