Content Type
Profiles
Forums
Events
Posts posted by reboot12
-
-
1 hour ago, Dietmar said:
On CSM-enabled boards, the firmware gives you a tiny real-mode stub (the “thunk”) or leaves paging/PE bits clear so you can drop back to real mode.
I test CSMWrap in virt-manager QEMU KVM virtual machine with 2016 OVMF UEFI 64-bit firmware OVMF_CODE-pure-efi.fd
There are other firmware versions in the edk2-ovmf-x64-20160418gita8c39ba-1.mga6.noarch.rpm archive:
The OVMF_CODE-with-csm.fd version includes SeaBIOS for Legacy support:
https://github.com/tianocore/tianocore.github.io/wiki/OVMFQuoteSome of these builds include a seabios CSM and can boot non-UEFI “legacy” operating systems. (Note: seabios is GPLv3 licensed.)
Can you check if in OVMF_CODE-pure-efi.fd give real-mode "thunk"?
https://www.mediafire.com/file/ezj7uzxix2mgs68/ovmf_x64_pure&CSM.zip/file.fd files can be opened in UEFITool
0 -
Have you tried running CSMWrap from SATA FAT32 partition instead USB? For me xHCI controler is problematic on Haswell motherboard and CSMWrap work OK only if:
- no any connected USB stick to USB port
- run UEFI Shell from SATA disk from FAT32 partition from EFI\Boot\bootx64.efi
- run CSMWrap from UEFI Shell
https://github.com/FlyGoat/csmwrap/issues/14#issuecomment-2907598008
0 -
You probably spreading misinformation - FlyGoat cannot create an account on MSFN and asked me to put such a post here:
I guess they (or maybe LLM behind them) never really understood how the project work. There is NO interrupt handler redirection happening to UEFI code, but it doesn't mean int13h (and other interrupt calls) won't work. They are handled by SeaBIOS.
For misinformation in their comments:
1. No Real-Mode Environment
SeaBIOS is executing in Real Mode.
2. No Legacy BIOS ROM Code
SeaBIOS is Legacy BIOS ROM Code.
3. No IVT Vector Patching
SeaBIOS will fill IVT table, no need to do any patching.
4. No Mode-Switch Plumbing
x86thunk in CSMWrap and SeaBIOS are doing all mode switch works.
5. UEFI’s Native Disk Interface Differs Completely
Yes, that's why SeaBIOS's own disk drivers are operating after handling control to CSM module. It's talking to hardware directly.
For the int13h handler flow, the IVT vector is set at ivt_init() https://github.com/FlyGoat/seabios-csmwrap/blob/efafa7514862b2caf082329e29dd8878dfe1d63d/src/post.c#L33, which set IVT to an assembly thunk handler, and redirected to actual handle function handle_13(struct bregs *regs) https://github.com/FlyGoat/seabios-csmwrap/blob/efafa7514862b2caf082329e29dd8878dfe1d63d/src/disk.c#L741.
They also tried to provide some code that will never work in this project, PLEASE, look into current implementation, we are not even using EDK II build environment. If in doubt, they can always ask me.
Original github post: https://github.com/FlyGoat/csmwrap/issues/14#issuecomment-2903984783
0 -
Disconnect all USB flash drive from USB port and run CSMWrap from FAT32 partition on SATA disk - best using UEFI Shell.
I use UEFI Shell 1.0, CSMWrap.efi efafa75-CSMWrap-34ee5ec0 -
1 hour ago, GD 2W10 said:
How do I fix this?
Boot to UEFI Shell, then run CSMWrap from shell - it works
https://github.com/FlyGoat/csmwrap/issues/14#issuecomment-29068662410 -
-
I test this build and now AHCI works on Asus H61 (Sandy Bridge)
(test winload.exe because ntldr not works with iGPU)
https://github.com/FlyGoat/csmwrap/actions/runs/15173994519
On Asus B85 (Haswell) other problem and don't detect any boot devices - stuck on:
SeaBIOS (version efafa75-CSMWrap-34ee5ec)
Version 1.2.0 not works with AHCI on Asus H61
0 -
8 hours ago, Dietmar said:
I think, even in the new 1.2 version of the csmwraper there is no INT13h support,
No, CSMWrap support all BIOS services:
QuoteThe truth is all BIOS interrupt service, including INT13h are always handled by SeaBIOS which is a part of CSMWrap. If there is any problem on recognising boot device, it might be caused by this issue, or ARL's PCI issue, or maybe another SeaBIOS driver issue.
https://github.com/FlyGoat/csmwrap/issues/14#issuecomment-2899365096
0 -
6 hours ago, sonyu said:
So... maybe there is a change to boot X64 Windows in non-UEFI mode in UEFI32 baytrail?
Yes of course. You need use CSMWrap ia32 32-bit version:
P.S. I purposely bought such a laptop - Asus T100TAF for testing but I bricked it when I changed the hidden settings in CMOS - I need reprogramming bios - probably need desolder SPI chip:
https://www.elektroda.pl/rtvforum/topic4120094.htmlMy tests before CSMWrap was released: https://forums.mydigitallife.net/threads/winxp-32-bit-on-a-modern-pc-iso-boot-wim-install-wim.88834/#post-1873937
Many laptops with UEFI32 have an eMMC drive - I don't know if there will be a problem with that. If the laptop has a normal SATA drive it should be OK.
Do you still have Lenovo Flex 10 with UEFI32?
0 -
WinXP 32-bit also works on UEFI32 if use CSMWrap e820 ia32 version
https://github.com/FlyGoat/csmwrap/issues/22#issuecomment-2895690281
0 -
-
Test this build: https://github.com/FlyGoat/csmwrap/actions/runs/15122472115
Memory Remap Enabled, Asus H61 SandyBridge, PCIe AMD6450 VBIOS AMD from this card:
WinXP SP2 32-bit - ntldr+NTDETECT.COM > 0K low memory:
https://github.com/FlyGoat/csmwrap/issues/7#issuecomment-2892732313
Same WinXP but Longhorn 5472 winload.exe loader boot but on screen stuck aurora bootscreen:
Screenshot over Remote Desktop:
P.S. If remove PCIe card and use iGPU then VBIOS is SeaVGABIOS
0 -
You still don't read previous posts. Don't you have forum notifications turned on?
Instead of hack your bios try first debugging CSMWrap through the COM port:
https://msfn.org/board/topic/186793-csmwrap-boot-csm-on-uefi-only-systems/page/3/#findComment-12801330 -
Please make own topic e.g. How unlock Memory Remap option in bios
Your posts are irrelevant to the this topic CSMWrap !!!
0 -
2 hours ago, Dietmar said:
Then I use RU.efi UEFI variable, Setup
But at Offset =272 there stands a 53, what cant be at all.
Make screenshot. Maybe try other UEFI Setup variable, maybe wrong offset. Setup often have more than 1 page (Ctrl+PageDown in ru.efi)
P.S. I know how to debug CSMWrap through the COM port:
https://github.com/FlyGoat/csmwrap/issues/140 -
No, You need run AMISCE tool for your platform or newer with /d option in UEFI Shell then generate CMOS settings to .txt file:
sceefi64 /d /o /s CMOS.txt
As I remember correctly I already explained to you recently (about unlock CSM in yours Intel Gen12 mobo) and I think I even sent for you AMISCE tool.
Yes, I found in topic Compiling ACPI v2.0... https://msfn.org/board/topic/183464-compiling-acpi-v20-driver-for-windows-xp-sp3-and-windows-2003-sp2-x32x64/page/133/#findComment-1266974
0 -
If you have AMI bios then you can generate all CMOS setting also hidden using AMISCE tool
0 -
But I do not need change remap on this way because I have normal option in CMOS Setup:
I can also change this with ru.efi in the UEFI Setup variable at the appropriate offset:
Setup Question = Memory Remap Token =2E3 // Do NOT change this line Offset =33B Width =01 BIOS Default =[01]Enabled Options =*[01]Enabled // Move "*" to the desired Option [00]Disabled
0 -
Sorry, I don't understand what I need to test?
0 -
7 minutes ago, Dietmar said:
Yepp, the error screen for winload.exe is exact as yours above.
This means that CSMWrap works on your Asrock Z370 board.
8 minutes ago, Dietmar said:Have you tested ntldr boot of XP SP3?
On Asus H61 ntldr not work but on AIMB-768 WinXP 64-bit from NVMe disk work with ntldr.
For high framebuffer I have no idea - You can create a issue on github: https://github.com/FlyGoat/csmwrap/issues
0 -
F..k, why don't you read the previous posts?
3 hours ago, Dietmar said:and this version on winload.exe crashes
What crash - like this?
Sorry, I forgot to write that you need to correct 2 entries in BCD - ApplicationDevice and OSDevice:
P.S. CSMWrap support AHCI and works OK on virt-manager:
On real hardware - Asus H61 AHCI not work (SeaBIOS detect only USB stick) and I need change to IDE in CMOS setup so that SeaBIOS can detect the HDD:
AHCI:IDE:
0 -
3 minutes ago, Dietmar said:
But I see 4 times the same screen and this version on winload.exe crashes
Screenshot please
0 -
Test, test, test and noticed that CSMWrap works differently on each machine or does not work:
- virt-manager - wrapper work, XP32 need Longhorn 5472 loader - tested AMD6450 driver but probably work also on vga.sys
- Asus H61 (iGPU 2gen) - wrapper work, SATA mode IDE, XP32 need Longhorn 5472 loader and work on vga.sys
- Asus B85 (iGPU 4gen) - wrapper run but stuck on CALL16 - not start SeaBIOS
-
AIMB-786 (CPU 8Gen, PCIe AMD7450) - wrapper work from NVMe MBR disk, SATA mode AHCI, XP64 boot on standard ntldr + NTDETECT.COM Quote
1.0.0
Initial Release!
Booting FreeDOS and Windows XP/7 is possible in QEMU and some physical machines.
Full E820/SMBIOS/ACPI support
0 -
Yeeeeeeaaaaaaaaaaa!!! This works
First time WinXP 32-bit on UEFI 64-bit using CSMWrap 1.1.0
virt-manager QEMU on Debian 9, OVMF_CODE-pure-efi.fd 64-bit 2016, passthrough PCIe AMD6450 graphics card (drivers installed), bootmgr + winload.exe 5472 x86 (patched) + BCD
Virtual graphics card VGA - stuck on aurora boot screen but WinXP work on AMD 6450:
Test on real hardware Asus H61 iGPU - works in safe mode in 800x600 on vga.sys - GUID 23A set to 800x600 60Hz
If change GUID 23A to e.g. 3840x2160 1Hz then safe mode work in 1024x768:
1
CSMwrap - boot CSM on UEFI only systems.
in Windows XP
Posted · Edited by reboot12
But CSMWrap.efi works OK on this UEFI64 firmware (works also 32-bit version OVMF 32-bit):
https://msfn.org/board/topic/186793-csmwrap-boot-csm-on-uefi-only-systems/#findComment-1280103
How do you explain it?