Hi All,
I would have asked this question on the wine-devel list but winehq made it quite clear that list was not for user questions but for developer use only so I ask it here.
Hmm..., normally I do the list moderation, and I cannot imagine that I would have rejected this.
I am attempting to run a native windows VB6 app (United Devices) in wine, fake windows, and continue to encounter an unimplemented API "CreateRemoteThread" call to kernel32 error using any and all RH distro kernels using any wine version. I was simply wondering as to when that API call might be implemented. I am in the process of filing a bug report to winehq in the hopes an engineer will be motivated to take it on so here is what my investigation has shown to date.
The function appears to be properly declared in winbase.h (wine of course) as is the already implemented function 'CreateThread' along with the structure type SECURITY_ATTRIBUTES common to both calls. The kernel32.spec file shows CreateRemoteThread apparently stubbed "@ stub CreateRemoteThread" but the implemented CreateThread shows "@ stdcall CreateThread (ptr long ptr long long ptr)".
I wish I knew C and patch submission procedure as I would gladly volunteer to work on this one but I only know some VB and am attempting to code this call in a simple VB6 procedure to replicate the error and, if sucessful, will provide the exe and source to winehq.
The patch submission is easy. But looking at the function description, it would appear to require some detailed knowledge of the way things work, rather than just a knowledge of C.
Just my personal view here... There is generally no "schedule" for implementing functions. For something like this, it generally means that someone who actually wants to use the application, and with the detailed knowledge required to fix it, be motivated to take it on. Unfortunately, I suspect few have the needed skill set (certainly it is way beyond my weak understanding of how things work). If you are just an individual, that kind of means you are stuck. For a company, there is of course always the option to pay someone to fix it.
_______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
