On Thu, 3 Sep 1998 [EMAIL PROTECTED] wrote:
> If a not fully decoded COM4 address interferes with my VGA, then why would the
> modem ever work, and why would it normally hang up successfully? Why would the
> modem hang only when the connection goes bad at the other end?
Good point. What made me think of a hardware conflict was that this
problem consist in other OSes too. AFAIK the 8514/A compatible cards (S3,
Mach8/32 etc.) use ports like 0x42e8, 0x46e8, 0x4ae8, 0x4ee8, 0x92e8 etc..
I have no idea about programming such a device. But if your RS232-ISA card
(just guessing) doesn't decode /correctly all of the 16 address bits on
the bus ... . A normal ppp connection is disconnected by sending +++ATH to
the modem <and> toggling DTR (anyone correct me if I'm wrong).
Other way round:
I assume you have an external modem connected to COM4. Are
there some more modems connected to this computer? Does exchanging modems
make any difference? Is a connection going bad "couldn't establish modem
connection" or is it "couldn't log in"?
If it's the first one then there's something wrong with the modem.
Normally a modem is supposed to hang up if connection is lost (time to
hangup in modem register S10).
The second one is a bit more tricky. The DTR hangup is used with the
'hardware' parameter in ppp (modem set to &D3/register S25 - make sure
this is set <after> any Z and &F[x] modem command, and if
possible not in the same line - some modems ignore any command after Z).
But the handling on this is up to the OS which leads me back to the
problem that this problem happens in all your OSes. And that the COM port
will be blocked doesn't sound like a modem problem.
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
