Hi, I'm trying to port Windows XP w/SP2 into Windows Fundamentals for Legacy PCs installation mechanism. But unlike setup mechanism of Windows Longhorn or later, it's separated into many indexes and each index contains different components. I tried to capture Windows XP VHD once and append eleven times, but it doesn't work. Is there any way I can do this? Thank you.
Use windows xp pro sp3 with posready update ( more simple ) For msi error use regsvr32 msi.dll ( after os installation )
I meant converting "i386" setup type to "WinFLP.wim" I want to install Windows XP using Windows Fundamentals for Legacy PCs installation method.
You have a similar project already done here https://forums.mydigitallife.net/th...ate-modern-windows-xp-installer-v1-5-6.82935/ Have a look. It's open source
I already know that. But I'm trying to do with Windows XP Embedded versions instead of Windows 7 + 10. I also know that how to do with Windows Longhorn. But it's similar way. I'm more interested in Windows Embedded Setups due to having more options to install Windows.
You need to unpack "Microsoft.Embedded.Setup.Data.Evaluation.dll" extract "Microsoft.Setup.WindowsEmbedded.Setup.xml" modify according with your preferences, insert modified xml in "Microsoft.Embedded.Setup.Data.Evaluation.dll". P.S Be sure to patch snk in order to avoid errors.
Sorry, my mistake. For Windows FLPC dll is "Microsoft.Embedded.Setup.Data.Volume.dll" and setup configuration is "Microsoft.Setup.WindowsEmbedded.Setup.xml".
It looks like I have to use a text-editor and edit the .dll file. Because I couldn't find the .xml file via opening with 7-Zip.
Thats the nasty part, i did this long time ago. If i remember correctly, you need to use il assembler and il dissasembler. snk means "strong name key" you need to patch dll after assembly in order to avoid errors because modified dll is tampered.
For offline scenarios, it could be interesting from Windows Embedded to be able to generate .wim files with metadata about Features, Packages, Drivers, Capabilities, etc to be used with DISM. For online scenarios, this would required to backport CBS, but starting with offline scenario could already be a good departure. Writing custom DISM providers could also be a path to explore.
Surely nobody would install Windows XP (whichever way) in any practical situation? So all this is really theoretical
There are practical reasons to do practically everything, no matter if they seem odd to you. There's are still tons of setup running even on DOS, especially in the industry. In Algeria one of the first water system ran from before Colombo discovered the Americas to 1971, and no one tough to replace it as long as it was pumping water, why in the heck the IT should work differently?
It's both a good and a very very bad practice. Perhaps good in very short term, but hereafter, when you reach this state, you are like a prisoner of time and you have lost both your freedom (to innovate, to pivot, to even reproduce) and the control of your driving wheel!