Portmon log for Paul (Part1)

[casey.o]

Paul, here is the Portman log file. This is connecting, and a small
time loading Firefox and connecting to google. I cut it off, because it
was getting huge, and I have a limit on the amount of bytes I can post
to the newsgroups. This log involves TWO connections, the first one
failed, then it retried. I generally have to try to connect at least 8
times before it works. Often, I hear the modem dial, then I hear the
operator saying "I'm sorry, the number you have dialed......". Other
times it dials, and I still hear the dialtone. Every so often, I
actuially get the modem connecting tones, but sometimes it still dont
connect. Although, there are times that I hear those tones on my W98
machine and dont connect either. That problem is probably my server.

Yesterday, I removed the modem from the puter, I removed all the drivers
for it, and even removed some regisrtry sections for the modem. Then I
replaced the modem and reinstalled the driiver pack, which comes for
that modem, from Compaq (for this Compaq model). Since then, after
repeated tries to connect, when I actually do connect, it does seem to
work, but slower than molasses in January.

This morning, I went to
http://windows.microsoft.com/en-us/windows/wallpaper and started to
download wallpapers as a test. In three hours, I got this:

25.65megs of data received
3.3megs sent

I was connected at 38.6 connect speed.

Therefore, I transferred about 30 megs of data in 3 hours. That's only
10 megs per hour. I can do almost triple that on my W98 machine. And I
had wallpapers downloading continuously, 2 or more at a time, so there
were no delays.

I've also noted that if I do not keep downloading, the modem
disconnects. My win98 machine can stay connected for a whole day with
nothing happening, unless my server is "processing", which they sort of
do on Sunday nights around 2 to 4 am.

I also tried to DL a file. I got about 1.6 to 1.8 KBPS. On my W98
machine, I normally get 4.5 to 6.5 kbps, and have topped out at 7.3kbps
a few times.

So, the XP connection is at least working, and I am posting this from
the XP puter, but I am downloading wallpapers to keep the connection
active, while I type this.

So, while I can actually connect and receive data now, it's horribly
slow, and a real bitch to establish the connection. I have not been
able to connect above 39.6, sometimes only 24.0 to 28.0.

Here is the Portmon log. I changed the phone number to 555-1212, and my
user name/ password is all #########, as well as the name of my server.

Otherwise it's just what the program saved.

There was one other change I made yesterday. It was set for HAVING a
network (besides the internet), I set network to NONE. (Probably
because there was a network card in this machine when I installed XP. I
have since removed that card, since it's nto needed now.

SHIT.... I'M GONNA HAVE TO SEND THIS IN SEVERAL PARTS. DUE TO AIOE
MESSAGE SIZE LIMIT.

---- Portmon log ----
[\\CASEY-XP]
0 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 1: .
0 0.00001397 SUCCESS
1 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
1 0.00000726 SUCCESS
2 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
2 0.00000251 SUCCESS
3 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 13
3 0.00001062 SUCCESS Length 13: .NO CARRIER..
4 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
4 0.00000391 SUCCESS
5 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
6 0.00000000 SVCHOST.EXE IRP_MJ_DEVICE_CONTROL PTSerial0 IOCTL:
0x2B0008
6 0.00000475 SUCCESS
7 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_MODEMSTATUS PTSerial0
7 0.00000503 SUCCESS
8 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 4: ATH.
8 0.00087497 SUCCESS
5 0.17899230 SUCCESS Length 1: A
9 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
9 0.00001090 SUCCESS
10 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 9
10 0.00001229 SUCCESS Length 9: TH...OK..
11 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
11 0.00000279 SUCCESS
12 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
13 0.00000000 SVCHOST.EXE IRP_MJ_DEVICE_CONTROL PTSerial0 IOCTL:
0x2B0008
13 0.00000531 SUCCESS
14 0.00000000 SVCHOST.EXE IOCTL_SERIAL_CLEAR_STATS PTSerial0
14 0.00000363 SUCCESS
15 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_COMMCONFIG PTSerial0
15 0.00000307 SUCCESS
16 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_BAUD_RATE PTSerial0
16 0.00000251 SUCCESS
17 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_LINE_CONTROL PTSerial0
17 0.00000335 SUCCESS
18 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_CHARS PTSerial0
18 0.00000251 SUCCESS
19 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_HANDFLOW PTSerial0
19 0.00000307 SUCCESS
20 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_BAUD_RATE PTSerial0
Rate: 115200
20 0.00000559 SUCCESS
21 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_DTR PTSerial0
21 0.00000419 SUCCESS
22 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_LINE_CONTROL PTSerial0
StopBits: 1 Parity:

NONE WordLength: 8
22 0.00000559 SUCCESS
23 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_CHAR PTSerial0 EOF:0
ERR:0 BRK:0 EVT:0

XON:11 XOFF:13
23 0.00000307 SUCCESS
24 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_HANDFLOW PTSerial0
Shake:9 Replace:80

XonLimit:10 XoffLimit:10
24 0.00000670 SUCCESS
25 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_DTR PTSerial0
25 0.00000251 SUCCESS
26 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_MODEMSTATUS PTSerial0
26 0.00001956 SUCCESS
27 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 3: AT.
27 0.00127363 SUCCESS
12 0.18934948 SUCCESS Length 1: A
28 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
28 0.00001006 SUCCESS
29 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 8
29 0.00001145 SUCCESS Length 8: T...OK..
30 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
30 0.00000307 SUCCESS
31 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
32 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 24:
AT&FE1&C1&D2&K3V1W3S0=0.
32 0.00070903 SUCCESS
31 0.00630667 SUCCESS Length 1: A
33 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
33 0.00000307 SUCCESS
34 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 29
34 0.00000615 SUCCESS Length 29: T&FE1&C1&D2&K3V1W3S0=0...OK..
35 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
35 0.00000279 SUCCESS
36 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
37 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 30:

ATS7=60S30=0M1\N3%%C3&K3B0N1X4.
37 0.00173765 SUCCESS
36 0.01639622 SUCCESS Length 1: A
38 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
38 0.00000279 SUCCESS
39 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 35
39 0.00000503 SUCCESS Length 35: TS7=60S30=0M1\N3%C3&K3B0N1X4...OK..
40 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
40 0.00000279 SUCCESS
41 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
42 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 7: ATS0=0.
42 0.00278052 SUCCESS
41 0.01643868 SUCCESS Length 1: A
43 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
43 0.00000307 SUCCESS
44 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 12
44 0.00000587 SUCCESS Length 12: TS0=0...OK..
45 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
45 0.00000279 SUCCESS
46 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
47 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_WAIT_MASK PTSerial0
Mask: DSR
47 0.00000950 SUCCESS
48 0.00000000 SVCHOST.EXE IOCTL_SERIAL_WAIT_ON_MASK PTSerial0
49 0.00000000 SVCHOST.EXE IRP_MJ_DEVICE_CONTROL PTSerial0 IOCTL:
0x2B0030
49 0.00000531 SUCCESS
50 0.00000000 SVCHOST.EXE IRP_MJ_DEVICE_CONTROL PTSerial0 IOCTL:
0x2B000C
50 0.00000782 SUCCESS
51 0.00000000 SVCHOST.EXE IRP_MJ_DEVICE_CONTROL PTSerial0 IOCTL:
0x2B0034
51 0.00000698 SUCCESS
52 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_WAIT_MASK PTSerial0
Mask:
48 0.00398654 SUCCESS
52 0.00004358 SUCCESS
53 0.00000000 SVCHOST.EXE IOCTL_SERIAL_PURGE PTSerial0 Purge:
TXABORT TXCLEAR
53 0.00000670 SUCCESS
54 0.00000000 SVCHOST.EXE IOCTL_SERIAL_PURGE PTSerial0 Purge:
RXABORT
46 0.00415639 CANCELLED
54 0.00001481 SUCCESS
55 0.00000000 SVCHOST.EXE IOCTL_SERIAL_PURGE PTSerial0 Purge:
TXABORT RXABORT TXCLEAR

RXCLEAR
55 0.00000531 SUCCESS
56 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_STATS PTSerial0
56 0.00000363 SUCCESS
57 0.00000000 SVCHOST.EXE IRP_MJ_CLEANUP PTSerial0
57 0.00001034 SUCCESS
58 0.00000000 SVCHOST.EXE IRP_MJ_CLOSE PTSerial0
58 0.00590354 SUCCESS
0 0.00000000 SVCHOST.EXE IRP_MJ_CREATE PTSerial0 Options: Open
0 0.00097470 SUCCESS
1 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_PROPERTIES PTSerial0
1 0.00015812 SUCCESS
2 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_COMMCONFIG PTSerial0
2 0.00000391 SUCCESS
3 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_BAUD_RATE PTSerial0
3 0.00000307 SUCCESS
4 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_LINE_CONTROL PTSerial0
4 0.00000335 SUCCESS
5 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_CHARS PTSerial0
5 0.00000223 SUCCESS
6 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_HANDFLOW PTSerial0
6 0.00000335 SUCCESS
7 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_BAUD_RATE PTSerial0 Rate:
115200
7 0.00000587 SUCCESS
8 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_DTR PTSerial0
8 0.00000363 SUCCESS
9 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_LINE_CONTROL PTSerial0
StopBits: 1 Parity:

NONE WordLength: 8
9 0.00000503 SUCCESS
10 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_CHAR PTSerial0 EOF:0
ERR:0 BRK:0 EVT:0

XON:11 XOFF:13
10 0.00000335 SUCCESS
11 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_HANDFLOW PTSerial0
Shake:9 Replace:80

XonLimit:10 XoffLimit:10
11 0.00000670 SUCCESS
12 0.00000000 SVCHOST.EXE IRP_MJ_DEVICE_CONTROL PTSerial0 IOCTL:
0x2B0008
12 0.00001676 SUCCESS
13 0.00000000 SVCHOST.EXE IOCTL_SERIAL_CLEAR_STATS PTSerial0
13 0.00000447 SUCCESS
14 0.00000000 SVCHOST.EXE IOCTL_SERIAL_PURGE PTSerial0 Purge:
RXABORT
14 0.00000363 SUCCESS
15 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_TIMEOUTS PTSerial0 RI:20
RM:0 RC:0 WM:10

WC:2000
15 0.00000279 SUCCESS
16 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_COMMCONFIG PTSerial0
16 0.00000196 SUCCESS
17 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
17 0.00000447 SUCCESS
18 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
19 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_BAUD_RATE PTSerial0
19 0.00000223 SUCCESS
20 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_LINE_CONTROL PTSerial0
20 0.00000279 SUCCESS
21 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_CHARS PTSerial0
21 0.00000251 SUCCESS
22 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_HANDFLOW PTSerial0
22 0.00000196 SUCCESS
23 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_BAUD_RATE PTSerial0
Rate: 115200
23 0.00000447 SUCCESS
24 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_DTR PTSerial0
24 0.00000419 SUCCESS
25 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_LINE_CONTROL PTSerial0
StopBits: 1 Parity:

NONE WordLength: 8
25 0.00000335 SUCCESS
26 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_CHAR PTSerial0 EOF:0
ERR:0 BRK:0 EVT:0

XON:11 XOFF:13
26 0.00000307 SUCCESS
27 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_HANDFLOW PTSerial0
Shake:9 Replace:80

XonLimit:10 XoffLimit:10
27 0.00000670 SUCCESS
28 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_DTR PTSerial0
28 0.00000279 SUCCESS
29 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_MODEMSTATUS PTSerial0
29 0.00000531 SUCCESS
30 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 3: AT.
30 0.00247797 SUCCESS
18 0.23405014 SUCCESS Length 1: A
31 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
31 0.00001090 SUCCESS
32 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 8
32 0.00001145 SUCCESS Length 8: T...OK..
33 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
33 0.00000279 SUCCESS
34 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
35 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 24:
AT&FE1&C1&D2&K3V1W3S0=0.
35 0.00117752 SUCCESS
34 0.00971101 SUCCESS Length 1: A
36 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
36 0.00001117 SUCCESS
37 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 29
37 0.00001090 SUCCESS Length 29: T&FE1&C1&D2&K3V1W3S0=0...OK..
38 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
38 0.00000279 SUCCESS
39 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
40 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 30:

ATS7=60S30=0M1\N3%%C3&K3B0N1X4.
40 0.00217486 SUCCESS
39 0.01619843 SUCCESS Length 1: A
41 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
41 0.00000950 SUCCESS
42 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 35
42 0.00001145 SUCCESS Length 35: TS7=60S30=0M1\N3%C3&K3B0N1X4...OK..
43 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
43 0.00000279 SUCCESS
44 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
45 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 7: ATS0=0.
45 0.00105265 SUCCESS
44 0.01623838 SUCCESS Length 1: A
46 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
46 0.00001034 SUCCESS
47 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 12
47 0.00001173 SUCCESS Length 12: TS0=0...OK..
48 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
48 0.00000307 SUCCESS
49 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
50 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_WAIT_MASK PTSerial0
Mask: DSR
50 0.00000838 SUCCESS
51 0.00000000 SVCHOST.EXE IOCTL_SERIAL_WAIT_ON_MASK PTSerial0
52 0.00000000 SVCHOST.EXE IRP_MJ_DEVICE_CONTROL PTSerial0 IOCTL:
0x2B0030
52 0.00000279 SUCCESS
53 0.00000000 SVCHOST.EXE IRP_MJ_DEVICE_CONTROL PTSerial0 IOCTL:
0x2B0034
54 0.00000000 SVCHOST.EXE IRP_MJ_DEVICE_CONTROL PTSerial0 IOCTL:
0x2B0008
54 0.00000279 SUCCESS
55 0.00000000 SVCHOST.EXE IOCTL_SERIAL_CLEAR_STATS PTSerial0
55 0.00000391 SUCCESS
56 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_COMMCONFIG PTSerial0
56 0.00000279 SUCCESS
57 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_BAUD_RATE PTSerial0
57 0.00000251 SUCCESS
58 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_LINE_CONTROL PTSerial0
58 0.00000307 SUCCESS
59 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_CHARS PTSerial0
59 0.00000251 SUCCESS
60 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_HANDFLOW PTSerial0
60 0.00000251 SUCCESS
61 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_BAUD_RATE PTSerial0
Rate: 115200
61 0.00000475 SUCCESS
62 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_DTR PTSerial0
62 0.00000447 SUCCESS
63 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_LINE_CONTROL PTSerial0
StopBits: 1 Parity:

NONE WordLength: 8
63 0.00000503 SUCCESS
64 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_CHAR PTSerial0 EOF:0
ERR:0 BRK:0 EVT:0

XON:11 XOFF:13
64 0.00000335 SUCCESS
65 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_HANDFLOW PTSerial0
Shake:9 Replace:80

XonLimit:10 XoffLimit:10
65 0.00000726 SUCCESS
66 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_DTR PTSerial0
66 0.00000279 SUCCESS
67 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_MODEMSTATUS PTSerial0
67 0.00000391 SUCCESS
68 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_WAIT_MASK PTSerial0
Mask:
51 0.00085653 SUCCESS
68 0.00002179 SUCCESS
69 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 3: AT.
69 0.00200752 SUCCESS
49 0.01627302 SUCCESS Length 1: A
70 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
70 0.00000866 SUCCESS
71 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 8
71 0.00001090 SUCCESS Length 8: T...OK..
72 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
72 0.00000279 SUCCESS
73 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
74 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 24:
AT&FE1&C1&D2&K3V1W3S0=0.
74 0.00193768 SUCCESS
73 0.01315586 SUCCESS Length 1: A
75 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
75 0.00001062 SUCCESS
76 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 29
76 0.00001257 SUCCESS Length 29: T&FE1&C1&D2&K3V1W3S0=0...OK..
77 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
77 0.00000279 SUCCESS
78 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
79 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 30:

ATS7=60S30=0M1\N3%%C3&K3B0N1X4.
79 0.00300820 SUCCESS
78 0.01614702 SUCCESS Length 1: A
80 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
80 0.00001062 SUCCESS
81 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 35
81 0.00001117 SUCCESS Length 35: TS7=60S30=0M1\N3%C3&K3B0N1X4...OK..
82 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
82 0.00000279 SUCCESS
83 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
84 0.00000000 SVCHOST.EXE IRP_MJ_DEVICE_CONTROL PTSerial0 IOCTL:
0x2B0030
84 0.00000643 SUCCESS
85 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 13:
ATDT555-1212.
85 0.00184996 SUCCESS
83 0.01628168 SUCCESS Length 1: A
86 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
86 0.00000866 SUCCESS
87 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 12
87 0.00001062 SUCCESS Length 12: TDT555-1212.
88 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
88 0.00000279 SUCCESS
89 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
89 65.21566233 SUCCESS Length 1: .
90 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
90 0.00001173 SUCCESS
91 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
91 0.00000251 SUCCESS
92 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 13
92 0.00001090 SUCCESS Length 13: .NO CARRIER..
93 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
93 0.00000279 SUCCESS
94 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
95 0.00000000 SVCHOST.EXE IRP_MJ_DEVICE_CONTROL PTSerial0 IOCTL:
0x2B0008
95 0.00000531 SUCCESS
96 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_MODEMSTATUS PTSerial0
96 0.00000503 SUCCESS
97 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 4: ATH.
97 0.00237265 SUCCESS
94 0.19558435 SUCCESS Length 1: A
98 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
98 0.00001006 SUCCESS
99 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 9
99 0.00001313 SUCCESS Length 9: TH...OK..
100 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
100 0.00000279 SUCCESS
101 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
102 0.00000000 SVCHOST.EXE IRP_MJ_DEVICE_CONTROL PTSerial0 IOCTL:
0x2B0008
102 0.00000447 SUCCESS
103 0.00000000 SVCHOST.EXE IOCTL_SERIAL_CLEAR_STATS PTSerial0
103 0.00000391 SUCCESS
104 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_COMMCONFIG PTSerial0
104 0.00000335 SUCCESS
105 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_BAUD_RATE PTSerial0
105 0.00000251 SUCCESS
106 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_LINE_CONTROL PTSerial0
106 0.00000335 SUCCESS
107 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_CHARS PTSerial0
107 0.00000279 SUCCESS
108 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_HANDFLOW PTSerial0
108 0.00000279 SUCCESS
109 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_BAUD_RATE PTSerial0
Rate: 115200
109 0.00000475 SUCCESS
110 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_DTR PTSerial0
110 0.00000419 SUCCESS
111 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_LINE_CONTROL PTSerial0
StopBits: 1 Parity:

NONE WordLength: 8
111 0.00000503 SUCCESS
112 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_CHAR PTSerial0 EOF:0
ERR:0 BRK:0 EVT:0

XON:11 XOFF:13
112 0.00000307 SUCCESS
113 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_HANDFLOW PTSerial0
Shake:9 Replace:80

XonLimit:10 XoffLimit:10
113 0.00000670 SUCCESS
114 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_DTR PTSerial0
114 0.00000279 SUCCESS
115 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_MODEMSTATUS PTSerial0
115 0.00000391 SUCCESS
116 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 3: AT.
116 0.00104622 SUCCESS
101 0.18594961 SUCCESS Length 1: A
117 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
117 0.00000447 SUCCESS
118 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 8
118 0.00000810 SUCCESS Length 8: T...OK..
119 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
119 0.00000279 SUCCESS
120 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
121 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 24:
AT&FE1&C1&D2&K3V1W3S0=0.
121 0.00324119 SUCCESS
120 0.00982192 SUCCESS Length 1: A
122 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
122 0.00000307 SUCCESS
123 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 29
123 0.00000475 SUCCESS Length 29: T&FE1&C1&D2&K3V1W3S0=0...OK..
124 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
124 0.00000251 SUCCESS
125 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
126 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 30:

ATS7=60S30=0M1\N3%%C3&K3B0N1X4.
126 0.00093252 SUCCESS
125 0.01308853 SUCCESS Length 1: A
127 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
127 0.00000279 SUCCESS
128 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 35
128 0.00000475 SUCCESS Length 35: TS7=60S30=0M1\N3%C3&K3B0N1X4...OK..
129 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
129 0.00000279 SUCCESS
130 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
131 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 7: ATS0=0.
131 0.00198936 SUCCESS
130 0.01643645 SUCCESS Length 1: A
132 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
132 0.00000279 SUCCESS
133 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 12
133 0.00000503 SUCCESS Length 12: TS0=0...OK..
134 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
134 0.00000251 SUCCESS
135 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
136 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_WAIT_MASK PTSerial0
Mask: DSR
136 0.00000922 SUCCESS
137 0.00000000 SVCHOST.EXE IOCTL_SERIAL_WAIT_ON_MASK PTSerial0
138 0.00000000 SVCHOST.EXE IRP_MJ_DEVICE_CONTROL PTSerial0 IOCTL:
0x2B0030
138 0.00000643 SUCCESS
139 0.00000000 SVCHOST.EXE IRP_MJ_DEVICE_CONTROL PTSerial0 IOCTL:
0x2B000C
139 0.00000782 SUCCESS
140 0.00000000 SVCHOST.EXE IRP_MJ_DEVICE_CONTROL PTSerial0 IOCTL:
0x2B0034
53 65.71330881 CANCELLED
140 0.00001173 SUCCESS
141 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_WAIT_MASK PTSerial0
Mask:
137 0.01206019 SUCCESS
141 0.00004665 SUCCESS
142 0.00000000 SVCHOST.EXE IOCTL_SERIAL_PURGE PTSerial0 Purge:
TXABORT TXCLEAR
142 0.00000726 SUCCESS
143 0.00000000 SVCHOST.EXE IOCTL_SERIAL_PURGE PTSerial0 Purge:
RXABORT
135 0.01223005 CANCELLED
143 0.00001369 SUCCESS
144 0.00000000 SVCHOST.EXE IOCTL_SERIAL_PURGE PTSerial0 Purge:
TXABORT RXABORT TXCLEAR

RXCLEAR
144 0.00000559 SUCCESS
145 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_STATS PTSerial0
145 0.00000363 SUCCESS
146 0.00000000 SVCHOST.EXE IRP_MJ_CLEANUP PTSerial0
146 0.00001034 SUCCESS
147 0.00000000 SVCHOST.EXE IRP_MJ_CLOSE PTSerial0
147 0.01365285 SUCCESS
148 0.00000000 SVCHOST.EXE IRP_MJ_CREATE PTSerial0 Options: Open
148 0.00100627 SUCCESS
149 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_PROPERTIES PTSerial0
149 0.00015700 SUCCESS
150 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_COMMCONFIG PTSerial0
150 0.00000363 SUCCESS
151 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_BAUD_RATE PTSerial0
151 0.00000363 SUCCESS
152 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_LINE_CONTROL PTSerial0
152 0.00000335 SUCCESS
153 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_CHARS PTSerial0
153 0.00000223 SUCCESS
154 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_HANDFLOW PTSerial0
154 0.00000307 SUCCESS
155 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_BAUD_RATE PTSerial0
Rate: 115200
155 0.00000615 SUCCESS
156 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_DTR PTSerial0
156 0.00000447 SUCCESS
157 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_LINE_CONTROL PTSerial0
StopBits: 1 Parity:

NONE WordLength: 8
157 0.00000475 SUCCESS
158 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_CHAR PTSerial0 EOF:0
ERR:0 BRK:0 EVT:0

XON:11 XOFF:13
158 0.00000335 SUCCESS
159 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_HANDFLOW PTSerial0
Shake:9 Replace:80

XonLimit:10 XoffLimit:10
159 0.00000726 SUCCESS
160 0.00000000 SVCHOST.EXE IRP_MJ_DEVICE_CONTROL PTSerial0 IOCTL:
0x2B0008
160 0.00001620 SUCCESS
161 0.00000000 SVCHOST.EXE IOCTL_SERIAL_CLEAR_STATS PTSerial0
161 0.00000475 SUCCESS
162 0.00000000 SVCHOST.EXE IOCTL_SERIAL_PURGE PTSerial0 Purge:
RXABORT
162 0.00000363 SUCCESS
163 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_TIMEOUTS PTSerial0
RI:20 RM:0 RC:0 WM:10

WC:2000
163 0.00000307 SUCCESS
164 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_COMMCONFIG PTSerial0
164 0.00000251 SUCCESS
165 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
165 0.00000447 SUCCESS
166 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
167 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_BAUD_RATE PTSerial0
167 0.00000223 SUCCESS
168 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_LINE_CONTROL PTSerial0
168 0.00000279 SUCCESS
169 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_CHARS PTSerial0
169 0.00000251 SUCCESS
170 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_HANDFLOW PTSerial0
170 0.00000223 SUCCESS
171 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_BAUD_RATE PTSerial0
Rate: 115200
171 0.00000503 SUCCESS
172 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_DTR PTSerial0
172 0.00000447 SUCCESS
173 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_LINE_CONTROL PTSerial0
StopBits: 1 Parity:

NONE WordLength: 8
173 0.00000335 SUCCESS
174 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_CHAR PTSerial0 EOF:0
ERR:0 BRK:0 EVT:0

XON:11 XOFF:13
174 0.00000279 SUCCESS
175 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_HANDFLOW PTSerial0
Shake:9 Replace:80

XonLimit:10 XoffLimit:10
175 0.00000726 SUCCESS
176 0.00000000 SVCHOST.EXE IOCTL_SERIAL_SET_DTR PTSerial0
176 0.00000279 SUCCESS
177 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_MODEMSTATUS PTSerial0
177 0.00000587 SUCCESS
178 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 3: AT.
178 0.00286070 SUCCESS
166 0.22738337 SUCCESS Length 1: A
179 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
179 0.00001173 SUCCESS
180 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 8
180 0.00001201 SUCCESS Length 8: T...OK..
181 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
181 0.00000307 SUCCESS
182 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
183 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 24:
AT&FE1&C1&D2&K3V1W3S0=0.
183 0.00055454 SUCCESS
182 0.00629801 SUCCESS Length 1: A
184 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
184 0.00000307 SUCCESS
185 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 29
185 0.00000670 SUCCESS Length 29: T&FE1&C1&D2&K3V1W3S0=0...OK..
186 0.00000000 SVCHOST.EXE IOCTL_SERIAL_GET_COMMSTATUS PTSerial0
186 0.00000279 SUCCESS
187 0.00000000 SVCHOST.EXE IRP_MJ_READ PTSerial0 Length 1
188 0.00000000 SVCHOST.EXE IRP_MJ_WRITE PTSerial0 Length 30:

ATS7=60S30=0M1\N3%%C3&K3B0N1X4.

 

[Paul]

Paul, here is the Portman log file. This is connecting, and a small
time loading Firefox and connecting to google. I cut it off, because it
was getting huge, and I have a limit on the amount of bytes I can post
to the newsgroups. This log involves TWO connections, the first one
failed, then it retried. I generally have to try to connect at least 8
times before it works. Often, I hear the modem dial, then I hear the
operator saying "I'm sorry, the number you have dialed......". Other
times it dials, and I still hear the dialtone. Every so often, I
actuially get the modem connecting tones, but sometimes it still dont
connect. Although, there are times that I hear those tones on my W98
machine and dont connect either. That problem is probably my server.

Yesterday, I removed the modem from the puter, I removed all the drivers
for it, and even removed some regisrtry sections for the modem. Then I
replaced the modem and reinstalled the driiver pack, which comes for
that modem, from Compaq (for this Compaq model). Since then, after
repeated tries to connect, when I actually do connect, it does seem to
work, but slower than molasses in January.

This morning, I went to
http://windows.microsoft.com/en-us/windows/wallpaper and started to
download wallpapers as a test. In three hours, I got this:

25.65megs of data received
3.3megs sent

I was connected at 38.6 connect speed.

Therefore, I transferred about 30 megs of data in 3 hours. That's only
10 megs per hour. I can do almost triple that on my W98 machine. And I
had wallpapers downloading continuously, 2 or more at a time, so there
were no delays.

I've also noted that if I do not keep downloading, the modem
disconnects. My win98 machine can stay connected for a whole day with
nothing happening, unless my server is "processing", which they sort of
do on Sunday nights around 2 to 4 am.

I also tried to DL a file. I got about 1.6 to 1.8 KBPS. On my W98
machine, I normally get 4.5 to 6.5 kbps, and have topped out at 7.3kbps
a few times.

So, the XP connection is at least working, and I am posting this from
the XP puter, but I am downloading wallpapers to keep the connection
active, while I type this.

So, while I can actually connect and receive data now, it's horribly
slow, and a real bitch to establish the connection. I have not been
able to connect above 39.6, sometimes only 24.0 to 28.0.

Here is the Portmon log. I changed the phone number to 555-1212, and my
user name/ password is all #########, as well as the name of my server.

Otherwise it's just what the program saved.

There was one other change I made yesterday. It was set for HAVING a
network (besides the internet), I set network to NONE. (Probably
because there was a network card in this machine when I installed XP. I
have since removed that card, since it's nto needed now.

SHIT.... I'M GONNA HAVE TO SEND THIS IN SEVERAL PARTS. DUE TO AIOE
MESSAGE SIZE LIMIT.

---- Portmon log ----

It looks like it took several tries before it decided what
it wanted to do. One dialing attempt ended up with "NO CARRIER"
as a response. Like the other end hung up, or there was
never a dial tone detected in the first place. About mid-way
into the second file, there is the CONNECT message, and the
PPP portion starts after that.

Either the modem isn't using the correct national standard,
or the conditions on your line aren't quite right. The DAA needs
to recognize certain conditions on the line, and it does some
of that by voltage sensing (like on or off hook).

OK, so I've selected the relevant bits out of the first two files.

ATH
AT
ATS0=0
AT&FE1&C1&D2&K3V1W3S0=0
ATS7=60S30=0M1\N3%%C3&K3B0N1X4
ATS0=0
AT
AT&FE1&C1&D2&K3V1W3S0=0
ATS7=60S30=0M1\N3%%C3&K3B0N1X4
ATS0=0
AT
AT&FE1&C1&D2&K3V1W3S0=0
ATS7=60S30=0M1\N3%%C3&K3B0N1X4
ATDT555-1212
..NO CARRIER..
ATH
AT
AT&FE1&C1&D2&K3V1W3S0=0
ATS7=60S30=0M1\N3%%C3&K3B0N1X4
ATS0=0
AT
AT&FE1&C1&D2&K3V1W3S0=0
ATS7=60S30=0M1\N3%%C3&K3B0N1X4
------------------------------
ATS0=0
AT
AT&FE1&C1&D2&K3V1W3S0=0
ATS7=60S30=0M1\N3%%C3&K3B0N1X4
ATDT555-1212
..CONNECT 38666/PROTOCOL:
LAPM/COMPRESSION: V.44..

You can see it sent the commands about six times,
before something worked.

Your connect message is encouraging.

(V44 is good stuff, if you read the description here.
Also, the presence of V.44, says the driver used supports V92 rather than V90)
http://en.wikipedia.org/wiki/List_of_ITU-T_V-Series_Recommendations

*******
Now to try decoding it. I tried several Hayes command set
references, but finally I clued in that I could use the
Zoltrix HSP web page to decode this.

Now, the %%C3 bothered me, but when reading the Wikipedia article
on Hayes command set, it says the AT string can be up to 40 characters
long. If I count characters, I hit 40 characters, just before that
out-of-place "%" shows up. It looks like perhaps somewhere in
the computer, the entire AT string is stored, and the extra % is
there as a hint to break the command into two pieces. I don't
think it is a coincidence that an out of place "%" appears
at that point. But you notice the command was actually broken
into two pieces anyway, but at a slightly different point
(less than 40 characters). Leaving that stupid extra % just sitting there.

ATS0=0 Auto-answer off (for FAX receiving)
AT
&F <--- Factory config ? Like a Z reset maybe ?
E1 Echo ON - That seems unlikely. Used during command phase.
&C1 DCD follows remote carrier
&D2 DTR drop causes modem to hang up
&K3 Enable RTS/CTS flow control
V1 Results codes in verbal form
W3 (Reporting line speed and Error Correcting mode???)
S0=0 Auto-answer off
AT
S7=60 Wait as long as 60 seconds for CARRIER
S30=0 Inactivity Disconnect Timer, disabled
M1 Speaker ON
\N3 Select auto reliable mode (LAPM if available?)
%%C3 Compression setting ??? MNP5 & V.42bis
&K3 Enable RTS/CTS DTE/DCE flow control.
B0 Select V.22 connection at 1200 bps
N1 Ignore S37, Ignore ATBn, connect at highest available speed
X4 Report all call progress result codes and connection rate

The question would be, how would the modem treat that
excess % symbol ? Is it ignoring everything after the % ?
The %C3 happens to be the default in the Zoltrix reference, the
B0 is irrelevant, the N1 would be a default. More or less,
if the stuff after the excess % were ignored, it probably
wouldn't hurt anything.

My plan was, to try to compare the INIT string of your
Win98 machine (which might be more visible), to whatever
the WinXP machine was doing.

The INIT string in WinXP is likely all one string. When some
layer below that gets the string, it breaks it into two parts.
You'll notice the INIT string defines three S registers.
And the command gets broken between the S0 definition and the
S7 definition. Breaking the line there appears to be
a conservative approach, as the Wikipedia article says
you could have up to 40 characters in an AT command if you
wanted.

I wouldn't say there is necessarily anything wrong with the
WinXP INIT string. But it would be interesting to compare
the one Win98 is using, to the one WinXP is using.

As well, being a PCTel soft modem, the driver revision and
sophistication, between the two OSes, could be different. The
WinXP driver appears to be V.92, at least based on the CONNECT
information reported. Perhaps the poor performance is related
to the DSP code, and the modem gradually reducing the
connect rate from the initial 38666 connect rate.

PortMon is unlikely to run on Win98, but you can try it. if the
Win98 INIT string is easier to find, you could see how much it
differs from the WinXP one. The options reported, certainly
look superior to the options I've used or set on modems here. I
doubt my modem is V92, and it's probably V90 at best.

This is the Zoltrix HSP command set I eventually settled on,
to decode the commands. The results are actually different
than looking at some other Hayes references.

http://www.zoltrix.com/support_html/PUBLIC/MODEM/ATmanual/ATHSP56.HTM

Paul

 

[casey.o]

Paul, here is the Portman log file for Win98. This is logged until
connected. Portmon works fine on Win98.

As before, multiple part post.....
This one got huge !

I connected at 38.6, which is slow for me on this computer, but it tends
to vary. I do have a bit of trouble connecting on here too, meaning
that I can call in and not actually connect, via name/password, and
occasionally it hangs, adn does nto connect at all. But this is
probably my ISP server. I'm used to that happening, usually 2 or 3
tries do the trick. Shutting off the modem, nad back on again seems to
help too when it's not trying to connect. But aside from that, I always
get a good solid and fast connection once i am connected, and I can
leave it on for hours, without it disconnecting.

This will probably take 5 parts to send....
So much repeated data, but I'm not sure what parts to delete, or I'd
trim it.

---Portmon log---

0 0.00000480 Tapisrv VCOMM_EscapeCommFunction 0x0
0x700465 Unknown Func: 38
1 0.00000320 Tapisrv VCOMM_EscapeCommFunction 0x0
0x700465 Unknown Func: 38
2 0.00191520 Tapisrv VCOMM_OpenComm COM2 SUCCESS
3 0.00000320 Tapisrv VCOMM_EnableCommNotification COM2
SUCCESS
4 0.00000320 Tapisrv VCOMM_EscapeCommFunction COM2
SUCCESS SETUPDATETIMERADDR
5 0.00000640 Tapisrv VCOMM_SetReadCallBack COM2 SUCCESS
Trigger: -1
6 0.00000400 Tapisrv VCOMM_ClearCommError COM2 SUCCESS
NOERROR
7 0.00000320 Tapisrv VCOMM_ReadComm COM2 SUCCESS Length:
0:
8 0.00000400 Tapisrv VCOMM_PurgeComm COM2 SUCCESS Transmit
Queue
9 0.00000320 Tapisrv VCOMM_ClearCommError COM2 SUCCESS
NOERROR
10 0.00000640 Tapisrv VCOMM_SetReadCallBack COM2 SUCCESS
Trigger: 1
11 0.00000320 Tapisrv VCOMM_GetCommState COM2 SUCCESS
Baud: 115200 Bits: 8 Stop: 1 Parity: None
12 0.23299360 Tapisrv VCOMM_SetCommState COM2 SUCCESS
Mask: ffffffff Baud: 115200 Bits: 8 Stop: 1 Parity: None
13 0.00000800 Tapisrv VCOMM_EscapeCommFunction COM2
SUCCESS SETDTR
14 0.00000480 Tapisrv VCOMM_EscapeCommFunction COM2
SUCCESS SETRTS
15 0.23956080 Tapisrv VCOMM_OpenComm Creative Modem Blaster
V.92 DE5721 SUCCESS
16 0.00000400 Tapisrv VCOMM_EscapeCommFunction Creative
Modem Blaster V.92 DE5721 SUCCESS CLRTIMERLOGIC
17 0.00000320 Tapisrv VCOMM_EscapeCommFunction Creative
Modem Blaster V.92 DE5721 SUCCESS IGNOREERRORONREADS
18 0.00028400 Tapisrv VCOMM_SetupComm Creative Modem Blaster
V.92 DE5721 SUCCESS RxSize: 4096 TxSize: 0
19 0.00000800 Tapisrv VCOMM_SetupComm Creative Modem Blaster
V.92 DE5721 SUCCESS RxSize: 4096 TxSize: 4096
20 0.00000320 Tapisrv VCOMM_GetCommState COM2 SUCCESS
Baud: 115200 Bits: 8 Stop: 1 Parity: None
21 0.00001600 Tapisrv VCOMM_SetCommState COM2 SUCCESS
Mask: ffffffff Baud: 115200 Bits: 8 Stop: 1 Parity: None
22 0.00000480 Tapisrv VCOMM_EscapeCommFunction COM2
SUCCESS SETDTR
23 0.00000480 Tapisrv VCOMM_EscapeCommFunction COM2
SUCCESS SETRTS
24 0.00000560 Tapisrv VCOMM_SetReadCallBack COM2 SUCCESS
Trigger: -1
25 0.00000400 Tapisrv VCOMM_ClearCommError COM2 SUCCESS
NOERROR
26 0.00000400 Tapisrv VCOMM_ReadComm COM2 SUCCESS Length:
0:
27 0.00000480 Tapisrv VCOMM_PurgeComm COM2 SUCCESS Transmit
Queue
28 0.00000240 Tapisrv VCOMM_ClearCommError COM2 SUCCESS
NOERROR
29 0.00000320 Tapisrv VCOMM_SetReadCallBack COM2 SUCCESS
Trigger: 1
30 0.00000400 Tapisrv VCOMM_SetCommEventMask COM2 SUCCESS
31 0.00000320 Tapisrv VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: -1
32 0.00000240 Tapisrv VCOMM_ClearCommError COM2 SUCCESS
NOERROR
33 0.00000320 Tapisrv VCOMM_PurgeComm COM2 SUCCESS Receive
Queue
34 0.00000320 Tapisrv VCOMM_ClearCommError COM2 SUCCESS
NOERROR
35 0.00000320 Tapisrv VCOMM_ReadComm COM2 SUCCESS Length:
0:
36 0.00000560 Tapisrv VCOMM_EscapeCommFunction COM2
SUCCESS SETDTR
37 0.00000320 Tapisrv VCOMM_ClearCommError COM2 SUCCESS
NOERROR
38 0.00000320 Tapisrv VCOMM_ReadComm COM2 SUCCESS Length:
0:
39 0.00000720 Tapisrv VCOMM_WriteComm COM2 SUCCESS Length:
6: ATZ&F.
40 0.00000320 Tapisrv VCOMM_GetCommQueueStatus COM2
SUCCESS RX: 0 TX: 0
41 0.00000240 Tapisrv VCOMM_GetCommQueueStatus COM2
SUCCESS RX: 0 TX: 0
42 0.00000320 Tapisrv VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: -1
43 0.00000880 KERNEL32 ReadNotifyProc COM2 VOID
RECEIVE: RXCHAR
44 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
45 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: A
46 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
47 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
48 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: T
49 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
50 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
51 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: Z
52 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
53 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
54 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: &
55 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
56 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
57 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: F
58 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
59 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
60 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: .
61 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
62 0.00000320 KERNEL32 VCOMM_GetCommQueueStatus
COM2 SUCCESS RX: 0 TX: 0
63 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
64 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
65 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 0:
66 0.00000400 KERNEL32 ReadNotifyProc COM2 VOID
RECEIVE: RXCHAR
67 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
68 0.00000400 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: .
69 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
70 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
71 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: .
72 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
73 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
74 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: O
75 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
76 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
77 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: K
78 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
79 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
80 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: .
81 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
82 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
83 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: .
84 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
85 0.00000640 KERNEL32 VCOMM_WriteComm COM2 SUCCESS
Length: 33: AT+IBC=0,0,0,,,,,0;+PCW=2;+PMH=1.
86 0.00000320 KERNEL32 VCOMM_GetCommQueueStatus
COM2 SUCCESS RX: 0 TX: 17
87 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: 1
88 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
89 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 0:
90 0.00000320 KERNEL32 ReadNotifyProc COM2 VOID
RECEIVE: RXCHAR
91 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
92 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: A
93 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
94 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: T
95 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
96 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: +
97 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
98 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: I
99 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
100 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: B
101 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
102 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: C
103 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
104 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: =
105 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
106 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: 0
107 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
108 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 0:
109 0.00000320 KERNEL32 ReadNotifyProc COM2 VOID
RECEIVE: RXCHAR
110 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
111 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: ,
112 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
113 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: 0
114 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
115 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: ,
116 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
117 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: 0
118 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
119 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: ,
120 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
121 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: ,
122 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
123 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: ,
124 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
125 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: ,
126 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
127 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 0:
128 0.00000320 KERNEL32 ReadNotifyProc COM2 VOID
RECEIVE: RXCHAR
129 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
130 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: ,
131 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
132 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: 0
133 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
134 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: ;
135 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
136 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: +
137 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
138 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: P
139 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
140 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: C
141 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
142 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: W
143 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
144 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: =
145 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
146 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 0:
147 0.00000560 KERNEL32 WriteNotifyProc COM2 VOID
TRANSMIT: TXCHAR
148 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
149 0.00000240 KERNEL32 VCOMM_GetCommQueueStatus
COM2 SUCCESS RX: 0 TX: 0
150 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
151 0.00000320 KERNEL32 ReadNotifyProc COM2 VOID
RECEIVE: RXCHAR
152 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
153 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: 2
154 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
155 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
156 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: ;
157 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
158 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
159 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: +
160 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
161 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
162 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: P
163 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
164 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
165 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: M
166 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
167 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
168 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: H
169 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
170 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
171 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: =
172 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
173 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
174 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: 1
175 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
176 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
177 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 0:
178 0.00000320 KERNEL32 ReadNotifyProc COM2 VOID
RECEIVE: RXCHAR
179 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
180 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: .
181 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
182 0.00000240 KERNEL32 VCOMM_GetCommQueueStatus
COM2 SUCCESS RX: 0 TX: 0
183 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
184 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
185 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 0:
186 0.00000320 KERNEL32 ReadNotifyProc COM2 VOID
RECEIVE: RXCHAR
187 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
188 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: .
189 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
190 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
191 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: .
192 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
193 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
194 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: O
195 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
196 0.00001280 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
197 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: K
198 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
199 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
200 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: .
201 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
202 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR

 

[casey.o]

203 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: .
204 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
205 0.00000640 KERNEL32 VCOMM_WriteComm COM2 SUCCESS
Length: 45: ATE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;+GCI=B5;W2.
206 0.00000320 KERNEL32 VCOMM_GetCommQueueStatus
COM2 SUCCESS RX: 0 TX: 29
207 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: 1
208 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
209 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 0:
210 0.00000320 KERNEL32 ReadNotifyProc COM2 VOID
RECEIVE: RXCHAR
211 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
212 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: A
213 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
214 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: T
215 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
216 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: E
217 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
218 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: 0
219 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
220 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: V
221 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
222 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: 1
223 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
224 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: S
225 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
226 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: 0
227 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
228 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 0:
229 0.00000320 KERNEL32 ReadNotifyProc COM2 VOID
RECEIVE: RXCHAR
230 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
231 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: =
232 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
233 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: 0
234 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
235 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: &
236 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
237 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: C
238 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
239 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: 1
240 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
241 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: &
242 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
243 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: D
244 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
245 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: 2
246 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
247 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 0:
248 0.00000320 KERNEL32 ReadNotifyProc COM2 VOID
RECEIVE: RXCHAR
249 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
250 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: +
251 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
252 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: M
253 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
254 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: R
255 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
256 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: =
257 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
258 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: 2
259 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
260 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: ;
261 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
262 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: +
263 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
264 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: D
265 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
266 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 0:
267 0.00000320 KERNEL32 WriteNotifyProc COM2 VOID
TRANSMIT: TXCHAR
268 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
269 0.00000320 KERNEL32 VCOMM_GetCommQueueStatus
COM2 SUCCESS RX: 0 TX: 0
270 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
271 0.00000320 KERNEL32 ReadNotifyProc COM2 VOID
RECEIVE: RXCHAR
272 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
273 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: R
274 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
275 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
276 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: =
277 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
278 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
279 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: 1
280 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
281 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
282 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: ;
283 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
284 0.00000240 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
285 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: +
286 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
287 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
288 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: E
289 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
290 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
291 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: R
292 0.00001280 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
293 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
294 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: =
295 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
296 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
297 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: 1
298 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
299 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
300 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: ;
301 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
302 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
303 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: +
304 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
305 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
306 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: G
307 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
308 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
309 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: C
310 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
311 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
312 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: I
313 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
314 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
315 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: =
316 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
317 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
318 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: B
319 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
320 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
321 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 0:
322 0.00000320 KERNEL32 ReadNotifyProc COM2 VOID
RECEIVE: RXCHAR
323 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
324 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: 5
325 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
326 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
327 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: ;
328 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
329 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
330 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: W
331 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
332 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
333 0.00000240 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: 2
334 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
335 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
336 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 1: .
337 0.00000240 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
338 0.00000240 KERNEL32 VCOMM_GetCommQueueStatus
COM2 SUCCESS RX: 0 TX: 0
339 0.00000320 KERNEL32 VCOMM_SetWriteCallBack COM2
SUCCESS Trigger: -1
340 0.00000320 KERNEL32 VCOMM_ClearCommError COM2
SUCCESS NOERROR
341 0.00000320 KERNEL32 VCOMM_ReadComm COM2 SUCCESS
Length: 0:
342 0.00000720 Portmon ReadNotifyProc COM2 VOID RECEIVE:
RXCHAR
343 0.00000560 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
344 0.00000480 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: .
345 0.00000480 Portmon VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: -1
346 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
347 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: .
348 0.00000320 Portmon VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: -1
349 0.00000240 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
350 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: O
351 0.00000320 Portmon VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: -1
352 0.00000240 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
353 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: K
354 0.00000320 Portmon VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: -1
355 0.00000240 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
356 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: .
357 0.00000240 Portmon VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: -1
358 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
359 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: .
360 0.00000240 Portmon VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: -1
361 0.00000800 Portmon VCOMM_WriteComm COM2 SUCCESS Length:
33: ATS7=90S30=0L3M1+ES=3,0,2;+DS=3;.
362 0.00000400 Portmon VCOMM_GetCommQueueStatus COM2
SUCCESS RX: 0 TX: 17
363 0.00000400 Portmon VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: 1
364 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
365 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
0:
366 0.00000480 Portmon ReadNotifyProc COM2 VOID RECEIVE:
RXCHAR
367 0.00000400 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
368 0.00000400 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: A
369 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
370 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: T
371 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
372 0.00000240 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: S
373 0.00000240 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
374 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: 7
375 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
376 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: =
377 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
378 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: 9
379 0.00000240 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
380 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: 0
381 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
382 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: S
383 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
384 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
0:
385 0.00000400 Portmon ReadNotifyProc COM2 VOID RECEIVE:
RXCHAR
386 0.00000400 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
387 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: 3
388 0.00000240 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
389 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: 0
390 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
391 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: =
392 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
393 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: 0
394 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
395 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: L
396 0.00000240 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
397 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: 3
398 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
399 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: M
400 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
401 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: 1
402 0.00000240 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
403 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
0:
404 0.00000640 Portmon ReadNotifyProc COM2 VOID RECEIVE:
RXCHAR
405 0.00000480 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
406 0.00000400 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: +
407 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
408 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: E
409 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
410 0.00000240 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: S
411 0.00000240 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
412 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: =
413 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
414 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: 3
415 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
416 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: ,
417 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
418 0.00000240 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: 0
419 0.00000240 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
420 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: ,
421 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
422 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
0:
423 0.00000480 Portmon WriteNotifyProc COM2 VOID
TRANSMIT: TXCHAR
424 0.00000480 Portmon VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: -1
425 0.00000400 Portmon VCOMM_GetCommQueueStatus COM2
SUCCESS RX: 0 TX: 0
426 0.00000320 Portmon VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: -1
427 0.00000320 Portmon ReadNotifyProc COM2 VOID RECEIVE:
RXCHAR
428 0.00000400 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
429 0.00000400 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: 2
430 0.00000320 Portmon VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: -1
431 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
432 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: ;
433 0.00000320 Portmon VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: -1
434 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
435 0.00000240 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: +
436 0.00000320 Portmon VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: -1
437 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
438 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: D
439 0.00000320 Portmon VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: -1
440 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
441 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: S
442 0.00000240 Portmon VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: -1
443 0.00000320 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
444 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: =
445 0.00000240 Portmon VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: -1
446 0.00000240 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
447 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: 3
448 0.00000320 Portmon VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: -1
449 0.00000240 Portmon VCOMM_ClearCommError COM2 SUCCESS
NOERROR
450 0.00000320 Portmon VCOMM_ReadComm COM2 SUCCESS Length:
1: ;
451 0.00000320 Portmon VCOMM_SetWriteCallBack COM2 SUCCESS
Trigger: -1

 

[Paul]

Paul, here is the Portman log file for Win98. This is logged until
connected. Portmon works fine on Win98.

As before, multiple part post.....
This one got huge !

I connected at 38.6, which is slow for me on this computer, but it tends
to vary. I do have a bit of trouble connecting on here too, meaning
that I can call in and not actually connect, via name/password, and
occasionally it hangs, adn does nto connect at all. But this is
probably my ISP server. I'm used to that happening, usually 2 or 3
tries do the trick. Shutting off the modem, nad back on again seems to
help too when it's not trying to connect. But aside from that, I always
get a good solid and fast connection once i am connected, and I can
leave it on for hours, without it disconnecting.

This will probably take 5 parts to send....
So much repeated data, but I'm not sure what parts to delete, or I'd
trim it.

OK, but in this case, now I'm seeing the Win98 external (Creative)
modem, and not the PCTel modem in the WinXP machine.

The idea is, to compare the AT commands from the two OSes,
to see if there are any differences at the AT Hayes Command Set level.

The difference is, the external modem, the DSP portion
doesn't change, when moved from the Win98 box to the WinXP
box. In the case of the PCTel internal, both the DSP code
is different, as well as the AT command set part (INIT string)
could be different.

*******

In the two files so far, there's not even an ATDT in there.
No attempt to dial is recorded. No CONNECT message.
And I'd definitely need the Creative manual to decode this.
It's using some fancy command with multiple comma separated parameters.

AT+IBC=0,0,0,,,,,0;+PCW=2;+PMH=1
ATE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;+GCI=B5;W2
ATS7=90S30=0L3M1+ES=3,0,2;+DS=3;

To make this fun, to compare apples to apples, we
need the same modem, used by the two different OSes
(where WinXP is sucking at transfers), then look to
see evidence the INIT strings are different. If you
use a dialup modem for both cases, that eliminates
DSP differences. And to decode these things, I need
the model number off the Creative, so I can track down
roughly what manual to use.

Paul

 

[Paul]

I send parts 1 and 2 of 4 for my Win98 portman log on Win98. I reached
my data limit for the next few hours. Will send the rest later or
tomorrow.

Anyhow, on the XP computer, I ran Modem Doctor. It's an old program for
Win98, but it runs fine. However the program dont go as high as 56K.
It only goes to 19.2K THERE IS NO UPGRADE, it appears the software was
abandoned.

No matter which tests I run on there, it keeps saying there is a
problem. I'm manually typing in this message on the Win98 machine.

Modem Doctor Warning

The flow control settings in the driver are incorrect. the driver
should be set for RTS/CTS mode, but it is not. Your driver may not be
Windows compatible. Modem may fail the following diagnostic tests.

ERROR MESSAGE #2

Carrier Detection Warning

The RLS signal is active, when it should be inactive. Modem may be
indicating falsely. Try the command AT &&C1 from the Interactive
terminal otherwise, cable is wired incorrectly.

After running (ALL) CARRIER TESTS, it says:

Chars sent = 512
Originate Errors = 128
answer Errors = 128

Fixed Link Advisory

Your modem's DTE rate between computer and modem is not locked. I had
to lower the baud rate to match the link rate. For high speed modems,
the DTE rate must be locked. Check your modem manual for instructions.

---

By the way, I noticed the modem is now on COM4. It used to be on COM3.
However, when I removed and replaced it in the computer, I used a
different PCI slot (just because it was easier to put in in that slot -
There are wires and another card in the way on the original slot). Did
it change to COM4 because I changed the PCI slot? I didn't think it
would matter. However, after changing this, is when I started to get a
usable (but slow) connection. (When I can get connected).

COMMENT: While most of this is "Greek" to me, I'm thinking the Carrier
problem (above) is why it is such a pain to actually get connected.

One other comemnt, almost everytime I type in a newsgroup message, by
the time I finish the message, the modem has disconnected, (unless i am
running a browser and downloading something in the background). It
seems it wont stay connected unless there is constant data exchange.
I'm speaking about the XP computer, not the W98 one.

The disconnect timer was disabled on the PCTel modem.
Perhaps the PPP protocol has some option for timing out,
but I don't even remember any config stuff for PPP.

Your problem sounds like spiral of death, but it's pretty
hard to reach such a conclusion with the PCTel. Because it's
DSP based, and doesn't have the same behaviors as the Creative
would have. I mean, the PCTel software designers, wouldn't
"emulate spiral of death" just for fun. They have a lot more
room to do something intelligent.

If you run Modem Doctor on the PCTel modem, the "flow control"
indications are at the IOCTL level and are virtual. They still work
in a similar way to how a physical modem might, because they're intended
to emulate how an external would function. But the timing of those
events, might not make the Modem Doctor happy. Just a guess.

The PCTel doesn't have any hardware that corresponds to
a COM port. But the software still makes one, by registering
one for Device Manager. And it's all part of ensuring that
programs (like HyperTerm), see the same software interfaces
as they'd see with a real external modem.

I think in terms of policy, you can set up a modem such
that it drops the communications rate, if errors are encountered.
The alternative, is to allow retransmissions (which waste
bandwidth), and maintain the original connect rate for the
entire session. I think that's an error control policy, so
you could look at the Hayes Command Set and see if changing that
policy helps at all or not.

Paul

 

[casey.o]

OK, but in this case, now I'm seeing the Win98 external (Creative)
modem, and not the PCTel modem in the WinXP machine.

The idea is, to compare the AT commands from the two OSes,
to see if there are any differences at the AT Hayes Command Set level.

The difference is, the external modem, the DSP portion
doesn't change, when moved from the Win98 box to the WinXP
box. In the case of the PCTel internal, both the DSP code
is different, as well as the AT command set part (INIT string)
could be different.

*******

In the two files so far, there's not even an ATDT in there.
No attempt to dial is recorded. No CONNECT message.
And I'd definitely need the Creative manual to decode this.
It's using some fancy command with multiple comma separated parameters.

AT+IBC=0,0,0,,,,,0;+PCW=2;+PMH=1
ATE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;+GCI=B5;W2
ATS7=90S30=0L3M1+ES=3,0,2;+DS=3;

To make this fun, to compare apples to apples, we
need the same modem, used by the two different OSes
(where WinXP is sucking at transfers), then look to
see evidence the INIT strings are different. If you
use a dialup modem for both cases, that eliminates
DSP differences. And to decode these things, I need
the model number off the Creative, so I can track down
roughly what manual to use.

Paul

As I said ,aAIOE is not letting nme send the other parts now. I get a
"too much data sent" error. I have to wait a few hours to send any
large messages again.

So you want me to use the Creative External modem on the XP machine,
right? I'm NOT gonna put the Pctel in the W98 machine, and risk
screwing somethng up. I know that W98 is a bitch for setting up
internal modems (of course XP is proving to be a bitch for ALL
modems)

Please tell me how to install the Creative EXT modem, on the XP machine,
without uninstalling the PCtel? I'm assuming there is a means to SELECT
which modem to use.

Actually, this creative modem came with a serial and a USB cable. I can
not get it to work via the USB cable at all. I actually prefer the
serial cable, but I was just truing the USB to see what would happen. I
cant use that USB on W98, due to W98 USB limits.

Please tell me how to swap modems, and I'll install the Creative EXT
modem to the XP machine.

It's a Creative Modem Blaster External V.92
Model DE5721.

I have the drivers file on the harddrive in W98 machine. It was
originally a CD. Contains the drivers, a fax program, and IE5.5 (yuck),
plus some other useless crap. I ONLY run the driver installs, nothing
more off that thing. I dont need fax either. The drivers have a SETUP
installer file and are dated for 2002 (2K and XP). ones. There are also
drivers for W98 and Win-ME on there. The drivers for XP and 2K are
identical. ALL are from 2002, regardless of OS.

These are the same drivers that i used to install that same modem on my
W2k dual boot on my W98 machine. Same computer, same modem, same phone
line, and I have never been able to get a usable connection under
Win2000. It connects, but dont transfer data. (Pretty much the same I
got on XP).



BTW: The actual connection on the W98 occurred in part 4 of 4. Maybe I
dont need to send part 3????? You tell me..... I'll send part 4 next,
cuz AIOE will probably limit me again after one file send.....

 

[casey.o]

The disconnect timer was disabled on the PCTel modem.
Perhaps the PPP protocol has some option for timing out,
but I don't even remember any config stuff for PPP.

Your problem sounds like spiral of death, but it's pretty
hard to reach such a conclusion with the PCTel. Because it's
DSP based, and doesn't have the same behaviors as the Creative
would have. I mean, the PCTel software designers, wouldn't
"emulate spiral of death" just for fun. They have a lot more
room to do something intelligent.

If you run Modem Doctor on the PCTel modem, the "flow control"
indications are at the IOCTL level and are virtual. They still work
in a similar way to how a physical modem might, because they're intended
to emulate how an external would function. But the timing of those
events, might not make the Modem Doctor happy. Just a guess.

The PCTel doesn't have any hardware that corresponds to
a COM port. But the software still makes one, by registering
one for Device Manager. And it's all part of ensuring that
programs (like HyperTerm), see the same software interfaces
as they'd see with a real external modem.

I think in terms of policy, you can set up a modem such
that it drops the communications rate, if errors are encountered.
The alternative, is to allow retransmissions (which waste
bandwidth), and maintain the original connect rate for the
entire session. I think that's an error control policy, so
you could look at the Hayes Command Set and see if changing that
policy helps at all or not.

Paul

What does DSP mean?

I had a small program I once used to keep connected, when i had a really
crappy ISP that would keep disconnecting me. It just sent a ping every
minute or so. But this is not an ISP problem now. I can stay connected
for many hours under W98. In fact people get pissed at me because I
tend to forget to disconnect and no one can call me.

 

[Paul]

As I said ,aAIOE is not letting nme send the other parts now. I get a
"too much data sent" error. I have to wait a few hours to send any
large messages again.

So you want me to use the Creative External modem on the XP machine,
right? I'm NOT gonna put the Pctel in the W98 machine, and risk
screwing somethng up. I know that W98 is a bitch for setting up
internal modems (of course XP is proving to be a bitch for ALL
modems)

Please tell me how to install the Creative EXT modem, on the XP machine,
without uninstalling the PCtel? I'm assuming there is a means to SELECT
which modem to use.

Actually, this creative modem came with a serial and a USB cable. I can
not get it to work via the USB cable at all. I actually prefer the
serial cable, but I was just truing the USB to see what would happen. I
cant use that USB on W98, due to W98 USB limits.

Please tell me how to swap modems, and I'll install the Creative EXT
modem to the XP machine.

It's a Creative Modem Blaster External V.92
Model DE5721.

I have the drivers file on the harddrive in W98 machine. It was
originally a CD. Contains the drivers, a fax program, and IE5.5 (yuck),
plus some other useless crap. I ONLY run the driver installs, nothing
more off that thing. I dont need fax either. The drivers have a SETUP
installer file and are dated for 2002 (2K and XP). ones. There are also
drivers for W98 and Win-ME on there. The drivers for XP and 2K are
identical. ALL are from 2002, regardless of OS.

These are the same drivers that i used to install that same modem on my
W2k dual boot on my W98 machine. Same computer, same modem, same phone
line, and I have never been able to get a usable connection under
Win2000. It connects, but dont transfer data. (Pretty much the same I
got on XP).



BTW: The actual connection on the W98 occurred in part 4 of 4. Maybe I
dont need to send part 3????? You tell me..... I'll send part 4 next,
cuz AIOE will probably limit me again after one file send.....

If you connect the modem to WinXP, you'd probably need to
"Scan for hardware changes" in Device Manager or something.
I don't remember what I did with mine. There's some text
here, about some things to try.

http://forums.cnet.com/7723-6142_102-40048/winxp-pro-can-t-detect-my-modem/

I was able to use my modem, under WinXP, after convincing it to
"eat" a generic driver. The driver was Unimodem, rather than
a branded US Robotics driver (as my modem was too old).

For the external, you don't need a "custom" driver, and can
potentially get away with using a generic driver from the
list of modem drivers.

The WinXP installer CD, would have a bunch of files with
"mdm" in the name, and that would be part of the collection
of modem install files. For example, I was able to find a
mdmpctel.in_, which is a compressed version of mdmpctel.inf.
That would be how your PCTel got installed.
But for my USRobotics, the USR-provided driver in WinXP,
refused to install, because my modem was too old.

*******

Your original theory was, there was a difference between
the way Win98 and WinXP use the modem, leading to
what appeared to be spiral of death symptoms. We
need a set of test conditions, where only differences in
the Hayes Command Set used, could account for it.
For PCTel type modems, it's not going to be possible to
reach any conclusions about what the DSP is doing, as it
isn't viewable. That means using the Creative External, because
we can apply debugging techniques to it.

I know you're working mightily to post the PortMon data,
but there is an alternative you could try. Pastebin
is a site that accepts text pastings. You could upload
the entire PortMon thing there, get the URL generated
from the upload and just post that here.

I just pasted five lines of text here, for you to look at.
Controls on the pastebin site were set to defaults.

http://pastebin.com/AG3hpPge

Paul

 

[Paul]

What does DSP mean?

I had a small program I once used to keep connected, when i had a really
crappy ISP that would keep disconnecting me. It just sent a ping every
minute or so. But this is not an ISP problem now. I can stay connected
for many hours under W98. In fact people get pissed at me because I
tend to forget to disconnect and no one can call me.

DSP means Digital Signal Processing. It uses the CPU on
your computer, to convert the "tones" on the phone line
(frequency buckets), into ones and zeros.

Yes, keep-alive programs can use things like ping, to keep
a connection open. I even use that on download links that
are performing poorly. Like a site I was using within the
last month, where it was delivering data at around 1KB per
second. And pinging the site, helped a tiny bit.

Back in my dialup days, I used to pay for Bell Voicemail,
so I had an answering machine at the phone company. That
allowed people to phone me and leave a message, at the same
time I was online. Doing it that way, it's not an "either/or"
kind of service. When the line is busy, the Bell Voicemail
would pick up at the phone company, and take the message.
The worst service I got out of that thing, was once it
took around 12 hours, before a call recorded on that system,
was accessible to me. So occasionally, it behaves like
a lot of other computerized stuff we use (i.e. not well).

Once I got ADSL, I was able to cancel the VoiceMail feature,
and put the saved money into the ADSL monthly bill instead.
ADSL doesn't block the phone, and so I just use a plugin
telephone recorder now, to take a message.

You could ask your phone company, if ISDN is available,
and see what kind of rate they'd charge for a 128Kbit (2B+D)
connection. The advantage of using that, is the
terminal equipment installed in your house, allows
the phone to work while you're online. And when you're
not using the phone, it goes about twice as fast as dialup.

Paul

 

[casey.o]

I just pasted five lines of text here, for you to look at.
Controls on the pastebin site were set to defaults.

http://pastebin.com/AG3hpPge

Paul

Ok, here it is.....
http://pastebin.com/k6eL8RU7

I think I figured out how to install 2 modems, Use ENABLE and DISABLE
in control panel to select the one I want to use.

Let me know if that pastebin works....
That's a handy gadget..... sure beats flooding the newsgroup with all
that stuff.

 

[Paul]

Ok, here it is.....
http://pastebin.com/k6eL8RU7

I think I figured out how to install 2 modems, Use ENABLE and DISABLE
in control panel to select the one I want to use.

Let me know if that pastebin works....
That's a handy gadget..... sure beats flooding the newsgroup with all
that stuff.

Creative Modem Blaster V.92 DE5721 (Win98)

Crappy text version of Conexant generic Hayes AT command set

http://ask.creative.com/wwenglish/modems/at_conexant.htm

A PDF version of the same document, where the Index at the
front makes things slightly more bearable.

http://www.linuxant.com/drivers/hsf/free/archive/100498D_RM_HxF_Released.pdf (703KB)

*******

This is from your pastebin, for Win98

ATZ&F
AT+IBC=0,0,0,,,,,0;+PCW=2;+PMH=1
ATE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;+GCI=B5;W2
ATS7=90S30=0L3M1+ES=3,0,2;+DS=3;
AT+IFC=2,2;BX4
ATDT;
ATDT555-1212

AT
+IBC ??? - can't find this in the manual
+PCW=2 Ignore Call Waiting
+PMH=1 Disable Modem Waiting

AT
E0 disable command echo
V1 Enables long-form (verbose) result codes
S0=0 disable auto-answer
&C1 RLSD follows the state of the carrier
&D2 Hang up on falling edge of DTR
+MR=2 Enables reporting of modulation connection (+ MCR:
and Receive Rate Only: are transmitted)
+DR=1 Data compression reporting enabled
+ER=1 Error control reporting enabled
+GCI=B5 Country of Installation = USA
W2 Upon connection, the modem reports the DCE speed

AT
S7=90 Wait Time For Carrier 90 seconds
S30=0 Disconnect Inactivity Timer = disabled
L3 Speaker volume HIGH
M1 Speaker ON
+ES=3,0,2 Original request = Initiate V.42 with Detection Phase
Fallback = Initiate call with Direct Mode
Answer = Initiate V.42 without Detection Phase
+DS=3 Data Compress = V.42bis P0=11 (default compression)

AT
+IFC=2,2 DTE Hardware flow control, CTS/RTS
B ??? - can't find this in the manual
X4 CONNECT <text> when connected...

OK, we'll see what kind of a mess that WinXP
makes of this. No evidence it's a V92 modem
in that capture.

Paul

 

[casey.o]

OK, we'll see what kind of a mess that WinXP
makes of this. No evidence it's a V92 modem
in that capture.

Paul

I planned to do that, and for soem reason, Portmon will NOT capture a
log file (or do anything) with that external modem connected. I did
connect again, but nothing was saved in Portmon. I used it the same way
as before..... I even deleted all the old .log files.

I dont know what is going on anymore. I got pissed off, and jsut shut
off the damn XP computer for awhile again. I'm back on Win98, which
works!

XP is /NOT/ what I expected. I always heard it was plug-n-play for
almost everything. Thats surely not true. Win98 is more P n P than XP
(at least for modems). The last time I had this much trouble with
modems, was back in the early 90's using Win 3.x. I've had Win2000
installed for around 5 years, and after hours and hours of trying, I
never could get that to connect properly either. If it wasn't for W2k
solving some of my USB connection problems with those external hard
drives, I'd delete it from my computer to save drive space. I never
even boot to it except for USB needs.

 

[casey.o]

The PortMon 3.02 has a menu to select the COM port to capture.
You need to set that, before beginning the capture. As the
"other" COM port will be silent.

Paul

I'll have to check that. I needed a break from damn thing this again.
All the time I've spent trying to get this thing to work seems like a
total waste at this point. Same shit I've dealt with using Win2000, and
could never resolve during 5 years. In fact, after putting the XP
machine away, I booted over to Win2000, and went online. During the
first 3 minutes, I was able to open some web pages, it got slower and
slower, and at about 20 min, I could not get anything. Even my
newsreader said "winsock error", yet I was connected. Same shit that XP
is doing! (Except using that internal PCTel modem, I can remain
connected, but it's very slow.) I'm wondering if this Creative modem is
just not suited to Win 2K and XP? Or, maybe none of those NT based OSs
are suited to dialup ?????

I'll send you that Portmon log, but I dont feel there is any solution
anymore. I guess I'm just plain frustrated. I guess I can continue to
use W98 for a few more years online, but will have less and less access
to the web. I'm thinking more and more about buying an Apple computer.
That would be mostly for the internet, while W98 will continue to run my
other programs just fine. There dont seem to be many more options.
Yea, I know, someone will suggest Linux again.....

I dont expect much, I just want an OS that will run newer browsers, and
connect at the same speed I get with W98 on dialup. High Speed internet
would be nice, but for most uses, my dialup is fine on W98 for my needs.
But waiting 20 minutes for one web page to load, and then completely
failing is NOT acceptable on XP or W2K. Even if I could only use W2K,
I'd be happy, since that allows newer browsers. After all, W2K is
mostly the same as XP, minus some things and most of the bloat. I have
the SP4 version installed. I have found XP to be a little more user
friendly though, once all the bloat is removed.

 

[Paul]

I'll have to check that. I needed a break from damn thing this again.
All the time I've spent trying to get this thing to work seems like a
total waste at this point. Same shit I've dealt with using Win2000, and
could never resolve during 5 years. In fact, after putting the XP
machine away, I booted over to Win2000, and went online. During the
first 3 minutes, I was able to open some web pages, it got slower and
slower, and at about 20 min, I could not get anything. Even my
newsreader said "winsock error", yet I was connected. Same shit that XP
is doing! (Except using that internal PCTel modem, I can remain
connected, but it's very slow.) I'm wondering if this Creative modem is
just not suited to Win 2K and XP? Or, maybe none of those NT based OSs
are suited to dialup ?????

I'll send you that Portmon log, but I dont feel there is any solution
anymore. I guess I'm just plain frustrated. I guess I can continue to
use W98 for a few more years online, but will have less and less access
to the web. I'm thinking more and more about buying an Apple computer.
That would be mostly for the internet, while W98 will continue to run my
other programs just fine. There dont seem to be many more options.
Yea, I know, someone will suggest Linux again.....

I dont expect much, I just want an OS that will run newer browsers, and
connect at the same speed I get with W98 on dialup. High Speed internet
would be nice, but for most uses, my dialup is fine on W98 for my needs.
But waiting 20 minutes for one web page to load, and then completely
failing is NOT acceptable on XP or W2K. Even if I could only use W2K,
I'd be happy, since that allows newer browsers. After all, W2K is
mostly the same as XP, minus some things and most of the bloat. I have
the SP4 version installed. I have found XP to be a little more user
friendly though, once all the bloat is removed.

There is a utility shown here, called ModemChk. You don't
need to click this (or buy the utility for that matter), because
you can DIY.

https://web.archive.org/web/20010208181902/http://808hi.com/56K/modemchk.htm

All it does, is issue command

ATI11

to the modem. You can do the same thing by using HyperTerm (WinXP) or Putty (third party).
You can talk to the modem and gather information.

In Device Manager, the modem item, if you do Properties on it,
has a Diagnostic tab. It runs various ATInn commands, but it doesn't
use high enough values of "nn". If you run the diagnostic tab, and
click the log button on the Device Manager modem dialog, you can
see the output of the various calls to ATInn.

But, you can also set up HyperTerm, to talk to the modem, type in
an AT command and get answers back.

You see, some of the modem functions, involve "memory". The modem
remembers the "last session". It remembers it as long as the
power doesn't go off.

In this FAQ item, a Multitech modem dumps 26 lines of information.
I suspect these lines could have used some editing.

http://www.multitech.com/en_us/SUPPORT/Help/resolutions/res2078.asp

Last Connection 56K V.90
Initial Transmit Carrier Rate 28800 28800
Initial Receive Carrier Rate 50000 49333
Final Transmit Carrier Rate 28800 28800
Final Receive Carrier Rate 50000 49333
Protocol Negotiation Result LAPM LAPM
Data Compression Result V42bis V42bis
Estimated Noise Level 152 152
Receive Signal Power Level (-dBm) 25 25
Transmit Signal Power Level (-dBm) 16 16
Round Trip Delay (msec) 4 4
Near Echo Level (-dBm) NA NA
Far Echo Level (-dBm) NA NA
Transmit Frame Count 3 3
Transmit Frame Error Count 0 0
Receive Frame Count 0 0
Receive Frame Error Count 0 0
Retrain by Local Modem 0 0
Retrain by Remote Modem 0 0
Rate Renegotiation by Local Modem 0 0
Rate Renegotiation by Remote Modem 0 0
Call Termination Cause 0 0
Robbed-Bit Signalling 00 00
Digital Loss (dB) 6 6
Remote Server ID 4342C3 NA
Last PCM S PTR
OK

Now, I just ran this on HyperTerm (without dialing
anything, dismiss the icon line and just use it to
the respective COM port). And this is what my modem
reports for ATI11. Not quite as much information.

U.S. Robotics 56K FAX EXT Link Diagnostics...

Modulation Unknown Speed
Carrier Freq (Hz)
Symbol Rate
Trellis Code
Nonlinear Encoding
Precoding
Shaping
Preemphasis (-dB)
Recv/Xmit Level (-dBm)
Near Echo Loss (dB)
Far Echo Loss (dB)
Carrier Offset (Hz)
Round Trip Delay (msec)
Timing Offset (ppm)
SNR (dB)
Speed Shifts Up/Down 0/0
Status :
OK

My modem did not return any "numbers", because
I haven't completed any calls That's why the fields
are empty.

In your case, you'd do a dialup session on the modem, then
when the session is finished, open HyperTerm and "talk" to the
modem. HyperTerm should be in Accessories/Communications menu
portion of the Programs menu on WinXP.

There's no guarantee what you'll find there, or even whether
ATI11 on the modem is detailed enough.

There is also some command, that dumps the information about
the frequency bins used in the 4KHz telephony passband. And
there used to be a web page, which explained how to interpret
that (to come up with ammunition to convince the telco to fix
the line).

Both of those capabilities, ATI11 or the frequency bin thing,
require that the modem complete a previous session, so some
"history" is available.

Paul

 

[casey.o]

There is a utility shown here, called ModemChk. You don't
need to click this (or buy the utility for that matter), because
you can DIY.

https://web.archive.org/web/20010208181902/http://808hi.com/56K/modemchk.htm

Thanks Paul,

I'm busy with other stuff, so I dont hae time to mess with this now, but
I thought I'd download that program while doing other stuff. It turns
out the URL link on that page is worthless....

Maybe I can find it on oldapps.com or one of those type of sites, but I
cant look now.

Just letting you know.

 

[Paul]

Thanks Paul,

I'm busy with other stuff, so I dont hae time to mess with this now, but
I thought I'd download that program while doing other stuff. It turns
out the URL link on that page is worthless....

Maybe I can find it on oldapps.com or one of those type of sites, but I
cant look now.

Just letting you know.

Well, I said not to bother with that page.

As you can do this for yourself, using a copy of Hyperterm.

You don't need the fancy dialog box. And you don't really know
until you try the ATI11 command on the modem, how good the report
is. The one on mine isn't much good, because it doesn't report
the starting baud rate and the rate it had dropped to later.

Paul

 

[casey.o]

Well, I said not to bother with that page.

As you can do this for yourself, using a copy of Hyperterm.

You don't need the fancy dialog box. And you don't really know
until you try the ATI11 command on the modem, how good the report
is. The one on mine isn't much good, because it doesn't report
the starting baud rate and the rate it had dropped to later.

Paul

PAUL, I really appreciate all you have dont to try and help me, but I'm
finished with it. It's gotten way beyond just getting on my nerves.
Like I said in another message, this is like trying to find a needle in
a haystack. All the possible init strings, combined with all the other
settings, that this could go on for the rest of my life and beyond....
There are probably billions of possibilities. The moden has no support
and the drivers are outdated. I cant find much of anything about it and
the company has no support anymore. I've spent damn near a full week on
this, and I have other priorities in my life that are more important and
much less stressful. I thought someone would suggest some software that
could find the problem and fix it, or at least tell me what to do. But
spending weeks trying all sorts of settings which I mostly dont even
understand is not my cup of tea. So, I'm done with it. I'll get
another modem, one that has support. If that dont work, there will be
an Apple computer in my future. In the meantime I still have Win98.

Again, I appreciate your help, but I hope you understand where I'm
coming from. This sort of thing is exactly why I wont use linux. I'm
no computer geek, and dont want to be. I can do the hardware part,
because I used to work with electronic repair, and I can install an OS,
but when it comes to all these settings, it's all greek to me, and I
find it extremely stressful. Actually I think the drivers are just no
good for 2K and XP. But there are no newer ones.

Thanks again

 

[Paul]

Thanks again

No problem

With your US Robotics modem on the way, you
can try that one out and see if it helps.

Paul

 

[Paul]

It's really a pity that this issue has been so vexing, since if it weren't
for this, he could be up and running well with XP. It's still surprising to
me that this low bitrate problem with XP (but not 98) even occurs.

Playing with modems is loads of fun, since they
made it so difficult to make headway.

In one case here, I ended up ripping out a wall jack
and replacing it, and the data rate came back up.

With my Macintosh, I ended up crafting my own INIT
string, because the one provided just wasn't working
right.

And with the US Robotics one, I learned you can use
Unimodem driver (part of WinXP installation, so the
Unimodem driver is already onboard), and that one seemed
to work.

At least with the USR modem, the DSP portion isn't likely
to be a variable, and then the INiT string is what counts.

Other than that, it could be an electrical problem, like some
difference in chassis noise between the WinXP machine and the
Win98 one. As far as I know, the DAA on the modem, should
provide isolation of anything dangerous, but I don't know if
every possible chassis noise problem is properly handled. All
it might take, is running one computer off a two-prong power
cable, instead of a three-pronged one, to put some hum on the
modem end. It should ignore the hum, but if the noise component
had any harmonic content, that could be an issue (as then it
would extend up into the voiceband).

Every experience with a dialup modem, is a learning experience.

Paul