Modemsite's Forum56 - The Modem Board
Main | profile | register | search | help | Ad-free Login
Forums | USR | USR 5699 won't install - probably bad h/w    Watch  
Author Topic
gospelmidi
Tl Posts:
252

USA
Posted - 12/31/2001 10:31:17 AM  Show Profile  Email Poster  Edit Message
I haven't been able to troubleshoot this one. The modem is probably bad, but maybe you know what to do.

Shuttle 591-P, AMD K6-2/300, 64Mb, mouse on COM1/IRQ4.
The USR 5699 can use IRQ 3, 4, 5, or 7, so I disabled COM2 in the CMOS. Only IRQ3 is free.

This is on a fresh Windows install, so there were no USR Winmodem references hanging around in the Registry.
When Win95B starts, the Update Device Driver Wizard recognizes a PCI Communications Device. When I insert the 5699 driver floppy, the Wiz says, "Windows was unable to locate a driver for this device."

These files are on the 5699 driver disk:

migrate.dll 34kb 8/3/98
turbovbf.vx_ 5kb 12/29/98
Turbovcd.vx_ 10kb 12/29/98
winmodem.inf 56kb 3/12/99
winmodem.vx_ 379kb 2/25/99
wmdll.dl_ 24kb 2/25/99
wmexe.ex_ 27kb 2/25/99
wmldr.vx_ 5kb 2/25/99
wmpass.dl_ 48kb 2/25/99

I have also tried the driver with the files of 1/19/99 and files of 8/19/98 instead of 2/25/99.

In Device Manager, next to the yellow question mark, Other Devices shows a PCI Communication Device using

Interrupt Request 12
Memory Range E5018000-E501803F
Memory Range E5000000-E500FFFF

The IRQ cannot be modified, which seems strange, since the 5699 requires 3, 4, 5, or 7. The mouse is on IRQ4.

Any suggestions before I ship it to the landfill?

Edited by - gospelmidi on 12/31/01 11:31:46 AM

v.Richard
Tl Posts:
6222

USA
Posted - 12/31/2001 11:52:19 AM  Show Profile  Email Poster  Edit Message  v.Richards Homepage
Do you have any USR documentation?
The USR support site which has driver file indicates to 'follow instructions that came with modem' to install it.

What happens if you try to Add Modem w/ Have disk?

Aloha,
Richard

charles
Tl Posts:
5879

USA
Posted - 12/31/2001 12:08:23 PM  Show Profile  Email Poster  Edit Message
check and make sure the path to the floppy is correct.I could not find a readme in the drivers also.

http://www.usr.com/support/s-win/s-win-docs/56kwm_im.pdf
Edited by - charles on 12/31/01 12:10:39 PM

charles
Tl Posts:
5879

USA
Posted - 12/31/2001 12:21:39 PM  Show Profile  Email Poster  Edit Message
If you have Windows 95 Version B:
When the “Update Device Driver Wizard” screen
appears, click next
Click finish When the “Insert Disk” screen
appears, make sure you have the floppy disk inserted
into the computer’s floppy drive. Click ok
When the “Copying Files” screen appears, type A:\ in
the box and click ok
gospelmidi
Tl Posts:
252

USA
Posted - 12/31/2001 9:10:04 PM  Show Profile  Email Poster  Edit Message
Yes, that is exactly the point.

The correct driver diskette (according to USR and DriverGuide) is in the A: drive.

Windows finds a "PCI Communications Device" at startup and requests the driver diskette in drive A:. When I press Enter, the diskette drive reads for several seconds, then Windows displays a message that the driver is not on this diskette. I have tried a number of diskettes with the three available revs of the 5699 driver.

Normally, this behavior occurs when Windows has failed to install the USR Winmodem completely. Thereafter, one must run the wmregdel.exe utility to remove the USR Winmodem entries from the Registry.

But this time it occurs on a clean Windows installation, with no mention of USR in the Registry.

Bob Starnes
Tl Posts:
4360

USA
Posted - 12/31/2001 11:19:29 PM  Show Profile  Email Poster  Edit Message
Loaded the latest 4-in-1 drivers for the VIA chipset? If not that could cause problems with the modem being detected properly.
gospelmidi
Tl Posts:
252

USA
Posted - 1/1/2002 5:24:37 PM  Show Profile  Email Poster  Edit Message
http://www.viahardware.com/download/index.shtm#4in1
has the VIA 4-n-1 driver 4.36. I'll give it a try.
pauldog
Tl Posts:
231

USA
Posted - 1/4/2002 1:26:05 AM  Show Profile  Email Poster  Edit Message  pauldogs Homepage
Make sure you're using the driver corresponding to your Winmodem model number. Presumably, the most recent one would be the best, but I certainly can't guarantee that!

There is no special significance in putting the driver on a floppy. It can be in a folder on your hard drive. You can use "Browse" to point the installer to the folder.

If the driver file you download is self-installing, try doing it that way (double-clicking), rather than using the "Add Modem" option (Modems control panel) or clicking "Refresh" in the Device Manager (System control panel).

And the above paragraph has another hint - "Refresh" can act differently from "Add Modem."

By now, you may have a partial installation going, and may need to run WMREGDEL before trying to install again.

pauldog
Tl Posts:
231

USA
Posted - 1/4/2002 1:48:27 AM  Show Profile  Email Poster  Edit Message  pauldogs Homepage
It sounds like you have 00569900 and not 3CP5699A. I tried opening each of these files, and the only option it gives (in either case) is expanding the file, not installing.

One more thing to try, then - when Windows finds the modem, click "Cancel" and then try to install by clicking "Add Modem", then "pick from a list" and then "Have Disk".

I tried this (with the 00569900 driver unzipped in a folder on my hard disk) without having a Winmodem installed, and the wizard found the INF file OK. I stopped there because I didn't want a nonexistent modem in my registry.

I doubt that you have a hardware problem - these modems are a pain in the ass to get the drivers installed right. ISA would probably be worse, in a computer with ISA and PCI slots. I had an older ISA Winmodem spontaneously uninstall itself repeatedly.

gospelmidi
Tl Posts:
252

USA
Posted - 1/4/2002 9:40:28 AM  Show Profile  Email Poster  Edit Message
I've installed the VIA 4.36 4-n-1 driver, but no joy.

I've installed the 00569900 winmodem.inf file with <right-click>install. Nothing doing.

Perhaps there is some clue as to why the modem won't answer up in the following from the winmodem.inf file. It doesn't match the modem FCC ID, 4X2USA-25314-M5-E.

[USR]

%Winmodem.DeviceDesc% = Winmodem, PCI\VEN_12B9&DEV_1006&SUBSYS_007F12B9&REV_00

[Winmodem]

; Added mm/dd/yy per Hardware Newsletter (October 98)
DriverVer=02/25/1999,1.00.017.0

AddReg=All, Data, Properties, Verbose, Internal, V22, V23, V32, V34, V80, 56K, DosBoxAddReg, DosBoxDelReg
CopyFiles=CopySys,CopyWM
UpdateInis=DosBoxINI
DelReg=DosBoxDelReg

[Properties]
HKR,, Properties, 1, 80,01,00,00, FF,00,00,00, FF,00,00,00, 07,00,00,00, 0F,00,00,00, 77,07,00,00, 00,C2,01,00, 60,EA,00,00

charles
Tl Posts:
5879

USA
Posted - 1/4/2002 10:21:16 AM  Show Profile  Email Poster  Edit Message
When your are ask from windows for the driver try A:\ or look in the floppy for the drivers and type in the folder that the drivers are in.

Model 5699-00, U.S. Robotics PCI 56K FAX Winmodem (PCI\VEN_12B9&DEV_1006&SUBSYS_007F12B9&REV_00)
Edited by - charles on 1/4/02 10:29:14 AM

Bob Starnes
Tl Posts:
4360

USA
Posted - 1/4/2002 4:36:49 PM  Show Profile  Email Poster  Edit Message
Maybe it's not a 5699...

4X2USA-25314-M5-E
CJEMUL-35734-M5-E

3Com/U.S. Robotics 56K Voice Internal PCI
F/M/V/J, Model 2884, [3CP3472-OEM-50] "Alana"
with external jacks/"Killer", Model 0642, Analog
Devices AD1806JS (controllerless) chipset
(PCI\VEN_12B9&DEV_1006&SUBSYS_005C12B9&REV_00)
-----------

4X2USA-25314-M5-E

Model 0637 [662974-81] (OEM "Alana" without
external jacks) 56K PCI Winmodem D/F/V

-----------

4X2USA-25314-M5-E

Model 0637 56K PCI Voice Win [3CP2974A-GTY]
Gateway OEM
---------

4X2USA-25314-M5-E

Model 0637-D (0421-00, 66297500 R:2) (OEM
"Coyote"),[663528], Model 2975, 56K PCI
Winmodem Data/Fax; Model 5690-00 D/F/V; Model
0642, AD1806JS chipset
(PCI\VEN_12B9&DEV_1006&SUBSYS_008012B9&REV_00)
---------

4X2USA-25314-M5-E

Model 5690-00, U.S. Robotics PCI 56K FAX Voice
Winmodem
(PCI\VEN_12B9&DEV_1006&SUBSYS_006812B9&REV_00)

---------

gospelmidi
Tl Posts:
252

USA
Posted - 1/4/2002 10:27:50 PM  Show Profile  Email Poster  Edit Message
Yes, Bob, that appears to be the case. The card is stenciled 1.012.0637-D, but it won't install with that driver. It does install as a U.S. Robotics 56K Win INT using the Coyote driver.

The 005699 sticker on the modem must have been stuck on it from another modem by someone whose name shall go unmentioned, OK?

Bob Starnes
Tl Posts:
4360

USA
Posted - 1/4/2002 10:57:58 PM  Show Profile  Email Poster  Edit Message
Perhaps it was just a slip of the finger, maybe it was intended to read as a 5690 rather than 5699...

Click Here To Close Thread, Administrators & Moderators Only.

Show All Forums |