http://bugs.winehq.org/show_bug.cgi?id=21601
--- Comment #6 from Kenneth Robinette support@securenetterm.com 2010-02-05 18:58:28 --- (In reply to comment #5)
(In reply to comment #4)
(In reply to comment #3)
Closing.
I don't think its a duplicate, however if thats what you want to believe, so be it.
Bug 13891 is about the start command, which uses ShellExecuteEx to open files.
Its really two problems, however I have a workaround which enables my stuff to work with the current wine releases.
Bug 13891 states that its a registry problem which can be fixed by editing the registry and adding a %1 to HKEY_CLASSES_ROOT\http\shell\open\command.
This works if ShellExecute() is called from an ansi application, but not from unicode based applications. The suggested patch to change main.c of winebrowser does not work either in this case.
When you do add %1 to the HKEY_CLASSES_ROOT\http\shell\open\command, and do a ShellExecute() from a unicode application, winebrowser does start and display the url, but you also get an error message stating "The DDE transaction could not be completed because other DDE transactions were being processed".
The workaround is to do a ShellExecute() passing the program to start as "winebrowser" with the URL as an argument. This works with both ansi and unicode applications. This of course requires a run time detection of wine in order to use the proper ShellExecute.
At least our applications can run correctly on all versions of Wine until the proper fix is made to Wine itself.