Replies

SupremeLaW wrote:

p.s.  And, for readers here who may have missed this point, we tried a fresh install of Windows 10 Pro x64, from an OEM disc, but the install aborted with the error message:

this CPU does not support “PrefetchW”

So, Windows 7 Ultimate did install AOK from another OEM disc that we purchased from Newegg several years ago.

The latter OS software is “genuine”;  it just needed a separate activation code, which we purchased from an eBay re-seller.

Many thanks to everyone who has helped with this topic.

Yep, this was introduced in Windows 8.1 as a minimum CPU requirement. It only applies to th x64 editions.

1 user thanked author for this post.

SupremeLaW

EP wrote:

steeviebops wrote:

XP was the only system that could trigger reactivation for a RAM swap. Back then, 10 categories were checked; things like CPU, RAM, MAC address, volume serial number, etc.; and 7 of the 10 had to pass or it required reactivation. Nowadays (since Vista I’d say), it’s pretty much just the motherboard.

The chance of a RAM swap triggering reactivation on XP are somewhat small steeviebops (assuming it was a “retail” non-OEM version of XP). I never encountered something like this on OEM WinXP Home for just a RAM chip swap.

Pre-installed OEM (SLP 1.0) versions were different altogether. They were tied to a text string in the DMI information of the BIOS. In that case, only a motherboard swap with one of a completely different vendor would trigger reactivation. So it was similar behaviour to later versions.

I only ever used non-SLP versions which used the “7 of 10 checks” as I mentioned above. In this case, a RAM swap alone wouldn’t trigger reactivation, but if three other changes were made beforehand then it could.

2 users thanked author for this post.

Microfix, SupremeLaW

XP was the only system that could trigger reactivation for a RAM swap. Back then, 10 categories were checked; things like CPU, RAM, MAC address, volume serial number, etc.; and 7 of the 10 had to pass or it required reactivation. Nowadays (since Vista I’d say), it’s pretty much just the motherboard.

1 user thanked author for this post.

SupremeLaW

I still have a 60GB OCZ Vertex 2 from 2007 that works just fine. I don’t have it in anything as a daily driver though. I’ve been using SSDs ever since that and only one has given me trouble. That was a 1TB WD Blue SSD. It didn’t stop working, it just got really slow at reading resting data. Anything newly written was fine but older files were excruciating. I replaced it with a Samsung 970 Pro and restored from my backups.

1 user thanked author for this post.

Microfix

Try running “C:\WINDOWS\syswow64\odbcad32.exe” – that should give you the 32-bit version if it exists.

Two things you can try:

Open command prompt as admin and enter these two, replacing the X with your actual product key.

slmgr -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
slmgr -ato

If that doesn’t work, run ‘slui.exe 4’ instead and that should give you the phone option.

That’s the generic USB 3.0 driver that comes with Windows, it was updated in a recent Windows update. I can see it here too. 13/01/2023, version 10.0.19041.2546.

It doesn’t seem to work for XWayland so that still needs a script hack by the way.

DrBonzo wrote:

“The whole middle click paste thing and inability to disable it globally is a deal breaker for me unfortunately.”

Maybe I don’t understand what you’re saying but I just copied and pasted the above quote without any middle clicking. Right click for context menu, click copy, then left click to position cursor, then right click, click on paste. Done.

Linux Mint 20.3 Cinnamon

KDE Neon now has the ability to disable this. Edit ~/.config/kwinrc and add the following:

[Wayland]
EnablePrimarySelection=false

This changes everything for me, I might have a contender on my hands here.

I just tested it, it works! At least in the current release of KDE Neon. Doesn’t seem to be in Kubuntu yet.

Edit ~/.config/kwinrc and add the following to the [Wayland] section (create it if it doesn’t exist):

EnablePrimarySelection=false
Log off and back on again and it’s all good! This changes everything for me. 🙂

Edit: It can also be done in System Settings > Workspace Behaviour, uncheck “Paste selected text”.

Looks like KDE might have given me what I wanted. Must try this again sometime.

https://bugs.kde.org/show_bug.cgi?id=441668

https://invent.kde.org/plasma/kwin/-/commit/4082fdf96092005106b5895e238e94a614035b0b

Can you run these two commands and post the output please?

cd “C:\Program Files\Microsoft Office\Office16”

cscript OSPP.VBS /dstatus

If you’re running 32-bit Office you might need to replace C:\Program Files with C:\Program Files (x86)

I remember having some in stock years ago in the shop I worked in. They were no-name cards but had NEC/Renesas chips on them.

1 user thanked author for this post.

SupremeLaW

I’m probably just being old by saying this, but “why?” I don’t get all this AI stuff!

I watched this video last week. However a big question I have is, was the Windows 11 install a bloatware OEM build or a stock Microsoft one? Can’t see why MS would be contacting McAfee servers.

1 user thanked author for this post.

b