Yes, its possible, all screenshots are currently from Windows 10 host. Running POWIS as "Autorun" in ISO will be possible, but host must support HTA, VBS, JS and WMIC and of course run it with Administrator rights. But It's not currently in my priority list, step by step. Most of boring work seems to be done, but still not finished to testing phase in WinPE..
Hey George, NIIICE WORk So Far on that 1.7 XP i am really grateful for doing something like that Can i ask a favor.Would you send me those testing enviremont so i can provide a feedback to see if it works for my configuration?
Nothing big. In rare free time (couple of minutes in day right now) I’m continuing in POWIS coding. I can confirm my XML loading mechanism for Unattended works fine. Everything is loaded and can be processed (not done yet). I mean disk in any scenarios using original installer or just POWIS way. Currently I have designed how I can interpret these Unattended settings in Target tab. Its insane amount of work to make it perfect. But Yes, I’m closer and closer, just lack of time (Thats why I published ListDisk, community can investigate it already in waiting) I think its needed like another 1500-2000 lines of code to make first deployment test. But mostly everything is in place, when its done, probably all stupid deyployment limits are gone
First picture - Powerful Windows Setup, Standard Windows Setup, XP2ESD Setup. How is possible to overlook that we have 3 options? 1) Custom method driven by POWIS GUI only 2) Standard Windows Setup + XP2ESD Setup is still same what we have, there is noreason to drop these things, when they works.
@George King I suppose that this upcoming release will be the biggest change that XP2ESD will achieve (compared to the previous versions of XP2ESD).
Yes, it's evolution. XP2ESD was born 3 years back and from begining it was supposed to became universal AIO deploying solution. During night I have noticed issues with Dynamic disk partition detection in Target tab which is powered by WMIC, now it's fixed and optimized. I think most of logic are correct and tested. Now I need to review my whole VBS script and optimize it. I think I will currently start working on new translation mechanism. I will probably turn language files to XML like ViStart have. Because when master English file will be out, adapting to all languages will be easy, I will include 38 languages AI translated as begin, so native speakers can update it. And another point is new POWIS will be on GitHub.
On Tuesday I am hope that i'm gonna have a Computer Fujitsu P420 E85+, Intel Core i3 4150 3.5GHz, 8GB DDR3 RAM, 500GB HDD, DVD-RW to test Windows XP x64 with XP2ESD using my HDMI video capture card through my VGA to HDMI adapter with audio. If I have two computers, maybe debugging XP2ESD's XP installation will be possible for me.
Sorry I meant if I don't have an OS installed on the system before hand or is that really the only way?
Exactly, in upcoming release are included some useful tools from Explorer++ Start Menu. Explorer++ is accesible from toolbox. It should be really easy in near future. That depends on situation, Because I decided to rewrite whole POWIS which is just GUI for setup.cmd which controls whole Windows Setup. Both methods Standard and XP2ESD are done and safe. POWIS method needs to be adapted. But thats easy part. Btw, I have succesfully tested new XML translation mechanism for POWIS. Now its time to be sure every element works correctly with translation changing on the fly - from dropdown for example. I still have 2 open points connected with wizard buttons… I think I have solution in my mind already. But its VBS vs JS. Template is HTA + external CSS, JS and VBS, then with VBS are dynamically loaded everything into HTA, and JS is called various times from VBS to bind table rows functions with abilities to add new rows into table without additional binding. Everything compatible with IE8 engine. So big testing was really succesful on many things. I hope I will prepare complete en-US.xml in few days.
Fair enough the other thing I wasn't sure is downloading say the dell optiplex 3070 micro drivers as a cab file or do I download them as the .exe setup they come in or extract them to just a folder and put that folder in the drivers location.
And according mentioned like Device manager in WinPE, I have already tried to code basic like device manager page for POWIS compatibility checker. I have not investigated that idea a lot, but I have tested all HWIDs grabbing into HTA. It should be doable to check If selected image have support for your HW. For example AHCI, USBx compatibility. And we already have SDI which can save all DriverPacks HWIDs into human readable TXTs. So when we construct for example all known Windows XP HWID list for GPU based on latest XP drivers (NVIDIA mods included) we can have compatibility check like 1. All drivers found in DriverPacks - no worry 2. Your GPU doesn’t support selected system etc. If anybody have idea how should looks compatibility checker, let me know about design. Creating compatibility list for 5.1/5.2, 6.0, 6.1 could be annoying, but really useful for deploying. I’m realy open in designing this part of POWIS