Actually UEFI Class 3+ has that ability of having secure boot always on. UEFI Class 3 and newer are UEFI-only and have no csm/legacy boot option in firmware. UEFI Class 2 with CSM disabled can function like UEFI Class 3 but it's not the same thing because CSM can be enabled in UEFI Class 2.
Yes, with Secure Boot Enabled is UEFI Class 3+ but Secure Boot Disabled & CSM Disabled = UEFI Class 3 - that's why this option is in the UEFI Setup so that CSM can be turned off If there is a CSM option in the UEFI Setup, the OS can be booted in three modes: CSM Enabled - boot from Legacy first > OS use legacy loader (ntldr or bootmgr) - this is like old bios legacy without UEFI CSM Enabled - boot from UEFI first > OS use UEFI loader (bootmgfw.efi) but also PCI Option ROM's e.g. VBIOS graphics card CSM Disabled - boot form UEFI only > OS use UEFI loader (bootmgfw.efi) and GOP firmware graphics card (PCI Option ROM's is unavailable) This is not about UEFI Class but the lack of ACPI compatibility with WinXP and no official USB and SATA/NVMe drivers for WinXP. Of course, there are unofficially modified drivers
With CSM enabled, you can load kernel with winload.exe from longhorn for Xp, but it need to be patched. It have some bugs if GPT is used.
I will PM all of you testing XP2ESD ISO for x64 UEFI research. I'm thinking I'm close to make everything automated, but still without ability to successfully boot. I need to catch that issue ASAP. I need to finish few more things before uploading, but it should be tomorrow. Hope you will succeed. This UEFI research is out of my plan, but if you find out needed steps I will add them.
@UsefulAGKHelper OK, maybe the UEFI class means the computer's capabilities but that's not the point. It is about the mode in which PC works, i.e. what components it is using or not. Windows on PC UEFI Class 3 (GPU has GOP) works in the same way as on the PC UEFI Class 2 with a graphics card that has a GOP when CSM mode is disabled.
Do you use the Mount or Capture tab? If Capture, what parameters do you set? I only use Mount tab, delete files from the current install.wim and add my own files. I tried to use the Capture tab to create a new install.wim file but something is wrong because in the installation time I have a error: Code: Windows could not display the images available for installation
Well it's obvious what I said earlier. So yeah I used the capture method, I ran as administrator the program GImageX V2 with high priority. For XP installations that were installed with the XP2ESD installer, make sure that the SKU Flag in GImageX matches the edition of XP x64, for example, I used the Professional edition so I chose the Professional SKU Flag. (this only works with XP built by XP2ESD because it has XP's EULA files placed in proper locations in XP's wim for the setup to work) Make sure to check "Boot" but uncheck "Verify" and "Check".
Hi @Gelip. you may change resolution from "UNATTEND.TXT" just insert: Code: [Display] BitsPerPel=8 Xresolution=1024 Yresolution=768 Vrefresh=60 also, you may disable signature verifier using those lines, in hivesft.inf: HKLM,"Software\Microsoft\Windows\CurrentVersion\Setup","MinimizeFootprint",REG_DWORD,1 HKLM,"Software\Microsoft\EmbeddedNT\Security","DisableSCE",REG_DWORD,1
@UsefulAGKHelper I see that you are using the newer version of GImageX 2.2.0 on Win7 host - I use the older version v2 2014 on WinXP 64-bit host but I did now as in the pictures and it works : Most important is only the SKU Flag set to Professional otherwise there is such a message: P.S. The Boot option is not needed (it is probably only needed to create or edit boot.wim) However, I noticed the difference in the size of the files: install.wim edited - 451MB install.wim captured - 473MB 473 - 451 = 22MB I checked the version GImageX 2.2.0 and no difference - the install.wim file still has 473MB
I also tried to capture using dism after the ADK 8.1 installation on Win7 and still install.wim has 473MB Why is the edited install.wim has 22 MB less than captured? I don't understand it Code: C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM>dism /capture-image /compress:maximum /imagefile:D:\Pobieranie\install.wim /capturedir:Y: /name:xp64 Deployment Image Servicing and Management tool Version: 6.3.9600.17029 Saving image [==========================100.0%==========================] The operation completed successfully.
@Gelip Now that I have two computers, how do I use WinDBG to debug my laptop (target pc) through USB with my desktop (debugger pc)?