I think his goal was simply to display it on the screen for his users, so they can easily deliver that information without knowing much about linux. It is a notable request.<br><br>Think of a "powered by wine" logo in the upper right hand corner. I will help him, as a software developer to distinguish what clients are running wine, and what wine versions they are having their issues with.<br>
<br>I don't think Cedric is trying to code Wine-version-specific work-arounds.<br><br>-Tres<br><br><div class="gmail_quote">On Mon, Feb 11, 2008 at 8:43 AM, L. Rahyen <<a href="mailto:research@science.su">research@science.su</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Monday February 11 2008 10:59:40 C�dric MARCOUX (sprimont) wrote:<br>
> Hi all,<br>
><br>
> i'm currently writing Win32 application under Delphi.<br>
> I do all possible to get it compatible with wine.<br>
> For design purpose I have made a little check to know in my application<br>
> is run under wine or not.<br>
> I just make a registry test to know if wine registries entry exist or<br>
> not and it work fine.<br>
> If exist I display a nice tux logo inside my appz :)<br>
><br>
> However, I was wondering if there is a way to get from my emulated<br>
> application the version of wine that host it?<br>
<br>
</div> By definition, if you are trying to detect WINE and this is successful - this<br>
is a bug. And there is no warranty that registry key you are testing doesn't<br>
exist on Windows or exist on WINE (at least user can create it by hand in<br>
Windows registry or remove it in WINE registry; or after some time it might<br>
be changed/removed in WINE registry).<br>
If there is any bugs, please report them at <a href="http://bugs.winehq.org" target="_blank">http://bugs.winehq.org</a> .<br>
If you decide to keep WINE-detection at least provide documented command-line<br>
keys to disable it. For example, I saw one application that tries to detect<br>
WINE and if this is successful it changes its behavior in some places and I<br>
prefer to disable that because modern WINE works much better that at the time<br>
the program (and its WINE-related workarounds) was created.<br>
In other words, any attempt to detect WINE, or, even worse, its version, is<br>
strongly discouraged practice (because relying on such a thing means relying<br>
on bugs).<br>
If you *really* require some workarounds ASAP, then you can give a user to<br>
choose (either in menu/options dialog or at first startup) does he/she use<br>
WINE or not - but this is also discouraged practice.<br>
Don't forget to report a bug if you found one!<br>
<div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
wine-users mailing list<br>
<a href="mailto:wine-users@winehq.org">wine-users@winehq.org</a><br>
<a href="http://www.winehq.org/mailman/listinfo/wine-users" target="_blank">http://www.winehq.org/mailman/listinfo/wine-users</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>- <a href="mailto:Tres.Finocchiaro@gmail.com">Tres.Finocchiaro@gmail.com</a>