Several different choices of links for the KB number I gave yesterday.
(Sorry I did not give a link then. I got the KB number out of my D/Led copy
of the then current page.)
http://support.microsoft.com/kb/q223188/
http://support.microsoft.com/support/kb/articles/Q223/1/88.ASP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;223188
Those also lead to:
http://support.microsoft.com/kb/249321/
Anyway, If you get this problem, you can NOT log-in to Windows, EVEN IN
safemode, so there is no way to fix the problem or do anything in a "normal way"
for repairs, etc. (Plus re-activation is blocked since WPA does not get far
enough
to do anything EXCEPT cause major pain and grief...) Other people report that
this happens on machines that never required WPA, and even on the Corp. builds!!!
(I have no real way of confirming that.)
I have found that once WPA is triggered, it is generally not fixable with-out
re-activating, IF you can get far enough to do that... THAT is what the KB
above is for... (I am aware of certain files that can be moved around, but even
"that" has failed me...)
I have always just restored a slightly older image that did not have the
problem...
I found this "problem" (again) recently while testing the Acronis TI 9 builds,
while
also using their Recovery Expert2003 and PartitionExpert2003 programs.
(ALL with NO hardware changes AT ALL, in this particular test.)
I will admit - I tested the limits of the programs and XP, and XP won that
round...
(I did not try anything like moving the "order" of partitions, etc. other than
the
hidden ones which "should have" not changed what the OS was trying to deal
with...)
Side note: It seems XP counts partitions even if it can't "see" them...
Anyway, that is a done deal... Not looking for any help there...
It would have taken 250 digital camera screen shots to show what I did...
(I actually counted that many on a different test recently, and Acronis asked me
for 43 (or so) specific ones to show what I was doing......) (And they say it
is fixed now.)
I was just "playing" with a (working perfect) drive that had mutiple old
partitions,
(both hidden and in use), and did not need to "repair" what I had done, etc., so
did not have to see the thing through... (But it did get me looking for a
solution...)
I brought it up because I have had this problem before (over the years), but
never
knew what was causing it until now... Being good at "working around" a problem,
even if I do not know the exact cause or cure, I have not "generated" this
problem
for several years.
Note that any time I had this problem, it was on perfectly legally licensed
drives
(or clones) that were STILL in the original machine with the rest of the
original
hardware...
(In other words, in a place where I "should" have had no trouble with WPA...)
I generally used (in the past) the System Builder (full)OEM versions with WPA.
That is a version name I picked up from MS recently.
I used to call it small-OEM version, meaning the "mom and pop" OEM version...)
I now have some FPP versions (full retail type) I am playing with.
Oh yea, to be complete, all the "new" stuff above was on XP-Pro-SP2 (install CD
was factory, not slipstreamed). Installed system was fully patched.
Hope this was helpful to someone and especially the original poster...
Rick Glazier
From: "Rick Glazier"
See the MS KB Article ID:223188 for the type of problems you might
run into... (This describes getting out of trouble, NOT how to change
a drive letter in advance...)
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.361 / Virus Database: 267.12.5/147 - Release Date: 10/24/2005
--
----------------------------------------
The WIN-HOME mailing list is powered by L-Soft's renowned
LISTSERV(R) list management software. For more information, go to:
http://www.lsoft.com/LISTSERV-powered.html
