dencorso

Install physically disconnected from the internet, then change the name of the updates folder, then connect to the net. It won't be able to update anymore, but should otherwise work OK.

CC is a space filler in PE files, if I'm not mistaken, and so it means no specific opcode in that context.

Here below the Tropic of Capricorn is scorching hot today. As most of Brazil is above it, it should be even worse. A computer room kept at 18°C is an incredible luxury, 'round here. Outside it's 31°C with 75% humidity, right now. And, yes, we use detectado, but both are intelligible (and both are paroxytones).

A bona-fide used Windows 7 Ultimate FPP in the original box with license number card, leafets and both x86 and x64 hologram DVDs sells 'round here for about US$100... it may reach US$150 for versions without geographic Activation Restrictions (to South America and the Caribbean). Brand-new, unopened, still in the intact shrink-wrap are much more expensive, but very rare to be found. And the media usually are pre-SP1, but that's no problem, of course, the license being good.

+1. BTW, the Great Zero Challenge has finished without anyone even claiming to be able to actually recovering any single-pass zeroed-out data, some seven years ago.

And you've managed to get jaclaz and me interested, at least for a while, not on the kernel extension, but on the nickname/gender linguistic question

Try Amazon.com... they're more reliable than eBay for that. YMMV, though.

Well Samuka might conceivably be a nickname for a girl named Samant(h)a, Samara or Samira, in PTB, not considering an almost infinite universe of invented names, which are also quite possible 'round here.

how do you mean "still" ? Ain't that your 1st post ?

Samuka is almost always a male name in PTB. It means "Sammy" or "Little Samuel". BTW, "Andrea" is a male name in Italian, but a female name in Portuguese: its male version would be "André", which is also pretty common 'round here. But nicknames allow for some more uncertainty, but I'd always guess, if required, it's a male nickname. That said, I'm not at all impressed with the little I know about Samuka's work. Then again, I disagree with y'all on the subject: while I think Xompie is great and an unofficial USB 3.0 driver for intel chipsets is sorely needed, I truly don't think there's really any need to expand XP's kernel32.dll at all.

there's no MS usbxhci.sys as part of XP SP3, nor is it a later addon. There are just usbuhci.sys; usbohci.sys and usbehci.sys, provided by MS.

It sure would. But there's no generic MS USB3 driver, and modding kernel32.dll is not useful, in this case... what ought to be modded for WDM drivers would be the ntdll.dll (or even the appropriate one of the ntoskrnl files), if I'm not mistaken...

May Pale Moon rest in peace. Let Moonchild get what he wants: to be forgotten.

I see. But... was the 10 SSD physically connected when you installed XP to the other SSD?

Yes! And welcome to this thread, jaclaz! Let's say I meant to say: "8.1 to 10 do not install by default in BIOS mode, when UEFI is available, while XP cannot boot in UEFI mode." In fact I don't think I meant to say that, but that's what I should have meant to say, whatever I actually meant to say at that time.

Well, not exactly... it does get smellier with time passing, doesn't it?

Good! Now we're going somewhere! So: 8.1 to 10 cannot boot from MBR, while XP cannot usually use UEFI. IIRR, that is an officially insoluble problem (by design), which begs the question: How have you set your multibooting rig? Describe in detail the chainload sequence and partition layout.

All our crystall balls are out tuning, and the shop they're in is closed for the holidays till next year. So a good anamnesis is in order. For starters, which processor is your machine running on? It was working fine since when? It cannot be much long, since the Z97 was released on March 2014, and the GA-Z97X-UD5H-BK must be from somewhat later... Then again why did you reinstall? If it was working fine, you had no need to reinstall. So... what happened? I mean, what happened in the days just preceding the 1st disappearance of the mouse and KBD How have you set your multibooting rig? Describe in detail the chainload sequence and partition layout. And for how long does the machine have 10? Which 10? Did it have 7 oe 8.x before? Whence Remote Desktop?

With all due respect: My kludge is just both regs you posted combined. Machines are consistent: the same actions always result in the same results... this is not quantum computing. Moreover, 2 *fully* independent actions can be performed in any order and must lead to the same final result. Always. When the order matters, the actions are not *fully* independent. Therefore, in RL, when 2 fully independent actions lead to different results it must be due to pebcak. Revise what you're doing carefully!!! If your performing the same actions don't lead to the same results *always*, no troubleshooting can ever succeed.

You said: so I said: and now you say: so I say: it makes no sense! It either worked before and again or didn't both times. It cannot have worked once then not worked once. No way! BTW, it strangely reminds me of a Chewbacca Defense.

OK. Fixed!

It's... complicated. Officially: not. But I see in your case maybe an opportunity for ust to pursue developing one. I'll tell you later.

Is it... safe?

Here it is: Extract uglykludge.reg into C:\Windows. Create a new shortcut named kbdmseback.lnk on the desktop, give it as target: C:\WINDOWS\REGEDIT.EXE /S C:\WINDOWS\uglykludge.reg and set it to run minimized. Move kbdmseback.lnk to the startup folder. Reboot. Do the mouse and kbd get reinstalled automatically after reboot? uglykludge.7z

No. If you're using the official intel driver, both EHCI and XHCI handoff should be kept activated. I'll post a possible workaround for your problem in a few minutes.