Question on KB181599 reinstalling TCP/IP

I'm reviewing "How to Remove and Reinstall Dial-up Networking and TCP/IP
Files" (KB 181599) and have an understanding question or two about why
I'm removing files and possible reinstall updates.

Background:

I have been dealing with a problem that arises when I try to install a
new network component. Have spent time with Gary T in the Windows98
Network user group going over all possibilities we could think of to
prove the trouble was a network problem, driver problem, or hardware
problem. The conclusion I've reached is that it is not.

The problem In a nutshell: I have no problem communicating on a local
network (5 computers and print server) or internet, via wireless router
and cable modem). When I install a new network item, I loose the
capability go internet, and any attempt to go internet manifests itself,
depending upon the application, in Access Violations, Invalid page
faults, application shut down or non starting.


I'm now focusing on possible corruption of file(s) in the TCP/IP protocol
that runs perfectly for what exists but then causes a problem when used
to introduce a new network interface card.

Now for the Questions:

In the KB 181599 article you are instructed to first rename a bunch of
files (about 35) as part of the remove and reinstall process. I can
appreciate that one or several of the files might have been corrupted and
that you are now going to do a reinstall with a clean slate (that is go
back to the cab files and install original Win98 files). When you remove
and reinstall TCP/IP you go to Control Panel Network and remove all the
entries, reboot and then reinstall a network component (You do the
similar thing for DUN, but I don't have DUN);

Question 1: On the reinstall does Windows use files that have been
previously installed? And not build from scratch?

Question 2: What do I then do if any of these files have subsequently
been updated by Microsoft or applications?


TIA.

1. It uses the files from your Windows CD.

2. Deal with any file version problem that might occur if it does occur.

I found that just moving the files to another folder (or deleting them) is a
lot faster than trying to rename them.

I have also found that just doing the procedure listed in the KB article
will not always cure DUN problems in that the registry entries could also be
the source of the problem. Here is an article I wrote some time ago and I
think it is probably still current:

1. To remove the DUN registry keys, go to Control Panel, Add-Remove
Programs, Windows Setup tab, double click Communications and make a list of
checked items. Hit cancel, remove the mark from Communications and hit OK.
Do not reboot.

2. Go to Control Panel, Network, and make a list of the components that are
installed. Leave any hardware adapters (i.e., NICs, IR ports, etc.) that
are present unless you want to reinstall the drivers for them. Delete all
adapters, clients and protocols such as Dial Up Adapter, Client for MS
Networks, and TCP/IP. Hit OK and reboot.

3. Once restarted, go to Run on the start menu and type: scanreg and hit
enter. Back up the registry when given the option. Open the registry
editor (regedit.exe) and delete these keys:

HKey_Local_Machine\System\CurrentControlSet\Servic es\Remote Access
HKey_Local_Machine\System\CurrentControlSet\Servic es\Winsock
HKey_Local_Machine\System\CurrentControlSet\Servic es\Winsock2
HKey_Local_Machine\System\CurrentControlSet\Servic es\VxD\Winsock
HKey_Local_Machine\System\CurrentControlSet\Servic es\VxD\Winsock2

4. Reboot. Go to Control Panel, Add-Remove Programs, Windows Setup tab,
double click Communications, mark the entries previously noted (assumes
they were all needed) and be sure to mark dial up networking. Hit OK but do
not reboot.

5. Go to Control Panel, Network. Add the components previously identified
(assumes all were needed) and ensure that Client for MS Networks, Dial Up
Adapter and TCP/IP are marked. Hit OK and reboot.

6. In conjunction with this, you may want to try this procedure which
replaces the DUN files:

How to Remove and Reinstall Dial-Up Networking and TCP/IP Files [Q181599]
http://support.microsoft.com/support.../q181/5/99.asp


--
Regards


Ron Badour, MS MVP for W98
Tips: http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo



"T. Duprex" tduprexATlandmark.net wrote in message
...
I'm reviewing "How to Remove and Reinstall Dial-up Networking and TCP/IP
Files" (KB 181599) and have an understanding question or two about why
I'm removing files and possible reinstall updates.

Background:

I have been dealing with a problem that arises when I try to install a
new network component. Have spent time with Gary T in the Windows98
Network user group going over all possibilities we could think of to
prove the trouble was a network problem, driver problem, or hardware
problem. The conclusion I've reached is that it is not.

The problem In a nutshell: I have no problem communicating on a local
network (5 computers and print server) or internet, via wireless router
and cable modem). When I install a new network item, I loose the
capability go internet, and any attempt to go internet manifests itself,
depending upon the application, in Access Violations, Invalid page
faults, application shut down or non starting.


I'm now focusing on possible corruption of file(s) in the TCP/IP protocol
that runs perfectly for what exists but then causes a problem when used
to introduce a new network interface card.

Now for the Questions:

In the KB 181599 article you are instructed to first rename a bunch of
files (about 35) as part of the remove and reinstall process. I can
appreciate that one or several of the files might have been corrupted and
that you are now going to do a reinstall with a clean slate (that is go
back to the cab files and install original Win98 files). When you remove
and reinstall TCP/IP you go to Control Panel Network and remove all the
entries, reboot and then reinstall a network component (You do the
similar thing for DUN, but I don't have DUN);

Question 1: On the reinstall does Windows use files that have been
previously installed? And not build from scratch?

Question 2: What do I then do if any of these files have subsequently
been updated by Microsoft or applications?


TIA.

Ron:

I appreciate the response. As you might have anticipated, I have a few
more questions.

1. It uses the files from your Windows CD.

Question: If it does use files from the CD, then why delete them if they
will be overwritten? (Not a challenge, just curious as to the reason)

DUN:

I don't think I have a need for DUN, never did. However, I found that it
was not installed when I started this trouble project, at least installed
properly.

In the early stages of this project, ISCDCLT was one of two items I found
in my startup that when disabled seemed to reduce the fallout of the
problem. Researched what it was there for in the first place, and
discovered the link to DUN. Since I never did computer to computer
communication I wanted to uninstall it as opposed to just disabling it in
startup. I went to COMMUNICATIONS in my Add/Remove Windows Setup and
double clicked however, DUN did not appear! I then installed DUN. Then
did the unistall/reinstall sequence (but without renaming or removing
files or registry entries). That did not fix my problem, but I've left it
installed.

Question: Is DUN required even though I just communicate via NIC,
wireless router cable modem to intra and internet using TSP/IP?


NOTE: (I maintain an Image of my system that I use to restore when I go
through testing that has not cleared the problem. This way I am dealing
with the original conditions I found rather than compounding the issue.
Once the trouble is in I've found no way, save restore the image, to
eliminate the fallout and be able to go internet)

I don't think they will be overwritten if the files on the drive are newer
than the ones on the CD. What you are trying to do with this procedure is
get back to a basic DUN configuration to see if it cures the problem
necessitating the procedure.

DUN is only required when you use dial up; however, it doesn't hurt to have
it installed. My laptop runs off of a wireless cable modem and I have DUN
installed for use when I am on the road and can't get wireless.

--
Regards


Ron Badour, MS MVP for W98
Tips: http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo



"T. Duprex" tduprexATlandmark.net wrote in message
...
Ron:

I appreciate the response. As you might have anticipated, I have a few
more questions.

1. It uses the files from your Windows CD.

Question: If it does use files from the CD, then why delete them if they
will be overwritten? (Not a challenge, just curious as to the reason)

DUN:

I don't think I have a need for DUN, never did. However, I found that it
was not installed when I started this trouble project, at least installed
properly.

In the early stages of this project, ISCDCLT was one of two items I found
in my startup that when disabled seemed to reduce the fallout of the
problem. Researched what it was there for in the first place, and
discovered the link to DUN. Since I never did computer to computer
communication I wanted to uninstall it as opposed to just disabling it in
startup. I went to COMMUNICATIONS in my Add/Remove Windows Setup and
double clicked however, DUN did not appear! I then installed DUN. Then
did the unistall/reinstall sequence (but without renaming or removing
files or registry entries). That did not fix my problem, but I've left it
installed.

Question: Is DUN required even though I just communicate via NIC,
wireless router cable modem to intra and internet using TSP/IP?


NOTE: (I maintain an Image of my system that I use to restore when I go
through testing that has not cleared the problem. This way I am dealing
with the original conditions I found rather than compounding the issue.
Once the trouble is in I've found no way, save restore the image, to
eliminate the fallout and be able to go internet)