Microsoft Activation Stupidity

  • Thread starter Thread starter Mr. Frazzlebottom
  • Start date Start date
Tough luck. One should be educated by now about standard terms and
conditions like it is in railways and other public transportation
system.

Ignorance is not an excuse!!
 
Since you say that "Not that I could not fix it, I can, and will, that
was not the point" indicates that you are a computer savvy person who
has used and probably installed many OSs in your entire life. Assuming
this is so, you must have accepted EULA sometimes on most legal software
packages. These all contain standard text book terms and conditions.
So what exactly are you compalining about?

I hope you have fixed your system by now as it takes about 1 hour to
make an average system running again.

Good luck in your pursuit of complaining and moaning about nothing!
 
ANONYMOUS said:
Tough luck. One should be educated by now about standard terms and
conditions like it is in railways and other public transportation
system.

Ignorance is not an excuse!!

Not being able to activate an OEM copy of XP on the Internet was NOT a
"standard term and condition" when the OP bought his copy. It's something
that MS has introduced recently. So why WOULD the OP know about it? Stop
trying to be an MS apologist.
 
ANONYMOUS wrote:
....
So what exactly are you compalining about?

That, after a new motherboard -- which caused XP to "find new hardware",
sucessfully -- XP informed me that, since there was a significant
hardware change, I had to re-activate and that I had three days to in
which to do so. Since a reboot was required for the new found hardware,
I rebooted.

After rebooting windows says that I can not login because it needed to
be activated.

My complaint -- filled with "flailing resentment" as someone said -- was
that I could not re-activate unless I could login. Hence, XP was broken.
I hope you have fixed your system by now as it takes about 1 hour to
make an average system running again.

Two hours on average I have found lately. No big deal.
Good luck in your pursuit of complaining and moaning about nothing!

Thanks!
 
Alias wrote:
....
No mention of a motherboard in the EULA.


Download any drivers that you need that XP doesn't have.


No reason for that.

Where's number 3?

Typo.

I think I my have been thinking of 4 as "All of the above."


Swapping out a motherboard should be a simple process. Windows does
re-install new drivers very well -- it is called "Plug & Play." BIOSs
and OSs are all pretty good at it, in my experience.

Maybe, perhaps, that, for my case at least, it was a fluke that XP
locked me out of when I moved it to a new system.

At least a few said that move XP to a new system is some sort of moral
injustice that deprive Microsoft of something and is a violation of the
EULA.

At least a few have implied that in order to upgrade to a new
motherboard one has to purchase an other copy of Windows.

At least a few had said that moving XP to a new system is of course not
going to work and that the required step was a "Repair Install," as if
that was the only way to do it.

At least a few have said that moving XP to a new system is not that same
as replacing the motherboard -- not exactly, but it can be if I had also
moved over the Video Card, all Drives, etc.

Possibly effected by my polemical way of posting my "complaint," at
least a few proceeded to attempt to insult me -- I of course, being a
passive aggressive type, responded in kind.

The amount of misinformation posted here as gospel or the one and only
truth simply amazes me. Not to say that some people just make mistakes
-- I do and did, of course, when I mentioned the scenario of Dell
replacing a motherboard and not having to re-activate is probably just
that Dell has an OEM version of XP or something. Maybe there are others,
I don't know.

Hey, I can be dumb sometimes. And arrogant. But I wonder how many are
still laughing out loud. (Ask me if I care.)

(This is a long winded post and people might want to just move on at
this point.)

Too many people have implied that XP is some sort of perfect OS, without
flaws, without problems, and that if anything goes wrong it must be the
Users fault. What can one say to that? Other than, *that crap pisses me
off.*

XP's re-activation code is flawed if it kicks in unnecessarily. Although
if one simply has to click the mouse a few times to do so then it is not
so bad -- just annoying. But if it fails and one has to "Repair Install"
then it is by definition a design flaw if not just a bug. And only
allowing three days in which to do so is a pretty rotten thing to do.

Yeah, yeah, there's piracy 'n all. Yeah, well, this "drone" ain't gonna
cry if Microsoft did not make an extra $99.00 this month because the kid
next door managed to get ahold of a bootleg copy of XP. I certainly
would not bombard him with insults even if this is Usenet. I have more
respect for a kid with perhaps not much money who is trying to get an
old system to work any way he can than any amount of non-arrogant MS MVPs.

And speaking of MS MVPs, I think that the few here who simply lurk all
day long and respond to newbie questions simply with "copy & pastes"
from Microsoft KBs are doing everyone, and mostly themselves, a disservice.

Cheers.
Mr. Frazzlebottom, The Polemic.
 
Gordon said:
Not being able to activate an OEM copy of XP on the Internet was NOT a
"standard term and condition" when the OP bought his copy. It's something
that MS has introduced recently. So why WOULD the OP know about it? Stop
trying to be an MS apologist.

Most of the "issues" with regard to this activate problem is that there
is no clear explanation from Microsoft -- or from Microsoft/XP
defenders -- aggavated by the fact that Microsoft just does a bad job
at documentation AND, sometimes, programming.

Granted, I "messed up" in starting this thread by not being
"diplomatic"... But if I had asked nicely about how does one fix the
re-activation "bug/design flaw" whereby XP appears to lock a user from
activating, would anyone had said this:

(The main bug is that XP was supposed to provide my with 3 days; it did
not and said that the system was unusable the next reboot.)

For a non-activated XP beyond it's activation grace period, XP will not
allow users to logon. And if you had the autologon feature enabled, XP
will be stuck in a loop, trying to log you in, being unable to do so
and respond with a message, you click OK and XP then re-tries to log
you in. A loop that apparently can not be terminated.

If you log into Windows in Safe Mode the same loop is the result.

If you log into Windows in Safe Mode Command Prompt you will be logged
in as the user with the autologin account. You can then -- if you have
administrator access - use REGEDIT to disable the autologon feature. If
you do not have administrator access you can "RUNAS /user: adminstrator
regedit" to REGEDIT.

But if you do not know the Administrator password you have to try
harder...

Also, if you had Remote Registry Service running one can try REGEDIT
from another machine.

Also, MSOOBE /a can not be run in Safe Mode.

Then there is always "Repair Install".

I wish that some MS MVP will write a FAQ about all this
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

The thing is is that Microsoft does a poor ass job of it.
 
Back
Top