From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: Using Linux+dosemu to install Windows
Date: Fri, 26 Jul 2002 20:47:26 +0400 [thread overview]
Message-ID: <3D417D1E.50902@yahoo.com> (raw)
Hello.
Patrick J. LoPresti wrote:
>> /usr/src/linux/arch/i386/kernel/vm86.c The attached patch must be a
>> good start for fixing the problem.
> Ah, so the problem is that the kernel's emulation does not account for
> multiple prefix bytes?
Yep, that was the problem.
> Will you submit your patch to Alan Cox? It would be nice to get this
> fixed in the long run.
Yes, I'll try to submit this one.
> One more thing. How precise should the emuluation be?
Hmm, 100%? :)
> The popfd instruction should not modify the VM or RF bits. (Not to
> mention any bits which are reserved in the current revision of the
> CPU.) Or does the kernel already take care of these concerns?
Yes, see how the thread.v86mask gets
initialised in do_sys_vm86().
> I believe clearing those flags is a bad idea. They are both used
> routinely to detect the CPU version:
I agree:(
The only good thing here is that the
amount of progs that works on 486 but
not on 386 is very minor...
> I suggest removing the BUG: stuff from the dosemu source code, then
> figuring out what the real problem is and fixing it properly.
This was suggested several times before
but still noone figured out the real
problem so all that suggestions failed.
> What do you think?
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.
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.
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.
next reply other threads:[~2002-07-26 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 16:47 Stas Sergeev [this message]
[not found] ` <mit.lcs.mail.linux-msdos/3D417D1E.50902@yahoo.com>
2002-07-27 15:02 ` Using Linux+dosemu to install Windows Patrick J. LoPresti
-- 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=3D417D1E.50902@yahoo.com \
--to=stssppnn@yahoo.com \
--cc=linux-msdos@vger.kernel.org \
--cc=stas.orel@mailcity.com \
/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