Damnation

@Dietmar I'm not sure what you mean? - I see NmrWaitForProviderDeregisterComplete function is in both vista and 7 netio.sys

@Dietmar I noticed that RmpStartModule makes use of MmAllocatePagesForMdlEx I made use of code from the windows research kernel for my implementation of it, can you debug that function in my ntoskrn8.sys?

@Dietmar I got the Vista RTM versions with PDB Symbols for you. https://ufile.io/j8gnil57 already redirected to ntoskrn8.sys

@Dietmar do the Vista RTM versions of ndis/netio/msrpc work with my ntoskrn8.sys?

@Dietmar I would ideally like to target windows7 ndis.sys since the LAN chip of my new B550 motherboard - Realtek RTL8125 - is Windows7 and later only, no vista support. regarding missing ndis.sys dependency - does vista RTM ndis.sys have it?

@Dietmar any idea for which part of ntoskrn8.sys I need to change?

@Dietmar I Implemented some more of the missing functions in assembly and included PDB symbols of everything for you. https://ufile.io/qnm6t9wa can you debug when you get the chance?

@Dietmar win7 ndis.sys depends also on netio.sys and msrpc.sys ntoskrn8.sys depends only on ntoskrnl.exe and hal.dll

@Dietmar @George King Back after trying a new thing. Can you guys try running win7 ndis.sys and debugging this new version? https://ufile.io/ktn5wbbo

@Dave-H make sure you have windbg open on your debugger and waiting for the debugee to connect. then on the debugee select the debug option from your XP boot menu. then switch back to the debugger and wait for it to connect.

@Dave-H The guide I gave you assumes XP is the only OS on the drive. Ideally, to get this debugging setup going, it would be best to make a backup image of your entire HDD (boot sector and all) and then wipe it, leaving XP as the only OS so you can use the boot.ini

@Dave-H It can be the windows 10 version of windbg if you prefer to use that. it just needs to support KDNET.

@Dave-H The HOST (debugger) does not need to be running XP like the TARGET (debugee) PC. It can be running newer OS's like Windows 10, and all windbg needs is a connection to the TARGET PC. Which in this case would be the TARGET PC's IP Address, a port, and encryption key.

@Dave-H Here are those kdnet you need. https://ufile.io/mr0jjupa

@Dave-H Here are some instructions @Mov AX, 0xDEAD sent me. type these commands in windbg for debugging - post full debug log.

@Dave-H You'd have to have windbg running on another machine as you click restart if you want to find what the cause of the problem is.

@windows2 there isn't enough in the leaked 2000 source code to make a complete build of the OS as it is, only some of the components were leaked.

There's a Windows 8.1 build USB 3 driver for XP? I thought there was only a windows 8.0 version?

no, it will not run x86 apps, it's an entirely different architecture from x86. Itanium IA64 was bad at what it was designed to do, it was slow even back then.

@Dietmar Ah, I forgot it doesn't work under XP. I used it on windows 10 to edit my windows 8.0 ISO.

@Dietmar not nlite - that's for XP - NTLite - that's for windows 7 and later, Vista is SOL. I don't remember exactly which one I used, I think it was acpi4.sys, not sure.

@Dietmar I recommend NTLite for editing Win 8.0 ISOs https://www.ntlite.com/download/

I don't think @Mov AX, 0xDEAD has any motivation to fix any USB 3.0 related issues on XP. Unless I'm mistaken?

I use the last free version of Comodo Internet Security that supported XP, it seems Comodo scrubbed the download links, if I can find the installer I'll post it here.

@George King Thanks!