George King

@reboot12 Is signed driver requirement only for winload.efi Driver signature enforcement problem?

If there will be language file in UTF-16 LE BOM format, it should work without issues probably. I'm not sure how works AutoIT strings-file handling.

@AstroSkipper There is no problem with "hacking" your compiled string and translate them. It's just recommendation (and learning experience), with MultiLanguage support using simple TXT / INI file for few string P.S. Release stable build first, then try to go with MultiLanguage support

@AstroSkipper Why not create strings language file? You can read current system locale and read strings from TXT / INI based on that. I have done this in POWIS Launcher like this. Here is mapping for all available 24 XP languages (No other MUI support at all, main base is enough). CMD based example taken from my POWIS Launcher (I use inside HTA JS+VBS, but it's really similar to this example) CMD to read Language settings REM Language for /f "tokens=3 delims= " %%i in ('REG QUERY HKLM\SYSTEM\ControlSet001\Control\Nls\Language /v "InstallLanguage"') do ( if /i "%%i" == "0401" set "SLLP=ar-SA" if /i "%%i" == "0404" set "SLLP=zh-TW" if /i "%%i" == "0405" set "SLLP=cs-CZ" if /i "%%i" == "0406" set "SLLP=da-DK" if /i "%%i" == "0407" set "SLLP=de-DE" if /i "%%i" == "0408" set "SLLP=el-GR" if /i "%%i" == "0409" set "SLLP=en-US" if /i "%%i" == "040B" set "SLLP=fi-FI" if /i "%%i" == "040C" set "SLLP=fr-FR" if /i "%%i" == "040D" set "SLLP=he-IL" if /i "%%i" == "040E" set "SLLP=hu-HU" if /i "%%i" == "0410" set "SLLP=it-IT" if /i "%%i" == "0411" set "SLLP=ja-JP" if /i "%%i" == "0412" set "SLLP=ko-KR" if /i "%%i" == "0413" set "SLLP=nl-NL" if /i "%%i" == "0414" set "SLLP=nb-NO" if /i "%%i" == "0415" set "SLLP=pl-PL" if /i "%%i" == "0416" set "SLLP=pt-BR" if /i "%%i" == "0419" set "SLLP=ru-RU" if /i "%%i" == "041D" set "SLLP=sv-SE" if /i "%%i" == "041F" set "SLLP=tr-TR" if /i "%%i" == "0804" set "SLLP=zh-CN" if /i "%%i" == "0816" set "SLLP=pt-PT" if /i "%%i" == "0C0A" set "SLLP=es-ES" ) Language.ini example en-US.AvailableDriverPacks=DriverPacks available en-US.Selected=Selected en-US.Filename=Filename en-US.Size=Size en-US.Copying=Copying en-US.InstallationInProgress=Installation in progress en-US.WinREButton=Recovery Environment en-US.CMDButton=Command prompt en-US.StartButton=Start en-US.CheckAllButton=Check all en-US.UnCheckAllButton=Uncheck all en-US.SetupType=Setup type en-US.SetupFile=Setup file en-US.Unattended=Unattended configuration en-US.WithoutUnatteded=Without configuration en-US.XP2ESDSetup=XP2ESD Setup en-US.StandardSetup=Standard Windows Setup en-US.Options=Options en-US.DynamicDrivers=Dynamic drivers folder en-US.DynamicDriversTip=Integrate drivers from drivers folder on setup media into deployed system before first boot en-US.DefaultPartition=Custom partition ID en-US.DefaultPartitionTip=Specify custom boot partition ID for Windows XP / 2003, usefull for custom multi-boot installations en-US.PAEPatch=PAE Patch en-US.PAEPatchTip=Remove 4GB RAM limit on 32bit systems en-US.SkipOOBE=Skip OOBE en-US.SkipOOBETip=Boot directly to desktop under Administrator account en-US.NoReboot=Noreboot en-US.NoRebootTip=Do not reboot de-DE.AvailableDriverPacks=DriverPacks verfügbar de-DE.Selected=ausgewählt de-DE.Filename=Dateiname de-DE.Size=Größe de-DE.Copying=Kopieren de-DE.InstallationInProgress=Installation wird durchgeführt de-DE.WinREButton=Wiederherstellungsumgebung de-DE.CMDButton=Eingabeaufforderung de-DE.StartButton=Start de-DE.CheckAllButton=Alles anwählen de-DE.UnCheckAllButton=Alles abwählen de-DE.SetupType=Installationtyp de-DE.SetupFile=Installationdatei de-DE.Unattended=Konfigurationsdatei für unbeaufsichtigte Installation de-DE.WithoutUnatteded=Ohne Konfigurationsdatei de-DE.XP2ESDSetup=XP2ESD Setup de-DE.StandardSetup=Standard Windows Setup de-DE.Options=Optionen de-DE.DynamicDrivers=Dynamischer Treiberordner de-DE.DynamicDriversTip=Treiber aus dem Treiberordner des Installationsmediums vor dem ersten Start in das bereitgestellte System integrieren de-DE.DefaultPartition=Benutzerdefinierte Partitions-ID de-DE.DefaultPartitionTip=Benutzerdefinierte Partitions-ID für Windows XP/Server 2003 angeben, nützlich für Multiboot-Installationen de-DE.PAEPatch=PAE-Patch de-DE.PAEPatchTip=Entfernung der 4GB-Arbeitsspeicherbegrenzung auf 32-Bit-Systemen de-DE.SkipOOBE=OOBE überspringen de-DE.SkipOOBETip=Direkt in den Desktop unter dem Administratorkonto starten de-DE.NoReboot=Kein Neustart de-DE.NoRebootTip=Nicht neu starten Of course there are hardcoded strings inside file when there is no Language.ini. I hope you can take inspiration from that

@AstroSkipper Is there any translation file for your PopMenu?

In various XP / 2003 languages are Documents and Settings / Program Files / Administrator / Start Menu translated. It's stupid, but you can safely use environment variables to overcome this issue And of course all coded paths must support spaces to avoid future problems

@AstroSkipper Will let you know in few hours, I'm still out of my testing machine

There already exist OpenVPN 2.5.4 for Windows XP https://winraid.level1techs.com/t/openvpn-v2-5-4-for-windows-xp-and-windows-server-2003-x86/39894 or https://sourceforge.net/projects/openvpn-for-windows-xp/

If it can be 10 lines tutorial, then yes. There are bunch of needed steps that must be done. It´s up to you, download toolkit and play with that If you would like to create XP/2003 universal image based on modern installer. I’m not going to spend days to create tutorial for manual job If somebody tell me reason about downloading 4GB, sorry. It´s still smaller than downloading Windows 10 ISO. And of course to create XP2ESD image you need both 7 and 10 too (can be based on 10 only).

You can do it without them, nothing is forced. Just simply inspect configurable options in config.ini.

I means this Furthermore, some final test have to be performed to finish private testing. And then, very soon, the beta testing can be started.

@AstroSkipper Let me know if want test to it (on x64 too)

@Jakob99 Here is my next attempt, INFs are fixed and with all available translations that exist in Windows 8.0 RTM, whole INFs are 8.1 based. Hope it will succed now. sd+mmc_generic_driver.7z

@AstroSkipper Have you tried it on XP x64 too?

@Jakob99 I have probably found whats wrong. I performed some tests on INFs and seems like they are broken a bit. I will upload fixed files soon, when I confirm they passed my tests with INF parsing

@Jakob99 What happends when you try to boot Windows 8.0 installer on your machine? Can you see your disk device? Also would be great if you can do same test with Windows 8.0 build 8056. EDIT: Windows 8.0 beta download links https://windowsbase.pl/w8beta.php

@AstroSkipper I saw that in past. It was not bug in start /wait, but it was caused by used workaround in called app by using some kind of "SendKeys" commands. Of course, when you need to wait until is finished, another crazy workaround is possible. start /wait "XX" cmd /c start mypapp.exe And it can be also launched using invisible.vbs. Yes, it's crazy, but doable, until problematic code in called app is fixed And yes, there could be like another 1000 different reasons why you see it as "bug"

@AstroSkipper Can you explain me more bug you are talking about?

@AstroSkipper It's not buggy you need to add Window Title. Example of correct order. You find like 10.000 lines of code in XP2ESD, you can take many code examples there start /wait "SDI" "%~dp0SDIO.exe" Using CMDOW is bad, it's flagged as virus from like 2006. Use native VBS instead to run application silently. Invisible.vbs (accepts parameters too) ' Run hidden cmd with arguments Dim Args() ReDim Args(WScript.Arguments.Count - 1) For i = 0 To WScript.Arguments.Count - 1 Args(i) = """" & WScript.Arguments(i) & """" Next CreateObject("WScript.Shell").Run Join(Args), 0, True And then use it this way %WinDir%\System32\wscript.exe //nologo "invisible.vbs" "%~dp0apps\Cleanup.exe"

Why not follow this tutorial to add one missing function? There is example how to extend GDI32 with custom function as GDI42. https://www.codeproject.com/Articles/17863/Using-Pragmas-to-Create-a-Proxy-DLL

@Jakob99 If you integrated them into boot.wim you were able to see your eMMC in setup?

Have you added newly compiled ntoskrn8.sys from latest sources mentioned after that? Or have you tried these ported drivers from latest XP2ESD which already have it?

XP2ESD is what you are looking for

@Jakob99 We finally managed to get working Windows 8.0 build 8056 Generic SD/MMC driver under XP. Here are same drivers for Windows 7 (ntoskrn8.sys is compiled as W7 target). EDIT: Broken files removed, see post bellow for updated files

@GD 2W10 @Damnation Yes, many more ported drivers are in collection. Currently my latest attempt seems to be success and we have now Generic SD/MMC driver from Windows 8.0 beta 8056 for XP/Vista/7 according to @Andalu tests with latest kernel extender