FlameOnion

I ran into same or similar issues with old ati cards in win 98 vm qemu as ruthan wrote on winraid forum: I created an issue on gitlab qemu related to segfault when using x-vga=on on old ati gpu x550. It happened if the vbios had "BAR0: 32 bit, BAR1: I/O" (lspci -vv) and someone made a fix. It is not in the qemu release, I had to build from source. (I have an ati x600 with a vbios that has BAR0: 32 bit, BAR1: I/O and another x600 that has BAR0: 64 bit, BAR4: I/O). There were no segfault issues with old ati gpus that have " BAR0: 64 bit, BAR4: I/O", but those old ati gpus x600, x700, x800 that I have, have " BAR0: 64 bit, BAR4: I/O" , have the issue that the driver does not load in win98, when desktop appears it says there is a problem with the display and it prompts me to set the resolution/color every time, if I change the resolution or number of colors, it prompts to restart, I hit ok and it stays at 'restarting windows'. I created an issue on gitlab qemu, no fix yet. Here are the issues: https://gitlab.com/qemu-project/qemu/-/issues/2856 https://gitlab.com/qemu-project/qemu/-/issues/2866

As info, I saw a little box(4k hdmi edid emulator) that have multiple switchable profiles. Also, to add to that "DVI cable mod", using arduino with multiple EDID eeprom to switch between them using COM port from PC with appropriate program in a .bat file(as a launcher for programs with different settings)

Replicated the same error with qemu using OVMF with csm (uefi bios) edk2.git-ovmf-x64-0-20200422.1378.ge54310451f.noarch.rpm

AMISCE - change hidden bios settings for AMI bioses Export the bios settings from both versions and try to compare the files with notepad++ or online text compare.

2020.txt_20201.txt.zip Who wants to sort and compare bios Setup changes from version 2020 to version 2021.Extracted from bios files. https://github.com/serdeliuk/VirtualBiosMod https://github.com/BoringBoredom/UEFI-Editor

Installed softice(I don't know how to use it).Thought maybe it can give some hint or an idea. After I press C to continue, "Vcache protection error" appears

disabled cores, downclocked to 2ghz, downclocked ram and increased timings, disabled lan, sound, sata controller, tpm, used less than 2gb partition fat, fat32, same. Booted from usb, same(on h87 it worked booting from sata and usb stick) Bootlog works. It stops at "[000EB590] DEVICEINIT = VCACHE "

Tried with 16gb(same as h87) and it was the same. With DEVICE=HIMEMX.EXE /MAX=64M, [386Enh] SysVMEMSLimit=2048 MaxPhysPage=40000 [vcache] MaxFileCache=344064 same mem(dos7.1 version) DEVICE=HIMEMX.EXE /MAX=64M Memory Type Total = Used + Free ---------------- -------- -------- -------- Conventional 624K 59K 565K Upper 0K 0K 0K Reserved 0K 0K 0K Extended (XMS) 65,535K 3K 65,532K ---------------- -------- -------- -------- Total memory 66,159K 62K 66,097K Total under 1Mb 624K 59K 565K Total Extended (XMS) 65,535K (67,107,840 bytes) Free Extended (XMS) 65,532K (67,104,768 bytes) Largest executable program size 565K (578,288 bytes) Largest free upper memory block 0K (0 bytes) Available space in High Memory Area 1K (608 bytes) MS-DOS is resident in the high memory area.

Tried Xmgr.sys, HIMEM.SYS /NUMHANDLES=64, HIMEMX.EXE , HIMEMX.EXE /NOABOVE16 /X /X2MAX32, it is the same.

the h87 had 4 4gb sticks, 1060(gtx 1060)

Is there a way to debug this? a way to trace and exclude memory with emm? On h87 with an i5 it worked(vdd protection error fixed by removing the 1060, and using igpu or ati x600).On z690 it does not work.I don't reach vdd protection error( I get vcache protection error).I can reach vdd protection error and pass it(with ati x600) if I boot with step by step and don't load ifshlp.vxd, but later I get blue screen vfat error with normal boot, safe mode, ends at "[00142D3F] DEVICEINIT = VCACHE" (I have 32gb ram, removed 1 stick and it was the same.Saw a video with a russian getting the same vcache protection error on z390, he then used an adapter and 2gb ddr4 sodimm and it was the same)