http://bugs.winehq.org/show_bug.cgi?id=15094
--- Comment #11 from Louis Lenders xerox_xerox2000@yahoo.co.uk 2008-09-04 16:16:00 --- (In reply to comment #10)
(In reply to comment #8)
Hi, could you attach console output when that error happens?
Also, as it seems to be a vb-app, maybe using native oleaut32 is worth a shot
(just run with WINEDLLOVERRIDES="oleaut32=n" wine SafelogAA.exe (or what was the executable called again? i forgot name of executable)
Yeah that oleaut32 thing didn't work, the program wouldn't start. And I attached the last few lines of the terminal when getting the error (I think that's what you wanted anyway). The "FNInvoke did not find member id -514" error is what comes up dozens of times when I get the spot where it starts malfunctioning.
Could you describe what exactly is malfunctioning: is there an error -messagebox coming up, or does it just exit silently?
As for the last part from your log: it looks like it fails to fire up winebrowser, that's a known bug , but it looks like there's a workaround (from another bug report:)
Quote: "I've had the same issue/error message launching URL's from Forte Agent - however, appended a "%1" to HKEY_CLASSES_ROOT\http\shell\open\command and now launches OK."
Could you try that too ( open regedit , and navigate to HKEY_CLASSES_ROOT\http\shell\open\command , and append %1 so C:\windows\system32\winebrowser.exe -nohome "%1"
If that doesn;t fix the bug, i guess it must be some bug wine's oleaut32