View Single Post
  #5  
Old October 30th 05, 10: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