dencorso

Well, from what little I have been able to ascertain, up to now, JodyT has a Xeon that is an Irwindale (according to CPU-Z). Irwindales are Prescott-derived Xeons form early 2005... It's not at all clear whether all Prescotts lack CMPXCHG16b. The E0 revision adds eXecute Disable (XD) (Intel's name for the NX bit) to Intel 64. LAHF/SAHF and PrefetchW may also be a problem, see this thread (at intel)... I'll keep you all posted, in case I find any more specific info. Now, I've found a way to determine which of these instructions behind the incompatibility with 8.1: Sysinternals Coreinfo 3.31 checks them all at once. So, in case you find just a little more time to give to this issue, Jody, we'll know for sure. Please download Coreinfo 3.31 (from MS) extract it to any folder, and run it from a cmd box, like this: coreinfo > xeoninfo.txt Then colect the txt, zip and attach it, please. Sorry for the bother, but I really did not find any clear specific info anywhere for Irwindales (nor to any late Prescotts, either).

A few, however, do (work with 9x/ME, I mean), usbccgp.sys being a good example of such rare XP files.

That is the main reason I've asked for the CPU-Z cpu identification Jody kindly provided. I do intend to delve into that question as soo as I can, perhaps even this weekend, or maybe a little later. I´m really curious about it. And I think the link Jody provided to eightforums may also provide another good start-point to investigate it. I´m quite confident you'll be as safe as 7sp1 or 8.1 with updates stopped, but NoelC's specific advice sure is warranted and much welcome here, of course!

That's my opinion, too: up to 8.1, one can defend one's own install/machine from morphing into 10. But, once one decides to use 10 instead, all one's bases are belong to MS.

It's working OK, right now!

I've redownloaded it from the link in the quote above right now, and the downloaded file is identical to the one I already had in my records. Please do try again, and make sure to use http, not https... sometimes the browser changes it without telling you, so you have to change it back explicitly, and only then it'll accept http.

You're welcome! It's a pleasure to be able to help a fellow MouseWorks fan!

If you have time and opportunity, please run the latest CPU-Z on it, so that, on knowing for sure what CPU is inside, we may pursue the reason why 8.1 doesn't like it, even if just to satisfy our collective curiosity.

Yes. Your system is totally up to date (for the time being, of course).

No. Keep automatic updates service on but turn it off on the control panel. Then download the very latest update agent here. Then install it from a cmd box with the /wuforce switch. Then start a manual custom update, and be sure to hide all telemetry and "Win 10 upgrade" patches before downloading and installing.

jaclaz is right! (of course!) In particular, usbccgp.sys up to and including v. 5.1.2600.6437 (the latest) does work, provided some Win Me files are also present, and suffices for having some composite devices working. Try simply adding it to 2k, and see whether it makes any difference.

No AVG Zen on paid AVG 2011 yet. I'll keep eyes wide open and let you all know whenever that changes.

What about the lovely ProcessHacker?

You might try starting autoruns from a TrustedInstaller cmd box. Is there any difference? Also don't forget to go to the Options menu and unhide everithing, even empty locations, just in case...

Yes. heinoganda's Cert_Updater.exe is a download once run many times program. And yes, you've got that right, when you run it, it retrives the latest certificates and revoke lists directly from MS, then installs them for you. So you need to be connected to the internet, when you run it, or it'll fail (and tell you so).

Have you got the latest Russinovitch autoruns?

Later. 2020 or even later still. No hurry at all. So, let's be happy! Long live XP! And, yes: delenda Cortana!!!

IMO, it probably is hardcoded into shell32.dll or maybe kernel32.dll...

Blackmore's Night - Child In Time

It's possible last month's missing .NET Framework 2.0 update will turn out to be in this month's collected updates .ISO (KB913086), just as it has happened in the recent past. And maybe this month's missing .NET Framework updates, in next month's collected updates .ISO, and so on. ... one can dream, can't one?

... and I bet it'll be the 1st post of a brand-new member. BTW, animated avatars are a no-no... are you sure you read the rules?

Happy birthday, Kel!

I continue to use the true Microsoft Intellimouse Optical v 1.1! I have 8 of 'em, 6 of which have had the left buttom microswitch replaced twice already. I use MouseWorks v. 6.11 with 98SE and v. 6.22 with XP SP3. Works beautfully! One can still find brand-new units of this mouse on eBay, albeit usually the black and silver ones.

The message is telling you the truth: the connection is really non-secured (nor does it need to be secure). The problem is you are using "https" instead of "http" !!! If you see that message again, on trying the links below, is because your browser is adding the final "s" on the "http" address. Highlight just that "s", delete it and hit enter, and the file ought to download OK. NDP20SP2-KB3074546-x86_B00E38544466254F6C7314127D2F658078C9D53A.exe NDP30SP2-KB3072308-x86_DF948B25BC71432E5CADE81A55E0840A833B8BDC.exe

THREED.VXD??? You mean THREED.VBX, of course!