Mail Archives: djgpp/1998/04/22/07:15:36
Charles Sandmann (sandmann AT clio DOT rice DOT edu) wrote:
> It is technically a bug in cwsdpr0.exe - but one that is known about,
> documented, and left that way for a good reason. You will see the
> same problem with PMODE.
Oh, didn't know that.
> If ring-0 access is all that is needed, you can use the create descriptor
> functions to provide ring 0 call gates or interrupts, lock your memory, etc
> to provide your own protected mode "kernel" functions with the standard
> CWSDPMI.
I just noticed it and thought I should ask whether it was a bug. I
really don't need it.
> cwsdpr0 was never planned to be a general purpose replacement for cwsdpmi.
> It was written for id Software to allow using the pentium profiling
> instructions during development. If anyone finds it useful for more than
> that, great - but it's really not something I want to support.
If I ask again, will this be a FAQ? :-)
--
Groeten, Michel. http://www.cs.vu.nl/~mdruiter
____________
\ /====\ / "You know, Beavis, you need things that suck,
\/ \/ to have things that are cool", Butt-Head.
- Raw text -