Bill said:
It was 42 MB over here, not 180 Meg (and that was very recently). I don't
know which version you were looking at, but it doesn't have to be that big.
Apparently that 180 one includes a whole bunch of other stuff you don't
need.
As for trying to network two PC's using dial-up to allegedly get your XP on
dial-up through the other one, I can't even imagine.
You can use ICS, on a machine with two network interfaces, to
share the network.
Modem Ethernet
The-Internet ------ ICS_Machine ---------- Some-other-machine-with-regular-LAN-setup
You could dial out with the ICS_Machine, and do your stuff that way.
Why they make articles like this, with absolutely no pictures,
is beyond me. There are so many useful pictures you could draw,
of working and non-working ICS setups, that would be so helpful.
http://en.wikipedia.org/wiki/Internet_connection_sharing
*******
All I can say, is unless you get into the Hayes Command Set, and
understand what's going on, you'll never fix it
I know this
for experiences, over and over again. Spread over probably 10-15 years.
On equipment as pitiful as Macintoshes. And PCs.
OK, now for some fun.
I wanted to find a serial port logger. I could find a commercial
one, I could find one that promised a download from CNET, but that
would mean dealing with nasty boring toolbars.
Then, I noticed Sysinternals wrote a Portmon. It records
serial port I/O calls.
Now, it would be too simple to just go to the web site and
get the current version and have it work. This is version 3.03,
the current one. Now, this is missing a crucial menu column at the top.
There is no way to "start" a capture. The capture menu is
grey. So forget the current version. We need to go back in time.
http://technet.microsoft.com/en-us/sysinternals/bb896644.aspx
How this works, is the author of this was not happy with just
capturing serial I/O. The tool was also designed to work
remotely. For that to happen, one copy of Portmon runs on the
computer you want to log. That is the "server". The other
copy runs on the server where you want to view what is
going on. That copy of the program is called the "client".
An older version of the program, has a "Connect Local" option.
That makes the one program, running on your WinXP machine,
perform both the "server" and "client" roles on the same computer.
This is version 3.02, which has the "Connect local" option.
This is the one that works.
https://web.archive.org/web/2008010...icrosoft.com/en-us/sysinternals/bb896644.aspx
This is the 142KB download. Unzip this in a separate folder.
Double click portmon.exe to run it. You should have administrator
rights, as this is going to install a temporary filter driver
in the serial port. When you shut down the program, no residue is
left behind. Mark writes portable programs, in the best possible way.
https://web.archive.org/web/20080102163853/http://download.sysinternals.com/Files/PortMon.zip
Once you do the Computer : "Connect Local", go to the
Capture menu. In there, the Capture item at the top will
have a tick next to it. Now, the next item down is "Ports".
I selected my COM3 port, which has my modem.
As a test, I went to Device Manager, selected the USR Modem,
went to the Diagnostic tab. clicked the button to run the
dialup diagnostics. This sends commands to the serial port.
The log in PortMon then starts to fill with data. I can save
the log file for later, using Save As in the program. Once I've captured
enough information to have the important bits in the log.
When the modem transmits, the PortMon captures an
entire string. In this case, a Hayes AT Command set
command is being sent. The program sending the command
is "mmc", which is the thing that makes the Device Manager
display on your screen. When debugging your setup, the name
will be other than "mmc.exe". My serial port, rather than
being "serial0" as Mark's documentation would show, is "VPC1",
because my serial port is a USB to RS232 dongle. Again, yours
will be different.
96 0.00046805 mmc.exe IRP_MJ_WRITE VCP1 SUCCESS Length 80: ATQ0V1E0........................................................
When the modem answers, for some reason, the characters
are logged individually. This is what you would normally
get from a Hayes AT command which doesn't have any
particular data output. The modem has returned "OK".
If you send "AT" to a modem, it says "OK" as an answer.
The two characters here, have received separate timestamps.
109 0.00000111 mmc.exe IRP_MJ_READ VCP1 SUCCESS Length 1: O
110 0.00000108 mmc.exe IRP_MJ_READ VCP1 SUCCESS Length 1: K
With this information in hand, you can start PortMon running,
log the port, then attempt to do DUN (Dialup Networking) in
WinXP. What you're looking for, is only the initial captures,
where the INIT string is being fed to the modem. Once we have
that, then the fun can begin. Post the string when you find
it, as well as the make and model number of the modem.
The INIT string could include stuff similar to my
example "ATQ0V1E0", followed by things like a phone
number "ATDT5551212". They may break the string into
separate AT commands, or attempt to load the whole
thing in one shot. This portion of the transaction,
is before PPP begins to run, and send authentication
info. If you specify some form of encryption in your
PPP session, the authentication info may be
encrypted. None of that is important at the moment,
because we don't care about the PPP stuff. Just the
Hayes strings matter at the moment. Stuff that will
be very near to the beginning of the trace. You can
replace the phone number with 5551212 when you post
the strings you find. I don't plan on testing your
modem pool. And please don't post the strings with
your PPP username or password, if they happen to be
in plaintext.
Paul
