View Single Post
  #2  
Old October 27th 05, 03:08 AM
glee
external usenet poster
 
Posts: n/a
Default Any Tapi/Dun/Modem Experts Question

If you were to contact MS for paid support, you would be given the procedures in
those two KB articles to try first. They would likely not continue until those had
been eliminated as possible causes. What you call "lame fixes" have worked for many
people with these errors. The problems you see when googling it represent the
minority.....certainly there are other causes, that goes without saying.

Exactly what driver for the modem have you installed, and where did you get it?
Links please, if you downloaded it.

The modem you describe (aztech mdp3880-w(u) modem) is apparently an HCF-chipset
modem...a controllerless Winmodem. More on what that is, here=
http://www.modemsite.com/56k/hcf1.asp
It probably has a Conexant HCF chipset and *may* have this PCI Vendor ID in the
Registry:
(PCI\VEN_14F1&DEV_1033&SUBSYS_4034122D)
It's simple enough to determine the Vendor info by checking the Registry sub-keys at
HKEY_LOCAL_MACHINE\Enum\PCI

You are not clear on exactly how you are installing and uninstalling the modem, and
also do not indicate if there is more than one instance of the modem in Device
Manager, in Normal Mode. Most if not all controllerless modems require a software
installation, meaning there will be an entry in Add\Remove Programs for removing the
modem and enumerator (the Enumerator will appear as a separate item in Device
Manager, and will show the actual resources used, if it appears). Uninstall of a
modem of this type requires that you use the uninstall provided in Add\Remove
Programs. prior to attempting a reinstall of the modem, you should start in Safe
Mode, and remove any and all instances of that modem in Device Manager that may
appear there, as well as any other modems that are no longer connected to the
machine, and all items in the "Other" category if it exists. Click OK/Close, then
restart in normal mode and install the modem exactly as described in the driver
documentation. Again, you have not told us exactly what driver you are installing,
by what method, and from where it came.

Personally, I would not use this type of modem if another option were available.
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm


"nonewbie" wrote in message ...
"glee" wrote in
:

OK, you tried both the telephon.ini rebuild (rename telephon.ini, then
StartRuntapiini.exe, then reboot); and you opened Regedit and went
to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr ent Version\
Telephony\Providers modified the data for the ProviderFilename0 value,
to TSP3216L.TSP, and rebooted; and you still get the same
error....correct?


yes, already did MS fix (another fix that doesn't work as others have
reported with the SAME problem)

If so, try the procedure in this article:
32-Bit TAPI Programs May Not Be Able to Access Your Installed Modem:
http://support.microsoft.com/kb/q150619/
to extract a new copy of the Unimdm.tsp file from your Windows CD to
the Windows\System folder.



Why should I try another of their lame fixes since I already checked
unimdm.tsp against one extracted from the cab files and they are
identical files. The bulletin says the problem is due to corruption or
missing unimdm.tsp and it is neither missing nor corrupted.

There is a exe file to use to clear the registry of win98 of winmodem
entries, but it is for another type of modem so I am reluctant to use
it. Does anyone in this group know if it is to be applied to all
winmodems or can be?

This is just another example of poor documentation and support by MS for
it's products.


Using SFC to extract a file:
http://www.rickrogers.org/sfc.htm#1pp
http://www.rickrogers.org/sfc.htm#2pp

HOW TO: Extract Original Compressed Windows Files:
http://support.microsoft.com/default...EN-US;129605#5