View Single Post
Old October 29th 05, 09:59 AM
external usenet poster
Posts: n/a
Default Any Tapi/Dun/Modem Experts Question

My daughter had not saved the old files, since the modem installed on her XP
machine with no trouble--wouldn't you know it! :-)

Anyhow, I looked for anything I might have, but all I came up with was the
generic Conexant package, which you have already seen, and I believe we used
the Dell package, anyhow. Probably, there is not a large difference between
the packages, if any.

If you have already uninstalled the enumerator (which appears in Add/Remove
as something like Conexant MDP3880 W {and may even say modem, but it's the
enumerator}) as well as the modem itself (glee discussed all this, I think)
and when you try again, you *don't* get something like 'PCI HSF Modem
Enumerator' installed first and then the modem itself, but some unknown PCI
device, *or*, in spite of the succession of 2 installation steps in which
you gave it specific file locations for the setup files, and you still
didn't get the modem to operate, you might try the following.

After uninstalling both the enumerator and the modem that had installed
incorrectly, go to the folder into which you extracted the package. There
will probably be four .INF files. You will need only two of them, and which
two depends upon the explicit model (I can't tell you). One installs the
enumerator, and the other the modem.

Find the two infs that have precisely the same modem ID in the [Strings]
section of each file. I.e., in the generic package, it's CXT\GenericHSF in
one set, and CXT\GenericHSFi in the other. Disable the .INFs that have,
say, CXT\GenericHSF by renaming the extensions to .JSF, and try the

If that doesn't work, try returning the extensions to .INF on that pair, and
changing the extensions on the other pair to .JSF, and try the installation

I don't recall if this is something I tried at the time, or not, but it
seems like something I might have tried. Beyond this, the best I can say is
that we had *exactly* the same symptomatic behaviour you describe, and I did
finally get it to work, and it didn't involve any messing around with the
DUN components.

Good Luck,
"nonewbie" wrote in message
on Thu 27 Oct 2005 09:34:39p, "jt3" wrote in

I looked through both my steno pads but couldn't find any notes
on the modem installation.

I will e-mail my daughter, since I think she kept the modem to
put on her new XP machine, and she *may* have kept the notes I
wrote up for her at the time, but I wouldn't bet on it. She
only keeps stuff she can leave here with us, otherwise travels
light-- I will look on some of the backup CDs I wrote at that
time, and see what I can find.

Note that glee has given a very good summation of the problem:

I read his post. Nothing new there, that I did not already know or
try. I appreciate the replies, but really nothing new. Guess I
will have to become a DUN expert to figure out what is going on.
It would be nice if MS provided documentation as to the highly
classified mystical operations of it's OS with regards to modems,
since they have already milked with win98 cow for what it is
worth, but even the one MS tapi "expert" who replied sarcastically
cannot fanthom up an answer,even a sarcastic one. The problem is
with the OS. It cannot properly detect the installed modem, even
with the correct drivers installed. This is to be expected with MS
products, nothing suprising on that count. I did find out today it
has nothing to do with modem settings as this is a plug an pray
modem and the bios does not have to be disabled for that type of

. Between that and
the links he provided, you'll probably get a clearer picture
than I can provide, but I'll look and see.

Good Luck,

"nonewbie" wrote in message
I am grateful for ANY help.
Several people other than myself have posted on this same
problem and I have not seen ANY definitive answers on it. I
already tried deinstalling under add/remove the enumerator and
then removing the modem and ports, nothing seems to work. I
think this is a registry problem, but there is nothing in the
MS KB about it and they say to remove all references to the
winmodem in the registry, but they do not tell you where they
are, nor how to remove them except for 3com modems that have
a special program.

"jt3" wrote in

Sorry about the vagueness, but as I said, it's been a while.

As well as I can recall, which is not very well, you end up
with two different things installed if you try the
directions/std install. I tried many different permutations
of install, and could easily be mixing them up now.
Uninstalling the modem doesn't uninstall the enumerator, I
believe; you must uninstall that explicitly in Add/Remove. I
believe that it was important to get all of the stuff
uninstalled to get it right finally.

I have an old notebook I used at the time and may have some
notes on it--will see if I can find it and get back. That
is, if you want it. I'm no professional, and don't claim to
know what I'm doing. It's mostly empirical, just as for
virtually everyone else here, and if you can't handle that,
then I'll be of no use to you.

"nonewbie" wrote in message
Thanks, not sure I know (or you do) what you mean.

If I install the latest driver package that IS the
enumerator, it automatically installs the modem on the OS.
So, how can you install the enumerator without installing
the modem?? In fact, I did install the enumbetor/driver
package prior to letting windows try it's install as I

Also nobody has said anything about what exactly the bios
settings should be on this install. Some say to disable the
irqs for the modem; which I'm guessing is "reserved" under
my bios. I think I may have tried it both ways. The problem
appears to be a windows screw up in the registry and windows
is confused again. There have been numerous posts on this
problem from different individuals (google it) and no one
has explained how this install process works, what the
interaction with tapi is and what to do about it.

Also does anyone know what the effect of removing unimdm.tsk
from the control panel will do on this system? Is it
possible to reinstall it without reinstalling the whole OS
if I try removing it?

Maybe MS wants me to call in any pay for tech support so
they don't give the real answers to this problem :-(.

"jt3" wrote in

I hesitate to say much when it's so fuzzy in my
memory--these days 2 years blanks me out pretty badly--but
my daughter's Dell had the same problem (same modem) and
as I recall after thrashing with it for the better part of
a month, I finally decided that the problem seems to occur
as a result of the modem being detected and an install
attempted before the Conexant enumerator is installed.

When they get installed in the wrong order, it does just
what you described.

I *think* I uninstalled the mess and tried again (one of
many retries), not allowing the modem to install
initially, and then when the enumerator gets installed (I
forget what it's called--HCF Modem or some such) you can
let it install the modem.

It worked well enough that when I had to reinstall it the
next year she was back from college, that I was able to do
it with only a little fumbling around. She isn't here,
and no longer has the machine anyway, or I'd check it out.

Hope this is of some use.

"nonewbie" wrote in message
cannot get dun to work with aztech mdp3880-w(u) modem.

installed latest drivers, install went fine. "more info"
reported info from the modem.

When I try to dialout using dun i get : "error 633- modem
is not installed or configured for dialup, double click
on the modems icon in control panel"

When I do the above, it tries to reinstall the modem
drivers,even though they have already been installed.

Tried on of MS's solutions and rebuilt telephon.ini,
still no go. Also did their registry fix for telephon.ini

tried uninstalling and reinstalling drivers and modem
still no problem. Modem now assigned to com3 IRQ 10

in my Dell dimension bios, there is a section for all the
irqs where u set it to either available or reserved, but
I was told that this is only for non-plug and pray modems
and I got a message from windows saying this is plug and
pray modem. IRQ is currently marked available in bios.