Have you tried installing the latest version of Oracle VM VirtualBox? I see that you are using the old version.
Actually I am using Latest version. It has been on this screen for 3 hours now. It only says 25 minutes. And it does not continue.
I thought you might help you try not to add the EMB2009 update, I'll have to work more time. Because Thailand is now being hit by more expensive electricity prices. Hello from Thailand, my house is still at night, please leave your message.
@George King Since we don't know which driver causes Windows 7 to load on uefi, we need to try take each safe-mode driver from windows 7 to windows xp to gain uefi support on xp. And yes, I mounted Windows 7 system hive from mounted windows 7 vhd (dual-booted on real hardware) using serviwin. I know the file (mssmbios.sys) from XP doesn't work to provide UEFI support, so I wonder if windows 7's ported mssmbios.sys will work to boot windows xp from pure UEFI on modern hardware If the ported file mssmbios.sys (from windows 7) still doesn't work to boot from uefi on XP on modern hardware, we shall try the other safe-boot files as well.
@diderius6 I was wondering if you or George King can debug XP2ESD XP installation (after extracting install.wim into XP drive using XP2ESD setup) on UEFI class 3 from modern hardware (8th core+) using debugger while LAN/serial connected from another computer? I am asking this because I have may figured from seeing your mounting tech photos (diderius' setup) that you have an advanced setup with multiple hardwares, parts, computers etc, I know XP x64 cannot work on UEFI mode without csm on coffee lake and higher hardware because we don't know what files it needs in order to boot from any uefi hardware properly. Windows 7 has uefi support so I was wondering if George King can find these necessary files in order to make this to work. The problem is that it's impossible to see the BSOD when booting XP on uefi from winload 16497 so we don't know what firmware driver files may be needed to be backported from windows 7 to windows xp (in order to allow windows xp to boot just like windows 7 would on uefi) without debugging. And that's where you came in. 1. So on a clean modern csm-free hardware, basically try to complete the WinPE part of XP2ESD setup as usual and shut down the machine. And before attempting to boot the installation, plug the hardware on a working computer and open efi BCD file using bcdedit/bootice to make debugger enabled, set debugger type to serial (or lan/network etc), and baud rate 115200 (or your baud rate from WinDBG), I assume you already know this but I just wanted to be specific so others can understand. 2. When the debugging is done, the Windbg log should be sent here (as usual) in a compressed archive (7z, zip etc). 3. @George King If when diderius' Windbg log gets published, you found problematic files or more errors than usual, then the obvious solution would be to replace those files with ported files from windows 7 safe-mode section (windows 7's minimal or network section on regedit). 4. If nothing works as expected with just one file then we shall repeat with the other files while keeping the ported file present. When these backported files are done, please send me the files in Conversations so I can try them on my only functional pure-uefi laptop (this is why I asked you guys to debug from your multiple hardware setups, I only have only one working laptop). Anyway, I apologize if I sound patronizing but I wanted to say what I meant so it's much easier to comprehend. You guys should try your best to make this work. If even with windows 7 safe-mode files, windows xp doesn't boot, then attempt with Windows 8 (6.2) safe-mode files. If this finally works, then potential UEFI support can be added to XP from XP2ESD.
Well, take your time with the code as much as you need then. No need to rush with the release, especially when I pointed out the problems I mentioned earlier.
Can you help me to make install.wim file manually? "CaptureVHD" I have WinXP.VHD. How do I make it install.wim. I'm mounting with OSFMount. For example to the "G" drive. How can I do after that? Code: C:\Windows\System32>C:\XP2ESD\apps\7z\x64\7z.exe x C:\XP2ESD\auto-sysprep\WinXP\WinXP.vhd -oC:\asdasdasd -y 7-Zip 19.00 (x64) : Copyright (c) 1999-2018 Igor Pavlov : 2019-02-21 Scanning the drive for archives: 1 file, 2582246912 bytes (2463 MiB) Extracting archive: C:\XP2ESD\auto-sysprep\WinXP\WinXP.vhd 0.ntfs WARNINGS: There are data after the end of archive -- Path = C:\XP2ESD\auto-sysprep\WinXP\WinXP.vhd Type = VHD Physical Size = 2582246912 Offset = 0 Created = 2022-09-20 03:48:17 Cluster Size = 2097152 Method = Dynamic Creator Application = vbox 6.1 Host OS = Windows Saved State = - ID = 8F533912AD43FB4A999ED261D3B4654E ---- Size = 10737418240 Packed Size = 2581594112 Created = 2022-09-20 03:48:17 -- Path = WinXP.mbr Type = MBR Physical Size = 10737418240 ---- Path = 0.ntfs Size = 10725732864 File System = NTFS Offset = 32256 Primary = + Begin CHS = 0-1-1 End CHS = 1023-254-63 -- Path = 0.ntfs Type = NTFS WARNINGS: There are data after the end of archive Physical Size = 10725732352 Tail Size = 512 File System = NTFS 3.1 Cluster Size = 4096 Sector Size = 512 Record Size = 1024 Created = 2022-09-20 09:49:23 ID = 12407453189377409894 Everything is Ok Archives with Warnings: 1 Warnings: 1 Folders: 1666 Files: 13073 Alternate Streams: 3 Alternate Streams Size: 3285480 Size: 4052735886 Compressed: 2582246912
@rulman TRK creation was tested and works. Read first post carefully and you will succed. Dont use CaptureVHD, its mentioned in first post too, its outdated now and it must be updated. Manualy created images will never work in 99% cases