First I solved all the problems. Windows 7 and 10 ISO gave an error because I added Turkish. When I changed it to English, the error was resolved. The other problem still persists. I developed a way myself and solved it that way. Finally I want to ask Windows 10, version 22H2 (19045.2075) Will support come? It stays in rcraid.sys in all but "safe mode".
Got it working again with removing wga and using a win xp sp2 activator. Anyway is wga rlly needed for xp?
@rulman Check these posts to identify If its already supported Code: https://forums.mydigitallife.net/threads/tool-xp2esd-create-modern-windows-xp-installer-v1-6-2.82935/page-71#post-1747206 I think its still fake build
yes it is 19041 i confirmed it just install KB5015684 it is 22H2 but really still system file is 19041
I tried my mi pad and the driver I offered ,it could work with win7's winusb driver however when I replace your win8 usb it got error with code 3.
@George King I know where to find the BLD file now, but the problem is: What is the command needed in Windows Run (WIN + R) to build compiled ntoskrn8.sys? Does WinDDK require parameters to point out to NTOSKRNL EMU location or something else? Or do I have to use the GIT command prompt to import fork and then type BLD and press enter? Because If I try to open BLD directly from the windows folder, the NTOSKRNL EMU is unaffected.
Is there a way to delete the XML-file in the root of ISO (probably made by NTlite)? And how can i integrate my own "autounatted.xml" in the root of the ISO?
What XML do you mean? There shouldn’t be any. For your unattended you can place multiple of them in ISO/USB root, POWIS Launcher allow you to choose them (or skip it too). But remember, currently you can’t use HDD partitioning. There will be some error ( cant remember, I’m still out of my PC). This error is caused by WinRaid modded drivers (Intel RST) by Fernando. You can locate them and delete in plugins\winpe and rebuild your ISO. I will investigate this issue later as I think its caused by badly created WinRaid signing certificate. But I don’t know now. If its really caused by bad signature, I will resign them. I have also PMed Fernando with this issue as his signed drivers are always shown as unsigned even with imported certificate. P.S. You can also place multiple WIM/ESD files in sources folder. Its designed to deploy all systems from one setup media. Just select Standard Windows Setup when installing 7-10. There will be also soon another script to fix License error when using language mistmatch boot.wim / Setup WIM/ESD. I would also like to find proper patch for this instead of WIM/ESD rebuilding..
There is always left a XML file in the root (looks like a "Last Session-xxxxxxxxxx.xml" by NTlite). It is shown in POWIS too. I always have to unpack the ISO, delete this file and place my own "autounatted.xl" in the root, after that i have to rebuild the ISO with NTlite. My suggestion: Modify the script for NTlite not to save the "Last Session.ini". And there`s got to be a folder in XP2ESD like "root" where we can place files that will be copied automaticly into the root of the ISO.
It should be automatically deleted, its already it script. Maybe you have previously Touched your ISO with NTLite? Because when is NTLite started from XP2ESD to clean boot.wim, then is Last session automatically deleted as far as I remember I can check it again after my return from vacation
I controlled my sources in "repository", there is no file like that in the roots. Here`s a screenshot of unpacked "WinXP_AIO_WIM.iso":
Easy, its caused by German translation. There is no pattern Last-Session in your file. I will modify boot.wim.xml preset to force suppress its creation instead.
@TesterMachineOS Code: https://forums.mydigitallife.net/threads/tool-xp2esd-create-modern-windows-xp-installer-v1-6-2.82935/page-91#post-1755587 P.S. Doesn’t tell you POWIS error everything you need to know?