Though the softgpu installer can't capable with xp,however the mesa3d wined3d openglide dlls could work on xp.So could you add the vga driver in xp2esd pack these 3d accerate components?
Kinda a asshole and rude thing to say while u can see this project its not dead because George and others are still actively working at it and still posting news about the progression about this project. Next time, read the thread of projects a bit before saying such things
There are no news. It is 1.6.2 since half year. Rarely few weeks people post anything relate to. Begin of year I asked here, about news, what is to solve for next release, when to expect approximately . No any answer to it. It is dead. Anyway, happy leap day.
Look man you are not the creator of this project only the creator can say if the project is dead or not in our case George be grateful they are working on it because not anyone can risk there precious free time doing such things for free!Show some respect.I agree it takes a lot of time but thats how it is if you know to finish it faster write an email to George and tell him what they are missing so the project can be finished
I can test stuff and help for free, but there is nothing to test after last release. Neither any questions relate to errors or feature requests get answered, see here 3 weeks ago for example. As I said, was interesting project, I also tested. I respect the work. But now no any new any more. No answers, nothing. So I'm out, but wish you the best while waiting for.. whatever.
Unceirtan if asked already but would you support all different version such as OEM, Retail, VL combined into 1 wim? Where's the ISO?
useless only vl build ( for pro sku ) and retail ( for familly are needed because xp are activable in full offline
Some news: Whole POWIS is now rewritten from scratch to bring “wizard” like dynamic GUI. First goal was to make it readable in Notepad++. So I have restructured it and achieved it. Adding new features and ipmroving current ones is easy. Most pain is GUI in HTA - its really limited. But even with that I achieved a lot of cool things comparing to current one. I will probably show some screens during this week, I have not expected amount of work to get GUI better.. Now I’m fighting with CSS. I have also designed it to support multiple styles and resolutions. This will probably break another limits we faced during Windows deploying Wait and be surprised.
@George King That's now very user friendly. This will save you a lot of user questions in the future.
Lets describe new POWIS from #2998: 1) Default WinPE resolution is changed to biggest possible one in list of 16:9 or 4:3 monitor styles. Can be easily added 5:3 or any other requested. So for example on my test machine is WinPE always resized to 1920x1080. Wallpaper is selected according to current resolution (We will need wallpapers / background images in various sizes) 2) Every element is designed to works in any language - translation mechanism is done, just need to create sew separated language files (probably XML) 3) Table react on mouse hover or click. Table headers can be used for sorting 4) Setup image, Unattended or Driverpack have new feature to select custom files (done in DriverPacks right now) 5) Unattended list WinPE related informations on the fly directly from XML - this is work in progress right now So now I need to finish Unattended handling because now it loads some data and it needs to be improved to support on the fly modifying. For example partition Size or Label should be editable on the fly. As we have dual-arch Unattended XMLs I would like to support cross-arch settings. For example I have x64 Unattended and I want deploy x86 one using same disk settings. Currently it will loads Unattended for selected image architecture on "Setup image" screen. Whole Unattended logic needs to be designed. I think I need to add some Unattended settings - "Change image selection on the fly" checkbox unchecked by default probably. There should be probably also another button "Format now" to be able to perform these disk related settings from Unattended screen and refresh Target selection, because InstallTo element can miss too in XML. Diskpart script will process partitioning from XML. This will be done when setup process begin. But what should be selected on "Target" screen? Fake row with "Unattended setup will be used" instead of partition selection? Even if I finish these Unattended points there is still a lot of work. But when I'm done with these points I can probably continue in reals tests in WinPE. I hope whole process will be quicked when we get rid of usage of original installer. "Powerful Windows Setup" option should not have any stupid limits. Standard Windows installer require EULA and FLAG and LANGUAGE limits (Product key aswell). This means you cant deploy cs-CZ image from en-US installer when EULA is not in correct place based on language and flag. So when user use "Powerful Windows Setup" then will be processed Unattended disk settings with diskpart and then will be seleced image applied to target location using wimlib, then will be applied rest of Unattended to offline image using DISM. I hope whole process should be smooth replacement for Windows image deploying from WIM / ESD / SWM.