if we are not allown to use undoc struct or api then this project is dead. for example how ms open the directx hal interface and what value to put into ntgdidd* to accpect the call is as well undoc. it was huge test and error and ms directdraw driver interface are some part undoc by ms. same with some gdi32 calls.
we must be allown to implement undoc api command and struct
I am not so good to type letters. I hope everyone understand what I mean
----- Original Message ----- From: "Thomas Weidenmueller" w3seek@reactos.com To: "ReactOS Development List" ros-dev@reactos.org Sent: den 31 January 2006 11:50 Subject: Re: [ros-dev] Undocumented APIs
Ge van Geldorp wrote:
- Should this be limited to APIs or include undocumented data
structures
too? An example I ran into last night: KPRCB. We know it's out there,
some
of the fields are listed (e.g. by Probert) but I couldn't find any "official" documentation.
That's going to be a huge problem because there's not just the KPRCB. A lot of structures are incompletely documented or not documented at all. But they exist and most driver developers know that...
- Thomas
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev