From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Probable seamless bug: can't pop es
Date: Mon, 15 Oct 2001 17:11:25 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805343@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805337@msgid-missing>
>>>>> On Sun, 14 Oct 2001 12:35:54 -0600, n0ano@indstorage.com said:
Don> Short answer: Yes, the GDTD was set up wrong, here's the patch
Don> to fix this. (I must be getting better, it only took me a
Don> weekend to find the single bit that had to change rather than
Don> my typical effort of over a week :-) We were neglecting to set
Don> the present bit, an obvious no-no.
Ah, yes, indeed. Good catch!
Don> Long answer: I'm amazed we've gotten as far as we have with
Don> this bug. ANY attempt by an IA32 program to load a segment
Don> register from the GDT would cause a fault. The only reason we
Don> have worked up to now is that the IA64 code sets up all of the
Don> segment descriptors manually without reference to the GDT and
Don> very few protected mode IA32 programs attempt to load any of
Don> the segment registers.
Don> Also, there is a non-zero change that this will fix the problem
Don> with Wine trying to run certain programs, you might want to try
Don> TurboTax again with this fix in.
I tried it and TurboTax does start up now! It's still pretty crash
happy (e.g., "View Forms" kills it), but it's still impressive to
watch it.
Does anyone know how well TurboTax works with WINE on a real x86
machine? Does it work without a full windows installation?
Perhaps more significantly, this apparently also was the bug that kept
x86 abiword from working.
Thanks,
--david
prev parent reply other threads:[~2001-10-15 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 0:19 [Linux-ia64] Probable seamless bug: can't pop es Robboy, David G
2001-10-12 1:11 ` David Mosberger
2001-10-14 18:35 ` n0ano
2001-10-15 17:11 ` David Mosberger [this message]
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=marc-linux-ia64-105590698805343@msgid-missing \
--to=davidm@hpl.hp.com \
--cc=linux-ia64@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