2011/2/2 Qian Hong <fracting@gmail.com>
Dear Nikolay and James,

On Sun, Jan 30, 2011 at 11:09 PM, James McKenzie
<jjmckenzie51@earthlink.net> wrote:
> Qian:
>
> I would like to echo Nikolay's comment and add one more:
>
> Please search through the Bug Reports before submitting a new one.

I really feel very sorry, I apologize for posting such issues the
wrong place and making noise. Thank you for your reminder and your
nice work on wine.
I have searched the Bugzilla with ntoskrnl.exe as keyword carefully,
it seems that none of the current bugs mentions unimplemented function
ntoskrnl.exe.IoGetDeviceInterfaces, so I report a new issue here:
http://bugs.winehq.org/show_bug.cgi?id=25964
Wish it not a duplicate.

>
> You might receive more assistance on the Wine User list as well.  Most of
> the developers lurk there.
>

I'll post such mails on the Wine User list from now on.
However, may I modestly consults below questions here:

1. If  a function is implemented in wine dll as a stup, then usually
this function won't cause crash,
and the wine debug will output  "fix:me ...stup" rather then
"Unimplemented function", is it right?
2. If a function is listed in the Wine API guide,
http://source.winehq.org/WineAPI/ , and marked as stup,
then this function must be implemented as a stup in  wine source code,
is it right?

I've read http://wiki.winehq.org/DebugChannels and
http://wiki.winehq.org/Developers-Hints,
but I still have some confusion.


Thanks a lot!


> Thank you.
>




--
Regards,
Qian Hong
-
Sent from Ubuntu
http://www.ubuntu.com/


Yes, a stub is a first step to implement a function. Sometimes a stub is enough for the application to proceed.
WineAPI is parsed from wine code, so if it says "stub" in the spec file of that dll it means there is no implementation yet, and a stub can be produced.