Leaderboard

Kinda actually , Biostar re released H61 chipset motherboard. link You can grab i5 3570 for $20 from eBay .So a new xp compatible computer under $150 is very much possible.

Well, fair enough, but DDR3 and such an old socket (LGA 1155) from 2013, it's hardly gonna attract anyone... I mean, who would want two DDR3 slots and an Ivy Bridge 22nm Intel CPU when the best thing you can put there is an Intel Core i7-4960X 6c/12th 15MB of cache released on September 2013... It would be useful to have modern chipsets released with Windows XP drivers, not old deprecated stuff brought back into manufacturing and offered as new when they're clearly not...

Wow, thank you so much @jaclaz! That spreadsheet must have involved a huge amount of work! OK, I will try your "proposed approach" and report back. I will try to give as much detail as I can on what the result is. Cheers, Dave.

Still waiting on 2004 to be released. The information I got was GA is April 2020, so it is supposed to be released today! But probably not.

Page 8: XP/2003 32 and 64 bit are supported, "fully updated" emphasized. Since POSReady updates took care of lot of recent vulnerabilities, this should just pick up the slack.

Sorry. Here's the correct link: https://0patch.com/user_manual.htm I corrected the link in my original post too.

404? Since the installation fails on Windows 2000 but not Windows 2000 pretending to be XP (though it doesn't run on any form of Windows 2000), I would think that these patches were made with XP in mind. Then again, so are Office 2010 updates apparently.

I agree. It also says on 0patch's pricing page you can contact them for a free trial so that's another option to check for any additional possible instability issues before you decide to move to the Pro version. I don't know if you've had a chance to peruse the 0patch user manual but I would recommend this as well. You will find everything you need to know about its intricacies in there.

An app calls CreateFile to create a device handle by prefixing the driver filename with "\\.\", then talks to it with calls to DeviceIoControl. See internals.cpp in the KernelEx source for an example.

I believe both are needed. Install UMDF (User-Mode Driver Framework) first.