WinModem FAQ Known Software Problems * Netscape Dialer 1.X Work around Get Netscape 2.X * All DOS Based Apps Work around None * Most Auto Dialers Work around None * Damaged or Incorrect Work Add ForceBridgeOrRouter=TRUE COMM.DRV around to the SYSTEM.INI * Reflections 1 or 2.X Work around Try the 95 Version (4.0) * Lap Link 6.X or 7.X Work around None, Laplink needs a modem that works in DOS Winmodem Troubleshooting Tips Problem: The Winmodem installed correctly and responds to AT commands fine, but whenever I call out, the modem makes a 9600 V.34 connection. Solution: This has been seen when there is a problem with the current communications driver. Adding ForceBridgeOrRouter=TRUE to the SYSTEM.INI may correct this problem by bypassing the current communications driver and going directly to the Winmodem. You should also make sure that your Port Rate is set to 19200 in your Control Panel/Port Settings in Windows 3.1x, and that it is set to 38400 or higher under Windows 95. ______________________________________________________________________ Problem: Win 95 never detected the modem. Solution: Make sure the system has a free Com Port or IRQ to use. Valid Com Ports are 1, 2, 3, and 4, and valid IRQ's are 3, 4, 5, 7, and 9. Check to see if the Winmodem was previously installed on the system with Win 3.1x running? If so, you need to search the SYSTEM.INI and WIN.INI files and remove all Winmodem settings. Under Windows 95, make sure that the modem is not listed in the device manager under "other devices". If it is, delete it and reinstall. Make sure the key USR1001 is not in the registry. This can be done by selecting Edit/Find in regedit, and searching for USR1001. If it is, delete it. (WARNING: Making Any Changes To The Windows 95 Registry Can Cause Major Problems. Do This At Your Own Risk! Make sure you have made a backup copy of your registry before starting regedit.) _____________________________________________________________________ Problem: Why does Winmodem install on COM 5 when 95 says that there is at least one of the following COM Ports free: 1, 2, 3, 4? Solution: A damaged Registry file may only show partial data for a COM Port. The Registry Plug and Play(PnP) files may have been affected by a partial or incomplete install of the Winmodem, or may have been affected by another program. All basic PnP settings may be in use. Change the port manually to see if Windows 95 accepts it. _____________________________________________________________________ Question: Why does MSD not see the Winmodem? Answer: The Winmodem will never show in MSD. It is strictly a Windows based modem and can never be seen in DOS. _____________________________________________________________________ Problem: I get an Error message 2007. Reason: ERR MSG: " Unable to hook Comm.DRV". You may have a damaged Communication Driver. ERR MSG: " Unable to hook Comm.DRV". You might be using a non-Microsoft Communication Driver ERR MSG: "Unable to open WINMODEM.VXD". Run CHKDSK. The Winmodem driver files may be damaged. _____________________________________________________________________ Problem: The Winmodem says it installed successfully in Windows 95, but in the Modem Diagnostics screen, in the Control Panel, under MORE INFO, it shows that it can not open the Port. Reason: This can occur when you install a Winmodem and Windows 95 already has a record for that COM Port in the registry prior to the install. _____________________________________________________________________ Problem: Reachout 5.0 For Windows doesn't work. Solution: With the 1.0 version of the software, turn OFF the DCD Watch option in Reachout and choose the Windows communications driver to fix it. If this does not help, turn on the Comm.drv compatible mode.option. _____________________________________________________________________ Problem: I upgraded from an older version of Netscape to the 2.x Professional version, but Netscape's dialer still can not initialize my modem. Solution: Installing the 2.x Professional version of Netscape will not automatically update the dialer. This has to be done manually. _____________________________________________________________________ Problem: How do I uninstall the Winmodem settings left behind from Windows 3.1 when I just upgraded to Win 95? I keep getting an error that WMCONFIG.EXE has performed an illegal instruction in UNKNOWN DLL. Solution: Step 1: In the SYSTEM.INI [Boot] section, remove the following from the DRIVERS= line: C:\WINMODEM\WINMODEM.DRV. In the [386enh] section of the SYSTEM.INI, remove the following line: DEVICE=C:\WINMODEM\WINMODEM.386. Next remove all items contained in the [Winmodem] section of the SYSTEM.INI including the line [Winmodem]. Step 2: From the WIN.INI file, remove the following sections of the load= line: C:\WINMODEM\wmconfig.exe and C:\WINMODEM\winmodem.exe Step 3: In the Device Manager; check under other devices to see if a record for Winmodem exists. If so, select it, and click on `Remove'. ( WARNING: Making Any Changes to the Windows 95 Registry Can Cause Major Problems. Do This At Your Own Risk! Make sure you have made a backup copy of the registry before starting regedit. ) 1. Click Start, select Run and type REGEDIT. 2. Click edit, then find and type USR1001. 3. When USR1001 in the Hardware\ISAPNP section is found, click edit then delete. 4. Close REGEDIT 5. Go to START/SHUT DOWN/RESTART THE COMPUTER 6. Windows 95 will now detect the Winmodem and install correctly _____________________________________________________________________ Question: How do I test if my installed Winmodem is working correctly? Answer: In Windows 3.1x, run Terminal. Select Settings, then Communications and select the correct Com Port or Connector as Terminal calls it. Set the Baud Rate to 19200, change the flow control to hardware, and click on OK. From the Terminal screen, type ATI3 and hit the ENTER key. If the modem responds, on screen, that the modem is a Sportster Winmodem, then the modem is working correctly. If not, begin normal troubleshooting. In Windows 95, click on Start/Settings/Control Panel/Modems/Diagnostiscs. Highlight the Com Port that shows the Winmodem installed on it. Click on MORE INFO. If the lower screen reports back ATIx information, the modem is successfully installed _____________________________________________________________________ Question: What is the Winmodem vendor ID? Answer: USR1001 _____________________________________________________________________ Problem: My Winmodem responds to AT commands, but always reports No Dial Tone. Answer: If the Winmodem dials with ATX3DT, you may have the wrong version of the Winmodem install software for that model modem(i.e. a 112502 modem with the 112500 install disk). Contact U.S. Robotics to make sure you are using the correct version of the software. _____________________________________________________________________ Problem: I installed the Winmodem successfully in Windows 95 on Com 3 IRQ 5, and now my system hangs when I try to go back into Windows 95? Solution: It has been reported that some sound cards using 16-bit DOS drivers may be set to IRQ 5, but never show up in Windows 95. Remove the sound card from the computer. If Windows 95 boots correctly without the sound card, then this is most likely the problem. The best way to resolve this conflict is to download the latest Windows 95 drivers for that sound card, from the manufacturer, and move it off IRQ 5. _____________________________________________________________________ Problem: My computer reports a Plug and Play(PnP) error during bootup in reference to the USR Winmodem. Reason: This is caused when one or more of the required settings for the Winmodem is unavailable, (i.e. I/O Address, IRQ, or Com Port ). _____________________________________________________________________ Problem: When starting Windows 3.1x, I receive an unable to load Winmodem.VXD error msg. Solution: Computers with insufficient resources are reporting this problem. This error will also happen on 286 or 386 machines which are not supported by the Winmodem. _____________________________________________________________________ Issue: In Win 3.1x, the COM Port used by the mouse is reported as Free during install. Reason: Versapoint and some other mouse drivers may not correctly report the status of the COM Port assigned to the mouse. _____________________________________________________________________ Problem: Error message reporting that Windows is unable to load a program at startup. The message displays a program name which is "cut off". Solution: The Load= line in the WIN.INI file is limited to 128 characters. If other programs were placed on this line prior to installing the Winmodem, it is possible that the additions made by the Winmodem exceeded the character limit. Move some of the prior statements from the Load= line to the Run= line.