I have already implemented patch for intelppm.sys for v1.6 (still unreleased as I'm not finished with all my changes), of course must be applied with PAE patch as it add FIX into HALs. or patch it manually Code: from CC CC CC CC CC C7 05 44 to CC CC CC CC CC C3 05 44 No, you already have the latest one with A5 AMILoadDDB patch .. Maybe @diderius6 can manage to solve it
I was talking about x64. Since you mention PAE, you must be talking about x86. Sorry. I'll stop talking about x64 here to avoid confusion.
@asdf23451 Both XP x86 and x64 have an issue where programs will misbehave on Intel platforms without timer patching. You can confirm if you have the problem when you get negative ratio with WinTimerTester 1.1 I don't have an Intel system to show it happening but @diderius6 does.
Hello! This project looks amazing but when I try it, after it copies the driverpacks to the harddrive... and then reboots the system i end up at a GRUB Rescue> prompt instead of getting the installation menu.... what gives? Any and all help is appreciated also I don't know if I messed up using this tool, is there a pre-made ISO that is known working?
Latest collection that I created is in modern Drivers topic Currently no changes at all, even they still need some touch Project finishing takes some time as its free time hobby
@ Trying to help This project has been going for ages . People were speculating that it would be ready by autumn ............ And then christmas . A problem is that people keep asking to have their needs added into it . Obscure versions . Different languages . It was only x32 and then x64 got added . Now its been combined with powis ? = It still isnt ready . .......... and its rapidly becomeing bloat ware Please can you just make a working version ? ............. and then add things if needed afterwards .
Just a friendly bit of advice (which could have also been applied to Longhorn or Titanic: Honour and Glory or several of my own projects unrelated to MDL) : Overloading yourself with too many goals at once is pretty counterproductive and might never yield a final product. Furthermore, judging by all the changes you have announced, it should be called 2.0 rather than 1.6 by now.
You need to understand some things. 1) This project is not my job. I need to work to pay bills and live my real life 2) I reached many milestones in XP2ESD. Many thing were rewritten as I want to support creating images in any language and in both architectures 3) Currently created POWIS Launcher is new way to provide great WinPE that can deploy all Windows version with simple GUI 4) XP2ESD use same features that are included in POWIS - Same method to launch installer, DriverPacks installation and RunOnceEx 5) Many things was revised and now can be used Windows 7 as base with Windows 8.0 and newer to Windows 10 21H2 as setup engine. I will try use Windows 11 too If it works for creating x64 based installers - It should work too 6) Maybe I can call new version as 2.0 7) If anybody want release this tool sooner you need to pay me and I can get “holiday” and investigate 100% of my time to test all things When I’m done with POWIS launcher and translatable app. I can maybe to release it sooner. But whole XP2ESD builder is huge project and needs some space. And first post must be completely rewritten according to new version which is really step forward in deployment. And things that needs many tests are currently connected with boot.wim in any versions and architectures P.S. Remember that “bloatware” words to show me these things after new version release.. And trust me, I really want to release new tool version to public soon as possible
there is two type of people here in MDL forums. one who take & complain. and one who give good feedback. even things are not 100% at first. I believe no body work for you, and for me. if you have complain do it yourself. who should delete this comment