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, 03:23 AM
glee
external usenet poster
 
Posts: n/a
Default Any Tapi/Dun/Modem Experts Question

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?

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.

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
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm


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



  #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.
  #4  
Old October 29th 05, 05:20 AM
glee
external usenet poster
 
Posts: n/a
Default Any Tapi/Dun/Modem Experts Question

"nonewbie" wrote in message ...
on Wed 26 Oct 2005 07:08:41p:

snip
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",


The Diagnostics tab is not in Device Manager, it is in Control PanelModems.

but there is no modem listed next to the com2 to which it is
assigned.


Where? In the Diagnostics tab of the Modems control panel? Or in Device Manager
under Ports? Or somewhere else? Please be specific about where you are looking in
each instance.
If no modem is listed next to COM2 in the Control Panel Modems Diagnostics tab,
then where are you finding it to request "More Info"?

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)


Again, what modem properties box, are you referring to, gotten to through what?

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.


So you still won't try that simple suggestion that would only take one minute? Are
you so sure that FC will tell you if there is a little bit-rot?


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.


....and ALL the removals were done from SAFE MODE....correct?

Reinstalled two comm ports,


You manually reinstalled them (bad idea), or you restarted in normal mode following
the Safe Mode removals, and Windows detected the COM ports....which?

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.


If you are referring to the ports listed in DM, the modem is not going to show up
there, regardless.

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.


Have you tried the suggestion in one of the other replies here, to uninstall the
Netgear Ethernet card, *and* the modem, and then reinstall them in a different
order?

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.


Sheesh....you paid $12 for the computer and you won't sink another $12 into a used
hardware modem from www.isellsurplus.com? The fact that the modem replies to the
info request in diagnostics has no bearing on whether the modem can connect out. I
have replaced countless modems that "pass" the Diagnostics info but are fried
(usually due to lightning surge) and will not connect out at all.

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.



How to Remove and Reinstall Dial-Up Networking and TCP/IP Files:
http://support.microsoft.com/?kbid=181599


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.


"Modem properties" where? Control Panel Modems, or elsewhere?
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm


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

on Fri 28 Oct 2005 09:20:34p, "glee"
wrote in :

"nonewbie" wrote in message
...
on Wed 26 Oct 2005 07:08:41p:

snip
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",


The Diagnostics tab is not in Device Manager, it is in Control
PanelModems.


I never said it wasn't. Please reread above. device mgr showed the
modem model name and no conflicts, working properly. Control panel
showed normal modem response to more info.

but there is no modem listed next to the com2 to which it is
assigned.


Where? In the Diagnostics tab of the Modems control panel? Or
in Device Manager under Ports? Or somewhere else? Please be
specific about where you are looking in each instance.
If no modem is listed next to COM2 in the Control Panel Modems
Diagnostics tab, then where are you finding it to request "More
Info"?

The modem itself is not listed only com2. This is supposedly
normal for pci enumerator modems, according to other reports. On
clicking where the modem would normally be listed in the empty box
next to com2 I get the normal feedback response from the modem
with all the at command info. No disrespect intended,but do you
have anything of substance to offer or are u just asking more
questions?

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)


Again, what modem properties box, are you referring to, gotten
to through what?


to tell the truth I cannot recall. But one thing is sure the
control panel-system shows the exact modem as working no
conflicts, but other boxes that are supposed to contain the modem
name are blank. If memory serves one was under the modems icon in
control panel.

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.


So you still won't try that simple suggestion that would only
take one minute? Are you so sure that FC will tell you if there
is a little bit-rot?


FC tells gives you "no differences" That means that the two files
are identical bit by bit.


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.


...and ALL the removals were done from SAFE MODE....correct?

Reinstalled two comm ports,


You manually reinstalled them (bad idea), or you restarted in
normal mode following the Safe Mode removals, and Windows
detected the COM ports....which?


did it both ways and inbetween each install removed all modems and
comm ports.PNP puts back com1 automatically. Followed the
recommended method of removing driver package from add/remove and
letting windows attemp to reinstall the drivers after I told
windows where to find them. But actually the recommended way that
comes with the driver file is to let setup install the driver
package, not windows. Doesn't matter, did it both ways, same
result. One post indicated that you must have the modem install
diskette that supposedly has special files for installing the
modem, but I don't believe that since both dell and another driver
source both offer a set of files with setup.exe and I followed
their procedures and get the same result-drivers appear to install
ok and cannot create DUN to modem, which wants me to install the
drivers that have already been installed. Many complaints for
others with this SAME problem and guess what? A myriad of
different solutions with no clear definitive answer. MS offers two
fixes neither of which works (their telephon.ini fix and
associated registry fix and their re extract the unimodem.tsp, for
corrupted files, which this is not an instance of) This is another
example of a crap OS and crap support, sorry all you MS
programmers and devotees, but that is my opinion, take it or leave
it.


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.


If you are referring to the ports listed in DM, the modem is not
going to show up there, regardless.


Ok then why are u asking me where I got if from?

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.


Have you tried the suggestion in one of the other replies here,
to uninstall the Netgear Ethernet card, *and* the modem, and
then reinstall them in a different order?


No, not yet. No one, including you has given me a rational as to
why that might even work. And, knowing windows the more
unsubstanciated messing I do with it, the greater the likelyhood
that the OS will simply not boot following such procedures. If you
can give me a rational reason as to why this might work, I will
try it.


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.


Sheesh....you paid $12 for the computer and you won't sink
another $12 into a used hardware modem from
www.isellsurplus.com? The fact that the modem replies to the
info request in diagnostics has no bearing on whether the modem
can connect out. I have replaced countless modems that "pass"
the Diagnostics info but are fried (usually due to lightning
surge) and will not connect out at all.


It is not a question of money, but I am just ****ed I cannot get
it to work. If I bought new hardware everytime Windows screwed up
I would not have room for all the equipment. I think the modem is
ok else it would not respond normally to the more info command. It
is the crap OS that is too stupid to correctly install the
winmodem and a winmodem that has a history of being junk judging
from all the complaints about it at dell's website and elsewhere.


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.



How to Remove and Reinstall Dial-Up Networking and TCP/IP Files:
http://support.microsoft.com/?kbid=181599



Do not think this will do it-too many posts of others who have
reinstalled dun with no effect.


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.


"Modem properties" where? Control Panel Modems, or elsewhere?


Modems, as best I can recall

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

"newbie" wrote in message ...
on Fri 28 Oct 2005 09:20:34p, "glee"
wrote in :

snip
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",


The Diagnostics tab is not in Device Manager, it is in Control
PanelModems.


I never said it wasn't. Please reread above. device mgr showed the
modem model name and no conflicts, working properly. Control panel
showed normal modem response to more info.


I already re-read it numerous times before replying....you never mentioned Control
Panel Modems in that context, which is why I made the clarification. Your
statement "The modem appears ok in the Device mgr under systems, and responds to
"more info-diagnostics with the parameter readout"" mentions it as if it were all in
Device Manager.


but there is no modem listed next to the com2 to which it is
assigned.


Where? In the Diagnostics tab of the Modems control panel? Or
in Device Manager under Ports? Or somewhere else? Please be
specific about where you are looking in each instance.
If no modem is listed next to COM2 in the Control Panel Modems
Diagnostics tab, then where are you finding it to request "More
Info"?

The modem itself is not listed only com2. This is supposedly
normal for pci enumerator modems, according to other reports. On
clicking where the modem would normally be listed in the empty box
next to com2 I get the normal feedback response from the modem
with all the at command info. No disrespect intended,but do you
have anything of substance to offer or are u just asking more
questions?


Your descriptions of where you are seeing various readouts have been slightly
unclear, and I want a clear picture of what you are seeing where, which is why I am
asking questions for clarification. You need to remember we cannot see your
computer screen and have to rely on clear descriptions in order to "see' what you
are looking at. :-)

It appears from what you are writing in this reply, above and below, that in Control
Panel Modems Diagnostics tab, you are seeing COM2 but with a blank where the modem
name should be....yet selecting that blank name is allowing you to get a successful
readout. If that's the case, then NO, that is *not* normal for an HCF modem with an
enumerator. I am currently using a Broadxent DSI v.92 HCF modem with an enumerator
in Device Manager, AND its own listing under Modems in DM, and it appears with a
name in the Diagnostics tab.....as have all the other HCF and HSF modems I have had
the bad luck to work with. ;-) The fact that you see no name at all indicates to
me at least, that the .inf file used is incorrect, incomplete or being mis-read
somehow at installation. I need to read your replies to Franc to see what if
anything you posted regarding the inf files used and their contents. Franc and jt3
have already given you some info on the inf files and registry keys involved, so I
will look over that info before adding anything redundant, if that's OK with you.


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)


Again, what modem properties box, are you referring to, gotten
to through what?


to tell the truth I cannot recall. But one thing is sure the
control panel-system shows the exact modem as working no
conflicts, but other boxes that are supposed to contain the modem
name are blank. If memory serves one was under the modems icon in
control panel.


OK....again that indicates that there may have been a problem reading the inf file,
or the Registry entries it was supposed to create were messed.

...and ALL the removals were done from SAFE MODE....correct?

Reinstalled two comm ports,


You manually reinstalled them (bad idea), or you restarted in
normal mode following the Safe Mode removals, and Windows
detected the COM ports....which?


did it both ways and inbetween each install removed all modems and
comm ports.PNP puts back com1 automatically. Followed the
recommended method of removing driver package from add/remove and
letting windows attemp to reinstall the drivers after I told
windows where to find them. But actually the recommended way that
comes with the driver file is to let setup install the driver
package, not windows. Doesn't matter, did it both ways, same
result. One post indicated that you must have the modem install
diskette that supposedly has special files for installing the
modem, but I don't believe that since both dell and another driver
source both offer a set of files with setup.exe and I followed
their procedures and get the same result-drivers appear to install
ok and cannot create DUN to modem, which wants me to install the
drivers that have already been installed. Many complaints for
others with this SAME problem and guess what? A myriad of
different solutions with no clear definitive answer. MS offers two
fixes neither of which works (their telephon.ini fix and
associated registry fix and their re extract the unimodem.tsp, for
corrupted files, which this is not an instance of) This is another
example of a crap OS and crap support, sorry all you MS
programmers and devotees, but that is my opinion, take it or leave
it.


No problem, though I think it is a problem more with the modem or its inf
files/installer, than with Windows.


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.


If you are referring to the ports listed in DM, the modem is not
going to show up there, regardless.


Ok then why are u asking me where I got if from?


Because you are not giving clear descriptions of *where* you are or are not seeing
these things. I am referring to Device Manager Ports section.....you will *not*
see the HCF modem listed there, that is normal. You will not see ANY modem listed
there regardless of its type. Where you *will* see a port and modem associated with
each other is on the properties sheets of the modem in the Modems control panel, and
in DM's Modems section on the properties sheets for the listed modems. It sounds
like you are referring to the Ports section, which is not going to show *any*.



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.


snip for now



Sheesh....you paid $12 for the computer and you won't sink
another $12 into a used hardware modem from
www.isellsurplus.com? The fact that the modem replies to the
info request in diagnostics has no bearing on whether the modem
can connect out. I have replaced countless modems that "pass"
the Diagnostics info but are fried (usually due to lightning
surge) and will not connect out at all.


It is not a question of money, but I am just ****ed I cannot get
it to work. If I bought new hardware everytime Windows screwed up
I would not have room for all the equipment. I think the modem is
ok else it would not respond normally to the more info command. It
is the crap OS that is too stupid to correctly install the
winmodem and a winmodem that has a history of being junk judging
from all the complaints about it at dell's website and elsewhere.


But you aren't looking at the possibility that the modem itself may be bad.

You say the modem is shown on COM2? Do you have COM2 disabled or enabled in the
BIOS?
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm


  #7  
Old October 30th 05, 11:43 PM
nonewbie
external usenet poster
 
Posts: n/a
Default Any Tapi/Dun/Modem Experts Question

on Sun 30 Oct 2005 03:40:13p, "glee"
wrote in :

"newbie" wrote in message
...
on Fri 28 Oct 2005 09:20:34p, "glee"
wrote in :

snip
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",

The Diagnostics tab is not in Device Manager, it is in
Control PanelModems.


I never said it wasn't. Please reread above. device mgr showed
the modem model name and no conflicts, working properly.
Control panel showed normal modem response to more info.


I already re-read it numerous times before replying....you never
mentioned Control Panel Modems in that context, which is why I
made the clarification. Your statement "The modem appears ok in
the Device mgr under systems, and responds to "more
info-diagnostics with the parameter readout"" mentions it as if
it were all in Device Manager.


but there is no modem listed next to the com2 to which it is
assigned.

Where? In the Diagnostics tab of the Modems control panel?
Or in Device Manager under Ports? Or somewhere else? Please
be specific about where you are looking in each instance.
If no modem is listed next to COM2 in the Control Panel
Modems Diagnostics tab, then where are you finding it to
request "More Info"?

The modem itself is not listed only com2. This is supposedly
normal for pci enumerator modems, according to other reports.
On clicking where the modem would normally be listed in the
empty box next to com2 I get the normal feedback response from
the modem with all the at command info. No disrespect
intended,but do you have anything of substance to offer or are
u just asking more questions?


Your descriptions of where you are seeing various readouts have
been slightly unclear, and I want a clear picture of what you
are seeing where, which is why I am asking questions for
clarification. You need to remember we cannot see your computer
screen and have to rely on clear descriptions in order to "see'
what you are looking at. :-)


Yes, I know, sorry.


It appears from what you are writing in this reply, above and
below, that in Control Panel Modems Diagnostics tab, you are
seeing COM2 but with a blank where the modem name should
be....yet selecting that blank name is allowing you to get a
successful readout. If that's the case, then NO, that is *not*
normal for an HCF modem with an enumerator. I am currently
using a Broadxent DSI v.92 HCF modem with an enumerator in
Device Manager, AND its own listing under Modems in DM, and it
appears with a name in the Diagnostics tab.....as have all the
other HCF and HSF modems I have had the bad luck to work with.
;-) The fact that you see no name at all indicates to me at
least, that the .inf file used is incorrect, incomplete or being
mis-read somehow at installation. I need to read your replies
to Franc to see what if anything you posted regarding the inf
files used and their contents. Franc and jt3 have already given
you some info on the inf files and registry keys involved, so I
will look over that info before adding anything redundant, if
that's OK with you.


Yes I believe ur above interpretation is correct.

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)

Again, what modem properties box, are you referring to,
gotten to through what?


to tell the truth I cannot recall. But one thing is sure the
control panel-system shows the exact modem as working no
conflicts, but other boxes that are supposed to contain the
modem name are blank. If memory serves one was under the modems
icon in control panel.


OK....again that indicates that there may have been a problem
reading the inf file, or the Registry entries it was supposed to
create were messed.


very well could be, since removing all registry entries that refer
to this particular modem, windows created new registry entries
that are different from previous and each time i boot now it asks
for the modem installation diskette (don't have orginal). Detail
of this are in response to Franc's reply. I am hoping that this
registry clean will facilitate the correct install of the new
drivers. Also found one post from a guy who could not get the dell
updated drivers to install, so I obtained even older version of
the driver package from dell to see if this makes any difference,
but the files seem quite similar across all install packages.
Looked at the inf files from one of them and was suprised to find
them catalogued as win2000 drivers even though I d/l them under
win98 driver, so maybe the initial install of this package
corrupted the registry. Also reinstalled unimdm.tsp despite file
compares readout that the one already there is identical.

...and ALL the removals were done from SAFE MODE....correct?


tried it both ways-regular and safe mode, but now I am back to a
virgin system as far as the modem registry entries go, or nearly.
MS says you have to delete all registry entries assoc. with
winmodems before reinstall in order for os to detect them.
However, they do not say which entries and I had to find them
through research. One mfg. and ms has an executable to do this but
not for the mdp3880-w(u) modem.


Reinstalled two comm ports,

You manually reinstalled them (bad idea), or you restarted in
normal mode following the Safe Mode removals, and Windows
detected the COM ports....which?


did it both ways and inbetween each install removed all modems
and comm ports.PNP puts back com1 automatically. Followed the
recommended method of removing driver package from add/remove
and letting windows attemp to reinstall the drivers after I
told windows where to find them. But actually the recommended
way that comes with the driver file is to let setup install the
driver package, not windows. Doesn't matter, did it both ways,
same result. One post indicated that you must have the modem
install diskette that supposedly has special files for
installing the modem, but I don't believe that since both dell
and another driver source both offer a set of files with
setup.exe and I followed their procedures and get the same
result-drivers appear to install ok and cannot create DUN to
modem, which wants me to install the drivers that have already
been installed. Many complaints for others with this SAME
problem and guess what? A myriad of different solutions with no
clear definitive answer. MS offers two fixes neither of which
works (their telephon.ini fix and associated registry fix and
their re extract the unimodem.tsp, for corrupted files, which
this is not an instance of) This is another example of a crap
OS and crap support, sorry all you MS programmers and devotees,
but that is my opinion, take it or leave it.


No problem, though I think it is a problem more with the modem
or its inf files/installer, than with Windows.


could be the modem, lots of complaints for others even after they
got it installed.


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.

If you are referring to the ports listed in DM, the modem is
not going to show up there, regardless.


no i think it was under "modems" in control panel.

Ok then why are u asking me where I got if from?


Because you are not giving clear descriptions of *where* you are
or are not seeing these things. I am referring to Device
Manager Ports section.....you will *not* see the HCF modem
listed there, that is normal. You will not see ANY modem listed
there regardless of its type. Where you *will* see a port and
modem associated with each other is on the properties sheets of
the modem in the Modems control panel, and in DM's Modems
section on the properties sheets for the listed modems. It
sounds like you are referring to the Ports section, which is not
going to show *any*.

Yes, the above is the way it was. did not mean ports section,
meant modems/control panel and dm's modems icon. sorry for the
confusion.


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.


snip for now



Sheesh....you paid $12 for the computer and you won't sink
another $12 into a used hardware modem from
www.isellsurplus.com? The fact that the modem replies to the
info request in diagnostics has no bearing on whether the
modem can connect out. I have replaced countless modems that
"pass" the Diagnostics info but are fried (usually due to
lightning surge) and will not connect out at all.


It is not a question of money, but I am just ****ed I cannot
get it to work. If I bought new hardware everytime Windows
screwed up I would not have room for all the equipment. I think
the modem is ok else it would not respond normally to the more
info command. It is the crap OS that is too stupid to correctly
install the winmodem and a winmodem that has a history of being
junk judging from all the complaints about it at dell's website
and elsewhere.


But you aren't looking at the possibility that the modem itself
may be bad.


suppose it is possible, but my experience is that if modem gives
proper readout from "more info" hardware is ok.


You say the modem is shown on COM2? Do you have COM2 disabled
or enabled in the BIOS?


tried it both ways had even had it assigned to different ports and
irqs during all of this with no positive effect. I think ur
correct it has something to do with the inf files not being
integrated properly into the rest of the system, just not sure
why, since I am using the packages that supposedly came with the
system. will try the older version tonight and see if it makes a
diff. thanks for your help. if i can solve this it will also help
several others that have posted identical problems, often with no
response. also have to look at the site Franc gave to see if there
are any special install instructions i have not yet come across.

  #8  
Old October 31st 05, 03:35 AM
glee
external usenet poster
 
Posts: n/a
Default Any Tapi/Dun/Modem Experts Question

"nonewbie" wrote in message ...
on Sun 30 Oct 2005 03:40:13p, "glee"
wrote in :
massive snip
But you aren't looking at the possibility that the modem itself
may be bad.


suppose it is possible, but my experience is that if modem gives
proper readout from "more info" hardware is ok.


Oh, heck no! It is quite typical for a modem to give a "proper readout" in "More
info", but not be able to connect, after damage from an electrical surge, such as
from lightning. I have replaced *lots* of modems with that issue.

Trying to get to Franc's post now....I am pretty busy here at the moment. Did you
try a Hyperterminal session with the modem?
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm

 




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
Hard Drive Question Yasoo General 6 March 14th 05 01:59 PM
Poledit question JohnDeeze General 0 December 6th 04 01:35 AM
New Install of Windows & W-TShooters question Star General 26 August 30th 04 07:48 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 10:14 AM.


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