Microsoft KB Archive/254332

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 17:16, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Article ID: 254332

Article Last Modified on 1/27/2007



APPLIES TO

  • Microsoft Windows 98 Standard Edition
  • Microsoft Windows Millennium Edition



This article was previously published under Q254332

If this article does not describe your hardware-related issue, please see the following Microsoft Web site to view more articles about hardware:

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry


SYMPTOMS

You may experience one of the following symptoms:

  • When you try to create a new Dial-Up Networking connection or open one in the Dial-Up Networking folder, you may not be able to select your modem in the Install New Modem wizard.
  • When you open Dial-up Networking you are prompted to install a modem.
  • If you look in Device Manager, you see the currently installed modem with the following device status in the modem's properties:

    This device is working properly.

If you open the Modem tool in Control Panel, and then click More Info on the Diagnostics tab, you do not receive any error messages.

CAUSE

This behavior can occur if one of the TAPI components are damaged or missing, or if a third-party Telephony driver is referenced in the registry and that driver is damaged or incompatible with Windows.

RESOLUTION

To resolve this issue, follow the steps in each method. At the end of each method, test to see if the issue is resolved.

Method 1: Check for Third-Party Telephony Drivers

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
Use Registry Editor to check the ProviderFilename0 value in the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Telephony\Providers


NOTE: The default value data for the ProviderFilename0 value is TSP3216L.TSP. If the value data is not TSP3216L.TSP, export the Providers registry key, and then change the value data to TSP3216L.TSP.

Method 2: Check for a Damaged Telephon.ini File

  1. Click Start, point to Find, and then click Files or Folders.
  2. In the Named box, type telephon.ini tapiini.exe, click your primary disk in the Look In box, and then click Find Now.
  3. Right-click the Telephon.ini file, and then click Delete.
  4. Double-click the Tapiini.exe file to create a new Telephon.ini file. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

    120221 How to Rebuild the Telephon.ini File

Method 3: Check for Damaged TAPI Components

  1. Click Start, point to Find, and then click Files or Folders.
  2. In the Named box, type tapiini.exe tapi.dll tapiui.dll tapisrv.exe tapiupr.exe tapi16.exe remotesp.tsp tsp3216l.tsp tsp3216s.dll tlocmgr.exe telephon.cpl tcmsetup.exe tapi.inf, click your primary disk in the Look In box, and then click Find Now.
  3. For each file found, right-click the file, and then click Rename. Change the file extension on each file to .old.

    NOTE: There is one TAPI file that requires you to rename it while you are in MS-DOS mode.
  4. Click Start, click Shutdown, click Restart in MS-DOS mode, and then click OK.
  5. At the C:\Windows prompt type the following lines, pressing ENTER after each line:

    cd system
    ren tapi32.dll tapi32.old
    exit

  6. Click Start, click Run, type sfc.exe in the Open box, and then click OK.
  7. In the System File Checker tool, click the Extract one file from installation disk option.
  8. In the Specify the system file you would like to restore box, type tapi32.dll, and then click Start.
  9. In the Restore from box, click the drive where you installed Windows.
  10. In the Save file in box, type c:\windows\system, and then click OK. Repeat steps 6 through 9 for each of the files below.

    NOTE: The Tapi.inf file is the only one of these files that does not reside in the C:\Windows\System folder. When you extract this file, change the Save file in box to c:\windows\inf.

    Tapi.inf
    Tapiini.exe
    Tapi.dll
    Tapiui.dll
    Tapisrv.exe
    Tapiupr.exe
    Tapi16.exe
    Remotesp.tsp
    Tsp3216l.tsp
    Tsp3216s.dll
    Tlocmgr.exe
    Telephon.cpl
    Tcmsetup.exe

  11. Restart the computer.

NOTE: A damaged modem driver or incorrect modem driver can also create this problem. If the problem continues, try removing and reinstalling the modem from Device Manager. Make sure you have the current modem drivers available to reinstall.

REFERENCES

SRX000914602787


Additional query words: HWMODTS

Keywords: kbenv kbnetwork kbprb KB254332