http://bugs.winehq.org/show_bug.cgi?id=11960
--- Comment #5 from Lei Zhang thestig@google.com 2008-03-10 15:03:17 --- (In reply to comment #4)
(In reply to comment #3)
can you run:
WINEDEBUG=+exec,+winebrowser wine legacy_app_name.exe > legacy_log.txt 2>&1
and attach legacy_log.txt to this bug report?
I entered WINEDEBUG=+exec,+winebrowser wine "c:\Legacy\legacy.exe" > legacy_log.txt 2>&1 which I presume is what you wanted. Legacy launched, I produced the web pages and confirmed I wished to view them in my browser, and a log was produced, but did not seem to have anything significant - just a bunch of 'fixme's, so I engaged brain.
From what I remember, the way Wine launches an external web browser is through
shellexec and winebrowser. Maybe legacy is doing it differently, which would explain why those logs came up empty.
Now, I have been using my **linux** browsers (inc. Konqueror as I indicated) and I realised this might be a problem, even though Legacy could launch them and access the Legacy site.
So I installed IE in wine and am now able to browse the web pages OK.
Did you install ies4linux? We can't support that BTW.
However, it still is not possible to check for updates from Legacy - it just times out. I've just checked on XP and it responds immediately. I did mention this as a possible problem in my initial bug. On the same dialog box used to check for updates, there is a link to 'See what's new' and that works as expected. Should I raise it as a separate bug, please?
Allan
Yes, please file a separate bug. There's been some wininet issues lately.
BTW, is this the website for the program? http://www.legacyfamilytree.com/