@UsefulAGKHelper XP2ESD images already have devcon.exe in system32. It was updated in v1.6 to latest version that runs under XP
@George King xp esd with acpi 19 not work for me in ryzen , old version work for ryzen. for intel acpi 19 / for ryzen other needed
@George King I think this code is incorrect because there's no "\Windows\Windows" directory in Windows. If installed, the msahci driver would get broken if installed because XP's original mshdc.inf still isn't removed. Instead of this: Code: REM Prevent orginal XP MSHDC install incorect files acording to Windows 7 MSAHCI if exist "!TEMP!\mount\Windows\system32\drivers\msahci.sys" ( del /q "!TEMP!\mount\Windows\Windows\inf\mshdc.inf" >nul 2>nul del /q "!TEMP!\mount\Windows\Windows\inf\mshdc.pnf" >nul 2>nul reg add "HKLM\TEMPSYSTEM\ControlSet001\Services\msahci" /v "SysprepCleanup" /t REG_DWORD /d "0" /f >nul ) It should be: Code: REM Prevent orginal XP MSHDC install incorect files acording to Windows 7 MSAHCI if exist "!TEMP!\mount\Windows\system32\drivers\msahci.sys" ( del /q "!TEMP!\mount\Windows\inf\mshdc.inf" >nul 2>nul del /q "!TEMP!\mount\Windows\inf\mshdc.pnf" >nul 2>nul reg add "HKLM\TEMPSYSTEM\ControlSet001\Services\msahci" /v "SysprepCleanup" /t REG_DWORD /d "0" /f >nul )
@UsefulAGKHelper Its not needed anymore. MSAHCI.INF handle this on its own with custom MSHDC.INF. Its mostly leftover from development
So the driver's already fixed? So, the errors are gone if I install this even if XP's original mshdc.inf is present because it will be replaced? Wonderful! Anyway, with the edit I made, I'd rather have the untouched mshdc.inf and mshdc.pnf files to be removed just to prevent errors if I try to install the msahci driver. In fact, I'd also copy mshdc.org renamed as mshdc.inf to avoid problems or BSODs with the IDE drivers, just in case (obviously I'm gonna borrow the same values from the other "copy" codes you added to avoid breaking anything inside XP2ESD).
@George King You may not include this modified code, but I will use it in XP2ESD's 1.6.3 release for obvious reasons unless this code causes problems. Code: REM Prevent orginal XP MSHDC install incorect files acording to Windows 7 MSAHCI if exist "!TEMP!\mount\Windows\system32\drivers\msahci.sys" ( del /q "!TEMP!\mount\Windows\inf\mshdc.inf" >nul 2>nul del /q "!TEMP!\mount\Windows\inf\mshdc.pnf" >nul 2>nul copy /y "%~dp0plugins\drivers\!ARCH!\Ported\Generic_MSAHCI_6.1.7601.25735\mshdc.org" "!TEMP!\mount\Windows\Inf\mshdc.inf" >nul reg add "HKLM\TEMPSYSTEM\ControlSet001\Services\msahci" /v "SysprepCleanup" /t REG_DWORD /d "0" /f >nul )
@UsefulAGKHelper I going to tell it to you again. When you install MSAHCI driver you don’t need to do any additional steps. No BSOD. Driver is standalone and during driver installation it overwrite original MSHDC with fixed one with commented out problematic HWIDS. If you encounter issue, describe step by step how to replicate it. I have tested in VirtualBox and on real HW too without issues. This driver is rewritten and fixed probably from v1.6. I don’t remember everything, Thats why I provide changelog (sounds for me like same situation with devcon). You are probably trying to “fix” something whats not broken. As I told you let me know exact situation when you find real issue. I don’t see it now. Otherwise I’m happy you digging around
Speaking of problems, when you booted deployed XP install from UEFI on real hardware you could see myfactory thanks to FlashBoot/Uefiseven? Because if that's so, then the problem in my case might not be related to int10h, mass storage controller (but XP's backported generic nvme driver gave me 0x7B in windows 7 at that time with driver signature enforcement disabled, so perhaps that's a clue?) If I install correct mass storage drivers on XP beforehand through VirtualBox, it stops crashing on real hardware if boot crash is enabled and correct kernel is set.
@George King Just so you know, if XP2ESD's created iso is mounted, POWIS Launcher can be launched inside the host Windows (because of the host PC's different screen resolution and fonts, obviously the items inside the window do not look the same). Once iso is mounted with a drive letter, POWIS Launcher can be opened from the Deployment folder or extracted boot.wim inside the temp folder. The fact that it worked for the launcher to open is fantastic! Clicking the Start button gives the "Installation ended with undefined exit code" error after a few seconds because I opened POWIS Launcher from the deployment folder. Extracting boot.wim into the Temp folder and then opening setup through the POWIS launcher may allow it to open. I know you won't consider this solution that I told you about earlier, but with this discovery, I may not even need to create a duplicate setup.cmd file, I could just use the code (I will try to do something about the boot partition thing so that if it exists, partition and file deletion should not proceed to preserve the host system's boot files) from the boot.wim file that shall be extracted every time before starting (unless it exists then the POWIS launcher shall start up immediately). Who knows, instead of doing this by scratch, the original code (with some extra touches) can speed up this process. If anything goes wrong, I can just overwrite the setup.cmd file with the untouched one from the archive.
@UsefulAGKHelper Do you think you discovered something? Or how do you think I wrote POWIS? Just read again what I told you about “upgrade” installation? You will never receive testing version again, as you totaly don’t know what does mean PRIVATE! P.S. You just tested nothing from 68 lines long changelog and only investigating again and again things that I told you many times again and again. If you want investigate them, do your useless “findings” alone. I’m happy you done OOBE GUI mod for 2003 and new LOGOS for installers. That was good work. Other discussion totaly waste of time.
That's not nice. First of all, when I told you that I could run OOBE (with Mouse tutorial) without errors from XP x64 using the XP2ESD build, that was the first time I tested with the updated build you sent me, so it's not "nothing". I tested the mouse tutorial from OOBE and it was nice to use it. It was the first time that the rcraid.sys driver error stopped appearing (because it was removed). I also had to the opportunity to test MyPal from the build. Second of all, the reason why I tried to do the multi-boot thing was to get XP to boot through UEFI Class 3 (I didn't want to erase my data on my real hardware, that's why I proposed all those solutions of not cleaning boot partition, it's all connected to this in my case). Because other tests of copying deployed pre-booted XP to another partition of the main HDD didn't work to get XP to boot on my UEFI laptop, the conclusion is that this multi-boot solution wouldn't work either in my case. I'm not the only one who couldn't manage to get XP to boot through UEFI Class 3, maybe Intel 8th generation coffee lake processor is too new for XP to boot, btw someone else in this XP2ESD topic already stated that they couldn't get it to boot XP through pure UEFI either, so it's not a "useless finding" that I can dismiss (I use latest x64 ACPI version from XP2ESD, I will try to swap the ACPI files again with the other x64 versions, if it doesn't work, then the problem in my case may be related to incompatibility with Asus x509FA rather than the drivers themselves). Tests confirm that XP2ESD's ported simonvme driver works on Windows 8.1, while XP2ESD's ported stornvme gives BSOD on Windows 8.1, which explains the BSODs that maybe I can't see from XP (but on XP even with simonvme only, it still doesn't work, so the problem is not related to mass storage drivers).
@George King On XP2ESD created ISO with windows 7 PE, efisys.bin uses the unmodified bootx64 file, this prevents the emulator from being used (XP2ESD setup based on win 7 PE won't start on pure UEFI without emulator). With Imdisk, unmounting the efisys.bin as a virtual floppy drive (A to replace the unmodified bootx64.efi with the FlashBoot patched one, and then unmounting efisys.bin, can fix this problem and allow the emulator to be used. I always had to modify the efisys.bin to get the XP2ESD ISO with windows 7 PE to boot through UEFI in VirtualBox or real hardware.
I am trying to install XP on my Dell Latitude 5490 with this tool. It gets through the first stage of XP2ESD setup, then boots into XP, but I don't have any keyboard or mouse, but I do get sound, then it finishes the second stage, but after that, it doesn't boot at all and says that hal.dll is either missing or corrupted. How can I fix this?
Hey there, looking to reinstall windows xp on my desktop and kinda waiting till 1.6.3 comes out. I assume it will be out this week? Also the driverpack stuff confuses me, what do I even download? or are the default basic ones in the 1.6.1 download enough to get me started to install my own drivers afterwards for my setup? I see you dont use a modified nv4_dispi.inf to support additional nvidia cards like the 980ti (easy change I can do on my end if you dont want that on your package) just poking around right now till you release 1.6.3 because my pc needs a reformat (endless BSOD's lately) and I am excited to try this out