February 2012 - Wine-Devel - list.winehq.org

Re: [PATCH 2/2] winealsa.drv: Optionally load extra ALSA device names from the registry
by Alexandre Julliard Feb. 14, 2012

Feb. 14, 2012

Andrew Eikum <aeikum(a)codeweavers.com> writes: > + while(*p){ > + if(alsa_try_open(p, stream)){ > + if(ids && keys){ > + len = MultiByteToWideChar(CP_UNIXCP, 0, p, -1, NULL, 0); > + ids[*num] = HeapAlloc(GetProcessHeap(), 0, len * sizeof(WCHAR)); > + MultiByteToWideChar(CP_UNIXCP, 0, p, -1, ids[*num], len); The registry is stored in Unicode, the conversion should be the other way around. -- Alexandre Julliard julliard(a)winehq.org

1 0

Windows-on-Arm won't support win32
by Dan Kegel Feb. 14, 2012

Feb. 14, 2012

According to http://www.zdnet.com/blog/perlow/the-long-kiss-goodbye-for-x86-desktop-wind… Microsoft is not letting developers use win32 on arm (although Microsoft is probably using it themselves for Office on arm). Instead, native apps have to use WinRT, a C++-based class library. According to http://en.wikipedia.org/wiki/Windows_Runtime, the WinRT libraries are built on top of win32 internally. If it takes off, and someone feels like supporting it in Wine, they would probably have to start by implementing the first bits in C like wine's msvcp support. Eventually, if and when llvm gets Visual C++ ABI support, maybe wine could start allowing C++ source code. (FWIW, I see Charles Davis was working on that, http://code.google.com/p/google-summer-of-code-2010-llvm/updates/list http://lists.cs.uiuc.edu/pipermail/cfe-dev/2011-March/014305.html https://llvm.org/viewvc/llvm-project/cfe/trunk/lib/CodeGen/MicrosoftCXXABI.… ).

4 6

Wine Gecko 1.5-beta1
by Jacek Caban Feb. 13, 2012

Feb. 13, 2012

Hi all, It's time for another Gecko update. I've uploaded builds to SourceForge [1], so anyone willing to test it may grab an MSI file from there and apply the attached patch to Wine. Mozilla releases Firefox 11, which this package is based on, in four weeks. The plan is to do Wine Gecko release a bit later (and, obviously, not sooner than Wine 1.4 release). Any help with testing will be appreciated! Thanks, Jacek [1] http://sourceforge.net/projects/wine/files/Wine%20Gecko/1.5-beta1/

1 0

Re: gdi32: rebuild the internal SystemLink every time.
by Alexandre Julliard Feb. 13, 2012

Feb. 13, 2012

Aric Stewart <aric(a)codeweavers.com> writes: > Our registry or settings may have changed since initial start, > especially on prefix creation, so rebuilg the internal system link > each time. I don't think you can do that. Other processes may be reading or writing the keys at the same time. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: msxml3: Use debugstr_a() to trace
by Alexandre Julliard Feb. 13, 2012

Feb. 13, 2012

Nikolay Sivov <nsivov(a)codeweavers.com> writes: > This fixes printf overflow in error callback that I get sometimes with > Outlook 2010, patch also changes a couple of similar cases. > > That's safe enough to include now. Apparently not... ../../../tools/runtest -q -P wine -M msxml3.dll -T ../../.. -p msxml3_test.exe.so domdoc.c && touch domdoc.ok wine_dbg_vprintf: debugstr buffer overflow (contents: 'err:msxml:doparse "XML declaration allowed only at the start of the document\n""XML declaration allowed only at the start of the document\n""XML declaration allowed only at the start of the document\n""XML declaration allowed only at the start of the document\n""XML declaration allowed only at the start of the document\n""XML declaration allowed only at the start of the document\n""XML declaration allowed only at the start of the document\n""XML declaration allowed only at the start of the document\n""XML declaration allowed only at the start of the document\n""XML declaration allowed only at the start of the document\n""XML declaration allowed only at the start of the document\n""XML declaration allowed only at the start of the document\n""XML declaration allowed only at the start of the document\n""XML declaration allowed only at the start of the document\n""XML declaration allowed only at the start of the document\n""XML declaration allowed only at the start of the document\n""XML declaration allowed only') wine: Assertion failed at address 0x68000822 (thread 0009), starting debugger... -- Alexandre Julliard julliard(a)winehq.org

1 0

half transparent window titles?
by Joerg-Cyril.Hoehle＠t-systems.com Feb. 13, 2012

Feb. 13, 2012

Hi, did anyone else notice that since a few weeks, window titles are somehow not refreshed and/or half transparent? I'm typically using virtual desktop mode in Ubuntu Linux. This is observable with winecfg, the "update .wine" requester, winetest as well as Wine's crash dialog. A search for "transparent" found nothing related in bugzilla. Regards, Jörg Höhle

2 1

Re: [PATCH 3/7] ntdll: fix endianness of three fields in DVD_LAYER_DESCRIPTOR (resend)
by Charles Davis Feb. 13, 2012

Feb. 13, 2012

On Feb 10, 2012, at 1:30 PM, Dan Kegel wrote: > --- > dlls/ntdll/cdrom.c | 12 +++++++++--- > 1 files changed, 9 insertions(+), 3 deletions(-) > > diff --git a/dlls/ntdll/cdrom.c b/dlls/ntdll/cdrom.c > index 802782b..6b64203c 100644 > --- a/dlls/ntdll/cdrom.c > +++ b/dlls/ntdll/cdrom.c > @@ -144,6 +144,12 @@ WINE_DEFAULT_DEBUG_CHANNEL(cdrom); > # define CD_FRAMES 75 /* frames per second */ > #endif > > +#ifdef WORDS_BIGENDIAN > +#define GET_BE_DWORD(x) (x) > +#else > +#define GET_BE_DWORD(x) RtlUlongByteSwap(x) > +#endif > + > static const struct iocodexs > { > DWORD code; > @@ -2568,9 +2574,9 @@ static NTSTATUS DVD_ReadStructure(int dev, const DVD_READ_STRUCTURE *structure, > p->Reserved1 = 0; > p->TrackDensity = l->track_density; > p->LinearDensity = l->linear_density; > - p->StartingDataSector = l->start_sector; > - p->EndDataSector = l->end_sector; > - p->EndLayerZeroSector = l->end_sector_l0; > + p->StartingDataSector = GET_BE_DWORD(l->start_sector); > + p->EndDataSector = GET_BE_DWORD(l->end_sector); > + p->EndLayerZeroSector = GET_BE_DWORD(l->end_sector_l0); I don't know about this. To make your original patch work right on Mac, one of the things I had to do was get rid of the OSReadBigInt32() calls that swapped the endianness of the sector fields from big to host. Chip > p->Reserved5 = 0; > p->BCAFlag = l->bca; > p->Reserved6 = 0; > -- > 1.7.9 > > >

2 3

Re: cryptnet/tests: Fix test failures on older NT4
by Marvin Feb. 13, 2012

Feb. 13, 2012

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=16947 Your paranoid android. === WINEBUILD (build) === Make failed

1 0

Re: cryptnet/tests: Fix test failures on older NT4
by Marvin Feb. 13, 2012

Feb. 13, 2012

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=16947 Your paranoid android. === WINEBUILD (build) === Make failed

1 0

Re: cryptnet/tests: Fix test failures on older NT4
by Marvin Feb. 13, 2012

Feb. 13, 2012

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=16947 Your paranoid android. === WINEBUILD (build) === Make failed

1 0

Re: cryptnet/tests: Fix test failures on older NT4
by Marvin Feb. 13, 2012

Feb. 13, 2012

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=16947 Your paranoid android. === WINEBUILD (build) === Make failed

1 0

Re: advapi32/tests: Fix a test failure on older NT4
by Marvin Feb. 13, 2012

Feb. 13, 2012

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=16946 Your paranoid android. === WINEBUILD (build) === Make failed

1 0

Fwd: Google Summer of Code 2012 DEADLINE: 2012-02-27
by Jeremy White Feb. 12, 2012

Feb. 12, 2012

Hi Folks, It's that time of year again - summer of code is going to start up soon. Maarten, you've been coordinating things for us for a while now - are you still game? Would you like help? Anyone else willing to volunteer to help admin the process? Cheers, Jeremy --- Conservancy Projects, I want to draw your attention to the fact that Google's Summer of Code program for 2012 is now accepting applications. Carol Smith wrote at 11:43 (EST) on Saturday: > We're pleased to announce that Google Summer of Code will be happening > for its eighth year this year: > > [1] - http://google-opensource.blogspot.com/2012/02/google-summer-of-code-2012-is… > [2] - http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc20… > [3] - http://www.google-melange.com/gsoc/events/google/gsoc2012 In particular, take a look at [3], which has the calendar for the SoC 2012 program.

6 7

Re: [PATCH 4/7] kernel32/tests: initial tests for cdrom.c (try 2)
by Charles Davis Feb. 10, 2012

Feb. 10, 2012

On Feb 10, 2012, at 1:30 PM, Dan Kegel wrote: > +START_TEST(cdrom) > +{ [...] > + /* GENERIC_WRITE because without it, passthrough doesn't work on win7 */ But with it, you can't open the device at all on Mac. As I explained on bug 29669, the device file only has 0440 access. Chip

1 0

The audio GetPosition dilemma (long)
by Joerg-Cyril.Hoehle＠t-systems.com Feb. 10, 2012

Feb. 10, 2012

Hi, mmdevapi's GetPosition returns "the stream position of the sample that is currently playing through the speakers", says MSDN. This is exactly what apps ought to use that want to synchronize audio & video (lip synchronisation). MSDN's wording about winmm's GetPosition is not exactly the same: "the current playback position of the given waveform-audio output device." However there's no other winmm function that could be used for lip-sync. Tests in winmm/tests/wave.c tend to show that WHDR_DONE notifications are only received after a position corresponding to the written number of bytes has been reached -- IOW the buffer has been played. Now look at winmm's PlaySound and mciwave code: /* make it so that 3 buffers per second are needed */ Both then proceed to play ping pong with two 1/3 second buffers. Every time WHDR_DONE is received, one of the two is empty, refilled and resubmitted using waveOutWrite. Now consider a system such as PulseAudio that wants to buffer 2 seconds of an audio stream internally. That scheme will fail completely. - If WHDR_DONE is based on GetPosition, notifications will only be sent after 2 seconds or an underrun. Neither PlaySound nor MCIWAVE buffer 2 seconds. They continuously hit an underrun as PA signals that it drained the tiny 40ms ALSA buffer we supplied. Is that PlaySound's fault? - If WHDR_DONE is instead based on buffer usage, it could be sent following snd_pcm_write and let PA buffer as much as it wants. But then our wave tests fail if GetPosition returns something like the position currently playing through the speakers, which is 2s late. Should we have GetPosition lie? And suffer loss of lip sync? DSound's GetCurrentPosition suffers from the exact same issue. For instance, playing an audio CD-ROM with mcicda in recent Wine causes constant underruns from DSound when Pulseaudio is involved. What's the root cause of the issue? 15 years ago, the audio HW would likely receive a pointer to the winmm header data and play that. Once played, the buffer was no more needed and returned to the app. Also, there was nothing sitting behind the audio HW causing significant latency (I mean DAC -> electronic -> speaker -> acoustic had latency negligible to the human brain). Equating GetPosition with the sample seen by the DAC was and is reasonable -- ALSA does exactly this with hw:0. DSound's model is that of a circular buffer from which the DAC is fed. No different. These days with mmdevapi, w7 users report a latency of 30-40ms introduced by the native mixer. Native's winmm might account for that in its GetPosition reports. This limit is below the threshold that my mmdevapi tests would notice. It is well below the approximately 100ms that matter to human perception when correlating visible and audible events. Note that native's mixer is the last in an audio graph before the HW. What happens in Linux with Wine? ALSA's dmix is known to introduce some latency as it operates in period-size chunks. However ALSA's periods are typically very small, e.g. 21.333ms and ALSA's dmix is typically connected to hw:0, immediately playing audio to the speakers. There's hardly a difference between audible GetPosition and a buffer position derived from snd_pcm_write (and old Wine mixed the two in the past). The picture looks a lot like with native's mmdevapi mixer. PulseAudio is entirely different. With PA, the wine mixer is no more near the end of the audio graph, rather than in front of a 2 second latency introducing element. A position derived from snd_pcm_write is 2s ahead of the true speaker position. How did we react? winealsa tried: 1. Using a small ALSA buffer so as to signal PA that large latencies are not ok. PA seems to ignore that hint. It still appears to buffer a lot somewhere internally (I've no experience with PA 1.0 or 1.1, please check). Even worse, small ALSA buffers like 40ms increased the risk of underruns and resulted in a worse audio experience to all users of wineALSA, whereas old wine would typically use a 100ms buffer. Small buffers are no issue to native's mixer. It's using "Pro Audio" priority, which is the highest priority on a native system AFAIK. By contrast, Wine is running at normal user priority. 2. Rate-Limiting. We currently believe we are doing it because we write no more than 3 periods at a time. But we're not. Nothing can prevent PA or any other device from filling its 2s buffer over time. It'll eventually do it, just slowly. We can't use our own clock to limit our writes because that would introduce clock skew issues with the audio HW clock. What if it runs faster than the system's interpretation of 48000fps? We can't second-guess the audio HW clock. IOW, we can't win a rate-limiting game. If the back-end signals via snd_pcm_avail that it has space, then we must feed it. Now we know the reason of our troubles. What can we do? 0. Ignore the issue. Equate GetPosition with Released_frames - GetCurrentPadding 1. Consider lip-sync important and strive to support audio & video applications. 2. mmdevapi appears to have a reasonable separation of concerns between buffering and speaker position. Leave as is. (It may happen though that apps built upon the assumption that they are no more than 40ms apart break when latencies like PA's enter the loop. Here it would be interesting to see whether native has some similar situation, like a remote desktop & audio environment). 3. Protect DSound from a too large delta between padding and position. The maximum is given by the DSound primary buffer size, since DSound's circular GetCurrentPosition abstraction breaks down completely should they be further apart. IOW, don't rate limit DSound writes, but lie about the position if the wineXYZ device says it's too far behind. Having this right may fix some of the bugs currently in bugzilla. That way, we'll get lip-sync with back-ends that don't introduce an unbearable latency. And we won't enter an underrun because the driver or the app never wait too much for the position to increase. 3. Protect winmm from a too large delta between padding and position. As there's no buffer limit to guide us, we must introduce an arbitrary one, around 100-200ms. I don't know whether a dynamic limit based on average supplied WHDR buffers would work. Regarding WHDR_DONE, I don't know whether we should then relax the tests. That feels unsafe, because an app may well wait for WHDR_DONE before calling waveOutReset or Close. WHDR_DONE should not come too early, or we may lose trailing sounds. Perhaps we should not delay the position when playing the last buffer in the list. Our winmm/tests/wave.c tests prove nothing more than that: at the end, the position corresponds to the sum of written samples. Perhaps a similar reflection on MS' side explains why in my tests native's mmdevapi GetPosition may stay 17 samples below the sum of written samples with some USB headsets (or is it just a bug in their driver?). 4. Observe the behaviour of libraries that target mmdevapi, winmm and DSound, e.g. OpenAL, XAudio2, bink, smack, SDL, FMOD and learn. Actually, thinking about what may happen to trailing samples in a system that introduces 2s latencies still gives headaches. If we issue snd_pcm_reset prior to snd_pcm_close, sound will be killed for sure. It looks like the device should remain open for some time. This applies to all wineXYZ devices, not just ALSA with PA. Some future OSS device may too introduce unforeseen latencies. Now I'll go and fix winmm as suggested above. Thank you for reading this far, Jörg Höhle

1 0

Re: [PATCH 3/3] ieframe: Added IProvideClassInfo::GetClassInfo tests
by Marvin Feb. 10, 2012

Feb. 10, 2012

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=16906 Your paranoid android. === WNT4WSSP6 (32 bit webbrowser) === webbrowser.c:3189: Test failed: Creating WebBrowser object failed: 80040154 webbrowser.c:3189: Test failed: Creating WebBrowser object failed: 80040154 webbrowser.c:3189: Test failed: Creating WebBrowser object failed: 80040154 webbrowser.c:3189: Test failed: Creating WebBrowser object failed: 80040154 webbrowser.c:3304: Test failed: Creating WebBrowser object failed: 80040154 webbrowser.c:3281: Test failed: Could not get WebBrowserV1 instance: 80040154 webbrowser: unhandled exception c0000005 at 0040A9DE === W2KPROSP4 (32 bit webbrowser) === webbrowser.c:2539: Test failed: expected GetOverridesKeyPath webbrowser.c:2543: Test failed: expected Invoke_SETSECURELOCKICON webbrowser.c:2544: Test failed: expected Invoke_FILEDOWNLOAD webbrowser.c:2153: Test failed: put_Resizable failed: 80004001 webbrowser.c:2154: Test failed: expected Invoke_WINDOWSETRESIZABLE webbrowser.c:2158: Test failed: put_Resizable failed: 80004001 webbrowser.c:2159: Test failed: expected Invoke_WINDOWSETRESIZABLE webbrowser.c:2539: Test failed: expected GetOverridesKeyPath webbrowser.c:2543: Test failed: expected Invoke_SETSECURELOCKICON webbrowser.c:2544: Test failed: expected Invoke_FILEDOWNLOAD webbrowser.c:410: Test failed: unexpected call Exec_SETDOWNLOADSTATE_0 webbrowser.c:2153: Test failed: put_Resizable failed: 80004001 webbrowser.c:2154: Test failed: expected Invoke_WINDOWSETRESIZABLE webbrowser.c:2158: Test failed: put_Resizable failed: 80004001 webbrowser.c:2159: Test failed: expected Invoke_WINDOWSETRESIZABLE webbrowser.c:2539: Test failed: expected GetOverridesKeyPath webbrowser.c:2543: Test failed: expected Invoke_SETSECURELOCKICON webbrowser.c:2544: Test failed: expected Invoke_FILEDOWNLOAD webbrowser.c:469: Test failed: unexpected nCmdID 29 webbrowser.c:1007: Test failed: unexpected call GetContainer webbrowser.c:517: Test failed: unexpected call webbrowser.c:1007: Test failed: unexpected call GetContainer webbrowser.c:517: Test failed: unexpected call webbrowser.c:2702: Test failed: expected Invoke_SETSECURELOCKICON webbrowser.c:2829: Test failed: expected TranslateUrl webbrowser.c:2830: Test failed: expected Invoke_BEFORENAVIGATE2 webbrowser.c:2832: Test failed: expected Invoke_PROPERTYCHANGE webbrowser.c:2838: Test failed: ReadyState = 1, expected 4 webbrowser.c:2648: Test failed: ReadyState = 1, expected 4 webbrowser.c:839: Test failed: unexpected call Invoke_PROPERTYCHANGE webbrowser.c:855: Test failed: unexpected call Invoke_BEFORENAVIGATE2 webbrowser.c:862: Test failed: ReadyState = 1, expected 4 webbrowser.c:614: Test failed: unexpected call Invoke_AMBIENT_USERMODE webbrowser.c:614: Test failed: unexpected call Invoke_AMBIENT_USERMODE webbrowser.c:617: Test failed: unexpected call Invoke_AMBIENT_DLCONTROL webbrowser.c:621: Test failed: unexpected call Invoke_AMBIENT_USERAGENT webbrowser.c:625: Test failed: unexpected call Invoke_AMBIENT_PALETTE webbrowser.c:1557: Test failed: unexpected call GetOptionKeyPath webbrowser.c:359: Test failed: unexpected call QueryStatus_SETPROGRESSTEXT webbrowser.c:839: Test failed: unexpected call Invoke_PROPERTYCHANGE webbrowser.c:839: Test failed: unexpected call Invoke_PROPERTYCHANGE webbrowser.c:839: Test failed: unexpected call Invoke_PROPERTYCHANGE webbrowser.c:839: Test failed: unexpected call Invoke_PROPERTYCHANGE webbrowser.c:469: Test failed: unexpected nCmdID 26 webbrowser.c:469: Test failed: unexpected nCmdID 29 webbrowser.c:1007: Test failed: unexpected call GetContainer webbrowser.c:517: Test failed: unexpected call webbrowser.c:791: Test failed: ReadyState = 1, expected 4 webbrowser.c:1568: Test failed: unexpected call GetDropTarget webbrowser.c:1007: Test failed: unexpected call GetContainer webbrowser.c:517: Test failed: unexpected call webbrowser.c:2702: Test failed: expected Invoke_SETSECURELOCKICON webbrowser.c:3225: Test failed: doc != doc2 webbrowser.c:614: Test failed: unexpected call Invoke_AMBIENT_USERMODE webbrowser.c:614: Test failed: unexpected call Invoke_AMBIENT_USERMODE webbrowser.c:617: Test failed: unexpected call Invoke_AMBIENT_DLCONTROL webbrowser.c:621: Test failed: unexpected call Invoke_AMBIENT_USERAGENT webbrowser.c:625: Test failed: unexpected call Invoke_AMBIENT_PALETTE webbrowser.c:1557: Test failed: unexpected call GetOptionKeyPath webbrowser.c:359: Test failed: unexpected call QueryStatus_SETPROGRESSTEXT webbrowser.c:469: Test failed: unexpected nCmdID 26 webbrowser.c:469: Test failed: unexpected nCmdID 29 webbrowser.c:1007: Test failed: unexpected call GetContainer webbrowser.c:517: Test failed: unexpected call webbrowser.c:1568: Test failed: unexpected call GetDropTarget webbrowser.c:1007: Test failed: unexpected call GetContainer webbrowser.c:517: Test failed: unexpected call webbrowser.c:2695: Test failed: expected TranslateUrl webbrowser.c:2702: Test failed: expected Invoke_SETSECURELOCKICON webbrowser.c:3232: Test failed: doc != doc2 webbrowser.c:614: Test failed: unexpected call Invoke_AMBIENT_USERMODE webbrowser.c:614: Test failed: unexpected call Invoke_AMBIENT_USERMODE webbrowser.c:617: Test failed: unexpected call Invoke_AMBIENT_DLCONTROL webbrowser.c:621: Test failed: unexpected call Invoke_AMBIENT_USERAGENT webbrowser.c:625: Test failed: unexpected call Invoke_AMBIENT_PALETTE webbrowser.c:1557: Test failed: unexpected call GetOptionKeyPath webbrowser.c:359: Test failed: unexpected call QueryStatus_SETPROGRESSTEXT webbrowser.c:469: Test failed: unexpected nCmdID 26 webbrowser.c:469: Test failed: unexpected nCmdID 29 webbrowser.c:1007: Test failed: unexpected call GetContainer webbrowser.c:517: Test failed: unexpected call webbrowser.c:1568: Test failed: unexpected call GetDropTarget webbrowser.c:1007: Test failed: unexpected call GetContainer webbrowser.c:517: Test failed: unexpected call webbrowser.c:2695: Test failed: expected TranslateUrl webbrowser.c:2702: Test failed: expected Invoke_SETSECURELOCKICON webbrowser.c:2829: Test failed: expected TranslateUrl webbrowser.c:2830: Test failed: expected Invoke_BEFORENAVIGATE2 webbrowser.c:2838: Test failed: ReadyState = 1, expected 4 webbrowser.c:2648: Test failed: ReadyState = 1, expected 4 webbrowser.c:855: Test failed: unexpected call Invoke_BEFORENAVIGATE2 webbrowser.c:862: Test failed: ReadyState = 1, expected 4 webbrowser.c:614: Test failed: unexpected call Invoke_AMBIENT_USERMODE webbrowser.c:614: Test failed: unexpected call Invoke_AMBIENT_USERMODE webbrowser.c:617: Test failed: unexpected call Invoke_AMBIENT_DLCONTROL webbrowser.c:621: Test failed: unexpected call Invoke_AMBIENT_USERAGENT webbrowser.c:625: Test failed: unexpected call Invoke_AMBIENT_PALETTE webbrowser.c:1557: Test failed: unexpected call GetOptionKeyPath webbrowser.c:359: Test failed: unexpected call QueryStatus_SETPROGRESSTEXT webbrowser.c:469: Test failed: unexpected nCmdID 26 webbrowser.c:469: Test failed: unexpected nCmdID 29 webbrowser.c:1007: Test failed: unexpected call GetContainer webbrowser.c:517: Test failed: unexpected call webbrowser.c:791: Test failed: ReadyState = 1, expected 4 webbrowser.c:1568: Test failed: unexpected call GetDropTarget webbrowser.c:469: Test failed: unexpected nCmdID 16 webbrowser.c:469: Test failed: unexpected nCmdID 15 webbrowser.c:469: Test failed: unexpected nCmdID 16 webbrowser.c:469: Test failed: unexpected nCmdID 15 webbrowser.c:469: Test failed: unexpected nCmdID 16 webbrowser.c:469: Test failed: unexpected nCmdID 15 webbrowser.c:469: Test failed: unexpected nCmdID 16 webbrowser.c:469: Test failed: unexpected nCmdID 15 webbrowser.c:469: Test failed: unexpected nCmdID 16 webbrowser.c:469: Test failed: unexpected nCmdID 15 webbrowser.c:469: Test failed: unexpected nCmdID 16 webbrowser.c:469: Test failed: unexpected nCmdID 15 webbrowser.c:469: Test failed: unexpected nCmdID 16 webbrowser.c:469: Test failed: unexpected nCmdID 15 webbrowser.c:469: Test failed: unexpected nCmdID 16 webbrowser.c:469: Test failed: unexpected nCmdID 15 webbrowser.c:469: Test failed: unexpected nCmdID 16 webbrowser.c:469: Test failed: unexpected nCmdID 15 webbrowser.c:469: Test failed: unexpected nCmdID 16 webbrowser.c:469: Test failed: unexpected nCmdID 15 webbrowser.c:1007: Test failed: unexpected call GetContainer webbrowser.c:517: Test failed: unexpected call webbrowser.c:469: Test failed: unexpected nCmdID 16 webbrowser.c:469: Test failed: unexpected nCmdID 15 webbrowser.c:2702: Test failed: expected Invoke_SETSECURELOCKICON webbrowser.c:2648: Test failed: ReadyState = 1, expected 4 webbrowser.c:839: Test failed: unexpected call Invoke_PROPERTYCHANGE webbrowser.c:855: Test failed: unexpected call Invoke_BEFORENAVIGATE2 webbrowser.c:614: Test failed: unexpected call Invoke_AMBIENT_USERMODE webbrowser.c:614: Test failed: unexpected call Invoke_AMBIENT_USERMODE webbrowser.c:617: Test failed: unexpected call Invoke_AMBIENT_DLCONTROL webbrowser.c:621: Test failed: unexpected call Invoke_AMBIENT_USERAGENT webbrowser.c:625: Test failed: unexpected call Invoke_AMBIENT_PALETTE webbrowser.c:1557: Test failed: unexpected call GetOptionKeyPath webbrowser.c:359: Test failed: unexpected call QueryStatus_SETPROGRESSTEXT webbrowser.c:469: Test failed: unexpected nCmdID 26 webbrowser.c:469: Test failed: unexpected nCmdID 16 webbrowser.c:469: Test failed: unexpected nCmdID 15 webbrowser.c:469: Test failed: unexpected nCmdID 29 webbrowser.c:1007: Test failed: unexpected call GetContainer webbrowser.c:517: Test failed: unexpected call webbrowser.c:791: Test failed: ReadyState = 1, expected 4 webbrowser.c:1568: Test failed: unexpected call GetDropTarget webbrowser.c:1007: Test failed: unexpected call GetContainer webbrowser.c:517: Test failed: unexpected call webbrowser.c:2702: Test failed: expected Invoke_SETSECURELOCKICON webbrowser.c:2943: Test failed: expected RequestUIActivate webbrowser.c:3035: Test failed: Got 0x80004002 webbrowser.c:3130: Test failed: QueryService failed: 80004002 webbrowser: unhandled exception c0000005 at 0040D5A2

1 0

winealsa.drv patch to enum all software devices from .asoundrc
by Нискородов Серёжа Feb. 10, 2012

Feb. 10, 2012

Hi, all. I'm not so good at programming. I just was looking for a way to make possible play sound from WINE to ALSA software device other than "default". I wrote a patch that allows you to select the ALSA software device from control panel, along with the hardware devices. Perhaps the code is not so clear and beautiful, but it works for me, and maybe someone wants to send it to the repository, or to correct and send a corrected.

2 5

[PATCH 1/6] include: new file ddk/scsi.h
by Dan Kegel Feb. 9, 2012

Feb. 9, 2012

Only adds the minimum definitions needed to use SCSIOP_READ_DVD_STRUCTURE.

1 0

winetest can't remove its temp directory
by Joerg-Cyril.Hoehle＠t-systems.com Feb. 9, 2012

Feb. 9, 2012

Hi, does anybody else see a message from winetest.exe about not being able to clean up at the end? This happened with e.g. winetest-1.4-rc2 and some earlier ones. Indeed, a temp directory with all the extracted *_test.exe is left half-full. It looks like files got deleted in alphabetical order starting with 'a'. mmdevapi_test.exe is the first one left, up to x*_test.exe Today's "[PATCH 2/4] mmdevapi/tests" adds a missing IAudioClock_Release(acl); Perhaps that prevented mmdevapi from cleaning up? How to explain such an effect? How to allow winetest to clean up and exit properly? That does not seem to be issue #12801. Thank you for your help, Jörg Höhle

2 1

Add a trailing full stop to the kernel32 error messages
by Francois Gouget Feb. 9, 2012

Feb. 9, 2012

Translators: This may concern you! See the (*) below. (hence the post to wine-devel) It was discovered that the kernel32 error messages are supposed to all end with a full stop. This is a lot of strings and impacts a lot of translations. http://www.winehq.org/pipermail/wine-devel/2012-January/093969.html So this fix is not provided as a patch but as a set of two scripts. * mcfix adds a trailing full stop if needed to the kernel32 error messages. * pofix does the matching changes to the specified PO file both on the English and translated strings (taking into account the full-width for Chinese and Japanese translations). The advantage is that this can update everything with no fuzzying and without risking conflicts when applying it to Wine(*). To update Wine, simply run: ./mcfix dlls/kernel32/winerror.mc; for i in po/*.po;do ./pofix $i;done (*) As a translator if you have a local PO file that you took before this change and you modified some kernel32 error translations you patch will conflict. But that's easy to solve, simply run: ./pofix myfile.po -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ 145 = 1! + 4! + 5!

1 0

Re: [PATCH 1/2] winmm: Avoid using SuspendThread, it can hang Wine.
by Alexandre Julliard Feb. 9, 2012

Feb. 9, 2012

Joerg-Cyril.Hoehle(a)t-systems.com writes: > @@ -1006,7 +1008,9 @@ static BOOL MMSYSTEM_MidiStream_MessageHandler(WINE_MIDIStream* lpMidiStrm, LPWI > LPMIDIHDR lpMidiHdr; > LPMIDIHDR* lpmh; > LPBYTE lpData; > + BOOL paused = FALSE; > > +still_paused: > switch (msg->message) { > case WM_QUIT: > SetEvent(lpMidiStrm->hEvent); > @@ -1028,6 +1032,16 @@ static BOOL MMSYSTEM_MidiStream_MessageHandler(WINE_MIDIStream* lpMidiStrm, LPWI > } > lpMidiStrm->lpMidiHdr = 0; > SetEvent(lpMidiStrm->hEvent); > + return TRUE; > + case WINE_MSM_RESUME: > + /* FIXME: send out cc64 0 (turn off sustain pedal) on every channel */ > + lpMidiStrm->dwStartTicks = GetTickCount() - lpMidiStrm->dwPositionMS; > + SetEvent(lpMidiStrm->hEvent); > + return TRUE; > + case WINE_MSM_PAUSE: > + /* FIXME: send out cc64 0 (turn off sustain pedal) on every channel */ > + paused = TRUE; > + SetEvent(lpMidiStrm->hEvent); > break; > case WINE_MSM_HEADER: > /* sets initial tick count for first MIDIHDR */ > @@ -1114,6 +1128,10 @@ static BOOL MMSYSTEM_MidiStream_MessageHandler(WINE_MIDIStream* lpMidiStrm, LPWI > FIXME("Unknown message %d\n", msg->message); > break; > } > + if (paused) { > + GetMessageA(msg, 0, 0, 0); > + goto still_paused; > + } Please stop abusing goto, write a proper loop instead. -- Alexandre Julliard julliard(a)winehq.org

3 4

Re: [PATCH 2/2] urlmon: Added more mk: combining tests
by Marvin Feb. 9, 2012

Feb. 9, 2012

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=16890 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: [PATCH 4/4] mmdevapi/tests: Check GetService's output parameter.
by Marvin Feb. 9, 2012

Feb. 9, 2012

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=16888 Your paranoid android. === WVISTAADM (32 bit render) === render.c:990: Test failed: ReleaseBuffer failed: 80070057 render.c:1013: Test failed: Position 0 vs. last 0 render.c:1076: Test failed: Reset failed: 8889000b render.c:1080: Test failed: Reset on a resetted stream returns 8889000b render.c:1089: Test failed: GetBuffer failed: 88890007 render.c:1094: Test failed: ReleaseBuffer failed: 80070057 render.c:1115: Test failed: Position 0 vs. last 0 render.c:1147: Test failed: Reset failed: 8889000b render.c:1154: Test failed: Reset on a resetted stream returns 8889000b render.c:1162: Test failed: GetBuffer failed: 88890007 render.c:990: Test failed: ReleaseBuffer failed: 80070057 render.c:1013: Test failed: Position 0 vs. last 0 render.c:1076: Test failed: Reset failed: 8889000b render.c:1080: Test failed: Reset on a resetted stream returns 8889000b render.c:1089: Test failed: GetBuffer failed: 88890007 render.c:1094: Test failed: ReleaseBuffer failed: 80070057 render.c:1115: Test failed: Position 0 vs. last 0 render.c:1147: Test failed: Reset failed: 8889000b render.c:1154: Test failed: Reset on a resetted stream returns 8889000b render.c:1162: Test failed: GetBuffer failed: 88890007 === W2K8SE (32 bit render) === render.c:990: Test failed: ReleaseBuffer failed: 80070057 render.c:1013: Test failed: Position 0 vs. last 0 render.c:1076: Test failed: Reset failed: 8889000b render.c:1080: Test failed: Reset on a resetted stream returns 8889000b render.c:1089: Test failed: GetBuffer failed: 88890007 render.c:1094: Test failed: ReleaseBuffer failed: 80070057 render.c:1115: Test failed: Position 0 vs. last 0 render.c:1147: Test failed: Reset failed: 8889000b render.c:1154: Test failed: Reset on a resetted stream returns 8889000b render.c:1162: Test failed: GetBuffer failed: 88890007 render.c:990: Test failed: ReleaseBuffer failed: 80070057 render.c:1013: Test failed: Position 0 vs. last 0 render.c:1076: Test failed: Reset failed: 8889000b render.c:1080: Test failed: Reset on a resetted stream returns 8889000b render.c:1089: Test failed: GetBuffer failed: 88890007 render.c:1094: Test failed: ReleaseBuffer failed: 80070057 render.c:1115: Test failed: Position 0 vs. last 0 render.c:1147: Test failed: Reset failed: 8889000b render.c:1154: Test failed: Reset on a resetted stream returns 8889000b render.c:1162: Test failed: GetBuffer failed: 88890007 === W7PRO (32 bit render) === render.c:990: Test failed: ReleaseBuffer failed: 80070057 render.c:1013: Test failed: Position 0 vs. last 0 render.c:1076: Test failed: Reset failed: 8889000b render.c:1080: Test failed: Reset on a resetted stream returns 8889000b render.c:1089: Test failed: GetBuffer failed: 88890007 render.c:1094: Test failed: ReleaseBuffer failed: 80070057 render.c:1115: Test failed: Position 0 vs. last 0 render.c:1147: Test failed: Reset failed: 8889000b render.c:1154: Test failed: Reset on a resetted stream returns 8889000b render.c:1162: Test failed: GetBuffer failed: 88890007 render.c:990: Test failed: ReleaseBuffer failed: 80070057 render.c:1013: Test failed: Position 0 vs. last 0 render.c:1076: Test failed: Reset failed: 8889000b render.c:1080: Test failed: Reset on a resetted stream returns 8889000b render.c:1089: Test failed: GetBuffer failed: 88890007 render.c:1094: Test failed: ReleaseBuffer failed: 80070057 render.c:1115: Test failed: Position 0 vs. last 0 render.c:1147: Test failed: Reset failed: 8889000b render.c:1154: Test failed: Reset on a resetted stream returns 8889000b render.c:1162: Test failed: GetBuffer failed: 88890007 === W7PROX64 (32 bit render) === render.c:990: Test failed: ReleaseBuffer failed: 80070057 render.c:1013: Test failed: Position 0 vs. last 0 render.c:1076: Test failed: Reset failed: 8889000b render.c:1080: Test failed: Reset on a resetted stream returns 8889000b render.c:1089: Test failed: GetBuffer failed: 88890007 render.c:1094: Test failed: ReleaseBuffer failed: 80070057 render.c:1115: Test failed: Position 0 vs. last 0 render.c:1147: Test failed: Reset failed: 8889000b render.c:1154: Test failed: Reset on a resetted stream returns 8889000b render.c:1162: Test failed: GetBuffer failed: 88890007 render.c:990: Test failed: ReleaseBuffer failed: 80070057 render.c:1013: Test failed: Position 0 vs. last 0 render.c:1076: Test failed: Reset failed: 8889000b render.c:1080: Test failed: Reset on a resetted stream returns 8889000b render.c:1089: Test failed: GetBuffer failed: 88890007 render.c:1094: Test failed: ReleaseBuffer failed: 80070057 render.c:1115: Test failed: Position 0 vs. last 0 render.c:1147: Test failed: Reset failed: 8889000b render.c:1154: Test failed: Reset on a resetted stream returns 8889000b render.c:1162: Test failed: GetBuffer failed: 88890007 === TEST64_W7SP1 (32 bit render) === render.c:990: Test failed: ReleaseBuffer failed: 80070057 render.c:1013: Test failed: Position 0 vs. last 0 render.c:1076: Test failed: Reset failed: 8889000b render.c:1080: Test failed: Reset on a resetted stream returns 8889000b render.c:1089: Test failed: GetBuffer failed: 88890007 render.c:1094: Test failed: ReleaseBuffer failed: 80070057 render.c:1115: Test failed: Position 0 vs. last 0 render.c:1147: Test failed: Reset failed: 8889000b render.c:1154: Test failed: Reset on a resetted stream returns 8889000b render.c:1162: Test failed: GetBuffer failed: 88890007 render.c:990: Test failed: ReleaseBuffer failed: 80070057 render.c:1013: Test failed: Position 0 vs. last 0 render.c:1076: Test failed: Reset failed: 8889000b render.c:1080: Test failed: Reset on a resetted stream returns 8889000b render.c:1089: Test failed: GetBuffer failed: 88890007 render.c:1094: Test failed: ReleaseBuffer failed: 80070057 render.c:1115: Test failed: Position 0 vs. last 0 render.c:1147: Test failed: Reset failed: 8889000b render.c:1154: Test failed: Reset on a resetted stream returns 8889000b render.c:1162: Test failed: GetBuffer failed: 88890007 === W7PROX64 (64 bit render) === render.c:990: Test failed: ReleaseBuffer failed: 80070057 render.c:1013: Test failed: Position 0 vs. last 0 render.c:1076: Test failed: Reset failed: 8889000b render.c:1080: Test failed: Reset on a resetted stream returns 8889000b render.c:1089: Test failed: GetBuffer failed: 88890007 render.c:1094: Test failed: ReleaseBuffer failed: 80070057 render.c:1115: Test failed: Position 0 vs. last 0 render.c:1147: Test failed: Reset failed: 8889000b render.c:1154: Test failed: Reset on a resetted stream returns 8889000b render.c:1162: Test failed: GetBuffer failed: 88890007 render.c:990: Test failed: ReleaseBuffer failed: 80070057 render.c:1013: Test failed: Position 0 vs. last 0 render.c:1076: Test failed: Reset failed: 8889000b render.c:1080: Test failed: Reset on a resetted stream returns 8889000b render.c:1089: Test failed: GetBuffer failed: 88890007 render.c:1094: Test failed: ReleaseBuffer failed: 80070057 render.c:1115: Test failed: Position 0 vs. last 0 render.c:1147: Test failed: Reset failed: 8889000b render.c:1154: Test failed: Reset on a resetted stream returns 8889000b render.c:1162: Test failed: GetBuffer failed: 88890007 === TEST64_W7SP1 (64 bit render) === render.c:990: Test failed: ReleaseBuffer failed: 80070057 render.c:1013: Test failed: Position 0 vs. last 0 render.c:1076: Test failed: Reset failed: 8889000b render.c:1080: Test failed: Reset on a resetted stream returns 8889000b render.c:1089: Test failed: GetBuffer failed: 88890007 render.c:1094: Test failed: ReleaseBuffer failed: 80070057 render.c:1115: Test failed: Position 0 vs. last 0 render.c:1147: Test failed: Reset failed: 8889000b render.c:1154: Test failed: Reset on a resetted stream returns 8889000b render.c:1162: Test failed: GetBuffer failed: 88890007 render.c:990: Test failed: ReleaseBuffer failed: 80070057 render.c:1013: Test failed: Position 0 vs. last 0 render.c:1076: Test failed: Reset failed: 8889000b render.c:1080: Test failed: Reset on a resetted stream returns 8889000b render.c:1089: Test failed: GetBuffer failed: 88890007 render.c:1094: Test failed: ReleaseBuffer failed: 80070057 render.c:1115: Test failed: Position 0 vs. last 0 render.c:1147: Test failed: Reset failed: 8889000b render.c:1154: Test failed: Reset on a resetted stream returns 8889000b render.c:1162: Test failed: GetBuffer failed: 88890007

1 0

Re: [PATCH 3/4] mmdevapi/tests: Perform renderer padding & position tests.
by Marvin Feb. 9, 2012

Feb. 9, 2012

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=16887 Your paranoid android. === WVISTAADM (32 bit render) === render.c:980: Test failed: ReleaseBuffer failed: 80070057 render.c:1003: Test failed: Position 0 vs. last 0 render.c:1066: Test failed: Reset failed: 8889000b render.c:1070: Test failed: Reset on a resetted stream returns 8889000b render.c:1079: Test failed: GetBuffer failed: 88890007 render.c:1084: Test failed: ReleaseBuffer failed: 80070057 render.c:1105: Test failed: Position 0 vs. last 0 render.c:1137: Test failed: Reset failed: 8889000b render.c:1144: Test failed: Reset on a resetted stream returns 8889000b render.c:1152: Test failed: GetBuffer failed: 88890007 render.c:980: Test failed: ReleaseBuffer failed: 80070057 render.c:1003: Test failed: Position 0 vs. last 0 render.c:1066: Test failed: Reset failed: 8889000b render.c:1070: Test failed: Reset on a resetted stream returns 8889000b render.c:1079: Test failed: GetBuffer failed: 88890007 render.c:1084: Test failed: ReleaseBuffer failed: 80070057 render.c:1105: Test failed: Position 0 vs. last 0 render.c:1137: Test failed: Reset failed: 8889000b render.c:1144: Test failed: Reset on a resetted stream returns 8889000b render.c:1152: Test failed: GetBuffer failed: 88890007 === W2K8SE (32 bit render) === render.c:980: Test failed: ReleaseBuffer failed: 80070057 render.c:1003: Test failed: Position 0 vs. last 0 render.c:1066: Test failed: Reset failed: 8889000b render.c:1070: Test failed: Reset on a resetted stream returns 8889000b render.c:1079: Test failed: GetBuffer failed: 88890007 render.c:1084: Test failed: ReleaseBuffer failed: 80070057 render.c:1105: Test failed: Position 0 vs. last 0 render.c:1137: Test failed: Reset failed: 8889000b render.c:1144: Test failed: Reset on a resetted stream returns 8889000b render.c:1152: Test failed: GetBuffer failed: 88890007 render.c:980: Test failed: ReleaseBuffer failed: 80070057 render.c:1003: Test failed: Position 0 vs. last 0 render.c:1066: Test failed: Reset failed: 8889000b render.c:1070: Test failed: Reset on a resetted stream returns 8889000b render.c:1079: Test failed: GetBuffer failed: 88890007 render.c:1084: Test failed: ReleaseBuffer failed: 80070057 render.c:1105: Test failed: Position 0 vs. last 0 render.c:1137: Test failed: Reset failed: 8889000b render.c:1144: Test failed: Reset on a resetted stream returns 8889000b render.c:1152: Test failed: GetBuffer failed: 88890007 === W7PRO (32 bit render) === render.c:980: Test failed: ReleaseBuffer failed: 80070057 render.c:1003: Test failed: Position 0 vs. last 0 render.c:1066: Test failed: Reset failed: 8889000b render.c:1070: Test failed: Reset on a resetted stream returns 8889000b render.c:1079: Test failed: GetBuffer failed: 88890007 render.c:1084: Test failed: ReleaseBuffer failed: 80070057 render.c:1105: Test failed: Position 0 vs. last 0 render.c:1137: Test failed: Reset failed: 8889000b render.c:1144: Test failed: Reset on a resetted stream returns 8889000b render.c:1152: Test failed: GetBuffer failed: 88890007 render.c:980: Test failed: ReleaseBuffer failed: 80070057 render.c:1003: Test failed: Position 0 vs. last 0 render.c:1066: Test failed: Reset failed: 8889000b render.c:1070: Test failed: Reset on a resetted stream returns 8889000b render.c:1079: Test failed: GetBuffer failed: 88890007 render.c:1084: Test failed: ReleaseBuffer failed: 80070057 render.c:1105: Test failed: Position 0 vs. last 0 render.c:1137: Test failed: Reset failed: 8889000b render.c:1144: Test failed: Reset on a resetted stream returns 8889000b render.c:1152: Test failed: GetBuffer failed: 88890007 === W7PROX64 (32 bit render) === render.c:980: Test failed: ReleaseBuffer failed: 80070057 render.c:1003: Test failed: Position 0 vs. last 0 render.c:1066: Test failed: Reset failed: 8889000b render.c:1070: Test failed: Reset on a resetted stream returns 8889000b render.c:1079: Test failed: GetBuffer failed: 88890007 render.c:1084: Test failed: ReleaseBuffer failed: 80070057 render.c:1105: Test failed: Position 0 vs. last 0 render.c:1137: Test failed: Reset failed: 8889000b render.c:1144: Test failed: Reset on a resetted stream returns 8889000b render.c:1152: Test failed: GetBuffer failed: 88890007 render.c:980: Test failed: ReleaseBuffer failed: 80070057 render.c:1003: Test failed: Position 0 vs. last 0 render.c:1066: Test failed: Reset failed: 8889000b render.c:1070: Test failed: Reset on a resetted stream returns 8889000b render.c:1079: Test failed: GetBuffer failed: 88890007 render.c:1084: Test failed: ReleaseBuffer failed: 80070057 render.c:1105: Test failed: Position 0 vs. last 0 render.c:1137: Test failed: Reset failed: 8889000b render.c:1144: Test failed: Reset on a resetted stream returns 8889000b render.c:1152: Test failed: GetBuffer failed: 88890007 === TEST64_W7SP1 (32 bit render) === render.c:980: Test failed: ReleaseBuffer failed: 80070057 render.c:1003: Test failed: Position 0 vs. last 0 render.c:1066: Test failed: Reset failed: 8889000b render.c:1070: Test failed: Reset on a resetted stream returns 8889000b render.c:1079: Test failed: GetBuffer failed: 88890007 render.c:1084: Test failed: ReleaseBuffer failed: 80070057 render.c:1105: Test failed: Position 0 vs. last 0 render.c:1137: Test failed: Reset failed: 8889000b render.c:1144: Test failed: Reset on a resetted stream returns 8889000b render.c:1152: Test failed: GetBuffer failed: 88890007 render.c:980: Test failed: ReleaseBuffer failed: 80070057 render.c:1003: Test failed: Position 0 vs. last 0 render.c:1066: Test failed: Reset failed: 8889000b render.c:1070: Test failed: Reset on a resetted stream returns 8889000b render.c:1079: Test failed: GetBuffer failed: 88890007 render.c:1084: Test failed: ReleaseBuffer failed: 80070057 render.c:1105: Test failed: Position 0 vs. last 0 render.c:1137: Test failed: Reset failed: 8889000b render.c:1144: Test failed: Reset on a resetted stream returns 8889000b render.c:1152: Test failed: GetBuffer failed: 88890007 === W7PROX64 (64 bit render) === render.c:980: Test failed: ReleaseBuffer failed: 80070057 render.c:1003: Test failed: Position 0 vs. last 0 render.c:1066: Test failed: Reset failed: 8889000b render.c:1070: Test failed: Reset on a resetted stream returns 8889000b render.c:1079: Test failed: GetBuffer failed: 88890007 render.c:1084: Test failed: ReleaseBuffer failed: 80070057 render.c:1105: Test failed: Position 0 vs. last 0 render.c:1137: Test failed: Reset failed: 8889000b render.c:1144: Test failed: Reset on a resetted stream returns 8889000b render.c:1152: Test failed: GetBuffer failed: 88890007 render.c:980: Test failed: ReleaseBuffer failed: 80070057 render.c:1003: Test failed: Position 0 vs. last 0 render.c:1066: Test failed: Reset failed: 8889000b render.c:1070: Test failed: Reset on a resetted stream returns 8889000b render.c:1079: Test failed: GetBuffer failed: 88890007 render.c:1084: Test failed: ReleaseBuffer failed: 80070057 render.c:1105: Test failed: Position 0 vs. last 0 render.c:1137: Test failed: Reset failed: 8889000b render.c:1144: Test failed: Reset on a resetted stream returns 8889000b render.c:1152: Test failed: GetBuffer failed: 88890007 === TEST64_W7SP1 (64 bit render) === render.c:980: Test failed: ReleaseBuffer failed: 80070057 render.c:1003: Test failed: Position 0 vs. last 0 render.c:1066: Test failed: Reset failed: 8889000b render.c:1070: Test failed: Reset on a resetted stream returns 8889000b render.c:1079: Test failed: GetBuffer failed: 88890007 render.c:1084: Test failed: ReleaseBuffer failed: 80070057 render.c:1105: Test failed: Position 0 vs. last 0 render.c:1137: Test failed: Reset failed: 8889000b render.c:1144: Test failed: Reset on a resetted stream returns 8889000b render.c:1152: Test failed: GetBuffer failed: 88890007 render.c:980: Test failed: ReleaseBuffer failed: 80070057 render.c:1003: Test failed: Position 0 vs. last 0 render.c:1066: Test failed: Reset failed: 8889000b render.c:1070: Test failed: Reset on a resetted stream returns 8889000b render.c:1079: Test failed: GetBuffer failed: 88890007 render.c:1084: Test failed: ReleaseBuffer failed: 80070057 render.c:1105: Test failed: Position 0 vs. last 0 render.c:1137: Test failed: Reset failed: 8889000b render.c:1144: Test failed: Reset on a resetted stream returns 8889000b render.c:1152: Test failed: GetBuffer failed: 88890007

1 0

Re: winecfg: Center main window on the screen.
by Dmitry Timoshkov Feb. 9, 2012

Feb. 9, 2012

Dmitry Timoshkov <dmitry(a)baikal.ru> wrote: > For bug 21645. What is this pending for? -- Dmitry.

1 0

libgcrypt thread safety
by Adam Martinson Feb. 8, 2012

Feb. 8, 2012

I've been looking into bug 27036 <http://bugs.winehq.org/show_bug.cgi?id=27036> , and it's due to the lack of thread safety by default in libgcrypt (in this case via libgnutls in secur32.dll). To be thread safe, libgcrypt requires a call to gcry_control(GCRYCTL_SET_THREAD_CBS) before any libgcrypt initialization is done. However, libgcrypt is used by a lot of different libs, one of which is being used by some other dll that's loading before secur32.dll. My question is, is it acceptable to do the gcry_control() call in ntdll's DllMain()? The alternative seems to be tracking down every lib used by wine that uses libgcrypt and doing it in each of those dlls. What's the best way to handle this?

3 2

Re: Profiing windows apps
by Ralph Little Feb. 8, 2012

Feb. 8, 2012

Hi, > Also please attach a full +ddraw log to the bug report. If it is too big > compress it. bzip2 should do a pretty decent job, if all fails try lrzip. OK, done! > If the testing doesn't reveal anything, look out for IDirectDraw::GetCaps > calls in the logs or IDirect3Dx::EnumZBufferFormats. IDirectDraw::GetCaps > returns a DDCAPS structure which has dwZBufferBitDepths containing some flags > for z buffer bit depths. EnumZBufferFormats calls a callback multiple times > with available DDPIXELFORMAT structures. The application may not like some > flags we set there. The Sims calls EnumDevices and I presume calls EnumZBufferFormats within the callback for each device: trace:ddraw:d3d3_EnumDevices Enumerating WineD3D D3DDevice interface. trace:ddraw:d3d3_EnumZBufferFormats iface 0x13d04c, device_iid {a4665c60-2673-11cf-a31a-00aa00b93356}, callback 0x586a7d, context 0xabc198. trace:ddraw:d3d7_EnumZBufferFormats iface 0x13d048, device_iid {a4665c60-2673-11cf-a31a-00aa00b93356}, callback 0x586a7d, context 0xabc198. trace:ddraw:d3d7_EnumZBufferFormats Asked for SW device. trace:ddraw:PixelFormat_WineD3DtoDD Converting wined3d format 0x52 to DDRAW. trace:ddraw:PixelFormat_WineD3DtoDD Returning: ( DDPF_ZBUFFER , Z bits : 16) trace:ddraw:d3d7_EnumZBufferFormats Enumerating wined3d format 0x52. trace:ddraw:d3d7_EnumZBufferFormats Format enumeration cancelled by application. trace:ddraw:d3d3_EnumDevices Enumerating HAL Direct3D device. trace:ddraw:d3d3_EnumZBufferFormats iface 0x13d04c, device_iid {84e63de0-46aa-11cf-816f-0000c020156e}, callback 0x586a7d, context 0xabc198. trace:ddraw:d3d7_EnumZBufferFormats iface 0x13d048, device_iid {84e63de0-46aa-11cf-816f-0000c020156e}, callback 0x586a7d, context 0xabc198. trace:ddraw:d3d7_EnumZBufferFormats Asked for HAL device. trace:ddraw:PixelFormat_WineD3DtoDD Converting wined3d format 0x52 to DDRAW. trace:ddraw:PixelFormat_WineD3DtoDD Returning: ( DDPF_ZBUFFER , Z bits : 16) trace:ddraw:d3d7_EnumZBufferFormats Enumerating wined3d format 0x52. trace:ddraw:d3d7_EnumZBufferFormats Format enumeration cancelled by application. trace:ddraw:d3d3_EnumDevices End of enumeration. I don't know if this looks sensible, though. I see from the code that there are a lot of "gotchas" (both in d3d7_EnumZBufferFormats and d3d3_EnumDevices) for a number of games expecting things to happen in specific sequences and containing specific responses. I wonder if the Sims is going to turn out to be another. Cheers, Ralph

1 0

OpenGL child windows (SketchUp)
by Brian Bloniarz Feb. 8, 2012

Feb. 8, 2012

Hi all, I could use a little help fixing a window lag and screen corruption issue in SketchUp: http://bugs.winehq.org/show_bug.cgi?id=25912 Long story short, I think the implementation of OpenGL child rendering needs a small update. As a reminder, this is how an OpenGL child window is setup: static BOOL set_win_format( HWND hwnd, XID fbconfig_id ) { gl_drawable = XCreateWindow(...); // offscreen window XCompositeRedirectWindow(..., gl_drawable, CompositeRedirectManual); } Here XComposite extension is render into an offscreen window. When it's time to display, the contents of that window are copied into the visible onscreen parent window (physDev is the onscreen window, gl_drawable is the offscreen window): BOOL X11DRV_SwapBuffers(PHYSDEV dev) { ... glXSwapBuffers(gdi_display, gl_drawable); ... /* The GL drawable may be lagged behind if we don't flush first, so * flush the display make sure we copy up-to-date data */ XFlush(gdi_display); XCopyArea(gdi_display, gl_drawable, physDev...); } The XFlush() is the problem; the buffer swap must happen before the copy, and accelerated renderers wouldn't guarantee to do that on an X queue flush. So how do you wait for a buffer swap? I wrote a test program, can you say "undefined behavior"? I tested on a few drivers: 1) ATI fglrx binary driver: glXSwapBuffers is instantaneous, existing code works fine. 2) NVidia binary driver: glXSwapBuffers is asynchronous, neither XFlush() nor XSync() is enough. Calling glXWaitGL or glFinish works. 3) Mesa DRI driver (Intel i915): glXSwapBuffers is asynchronous. None of XFlush/XSync/glXWaitX/glXWaitGL is enough. glFinish works. 4) r600g (Open Source accelerated ATI) driver: glXSwapBuffers is asynchronous. None of the flush calls wait for it (XFlush/XSync/glXWaitGL/glXWaitX/glFinish). The last one is the tricky part -- this driver is also based on the DRI, so I'm guessing it may appear on other open-source accelerated drivers (looking at http://www.x.org/releases/current/doc/dri2proto/dri2proto.txt suggests that this is new behavior as of 1.99.2) So how to come up with a common fix? I could think of 3 possibilities: 1) Use the GLX_OML_sync_control extension, it has an explicit call to wait for a buffer swap. Not supported by NV or fglrx, but we could fallback to glXWaitGL on those drivers. Probably simplest. 2) Use the X Damage extension, wait for an XDamageNotify event before copying. This should work everywhere, all drivers probably implement damage so that compositing window managers can use it. 3) Talk to the DRI people, maybe glXWaitGL should't return when there's a pending a buffer swap. The GLX spec seems to say it should wait, but it's a grey area and the Composite extension was designed much later. Not a quick fix. Any ideas or thoughts? If I hear nothing, I can code up a patch that does (1), but it'd be great to hear from some people who know this area well. Thanks, Brian Bloniarz

3 2

Re: gdi32: Consider whether the logical font face is vertical when selecting.
by Marvin Feb. 8, 2012

Feb. 8, 2012

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=16876 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

1 0

Re: winecfg: Center main window on the screen.
by Vitaliy Margolen Feb. 8, 2012

Feb. 8, 2012

Please don't! I want my window manager decide based on how I configured it where to position new windows. And not every program open in the middle of the screen just because it things it's the most important thing on my screen. Vitaliy.

4 3

winmm: TRACE unhandled messages
by Joerg-Cyril.Hoehle＠t-systems.com Feb. 8, 2012

Feb. 8, 2012

Andrew, it's good that you log these now. I had a question in mind since your winmm rewrite: Your rewrite no more maps WOD_XYZ* messages to waveOut functions. I believe that it is possible that an old app entirely uses the generic SendDriverMessage function (esp. in the mciavi/msvfw area, cf. ICSendMessage) instead of the specific wave/midi* ones. Can you be sure that this is not supported by native, esp. w9x? If Wine does not map these, all we'll get to "hear" in AppDB is that attentive people miss sound or music that they remember listening to 10 years ago on native. Regards, Jörg Höhle

2 1

Re: [1/2] user32: Add a bunch of RealChildWindowFromPoint tests.
by Alexandre Julliard Feb. 8, 2012

Feb. 8, 2012

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > win.c:6753: Test failed: FlashWindowEx succeeded > win.c:6764: Test failed: FlashWindowEx failed with -559038737 > > are intermittent, and have nothing to do with these tests. Maybe not directly, but the failures are clearly caused by your change, and they look pretty bad on the test results. Please fix that. -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: po: Remove untranslated English strings from the Romanian translation
by Michael Stefaniuc Feb. 7, 2012

Feb. 7, 2012

Hello Frédéric, the patch is wrong. Frédéric Delanoy wrote: > --- > po/ro.po | 6 +++--- > 1 files changed, 3 insertions(+), 3 deletions(-) > > diff --git a/po/ro.po b/po/ro.po > index a0912c2..c9375c4 100644 > --- a/po/ro.po > +++ b/po/ro.po > @@ -11803,11 +11803,11 @@ msgstr "Bază" > > #: regedit.rc:282 > msgid "Hexadecimal" > -msgstr "Hexadecimal" > +msgstr "" > > #: regedit.rc:283 > msgid "Decimal" > -msgstr "Decimal" > +msgstr "" Those aren't untranslated but the Romanian words match the English ones. > #: regedit.rc:290 > msgid "Edit Binary" > @@ -13243,7 +13243,7 @@ msgstr "Afișează opțiunile a&vansate" > > #: winecfg.rc:240 > msgid "De&vice:" > -msgstr "De&vice:" > +msgstr "" > > #: winecfg.rc:242 > msgid "Bro&wse..." bye michael

3 3

Re: po: Fix some trailing ellipses errors in Catalan translation
by Alex Henrie Feb. 7, 2012

Feb. 7, 2012

#: ieframe.rc:68 winhlp32.rc:66 msgid "Print..." -msgstr "Imprimeix" +msgstr "Imprimeix..." I intentionally left the ellipse off of the word "Imprimeix" in Internet Explorer so that the text would fit on the toolbar button. Any suggestions? -Alex

3 2

Re: po: Update finnish locales
by Lauri Kenttä Feb. 7, 2012

Feb. 7, 2012

On 2012-02-06 23:00, Olli-Pekka Wallin wrote: > +msgstr "KB/s" > ... > +msgstr "Yksi sivua" > ... > +msgstr "Wordpad ojelman kÃƒÂ¤ynnistys epÃƒÂ¤onnistui" I'm sorry to say this, but these translations are really bad. I suggest you either have someone check your translations thoroughly before submitting or leave the whole job for others. (I'm already working on it.) The patch is also based on an old revision and changes a msgid. -- Lauri Kenttä

1 0

SourceForge forbids download
by Aidin Gharibnavaz Feb. 7, 2012

Feb. 7, 2012

Dear Wine developers, SourceForge blocked download for some countries by default, such as Iran. (More detail can be found here<https://sourceforge.net/blog/some-good-news-SourceForge-removes-blanket-blo…> ) So, if it's not illegal to you to let Iranians download your software, please go to the SourceForge's ProjectAdmin, and set the ExportControl option, to let us enjoy the great work of yours. Thanks.

3 2

Re: po: Update finnish locales
by Francois Gouget Feb. 7, 2012

Feb. 7, 2012

On Mon, 6 Feb 2012, Olli-Pekka Wallin wrote: > po: Update finnish locales > > #: appwiz.rc:49 > msgid "Installing..." > -msgstr "" > +msgstr "Asennetaan.." It looks like there's a missing dot here. But thanks a lot for the patch. Feel free to tackle any other issue in: http://fgouget.free.fr/wine-po/fi-errors.html Also don't hesitate to let me know about false positives so I can silence them. -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ Any sufficiently advanced bug is indistinguishable from a feature. -- from some indian guy

1 0

Re: ID3DXBaseEffect::SetValue
by luis.busquets＠ilidium.com Feb. 7, 2012

Feb. 7, 2012

For the textures point, it is judt that the implemenyation is just the change of one pointer ----- Reply message ----- De: "Rico Schüller" <kgbricola(a)web.de> Para: "Luis Carlos Busquets Pérez" <luis.busquets(a)ilidium.com> CC: <wine-devel(a)winehq.org> Asunto: ID3DXBaseEffect::SetValue Fecha: mar., feb. 7, 2012 10:03 Am 07.02.2012 06:02, schrieb Luis Carlos Busquets Pérez: > 1. If the functions returns E_FAIL for a sample then > test_effect.c:1917: Test failed: Got result 80004005, expected 0 (D3D_OK) I'll have a look at those. > 2. For D3DXPT_VERTEXSHADER and D3DXPT_PIXELSHADER replying with E_FAIL > avoids > test_effect.c:1812: Test failed: Got result 0, expected 0x80004005 > (E_FAIL) > test_effect.c:1814: Test failed: Got result 0, expected 0x80004005 > (E_FAIL) > test_effect.c:1881: Test failed: Got result 0, expected 0x80004005 > (E_FAIL) Sure, that's not implemented, yet. You should get a FIXME for those cases. > 3. If the function just sets the memory with the data for a bool then > test_effect.c:969: Test failed: Got 46, expected 1 In this case it may be required, that the input has to be converted before it is put into data. A solution would be to use Set*Array to set the values. In general, I think it's also fine to convert the values in get_int() and get_float() in the case of D3DXPT_BOOL with get_bool(data) - I'll send a patch for this. But I also think a test to show, that the value is converted while it is set, is still the way to go. Well SetValue isn't complete, yet. > 5. Concerning textures, the compiler does not accept arrays of textures, > so any change to a texture type should be just a change of the pointer > to the texture at param->data (or NULL) I didn't got the point. Only that it is impossible to declare texture arrays in effect files, which I could confirm. Do you mean, that the HeapAlloc for the additional pointer for textures should be avoided? This could be done, it just needs separate handling for textures. As it is now, it mostly uses the same handling together with the shaders (e.g. IUnknown_Release(*(IUnknown **)param->data)). Cheers Rico

1 0

Re: ID3DXBaseEffect::SetValue
by luis.busquets＠ilidium.com Feb. 7, 2012

Feb. 7, 2012

Concerning the vertrd a picel shadet, the truth is that sin e very soon in the history of d3dx the functions ID3DXEffect::SetPixelShader and ID3DXEffect::DetVertexShader wete removed. So actually it does not seem that you can change them. Because of that, the MS implementation replies with D3DERR_INVALIDCALL and their implementation in SetValue is straight. ----- Reply message ----- De: "Rico Schüller" <kgbricola(a)web.de> Para: "Luis Carlos Busquets Pérez" <luis.busquets(a)ilidium.com> CC: <wine-devel(a)winehq.org> Asunto: ID3DXBaseEffect::SetValue Fecha: mar., feb. 7, 2012 10:03 Am 07.02.2012 06:02, schrieb Luis Carlos Busquets Pérez: > 1. If the functions returns E_FAIL for a sample then > test_effect.c:1917: Test failed: Got result 80004005, expected 0 (D3D_OK) I'll have a look at those. > 2. For D3DXPT_VERTEXSHADER and D3DXPT_PIXELSHADER replying with E_FAIL > avoids > test_effect.c:1812: Test failed: Got result 0, expected 0x80004005 > (E_FAIL) > test_effect.c:1814: Test failed: Got result 0, expected 0x80004005 > (E_FAIL) > test_effect.c:1881: Test failed: Got result 0, expected 0x80004005 > (E_FAIL) Sure, that's not implemented, yet. You should get a FIXME for those cases. > 3. If the function just sets the memory with the data for a bool then > test_effect.c:969: Test failed: Got 46, expected 1 In this case it may be required, that the input has to be converted before it is put into data. A solution would be to use Set*Array to set the values. In general, I think it's also fine to convert the values in get_int() and get_float() in the case of D3DXPT_BOOL with get_bool(data) - I'll send a patch for this. But I also think a test to show, that the value is converted while it is set, is still the way to go. Well SetValue isn't complete, yet. > 5. Concerning textures, the compiler does not accept arrays of textures, > so any change to a texture type should be just a change of the pointer > to the texture at param->data (or NULL) I didn't got the point. Only that it is impossible to declare texture arrays in effect files, which I could confirm. Do you mean, that the HeapAlloc for the additional pointer for textures should be avoided? This could be done, it just needs separate handling for textures. As it is now, it mostly uses the same handling together with the shaders (e.g. IUnknown_Release(*(IUnknown **)param->data)). Cheers Rico

1 0

Re: comctl32: Remove an obsolete resource attribute.
by Marvin Feb. 7, 2012

Feb. 7, 2012

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=16849 Your paranoid android. === WNT4WSSP6 (32 bit) === No test summary line found === W2KPROSP4 (32 bit) === No test summary line found === WXPPROSP3 (32 bit) === No test summary line found === W2K3R2SESP2 (32 bit) === No test summary line found === WVISTAADM (32 bit) === No test summary line found === W2K8SE (32 bit) === No test summary line found === W7PRO (32 bit) === No test summary line found === W7PROX64 (32 bit) === No test summary line found === TEST64_W7SP1 (32 bit) === No test summary line found === W7PROX64 (64 bit) === No test summary line found === TEST64_W7SP1 (64 bit) === No test summary line found

2 1

ID3DXBaseEffect::SetValue
by Luis Carlos Busquets Pérez Feb. 7, 2012

Feb. 7, 2012

The functin returns D3DERR_INVALIDCALL whenever it is tried on a parameter with elements. A check should be included. Luis

2 3

Re: user32: Only call SetWindowPos() in UpdateLayeredWindowIndirect() if needed. (try 5)
by Dmitry Timoshkov Feb. 7, 2012

Feb. 7, 2012

Adam Martinson <adam.r.martinson(a)gmail.com> wrote: > (We should not be calling SetWindowPos() in UpdateLayeredWindowIndirect() at all.) > Fixes bug 26924. Much better now, thanks. -- Dmitry.

1 0

Re: user32: Fix a couple of typos.
by Marvin Feb. 7, 2012

Feb. 7, 2012

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=16847 Your paranoid android. === TEST64_W7SP1 (32 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === TEST64_W7SP1 (64 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737

1 0

Re: user32: Only call SetWindowPos() in UpdateLayeredWindowIndirect() if needed. (try 5)
by Marvin Feb. 7, 2012

Feb. 7, 2012

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=16845 Your paranoid android. === WVISTAADM (32 bit msg) === Failure running script in VM: The specified guest user must be logged in interactively to perform this operation === TEST64_W7SP1 (32 bit win) === win.c:6825: Test failed: FlashWindowEx succeeded win.c:6836: Test failed: FlashWindowEx failed with -559038737 === TEST64_W7SP1 (64 bit win) === win.c:6825: Test failed: FlashWindowEx succeeded win.c:6836: Test failed: FlashWindowEx failed with -559038737

1 0

ID3DXEffect::SetValue
by Luis Carlos Busquets Pérez Feb. 6, 2012

Feb. 6, 2012

The current implementation includes a check on param->bytes >= bytes specifically: if (data && param->bytes >= bytes) { ... } So if bytes<param->bytes returns D3DERR_INVALIDCALL. However, the MS version does not act that way: If the parameter is shorter than the length of the data, then the data that fits in the parameter is put and returns D3D_OK Therefore, the check of the size should be eliminated and in memcpy instead of referring to bytes, it should refer to min(bytes, param->bytes) Luis

3 2

Re: (try2) quartz: AMFilterData_ParseFilterData returns a pointer to a pointer to filter data
by Marvin Feb. 6, 2012

Feb. 6, 2012

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=16838 Your paranoid android. === WINEBUILD (build) === Make failed

1 0

Re: [2/2] user32: RealChildWindowFromPoint should skip invisible windows.
by Marvin Feb. 6, 2012

Feb. 6, 2012

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=16834 Your paranoid android. === W2KPROSP4 (32 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === WXPPROSP3 (32 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === W2K3R2SESP2 (32 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === WVISTAADM (32 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === W2K8SE (32 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === W7PRO (32 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === W7PROX64 (32 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === TEST64_W7SP1 (32 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === W7PROX64 (64 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === TEST64_W7SP1 (64 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737

1 0

Re: [1/2] user32: Add a bunch of RealChildWindowFromPoint tests.
by Marvin Feb. 6, 2012

Feb. 6, 2012

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=16833 Your paranoid android. === W2KPROSP4 (32 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === WXPPROSP3 (32 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === W2K3R2SESP2 (32 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === WVISTAADM (32 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === W2K8SE (32 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === W7PRO (32 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === W7PROX64 (32 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === TEST64_W7SP1 (32 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === W7PROX64 (64 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737 === TEST64_W7SP1 (64 bit win) === win.c:6753: Test failed: FlashWindowEx succeeded win.c:6764: Test failed: FlashWindowEx failed with -559038737

1 0

Re: user32: Only call SetWindowPos() in UpdateLayeredWindowIndirect() if needed. (try 4)
by Dmitry Timoshkov Feb. 6, 2012

Feb. 6, 2012

Adam Martinson <adam.r.martinson(a)gmail.com> wrote: > (We should not be calling SetWindowPos() in UpdateLayeredWindowIndirect() at all.) > Fixes bug 26924. That's not what I was asking about (a bunch of message tests with various parameters). Your current version essentially tests nothing. You should call UpdateLayeredWindowIndirect with a buch of differnt parameters, and check what message sequence they produce and how they change window state. See dlls/user32/tests/msg.c how to create a message test. -- Dmitry.

2 2

Re: [PATCH] [Kernel32]: added a couple of tests about console creation through CreateFile, and fix some corner cases
by Marvin Feb. 5, 2012

Feb. 5, 2012

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=16816 Your paranoid android. === W7PRO (32 bit console) === console.c:1173: Test failed: Expected CreateFileW to succeed for index 0 console.c:1173: Test failed: Expected CreateFileW to succeed for index 2 console.c:1173: Test failed: Expected CreateFileW to succeed for index 7 console.c:1173: Test failed: Expected CreateFileW to succeed for index 9 === W7PROX64 (32 bit console) === console.c:1173: Test failed: Expected CreateFileW to succeed for index 0 console.c:1173: Test failed: Expected CreateFileW to succeed for index 2 console.c:1173: Test failed: Expected CreateFileW to succeed for index 7 console.c:1173: Test failed: Expected CreateFileW to succeed for index 9 === TEST64_W7SP1 (32 bit console) === console.c:1173: Test failed: Expected CreateFileW to succeed for index 0 console.c:1173: Test failed: Expected CreateFileW to succeed for index 2 console.c:1173: Test failed: Expected CreateFileW to succeed for index 7 console.c:1173: Test failed: Expected CreateFileW to succeed for index 9 === W7PROX64 (64 bit console) === console.c:1173: Test failed: Expected CreateFileW to succeed for index 0 console.c:1173: Test failed: Expected CreateFileW to succeed for index 2 console.c:1173: Test failed: Expected CreateFileW to succeed for index 7 console.c:1173: Test failed: Expected CreateFileW to succeed for index 9 === TEST64_W7SP1 (64 bit console) === console.c:1173: Test failed: Expected CreateFileW to succeed for index 0 console.c:1173: Test failed: Expected CreateFileW to succeed for index 2 console.c:1173: Test failed: Expected CreateFileW to succeed for index 7 console.c:1173: Test failed: Expected CreateFileW to succeed for index 9

1 0