qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
To: Bug 1819289 <1819289@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1819289] Re: Windows 95 and Windows 98 will not install or run
Date: Wed, 21 Aug 2019 00:31:21 +0200	[thread overview]
Message-ID: <CAL1e-=gp6ZEP8GeseG9hPJbP7=ma4+GkV7RLrV8ttqQvnUQJxA@mail.gmail.com> (raw)
In-Reply-To: <156633742863.16769.2783105280357246181.malone@wampee.canonical.com>

20.08.2019. 23.56, "Brad Parker" <1819289@bugs.launchpad.net> је написао/ла:
>
> So it looks like even though that commit fixed it, it seems to break
> again (differently) in 3.0.0, so I'll need to do another bisect between
> cfcca36 and v3.0.0 then I guess. And keep working my way up to master as
> well.
>
> --

At least you will have an interesting debugging story to tell afterwards. I
wish you luck!

Aleksandar

> 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
>

  reply	other threads:[~2019-08-20 22:32 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 [this message]
2019-08-21 13:59     ` Maxim Levitsky
2019-08-21  3:42 ` Brad Parker
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='CAL1e-=gp6ZEP8GeseG9hPJbP7=ma4+GkV7RLrV8ttqQvnUQJxA@mail.gmail.com' \
    --to=aleksandar.m.mail@gmail.com \
    --cc=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).