View Single Post
  #7  
Old October 31st 05, 12:43 AM
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.