Paul Miller writes:
> I have opened Minicom, and I get the NO CARRIER response as soon as it
> opens. This would be in response to the initialization string that
> Minicom uses. I can then succesfully send any AT commands after that.
Replaces 'OK' with 'OK-AT-OK' . This tells chat to expect 'OK',
John Hasler wrote:
>
> Paul Miller writes:
> > I get the NO CARRIER in response to the ATZ command. This is the first AT
> > command sent to the modem.
>
> That sounds like a modem problem. Try connecting to the modem with minicom
> and sending it ATZ.
I have opened Minicom, and I get the NO CA
Paul Miller writes:
> I get the NO CARRIER in response to the ATZ command. This is the first AT
> command sent to the modem.
That sounds like a modem problem. Try connecting to the modem with minicom
and sending it ATZ.
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, W
Sandy Kear wrote:
>
> At 10:09 PM 6/27/99 -0500, you wrote:
> >Hi everybody,
> >
> >Ever since upgrading to the 2.2.x Kernel, I have had strange things
> >happening with my modem. It is a NewComm 33.6Kbps ISA PnP Fax/Modem (now
> >that's a mouth full).
> >
> >I have isapnp set up correctly to init
Hi everybody,
Ever since upgrading to the 2.2.x Kernel, I have had strange things
happening with my modem. It is a NewComm 33.6Kbps ISA PnP Fax/Modem (now
that's a mouth full).
I have isapnp set up correctly to initialize the modem, and I know it
works as the modem still dials out and connects.
5 matches
Mail list logo