A Windows 98 & ME forum. Win98banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Win98banter forum » Windows 98 » General
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

Any Tapi/Dun/Modem Experts Question



 
 
Thread Tools Display Modes
  #1  
Old October 25th 05, 04:25 AM
jt3
external usenet poster
 
Posts: n/a
Default Any Tapi/Dun/Modem Experts Question

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.

Joe
"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.




  #2  
Old October 26th 05, 10:27 PM
jt3
external usenet poster
 
Posts: n/a
Default Any Tapi/Dun/Modem Experts Question

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.

Joe
"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
recall.

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.




Joe
"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.








  #3  
Old October 28th 05, 05:34 AM
jt3
external usenet poster
 
Posts: n/a
Default Any Tapi/Dun/Modem Experts Question

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:
. 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,
Joe


"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.

Joe
"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 recall.

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.



Joe
"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.




  #4  
Old October 28th 05, 08:30 AM
nonewbie
external usenet poster
 
Posts: n/a
Default Any Tapi/Dun/Modem Experts Question

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
modem.

. 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,
Joe


"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.

Joe
"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
recall.

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.



Joe
"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.





  #5  
Old October 29th 05, 09:59 AM
jt3
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
installation.

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
again.

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,
Joe
"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
modem.

. 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,
Joe


"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.

Joe
"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
recall.

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.



Joe
"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.







  #6  
Old October 30th 05, 10:37 AM
nonewbie
external usenet poster
 
Posts: n/a
Default Any Tapi/Dun/Modem Experts Question

on Sat 29 Oct 2005 01:59:47a, "jt3" wrote in
:

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


Thanks for your persistence, I appreciate it, jt3. See below for some
further developments, if your not to feed up with me yet, haha.


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.


See my reply to Franc above, tried two different driver revisions,
very similar, same bad results. The problem is with windows, I
think, but I suppose it COULD still be an inappropriate driver
package, but as I said to Franc could be that the original modem
install diskette has something on it that eases the install.

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.


see reply to Franc. deleted all registry entries related to this
particular modem after again removing it from control
panel-enumerator would not remove from add/remove until I went
through the registry. also removed(renamed) all driver files
installed by previous installs from win/sys/dir and their
corresponding entries in the registry.Now each windows boot gives:
building driver base, insert modem install disk, to which I reply
cancel since I don't have the original disk and am not sure which
of three same modem driver packages to try next. Windows added 3
registry keys on reboot- /services/class/hcfmodem/ empty and
control/asd/root/modem/0000 and enum/root/unknown/0000/mpd3880 pci
modem enumerator

These new registry entries are different than what was there
before, so I am hopeful I am not being led up the primose path
again and that if I now give it the driver file directory it is
asking for all will go well, but not holding my breath.



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 installation.

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 again.


Ok, but this is dependent on already having those files in either
or both the windows directory and registry-both of which I have
removed. There are two files that seem to be critical mdmp4034.inf
and brdg4034.inf I guess the mdmp4034 is the one for the modem,
but not sure at this point. dell only talks about installing the
brdg4034 file although both files are in the package. This may
have been a case of a corrupted registry as I found numerous
entries for various .inf files for this modem there. One of these
driver packages just says to run setup.exe (which I tried) and the
other from dell says point to the inf file brdg4034 and the directory
it is in and let windows do it's stuff, so I am somewhat confused on
exactly what the right install method should be.

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.


Yeah, it has nothing to do with DUN itself, but with the
interaction between windows and the driver files and the registry.
As with so many win**** screwups it is usually traceable to
screwups with their registry and win**** getting confused and then
going beserk. If I wasn't going to sell this box and if win****
didn't have such a stranglehold over the populace and third party
software developers I would have wiped the drive and installed
another OS. I might just break down and buy a real internal modem for
it, but that might be opening up just another can of worms.



Good Luck,
Joe
"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 modem.

. 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,
Joe


"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.

Joe
"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 recall.

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.



Joe
"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.








  #7  
Old October 31st 05, 08:20 PM
jt3
external usenet poster
 
Posts: n/a
Default Any Tapi/Dun/Modem Experts Question

Replies inline:
"nonewbie" wrote in message
...
on Sat 29 Oct 2005 01:59:47a, "jt3" wrote in
:

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


Thanks for your persistence, I appreciate it, jt3. See below for some
further developments, if your not to feed up with me yet, haha.


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.


See my reply to Franc above, tried two different driver revisions,
very similar, same bad results. The problem is with windows, I
think, but I suppose it COULD still be an inappropriate driver
package, but as I said to Franc could be that the original modem
install diskette has something on it that eases the install.


We used a Dell version downloaded from their site. Didn't have anything
that came with the machine, no install disk.
Let me emphasize that IIRC, your symptoms are virtually identical to those
we received. Your mention of the the inf file names jogged my memory--those
were the ones involved--I printed them out at one point.
I did manually clean the registry, but I don't recall if that was actually
necessary in the final phases of our efforts, I think not, since the second
time, a year later, was much simpler.

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.


see reply to Franc. deleted all registry entries related to this
particular modem after again removing it from control
panel-enumerator would not remove from add/remove until I went
through the registry. also removed(renamed) all driver files
installed by previous installs from win/sys/dir and their
corresponding entries in the registry.Now each windows boot gives:
building driver base, insert modem install disk, to which I reply
cancel since I don't have the original disk and am not sure which
of three same modem driver packages to try next. Windows added 3
registry keys on reboot- /services/class/hcfmodem/ empty and
control/asd/root/modem/0000 and enum/root/unknown/0000/mpd3880 pci
modem enumerator


the enum/root/unknown/... key is the result of Win trying to find the setup
(inf) files in the \INF folder, and not succeeding.


These new registry entries are different than what was there
before, so I am hopeful I am not being led up the primose path
again and that if I now give it the driver file directory it is
asking for all will go well, but not holding my breath.



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.

These suggestions were based upon the generic Conexant package, which was
the only thing I still had in my backup files, but, though we tried them at
some point, was not the package we used.

As I said, you jogged my memory on the matter.
But if you unzip the Dell package, you should have those infs you mentioned
in a folder you specify, and when the 'found hardware' box comes up, when
you're asked for a disk or location, just cancel it out. IIRC, it may
*still* install something, I don't recall which, logically the modem without
the enumerator, but once the machine is finished booting, you can uninstall
that--but don't reboot. Then, go to that folder where you unzipped the
package. (I'm flying in a fog here with no instruments--it was too long
ago) I don't recall if there is a 'start.exe', or an 'install.exe' routine
in the package that reads the infs and everything, but there might be. If
so, execute that. If not execute the inf (probably the 'bridge' one, but I
don't recall this) using the right-click menu. Again, this is all so hazy
in my memory that I can't promise any accuracy in any of it. One doesn't
know whether to bow to Redmond, Texas, or Mexico, where the Conexant chip is
made.

Once again, best of luck, and hope this helps rather than hinders!
Joe


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 installation.

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 again.


Ok, but this is dependent on already having those files in either
or both the windows directory and registry-both of which I have
removed. There are two files that seem to be critical mdmp4034.inf
and brdg4034.inf I guess the mdmp4034 is the one for the modem,
but not sure at this point. dell only talks about installing the
brdg4034 file although both files are in the package. This may
have been a case of a corrupted registry as I found numerous
entries for various .inf files for this modem there. One of these
driver packages just says to run setup.exe (which I tried) and the
other from dell says point to the inf file brdg4034 and the directory
it is in and let windows do it's stuff, so I am somewhat confused on
exactly what the right install method should be.

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.


Yeah, it has nothing to do with DUN itself, but with the
interaction between windows and the driver files and the registry.
As with so many win**** screwups it is usually traceable to
screwups with their registry and win**** getting confused and then
going beserk. If I wasn't going to sell this box and if win****
didn't have such a stranglehold over the populace and third party
software developers I would have wiped the drive and installed
another OS. I might just break down and buy a real internal modem for
it, but that might be opening up just another can of worms.



Good Luck,
Joe
"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 modem.

. 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,
Joe


"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.

Joe
"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 recall.

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.



Joe
"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.










  #8  
Old November 1st 05, 03:02 AM
nonewbie
external usenet poster
 
Posts: n/a
Default Any Tapi/Dun/Modem Experts Question

Ok, thanks, please see below for final question, not sure about
your instructions. snip as per newserver complaining.




We used a Dell version downloaded from their site. Didn't have
anything that came with the machine, no install disk.
Let me emphasize that IIRC, your symptoms are virtually identical
to those we received. Your mention of the the inf file names
jogged my memory--those were the ones involved--I printed them
out at one point. I did manually clean the registry, but I don't
recall if that was actually necessary in the final phases of our
efforts, I think not, since the second time, a year later, was
much simpler.

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.


see reply to Franc. deleted all registry entries related to
this particular modem after again removing it from control
panel-enumerator would not remove from add/remove until I went
through the registry. also removed(renamed) all driver files
installed by previous installs from win/sys/dir and their
corresponding entries in the registry.Now each windows boot
gives: building driver base, insert modem install disk, to
which I reply cancel since I don't have the original disk and
am not sure which of three same modem driver packages to try
next. Windows added 3 registry keys on reboot-
/services/class/hcfmodem/ empty and control/asd/root/modem/0000
and enum/root/unknown/0000/mpd3880 pci modem enumerator


the enum/root/unknown/... key is the result of Win trying to find
the setup (inf) files in the \INF folder, and not succeeding.


ok, another clue.


These new registry entries are different than what was there
before, so I am hopeful I am not being led up the primose path
again and that if I now give it the driver file directory it is
asking for all will go well, but not holding my breath.



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.


Dell says to feed windows the brdg4034.inf the other is mdmp4034.inf
I guess brdg must be short for bridge.



These suggestions were based upon the generic Conexant package,
which was the only thing I still had in my backup files, but,
though we tried them at some point, was not the package we used.

As I said, you jogged my memory on the matter.
But if you unzip the Dell package, you should have those infs you
mentioned in a folder you specify, and when the 'found hardware'
box comes up, when you're asked for a disk or location, just
cancel it out. IIRC, it may *still* install something, I don't
recall which, logically the modem without the enumerator, but
once the machine is finished booting, you can uninstall that--but
don't reboot. Then, go to that folder where you unzipped the
package. (I'm flying in a fog here with no instruments--it was
too long ago) I don't recall if there is a 'start.exe', or an
'install.exe' routine in the package that reads the infs and
everything, but there might be. If so, execute that. If not
execute the inf (probably the 'bridge' one, but I don't recall
this) using the right-click menu. Again, this is all so hazy in
my memory that I can't promise any accuracy in any of it. One
doesn't know whether to bow to Redmond, Texas, or Mexico, where
the Conexant chip is made.


I guess the substance of what you are saying is install the
enumerator BEFORE installing the modem? So you are saying to run
setup.exe(from the driver package) BEFORE telling windows where to
find the inf files? Windows does not install anything if you click
cancel when it asks for the diskette-it only modifies the registry
as per the two entries I mentioned above. I believe the file is
the brdg4034.inf is the one to feed windows went it asks for the
diskette. The setup.exe is the one that makes the enumerator popup
into the add/remove section of windows. The brdg4034.inf file is the
one dell says to give windows when it asks for the location of the
driver files.

Thanks for you help.

Once again, best of luck, and hope this helps rather than
hinders!

Thanks for your help. If it is possible to get it running I will,
then on to buying new modem.


Joe

  #9  
Old November 1st 05, 07:44 AM
jt3
external usenet poster
 
Posts: n/a
Default Any Tapi/Dun/Modem Experts Question

Yes, the brdgXXXX.inf is the one I meant. That's the memory jog.

Whether or not you can start it that way depends upon whether or not the
..inf is a so-called 'advanced inf'.

If it is, you can't--you have to use another method.

You can tell by looking at the first section of the .inf file--it will say
so.
It's just text, you can read it with Notepad. But I think it's just the
simple variety.

Joe
"nonewbie" wrote in message
...
Ok, thanks, please see below for final question, not sure about
your instructions. snip as per newserver complaining.

{snip}

the enum/root/unknown/... key is the result of Win trying to find
the setup (inf) files in the \INF folder, and not succeeding.


ok, another clue.

{more snips}

Dell says to feed windows the brdg4034.inf the other is mdmp4034.inf
I guess brdg must be short for bridge.



These suggestions were based upon the generic Conexant package,
which was the only thing I still had in my backup files, but,
though we tried them at some point, was not the package we used.

As I said, you jogged my memory on the matter.
But if you unzip the Dell package, you should have those infs you
mentioned in a folder you specify, and when the 'found hardware'
box comes up, when you're asked for a disk or location, just
cancel it out. IIRC, it may *still* install something, I don't
recall which, logically the modem without the enumerator, but
once the machine is finished booting, you can uninstall that--but
don't reboot. Then, go to that folder where you unzipped the
package. (I'm flying in a fog here with no instruments--it was
too long ago) I don't recall if there is a 'start.exe', or an
'install.exe' routine in the package that reads the infs and
everything, but there might be. If so, execute that. If not
execute the inf (probably the 'bridge' one, but I don't recall
this) using the right-click menu. Again, this is all so hazy in
my memory that I can't promise any accuracy in any of it. One
doesn't know whether to bow to Redmond, Texas, or Mexico, where
the Conexant chip is made.


I guess the substance of what you are saying is install the
enumerator BEFORE installing the modem? So you are saying to run
setup.exe(from the driver package) BEFORE telling windows where to
find the inf files? Windows does not install anything if you click
cancel when it asks for the diskette-it only modifies the registry
as per the two entries I mentioned above. I believe the file is
the brdg4034.inf is the one to feed windows went it asks for the
diskette. The setup.exe is the one that makes the enumerator popup
into the add/remove section of windows. The brdg4034.inf file is the
one dell says to give windows when it asks for the location of the
driver files.


I'm *guessing* since I don't remember, but I think Windows is trying to
install the modem before the enumerator, since it finds the modem during a
hardware search, and the enumerator is software, though installed similarly.
If you don't allow it to try, but then set the install in motion from the
setup directory (where all the files you unzipped are) you can start it off
in the right direction--either by using a setup.exe (or whatever) *or* by
right-clicking on the brdgXXXX.INF file and clicking 'Install'. If there is
a setup.exe, that would probably be the better choice.

Hope it works,
Joe


  #10  
Old November 2nd 05, 12:38 AM
nownewbie
external usenet poster
 
Posts: n/a
Default Any Tapi/Dun/Modem Experts Question

on Tue 01 Nov 2005 12:44:17a, "jt3" wrote in
:

Yes, the brdgXXXX.inf is the one I meant. That's the memory
jog.


(some server probs, sorry if this dupes)
ok, thanks jt3. I've got about 4-5 things on my list to try now,
just sorting them out now, this is becoming a major project, haha.
Will let you know how things work out, or don't.
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Any Tapi/Dun/Modem Experts Question glee General 7 October 31st 05 03:35 AM
Hard Drive Question Yasoo General 6 March 14th 05 01:59 PM
Poledit question JohnDeeze General 0 December 6th 04 01:35 AM
restore files question and AVERT question Zavia Software & Applications 1 August 19th 04 04:23 PM
question on temp files PJ General 1 August 5th 04 11:52 AM


All times are GMT +1. The time now is 02:01 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.
Copyright 2004-2018 Win98banter.
The comments are property of their posters.