View Single Post
  #3  
Old October 28th 05, 08:17 AM
nonewbie
external usenet poster
 
Posts: n/a
Default Any Tapi/Dun/Modem Experts Question

on Wed 26 Oct 2005 07:08:41p, "glee"
wrote in :

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


I tried two driver packages for that exact modem. One from the
dell site that is supposedly the original package that came with
the box and the second an update driver package also for that
exact same modem from a third party. Both result in the same
outcome. The modem appears ok in the Device mgr under systems, and
responds to "more info-diagnostics with the parameter readout",
but there is no modem listed next to the com2 to which it is
assigned. Everytime I try to make a dun it wants me to reinstall
the drivers. The modem properties box is also devoid of any entry
(empty) yet the exact name of the modem appears in device manager.
I know exactly what modem it is because there is a sticker on the
back of the modem. Aztech modem, also attibuted to HCF and
Rockwell-aztech mdp3880-w(u) modem It is a winmodem that must use
the enumerator to communicate. The breakdown is occuring between
the modem and dun, since the modem responds to diagnostic command
under more info, yet dun cannot be made. I have tried both MS
fixes and neither works. The second fix is to re extract the
unimdm.tsp file, but that is only in cases where it is missing or
corrupted and I checke it with file compare against a freshly
extracted file and they are identical, so that fix will do
nothing.


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.


I think I did explain this but I will do it again. I followed the
procedure you just stated above. I even did this: removed the
enumerator from add/remove, removed the modem from device manager,
removed all com ports. Reinstalled two comm ports, installed the
enumerator using setup from the drive package install, which
automatically installs the modem to the device manager. Modem
appears ok in device manager, but no modem name or model next to
com port to which it is assigned and from which I get a normal
response using more info-diagnostics. Everything appears normal,
yet each time I try to make a dun, it asks me to select the
locaton of the driver package that has already been installed.
There is no "OTHER" in device manager; and no other modems
installed. Only other thing installed is netgear stuff for
networking on a ethernet card.

Personally, I would not use this type of modem if another option
were available.


Well, yes, but since I only paid $12 for this machine which has
everything else working fine, including a brand new sony 52x
cd-rw, I hesitate to spend money for a new modem, since I'm going
to sell it anyways and since I do not feel the winOS warrants
buying new hardware. I already know modem is a sucky modem, but
it responds to the diagnostic commands, so am inclined to think
this is another windows OS quagmire that no one seems to be able
to answer.

I am going to try to remove all modem entries in registry next
after removing the modem and drivers again to see if it is a
registry problem.

Does anyone here know how to deinstall and reinstall all OS
related software related to DUN to modem interaction without
necessitating a complete OS nuke and reinstall? Several others
have reported reinstalling done did nothing to fix this problem.

Dun is not seeing the modem as installed and the part of the OS that
reports the modem name and model in "modem properties" is not showing
it either, although it is reported fine in device manager. I have no
guarantee even if I buy a new modem that win98 will see it properly
either.