From: trannks@gmail.com
To: devel@edk2.groups.io
Subject: Issue OVMF + CSM(seabios), while booting win98: "While initializing device VCACHE: Windows protection error. You need to restart your computer."
Date: Wed, 21 Jun 2023 08:17:44 -0700 [thread overview]
Message-ID: <uiyU.1687360664716653986.ULyI@groups.io> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1595 bytes --]
On some UEFI bioses(modern hardware) there is a issue when booting win98: "While initializing device VCACHE:
Windows protection error. You need to restart your computer."
There is this person that has BIOSTAR X470GTA(ryzen) that can boot win98 with bios version 2020(X47BG721.BST). But with bios version 2021(X47BG223.BST) he gets Vcache protection error when trying to boot win98. He rolled back to bios version 2020 and Win98 booted successfully again.
I thought to try to boot win98 in qemu with UEFI+CMS(OVMF+SeaBios) and it happened that I received the same error. I installed bootice(I don't know assembly), on real hardware and in QEMU, both stop at VCACHE: **0028:C03819A6 MOV [EDX+00000100],EAX**
QEMU(64mb ram) OVMF with csm (uefi bios) edk2.git-ovmf-x64-0-20200422.1378.ge54310451f.noarch.rpm( same when building the latest OVMF + CSM):
When building and using seabios.bin(standalone)there is no issue with vcache.
So maybe its a problem with seabios when configured as csm16 module and or with OVMF?
VCACHE is a 32-bit driver disk cache in Windows 9x running in Protected Mode
https://fd.lod.bz/rbil/interrup/windows/20_vx048b.html
Win9x boot process:
http://www.iselfschooling.com/aplus/BootProcessWin9x.htm
There are a bunch of people who run win98 on modern hardware, but on some UEFI(CSM enabled) there is this issue with vcache.(it is not the amount of ram, and there are workaround and patches to limit win98 ram to low values ex 512mb ram). So if issue can be identified and fixed in OVMF+CSM maybe it can give ways to deal with it on real hardware.
[-- Attachment #1.2: Type: text/html, Size: 3141 bytes --]
[-- Attachment #2: 244766149-f0480401-ffe7-4a6f-a629-1a61041bbe2b.jpg --]
[-- Type: image/jpeg, Size: 90420 bytes --]
[-- Attachment #3: 244766218-9de8c104-7195-4a9c-8b67-4bd4f975bb89.png --]
[-- Type: image/png, Size: 110069 bytes --]
reply other threads:[~2023-06-21 15:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uiyU.1687360664716653986.ULyI@groups.io \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox