I will think about 2000 support in future, sadly there doesn't exist multilanguage UpdatePacks.. I'm currectly busy with my other projects. I'm adding this into ToDo list. Repacking using obsolete setup engine aka "PantherXP by Thunderboy" was possible, but this Longhorn boot.wim it lack HW support, missing translation and many more possible problems.
Thank you so much. I couldn't quoted, because I don't have 5 posts yet, so I couldn't quoted your reply. Edit: XP2ESD gave me "ntoskrnl.exe" error which one also happened to me tons of times until I found the fix. But I think if Windows 2000 support gets improved then why not.
@George King I would propose moving runonceex.cmd execution into watcher.cmd as opposed to runonce. Because on some of xp2esd attempts i ran into following behaviour: first boot: mysysprep and sdi runs normally reboot second boot: runonceex -> sysprep folder is flushed out runonce -> windows tries to execute the already deleted runonceex.cmd which was supposed to run on first boot
There are needed more changes as my goal is to create one universal ISO for USB with XP and all newer system. I’m currently little bit busy with my reals life and problems. So I will investigate it later as there is also new RunOnceEx translation method introduced in POWIS. So compatibility changes needs to be done as my goal is to use one support folder with SDI and driverpacks for all systems etc. But currently is in my radar Vista offline integrator to get this OS fully updated too
@George King from where do the dism and bcd tools in xp2esd (apps and apps\dism folders) come from? Did you get it from the ADK or from an iso? Furthermore, I would propose having winntbbu.dll replaced with a localised version for each auto sysprep to show localized "Windows is being started" text on first boot before myfactory is launched
DISM and BCD tools are from WAIK, MUIs are from ISO. This winntbbu.dll in Auto-Sysprep include patched one with string in all languages. This should work. Can you provide a picture what exactly do you mean?
i am still trying but i screwed up that windows xp vm without creating snapshots so it might take a while
@George King Do you think there is a chance that XP2ESD will work on Windows XP x64 or Server 2003 x64?
@George King Was Offline Sysprep ever considered as a possible workaround for VBox requirement? Also, is it possible to crate an installer similar to POSReady/WinFLP, where he final steps would be handled by FBA? And maybe some support for WES2009 images along the road? All of these questions are theoretical, since I don't know how each of these actually work.
I don't think it's possible. The install.wim file of POSReady/WinFLP/Embedded contains windows components separated by multiple folders instead of full OS in one folder. I looked into Windows FLP's install.wim file by 7-zip and it contained 12 folders, and each folder contains different components.
I'm referring to the way WinFLP installer does things, i.e a (more-or-less) live system that needs FBA to quickly set it up. It is way faster than the XP setup. And, maybe eventually that can potentially lead to WES2009 image support for this tool. I haven't messed with WES2009 too much, but it seems like you can only manually deploy it to the target system, but no way to create a bootable installer. Also, any word on OfflineSysPrep?