wine-devel September 2010

wine-devel@winehq.org

116 participants
356 discussions

RE: Problem with getting account at testbot
by Greg Geldorp 12 Sep '10

12 Sep '10

Hi Mariusz, > From: Mariusz Pluciński > > I have a problem with my account at testbot.winehq.org. Long time ago, I > registered my account. To this day I have not received an activation > e-mail. I thought it was maybe rejected, because I was not "well-known > member of the Wine community" that time. > > Today I noticed that I can not send request for account, because "User > already exists". Trying to use "forgotten password" feature gave me > information that my account was not activated. What could I do with > this? I was working on Wine some time without this, but now testbot > account would be very helpful for me. Sorry about that, I must have missed the notification when you first registered. I have now activated your account (you should have received an e-mail about it), just let me know if you still encounter problems. You can either reply directly to this email or use the Feedback link on the website to contact me. Ge.

1 0

Assertion in winebuild
by André Hentschel 12 Sep '10

12 Sep '10

Hi, I run in the assertion in function output_stubs in winebuild/import.c obsiouly not on x86/x86_64, but in my rebased(to a more recent wine tree) ARM build in dlls like msvcp80, msvcp90 and up, but not msvcirt or msvcrt and the normal others like ntdll and so on. So i wonder: - how x86/x86_64 are treated different. (really couldn't trace that down, see below) - what is different with e.g. msvcp80 so that non-x86/x86_64 builds get into the assertion? As i can see it is always called in function BuildSpec32File in spec32.c, so some values seem to be modified on non-x86/x86_64 e.g. odp->type -- Best Regards, André Hentschel

1 0

Problem with geting account at testbot
by Mariusz Pluciński 12 Sep '10

12 Sep '10

Hello I have a problem with my account at testbot.winehq.org. Long time ago, I registered my account. To this day I have not received an activation e-mail. I thought it was maybe rejected, because I was not "well-known member of the Wine community" that time. Today I noticed that I can not send request for account, because "User already exists". Trying to use "forgotten password" feature gave me information that my account was not activated. What could I do with this? I was working on Wine some time without this, but now testbot account would be very helpful for me. Mariusz Pluciński

2 1

Release plans
by Alexandre Julliard 12 Sep '10

12 Sep '10

Folks, There won't be a release this week, since I'll be spending my Friday on an airplane. Release 1.1.44 will be next Friday. If all goes well and I can finish the few remaining bits of 64-bit support, it should be the last release of the 1.1.x series. We'll then enter code freeze and start the 1.2-rc series. The 1.2 final release should thus happen hopefully sometime in June. -- Alexandre Julliard julliard(a)winehq.org

1 0

Macro names instead of numbers in logs
by Florian Köberle 12 Sep '10

12 Sep '10

Hello when running a program using wine it's possible to log +message to get informed about all the messages which get sent. This debug channel displays the macro names like WM_NOTIFY instead of numbers. The most other debug channels and the regression tests however display numbers. Functions like SPY_GetMsgName which can make window messages more human readable can be found in dlls/user32/spy.c. Is there a acceptable way of making functions like SPY_GetMsgName available to other libraries and tests? There are about 80 TRACE/trace lines which could be improved: egrep "trace.*hwnd.*lParam" dlls/ -R -i -I|grep -v user32|wc Best regards, Florian

5 10

Keeping people from trying iTunes in Wine?
by Dan Kegel 11 Sep '10

11 Sep '10

Watching Twitter, one fairly frequently seems people trying and failing to run iTunes 10 and the like in Wine. Should we let them bash their heads against the wall like that? Maybe we should detect the top ten apps that don't work with Wine, and put up a warning dialog saying they are known not to work, and people shouldn't try. (Kind of like what Windows 7 does when you do something dangerous, e.g. try to look at the contents of drive C:.)

15 19

Re: [PATCH 2/3] wined3d: store amount of video memory in gpu_description_table
by Rico Schüller 11 Sep '10

11 Sep '10

Am 11.09.2010 03:59, schrieb Roderick Colenbrander: > /* Geforce 300 midend mobile (Geforce GT 325M/330M use the same core) */ > if (strstr(gl_renderer, "GT 325M") > || strstr(gl_renderer, "GT 330M")) > { > - *vidmem = 1024; > - return CARD_NVIDIA_GEFORCE_GT325M; > + return CARD_NVIDIA_GEFORCE_GT325M; > } > > /* Geforce 200 - midend */ > if (strstr(gl_renderer, "GT 240")) > { > - *vidmem = 512; > return CARD_NVIDIA_GEFORCE_GT240; > } > > /* Geforce 200 lowend */ > if (strstr(gl_renderer, "GT 220")) > { > - *vidmem = 512; /* The GT 220 has 512-1024MB */ > return CARD_NVIDIA_GEFORCE_GT220; > } > /* Geforce 200 lowend (Geforce 305/310 use the same core) */ > @@ -1461,7 +1459,6 @@ static enum wined3d_pci_device select_card_nvidia_binary(const struct wined3d_gl > || strstr(gl_renderer, "Geforce 305") > || strstr(gl_renderer, "Geforce 310")) > { > - *vidmem = 512; > return CARD_NVIDIA_GEFORCE_210; > } > > Hi Roderick, you probably might fix the whitespaces for all occurrences. Cheers Rico

1 0

Does testbot's MingW miscompile winmm:midi tests?
by Joerg-Cyril.Hoehle＠t-systems.com 11 Sep '10

11 Sep '10

Hi, on test.winehq, WinME systems always report 8 rc=MMSYSERR_INVALPARAM errors. However, when running a MSVC compiled binary (as found in testbot job #4990), no such error occurs. Paul Vriens wrote: >I only see those 8 errors with the winetest executable from >test.winehq.org. My own cross-compiled version is fine, no errors there. Likewise, Octavian Voicu's machines saw no failure with the MSVC binary, but constantly produce red color on testbot. This could - Either be a bug in testbot's MingW (compilation or includes)? What's the difference between testbot compilation and Paul Vriens'? - Some weird memory corruption affecting only WinME? - a bug in my tests? Those INVALPARAM errors happen since May. However my May-19 patch did not change the tests that since fail, so it must be a side effect of something else. 1. dwBytesRecorded is left uninitialised, which may produce random results -- if it were used. 2. dwOffset is now set to 0xDEADBEEF; previously uninitialised. Yet that does not explain why MSVC's and Paul's cross compiled binary succeed. Paul and I found a bug in the mingw includes once. Perhaps that's another instance? How to proceed from here? Jörg Höhle

3 4

Re: msxml3: Implement property SelectionNamespaces for XPath (try #2)
by testbot＠testbot.winehq.org 10 Sep '10

10 Sep '10

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=5183 Your paranoid android. === W98SE (32 bit domdoc) === domdoc.c:6044: Test failed: failed to create CLSID_DOMDocument instance: 0x80040154 === WNT4WSSP6 (32 bit domdoc) === domdoc.c:6044: Test failed: failed to create CLSID_DOMDocument instance: 0x80040154 === W2KPROSP4 (32 bit domdoc) === domdoc.c:6044: Test failed: failed to create CLSID_DOMDocument instance: 0x80040154

1 0

Re: [PATCH] Fixed a couple of cases where the console was not reset in cooked mode after a bare console has been created
by Juan Lang 10 Sep '10

10 Sep '10

Hi Eric, minor quibble on this patch: #ifdef HAVE_TERMIOS_H # include <termios.h> #endif +#ifdef HAVE_TERMIOS_H +#include <termios.h> +#endif This hunk isn't needed. --Juan

1 0

← Newer
1
...
19
20
21
22
23
24
25
...
36
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel September 2010