[ros-dev] Undocumented APIs

James Tabor jimtabor at adsl-64-217-116-74.dsl.hstntx.swbell.net
Wed Feb 1 02:26:14 CET 2006

Magnus Olsen wrote:
> Then accoring  "2. There exists a third party driver/application using the
> behavior" then we can  remove whole pnp, directx, win32k, rpc, network, usb
> and more. alot of api is undoc or is wrong. WHat we have left no reactos
> and I agesnt it. alot of manufactor using undoc api in lowlevel and u need
> implement it right.  and I do not like we have vote on it. let us work on
> how to implement stuff as we have always done.
Wine is starting to fall into this trap too. If this policy goes into place
we will have to write up documents for these unknown apis and explain what
they do. Eventually we will publish M$ api for them w/o M$ giving it to the EU.

Well PnP, we have good source and 3rd party drivers using our interface to
install drivers from 3rd party vendors. The INF files are readable right?

Win32k, we can show and demonstrate the unknown apis with books and point to
locations in those books that those api functions do exist and we use them in
different ways.

The rest is the same. We have demonstrated with ReactOS that these unknown apis
exist and are used in one form or another with drivers and applications. We
have in our original source code to prove this even in a court. All we have to
do is document the apis. Yuck more work!

Get my point!

> other wise we can never achive
> the goal
> "ReactOS aims to achieve complete binary compatibility with both
> applications and device drivers"
Yes we are loosing focus.

More information about the Ros-dev mailing list