Newsgroup: it.comp.hardware
Titolo: Phoebe 33.6 Data/Fax/Voice & Windows 95 Dial-up Networking

Hello, I'm running Win95 on a 133Mhz Pentium Intel Chipset. I have a
"Phoebe" (US Robotics compatible) internal 33.6 modem. It works like a
charm in all but one respect. It simply won't dial the phone using a
Dial-Up Networking connection. It pretends to, but it doesn't even
initialize the modem, hence, no dial tone. I get an error message after
it pretends to dial - no dialing sounds occur - that states, line busy,
try again later. This was very perplexing until I ran across a Knowledge
Base article on the Microsoft web site	this article gave me an extra
modem string to put in the Dial-Up Networking connectoid. I think this
might even work, except for the fact that the modem string is for a
Phoebe 28.8 modem. I even tried it, no luck. I tend to think that this
problem is hardware specific, because I loaded Windows 95, Plus!, Service
Pak, and MSN (The Microsoft Network) identically to a P75 I have in
another room. Yes, of course the systems are not identical, given the
differences in motherboards and processors.
So, my question is, does anyone, like you who are reading this, know of
the extra modem string to put in my DUN connectoid that is specific to
this particular modem?
It could be that my reasoning is faulty regarding this problem, or I
could be overlooking something in the configuration, or hardware
settings. Let me know if you have any ideas. Thank you.
Brook Hatch
Microsoft Corporation
Lincoln Plaza Desktop Support
-------------------==== Posted via Deja News ====-----------------------
 
http://www.dejanews.com/
     Search, Read, Post to Usenet

 this particular modem?
I had a similar problem with a brand new PC, that had a Logicode Modem.
Modem worked fine, but DUN wouldn't dial. I deleted the modem driver and
had Windows 95 autodetect my modem. It used a standard modem driver. And
voila, everything works fine (as far as I can tell). Give that a shot.
-- 
+---------------------------------+------------------------------------+
| Paige Miller                    | "Few things are harder to put up   |
| Eastman Kodak Company           | with than the annoyance of a good  |
| 
Pai...@kodak.com
                | example" -- Mark Twain             |
+---------------------------------+------------------------------------+
| The opinions expressed herein do not necessarily reflect the         |
| views of the author nor the views of the Eastman Kodak Company.      |
+----------------------------------------------------------------------+

 
Hi Brook
1. When you encounter any problems with your modem you should activate
the LOG file option in your modem properties under settings\advanced (as
I'm using a german Windows version I don't exactly know the english
button/window/dialog titles). Then try a connection and
after you've got the error message have a look at the MODEMLOG.TXT file
in your windows directory. There you can follow the dialog between
software and modem.
2. You say that it works like a charm. Does that mean that you have been
able to use other applications with your modem (DIALER.EXE etc) and only
DUN doesn't work? If so the init string can't be that bad.
As far as I know there's only one interface in the system and any
application that wants to access the modem must use this interface. This
means that there's only one modem configuration. There are several ways
to change the initialization sting (and other parameters):
first     directly via controlpanel\modems
second    from DUN via conection properties
third     from DIALER.EXE (CCDIALER) via dialling parameters
last      from any software that accesses the modem
But whatever way possibility you select you always simply enter the
modem configuration dialog. You can check this by simply changing
parameters from within DUN and then look at DIALER or controlpanel.
You see, if other applications work with your modem but DUN doesn't, the
reason must be looked for elsewhere in tour connection properties.
If, however, none of your applications work with the modem, you should
go to controlpanel\modem properties and select the diagnosis tab and let
the system perform the modem test. If you see lots of reactions from the
modem (e.g. chipset, id etc), your hardware is ok and you must fiddle
with your connection properties.
If you don't see any proper reaction you should check if everything is
ok with the interrupt assigned. Are you using internal or external
drivers (provided by the manufacturer)?
Another possibility is to delete the modem from the system configuration
and then start the hardware assistant and install a STANDARD MODEM or
standard 28.800 modem. ANY modem should work this way. If yours does,
too, you know at least that it works. And that ist better than nothing,
isn't it. Of course, this way you can't use most of the features. But
its a starting point. Perhaps you should look for other drivers.
To mention the init string once more: If you enter a string in the
configuration dialog this string as added to the internally stored
original initialisation string. Both strings are stored in the Registry
under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Modem\
0000\Settings\Init. Under this key you will find the entries STANDARD, 1
and 2. 1 contains the original string, 2 shows the one you entered.
To completely change the string you must edit the value of "1". But
don't forget to backup the original value (mark the key INIT in the left
window, then ckick REGISTRY, EXPORT and enter a file name [regedit will
add the extension .reg], restoring can be done anytime by doubleclicking
the file.)
Henning
vo...@wad.org
 (Hans-Henning Vossieck)