No subject


Tue Aug 30 17:20:58 CDT 2005


[snip]
< 0806a488:Call kernel32.CreateFileA(7f875000
"\\\\.\\VNETBIOS",c0000000,00000003,00000000,00000003,00000080,00000000)
ret=7f8710a6
[snip]
< 0806a488:Call
kernel32.DeviceIoControl(00000070,00000100,405f193c,00000040,00000000,000000
00,00000000,00000000) ret=7f871b0d
< fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device
VNETBIOS
< 0806a488:Ret  kernel32.DeviceIoControl() retval=00000000 ret=7f871b0d
[snip]
< 0806a488:RET  netbios.6: _Netbios(405f193c) retval = 00000000 ret=7f9c1026
< 0806a488:RET  netapi32.1: Netbios(405f193c) retval = 00000000 ret=1001de6e

Good. It seems to work exactly the way I thought (or rather hoped) it would.

Now we can presumably forget about the VxD and the undocumented NETBIOS DLL
and concentrate on implementing the documented NETAPI32 DLL.

It would be intresting to know what the content of NCB structure that
Netbios takes as pointer to as argument.

So the next step would be to make a Wine implementation of the NETAPI32.DLL
with a stub with an appropriate TRACE to display to NCB structure.

I don't think I have time do it is the next few days though.
Can somebody else please do it?

PS. On second thought perhaps we should make the NETAPI32.DLL just a forward
to the NETBIOS.DLL. It seems from the trace above that the Netbios function
in NETAPI32.DLL is the same function as _Netbios in NETAPI32.DLL and Netbios
is the only  function in NETAPI32 while NETBIOS have more functions
eventhough
they are AFAIK undocumented.




More information about the wine-devel mailing list