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
I want to see the GUI designs on DM, maybe I can give you feedback, suggestions and advice regarding that!
So after updating all my drivers and what not on a windows 10 22h2 build I simply ran in powershell: Export-WindowsDriver -Online -Destination "F:\Drivers Backup" I assume from there I would need to manually compress each folder into a .7z and place them in XP2ESD\plugins\driverpacks
If you want my opinion, I think that the design should be user-friendly and look similar to Windows' Device Manager.
Please again that post. Compatibility checker should looks like device manager? Sorry, but thats not opinion I’m looking for. Thanks.
Oh, I thought you were talking about the device manager. The compatibility checker should look like Windows's compatibility checker.
Yes, thats way to backup drivers for your Windows 10 for reinstalling. Of course we can use other tools, like Driver Backup! Etc.
So after running the installer Windows Boot Manager just goes to a screen saying Windows failed to start. The file in question: \ntldr Status: 0xc0000098 Info: The selected entry could not be loaded because the application is missing or corrupt
@George King I am excited to see all the progress! A suggestion, I notice that ListDisk does not have a license. I do not have enough posts to share a link, but GitHub runs a website called Choose A License, that explains the basics of licenses, if you don't know which one to pick. Any license is better than none, regardless of how restrictive or open you want to be.
NEWS: I'm still working on translations on "current POWIS level". I have not expected amount that amount of work again During this journey I have added some improvements as when I masively clicking and trying POWIS new ideas were born. And of course a lot of text to translate too. Now I have added new checkbox to "Target disk" tab to be able to hide not mounted partitions. Also Virtual rows from Unattended settings are now idetified as "Virtual partition" and "Unattended settings" in Partition type and detail. If everything goes as expected I think I will finish tonight whole POWIS translation. This mean I will have en-US and cs-CZ done. I have already tested th-TH to be sure all characters are loadedl correctly. Then Options and Review page needs to be coded - they are still empty.. Still need to decide which options should be there, RunOnceEx, Noreboot, PAE? (can be run only in x86 setup or we need to add x86 subsystem to x64 WinPE, or grab latest PAE patch3 sourcecode for 6.0-10.0, or add some kind of inject to automatically patch these files on first run and create PAE files with their own boot entry), Skip OOBE (depends on Unattended settings), Dynamic Drivers should be reworked - still not sure how I re-add it as it needs some kind of INF checker for supported OSes - probably will work still only on checkbox without additional check for now. Quibble should be there too, I think I would like to add Bootloaders into Options tab, to add ability to automatically install GRUB and call needed boot entries from there - Standard Boot Windows manager or Quibble or single boot option outside Standard Windows Boot manager. Because if we can just tick checkbox to install GRUB, it's another "unlock". But still huge amount of work. And some features will be added 100% in future after 1.7. Currently I need to push new POWIS to same working level like old one was. And that hopefuly dont require huge amount of coding. For example translation mechanism is currently like 500 lines of code and still not done, but works like a charm.. New screenshots will be done when I finish translation - I will then do some AI translation probably for ro-RO for @UsefulAGKHelper / th-TH for @MilkChan to fix it as native speaker can. Of course there will be probably new lines with translation soon, but for testing purposes we should do this. EDIT: HTA + CSS + VBS + JS = ~4500 lines of codes right now
As I still have not coded default settings for new POWIS readed from settings.ini, I’m thinking about adding “Settings” link into bottom of “Toolbox” to access hidden “Settings” tab. There should be everything change-able on the fly. Like default WIM/ESD, Default Unattended file and other possible settings, and of course If its booted from writable media, save these settings too. Maybe this “Settings” link in toolbox should be available only when booted from writable media. Of course this lead into another new lines for translating. But better to do all of these things now, as code became huge and huge..
Hello, sorry if I'm interrupting anything or unnecessarily bothering you, but, if I have understood correctly, you're currently making an automated software that would help the less software knowledgeable people like me install Windows XP on most UEFI non CSM pcs? Because I currently have a Kaby Lake processor PC that, after using this tutorial https: //msfn.org/board/topic/185917-windows-xp-on-surface-pro-1/ I was able to get my pc only to the boot screen post install, and was being told by the tutorial creator that if I want to get it to work, I'd have to make customizations, which I don't know how. So, if i do wait for you to finish with the software you're making it, may end up working on my PC too, without me having to start learning how this works from scratch, right?
@UsefulAGKHelper Have you used “your method” to deploy XP2ESD image? Why you don’t have installed all other drivers? Why I’m asking? I have not faced that issue on any of tested machines.