Re: Microsoft Activation Stupidity
Tech-Archive recommends: Fix windows errors by optimizing your registry
No it's not broken. Windows Product Activation works off a hardware
hash. Made of up of seven unique identifiers, such as NIC MAC address,
Memory count...When XP boots, it compares the hash code with that
of the current platform. If the number of changes (Votes) exceeds the limit
then it triggers a re-activation. I can't remember in all this floundering
around if you took a working XP instance drive and put it in a new(er) PC.
If that's the case then it would immediately detect a new Hash value and
request activation. Then if you let the timer expire XP enters a lock down
mode, where you cannot use the PC until it's activated. Essentially if you
let the "Grace Period" expire then the heading of your posting is placing
blame incorrectly.
"Mr. Frazzlebottom" <Mr.Frazzlebottom@xxxxxxxxx> wrote in message
news:1138824679.516388.118570@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> chrispsg wrote:
>> ok here is the quote from the retail EULA
>>
>> "you must acquire and dedicate an additional license for each separate
>> Workstation Computer on or from which the Software is installed, used,
>> accessed, displayed or run."
>
> So, replying "It's your fault. You violated the EULA." is not an
> arrogant thing to say?
>
> The key thing you are missing that this is not an "each seperate"
> computer issue. This is running the product only on one single computer
> at a time. This is standard software licensing allowable under any law.
>
> Think of it this way. One can un-install on one computer and then
> install on another. Perfectly reasonable and always allowable (by
> commercial of the shelf software).
>
> What the "acquire and dedicate an additional license" means is that I
> have to re-activate Windows. Just as Windows itself warned me.
>
> The thing is, and which started all this and which no one gets (due to
> my own self admitted arrogance) is that the process of re-activating
> upon moving a HDD from one computer to another is BROKEN.
>
.
Relevant Pages
- Re: Sysprep and Activation
... How to Use Sysprep with Windows Product Activation or Volume License Media ...
(microsoft.public.windowsxp.setup_deployment) - error code: 0x800703e7
... Windows Product Activation ... A problem is preventing windows from accurately checking ... the license on this computer. ...
(microsoft.public.windowsxp.hardware) - RE: A question about passwords and login/authentication
... > Hash: SHA1 ... > I have heard that many *nix flavors used to default to using DES as ... > What I'm wondering is how long can a Linux password be? ... (console, xterm, windows SSH client, etc) ...
(Focus-Linux) - SV: Brute-forcing cached Windows login password hashes
... doing a dictionary/hybrid attack will probably give ... I've done quite a bit of password audits on Windows ... The hash algorithm is a salted MD4. ... My question is regarding the encrypted password hashes that Windows ...
(Pen-Test) - RE: Windows NTFS Authentication Caching
... Subject: Windows NTFS Authentication Caching ... I believe Carol means that they have an NT Box running IIS as their ... This hash is stored on the server. ...
(Security-Basics) |
|
