Text 774, 68 rader
Skriven 2014-01-07 21:52:00 av Ed Vance (12451.windowsa)
Ärende: SVCHOST and WindowsUpdate
=================================
Lots of days I am seeing Windows Update's (WU) SVCHOST program
Hogging XP's Task Manager (TM).

Recently I learned if I start TM and then Minimize it I can see
TMs Task Bar Icon indicating lots of CPU use and it is SVCHOST
that is the cause of the heavy CPU use.

I was reading about SVCHOST on Ask-Leo and noticed a lot of
the comments about WU and SVCHOST were dated in May 2007.

The first time I noticed SVCHOST running back in December 2007
I made a Search for the word on ask.com and found a article
from Leo in the Results listing and after reading it I signed
up for his Email Newsletter.

I've read articles about the same thing happening near the end
of this last year (2013) with comments that Microsoft is going
to issue a Fix for this problem that people started noticing
almost Seven Years Ago.

Is anyone else seeing a Slow Down on their computer that runs
any Windows OS?

Another thing bothering me is that if my XP box has been the
only thing connected to the internet through my router I will
see the IP Address of 192.168.1.100 is used (usually).

But it seems anytime I turn on the Vista box after I have been
using the XP box, I will keep the DOT 100 IP Address UNTIL I
turn the computers and router OFF and the next time I start up
the XP box I don't get DOT 100, but I get DOT 101 or another
100 series number, even when I hadn't turned the Vista box ON.

I thought I solved the DOT 100 problem by always unplugging
the CAT-5 LAN wire from the Vista box whenever I turn things
off so the Vista box won't GRAB the DOT 100 IP Address for
its self which I've noticed that "it" will do if I turn on
Vista with the LAN wire plugged in to "it" before I turn on the
XP box.

Why this bothers me is for some reason the GETLOG program that
is used along with WallWatcher, will give me a POP UP saying that
GetLog can't contact my Linksys router.

When I start GetLog it wants to connect to the Routers IP Address
of 192.168.1.1 after I tell it my routers Users Name and the
Password that I have set up, BTW which ISN"T the one Linksys
set it to use.

Now 'Once In A While' GetLog will work O.K. even if the XP box's
IP Address is 192.168.1.101 , but later during the session it will
start complaining that it can't contact the router so the Log
in WallWatcher could be updated.

I've been trying to learn how to tell the XP box to stop using
the DOT 101 Address and start using the DOT 100 Addrss that seems
to let GetLog work O.K. .

I know I can't do that while in a Limited Users Account, but I
would like to know of a Command I can use to make a Batch file
that I could run when ever I see the XP box is given a different
IP Address other than the DOT 100, so I can have things going
MY WAY!.

... Why does only one company make the game "Monopoly"?
--- MultiMail/Win32 v0.49
--- SBBSecho 2.12-Linux
 * Origin: telnet & http://cco.ath.cx - Dial-Up: 502-875-8938 (1:2320/105.1)