Alberto,
Yaps, I can see that . However, Linux / BSD has accees to those only like a
consequence of the fact its open src. So , basically, anyone can do any
insane thing calling any API, even private ones, if they very slightly
modify kernel sources (or sometimes directly, they are a bit less
restrictive than NT, I agree). Like a engineer which wants to control
sometimes as much as possible of the OS state I would love NT beeing open
src, and with an API giving direct access to anything. Like a user, I would
be not. Most likely, it would result in 1001 flawed drivers and flawed
designs on the market. I really dont need engineers fascinated by “Im the
god of OS”… If I have to choose between those two, then a rigid API is
the way to go for me. Not to mention that I strongly beleive in closed
source, altough , paradoxally, I encourage ppl to employee reverse
engineering techniques where its legal to gain a better picture of OS
internals and a deeper understanding of things. I think I stay between the
heretic and the blindly beleiver. Of course , all in the spirit of DMCA 
Ciao, dan
----- Original Message -----
From: “Moreira, Alberto”
To: “NT Developers Interest List”
Sent: Tuesday, August 06, 2002 12:36 AM
Subject: [ntdev] RE: Using Local APIC as a better method than modifyin g the
IDT
> Actually, NT display drivers are the closest to what I’d call a “Kernel
> Module”.
>
> What I mean is a piece of software that (1) adds functionality to the OS,
> (2) has access to the hardware, and (3) does not depend on PnP or WDM
> structures or even entry point organization. All one needs is a
DriverEntry
> and a DrvEscape, like the good old OpenGL ICD I worked with. Timing and
> performance measurement is an obvious application, there are others.
>
>
> Alberto.
>
>
>
> -----Original Message-----
> From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
> Sent: Monday, August 05, 2002 5:05 PM
> To: NT Developers Interest List
> Subject: [ntdev] RE: Using Local APIC as a better method than modifyin g
> the IDT
>
>
> > about time you guys give us mechanisms to implement Kernel Modules,
> not just
> > device drivers.
>
> I suspect “device drivers” is just how “kernel modules” are called in
> NT.
>
> Max
>
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@compuware.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
>
> The contents of this e-mail are intended for the named addressee only. It
> contains information that may be confidential. Unless you are the named
> addressee or an authorized designee, you may not copy or use it, or
disclose
> it to anyone else. If you received it in error please notify us
immediately
> and then destroy it.
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@rdsor.ro
> To unsubscribe send a blank email to %%email.unsub%%
>