@George King I wonder why XP2ESD's WinPE is called "POWIS" instead of "XP2ESD". Will XP2ESD be merged with POWIS in the future?
Because everyone will probably use only POWIS option. Standard Setup just for upgrade installations. XP2ESD setup option will be there as I don’t se reason to remove it. Also much better to have that PE named POWIS instead of autogenerated name. POWIS is already part of XP2ESD. In future there will be also updated standalone POWIS. I want to have POWIS on GitHub too to make it acessible for everyone as its really Windows Setup replacement with PE additions
@wyf180 I don’t curently to play with drivers. POWIS is priority. Then XP2ESD release. Then work on kernel8.sys in same way as we have ntoskr8.sys to bring some common missing exports.
Will there be any new POWIS update? (apart from XP2ESD + POWIS), I published POWIS v1.0.3 a long time ago, will there be new changes for it?
@TesterMachineOS Its long time, But fully functional in its state. And Yes, when times come, then POWIS itself receive this update too.
If you want to speed up the process, you can ask the experienced community to help you with the development of XP2ESD 1.7.
Hi guys i dont wanna look like i am rushing or anything but is there an aproximate release date for XP2ESD 1.7 release date?
I don’t see currently any benefits in sharing unfinished POWIS, people like you will only have tons of “ideas to improve” instead bring something to be closer to finish line. I also don’t have time to tell and write down my ideas that will be implemented. Be patient, until I can publish working POWIS. Then you can inspect code and bring improvements directly. If you really want to help me, write JS function for returning multiple files paths in array from “Choose files dialog”. And remember it must be Internet Explorer 8 compatible. I was not able to find working piece of code without any additional “libraries”. Current method I did is in VBS, But supports only one file and doesn’t work in XP or 7 WinPE
Release date is unknown - it depends when I finish all needed work on POWIS, which is really crucial in whole systems deploying. Its like limits remover of Classic Windows Setup.
@ohault That require additional "libraries" and probably not suitable in IE8 in WinPE. I dont think there exist morking method. My VBS approach is fine for one file selection - I can deal with that, one file is fine, better than nothing. I will try to find compatible VBS approach, but still without success..
Hello i have tried to build WIXp x64 iso, but after booting it i have starting installer screen, and popup that installer cant find Wim or esd file, or i have bad mass storage or usb driver. My device is Thinkpad x280, and it has only usb 3.0, and only nvme for disk, i didnt have same problem on xp x32. Help pls
Actually I might be able to help you out with that, can you give me a little bit of context. Node.js version? Do we have access to "fs" or we consider even this library a problem? If we have access, I know how to work from there. Overall, If you don't mind, I'd love to help develop/work on the project, I have a vast JS experience if you do have a lot more that has to be done in it. In case you think we could colaborate (and I'm not coming off as intrusive), my discord: oosukeren P.S: Any library could be: 1) Compiled into a min.js that is easily importable everywhere 2) Transpiled to ES5(and earlier) for IE8 support with Babel
I am trying to install w xp on my computer. Instalation from sata cd/dvd drive connected to motherboard. A few cd with different drivers set. Till now xp sp3 integral and one x64 sp2 works to the moment when during Instalation proces I need press enter to install R to repair or f3 to quit. But in this moment keyboard doesn't work. I can press any button and nothing. I have 2 different usb keyboard and both doesn't work without exception if I connect them to usb 2, 3, 3.2 port. Anyone knows, has any clue where is the problem? How to solve it?
Would be nice if you gave the specific model of your motherboard. But generally speaking, you're most likely missing the driver for your usb controller. And no, usb2 is not a separate controller. It's now an emulation through the usb 3.x controller, so if your usb devices don't work at some point, this is likely the driver you're missing.
Msi z790 ace max, for this installation only 8gb ram. i9 14gen. Csm on, all fast boot and secure boot, disabled. For me a little bit weird situation, keyboard works till the last step. Never had such situation before.
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