1 |
I'll keep going with this, because there is a Gentoo twist at the end! LOL! |
2 |
|
3 |
On Tuesday, 7 January 2020 16:58:43 GMT Mark Knecht wrote: |
4 |
|
5 |
> After maybe 16 hours it didn't activate but logically I don't know why it |
6 |
> would have. I've installed Win 10 using the M$ install tool writing to a |
7 |
> USB flash drive but I'm not given any product IDs/Keys. M$ would have had |
8 |
> to determine on their own with no help from me this was a reinstall and |
9 |
> generously activated it which I think is asking too much. |
10 |
|
11 |
The (re)activation process does not work like you assume. Your MS Product key |
12 |
would have been provided with the original (Windows 7) installation media, a |
13 |
sticker under the laptop, your laptop's OEM box/activation card, or the |
14 |
MSWindows Online Shop. If you do not possess this key you cannot readily |
15 |
(re)activate the installation. |
16 |
|
17 |
You could call Microsoft Support to ask for your key since this is a legit |
18 |
installation, but as the key is still in the original disk, boot into the old |
19 |
disk and use some of the methods mentioned here to extract it: |
20 |
|
21 |
https://www.howtogeek.com/206329/how-to-find-your-lost-windows-or-office-product-keys/ |
22 |
|
23 |
|
24 |
> Owing that I'm not 100% sure the previous install was actually Win 10 Pro, |
25 |
> having updated from Win 7 with their free conversion to Win 10, I'm going |
26 |
> to put the old drive back in, double check what version of Win 10 I was |
27 |
> using and then try again if I installed the wrong version this time. |
28 |
|
29 |
Yes, the Product key or Digital License can only be reused on the same Windows |
30 |
10 edition as the original. If not you'll get some error pointing to the fact |
31 |
your key is not suitable for the edition of the OS you are trying to activate. |
32 |
|
33 |
|
34 |
> On a more Linux note I'll build a bootable USB drive with clonezilla and |
35 |
> see about cloning the old drive to the new SDD that way. that sort of |
36 |
> solution is why I posted here in the first place. Trying the Win 10 install |
37 |
> and hoping it worked was just an easy 1-day experiment. |
38 |
|
39 |
That could be the easiest way without having to fight your way through the |
40 |
Windows Activation Process. On the other hand, if you manage to re-activate |
41 |
it, you'll know how to go about it next time you reinstall - this is MSWindows |
42 |
after all! ;-) |
43 |
|
44 |
|
45 |
> P.S. - I'd love to get back to running Gentoo one of these days. For those |
46 |
> of us that wanted a stable machine with just a couple of testing packages, |
47 |
> especially as the machines become older and the software becomes larger, it |
48 |
> just became too many hours building code, especially on these older |
49 |
> laptops. Kubuntu has worked well enough for me be there's no better |
50 |
> community that you here at gentoo-user for straight forward technical |
51 |
> discussion and I want to thank everyone here for years and years of good |
52 |
> times and good information. |
53 |
|
54 |
Have a search for 'chroot' and 'cross-compiling' on Gentoo wiki & forums. |
55 |
There should be a few articles explaining how to cross-compile binary packages |
56 |
within a chrooted directory on a faster/bigger/better PC and then rsync and |
57 |
emerge these packages with '--usepkg y', or '--usepkgonly y' on the slower |
58 |
laptop. As far as the laptop is concerned, this last part ought to be almost |
59 |
as fast as updating/installing binary packages on Kubuntu. This is probably |
60 |
the only way to install really large compiled applications like Chromium, |
61 |
LibreOffice, etc. on old PCs with very low RAM. |
62 |
|
63 |
-- |
64 |
Regards, |
65 |
Mick |