Re: reactivation when nothing changed
- From: RealGomer <RealGomer@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 24 Dec 2005 20:24:02 -0800
You know, Vanguard, it's [----] like you who give support / community forms a
bad name.
First off, IF Microsoft's hardware database for each PC were coded
correctly, it would realize that every piece of hardware had been reseated
into the exact same position as before. That's called fall over. Secondly,
with the way Microsoft has its reactivation currently coded, you can need to
reactivate after just swpping CD-Drives, which by the way, has happened to
me. Not put a new one in. I mean just switching their positions on the cable.
Thirdly, if Microsoft were in the least bit interested in its customers and
users, it would simply compare the license and user info to a database first,
then see if the mobo were the same. Most of the people I know have changed
CPUs, hard drives, optical drives, memory and goodness knows what else
several times on the SAME box.
Anyway, I installed XP into my own PC after I had to replace a fried hard
drive. That happens occasionally with lightning strikes, car wrecks, and
winter static. Microsoft's paranoia over reactivation is second only to those
in Washington.
--
I know enuff to be dangerous.
"Vanguard" wrote:
> "RealGomer" <RealGomer@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:580F8AF7-8C1B-4001-BE63-658DCA4059A2@xxxxxxxxxxxxxxxx
> > My PC froze and then wouldn't reboot. So, following SOP, I removed
> > everything
> > except for one bank of RAM. Rebooted. POST. Turned off. Added another bank
> > of RAM. Rebooted. POST. Turned off. Added third bank of RAM. Rebooted,
> > POST.
> > Turned off. I kept doing that until all the hardware was reinstalled into
> > the
> > EXACT SAME SLOTS, PORTS, AND CONNECTERS. Nothing changed!
>
>
> Oh, c'mon, even you realize that you changed the hardware as many times as
> you changed it. Every change was a change. You removed lots at once.
> Change #1: You added a stick of memory. Change #2: You added another stick
> of memory. Changes 3 to N: You keep adding more stuff (presumably one at a
> time) so, for N more changes in hardware, you made N more changes (yeah,
> that statement is circular because a change is a change). So eventually you
> hit a threshold, like 10 changes, which triggered the activation event.
>
> Nothing changed? Hah! LOTS changed. Doesn't matter that you put back in
> what was there before. You made changes. You changed your system from
> loaded to barebones. Then you made subsequent changes, one at a time, as
> you added "new" hardware to that barebones system (what, you think Windows
> will somehow magically know the memory stick you had before is the same one
> you added later?).
>
> > I got the reactivation BS. When I run the reactivation BScript, I'm told
> > the
> > product number is incorrect. Funny. I only have the one copy of XP Pro so
> > how
> > the blazes could the number be wrong!!!!!!
>
> Did YOU do the install of Windows? Or did it come as some pre-built that
> you relied on someone else to fab? If someone else, could be they didn't
> use SysPrep properly, or simply copied an image onto the drive, resulting in
> the same license getting proliferated on every host they prebuild. Even if
> they gave you an install CD (and a product key for it), could be you are
> supposed to use the product key on the sticker that they were supposed to
> affix to your computer (but if they prepped the computer wrong then maybe
> even that product key won't work). You'll have to call whomever built the
> computer to get help from them since the version of Windows that came with
> that computer is an OEM version and Microsoft has no responsibility to
> support that version (you got it cheap because it did NOT include support
> from Microsoft; it is an OEM version so you have to go back to the OEM for
> help).
>
> If the product activation fails, as you indicate, it should give you a
> telephone number to call. So explain why you didn't bother to call.
>
> > Suggestion will be appreciated, except the certain MVP whose name is the
> > same as a restaurant and thinks Microsoft's activation program is just
> > dandy.
>
> Yeah, that statement was clear as mud. Since a restaurant can be whatever
> name the proprietor wants, and could be their name, their daughter's name
> (like Wendy's), someone else's name, or not even a person's name (you think
> there is someone walking around named Napa Auto Parts that started that auto
> parts chain?), your statement is just whiny fluff.
>
> > --
> > I know enuff to be dangerous.
>
> For sure.
>
> --
> __________________________________________________
> Post replies to the newsgroup - Share with others.
> E-mail: Remove "NIX" and append "#VC811" to Subject.
> __________________________________________________
>
>
.
- Follow-Ups:
- Re: reactivation when nothing changed
- From: Vanguard
- Re: reactivation when nothing changed
- References:
- Re: reactivation when nothing changed
- From: Vanguard
- Re: reactivation when nothing changed
- Prev by Date: Re: Device Manager
- Next by Date: Re: How to do simple PING batch file?
- Previous by thread: Re: reactivation when nothing changed
- Next by thread: Re: reactivation when nothing changed
- Index(es):
Relevant Pages
|
