Path:
eternal-september.org!reader02.eternal-september.org!news.eternal-september.org
!.POSTED!not-for-mail
From: "J. P. Gilliver (John)" 
Newsgroups: microsoft.public.windowsxp.general
Subject: Re: Cloning a 2.5" IDE/PATA Laptop Hard drive
Date: Tue, 7 Nov 2017 14:05:59 +0000
Organization: 255 software
Lines: 57
Message-ID: 
References: 
 
  
  
  
Mime-Version: 1.0
Content-Type: text/plain;charset=us-ascii;format=flowed
Injection-Info: reader02.eternal-september.org;
posting-host="6bde7923b02edf652bd5a635f0d27085";
 logging-data="1763"; mail-complaints-to="abuse@eternal-september.org";
posting-account="U2FsdGVkX1+PFPZj5XZ/2gSNdgil7nJQ"
User-Agent: Turnpike/6.07-M ()
Cancel-Lock: sha1:LAZ0FoBQnFngQ+WIZTl6iUIUD2M=
Xref: news.eternal-september.org microsoft.public.windowsxp.general:134457

In message , Some Guy  writes:
>J. P. Gilliver (John) wrote:
>
>> Just out of curiosity, why have you cloned so many from "a handful"?
>
>We made several hundred windows-based systems with custom hardware
[]
Thanks, interesting.
[]
>> Is that going to be either easier or better than Macrium or Acronis? 
>>(Or  does Hiren include one or both of those?)
>
>Hiren's BootCD is at version 15.3 (or maybe higher?).  Previous 
>versions have included Macrium Reflect 4.2.3775 and Acronis True Image 
>8.1.945 (or higher). I don't know if the current / latest version still 
>includes Macrium or Acronis.  Sometimes commercial stuff gets removed 
>from Hiren's so different versions will contain a different mix of 
>software.  You probably need to get older (maybe more desirable) 
>versions of Hiren's from mirror sites or torrent.

If you want to play; if you just want Macrium or Acronis, of course, you 
can get them from source. (I like my Macrium, as it fits on a mini-CD; I 
like mini-CDs, as they're easier to keep with - in this case - my backup 
drive, than a full-size CD would be, and less likely to get broken.)
>
>>> Yes, a system that hasn't tried to re-validate itself in the past 
>>>120  days should be in the clear to do it again, but I think the risk 
>>>is  too high if you can avoid it.  The risk that your product key 
>>>has, for  what-ever reason, been added to Micro$haft's black-list of keys.
>>  Does XPinfo (on machines where it works!) cover this, or only 
>>compare  the system to how it was at (last) activation? (Or original 
>>activation?)
>
>I think I knew that XPinfo didn't work with VLK, but I thought it did 
>work with OEM licenses.  I can tell you it works with system builder 
>and retail licenses, and *I think* MSDN / Technet subscriptions too.

The wording in the readme is something like "won't work with any version 
that does not require activation, such as OEM or volume licencing keys".
>
>XPinfo will tell you the current state of which components are the same 
>now vs when XP was last validated (which is usually, but not 
>necessarily when XP was originally installed).

It didn't work on this machine (came - new - with XP installed). Well, I 
say didn't work: it at first came up with an error box saying "Cannot 
collect configuration data (-204). (a) You are running a volume-licensed 
version or OEM release of Windows XP. (b) You have not activated your 
installation of XP, yet. OK". (I assume there's an implied "OR" between 
those.) When I click OK, it comes up with another window headed "Fully 
Licensed" in big letters, below which are ten text boxes for things like 
Processor model, which are indeed greyed out; it does show the first 15 
characters of the key though.
-- 
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Never be led astray onto the path of virtue.
--- Platinum Xpress/Win/WINServer v3.1