From: Brad Parker <1819289@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1819289] Re: Windows 95 and Windows 98 will not install or run
Date: Wed, 21 Aug 2019 03:42:04 -0000 [thread overview]
Message-ID: <156635892465.26559.12940677354754486239.malone@soybean.canonical.com> (raw)
In-Reply-To: 155216177409.9624.16357609956497374456.malonedeb@gac.canonical.com
Just finished a bisect between cfcca36 (working) and current master (not
working), here is the result:
$ git bisect bad
cd1bfd5ef336166b275a09dc9842542bf5e63ae3 is the first bad commit
commit cd1bfd5ef336166b275a09dc9842542bf5e63ae3
Author: Gerd Hoffmann <kraxel@redhat.com>
Date: Wed Jun 20 12:17:34 2018 +0200
seabios: update bios and vgabios binaries
Adds two new vgabios binaries, for ramfb and bochs-display.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
pc-bios/bios-256k.bin | Bin 262144 -> 262144 bytes
pc-bios/bios.bin | Bin 131072 -> 131072 bytes
pc-bios/vgabios-bochs-display.bin | Bin 0 -> 27648 bytes
pc-bios/vgabios-cirrus.bin | Bin 38400 -> 38400 bytes
pc-bios/vgabios-qxl.bin | Bin 38912 -> 38912 bytes
pc-bios/vgabios-ramfb.bin | Bin 0 -> 28160 bytes
pc-bios/vgabios-stdvga.bin | Bin 38912 -> 38912 bytes
pc-bios/vgabios-virtio.bin | Bin 38912 -> 38912 bytes
pc-bios/vgabios-vmware.bin | Bin 38912 -> 38912 bytes
pc-bios/vgabios.bin | Bin 38400 -> 38400 bytes
10 files changed, 0 insertions(+), 0 deletions(-)
create mode 100644 pc-bios/vgabios-bochs-display.bin
create mode 100644 pc-bios/vgabios-ramfb.bin
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1819289
Title:
Windows 95 and Windows 98 will not install or run
Status in QEMU:
New
Bug description:
The last version of QEMU I have been able to run Windows 95 or Windows
98 on was 2.7 or 2.8. Recent versions since then even up to 3.1 will
either not install or will not run 95 or 98 at all. I have tried every
combination of options like isapc or no isapc, cpu pentium or cpu as
486. Tried different memory configurations, but they just don't work
anymore.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1819289/+subscriptions
next prev parent reply other threads:[~2019-08-21 3:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 20:02 [Qemu-devel] [Bug 1819289] [NEW] Windows 95 and Windows 98 will not install or run John M
2019-08-17 21:27 ` [Qemu-devel] [Bug 1819289] " Brad Parker
2019-08-19 17:26 ` Brad Parker
2019-08-19 17:55 ` Philippe Mathieu-Daudé
2019-08-19 18:20 ` Brad Parker
2019-08-20 0:21 ` Brad Parker
2019-08-20 9:08 ` Dr. David Alan Gilbert
2019-08-20 16:45 ` Brad Parker
2019-08-20 16:55 ` Peter Maydell
2019-08-20 21:05 ` Brad Parker
2019-08-20 21:43 ` Brad Parker
2019-08-20 22:31 ` Aleksandar Markovic
2019-08-21 13:59 ` Maxim Levitsky
2019-08-21 3:42 ` Brad Parker [this message]
2019-08-21 12:53 ` Brad Parker
2019-08-21 13:48 ` Philippe Mathieu-Daudé
2019-08-22 0:02 ` Philippe Mathieu-Daudé
2019-08-22 1:14 ` Brad Parker
2020-02-10 17:21 ` John M
2021-03-29 5:54 ` Thomas Huth
2021-08-27 17:26 ` Philippe Mathieu-Daudé
2021-08-29 17:07 ` Thomas Huth
2021-08-30 8:59 ` Philippe Mathieu-Daudé
2023-09-21 16:26 ` John M
2023-09-22 7:16 ` Michael Tokarev
2023-09-22 10:33 ` Michael Tokarev
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-all 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=156635892465.26559.12940677354754486239.malone@soybean.canonical.com \
--to=1819289@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).