Hi Andre,
>> Entry Pt Ordn Name
>> 00012900 1 VSTPluginMain
>> 00012900 2 main
>
> so with:
>> 0042:Call KERNEL32.GetProcAddress(18000,7f77bb3950b0 "VSTPluginMain")
>> ret=7f77bb394182
>> 0042:Ret KERNEL32.GetProcAddress() retval=180012900 ret=7f77bb394182
>
> it looks as exp
Am 01.04.2013 20:28, schrieb jordan:
> Hi Andre,
>
>>> Can anyone offer any help / advice on how to determine / confirm that
>>> address returned by GetProcAddress is correct in our test64.exe??
>>
>> I doubt that's the problem, but to really confirm it i'd need a:
>> winedump -j export yourvst.dl
Hi Andre,
>> Can anyone offer any help / advice on how to determine / confirm that
>> address returned by GetProcAddress is correct in our test64.exe??
>
> I doubt that's the problem, but to really confirm it i'd need a:
> winedump -j export yourvst.dll
Okay, I am trying to load Automation.dll wi
Am 01.04.2013 19:56, schrieb jordan:
> Can anyone offer any help / advice on how to determine / confirm that
> address returned by GetProcAddress is correct in our test64.exe??
I doubt that's the problem, but to really confirm it i'd need a:
winedump -j export yourvst.dll
Hi Daniel
> This is a little off-topic from the original thread, but I think 64-bit Wine
> works pretty well. Our ArcGIS Server > on Linux is exclusively 64-bit and is
> in use by some large organizations.
..and those 'large organizations' are not the only one's out there
using Wine64. ;)
I t
> probably Wine's 64-bit support, since that's a little-used feature).
>
This is a little off-topic from the original thread, but I think 64-bit Wine
works pretty well. Our ArcGIS Server on Linux is exclusively 64-bit and is in
use by some large organizations
Hey Vincent,
First thank you for your input :)
On Mon, Apr 1, 2013 at 11:57 AM, Vincent Povirk wrote:
> Given that Wine uses winelib for its builtin exe's and dll's, and that
> the way it works is not much different from a PE exe or dll, I don't
> think winelib is likely to be at fault here. My
Given that Wine uses winelib for its builtin exe's and dll's, and that
the way it works is not much different from a PE exe or dll, I don't
think winelib is likely to be at fault here. My guess is that you are
running into an ordinary Wine bug relating to your specific dll (and
probably Wine's 64-b
Hi list.
A friend of mine and myself, have been exploring expanding a (currently,
32bit only) winelib app to support 64bit plugins in wine (64). The app is
called FSThost, which is used to host win32 VST instruments and effects
(.dll) as a standalone app in Gnu/linux. Webpage:
http://sourceforge.n
