public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: "Patrick J. LoPresti" <patl@curl.com>
To: linux-msdos@vger.kernel.org
Subject: Re: Using Linux+dosemu to install Windows
Date: 27 Jul 2002 11:02:18 -0400	[thread overview]
Message-ID: <s5g4reljjt1.fsf@egghead.curl.com> (raw)
In-Reply-To: <mit.lcs.mail.linux-msdos/3D417D1E.50902@yahoo.com>

Stas Sergeev <stssppnn@yahoo.com> writes:

> I agree:(
> The only good thing here is that the amount of progs that works on
> 486 but not on 386 is very minor...

But how annoying when you run into one :-).

> Currently the "BUG" cannot be removed.  Just set the $_cpu=(80486)
> and try to run FoxPro after removing the "BUG" from dpmi.c and
> sigsegv.c (there are 3 places where the AC gets cleared) and it will
> crash.

Couldn't you just tell people to use $_cpu=(80386) as a workaround?
That would have the side-effect of protecting the AC bit, wouldn't it?

Or, if that is too extreme, you could have a configuration option to
specifically protect those bits.

> Furthermore somehow it happens that if the signal was received while
> AC is set, dosemu itself executes with AC set and crashs somewhere
> in glibc functions due to exception 0x11.

Is that not a bug in the emulator design?  I mean, shouldn't *all* of
the emulator's state be isolated from the emulated machine's?

I am sorry for asking so many stupid questions; I do not fully
understand the vm86 design (yet).

> If you can find the roots of the problem, the "BUG" will be removed,
> thats for sure...  My guess is that the problem is somewhere in the
> kernel/vm86() because when CPU-emu is used, the "BUG" doesn't
> occure.

I am not sure I have time to debug FoxPro...  But I do have time to
create a patch to allow people to enable the BUG: code from
dosemu.conf.  Would you accept such a patch?

 - Pat

  parent reply	other threads:[~2002-07-27 15:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-26 16:47 Using Linux+dosemu to install Windows Stas Sergeev
     [not found] ` <mit.lcs.mail.linux-msdos/3D417D1E.50902@yahoo.com>
2002-07-27 15:02   ` Patrick J. LoPresti [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-28  7:09 Stas Sergeev
2002-07-27 21:10 Stas Sergeev
2002-07-27 22:11 ` Bart Oldeman
2002-07-26 14:02 Stas Sergeev
     [not found] ` <mit.lcs.mail.linux-msdos/3D41566B.5030903@yahoo.com>
2002-07-26 16:06   ` Patrick J. LoPresti
2002-07-26  3:50 Patrick J. LoPresti

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=s5g4reljjt1.fsf@egghead.curl.com \
    --to=patl@curl.com \
    --cc=linux-msdos@vger.kernel.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