Robert Donovan wrote:
On 9/14/07, Paul G. Allen <[EMAIL PROTECTED]> wrote:
[snip]
It's nice to know that Windows phones home without me telling it that it
can. I'm curious to know how often newer versions of Windows phone home.
I also find it interesting that it seems the only way to disable the
network connection completely (once you've configured it), is to unplug
the cable or un-configure it.
It makes one appreciate Linux that much more.
PGA
Newer versions do the same thing because MS can't imagine that you
wouldn't want to have them constantly checking your system for pirated
software, and automatic updates and security fixes, of which most of
the latter wouldn't be needed if they'd get it right to begin with.
The latest thing is their GenuineAdvantage executable, which embeds
itself into the registry and, in addition to informing you with
annoying pop-up balloons of new updates, forbids you from updating
anything until they've rifled through your system to check for
unlicensed software. Oh, and you you won't be allowed to update
anything unless you have GA installed, so just saying no to it is not
an option. If they find anything suspicious, the update stops. One way
to mitigate this somewhat is to get a copy of XP anti-SPY from
http://xp-antispy.org and follow the directions. One of the things it
does, its turn off all automatic updates. Be aware though, you'll
still need to install genuine advantage if you want to do updates and
the updates automatically turn all the stuff back on that antiSPY
turns off, all without your knowledge or consent, of course, so you
need to run antiSPY after each update. AntiSPY doesn't remove the
genuine advantage software, unfortunately.
Robert Donovan
Well, maybe that's what M$ wants everyone to believe, but I have _very_
intimate knowledge of someone (who shall remain nameless - we'll call
them The Person) running "The Devil's Own" version of XP Pro and has
none of these problems so far.
In fact The Person had M$ do an update to the machine just yesterday
even though it is not running WGA. It /wants/ to install WGA; it pleads
and begs to install WGA, but the Person won't let it.
The only /potential/ refusal on the part of M$ was when The Person
needed to install a fairly new patch to the Wireless Client so that The
Person could connect XP to an AP using WPA2-Personal[1].
The patch is not part of the Windows Update system. It has to be added
explicitly. But the process requires the user to run a WGA-type
validation tool, which, after mucking through one's computer, generates
a pass-code, which in turn is used on the M$ website as a key to
entrance into the Seekrit Software Download Vault.
Of course, not trusting such a tool, The Person did some additional
research which led them to a site whose author said "You can get this
patch from M$ <here> or...just get it directly from me"[2].
Problem solved, patch scanned, installed, and working. Risky? Yes, but
then, that's intrinsic in the process of running any Windows OS, pure or
otherwise. Nevertheless, The Person is happy because they can still run
their games. BioShock here they come!
[1] Windows Wifi out-of-the-box sucks! Security options are Open or
Shared, with the only encryption available being WEP. If things don't
work, unless you're a Windows Guru, not much way to debug, let alone
fix, the problem. The latest patch, KB917021, at least adds WPA/WPA2
(including Radius support).
[2] One can also use Autopatcher. Although its author has been ordered
to stop doing M$'s job better than M$, there are available update files
current as of August 2007, at least on mirror sites, like
http://www.ap.500words.ca/category/windows-xp.
--
Best Regards,
~DJA.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
