[EMAIL PROTECTED] wrote:
Thanks for the helpful replies.



I have been working on the Winelib approach
suggested by Jeremy. As my first step I wanted to get a windows console 
application
to compile and run anyway.



I now have an executable that runs and calls
functions in the windows dll, but it does not work correctly. If I run it
with winedbg it gives me a backtrace with errors coming from deep inside the
dll. I assume there is some problem with the arguments going to the function
that serves as the entry to the dll. Is there a way to find out what is getting
passed to the dll and/or debugging inside the dll (without source code)?



Can you open the DLL from a very simple standard Windows EXE with Wine?

If that doesn't work, there is probably something within the DLL that Wine can
not handle, yet.

// Jakob



Reply via email to