Re: 770Z: Error 630 when using modem

New Message Reply Date view Thread view Subject view Author view Attachment view

From: Allan Ballard (aballard_at_ix.netcom.com)
Date: Tue Oct 05 1999 - 20:12:23 EDT


You can ATDT<actual phone number> to get a good idea what is not going on.
ATH will hang up when you need to.

If on the wrong port, well, gotta get that right first. If the port is
disabled, then enable it in TP utilities, or delete it in Device Manager and
boot, so that it will be re-added.

All the 3 commas will do is induce a pause.

Worst case, delete the modem and readd. Make it go away totally from device
manager. Then check the com port it landed on very carefully. Then check
your apps to make sure they have the same com port setting.

If you can find an old DOS app, like Procom, they are much better than
Hyperterm for tinkering around with modems.

-----Original Message-----
From: John Fenk <fenk_at_agora.rdrop.com>
To: Thinkpad_at_cs.utk.edu <Thinkpad_at_cs.utk.edu>
Date: Tuesday, October 05, 1999 7:06 PM
Subject: Re: 770Z: Error 630 when using modem

>At 10:37 AM 9/30/99, you wrote:
>>Make sure in Hyperterminal you use: File --> Properties --> Direct to
COMx
>>where COMx is the port the modem is configured. Then: Configure --> Flow
>>Control --> Hardware.
>>Once these are set you may need to "blind type" AT&F or ATE0Q1 to turn
"on"
>>echo and modem responses. "Blind type" means typing without getting any
>>feedback until you hit RETURN. You should get OK after hitting RETURN.
>>
>> >
>> >Also you mention a modem log. Do you know how I produce one? That
sounds
>> >like it would be useful.
>>
>>Control Panel --> Modems --> Properties --> Connection -->
>>Advanced -->Record a log file
>>
>>If one of the PC cards is ethernet, you could replace it with a combo
>>modem/ethernet.
>>I agree the 770 internal should work fine at 33.6. Have you considered
>>reinstalling the OS from scratch to try to fix your problem? These types
of
>>problems can be caused by "power management" issues. Test to see if a
>>suspend operation is the precursor to the modem trouble.
>>
>>Aaron Brown.
>
>Thanks. I had the problem again twice today after I started recording the
>modem log. When I get error, there is nothing at all added to the log
>file. I didn't get to try out the hyperterminal because I just figured out
>that the modem is on COM2. I had thought it was COM1. I called IBM and
>they looked up the error on microsoft's web site and had me try two
>workarounds - removing the check mark from the modem properties "wait for
>dial tone" and putting three commas in front of the phone number and then
>reboot. I don't think this will help, but I'll do it and just call them
>again when it happens. There was a suspend today before each error, but I
>know that it has happened without there having been a suspend
>operation. Thanks again for the help.
>
>--
>John Fenk
>fenk_at_agora.rdrop.com
>(503) 641-8036


New Message Reply Date view Thread view Subject view Author view Attachment view

This archive was generated by hypermail 2.1.3 : Thu Jan 23 2003 - 09:55:27 EST