JorgitoXP Posted June 24, 2022 Share Posted June 24, 2022 Hi. I am trying to modifying syssetup.inf and layout.inf. but i didnt got any modified version of syssetup or setupapi so i cant modify that. Does someone has got these files patched and send a link? I need to change Syssetup.inf but WITHOUT those annoying 'New hardware wizard' messages. I need to let it install automatically. Like original Windows XP. If you have any patched version of this files you can post here. please. Thanks! Link to comment Share on other sites More sharing options...
George King Posted June 24, 2022 Share Posted June 24, 2022 (edited) Here you can find what you are looking for https://www.wincert.net/forum/topic/17689-xpw2k3-x64-on-modern-hardware/?do=findComment&comment=138860 https://www.wincert.net/forum/topic/17689-xpw2k3-x64-on-modern-hardware/ Edited June 24, 2022 by George King 1 Link to comment Share on other sites More sharing options...
JorgitoXP Posted June 26, 2022 Author Share Posted June 26, 2022 OMG THANKS!!!!!!!! I was searching this since April 2021. You save me! 1 Link to comment Share on other sites More sharing options...
LoneCrusader Posted February 11 Share Posted February 11 On 6/24/2022 at 7:39 AM, George King said: Here you can find what you are looking for https://www.wincert.net/forum/topic/17689-xpw2k3-x64-on-modern-hardware/?do=findComment&comment=138860 https://www.wincert.net/forum/topic/17689-xpw2k3-x64-on-modern-hardware/ Patch is there for SYSSETUP.DLL but not for SETUPAPI.DLL. I've not been able to locate a patch for the x64 version of this file, and the byte sequence for the x86 version doesn't match even though they're the same build number. Anyone have information on this? Thanks! Link to comment Share on other sites More sharing options...
pappyN4 Posted March 28 Share Posted March 28 @LoneCrusaderI dont know what you need it for... But looks like all the patch does is skip the checks in pSetupVerifyFile found in setupapi.dll. Fortunately XP64 has the same logic as XP for that part so same patch should also work. x86 setupapi.dll 5.1.2600.5603 @53789 8B FF 55 8B EC -> 33 C0 C2 30 00 x64 setupapi.dll 5.2.3790.4511 @94240 48 81 EC 98 00 -> 33 C0 C2 30 00 1 Link to comment Share on other sites More sharing options...
LoneCrusader Posted March 30 Share Posted March 30 On 3/28/2024 at 11:11 AM, pappyN4 said: @LoneCrusaderI dont know what you need it for... But looks like all the patch does is skip the checks in pSetupVerifyFile found in setupapi.dll. Fortunately XP64 has the same logic as XP for that part so same patch should also work. Thanks for the info. For completeness could you also list the correct location for patching x64 version 5.2.3790.3959? I note that the same byte sequence occurs several times throughout the file.. how does one know which instance specifically requires patching? The SETUPAPI patch allows one to modify certain files on the installation source prior to SETUP.. some can be edited without problems (i.e. TXTSETUP.SIF, DOSNET.INF that are used by nLite) but others such as LAYOUT.INF cannot be modified without causing errors during SETUP. FDV's patch for this works on XP x86 but I had no way to port it to XP x64. 1 Link to comment Share on other sites More sharing options...
pappyN4 Posted March 30 Share Posted March 30 6 hours ago, LoneCrusader said: I note that the same byte sequence occurs several times throughout the file.. how does one know which instance specifically requires patching? The example you posted for x86 5512 had some extra bytes shown as well. So if you do a search with that, then its usually unique enough to only have one. That way, to update it for a newer file, you can usually get away with using the same search even if the byte sequence is in a different position. To get the x64, I looked up the x86 in IDA at the byte position to see what was actually being changed, in this case pSetupVerifyFile. So with the x64 file having the exact same logic it was simple to make the same change. Unlike syssetup.dll where the difference between XP (5.1) and XP64 (5.2) was large. In this case it looks like x64 3959 change is in the same position. byte search 505DC3909090909090904881EC9800 I'll also mention the post SP2 updates that are available for XP64 if you want to use the latest version. https://www.mediafire.com/folder/x6qqeye5y0a0x/x64 Link to comment Share on other sites More sharing options...
MilkChan Posted March 30 Share Posted March 30 (edited) 7 hours ago, pappyN4 said: I note that the same byte sequence occurs several times throughout the file.. how does one know which instance specifically requires patching? The example you posted for x86 5512 had some extra bytes shown as well. So if you do a search with that, then its usually unique enough to only have one. That way, to update it for a newer file, you can usually get away with using the same search even if the byte sequence is in a different position. To get the x64, I looked up the x86 in IDA at the byte position to see what was actually being changed, in this case pSetupVerifyFile. So with the x64 file having the exact same logic it was simple to make the same change. Unlike syssetup.dll where the difference between XP (5.1) and XP64 (5.2) was large. In this case it looks like x64 3959 change is in the same position. byte search 505DC3909090909090904881EC9800 I'll also mention the post SP2 updates that are available for XP64 if you want to use the latest version. https://www.mediafire.com/folder/x6qqeye5y0a0x/x64 It's better to use my latest version. That was the old version that had the problem and I deleted the file. There is all the Source Files Update Packs that I uploaded. https://archive.org/details/5eraphupdatepacks Edited March 30 by MilkChan Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now