Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
RDTSC GPF's in V86 mode on AMD K6
7 views
Skip to first unread message
julian...@my-deja.com
Nov 2, 1999, 3:00:00 AM11/2/99
to
Does anyone know why I'm getting a GPF using RDTSC on an AMD K6 in V86
mode? The disabling bit in CR4 is not set and the fault does not seem
to occur in either real or protected modes. I've tried this on both a
K6 200MHz and a K6-2 450MHz, with the same results. Of course, the
problem can be fixed under WINDOWS using a VXD to trap the fault(though
I'm not sure how to deal with it under a memory manager in DOS mode),
but why does it happen in the first place?
mode? The disabling bit in CR4 is not set and the fault does not seem
to occur in either real or protected modes. I've tried this on both a
K6 200MHz and a K6-2 450MHz, with the same results. Of course, the
problem can be fixed under WINDOWS using a VXD to trap the fault(though
I'm not sure how to deal with it under a memory manager in DOS mode),
but why does it happen in the first place?
Sent via Deja.com http://www.deja.com/
Before you buy.
Robert Zanatta
Nov 6, 1999, 3:00:00 AM11/6/99
to
This call is invalid in V86 mode - should cause an invalid op code fault.
julian...@my-deja.com wrote in article <7vn5gm$66q$1...@nnrp1.deja.com>...
Tim Roberts
Nov 9, 1999, 3:00:00 AM11/9/99
to
>julian...@my-deja.com wrote in article <7vn5gm$66q$1...@nnrp1.deja.com>...
>> Does anyone know why I'm getting a GPF using RDTSC on an AMD K6 in V86
>> mode? The disabling bit in CR4 is not set and the fault does not seem
>> to occur in either real or protected modes. I've tried this on both a
>> K6 200MHz and a K6-2 450MHz, with the same results. Of course, the
>> problem can be fixed under WINDOWS using a VXD to trap the fault(though
>> I'm not sure how to deal with it under a memory manager in DOS mode),
>> but why does it happen in the first place?
>> Does anyone know why I'm getting a GPF using RDTSC on an AMD K6 in V86
>> mode? The disabling bit in CR4 is not set and the fault does not seem
>> to occur in either real or protected modes. I've tried this on both a
>> K6 200MHz and a K6-2 450MHz, with the same results. Of course, the
>> problem can be fixed under WINDOWS using a VXD to trap the fault(though
>> I'm not sure how to deal with it under a memory manager in DOS mode),
>> but why does it happen in the first place?
"Robert Zanatta" <rzan...@absolute.com> wrote:
>
>This call is invalid in V86 mode - should cause an invalid op code fault.
Is this K6 specific? RDTSC works perfectly well from a V86 app in Windows
NT on my PentiumPro.
--
- Tim Roberts, ti...@probo.com
Providenza & Boekelheide, Inc.
0 new messages