News: Today I was finaly able to install XP in VirtualBox with new POWIS. setup.cmd was modified to accept new setup mechanism “POWIS” - so diskpart script and deploying image works, finaly. Now another challenge is there.. I have great solution to run and hide CMD script and then watch its redirected output. But that look currently like issue in my setup.cmd - works fine, But when redirected to txt, then it hangs. Probably issue with my overcoming method to accept more than 9 parameters in my setup.cmd… I’m using /shift and goto mechanism to parse them. Any idea about that? Now I need to check and improve deploying other images. This should be easy
100% useles with latest compiled one. If you want, you can always use $OEM$ folder for your experiments. If you mean ACPI type, Thats still there with modified Longhorn NTLDR on first boot. Thats best way to keep compatibility with any XP machines including old machines from around 2000
It will be sooner than 2025. My daughter just born few weeks back… I have 14 free days begining 22.7. So hope for some progress in POWIS during that time But most of hard things are done according to my notes Only one hard thing still remains - Fix ListDisk mountvolume function. I think I can find solution in Rufus code. I exactly know what must be fixed, But don’t know solution..
booting from ventoy, made the iso using default things just changed the iso names on the first part of the ini file. windows 7 boot (that one with the four colours that stick up together to form the windows logo) it freezes on that and i cant proceed. is there any way to do just a windows 10 setup enviroment instead of 7?
Ventoy will never be compatible with my projects. And according you second thing, you are booting UEFI, right?
Uefi no, but i tried working around with the isos and i put in place of windows 7 iso, a windows 10 iso, and it worked with ventoy, thanks
I tried this out on my ryzen system with a nvme SSD. Went far as last step after driver install than comes up with hal.dll error.
Hi guys i wanna hughlight the error i have been having for while with 1.6.2 I appeared as well on a very very old laptop which supports xp by default will 1.7 fix this bacause i it is the same one i have been recieving on my modern hardware pc
If the wim is present, the issue is not detecting the respective driver properly (for example, if it's from USB, make sure that the USB driver is present and working properly) on boot.wim. If it's from a CD and/or DVD, make sure that the SATA and/or IDE drivers for the optical drive are working properly on boot.wim. If it's from Grub4DOS, ensure the SVBUS driver is present and working properly on boot.wim (including install.wim/install.esd if you plan to install Windows XP from Grub4DOS using POWIS Setup).
i am trying from usb yes but i doesnt make sense not ot detect them when i have downloaded a lot of usb drivers from the drivers page of xp2esd i think it is not adding some of them on purpose i dont know really no matter how many times i try no matter what drivers i add nothing changes so i really need help also there is no install.wim but there is the install.esd,but it doesnt matter which one is used the errro is the same
Judging by your response, does that mean that POWIS is now out and able to install windows XP? Or it's always been able to, just the ability to do so on UEFI 3 physical hardware is still not present.
George King has done some progress on this, just so you know. With my help, Gelip and others, he figured out how to boot XP x64 on UEFI Class 3 Coffee Lake (8th Gen) hardware (bootdebug/debuggerenabled needs to be enabled and set to yes/true).
Just a huge thanks to everyone (but especially @George King) for sharing their knowledge and effort with the project. I have some odd no-csm x86/IA32 UEFI hardware I’m hoping to try XP2ESD on in future, and I’m looking forward to how those UEFI features play out.
This one has no EMMC, open source firmware, UGA, and 2 x mPCIE slots. Intention is IA32 UGA gpu in one slot and either NVME or an XP bootable sas/sata card in the second (probably LSI or ATTO which both have IA32 UEFI drivers).
@George King as i understand there is nothing new to install XP on modern hardware today or i'm wrong ? (Zotac ZBOX ID83 Core i3 3120M Ivy Bridge / Zotac ZBOX BI319 Celeron N2807 Bay Trail)