Re: Modem stopped working

From: Lena (lenav_at_prodigy.net)
Date: 07/17/03 

Date: Thu, 17 Jul 2003 18:20:21 GMT

> >>I'm assuming that this is this a dual-boot box where you can boot it
> >>into windows or SuSE? You might want to look to see what command
> >>strings are being sent to the modem under windows vs that under SuSE.
> >
> >
> > Yes, I am running a dual-boot with windows 98 on a desktop. My modem
> > is a Conexant HCF V90 Data Fax modem. I found where the modem command
> > string is under SuSE, but no idea where to look in windows...checked
> > Control Panel->modems and Dial-up networking->Yahoo->properties but
> > couldn't find anything that resembled a modem command string.
>
> Windows also keeps a log file. I'm sorry but I don't currently have a
> Win98 system here to play with, but have XP on my dual-boot laptop.
> Under XP it is a log file in the \WINDOWS directory.
>
> An easy way to find it is to go into a COMMAND prompt window and:
> cd \WINDOWS (perhaps this is WIN98 under Windows 98?)
>
> Then go dial your modem
> then in the COMMAND window do:
>
> dir /od
>
> that will give you a directory sorted by date. The last thing or nearly
> last thing that shows up should be the modem log file (since it was
> modified last). Doing this in my XP system shows a log file named after
> the modem:
>
> dir/od
>
> (much deleted)
>
> 07/14/2003 11:35 PM 22,666 Windows Update.log
> 07/14/2003 11:35 PM 22,666 ModemLog_Conexant-Ambit SoftK56
> Data,Fax ICH Modem.txt
> 07/17/2003 09:16 AM 0 0.log
> 51 File(s) 1,988,080 bytes
> 0 Dir(s) 1,853,112,320 bytes free
>
> C:\WINDOWS>
>
>
> I was thinking that it was a .log file, but I was wrong as on my XP
> system it is a .txt file. It is named after the modem however.
>
> - Bruce
>

Thanks Bruce! I found it. This is what it said:

<snip>
07-17-2003 12:18:14.74 - 115200,N,8,1
07-17-2003 12:18:14.74 - Initializing modem.
07-17-2003 12:18:14.74 - Send: AT<cr>
07-17-2003 12:18:14.75 - Recv: <cr><lf>OK<cr><lf>
07-17-2003 12:18:14.75 - Interpreted response: Ok
07-17-2003 12:18:14.75 - Send: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W0<cr>
07-17-2003 12:18:14.75 - Recv: <cr><lf>OK<cr><lf>
07-17-2003 12:18:14.75 - Interpreted response: Ok
07-17-2003 12:18:14.75 - Send: ATS7=60M1+ES=3,0,2;+DS=3;+IFC=2,2;X4<cr>
07-17-2003 12:18:14.76 - Recv: <cr><lf>OK<cr><lf>
07-17-2003 12:18:14.76 - Interpreted response: Ok
07-17-2003 12:18:14.76 - Dialing.
07-17-2003 12:18:14.76 - Send: ATDT;<cr>
07-17-2003 12:18:16.73 - Recv: <cr><lf>OK<cr><lf>
07-17-2003 12:18:16.73 - Interpreted response: Ok
07-17-2003 12:18:16.73 - Dialing.
07-17-2003 12:18:16.73 - Send: ATDT##########<cr>
07-17-2003 12:18:40.92 - Recv: <cr><lf>+MCR: V90<cr><lf>
07-17-2003 12:18:40.92 - Interpreted response: Informative
07-17-2003 12:18:40.92 - Recv: <cr><lf>+MRR: 49333<cr><lf>
07-17-2003 12:18:40.92 - Interpreted response: Informative
07-17-2003 12:18:41.52 - Recv: <cr><lf>+ER: LAPM<cr><lf>
07-17-2003 12:18:41.52 - Interpreted response: Informative
07-17-2003 12:18:41.52 - Recv: <cr><lf>+DR: V42B<cr><lf>
07-17-2003 12:18:41.52 - Interpreted response: Informative
07-17-2003 12:18:41.52 - Recv: <cr><lf>CONNECT 115200<cr><lf>
07-17-2003 12:18:41.52 - Interpreted response: Connect
07-17-2003 12:18:41.52 - Connection established at 49333bps.
07-17-2003 12:18:41.52 - Error-control on.
</snip>

the kinternet log showed:
<snip>
pppd: ATZ
pppd: OK
pppd: --> Sending: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
pppd: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
pppd: OK
pppd: --> Sending: ATM1
pppd: ATM1
pppd: OK
pppd: --> Modem initialized.
pppd: --> Sending: ATDT4105464279
pppd: --> Waiting for carrier.
pppd: ATDT4105464279
pppd: NO CARRIER
pppd: --> No Carrier! Trying again.
pppd: --> Sending: ATDT4105464279
</snip>

Unfortunately, I don't have much (meaning no) experience with modems. Any
ideas? or a link to a web page that may help?

Thanks!

Relevant Pages

  • Re: problems with wvdial
    ... I probably won't get back to looking into the failure modes ... pppd wants a "working" serial link and this is ... commands are evidently implemented by the modem, ... than a regular PSTN modem. ...
    (comp.os.linux.networking)
  • Re: problems with wvdial
    ... pppd wants a "working" serial link and this is ... commands are evidently implemented by the modem, ... than a regular PSTN modem. ... the peer. ...
    (comp.os.linux.networking)
  • Re: [SLE] Dialup problems
    ... What I have is a normal external 56k modem. ... Break the connection manually. ... # Defaultroute: no: pppd will not set the default route to the remote ip ...
    (SuSE)
  • Re: pppd does not set ppp0 interface
    ... >> I'm a Slackware fan but that script should be taken out and shot. ... > ABORT ERROR ... >> Here the ISP starts pppd and expects it's client to do the same. ... I had a difficult time getting an external Supra modem to dial and ...
    (comp.os.linux.networking)
  • Re: problems with wvdial
    ... When this happens, the modem sometimes locks up, at least ... specific failure mode at hand. ... thing that does the actual work, namely pppd. ...
    (comp.os.linux.networking)