HP3000-L Archives

May 1996, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Bob Jankalski <[log in to unmask]>
Reply To:
Bob Jankalski <[log in to unmask]>
Date:
Thu, 23 May 1996 23:02:21 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
It's possible that messages from the modem (i.e. "OK", "CARRIER" etc.)
are causing the port to start speed sensing. The ideal situation would
be for the modem to soft reset (probably AT&D3) and then say nothing
to the port (probably ATQ1) when DTR is dropped. This way the first
thing that the port will see when someone connects is the remote user
pressing carriage return to get a prompt. I'm assuming a lot here such
as the proper cabling, speed sensing and modem control enabled for the
port, DSR forced on by the modem, and CD not forced but showing the
true state of the detected carrier.
 
Bob Jankalski -- Ideal Computer Services
 
 
 
On Thu, 23 May 1996, Mike Farrell wrote:
 
> I have a Practical Peripheral PM144MT II modem hooked to one of my DTC
> ports which we use to dial in to our system. Once we have connected and
> completed our business we say :BYE and then use the Hayes command +++ to
> disconnect. But, the next time I try to dialin to the same port it
> appears to be busy. A showdev on the port reports SYS #1. Unless I have
> someone do an abortio on the port I cannot get access to that port.
> Anyone experience this type of problem. Is there a modem setting that
> needs to be changed? maybe a port config setting?
>
> Humbly,
>
>
>
>
> --
> Mike Farrell
> Intermountain Gas Company
> Data Center Operations Supervisor
> 555 South Cole Road
> Boise,  ID  83707
>

ATOM RSS1 RSS2