Hi,
The suggestion was something that I already tried, but basically, it seems a case of the COM port being there, and being able to send signals 'out', but somehow not getting anything back. Again, the example is that COM3 & 4 appear OK in the device manager, but seem to fail with all devices (modem being my test/debug device at the moment), but I have tried a mouse and digital camera output as well.
From the modem log, I see this (the modem works fine on COM1 or COM2):
08-03-1997 20:57:39.95 - TNC MERZ336 HI SPEED FAX MODEM in use.
08-03-1997 20:57:39.96 - Modem type: TNC MERZ336 HI SPEED FAX MODEM
08-03-1997 20:57:39.96 - Modem inf path: MERZ3361.INF
08-03-1997 20:57:39.96 - Modem inf section: Modem1
08-03-1997 20:57:40.21 - 115200,N,8,1
08-03-1997 20:57:40.26 - 115200,N,8,1
08-03-1997 20:57:40.28 - Initializing modem.
08-03-1997 20:57:40.28 - Send: AT<cr>
08-03-1997 20:57:42.28 - Recv: <no response>
08-03-1997 20:57:42.28 - WARNING: Unrecognized response. Retrying...
08-03-1997 20:57:42.28 - Send: AT<cr>
08-03-1997 20:57:44.29 - Recv: <no response>
08-03-1997 20:57:44.29 - WARNING: Unrecognized response. Retrying...
08-03-1997 20:57:44.29 - Send: AT<cr>
08-03-1997 20:57:46.29 - Recv: <no response>
08-03-1997 20:57:46.29 - WARNING: Unrecognized response. Retrying...
08-03-1997 20:57:46.29 - Send: AT<cr>
08-03-1997 20:57:48.30 - Recv: <no response>
08-03-1997 20:57:48.30 - WARNING: Unrecognized response. Retrying...
08-03-1997 20:57:48.30 - Send: AT<cr>
08-03-1997 20:57:50.30 - Recv: <no response>
08-03-1997 20:57:50.30 - ERROR: Unable to recover from unrecognized response.
08-03-1997 20:57:50.30 - Hanging up the modem.
08-03-1997 20:57:50.55 - Session Statistics:
08-03-1997 20:57:50.55 - Reads : 0 bytes
08-03-1997 20:57:50.55 - Writes: 15 bytes
08-03-1997 20:57:50.55 - TNC MERZ336 HI SPEED FAX MODEM closed.
Main Topics
Browse All Topics
by: smeebudPosted on 1997-08-03 at 07:54:38ID: 1749932
Check it out with a modemdet.log, then get back with me,
----------
To enable the creation of the Modemlog.txt file, follow these steps:
1. In Control Panel, double-click Modems.
2. Click the modem you want to create a log file for, and then
click Properties.
3. On the Connection tab, click Advanced.
4. Click the Record A Log File check box to select it, and then
click OK.
5. Click OK, and then click Close.
After you follow the above steps, the Modemlog.txt file is written to
whenever a communications session is established by a TAPI-enabled
communications program (such as HyperTerminal, Phone Dialer, or
Dial-Up Networking). Note that programs that are not TAPI-enabled do
not log information to the Modemlog.txt file. The Modemlog.txt file is
located in the Windows folder.
The entries in the Modemlog.txt file have the following format:
<Time/Date> <Message/Status Information>
The following is a sample Modemlog.txt file with explanations. Note
that explanations do not appear in an actual Modemlog.txt file. The
contents of an actual Modemlog.txt file may differ greatly from this
sample file.
Sample Modemlog.txt File
05:02:56 05-25-1994 - TI V.32Bis-V17 Internal in use. 05:02:55
05-25-1994 - Modem Type: TI V.32bis-V.17 Internal
A program has called TAPI to open this modem's line handle.
Unimodem.tsp called the Win32 function to open a file handle to
Unimodem.vxd for this modem.
05:02:56 05-25-1994 - 38400,N,8,1
Unimodem has called VCOMM to open the correct serial port for this
modem, and set its default COM port settings.
05:02:56 05-25-1994 - Initializing modem. 05:02:56 05-25-1994 - Send:
AT
Unimodm sends an 'AT' to initialize the modem's autobaud setting.
05:02:57 05-25-1994 - Recv: AT<CR><CR><lf>OK<CR><lf> 05:02:57
05-25-1994 - Interpreted response: OK
The "AT<CR>" is echoed back by the modem, along with an "OK"
response code. Unimodem discards the echoed command, and correctly
interprets the OK response.
05:02:57 05-25-1994 - Send: AT &F0 05:02:59 05-25-1994 - Recv: AT &F0
<CR><CR><lf>OK<CR><lf> 05:02:59 05-25-1994 - Interpreted response: OK
Unimodem sends the first initialization string specified in the
.inf file, discards the echoed command, and interprets the OK response
correctly.
05:02:59 05-25-1994 - Send: AT E0 Q0 V0 W1 T L2 M1 &C1 05:03:01
05-25-1994 - Recv: AT E0 Q0 V0 W1 T L2 M1 &C1 <CR>0<CR> 05:03:01
05-25-1994 - Interpreted response: OK
Unimodem sends the second initialization string from the .inf
file. The command is echoed back, and numeric response codes are now
in use.
05:03:01 05-25-1994 - Send: AT &D2 &S0 X4 %C1 \JO \N7 \Q3 \V1 \T0
05:03:03 05-25-1994 - Recv: 0<CR>
Unimodem successfully sends the third initialization string from
the .inf file. Note that this command is not echoed back by the modem.
05:03:03 05-25-1994 - Send: ATS7=50\T0L2M1%C1\N7\Q3B1X
05-25-1994 - Recv: 0<CR> 05:03:04 05-25-1994 - Interpreted response:
OK
This is the dynamic initialization stage. Unimodem sent a string
to configure the modem to settings requested by the user or program.
The command string is built dynamically based on registry keys
originally specified by Settings values in the .inf file.
05:03:04 05-25-1994 - Dialing ". 05:03:04 05-25-1994 - Send: ATX4
05:03:06 05-25-1994 - Recv: 0<CR> 05:03:07 05-25-1994 - Interpreted
response: OK
Unimodem first sets dial tone detection on.
05:03:07 05-25-1994 - Send: ATDT; 05:03:09 05-25-1994 - Recv: 0<CR>
05:03:09 05-25-1994 - Interpreted response: OK
Unimodem takes the modem off-hook.
05:03:09 05-25-1994 - Dialing '9555 1212' 05:03:04 05-25-1994 - Send:
ATX4 05:03:11 05-25-1994 - Recv: 0<CR> 05:03:11 05-25-1994 -
Interpreted response: OK 05:03:11 05-25-1994 - Send: ATDT9555 1212;
05:03:15 05-25-1994 - Recv: 0<CR> 05:03:15 05-25-1994 - Interpreted
response: OK
Unimodem dials the phone number provided by the program via TAPI.
05:03:15 05-25-1994 - Originating the call. 05:03:15 05-25-1994 -
Send: ATX3D
Unimodem originates the call. Note that "X3" is included because
this modem will not work correctly without it. Some modems do not
require this.
05:03:30 05-25-1994 - Recv: 52<CR>77<CR>69<CR> 05:03:30 05-25-1994 -
Interpreted response: Ignore
"Ignore" is misleading. Here, Unimodem recognized "52<CR>" as a
call progress response code.
05:03:30 05-25-1994 - Recv: 77<CR>69<CR> 05:03:30 05-25-1994 -
Interpreted response: Ignore
Unimodem recognized "77<CR>" as a call progress response code.
05:03:30 05-25-1994 - Recv: 69<CR> 05:03:30 05-25-1994 - Interpreted
response: Connect
Unimodem recognized "69<CR>" as indication of a connection.
05:03:30 05-25-1994 - Connection established at 14400bps. 05:03:30
05-25-1994 - Error-control activated. 05:03:30 05-25-1994 - No data
compression, or modem does not support
compression reporting.
Unimodem knows that this is a 14,400 bps call with error
compression but no data compression, based on the "52<CR>77<CR>69<CR>"
response codes.
The call is now in progress, in use by the program.
05:03:41 05-25-1994 - Remote modem hung up.
Unimodem detected a carrier loss. The call was disconnected by the
other computer. This output is different if Unimodem is called to
disconnect.
05:03:41 05-25-1994 - Hanging up the modem.
Unimodem dropped DTR to cause the modem to hang up.
05:03:41 05-25-1994 - TI V.32bis-V.17 Internal Closed.
Unimodem.tsp closed its Win32 file handle to the modem.