🚀 go-pugleaf

Hi,

"Daniel Pfeffer" <pfefferd@hotmail.co.il> wrote:
>I still stand by my assertion that doing this is a Bad Thing.

May be you still stand on your assertion because do not saw 
source code of winio? Winio it is not only dll it's include 
sys driver that is provide access to physical memory and 
hardware ports. 

>What prevents
>two different applications that must both access the same physical memory
>from corrupting each other's data? Some sort of system-level driver is
>necessary in order to ensure no problems.

And Winio uses common DDK way for it. 
Most drivers do it operation with physical memory.

DDK is not something monolithic, with good base theory.
Microsoft puts groups of functions in DDK because thinks 
that it should be in DDK. Or because they still not ready 
put it in SDK.
 Even function belong to DDK it is not mean that it 
impossible to use it in normal application.
Many program pearls based on it.

And I never say about writing or not writing drivers via 
Winio. In my previous letter I answered on question that 
I put in the begin of letter. May be you do not see it?
Reread my message.

I absolutely sure that for working with complex devices the
driver is obligatory thing.
But I also sure that in easy cases it possible to do 
via way that I read before. I sure that many DDK 
function is very useful for normal applications.
And here I stand.

Vladimir.