Q: Unimplemented control 256 for VxD device VNETBIOS

[Patrik Stridvall]

>     Michael> I'm looking forward for any hints.
> 
> These FLEX LMs are always a problem.
> 
> I guess, the license isn't bind to a physical dongle on the parallel
> port. So one can conclude that the software tries to read the 
> MAC. This
> probably happens in a NETBIOS.DLL call which then probably calls the
> NETBIOS.VXD.  I propose you run with --debugmsg 
> +relay,+snoop,+vxd and try
> to decipher what is going on before that failing VXD call. In 
> the easiest
> approach, you can build a fake builtin NETBIOS DLL, with the 
> appropriate
> function returning the MAC in the first approach hardcoded or 
> really reading
> it with OS calls.
> 
> If running with --debugmsg +snoop crashes, I have a hack that may help
> there. I have also patches for an empty NETBIOS dll.

Why haven't you submitted it?

Did Alexandre reject it?

Having empty version of a standard DLL is almost always useful.
Of course Wine should be configured to use the native DLL
in the first place but still.

> However I guess that this probably isn't enough to make FLEX LM happy.

It is worth trying as well. However NETBIOS.DLL is not documented
like NETAPI32 AFAIK is so it is more likely that it calls NETAPI32.

Also note the NETAPI32 imports the NETBIOS.DLL function _Netbios so
it would be a little strange if the application called NETBIOS directly
but you never know. :-)

Oh, well. Only one way to find out. Please do as Uwe suggest and run
wine with --debugmsg +relay,+snoop,+vxd and post the result.