+1 from me.
On 07/08/13 15:03, Rosanne DiMesio wrote:
On Wed, 07 Aug 2013 14:23:53 +0100 Ken Sharp kennybobs@o2.co.uk wrote:
Would I be right in assuming you would like to see bugs in 32-bit applications that are only present in a wow64 WINEPREFIX? Are there many?
Yes. As to how many there are, I've been able to find 7 by doing searches of summaries/comments for things like "wow64" and "64" and then reading the bugs to see if they fit, but since people have such wildly varying ways of phrasing things, I don't know if that's all of them. I have seen it often enough on the forum that I now routinely tell 64 bit users to try a 32 bit wineprefix and have added instructions on how to create one to the FAQ. That's why I'd like an easier way to track these bugs.
I see. A lot of people say this over and over again.
+1 from me for a wow64 keyword. They may even be fairly easy to solve (picking the right paths / registry entries).
As to keyword usage, some of those bugs were tagged with the win64 keyword, some weren't. I know there is also a win32 keyword, and perhaps that is meant to be used for the kinds of bugs I am looking for, but if so, that is not at all clear from the keyword definition, and it is not how people are using the keywords.
There's no win32 keyword?
On Wed, Aug 7, 2013 at 4:30 PM, Ken Sharp kennybobs@o2.co.uk wrote:
+1 from me.
On 07/08/13 15:03, Rosanne DiMesio wrote:
As to keyword usage, some of those bugs were tagged with the win64 keyword, some weren't. I know there is also a win32 keyword, and perhaps that is meant to be used for the kinds of bugs I am looking for, but if so, that is not at all clear from the keyword definition, and it is not how people are using the keywords.
There's no win32 keyword?
There's no win32 keyword ; only win16 and win64
There wouldn't be any use anyway since it would be the default
Frédéric Delanoy
On Wed, 7 Aug 2013 21:07:29 +0200 Frédéric Delanoy frederic.delanoy@gmail.com wrote:
There's no win32 keyword ; only win16 and win64
There wouldn't be any use anyway since it would be the default
I know; Ken pointed that out. I think I misread win16. Clearly I should not post before having coffee.