- wine-devel - winehq.org

Re: [PATCH] d3drm: Retreive mesh name at loading time. Implement GetName and SetName. (try 5) (resend)
by Alexandre Julliard 09 May '12

09 May '12

Christian Costa <titan.costa(a)gmail.com> writes: > Try 5: Use a growing buffer to store name. I don't think a growing buffer makes sense for this. > + if (name) > + { > + *size = min(*size, This->name_size); > + memcpy(name, This->name, *size); > + /* Make sure we have the terminating 0 in case of truncation */ > + name[*size] = 0; Buffer overflow. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: Ubuntu 12.04 (version#2, drop previous mail)
by Eric Pouech 09 May '12

09 May '12

> This is because you _cannot_ install the 32-bit -dev packages onto > 12.04. It's not just symlinks that are missing, many of the header > files are different between the arches. I'm not sure this is a generic rule, and if it were, then exclusion between i386 and x86_64 should be defined on most dev packages, and it's not the case also note, that in some cases, arch specific headers are moved to arch dependent directories (e.g. jpeg, glib...), which should also parallel install of multi-arch libs in any case, the job by ubuntu folks in 12.04 done is crappy, to say the least > Just do the chroot. You will save yourself so much grief and it will > actually work. if the ubuntu folks keep this state of mind, then they'll continue to sink the best solution is then to pick up another distro A+ -- -- Eric Pouech

3 4

Re: [2/5] gdi32: Set tmDigitizedAspectX/Y to 96 instead of 300 for consistency.
by Dmitry Timoshkov 08 May '12

08 May '12

Dmitry Timoshkov <dmitry(a)baikal.ru> wrote: > --- a/dlls/gdi32/freetype.c > +++ b/dlls/gdi32/freetype.c > @@ -6677,8 +6677,8 @@ static BOOL get_outline_text_metrics(GdiFont *font) > TM.tmWeight = pOS2->usWeightClass; > } > TM.tmOverhang = 0; > - TM.tmDigitizedAspectX = 300; > - TM.tmDigitizedAspectY = 300; > + TM.tmDigitizedAspectX = 96; /* FIXME */ > + TM.tmDigitizedAspectY = 96; /* FIXME */ A couple of comments to the patch: 1. the values should be set to the resolution of the target device, and 96 looks more natural since most of the time the device is a display. 2. the change is for consystency with get_bitmap_text_metrics() which sets these values to 96. 3. even if this pacth is rejected, other patches in the sequence should not be affected by it. -- Dmitry.

1 0

running 16bit code
by David Laight 08 May '12

08 May '12

Does wine support running of 16bit windows apps? If so does it rely on the underlying OS having support for 'virtual 8086 emulation'? I'm thinking of removing the VM86 support from NetBSD, and wine is about the only likley user. David -- David Laight: david(a)l8s.co.uk

5 5

Re: [PATCH 4/4] dmsynth: Add stubbed IKsControl interface to DirectMusicSynthSink object.
by Alexandre Julliard 08 May '12

08 May '12

Christian Costa <titan.costa(a)gmail.com> writes: > --- > dlls/dmsynth/dmsynth_private.h | 1 + > dlls/dmsynth/synthsink.c | 67 ++++++++++++++++++++++++++++++++++++++++ > 2 files changed, 68 insertions(+), 0 deletions(-) It fails here: ../../../tools/runtest -q -P wine -M dmsynth.dll -T ../../.. -p dmsynth_test.exe.so dmsynth.c && touch dmsynth.ok dmsynth.c:56: Test succeeded inside todo block: IDirectMusicSynthSink_QueryInterface returned: 0 make: *** [dmsynth.ok] Error 1 -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH 5/5] d3dcompiler: Partially implement D3DCompile function.
by Henri Verbeet 08 May '12

08 May '12

I realize compile_shader() is mostly a copy of assemble_shader(), but nevertheless: On 8 May 2012 16:17, Matteo Bruni <mbruni(a)codeweavers.com> wrote: > +struct bwriter_shader *parse_hlsl_shader(const char *text, enum shader_type type, DWORD version, If this isn't called outside of compiler.c it should be static. > + LPD3DBLOB buffer; "ID3DBlob *" > + CopyMemory(pos, preproc_messages, strlen(preproc_messages) + 1); memcpy() should do fine. > + hr = SlWriteBytecode(shader, 9, &res); ... > + size = HeapSize(GetProcessHeap(), 0, res); > + hr = D3DCreateBlob(size, &buffer); That's not very pretty, SlWriteBytecode() should probably just return the size as well.

2 1

Re: mscoree: Implement vtable fixups.
by Alexandre Julliard 08 May '12

08 May '12

Vincent Povirk <madewokherd(a)gmail.com> writes: > + if (fixup->fixup->type & COR_VTABLE_32BIT) > + { > + DWORD *vtable = fixup->vtable; > + DWORD *tokens = fixup->tokens; > + for (i=0; i<fixup->fixup->count; i++) > + { > + TRACE("%x\n", tokens[i]); > + vtable[i] = (DWORD)host->mono->mono_marshal_get_vtfixup_ftnptr( > + image, tokens[i], fixup->fixup->type); This will cause warnings on 64-bit. -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: kernel32: Add UTF-7 support
by Alex Henrie 08 May '12

08 May '12

2012/5/7 Ben Klein <shacklein(a)gmail.com>: > Without being a regular contributor, here are a few tips from a cursory glance: > 1) Whitespace change on at least one line The only change to whitespace I made was: - if( flags) + if (flags) I don't think this is a big deal. > 2) Why the change from ERROR_INVALID_PARAMETER to ERROR_INVALID_FLAGS? To match the behavior of Windows. I verified this with both MSDN and empirical tests. If the flags parameter is not null, all versions of Windows tested report ERROR_INVALID_FLAGS with the possible exception of Windows NT4. See http://testbot.winehq.org/JobDetails.pl?Key=18148 > 3) New function defs do not match format of surrounding defs in unicode.h This was a hard one. I didn't know if I should keep Katayama's use of INT or change the functions to use int like the UTF-8 functions do. So you're saying it should all be int? Do LPCSTR and LPCWSTR need to be changed to something else as well? > 4) No new tests to confirm the behaviour is correct (or mention of > current tests succeeding) dlls/kernel32/tests/locale.c already has just as many UTF-7 tests as it has UTF-8 tests. What tests do we need for UTF-7 which are not needed for UTF-8? Thanks for your quick response, -Alex

2 1

Re: msi: Tweak msiexec's usage message.
by Julian Rüger 07 May '12

07 May '12

Hi Francois and wine-devel, while we're at it, shouldn't these >"Advertise a product:\n" >"\t/j[u|m] package [/t transform] [/g languageid]\n" >"Apply a patch:\n" >"\t/p patch_package [property]\n" >"\t/p patch_package /a package [property]\n" also be put in curly brackets? Like this: \t/j[u|m] {package} [/t transform] ... \t/p {patch_package} [property]\n ... Best, Julian

3 3

Re: [Programs] Notepad: sync with ReactOS notepad (2)
by carlo.bramix＠libero.it 07 May '12

07 May '12

Hello friends, >> Because you do seriously believe that ReactOS developers reversed the >> Windows notepad?! Along with Solitaire & calculator, I suppose? >> Common sense is a powerful tool, let's make use of it :-). > >It's a matter of trust. If a person is known to use illegal practices >to write ReactOS code then even adding one line of code to notepad >makes her/his contribution dangerous for the entity accepting that code. > >> For the record, ReactOS as well disallows any person who has seen the >> Microsoft Windows code to comment, contribute, commit to the project. > >That's just a blanket statement, nothing more. It's hard to believe >to it if the person(s) publicly accused in using leaked code still >commit to ReactOS without any limitation. as I already wrote, I totally agree. Please reject the patches. Sincerely, Carlo Bramini.

1 0

Re: [Programs] Notepad: sync with ReactOS notepad (2)
by carlo.bramix＠libero.it 07 May '12

07 May '12

Hello friends, >The issue is whether the appropriate guidelines were followed >(http://wiki.winehq.org/CleanRoomGuidelines). One issue is that Wine >does not allow people that have ever viewed Microsoft source code to >contribute to Wine, but there are other issues. You'll have to talk >to Alexandre and see how he feels about this specific issue, but if >you've followed all of the guidelines and contribute only your own >changes then he might be ok with your contribution. I see. Perhaps it would be better to reject all these patches since I'm not the only author of all the changes. I understand that this is done to protect yourself and the project, because you do not know the people who touched the sources of the notepad, who they are and how they collected their information, so I agree with you. Sincerely, Carlo Bramini.

3 2

Re: [Programs] Notepad: sync with ReactOS notepad (2)
by carlo.bramix＠libero.it 06 May '12

06 May '12

Hello friends, >thank you for working on this. I think you will improve the chances for >your patches to be accepted if you give them individually meaningful >names, like > >"notepad: Don't use reserved MSVC keyword." > >for patch #2. Actually, I followed the tip I read into the wiki of WINE in "Patch submission guidelines", so I tried to imitate the style of other patches for WINE and for this reason I used an identical title with a progressive number as subject. If something different is prefered, no problem, I will follow your suggestion and I will use a more focused title. >Also, like Jerome said, we may have a problem if different people >commited these changes to ReactOS. I'm no expert on this, but as I >understand, Wine needs the patch to be credited to the author who >actually wrote the code. Well, ReactOS notepad had been imported from WINE long time ago and various people did some changes on it and I'm included in them since, in this specific case, the status bar implementation had been almost rewritten by me. I'm not an expert too, but since it is distribuited under the same license of WINE, with same coding restrictions and all people who sent patches have agreed to the same GPL as well, my intuition would say that there is no problem on this... because the owner who can providing this code to you is the ReactOS project itself. That's just my opinion of course... I will wait for your suggestions/orders... ;-) Sincerely, Carlo Bramini.

4 3

Re: [Programs] Notepad: sync with ReactOS notepad (2)
by Julian Rüger 06 May '12

06 May '12

Hi Carlo, thank you for working on this. I think you will improve the chances for your patches to be accepted if you give them individually meaningful names, like "notepad: Don't use reserved MSVC keyword." for patch #2. Also, like Jerome said, we may have a problem if different people commited these changes to ReactOS. I'm no expert on this, but as I understand, Wine needs the patch to be credited to the author who actually wrote the code. (Can someone else please comment on this, if I am mistaken?) Best regards, Julian

1 0

Re: rpcrt4/tests: Fix build with PSDK headers.
by Marvin 05 May '12

05 May '12

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=18238 Your paranoid android. === WNT4WSSP6 (32 bit ndr_marshall) === ndr_marshall: unhandled exception c0000005 at 004081C6

1 0

Re: [Programs] Notepad: sync with ReactOS notepad
by Jerome Leclanche 05 May '12

05 May '12

On Sat, May 5, 2012 at 2:15 PM, carlo.bramix(a)libero.it < carlo.bramix(a)libero.it> wrote: > Attached patch synces the WINE's notepad with the improvements added into > ReactOS' Notepad. > > - Imported status bar implementation, it fixes Bug #18715. New menu voice > has > been introduced into the resource file. > This is the biggest part of the patch, that it caused to touch all files > modified by the patch. > Other minor fixes included here are: > > - Implemented GOTO function. Since its menu voice has been added into the > resource file when adding support the statusbar, the related dialog box > and the > source code have been introduced too. > > - Find/Replace functions have an extremely similar behavior, so the job > can be > implemented with a single function. > > - Find and Find next commands must be grayed if there is not a text to > search > into. > > - The "class" word is a reserved keyword in MSVC, so I also imported the > fix > into the creation of the class of the window: "class" has been replaced > with > "wndclass", no code change. > > Sincerely, > > Carlo Bramini > > It's not going to be accepted as one big patch. It needs to be split. Also, are you the author of all the patches or are these other contributors for this? J. Leclanche

1 0

Re: kernel32: add more tracing to GetDiskFreeSpaceW
by Dmitry Timoshkov 05 May '12

05 May '12

Austin English <austinenglish(a)gmail.com> wrote: > @@ -1687,6 +1689,8 @@ BOOL WINAPI GetDiskFreeSpaceW( LPCWSTR root, LPDWORD cluster_sectors, > if (sector_bytes) *sector_bytes = info.BytesPerSector; > if (free_clusters) *free_clusters = info.AvailableAllocationUnits.u.LowPart; > if (total_clusters) *total_clusters = info.TotalAllocationUnits.u.LowPart; > + TRACE("%u, %u, %u, %u, capped=%d\n", cluster_sectors ? *cluster_sectors : 0, sector_bytes ? *sector_bytes : 0, > + free_clusters ? *free_clusters : 0, total_clusters ? *total_clusters : 0, capped); Why not print in the values directly from info structure? That way all the data are in the trace regardless of what info appication requested. I'd guess that printing valus in hex would be more readable, and once the data is printed in hex it should be obvious when the values were capped, making 'capped' flag redundant. -- Dmitry.

1 0

Re: [2/5] msvcm80: Add stub dll.
by Charles Davis 04 May '12

04 May '12

On May 4, 2012, at 10:07 AM, Vincent Povirk wrote: > > <0002-msvcm80-Add-stub-dll.txt> msvcmrt? The Managed C++ Runtime DLL? I imagine you won't get far on that without a C++/CLI compiler that understands the Microsoft Visual C++ ABI--unless you're willing to write all the marshaling glue code by hand. There's only one such compiler right now, and it only runs on Windows. VC++ ABI support is on my Clang to-do list--heck, it's my GSoC project--but C++/CLI is something I won't get to for a while. Given all that, how do you intend to implement this? Chip

2 2

Re: [2/5] msvcm80: Add stub dll.
by Stefan Dösinger 04 May '12

04 May '12

3 2

Re: [5/5] msvcm80: Add __setusermatherr_m stub.
by Charles Davis 04 May '12

04 May '12

On May 4, 2012, at 10:10 AM, Vincent Povirk wrote: > diff --git a/dlls/msvcm80/msvcm80_main.c b/dlls/msvcm80/msvcm80_main.c > index cd38f5b..eb09898 100644 > --- a/dlls/msvcm80/msvcm80_main.c > +++ b/dlls/msvcm80/msvcm80_main.c > @@ -50,3 +50,10 @@ void __cdecl CrtImplementationDetails_RegisterModuleUninitializer(void* handler) > FIXME("%p: stub\n", handler); > } > > +/* handler is a "method" with signature int32 (*handler)(_exception*), but I'm > + * not sure what that means */ I am. Actually, it's: int (__clrcall *handler)(struct _exception *) i.e. a "pointer to a function intended to be called from managed code that takes a pointer to a struct _exception and returns an int." The definition of struct _exception is in <math.h> under Visual Studio. To write such a function, you'd need a C++/CLI compiler. Chip

1 0

Wine Gecko 1.6-beta1
by Jacek Caban 04 May '12

04 May '12

Hi all, I've uploaded a beta version of another Gecko update. Other than usual Gecko changes coming from Mozilla (for upcoming Firefox 13), it contains fixes for Wine bugs 30465 and 25243. To try it, as usually, the attached patch is required as well as the build that may be found on SourceForge [1], installed in usual way [2] (or your own build, it's easy those days! See wine-gecko-1.6 branch on [3]). All help with testing is appreciated! Thanks, Jacek [1] http://sourceforge.net/projects/wine/files/Wine%20Gecko/1.6-beta1/ [2] http://wiki.winehq.org/Gecko [3] http://wine.git.sourceforge.net/git/gitweb.cgi?p=wine/wine-gecko;a=summary

1 0

Re: [PATCH 1/2] jscript: Skip failing tests on old jscript versions
by Marvin 04 May '12

04 May '12

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=18229 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

1 0

Re: po: English (neutral / Great Britain) spelling fixes.
by Nicolas Le Cam 03 May '12

03 May '12

Le 3 mai 2012 02:45, "Francois Gouget" <fgouget(a)free.fr> a écrit : > @@ -9429,9 +9429,9 @@ msgstr "" > "start [options] document_filename\n" > "\n" > "Options:\n" > -"/M[inimized] Start the program minimized.\n" > -"/MAX[imized] Start the program maximized.\n" > -"/R[estored] Start the program normally (neither minimized nor maximized).\n" > +"/M[inimized] Start the program minimised.\n" > +"/MAX[imized] Start the program maximised.\n" > +"/R[estored] Start the program normally (neither minimised nor maximised).\n" > "/W[ait] Wait for started program to finish, then exit with its exit " > "code.\n" > "/Unix Use a Unix filename and start the file like windows explorer.\n" Hi Francois, Shouldn't the end of words between brackets be translated too ? -- Nicolas Le Cam

3 3

Re: [3/5] d3dx9: Implement D3DXSaveSurfaceToFileW.
by Henri Verbeet 03 May '12

03 May '12

On 2 May 2012 23:32, Józef Kucia <joseph.kucia(a)gmail.com> wrote: > + if(wic_pixel_formats[i].d3dformat == format) Missing whitespace. > +HRESULT WINAPI D3DXSaveSurfaceToFileW(LPCWSTR dst_filename, D3DXIMAGE_FILEFORMAT file_format, "LPCWSTR" -> "const WCHAR *" > + TRACE("(%s, %d, %p, %p, %p)\n", > + wine_dbgstr_w(dst_filename), file_format, src_surface, src_palette, src_rect); wine_dbgstr_rect(). > + memcpy(&wic_pixel_format, pixel_format_guid, sizeof(GUID)); > + hr = IWICBitmapFrameEncode_SetPixelFormat(frame, &wic_pixel_format); > + d3d_pixel_format = wic_guid_to_d3dformat(&wic_pixel_format); What is all this for? Also, how do you intend to implement D3DXSaveSurfaceToFileInMemory()?

2 2

Re: [2/5] d3dx9: Forward D3DXSaveSurfaceToFileA to D3DXSaveSurfaceToFileW.
by Henri Verbeet 03 May '12

03 May '12

On 2 May 2012 23:32, Józef Kucia <joseph.kucia(a)gmail.com> wrote: > +HRESULT WINAPI D3DXSaveSurfaceToFileA(LPCSTR dst_filename, D3DXIMAGE_FILEFORMAT file_format, > + IDirect3DSurface9 *src_surface, const PALETTEENTRY *src_palette, const RECT *src_rect) If you're changing these anyway, LPCSTR is a broken way of saying "const char *". > + TRACE("(%s, %d, %p, %p, %p): relay\n", > + wine_dbgstr_a(dst_filename), file_format, src_surface, src_palette, src_rect); I generally prefer %#x for things like file_format, but don't care particularly strongly. For src_rect you should use %s and wine_dbgstr_rect(). I don't care much for the "relay" suffix, but I suppose half the existing code has it as well. > + len = MultiByteToWideChar(CP_ACP, 0, dst_filename, -1, NULL, 0); > + filename = HeapAlloc(GetProcessHeap(), HEAP_ZERO_MEMORY, len * sizeof(WCHAR)); The HEAP_ZERO_MEMORY flag is useless, you're immediately going to overwrite all the memory afterwards. Sadly the existing d3dx9 code isn't a very good example here either.

1 0

Request for help/advice in investigation of one interesting "huge FPS regression" bug
by Alexey Loukianov 03 May '12

03 May '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Good day to all. Henri, Stefan, I address this message to you at the first place as to a main developers of wined3d/opengl stuff. Nevertheless, hints and help are welcome from anyone, cause ATM I'm totally confused and don't know what else to try to investigate a case. What I've got here is an app (localized version of "Perfect World" MMORPG game client from "Mail.Ru Games Corp") that seems to suffer huge FPS regression which I believe to be a bug in nVIDIA drivers rather than a regression in Wine. Details are following. When I configure an app to run in a windowed mode I've got around 40 FPS on game login screen with nVIDIA drivers 275.09.07, but switching into using more recent versions causes FPS to drop to around ~10. Configuring the game to use fullscreen more fixes the issue - I've got ~30-40 FPS at game login screen no matter the driver version I use. I've been suspecting that this issue might be related to vsync control (and a recent change in nVIDIA linux drivers for vsync to be on by default) that causes the issue, so I had exported __GL_SYNC_TO_VBLANK="0" into the environment and used nvidia-settings to set vsync to be off by default. Using a small native opengl demo program I had specifically written to test for vsync state I can prove that vsync defaults to be off on my system. Also I had modified Wine's winex11.drv opengl.c in a way that a call to wglSwapIntervalEXT always sets swap_interval to be zero, no matter what was originally requested. Nevertheless, I still got this strange FPS drop when I run the game in a windowed more with a recent nVIDIA drivers. What could be a cause for it? What I want is to track down the problem to it's roots and check if it's really a bug in nVIDIA drivers. In the end I would like to implement a small opengl demo that would trigger the bug so nVIDIA wouldn't be able to reject my bug report on a matter that "it's a Wine bug, prove us that it's not". - -- Best regards, Alexey Loukianov mailto:mooroon2@mail.ru System Engineer, Mob.:+7(926)218-1320 *nix Specialist -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPij76AAoJEPB9BOdTkBULjz4H/1B/Nw6qOQUlEmDb64SmabvQ LQmzIHcnH38Ftz3KyWQxlYZ5EtLDYAIOQeP4pAHfzxKhGUJ1mCumv4ByaSs4YDhI juWJ/u/88vKwZYXJ9nZLQVqJY+dkr9MbxP3q0eGNaAFLNRDIqodzJJWB5EPucMrX Yid/zMjl5uGd9QDCO3Db4gwJKYpvHCbAfzADddqBwPoak9jXdlq53H9a2mImTbCB JR1MXQq6gFakOgtxXPxzFSU2Ge0n8RBGGN7UeZEubsLiktnmvTbKAJmmgWgPG80Y mlud7LrM4wLRPtpwTwS+M1n8TuVtUZzzCTagRyj3XSRL8Pqf2d5S3H+MpxBT1JQ= =TkMD -----END PGP SIGNATURE-----

5 8

Re: [PATCH 5/9] jscript: Better handling of to_integer result in String.lastIndexOf
by Marvin 03 May '12

03 May '12

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=18203 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

1 0

Re: [PATCH 4/9] jscript: Bettter handling of to_number result in String.indexOf
by Marvin 03 May '12

03 May '12

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=18202 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

1 0

Re: [PATCH 3/9] jscript: Better handling of to_integer result in String.charCodeAt
by Marvin 03 May '12

03 May '12

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=18201 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

1 0

Re: [PATCH 2/9] jscript: Better handling of to_integer result in String.charAt
by Marvin 03 May '12

03 May '12

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=18200 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

1 0

Re: [PATCH 1/9] jscript: Better handling of to_integer result in Array.splice
by Marvin 03 May '12

03 May '12

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=18199 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

1 0

Re: [PATCH 2/2] d3drm: Implement IDirect3DRMFrameX_GetChildren method and IDirect3DRMFrameArray interface. (try 2) (resend)
by Marvin 03 May '12

03 May '12

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

1 0

Building 64 & 32 bit wine on Ubuntu 12.10?
by Dan Kegel 03 May '12

03 May '12

What's the standard procedure for building both 32 and 64 bit wine together on Ubuntu 12.10? Sadly, it seems you can't install both 32 and 64 bit development files at the same time. And trying to use a 32 bit chroot is awkward because wine's build system tries to use the 64 bit makedep from inside the 32 bit chroot (which fails because the 64 bit shared libraries aren't present).

2 1

GSOC 2012 has started
by Austin English 02 May '12

02 May '12

Howdy, Google Summer of Code 2012 has started, and we have 5 students this year: Józef Kucia - Implement missing functions in D3DX9, mentored by Stefan Dösinger - https://google-melange.appspot.com/gsoc/project/google/gsoc2012/jos/58002 Lucas Fialho Zawacki, mentored by Joystick configuration and testing applet Marcus Meissner - https://google-melange.appspot.com/gsoc/project/google/gsoc2012/lfzawacki/3… Magdalena Nowak - Control Panel, mentored by Owen Rudge - https://google-melange.appspot.com/gsoc/project/google/gsoc2012/magdalena/1… Marek K Chmiel - Encryption – digital signature security, mentored by Juan Lang - https://google-melange.appspot.com/gsoc/project/google/gsoc2012/mkchmiel/16… Qian Hong - GSoC project: Improve CJK font support, mentored by Aric Stewart - https://google-melange.appspot.com/gsoc/project/google/gsoc2012/fracting/11… Good luck everyone! -- -Austin

3 3

Re: [PATCH] include: Add definition of IKsControl interface in dmksctrl.h.
by Alexandre Julliard 02 May '12

02 May '12

Christian Costa <titan.costa(a)gmail.com> writes: > +typedef struct { > + union { > + struct { > + GUID Set; > + ULONG Id; > + ULONG Flags; > + }; > + LONGLONG Alignment; > + }; > +} KSIDENTIFIER, *PKSIDENTIFIER; Check how anonymous unions/structs are done in other headers. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH] dmusic: Midi message takes 4 bytes space but only 3 are relevant + add tests to check buffer content.
by Alexandre Julliard 02 May '12

02 May '12

Christian Costa <titan.costa(a)gmail.com> writes: > +static inline char* debugstr_longlong(LONGLONG val) > +{ > + static char string[17]; > + sprintf(string, "%08x%08x", *((DWORD*)&val + 1), *(DWORD*)&val); > + return string; Check how this is done in other places. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: kernel32/tests: Add tests for K32GetModuleFileNameEx (try 2)
by Alexandre Julliard 02 May '12

02 May '12

Bruno Jesus <00cpxxx(a)gmail.com> writes: > try2: > Based on latest git > > Tests intended as complement for the buffer overflow fix from > > http://source.winehq.org/git/wine.git/commitdiff/fd11023e4b44b18af7f9d44b21… This should be merged with the existing psapi tests. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [1/5] d3dx9: Implement mapping from WICPixelFormat GUIDs to D3DFORMATs.
by Stefan Dösinger 02 May '12

02 May '12

It looks like patch 2 is missing

2 1

Re: [1/5] d3dx9: Implement mapping from WICPixelFormat GUIDs to D3DFORMATs.
by Stefan Dösinger 02 May '12

02 May '12

Am Mittwoch, 2. Mai 2012, 14:55:35 schrieb Józef Kucia: > +static const struct > +{ > + const GUID *wic_guid; > + D3DFORMAT d3dformat; > +} wic_pixel_formats[] = { Wouldn't it make sense to include this info in PixelFormatDesc?

2 1

Re: [PATCH 2/2] mshtml: Added IHTMLWindow2::get_history implementation
by Marvin 02 May '12

02 May '12

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=18178 Your paranoid android. === WXPPROSP3 (32 bit dom) === dom.c:4490: Test failed: unexpected guid {FECEAAA2-8405-11CF-8BA1-00AA00476DA6} === WVISTAADM (32 bit dom) === dom.c:4490: Test failed: unexpected guid {FECEAAA2-8405-11CF-8BA1-00AA00476DA6} === W2K8SE (32 bit dom) === dom.c:4490: Test failed: unexpected guid {FECEAAA2-8405-11CF-8BA1-00AA00476DA6}

1 0

Find Wine software installer
by Shanuka Wijekoon 01 May '12

01 May '12

haiiii I have a problem that i need to track the software installation.that means I need to keep the location where the files are installed. Are there any place in wine source code to get help for my problem. thank you.

2 1

Re: kernel32/tests: Add tests for K32GetModuleFileNameEx
by Bruno Jesus 01 May '12

01 May '12

On Tue, May 1, 2012 at 02:34, Bruno Jesus <00cpxxx(a)gmail.com> wrote: > Add some tests required for http://bugs.winehq.org/show_bug.cgi?id=30543 Please, ignore this patch. It was based on old git. Apologies, Bruno

1 0

Re: [PATCH 4/4] amstream: Add stubbed implementation of AudioStreamSample. (try 2) (resend)
by Marvin 01 May '12

01 May '12

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

1 0

Re: [PATCH 3/4] amstream: Add stubbed implementation of DirectDrawStreamSample. (try 2) (resend)
by Marvin 01 May '12

01 May '12

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

1 0

Re: [PATCH 1/4] dmusic: Add tests to enumerate master clocks.
by Marvin 01 May '12

01 May '12

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

1 0

Fwd: Ubuntu 12.04 (version#2, drop previous mail)
by Eric Pouech 01 May '12

01 May '12

for the devels having upgraded their boxes to ubuntu 12.04, here's a couple of stuff I had to do, especially to get 32bit wine compile This could be useful if you want to have a dual x86_64 : i386 setup this is an updated version to what I already sent to scott ritchie of course this is not a step by step installation, just hints if you want to take that road (version #3) (I'm using a multiarch x86_64/i386) now wine compiles and runs in 32bit while compiled on 64bit machine here's the summary of the pain getting it right after upgrade in response to https://bugs.launchpad.net/ubuntu/+source/wine1.4/+bug/944321 I was able to compile 32bit-wine on 64bit as I always, and without a chroot or anything similar Problem #1 ---------- an old (11.10 according to the dates) directory was left over after migration, whereas it should have been removed /usr/include/i386-linux-gnu Problem #2 ---------- a ton of symlinks are missing in /usr/lib/i386-linux-gnu for example [root:/usr/lib/i386-linux-gnu]# ls -l /usr/lib/i386-linux-gnu/libfree* lrwxrwxrwx 1 root root 20 avril 3 10:54 /usr/lib/i386-linux-gnu/libfreetype.so.6 -> libfreetype.so.6.8.0 -rw-r--r-- 1 root root 624084 avril 3 10:54 /usr/lib/i386-linux-gnu/libfreetype.so.6.8.0 and it misses lrwxrwxrwx 1 root root 16 avril 28 21:30 /usr/lib/i386-linux-gnu/libfreetype.so -> libfreetype.so.6 the same applies for a lot libraries libXcursor.so libXi.so libXxf86vm.so libxrandr.so libxinerama.so libxcomposite.so libGLU.so libdbus-1.so (libdbus-1.so lies in /lib/i386-linux-gnu, not /usr/lib/i386-linux-gnu) libgnutls.so libsane.so libv4l1.so libgphoto2.so libgphoto2_port.so libgstreamer-0.10.so (***) libcapi20.so libcups.so libfontconfig.so libtiff.so libmpg123.so libopenal.so libxrender.so libGL.so (libGL.so is in mesa subdir!!!) libxml2.so libxslt.so libssl.so libcrypto.so libjpeg.so (***) libpng.so.0 (libpng12.so.0 lies in /lib/i386-linux-gnu, not /usr/lib/i386-linux-gnu) libXext.so the ones marked (***) means that the symlink is missing but it doesn't solve fully the issue from a wine perspective (see below) Problem #3 (jpeg) ----------------- Fails to open<jconfig.h>. which only lies in /usr/include/x86_64-linux-gnu/jconfig.h, and couldn't be accessed from 32bit build Creating the /usr/include/i386-linux-gnu/ directory and creating a symlink for jconfig.h to /usr/include/x86_64-linux-gnu/jconfig.h just works (I checked the contents of jconfig.h and it looks reasonable to do so) Problem #4 (gstreamer) ---------------------- it doesn't work as only /usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h is installed (/usr/lib/i386-linux-gnu/glib-2.0/include/glibconfig.h doesn't exist, dpkg -S doesn't find it) and /usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h defines gint64 as long, which is correct on 64bit targets one wrong on 32 bit ones... one should craft a decent /usr/lib/i386-linux-gnu/glib-2.0/include/glibconfig.h, or grab one out of pure i386 install (I haven't had time to look further into those, my main interest was to have a 32bit setup up& running) List of potentially installed i386 packages ------------------------------------------- fixed by installing i386 packages (not exhaustive, unfortunately, as I didn't note all the :i386 packages I've manually installed) libldap2.so alternatively, if I do a [eric:~]$ dpkg -l | grep i386 | grep -- -dev ii libc6-dev-i386 2.15-0ubuntu10 Embedded GNU C Library: 32-bit development libraries for AMD64 ii libldap2-dev:i386 2.4.28-1.1ubuntu4 OpenLDAP development libraries ii libpthread-stubs0-dev:i386 0.3-3 pthread stubs not provided by native libc, development files ii libx11-dev:i386 2.1.4.99.1-0ubuntu2 X11 client-side library (development headers) ii libxau-dev:i386 1:1.0.6-4 X11 authorisation library (development headers) ii libxcb1-dev:i386 1.8.1-1 X C Binding, development files ii libxdmcp-dev:i386 1:1.1.0-4 X11 authorisation library (development headers) tends to ask for libc6-dev:i386, libldap2-dev:i386, libx11-dev:i386, libxau-dev:i386, libxcb1-dev:i386, libxdmcp-dev:i386 as dedicated installations of dev:i386 packages but strangely enough, when looking at details, libx11-dev (for example) cannot be installed with libx11-dev:i386 according to manifest, but I have both installed (and both install the same files in /usr/include for example) this looks very strange indeed List of stuff that won't work ----------------------------- won't be supported (just to note them, as those are the left overs from the configure failing list) compiled without multiarch support: libhal, libgsm Warning at compilation ---------------------- when compiling, some warnings still have to be worked upon /home/eric/work/wine/dlls/winex11.drv/keyboard.c:1109:5: warning: 'XKeycodeToKeysym' is deprecated (declared at /usr/include/X11/Xlib.h:1695) [-Wdeprecated-declarations] this one can be forgotten for now (it's just being marked deprecated in precise, so warning doesn't come from misconfiguration) debugging (32bit and 64bit) is broken ------------------------------------- the debugging is broken it turns out that ptrace and prctl (which had to be added in 11.10) work fine when tracing, only the first started process get correct pid out of wineserver in socket SCM_CREDENTIALS info. the later get 0 I tried to force the pid without requiring the recvmsg stuff and it works just fine I've not found yet the change that broke this more to come if get any futher on the remaining topics A+ -- Eric Pouech "The problem with designing something completely foolproof is to underestimate the ingenuity of a complete idiot." (Douglas Adams)

5 7

Re: [PATCH 4/4] ws2_32/tests: Test for IOCP behavior without AcceptEx call (resend).
by Marvin 01 May '12

01 May '12

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=18138 Your paranoid android. === W7PROX64 (64 bit sock) === sock.c:5628: Test failed: Internal status is c0000120 === TEST64_W7SP1 (64 bit sock) === sock.c:5628: Test failed: Internal status is c0000120

1 0

Re: [PATCH 3/4] ws2_32/tests: Test for AcceptEx IOCP behavior for a duplicated handle (try 2).
by Marvin 01 May '12

01 May '12

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=18137 Your paranoid android. === W7PROX64 (64 bit sock) === sock.c:5628: Test failed: Internal status is c0000120 === TEST64_W7SP1 (64 bit sock) === sock.c:5628: Test failed: Internal status is c0000120

1 0

Re: [PATCH 4/4] ws2_32/tests: Test for IOCP behavior without AcceptEx call.
by Marvin 01 May '12

01 May '12

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=18134 Your paranoid android. === WVISTAADM (32 bit sock) === sock.c:5628: Test failed: Internal status is c0000120 === W2K8SE (32 bit sock) === sock.c:5628: Test failed: Internal status is c0000120 === W7PRO (32 bit sock) === sock.c:5628: Test failed: Internal status is c0000120 === W7PROX64 (32 bit sock) === sock.c:5628: Test failed: Internal status is c0000120 === TEST64_W7SP1 (32 bit sock) === sock.c:5628: Test failed: Internal status is c0000120 === W7PROX64 (64 bit sock) === sock.c:5628: Test failed: Internal status is c0000120 === TEST64_W7SP1 (64 bit sock) === sock.c:5628: Test failed: Internal status is c0000120

1 0

Re: [PATCH 3/4] ws2_32/tests: Test for AcceptEx IOCP behavior for a duplicated handle.
by Marvin 01 May '12

01 May '12

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=18133 Your paranoid android. === WVISTAADM (32 bit sock) === sock.c:5628: Test failed: Internal status is c0000120 === W2K8SE (32 bit sock) === sock.c:5628: Test failed: Internal status is c0000120 === W7PRO (32 bit sock) === sock.c:5628: Test failed: Internal status is c0000120 === W7PROX64 (32 bit sock) === sock.c:5628: Test failed: Internal status is c0000120 === TEST64_W7SP1 (32 bit sock) === sock.c:5628: Test failed: Internal status is c0000120 === W7PROX64 (64 bit sock) === sock.c:5628: Test failed: Internal status is c0000120 === TEST64_W7SP1 (64 bit sock) === sock.c:5628: Test failed: Internal status is c0000120

1 0

Patches 85862 & 85862
by Christian Costa 30 Apr '12

30 Apr '12

What's wrong with these patches : - http://source.winehq.org/patches/data/85862 - http://source.winehq.org/patches/data/85862 There are marked as pending but can't see anything wrong. Maybe I'm missing something. Christian

1 0

Re: [1/3] d3dx9: Define DDS structures. (try 3)
by Stefan Dösinger 30 Apr '12

30 Apr '12

The patches look good to me. Am Sonntag, 29. April 2012, 21:43:08 schrieb Józef Kucia: > This patch series implements the DDS support for D3DXGetImageInfo functions. > > Try 2: Define pitch as LONG. > Try 3: Revert it back to DWORD. > --- > dlls/d3dx9_36/surface.c | 66 > ++++++++++++++++++++++++++++++++++++++++++++++- 1 files changed, 65 > insertions(+), 1 deletions(-) > > diff --git a/dlls/d3dx9_36/surface.c b/dlls/d3dx9_36/surface.c > index 567282c..3319927 100644 > --- a/dlls/d3dx9_36/surface.c > +++ b/dlls/d3dx9_36/surface.c > @@ -28,9 +28,73 @@ WINE_DEFAULT_DEBUG_CHANNEL(d3dx); > > > /* Wine-specific WIC GUIDs */ > - > DEFINE_GUID(GUID_WineContainerFormatTga, > 0x0c44fda1,0xa5c5,0x4298,0x96,0x85,0x47,0x3f,0xc1,0x7c,0xd3,0x22); > > +/* dds_header.flags */ > +#define DDS_CAPS 0x1 > +#define DDS_HEIGHT 0x2 > +#define DDS_WIDTH 0x2 > +#define DDS_PITCH 0x8 > +#define DDS_PIXELFORMAT 0x1000 > +#define DDS_MIPMAPCOUNT 0x20000 > +#define DDS_LINEARSIZE 0x80000 > +#define DDS_DEPTH 0x800000 > + > +/* dds_header.caps */ > +#define DDS_CAPS_COMPLEX 0x8 > +#define DDS_CAPS_TEXTURE 0x1000 > +#define DDS_CAPS_MIPMAP 0x400000 > + > +/* dds_header.caps2 */ > +#define DDS_CAPS2_CUBEMAP 0x200 > +#define DDS_CAPS2_CUBEMAP_POSITIVEX 0x400 > +#define DDS_CAPS2_CUBEMAP_NEGATIVEX 0x800 > +#define DDS_CAPS2_CUBEMAP_POSITIVEY 0x1000 > +#define DDS_CAPS2_CUBEMAP_NEGATIVEY 0x2000 > +#define DDS_CAPS2_CUBEMAP_POSITIVEZ 0x4000 > +#define DDS_CAPS2_CUBEMAP_NEGATIVEZ 0x8000 > +#define DDS_CAPS2_VOLUME 0x200000 > + > +/* dds_pixel_format.flags */ > +#define DDS_PF_ALPHA 0x1 > +#define DDS_PF_ALPHA_ONLY 0x2 > +#define DDS_PF_FOURCC 0x4 > +#define DDS_PF_RGB 0x40 > +#define DDS_PF_YUV 0x200 > +#define DDS_PF_LUMINANCE 0x20000 > + > +struct dds_pixel_format > +{ > + DWORD size; > + DWORD flags; > + DWORD fourcc; > + DWORD bpp; > + DWORD rmask; > + DWORD gmask; > + DWORD bmask; > + DWORD amask; > +}; > + > +struct dds_header > +{ > + DWORD signature; > + DWORD size; > + DWORD flags; > + DWORD height; > + DWORD width; > + DWORD pitch_or_linear_size; > + DWORD depth; > + DWORD miplevels; > + DWORD reserved[11]; > + struct dds_pixel_format pixel_format; > + DWORD caps; > + DWORD caps2; > + DWORD caps3; > + DWORD caps4; > + DWORD reserved2; > +}; > + > + > /************************************************************ > * D3DXGetImageInfoFromFileInMemory > *

1 0

Re: wined3d: Fix build with MSVC (try 2).
by Stefan Dösinger 30 Apr '12

30 Apr '12

Am Samstag, 28. April 2012, 10:16:13 schrieb Thomas Faber: > Apparently NAN and INFINITE are C99 as well (I should really get a > version of the old standard instead of mostly reading C99 :|). > > How about a simple const variable that will trick MSVC, while not > changing semantics. How about a function in libs/port or a macro in one of its headers? I believe the NAN/INFINITE issue is not specific to wined3d. With the const variable, msvc compiles the code, but still produces a warning.

2 2

Re: [1/2] gdi32: GetGlyphOutline should fail for a bitmap font.
by Huw Davies 30 Apr '12

30 Apr '12

On Sat, Apr 28, 2012 at 05:52:13PM +0900, Dmitry Timoshkov wrote: > --- > dlls/gdi32/freetype.c | 6 ++++++ > dlls/gdi32/tests/font.c | 17 ++++++++++++----- > 2 files changed, 18 insertions(+), 5 deletions(-) This will break the display of bitmap fonts in winex11.drv . Do you have an app that depends on this? Huw.

2 1

Wine developer example sessions?
by Dan Kegel 27 Apr '12

27 Apr '12

I'm bringing a new intern up to speed, and while I was showing him how to diagnose one particular wine bug, I recorded the session on a web page, http://kegel.com/wine/bug30486.html It occurred to me that recorded sessions like that might be useful to other beginners (above and beyond the more structured wine developer doc), so I created http://wiki.winehq.org/DeveloperExamples and linked to it from there. Does that seem useful, and are there other tutorials that could be linked to?

2 2

Re: user32/tests: Update DlgDirList tests
by Bruno Jesus 27 Apr '12

27 Apr '12

On Sat, Apr 14, 2012 at 21:57, Bruno Jesus <00cpxxx(a)gmail.com> wrote: > Based on original patch from Christian Lupien from bug 8226. > > Tests required to later fix http://bugs.winehq.org/show_bug.cgi?id=8226 Is there anything else I could provide in helping to get this patch accepted? http://source.winehq.org/patches/data/85434 Regards, Bruno

1 0

Re: [1/3] d3dx9: Define DDS structures.
by Stefan Dösinger 27 Apr '12

27 Apr '12

Am Donnerstag, 26. April 2012, 11:47:51 schrieb Józef Kucia: > + DWORD pitch_or_linear_size; Are you aware that lPitch is a (signed) LONG in the original DDSURFACEDESC structure? Honestly I have no idea why, and I have never seen an app that passes a negative pitch, but it might lead to obscure bugs if it is not checked.

3 2

Re: [3/3] d3dx9: Implement conversion from DDS pixel format to D3DFORMAT.
by Matteo Bruni 26 Apr '12

26 Apr '12

Il 26 aprile 2012 11:47, Józef Kucia <joseph.kucia(a)gmail.com> ha scritto: > static D3DFORMAT dds_pixel_format_to_d3dformat(const struct dds_pixel_format *pixel_format) > { > - FIXME("Pixel format conversion not implemented.\n"); > + if (pixel_format->flags & DDS_PF_FOURCC) > + return dds_fourcc_to_d3dformat(pixel_format->fourcc); > + else if (pixel_format->flags & DDS_PF_RGB) > + return dds_rgb_to_d3dformat(pixel_format); > + else if (pixel_format->flags & DDS_PF_LUMINANCE) > + return dds_luminance_to_d3dformat(pixel_format); > + else if (pixel_format->flags & DDS_PF_ALPHA_ONLY) > + return dds_alpha_to_d3dformat(pixel_format); You don't need all those 'else's, the 'return's imply that you get there only when the 'if' condition isn't true. The same applies in other areas of this patch. I don't mind much, but since you have to resend the series anyway...

1 0

Re: [1/3] d3dx9: Define DDS structures.
by Henri Verbeet 26 Apr '12

26 Apr '12

Is there no header that should define these?

2 2

Re: [2/3] d3dx9: Add partial DDS support implementation for D3DXGetImageInfo functions.
by Henri Verbeet 26 Apr '12

26 Apr '12

On 26 April 2012 11:47, Józef Kucia <joseph.kucia(a)gmail.com> wrote: > +static HRESULT get_image_info_from_dds(LPCVOID buffer, DWORD length, D3DXIMAGE_INFO *info) Please avoid types like LPCVOID.

1 0

Re: [PATCH 1/2] amstream: Add stubbed implementation of DirectDrawStreamSample. (try 4)
by Marvin 26 Apr '12

26 Apr '12

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=18050 Your paranoid android. === WVISTAADM (32 bit amstream) === Failure running script in VM: The specified guest user must be logged in interactively to perform this operation

1 0

Re: gdiplus: GdipDrawString is not supposed to use the layout rectangle for clipping. Take 2.
by Dmitry Timoshkov 25 Apr '12

25 Apr '12

Dmitry Timoshkov <dmitry(a)baikal.ru> wrote: > There is a dedicated clip region in the graphics object. Please ignore that patch or mark it as rejected, the real problem has been fixed by 9b5b04c1c1a7b32dd3e1e453b6d739082c4ccede. -- Dmitry.

1 0

Re: [PATCH 1/2] amstream: Add stubbed implementation of DirectDrawStreamSample. (try 3)
by Alexandre Julliard 25 Apr '12

25 Apr '12

Christian Costa <titan.costa(a)gmail.com> writes: > Try3: Put sample stuff in stream_sample.c > Try2: Fix QueryInterface. It was better without creating a new file. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH 1/4] make_unicode: Create tables with data needed by nameprep algorithm
by Alexandre Julliard 25 Apr '12

25 Apr '12

Piotr Caban <piotr(a)codeweavers.com> writes: > + dump_nameprep_range($INPUT, $nameprep_flags{"unassigned"}, \@flags_table) if (/A.1/); > + dump_nameprep_range($INPUT, $nameprep_flags{"prohibited"}, \@flags_table) if (/C.1.2/); > + dump_nameprep_range($INPUT, $nameprep_flags{"prohibited"}, \@flags_table) if (/C.2.2/); > + dump_nameprep_range($INPUT, $nameprep_flags{"prohibited"}, \@flags_table) if (/C.3/); > + dump_nameprep_range($INPUT, $nameprep_flags{"prohibited"}, \@flags_table) if (/C.4/); > + dump_nameprep_range($INPUT, $nameprep_flags{"prohibited"}, \@flags_table) if (/C.5/); > + dump_nameprep_range($INPUT, $nameprep_flags{"prohibited"}, \@flags_table) if (/C.6/); > + dump_nameprep_range($INPUT, $nameprep_flags{"prohibited"}, \@flags_table) if (/C.7/); > + dump_nameprep_range($INPUT, $nameprep_flags{"prohibited"}, \@flags_table) if (/C.8/); > + dump_nameprep_range($INPUT, $nameprep_flags{"prohibited"}, \@flags_table) if (/C.9/); > + dump_nameprep_range($INPUT, $nameprep_flags{"bidi_ral"}, \@flags_table) if (/D.1/); > + dump_nameprep_range($INPUT, $nameprep_flags{"bidi_l"}, \@flags_table) if (/D.2/); > + > + dump_nameprep_map($INPUT, \@mapping_table) if (/B.1/); > + dump_nameprep_map($INPUT, \@mapping_table) if (/B.2/); These names are confusing, the functions are loading data not dumping it. > + for (my $i = 0; $i < 65536; $i++) > + { > + next unless defined $flags_table[$i]; > + $flags_table[$i] += $i; > + } > + > + open OUTPUT,">$filename.new" or die "Cannot create $filename"; > + print "Building $filename\n"; > + print OUTPUT "/* Nameprep algorithm related data */\n"; > + print OUTPUT "/* generated from $STRINGPREP */\n"; > + print OUTPUT "/* DO NOT EDIT!! */\n\n"; > + print OUTPUT "#include \"wine/unicode.h\"\n\n"; > + DUMP_CASE_TABLE( "nameprep_char_type", @flags_table ); It doesn't make sense to use a case table for this, it's just flags. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: vbscript: 'property' may be both keyword and identifier
by Marvin 25 Apr '12

25 Apr '12

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=18045 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

1 0

Re: [PATCH 1/3] server: Revise completion behavior to allow completions for cancelled sockets (try 2).
by Alexandre Julliard 24 Apr '12

24 Apr '12

"Erich E. Hoover" <ehoover(a)mines.edu> writes: > Real Name: > Erich Hoover > > Description: > This patch changes how the close socket operation works so that if > an async operation is registered then closing the handle will be > deferred until the async operation has completed. I would find it very suprising if this were how it's supposed to work, particularly since multiple handles can of course be opened to the same socket. You'll need very convincing tests for this... -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: [2/5] gdi32: Introduce a list of font file/data.
by Alexandre Julliard 24 Apr '12

24 Apr '12

Kusanagi Kouichi <slash(a)ac.auone-net.jp> writes: > @@ -962,6 +972,22 @@ static Family *find_family_from_any_name(const WCHAR *name) > return NULL; > } > > +static Font *find_font_file(const char *file) > +{ > + if (file != NULL) > + { > + Font *font; > + > + LIST_FOR_EACH_ENTRY(font, &font_list, Font, entry) > + { > + if (font->file != NULL && strcmp(font->file, file) == 0) > + return font; > + } > + } > + > + return NULL; > +} You can't compare files this way, different paths can point to the same file. > @@ -2927,7 +2988,8 @@ static BOOL get_fontdir( const char *unix_name, struct fontdir *fd ) > DWORD type; > > if (!ft_face) return FALSE; > - face = create_face( ft_face, 0, unix_name, NULL, 0, 0, FALSE ); > + font.file = (char *)unix_name; Don't do that. -- Alexandre Julliard julliard(a)winehq.org

2 4

Re: gdi32: Add support for emulating bold faces of bitmap fonts.
by Dmitry Timoshkov 24 Apr '12

24 Apr '12

Hello, Any feedback on this patch? -- Dmitry.

1 0

Re: winex11.drv: Windows always generates VK_DECIMAL for Del/. on a keypad.
by Dmitry Timoshkov 24 Apr '12

24 Apr '12

Dmitry Timoshkov <dmitry(a)baikal.ru> wrote: > Windows always generates VK_DECIMAL for Del/. on a keypad while some > X11 keyboard layouts generate XK_KP_Separator instead of XK_KP_Decimal > in order to produce a locale dependent numeric separator. > > X11 handles XK_KP_Separator same way as XK_KP_Decimal for all tested > keyboard layouts, so passing XK_KP_Separator instead of XK_KP_Decimal > to XKeysymToKeycode doesn't break things. Pressing Del/. with NumLock > turned on still correctly generates '.' or ',' depending on keyboard > layout and matches what Windows does. > > This patch fixes an application which uses VK_DECIMAL as a sign to break > the input string and insert a separator while entering a currency/price. Is there anything else I could provide in helping to get this patch accepted? -- Dmitry.

1 1

Re: [3/5] mapi32: Convert sendmail_extended_mapi to Unicode
by Alexandre Julliard 24 Apr '12

24 Apr '12

Owen Rudge <orudge(a)codeweavers.com> writes: > + > +/* Macro to test for validity before freeing a pointer */ > +#define mapi_heap_free(_ptr) if (_ptr) { HeapFree(GetProcessHeap(), 0, (_ptr)); } You don't need that. -- Alexandre Julliard julliard(a)winehq.org

1 0

Mono packaging status
by Vincent Povirk 24 Apr '12

24 Apr '12

So, I've finally had some time to work on Mono packaging. I think I have a sort of "first draft" ready. The goal is to create an MSI package of Mono, similar to the one we use for Gecko, which Wine will install automatically when updating a prefix, unless native mscoree is installed. This package will include all the Mono runtime files, as well as any registry keys and files that need to be installed to the Windows system for .NET compatibility. Anything .NET that we want to replace (including XNA, WPF, and msvcm libraries) will be included. Ideally, with this package installed, any official installers for .NET components will decide they are already installed and do nothing. To install native .NET, it will be necessary to uninstall the Mono package (using "wine uninstaller --remove '{E45D8920-A758-4088-B6C6-31DBB276992E}'", which will continue to work for the foreseeable future). Before the Mono package is installed, and after it is removed, no .NET registry keys or files will be present, so in theory the installers will just work (but in practice they probably will require work-arounds for Wine bugs). There will be only one package for 32-bit and 64-bit. Most of the compiled code is architecture-independent, so it doesn't make much sense to have separate packages. The Mono package versions will be loosely tied to Wine version. On prefix creation time, Wine will attempt to install the version it "prefers". Due to limitations of MSI, this may mean that Wine will upgrade Mono automatically but never downgrade it. Because the Mono API is stable, it should be possible to use any Mono package with any Wine version back to 1.5.1, which was the first version to search for the Mono runtime dll based on architecture. I'm currently publishing the source code at https://github.com/madewokherd/wine-mono, but I'm not sure if that is a good permanent home. I do want to keep it on github so I can make and accept pull requests. I'm using submodules, so it will be necessary to clone with --recursive and update the submodules from time to time. The build process requires mingw-w64 (both 32-bit and 64-bit), Wine, and a version of the Mono C sharp compiler (gmcs or dmcs, I think), and not surprisingly is done by running build-winemono.sh. There should never be any more requirements, and I'd like to keep the version requirements on those as broad as I can. I want this to be easy to build, so other people can work on it. The 64-bit part appears to work on Windows, but it is not useful on Wine currently. I'll be working on fixing that, or at least getting Alexandre bug reports and test cases so he can work on it. I think that when it is fixed, we'll have a lot more 64-bit processes than we used to, for better or worse. For now, the only way to install the package is with msiexec. The current version is based on Mono 2.11.0, which has a serious deadlock bug on Windows. This will need to be resolved before I can do an actual release. Otherwise, I'm not expecting much difference from the official Mono 2.10 packages for Windows. The XNA, WPF, and msvcm stuff is not ready yet. So, I know it's kind of crappy right now, and I'm not asking for testing so much as comments. If you are a packager of Wine, I would like to make sure you can build it, and that the resulting build works apart from that deadlock bug. If for some reason you want to try it, the current version is at https://github.com/downloads/madewokherd/wine-mono/winemono-0.0.2.msi. I think I will need a new home for the binaries, because github only gives me enough space for about 5 of them. So, uh, don't count on that URL sticking around.

4 5

Re: [2/2] gdi32: Enumerated font size should not be too large.
by Huw Davies 23 Apr '12

23 Apr '12

On 23/04/2012 15:32, Dmitry Timoshkov wrote: > This reverts commit f4625d1ae1109ee9a30faa8254b10779853f0ac2. > --- > dlls/gdi32/freetype.c | 2 +- > dlls/gdi32/tests/font.c | 1 + > 2 files changed, 2 insertions(+), 1 deletion(-) > > diff --git a/dlls/gdi32/freetype.c b/dlls/gdi32/freetype.c > index 3875e4f..401cfd1 100644 > --- a/dlls/gdi32/freetype.c > +++ b/dlls/gdi32/freetype.c > @@ -5048,7 +5048,7 @@ static void GetEnumStructs(Face *face, LPENUMLOGFONTEXW pelf, > font = alloc_font(); > > if(face->scalable) { > - height = -2048; /* 2048 is the most common em size */ > + height = 100; > width = 0; > } else { > height = face->size.y_ppem>> 6; You'll need to fix the ntmTm.ntmCellHeight and ntmTm.ntmAvgWidth values. Huw.

2 3

Re: gdiplus: Use symbolic name of the font style.
by Nikolay Sivov 23 Apr '12

23 Apr '12

On 4/23/2012 17:31, Dmitry Timoshkov wrote: > --- > dlls/gdiplus/font.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/dlls/gdiplus/font.c b/dlls/gdiplus/font.c > index 169e28f..8157b0a 100644 > --- a/dlls/gdiplus/font.c > +++ b/dlls/gdiplus/font.c > @@ -767,7 +767,7 @@ GpStatus WINGDIPAPI GdipGetLineSpacing(GDIPCONST GpFontFamily *family, > static INT CALLBACK font_has_style_proc(const LOGFONTW *elf, > const TEXTMETRICW *ntm, DWORD type, LPARAM lParam) > { > - INT fontstyle=0; > + INT fontstyle = FontStyleRegular; > > if (!ntm) return 1; > Maybe it's better to make it 'enum FontStyle' after all.

2 1

Re: [PATCH 1/4] amstream: rename mediastream to ddrawmediastream. (resend)
by Alexandre Julliard 23 Apr '12

23 Apr '12

Christian Costa <titan.costa(a)gmail.com> writes: > --- > dlls/amstream/Makefile.in | 2 > dlls/amstream/amstream.c | 6 + > dlls/amstream/amstream_private.h | 2 > dlls/amstream/ddrawmediastream.c | 256 ++++++++++++++++++++++++++++++++++++++ > dlls/amstream/mediastream.c | 251 ------------------------------------- > 5 files changed, 263 insertions(+), 254 deletions(-) > create mode 100644 dlls/amstream/ddrawmediastream.c > delete mode 100644 dlls/amstream/mediastream.c There's no reason to rename the file. Just put everything in there. -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: iphlpapi: Move get_pid_map() and find_owning_pid() under #ifdef #ifdef __linux__.
by Alexandre Julliard 23 Apr '12

23 Apr '12

Gerald Pfeifer <gerald(a)pfeifer.com> writes: > ...like their sole user. > > Otherwise this warns on everything which is not __linux__. ;-) That's a feature. It needs to be implemented on other platforms. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH 2/3] dmusic: Pass creation parameters to DMUSIC_CreateDirectMusicBufferImpl then allocate data buffer and set format accordingly.
by Alexandre Julliard 23 Apr '12

23 Apr '12

Christian Costa <titan.costa(a)gmail.com> writes: > +HRESULT WINAPI DMUSIC_CreateDirectMusicBufferImpl(LPDMUS_BUFFERDESC desc, LPVOID* ret_iface) > +{ > + IDirectMusicBufferImpl* dmbuffer; > + > + TRACE("(%p, %p)\n", desc, ret_iface); > + > + dmbuffer = HeapAlloc(GetProcessHeap(), HEAP_ZERO_MEMORY, sizeof(IDirectMusicBufferImpl)); > + if (!dmbuffer) { > + *ret_iface = NULL; > + return E_OUTOFMEMORY; > + } > + > + dmbuffer->lpVtbl = &DirectMusicBuffer_Vtbl; > + dmbuffer->ref = 0; /* Will be inited by QueryInterface */ > + > + memcpy(&dmbuffer->format, &desc->guidBufferFormat, sizeof(GUID)); > + dmbuffer->size = (desc->cbBuffer + 3) & ~3; /* Buffer size must be multiple of 4 bytes */ > + > + dmbuffer->data = HeapAlloc(GetProcessHeap(), 0, sizeof(dmbuffer->size)); > + if (!dmbuffer->data) { > + HeapFree(GetProcessHeap(), 0, dmbuffer); > + *ret_iface = NULL; > + return E_OUTOFMEMORY; > + } > + > + return IDirectMusicBufferImpl_QueryInterface((LPDIRECTMUSICBUFFER)dmbuffer, &IID_IDirectMusicBuffer, ret_iface); While you are changing the function please also make it handle errors properly. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH 2/3] dmsynth: Check the rigth CLSID to create the DirectMusicSynthSink object. (resend)
by Marvin 21 Apr '12

21 Apr '12

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

1 0

winedbg and program stdout
by Ilya Basin 21 Apr '12

21 Apr '12

When I debug a program with winedbg, it's output never goes to the same terminal. If it's compiled with -mconsole, it goes to a new console window; if compiled with -mwindows, the output is discarded. Any way to change this behavior?

2 1

Re: d3dx9_36: Add adjacency for D3DXCreateCylinder
by Rico Schüller 20 Apr '12

20 Apr '12

Am 20.04.2012 16:20, schrieb David Adam: > > + if (adjacency) > > I'm not sure that this is correct, but why is adjacency not touched? What should be returned for adjacency, maybe a test will show it? I guess the temp ID3DXBuffer should be returned instead of leaked when all is successful... Cheers Rico

1 0

Re: jscript: Added regexp 'pre-parser' to support non-backslash-sequenced non-terminating '/' in characted classes
by Marvin 20 Apr '12

20 Apr '12

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=17979 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

1 0

Are we missing the small folder_open icons?
by Francois Gouget 20 Apr '12

20 Apr '12

In dlls/shell32/shell32.rc I see the following fixme: /* FIXME: Following three resources are not yet added */ /* @makedep: folder_open.ico */ IDI_SHELL_FOLDER_OPEN_SMALL ICON folder_open.ico /* @makedep: folder_open.ico */ IDI_SHELL_FOLDER_OPEN_LARGE ICON folder_open.ico /* @makedep: folder_open.ico */ IDI_SHELL_FOLDER_SMALL_XP ICON folder_open.ico However folder_open.ico is generated from an SVG file and we seem to be having it in multiple sizes. Also this fixme has been there forever. So is there really still something to be fixed? -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ "Lotto: A tax on people who are bad at math." -- unknown "Windows: Microsoft's tax on computer illiterates." -- WE7U

2 1

Updating GSoC proposal
by Jacek Caban 19 Apr '12

19 Apr '12

Hi all, GSoC is starting this year and, if we want to have good applications, we need to update our proposals. Usually the most attention is directed into adding new ones, while we keep obviously bad (or just bad IMO) proposals on the page. I'm planning to remove following project proposals: Security - implement sandboxing Theming - Implement Wine theming support NTDLL - support performance registry keys Winelib Aware Scons (or cmake) Cleanup Winemenubuilder to support generating Application Bundles on Mac OS X Wine-based application virtualization If someone knows a reason to not remove them, please reply. Cheers, Jacek

2 1

Re: d3dx9/tests: Add DDS pixel format tests for D3DXGetImageInfoFromFileInMemory.
by Matteo Bruni 19 Apr '12

19 Apr '12

Il 19 aprile 2012 19:37, Józef Kucia <joseph.kucia(a)gmail.com> ha scritto: > --- > dlls/d3dx9_36/tests/surface.c | 65 +++++++++++++++++++++++++++++++++++++++++ > 1 files changed, 65 insertions(+), 0 deletions(-) > > diff --git a/dlls/d3dx9_36/tests/surface.c b/dlls/d3dx9_36/tests/surface.c > index 87aa03e..51d6ebd 100644 > --- a/dlls/d3dx9_36/tests/surface.c > +++ b/dlls/d3dx9_36/tests/surface.c > @@ -22,6 +22,8 @@ > #include "wine/test.h" > #include "d3dx9tex.h" > #include "resources.h" > +#undef MAKE_DDHRESULT > +#include "ddraw.h" > I'm not sure that's a good idea. ddraw.h is not included in recent DirectX SDKs and the relevant definitions are "gone", as far as I know. So I think d3dx9 or its tests should not depend on that header. I'd just (re)declare the stuff you need privately in the test source file instead. You don't even need to use the same types/defines/variables names as those from ddraw.h, you just have to keep them compatible. On that point, I see that MSDN mentions the equivalent DDS_HEADER and DDS_PIXELFORMAT structures (http://msdn.microsoft.com/en-us/library/windows/desktop/bb943991%28v=vs.85%…), except those don't seem to be defined in the MS headers either. I guess you are free to use whatever names you like...

3 3

Re: [PATCH 4/4] jscript: Added Number.toPrecision implementation
by Marvin 19 Apr '12

19 Apr '12

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=17957 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

1 0

Re: [PATCH 3/4] jscript: Added Number.toExpontential implementation
by Marvin 19 Apr '12

19 Apr '12

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=17956 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

1 0

Re: [PATCH 2/4] jscript: Added Number.toFixed implementation
by Marvin 19 Apr '12

19 Apr '12

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=17955 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

1 0

Re: [PATCH 1/3] ws2_32: Revise AcceptEx behavior to send completions for canceled sockets (resend 3, deferred).
by Alexandre Julliard 19 Apr '12

19 Apr '12

"Erich E. Hoover" <ehoover(a)mines.edu> writes: > @@ -256,10 +256,12 @@ void async_set_result( struct object *obj, unsigned int status, unsigned int tot > else > { > if (async->timeout) remove_timeout_user( async->timeout ); > + if (async->completion && async->data.cvalue && status != STATUS_ALERTED) > + add_completion( async->completion, async->comp_key, async->data.cvalue, status, total ); > + else if (async->completion && async->data.cvalue && status == STATUS_ALERTED) > + status = STATUS_SUCCESS; This looks pretty hackish, the server shouldn't have to care about the status values or patch them up for the client. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH 2/2] wininet: Add a new common module information struct
by Piotr Caban 18 Apr '12

18 Apr '12

On 04/16/12 22:03, Morten Rønne wrote: > Add a new common module information struct for urlcache and functions to > do initialization of the struct. This is intended to be a new way to > more easily create Ansi and Unicode version of the functions, by doing a > Ansi/Unicode preamble code that calls a common worker function that do > the real work. Is there any reason not to call Ansi function inside Unicode function? (This is the other way then it is done in most parts of wine, the reason for this is that urlcache stores ansi strings internally. Unicode urls should probably be converted using punycode encoding (IdnToAscii?)). This patch is also introducing lots of unneeded Ansi/Unicode conversions. I'm not sure if storing all url entry related information inside a structure makes anything easier/more readable. Especially when you need to make sure that a field is initialized before accessing it.

2 1

Re: [PATCH 1/2] wininet: Update structs with more information in preparation for implementation of more functionality.
by Piotr Caban 18 Apr '12

18 Apr '12

On 04/16/12 22:00, Morten Rønne wrote: + DWORD AllocationTable[0xF6C]; There are defines describing allocation table size. It's better to define it as BYTE AllocationTable[ALLOCATION_TABLE_SIZE];

2 1

Patch 85420
by Christian Costa 18 Apr '12

18 Apr '12

Hi, Patch http://source.winehq.org/patches/data/85420 is marked as pending. I've taken a look but I still don't understand what's wrong. Is there anything I've missed ? Thanks Christian

3 3

Re: gdiplus: Use StretchBlt instead of GdiAlphaBlend if device doesn't support alpha blending. Resend.
by Dmitry Timoshkov 18 Apr '12

18 Apr '12

Dmitry Timoshkov <dmitry(a)baikal.ru> wrote: > This patch makes printing of PNG and other images work from applications > which use gdiplus for that. > > Printer drivers can't support transparency or alpha blending in any way. > This patch was tested with wide range of images (some mixed with other > graphics and text), and output matches what native gdiplus does. Is there anything else I could provide in helping to get this patch accepted? -- Dmitry.

2 2

Re: mshtml: Copy filter value in HTMLElement_clone
by Marvin 18 Apr '12

18 Apr '12

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=17938 Your paranoid android. === 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

1 0

Re: [PATCH 2/2] wininet: Add a new common module information struct
by Jacek Caban 18 Apr '12

18 Apr '12

Hi Morten, On 04/16/12 22:03, Morten Rønne wrote: > typedef struct _HASH_CACHEFILE_ENTRY > { > CACHEFILE_ENTRY CacheFileEntry; > DWORD dwAddressNext; > DWORD dwHashTableNumber; > - struct _HASH_ENTRY HashTable[HASHTABLE_SIZE]; > -} HASH_CACHEFILE_ENTRY; > + HASH_ENTRY HashTable[HASHTABLE_SIZE]; > +} HASH_CACHEFILE_ENTRY, *LPHASH_CACHEFILE_ENTRY; > > typedef struct _DIRECTORY_DATA > { > @@ -187,13 +187,56 @@ typedef struct _URLCACHECONTAINER > HANDLE hMapping; /* handle of file mapping */ > DWORD file_size; /* size of file when mapping was opened */ > HANDLE hMutex; /* handle of mutex */ > -} URLCACHECONTAINER; > +} URLCACHECONTAINER, *LPURLCACHECONTAINER; Please don't use this kind of defined. LP* types make the code less readable for no good reason. Cheers, Jacek

1 0

Re: [PATCH 2/2] jscript: Correctly handle empty matches in String.replace
by Marvin 18 Apr '12

18 Apr '12

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=17935 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

1 0

Re: [7/7] server: Propagate an error code returned by token_access_check() to the client. Resend.
by Marvin 18 Apr '12

18 Apr '12

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=17934 Your paranoid android. === TEST64_W7SP1 (32 bit sync) === sync.c:924: Test failed: ChangeTimerQueueTimer

1 0

SymEnumSymbolsForAddr in dbghelp.dll
by Roger Cruz 18 Apr '12

18 Apr '12

I wrote a simple piece of code that uses dbghelp.dll's SymEnumSymbolsForAddr() but when I went to search for its code in Wine, it looks to be missing. The dbghelp.spec has that function listed as "stub". What does stub mean in this context? Does it mean the function is not implemented? Are there any plans to? Thanks Roger R. Cruz

2 4

Re: wsnmp32: New stub dll (resend)
by Alexandre Julliard 17 Apr '12

17 Apr '12

Stefan Leichter <Stefan.Leichter(a)camline.com> writes: > @@ -0,0 +1,49 @@ > +# imported from D-Link EMS by ordinal > +320 stub SnmpSetPort > +# > +@ stub SnmpCancelMsg > +@ stub SnmpCleanup > +@ stub SnmpClose > +@ stub SnmpContextRoStr > +@ stub _SnmpConveyAgentAddress > +@ stub SnmpCountVbl > +@ stub SnmpCreatePdu > +@ stub SnmpCreateSession > +@ stub SnmpCreateVbl > +@ stub SnmpDecodeMsg > +@ stub SnmpDeleteVb > +@ stub SnmpDuplicatePdu > +@ stub SnmpDuplicateVbl > +@ stub SnmpEncodeMsg > +@ stub SnmpEntityTpStr > +@ stub SnmpFreeContext > +@ stub SnmpFreeDescriptor > +@ stub SnmpFreeEntity > +@ stub SnmpFreePdu > +@ stub SnmpFreeVbl > +@ stub SnmpGetLastError > +@ stub SnmpGetPduData > +@ stub SnmpGetRetransmitMode > +@ stub SnmpGetRetry > +@ stub SnmpGetTimeout > +@ stub SnmpGetVb > +@ stub SnmpGetVendorInfo > +@ stub SnmpListen > +@ stub SnmpOidCompare > +@ stub SnmpOidCopy > +@ stub SnmpOidToStr > +@ stub SnmpOpen > +@ stub SnmpRecvMsg > +@ stub SnmpRegister > +@ stub SnmpSendMsg > +@ stub _SnmpSetAgentAddress > +@ stub SnmpSetPdu > +@ stub SnmpSetRetransmitMode > +@ stub SnmpSetRetry > +@ stub SnmpSetTimeout > +@ stub SnmpSetTranslateMode > +@ stub SnmpSetVb > +@ stub SnmpStartup > +@ stub SnmpStrToContext > +@ stub SnmpStrToEntity > +@ stub SnmpStrToOid They should probably all be ordinals, also some of the names are wrong. -- Alexandre Julliard julliard(a)winehq.org

1 0

New forum software
by Vitaliy Margolen 17 Apr '12

17 Apr '12

Can I ask when we'll have the new forum software installed? It's been discussed ages ago and we still using the same old crappy version. Vitaliy.

4 4

Re: gdi32/dibdrv: don't add_join if points are coincident in wide_line_segments (try 2)
by Alexandre Julliard 17 Apr '12

17 Apr '12

Daniel Lehman <dlehman(a)esri.com> writes: > Was mistakenly sent to wine-devel > > try 2 - integrate into existing tests; updated commit message > > I think the only points in the middle of the points array can cause > the crash I was seeing. wide_pen_lines trims coincident points/empty > segments from the beginning and end of the array, so the > wine_line_segment calls before and after the for loop I modified will > always return valid faces It doesn't work here: ../../../tools/runtest -q -P wine -M gdi32.dll -T ../../.. -p gdi32_test.exe.so dib.c && touch dib.ok dib.c:1324: Test failed: 8888: wide pen - empty segments: expected hash 5bac9c515315bced1ac5cb46a771690d02040278 got 56cc0584aaeb790419b343dae0ea09591c384ac4 dib.c:1324: Test failed: 8888 - bitfields: wide pen - empty segments: expected hash 5bac9c515315bced1ac5cb46a771690d02040278 got 56cc0584aaeb790419b343dae0ea09591c384ac4 dib.c:1324: Test failed: a8b8g8r8: wide pen - empty segments: expected hash 1aa5e414c797fd74fe1400757548ef79650fe994 got ee5a5dc02ec61af2462c265424943049ea7c23eb dib.c:1324: Test failed: r10g10b10: wide pen - empty segments: expected hash 65f7fc7219e7cc29d20aeab7d38a60ac6c303726 got d7ee8801ea0c3e7cf012153b77bd7ba9b388f459 dib.c:1324: Test failed: r6g6b6: wide pen - empty segments: expected hash b1e3aeac484f49b1874033509924627ef0a4c3bc got 906c2d8da24180ccbe84fd4fd5ba964d8f9a3a44 dib.c:1324: Test failed: 24: wide pen - empty segments: expected hash f11f301314f9729ab351294a4d8a72b72fc2491d got 9433b11e4190cf1d77f4b84017e8561884ccd73c dib.c:1324: Test failed: r5g5b5: wide pen - empty segments: expected hash ffa75c684138fdb296f4001e2dc36ed1ae33065b got e141eb6b73e91eb2e4b5fd31688084d4b4c70d30 dib.c:1324: Test failed: r4g4b4: wide pen - empty segments: expected hash 9aa687dc13503e3ff4e12e67c361ca140cbdb48d got 27afb67bda17491c7806f1a42650deb9d47bba71 dib.c:1324: Test failed: 8 color: wide pen - empty segments: expected hash 7897ba51f37e01c6a54a2733459e79285b52d213 got d905bc3cd08fc4a7110608ec8b80e494077e859e dib.c:1324: Test failed: 8 grayscale: wide pen - empty segments: expected hash 88eb0c6542a2c03036241cdb5e08f13401a92f31 got bef8347c9bc96d709aaf002fcf6b4da66e5267e7 dib.c:1324: Test failed: 8: wide pen - empty segments: expected hash 00b34f58bb4876b597fad1a275bccb2c9a95967b got 3f318b982da1b8d26eff59ed8c6d7ce6a84f857a dib.c:1324: Test failed: 4: wide pen - empty segments: expected hash 9b5ecb81cf32c34c43cb13310e4b479b6909f3ec got 10271cb9b746fb9b507a9322c16f1279deb69a95 dib.c:1324: Test failed: 4 grayscale: wide pen - empty segments: expected hash 048ce4615962675d66b648631dc556238a86b4df got 9cf16c3165ac241aa6fb50bb0a05c3548fbaeb43 dib.c:1324: Test failed: 1: wide pen - empty segments: expected hash 1dde794388a3ca3ac710acc0aff97f7df70687e5 got e203905ad4c0a609b5ac78e66714b66ffe792b8b make[1]: *** [dib.ok] Error 14 -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [2/4] server: Add access mapping for a named pipe device object, adjust its default access rights. Resend.
by Alexandre Julliard 17 Apr '12

17 Apr '12

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > @@ -238,7 +238,7 @@ static const struct object_ops named_pipe_device_ops = > no_satisfied, /* satisfied */ > no_signal, /* signal */ > named_pipe_device_get_fd, /* get_fd */ > - no_map_access, /* map_access */ > + named_pipe_map_access, /* map_access */ > default_get_sd, /* get_sd */ > default_set_sd, /* set_sd */ > named_pipe_device_lookup_name, /* lookup_name */ > @@ -270,10 +270,10 @@ static void named_pipe_dump( struct object *obj, int verbose ) > > static unsigned int named_pipe_map_access( struct object *obj, unsigned int access ) > { > - if (access & GENERIC_READ) access |= STANDARD_RIGHTS_READ; > + if (access & GENERIC_READ) access |= STANDARD_RIGHTS_READ | FILE_READ_ATTRIBUTES; > if (access & GENERIC_WRITE) access |= STANDARD_RIGHTS_WRITE | FILE_CREATE_PIPE_INSTANCE; > if (access & GENERIC_EXECUTE) access |= STANDARD_RIGHTS_EXECUTE; > - if (access & GENERIC_ALL) access |= STANDARD_RIGHTS_ALL; > + if (access & GENERIC_ALL) access |= STANDARD_RIGHTS_ALL | FILE_READ_ATTRIBUTES | FILE_CREATE_PIPE_INSTANCE; > return access & ~(GENERIC_READ | GENERIC_WRITE | GENERIC_EXECUTE | GENERIC_ALL); Why do you need this for the device? -- Alexandre Julliard julliard(a)winehq.org

2 3

Re: [PATCH 2/3] Added support for shadowing of element pseudo-variables
by Marvin 17 Apr '12

17 Apr '12

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=17915 Your paranoid android. === 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

1 0

Re: [4/4] server: Propagate an error code returned by token_access_check() to the client. Resend.
by Marvin 17 Apr '12

17 Apr '12

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=17912 Your paranoid android. === W7PROX64 (64 bit sync) === sync.c:923: Test failed: DeleteTimerQueueTimer sync.c:924: Test failed: ChangeTimerQueueTimer

2 1

Re: kernel32: Add more memory access checks.
by Marvin 17 Apr '12

17 Apr '12

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=17913 Your paranoid android. === TEST64_W7SP1 (64 bit virtual) === virtual.c:854: Test failed: got size 0x100000 virtual.c:935: Test failed: got size 0x100000

1 0

Re: [3/4] server: Perform an access check for kernel objects without a security descriptor using access rights of the owner'
by Marvin 17 Apr '12

17 Apr '12

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=17911 Your paranoid android. === WVISTAADM (32 bit sync) === sync.c:923: Test failed: DeleteTimerQueueTimer

2 1

[shlwapi] Add NULL checks to StrCpyW and StrCatW
by carlo.bramix＠libero.it 16 Apr '12

16 Apr '12

Hello friends, according to these results, it looks like the test I added in the patch crashes win2k SP4 but it works on all others. And it does not seem to be a thing that it can be resolved with dynamic library loading. So, what should I do? Do I need to comment them like it has been done (for example) into test_StrChrA()? Do I need to remove interely the test and revive previous patch? Please excuse my inexperience... Sincerely, Carlo Bramini. >----Messaggio originale---- >Da: testbot(a)testbot.winehq.org >Data: 16/04/2012 22.48 >A: <carlo.bramix(a)libero.it> >Ogg: TestBot job 17900 results: [shlwapi] Add NULL checks to StrCpyW and StrCatW > >VM Status Number of test failures >WINEBUILD completed >WNT4WSSP6 completed 0 >W2KPROSP4 completed 1 >WXPPROSP3 completed 0 >W2K3R2SESP2 completed 0 >WVISTAADM completed 0 >W2K8SE completed 0 >W7PRO completed 0 >W7PROX64 completed 0 >TEST64_W7SP1 completed 0 >W7PROX64 completed 0 >TEST64_W7SP1 completed 0 > >=== WINEBUILD (build) === >No build failures found > >=== WNT4WSSP6 (32 bit string) === >No test failures found > >=== W2KPROSP4 (32 bit string) === > >shlwapi: >string: unhandled exception c0000005 at 77C7F8A8 > >=== WXPPROSP3 (32 bit string) === >No test failures found > >=== W2K3R2SESP2 (32 bit string) === >No test failures found > >=== WVISTAADM (32 bit string) === >No test failures found > >=== W2K8SE (32 bit string) === >No test failures found > >=== W7PRO (32 bit string) === >No test failures found > >=== W7PROX64 (32 bit string) === >No test failures found > >=== TEST64_W7SP1 (32 bit string) === >No test failures found > >=== W7PROX64 (64 bit string) === >No test failures found > >=== TEST64_W7SP1 (64 bit string) === >No test failures found

1 0

Re: [shlwapi] Add NULL checks to StrCpyW and StrCatW
by Marvin 16 Apr '12

16 Apr '12

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=17900 Your paranoid android. === W2KPROSP4 (32 bit string) === string: unhandled exception c0000005 at 77C7F8A8

1 0

Re: [PATCH] winealsa.drv: Init *num to 0 (Coverity)
by Andrew Eikum 16 Apr '12

16 Apr '12

On Mon, Apr 16, 2012 at 09:09:58AM +0200, Marcus Meissner wrote: > Also initialize a "may be uninitialized" value the compiler sees. > Not sure what this means. *num is initialized at the beginning of alsa_enum_devices, which is always called from GetEndpointIDs. Seems like a Coverity oversight. I'd either leave it as-is, or also remove the *num=0 from alsa_enum_devices. Andrew > Ciao, Marcus > --- > dlls/winealsa.drv/mmdevdrv.c | 3 ++- > 1 files changed, 2 insertions(+), 1 deletions(-) > > diff --git a/dlls/winealsa.drv/mmdevdrv.c b/dlls/winealsa.drv/mmdevdrv.c > index e3c1d15..d84bbb2 100644 > --- a/dlls/winealsa.drv/mmdevdrv.c > +++ b/dlls/winealsa.drv/mmdevdrv.c > @@ -345,7 +345,7 @@ static WCHAR *construct_device_id(EDataFlow flow, const WCHAR *chunk1, const cha > { > WCHAR *ret; > const WCHAR *prefix; > - DWORD len_wchars = 0, chunk1_len, copied = 0, prefix_len; > + DWORD len_wchars = 0, chunk1_len = 0, copied = 0, prefix_len; > > static const WCHAR dashW[] = {' ','-',' ',0}; > static const size_t dashW_len = (sizeof(dashW) / sizeof(*dashW)) - 1; > @@ -583,6 +583,7 @@ HRESULT WINAPI AUDDRV_GetEndpointIDs(EDataFlow flow, WCHAR ***ids, GUID **guids, > > TRACE("%d %p %p %p %p\n", flow, ids, guids, num, def_index); > > + *num = 0; > *ids = NULL; > *guids = NULL; > > -- > 1.7.3.4 > > >

2 2

Re: msvcrt: Added more length modifiers in scanf function
by Marvin 16 Apr '12

16 Apr '12

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=17893 Your paranoid android. === WNT4WSSP6 (32 bit scanf) === scanf.c:144: Test failed: sprintf retuned 10 scanf.c:145: Test failed: got 1942892530, expected 12345678901234 === W2KPROSP4 (32 bit scanf) === scanf.c:144: Test failed: sprintf retuned 10 scanf.c:145: Test failed: got 1942892530, expected 12345678901234 === WXPPROSP3 (32 bit scanf) === scanf.c:144: Test failed: sprintf retuned 10 scanf.c:145: Test failed: got 1942892530, expected 12345678901234 === W2K3R2SESP2 (32 bit scanf) === scanf.c:144: Test failed: sprintf retuned 10 scanf.c:145: Test failed: got 1942892530, expected 12345678901234

1 0

Re: ws2_32: Fix hostent memory allocation
by Alexandre Julliard 16 Apr '12

16 Apr '12

Bruno Jesus <00cpxxx(a)gmail.com> writes: > @@ -5546,24 +5546,70 @@ INT WINAPI WSAUnhookBlockingHook(void) > * pointers (via a template of some kind). > */ > > -static int list_size(char** l, int item_size) > +/*********************************************************************** > + * list_size (INTERNAL) > + * > + * Calculate the size of data and number of items from a list based on > + * a fixed item size or strings by using strlen. The source list must be > + * NULL terminated. > + * > + * PARAMS > + * l [I] Pointer to array of source items. > + * item_size [I] Fixed item size or zero if it's a string list. > + * size_sum [O] Pointer to where the sum of item bytes will be > + * stored. May be NULL if not required by the caller. > + * item_count [O] Pointer to where the number of items bytes will be > + * stored. May be NULL if not required by the caller. > + * > + * NOTES > + * When item_size is zero the byte sum will also count the NULL > + * terminator for each string. > + */ > +static void list_size(char** l, int item_size, int *size_sum, int *item_count) > { > - int i,j = 0; > - if(l) > - { for(i=0;l[i];i++) > - j += (item_size) ? item_size : strlen(l[i]) + 1; > - j += (i + 1) * sizeof(char*); } > - return j; > + int s, c, *sum = (size_sum ? size_sum : &s), *count = (item_count ? item_count : &c); > + *sum = *count = 0; > + if(l) > + { > + for(;l[*count];(*count)++) > + *sum += (item_size) ? item_size : strlen(l[*count]) + 1; > + } That's not a good helper function, with all the optional parameters and various behaviors. Also if you need a big documentation block like this for a 5-line function it's a sign that something is wrong. -- Alexandre Julliard julliard(a)winehq.org

2 1

WASAPI ISimpleAudioVolume::SetMasterVolume appears to not work
by adam smith 16 Apr '12

16 Apr '12

Hi, I've been trying to get WASAPI audio output working for our app as Directsound output was very glitchy post the new audio stack. All seems to work great with WASAPI however I need to able to set the volume level independently for individual audio sessions / streams for crossfading however I'm having problems controlling the volume levels of a shared mode audio session / stream. specifically, ISimpleAudioVolume::SetMasterVolume http://msdn.microsoft.com/en-us/library/windows/desktop/dd316537(v=vs.85).a… Doesn't seem to work under Wine i.e. HRESULT hr; hr=audioClient_->GetService(IID_ISimpleAudioVolume,(void**)&simpleAudioVolume_); if (SUCCESS(hr)) hr=simpleAudioVolume_->SetMasterVolume(0.1,NULL); returns success but does not change the volume level though interestingly HRESULT hr; hr=audioClient_->GetService(IID_ISimpleAudioVolume,(void**)&simpleAudioVolume_); if (SUCCESS(hr)) hr=simpleAudioVolume_->SetMute(TRUE,NULL); does work and mute the volume. I've also tried usingsthe IAudioStreamVolume interface to control the volume again to no avail. Does anyone have any experience of these interfaces or know equivalent interfaces to use instead working I've tested on : Ubuntu 10.04, 11.10 Wine 1.4 , 1.5 , 1.5.2 PulseAudio 0.9.21 , 1.0 , no pulse audio (and windows 7 where the code works fine) Thanks, Adam

2 1

Re: jscript: Make sure to jump out of switch before entering implicit default clausule
by Marvin 16 Apr '12

16 Apr '12

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=17883 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

1 0

Testbot certificate has expired
by Morten Rønne 16 Apr '12

16 Apr '12

Hi testbot.winehq.com certificate expired on 13-04-2012. So now the wininet tests in dlls/wininet/tests/http.c are failing with an error for me. I can't determine if the fault are in the test or the function called should handle the error case. The error message is: err:wininet:NETCON_secure_connect SSL_connect failed: 12037 http.c:2873: Test failed: HttpSendRequest failed: 12037 wine: Unhandled page fault on read access to 0x00000008 at address 0x68a876c5 (thread 0009), starting debugger... Unhandled exception: page fault on read access to 0x00000008 in 32-bit code (0x68a876c5). Best Regards Morten Rønne

2 1

Re: gdi32: Add support for emulating bold faces of bitmap fonts.
by Huw Davies 16 Apr '12

16 Apr '12

On Mon, Apr 16, 2012 at 04:37:39PM +0900, Dmitry Timoshkov wrote: > diff --git a/dlls/gdi32/freetype.c b/dlls/gdi32/freetype.c > index 0a5d3c3..eb3f9b5 100644 > --- a/dlls/gdi32/freetype.c > +++ b/dlls/gdi32/freetype.c > @@ -5669,12 +5669,27 @@ static inline BYTE get_max_level( UINT format ) > return 255; > } > > -static const BYTE masks[8] = {0x80, 0x40, 0x20, 0x10, 0x08, 0x04, 0x02, 0x01}; > +static void emulate_bold_glyph(BYTE *buf, int pitch, int height) > +{ > + int x, y; > + BYTE *p = buf; > + > + for (y = 0; y < height; y++) > + { > + for (x = pitch - 1; x >= 0; x--) > + { > + p[x] |= p[x] >> 1; > + if (x > 0) p[x] |= p[x - 1] << 7; > + } > + p += pitch; > + } > +} > Don't we need to add some bytes if glyph_width % 32 == 0 ? Huw.

2 3

Re: msvcp90: Add codecvt ctors and dtors
by Piotr Caban 16 Apr '12

16 Apr '12

Hi, On 04/16/12 02:50, William Panlener wrote: > typedef struct { > + locale_facet facet; > + /* FIXME: type definition in standard but var here */ > + enum { ok, partial, error, noconv } result; > +} codecvt_base; This structure has incorrect size. It should not contain result variable. > +typedef struct { > + codecvt_base base; > + /* FIXME: incomplete struct definition */ > +} codecvt_char_char_mbstate; It's better to define whole structure. Also other structures are named differently, it would be probably better to name it codecvt_char. > +typedef struct { > + codecvt_base base; > + /* FIXME: incomplete struct definition */ > +} codecvt_short_char_mbstate; > + > +typedef struct { > + codecvt_base base; > + /* FIXME: incomplete struct definition */ > +} codecvt_wchar_char_mbstate; There's no reason to define separate structures for unsigned short and wchar_t variants of the class. Probably the only difference between this classes is typeinfo structure. > +/* FIXME: Potentially unused */ > +/* ?id@?$codecvt@DDH@std@@2V0locale@2@A */ > +locale_id codecvt_char_char_mbstate_id = {0}; I don't understand this comment. The id fields will be used by locale class. > +/* ??1codecvt_base@std@@UAE@XZ */ > +/* ??1codecvt_base@std@@UEAA@XZ */ > +DEFINE_THISCALL_WRAPPER(codecvt_base_dtor, 4) > +void __thiscall codecvt_base_dtor(codecvt_base *this) > +{ > + FIXME("(%p)\n stub!", this); > + TRACE("(%p)\n", this); > +} There's no need to use both FIXME and TRACE. > +/* ??1?$codecvt@DDH@std@@MAE@XZ */ > +/* ??1?$codecvt@DDH@std@@MEAA@XZ */ > +DEFINE_THISCALL_WRAPPER(codecvt_char_char_mbstate_dtor, 4) > +void __thiscall codecvt_char_char_mbstate_dtor(codecvt_char_char_mbstate *this) > +{ > + /*FIXME stub*/ > + codecvt_base_dtor(&this->base); > + TRACE("(%p)\n", this); > +} It's better to print a fixme message here. > +DEFINE_RTTI_DATA(codecvt_char_char_mbstate, 0, 1,&locale_facet_rtti_base_descriptor, NULL, NULL, " ?AV?$codecvt@DDH@std@@"); > +DEFINE_RTTI_DATA(codecvt_short_char_mbstate, 0, 1,&locale_facet_rtti_base_descriptor, NULL, NULL, " ?AV?$codecvt@GDH@std@@"); > +DEFINE_RTTI_DATA(codecvt_wchar_char_mbstate, 0, 1,&locale_facet_rtti_base_descriptor, NULL, NULL, ".?AV?$codecvt@_WDH@std@@"); The RTTI data for these structures is incorrect. > + __ASM_VTABLE(codecvt_base, ""/*FIXME*/); > + __ASM_VTABLE(codecvt_char_char_mbstate, ""/*FIXME*/); > + __ASM_VTABLE(codecvt_short_char_mbstate, ""/*FIXME*/); > + __ASM_VTABLE(codecvt_wchar_char_mbstate, ""/*FIXME*/); It's better to create correct virtual functions table. This may lead to some strange crashes.

1 0

Re: [PATCH 1/3] browseui: Add IOleWindow to IProgressDialog
by Nikolay Sivov 15 Apr '12

15 Apr '12

On 4/15/2012 23:08, Detlef Riekenberg wrote: > Used by apps to adjust the dialog position > or remove the cancel button before vista > > -- > By by ... Detlef > --- > dlls/browseui/progressdlg.c | 69 ++++++++++++++++++++++++++++++++++++++++++- > 1 files changed, 68 insertions(+), 1 deletions(-) > > diff --git a/dlls/browseui/progressdlg.c b/dlls/browseui/progressdlg.c > index 9b970e2..2807622 100644 > --- a/dlls/browseui/progressdlg.c > +++ b/dlls/browseui/progressdlg.c > @@ -60,6 +60,7 @@ WINE_DEFAULT_DEBUG_CHANNEL(browseui); > > typedef struct tagProgressDialog { > IProgressDialog IProgressDialog_iface; > + IOleWindow IOleWindow_iface; > LONG refCount; > CRITICAL_SECTION cs; > HWND hwnd; > @@ -79,6 +80,11 @@ static inline ProgressDialog *impl_from_IProgressDialog(IProgressDialog *iface) > return CONTAINING_RECORD(iface, ProgressDialog, IProgressDialog_iface); > } > > +static inline ProgressDialog *impl_from_IOleWindow(IOleWindow *iface) > +{ > + return CONTAINING_RECORD(iface, ProgressDialog, IOleWindow_iface); > +} > + > static void set_buffer(LPWSTR *buffer, LPCWSTR string) > { > static const WCHAR empty_string[] = {0}; > @@ -270,9 +276,20 @@ static HRESULT WINAPI ProgressDialog_QueryInterface(IProgressDialog *iface, REFI > ProgressDialog *This = impl_from_IProgressDialog(iface); > *ppvOut = NULL; > > - if (IsEqualIID(iid,&IID_IUnknown) || IsEqualIID(iid,&IID_IProgressDialog)) > + if (IsEqualIID(iid,&IID_IUnknown)) > { > *ppvOut = This; > + TRACE("(%p, IID_IUnknown, %p) -> %p\n", This, ppvOut, This); > + } > + else if (IsEqualIID(iid,&IID_IProgressDialog)) > + { > + *ppvOut = This; > + TRACE("(%p, IID_IProgressDialog, %p) -> %p\n", This, ppvOut, This); > + } > + else if (IsEqualIID(iid,&IID_IOleWindow)) > + { > + *ppvOut =&This->IOleWindow_iface; > + TRACE("(%p, IID_IOleWindow, %p) -> %p\n", This, ppvOut, *ppvOut); > } What's a point in different traces? A single one is enough, with printed riid of course. Also please return iface instead of This, like *ppvOut = iface;, or if you prefer instance pointer add a pointer to interface like - &This->... > > if (*ppvOut) > @@ -495,6 +512,55 @@ static const IProgressDialogVtbl ProgressDialogVtbl = > ProgressDialog_Timer > }; > > +static HRESULT WINAPI OleWindow_QueryInterface(IOleWindow *iface, REFIID iid, LPVOID *ppvOut) > +{ > + ProgressDialog *This = impl_from_IOleWindow(iface); > + > + TRACE("(%p, %s, %p)\n", iface, debugstr_guid(iid), ppvOut); > + return ProgressDialog_QueryInterface(&This->IProgressDialog_iface, iid, ppvOut); > +} > + This trace should go to ProgressDialog_QueryInterface(), no need to place it in every interface.

1 0

Re: ddraw/tests: Compare the correct surface pointers.
by Marvin 15 Apr '12

15 Apr '12

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=17873 Your paranoid android. === W2KPROSP4 (32 bit dsurface) === dsurface.c:272: Test failed: lpSurface from GetSurfaceDesc(00000000) differs from the one returned by Lock(00A70028) === WXPPROSP3 (32 bit dsurface) === dsurface.c:272: Test failed: lpSurface from GetSurfaceDesc(00000000) differs from the one returned by Lock(00BA0028) === W2K3R2SESP2 (32 bit dsurface) === dsurface.c:272: Test failed: lpSurface from GetSurfaceDesc(00000000) differs from the one returned by Lock(00E40028) === WVISTAADM (32 bit dsurface) === dsurface.c:272: Test failed: lpSurface from GetSurfaceDesc(00000000) differs from the one returned by Lock(02210028) === W2K8SE (32 bit dsurface) === dsurface.c:272: Test failed: lpSurface from GetSurfaceDesc(00000000) differs from the one returned by Lock(02800028) === W7PRO (32 bit dsurface) === dsurface.c:272: Test failed: lpSurface from GetSurfaceDesc(00000000) differs from the one returned by Lock(01BF0028) === W7PROX64 (32 bit dsurface) === dsurface.c:272: Test failed: lpSurface from GetSurfaceDesc(00000000) differs from the one returned by Lock(02740028) === TEST64_W7SP1 (32 bit dsurface) === dsurface.c:272: Test failed: lpSurface from GetSurfaceDesc(00000000) differs from the one returned by Lock(02690028) === W7PROX64 (64 bit dsurface) === dsurface.c:272: Test failed: lpSurface from GetSurfaceDesc(0000000000000000) differs from the one returned by Lock(0000000002390040) === TEST64_W7SP1 (64 bit dsurface) === dsurface.c:272: Test failed: lpSurface from GetSurfaceDesc(0000000000000000) differs from the one returned by Lock(0000000002360040)

2 1

Re: [PATCH 1/3] browseui: Add IOleWindow to IProgressDialog
by Michael Stefaniuc 15 Apr '12

15 Apr '12

Hello Detlef, On 04/15/2012 10:08 PM, Detlef Riekenberg wrote: > Used by apps to adjust the dialog position > or remove the cancel button before vista > > -- > By by ... Detlef > --- > dlls/browseui/progressdlg.c | 69 ++++++++++++++++++++++++++++++++++++++++++- > 1 files changed, 68 insertions(+), 1 deletions(-) > > diff --git a/dlls/browseui/progressdlg.c b/dlls/browseui/progressdlg.c > index 9b970e2..2807622 100644 > --- a/dlls/browseui/progressdlg.c > +++ b/dlls/browseui/progressdlg.c > @@ -270,9 +276,20 @@ static HRESULT WINAPI ProgressDialog_QueryInterface(IProgressDialog *iface, REFI > ProgressDialog *This = impl_from_IProgressDialog(iface); > *ppvOut = NULL; > > - if (IsEqualIID(iid, &IID_IUnknown) || IsEqualIID(iid, &IID_IProgressDialog)) > + if (IsEqualIID(iid, &IID_IUnknown)) > { > *ppvOut = This; > + TRACE("(%p, IID_IUnknown, %p) -> %p\n", This, ppvOut, This); > + } > + else if (IsEqualIID(iid, &IID_IProgressDialog)) > + { > + *ppvOut = This; this is not correct as ppvOut takes an interface and not an object. While at it please fix the above one too. thanks bye michael

1 0

[GSoC] Reduce dependency on native dlls
by William Panlener 15 Apr '12

15 Apr '12

My name is William Panlener, and I am currently attending the University of Mississippi as a first semester Masters student in Computer Science. This is my first time participating in GSoC. My proposal for GSoC involves choosing an application with high dependence on native dlls and implementing enough stubs so as to eliminate this dependency. I chose the game, League of Legends, and its installer, Pando Media Booster. Most stubs that require implementation are in msvcp90 and wininet. I have two concerns with this proposal: 1) Is it unusual to work towards improving a specific application rather than focusing on a specific component of wine? 2) The scope of the project is difficult to gauge in advance since the next problematic stub cannot be identified until all the previous problematic stubs are taken care of. Is this an issue for a GSoC proposal? I would be more than willing to revise my proposal (if this is allowed) if either of the above points is a problem.

2 1

Re: [1/2] comctl32/tests: Added tests for mouse events handling (try 3)
by Dmitry Timoshkov 15 Apr '12

15 Apr '12

Daniel Jelinski <djelinski1(a)gmail.com> wrote: > Skipping tests on WinNT - older versions of comctl send a different > set of events. Then you need to figure out what is different, and make the tests pass there as well (there is 'optional' flag for that), otherwise you risk breaking applications written for NT. > + /* WM_RBUTTONDOWN does not return until it gets another mouse event. > + Make sure it gets one by posting WM_RBUTTONUP to message queue */ > + PostMessageA(hTree, WM_RBUTTONUP, 0, (LPARAM)0x10001); > + /* this sequence should NOT send WM_CONTEXTMENU */ > + SendMessageA(hTree, WM_RBUTTONDOWN, 2, (LPARAM)0x10001); > + > + /* ditch the first sequence as it processed more messages than we need. Redo */ > + flush_sequences(sequences, NUM_MSG_SEQUENCES); > + > + PostMessageA(hTree, WM_RBUTTONUP, 0, (LPARAM)0x10001); > + SendMessageA(hTree, WM_RBUTTONDOWN, 2, (LPARAM)0x10001); This can't work. If you use PostMessage you need to flush message queue before testing the sequence. Using SendMessage after PostMessage doesn't guarantee that a posted message is handled before a sent one, you may try generating hardware messages instead. > + > + if(sequences[PARENT_SEQ_INDEX]->sequence->message == 0x133) > + { > + win_skip("Comctl32 versions prior to 5.80 send different set of events"); > + return; > + } Please use symbolic names for messages instead of magic numbers. -- Dmitry.

4 5

automate winedbg IDE integration
by Ilya Basin 15 Apr '12

15 Apr '12

Hi developers. There's a manual on this page: http://www.winehq.org/docs/winedev-guide/dbg-others > Start the Wine debugger with a command line like: > winedbg --gdb --no-start <name_of_exe_to_debug.exe> > Start ddd > In ddd, use the 'Open File' or 'Open Program' to point to the Wine executable (which is either wine-pthread or wine-kthread depending on your settings). > In the output of 1/, there's a line like > target remote localhost:32878 > copy that line and paste into ddd command pane (the one with the (gdb) prompt) So many steps. Is there an easier way? Or maybe everyone use plain winedbg without any IDE?

2 5

winedbg-eclipse - winedbg wrapper for Eclipse IDE
by Ilya Basin 14 Apr '12

14 Apr '12

- Get Eclipse 3.7.2 CDT - Import existing code as Makefile (a wine component or a standalone - winelib program) - Check "Automate discovery" in project properties/C/C++ Build/Discovery - Create a standart C/C++ Application debug configuration - Set *.exe.so as application - Set winedbg-eclipse as GDB debugger - fix bugs faster!

1 0

Re: Wine release 1.5.2
by mike＠yurick.ca 13 Apr '12

13 Apr '12

I am no longer using this e-mail. Please contact me for my new e-mail address. Thank you, Mike

1 0

Re: vbscript: Short if statement may have optional 'end if'
by Marvin 13 Apr '12

13 Apr '12

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=17842 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

1 0

gdi32/dibdrv: don't add_join if points are coincident in wide_line_segments (try 2)
by Daniel Lehman 13 Apr '12

13 Apr '12

try 2 - integrate into existing tests; updated commit message I think the only points in the middle of the points array can cause the crash I was seeing. wide_pen_lines trims coincident points/empty segments from the beginning and end of the array, so the wine_line_segment calls before and after the for loop I modified will always return valid faces

1 0

Re: gdiplus: Use StretchBlt instead of GdiAlphaBlend if device doesn't support alpha blending. Resend.
by Vincent Povirk 13 Apr '12

13 Apr '12

I ran some of my drawing tests with GdipSetCompositingMode(graphics, CompositingModeSourceCopy), and it looks like native in that mode does roughly what your patch does, except that pixels that would be 100% transparent are not drawn. If a printer device behaves differently then that would be very strange. If it is the same, it probably makes sense to use (and maybe set at graphics creation time if it's appropriate for the HDC) the compositing mode flag. So I guess this is an acceptable approach, and could probably be committed as is and refined later, but it'd be nice if you could look into compositing modes and drawing with 100% transparent colors, since you have a test program set up for printing and I don't.

1 0

Re: [PATCH 4/4] d3drm: Implement IDirect3DRMFrameX_GetChildren method and IDirect3DRMFrameArray interface. (try 2) (resend)
by Marvin 13 Apr '12

13 Apr '12

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

1 0

Re: [PATCH 3/4] d3drm: Implement IDirect3DRMFrameX_GetParent and update tests. (resend)
by Marvin 13 Apr '12

13 Apr '12

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

1 0

Re: [PATCH 4/4] d3drm: Implement IDirect3DRMFrameX_GetChildren method and IDirect3DRMFrameArray interface. (try 2) (resend)
by Marvin 13 Apr '12

13 Apr '12

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

1 0

Re: [PATCH 3/4] d3drm: Implement IDirect3DRMFrameX_GetParent and update tests. (resend)
by Marvin 13 Apr '12

13 Apr '12

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

1 0

Regression testing
by Daniel Jeliński 12 Apr '12

12 Apr '12

Hello all, I am trying to get Microsoft SQL Server Management Studio to work flawlessly under Wine. For the most part I create and triage related bug reports, but recently I also started tinkering with code, specifically with comctl library, which I am most familiar with. Back on subject. I thought I found a regression - on Wine 1.4 package downloaded from launchpad the "New query" button works fine, while on my compiled Wine it produces an error. So I did: git reset --hard wine-1.4 make and, surprisingly, I still had the problem with the compiled version. However after some combination of deleting leftover files, running make clean, make depend and make the button started working, so I started bisecting, hoping for the best. At some point I started getting bad versions, and every subsequent compile was bad - even after I ended bisecting and returned to wine-1.4, the button still did not work (and it still works under packaged Wine - I use the same install for all tests). This time make clean && make depend && make did not help. I am comparing what I did to [1], and the only difference I see is that I did not run configure before make. I'll try doing that later, but I think this shouldn't affect the outcome. Any other ideas? Also [1] suggests to set CC="ccache gcc -m32" on amd64 machines. I did that and when doing make I noticed that many lines start with: ccache gcc -m32 -m32 I guess that CC="ccache gcc" would be enough - but I didn't test that yet. Also I noticed that running parallel make (make -j) is never mentioned on [1]. Is there any reason I shouldn't use it? Daniel [1] http://wiki.winehq.org/RegressionTesting

5 6

Re: [PATCH 1/4] d3drm: Implement IDirect3DRMFrameX_AddChild. (try 2) (resend)
by Alexandre Julliard 12 Apr '12

12 Apr '12

Christian Costa <titan.costa(a)gmail.com> writes: > + children = (IDirect3DRMFrame3**)HeapAlloc(GetProcessHeap(), 0, (This->nb_children + 1) * sizeof(IDirect3DRMFrame3*)); > + if (!children) > + return E_OUTOFMEMORY; > + > + CopyMemory(children, This->children, This->nb_children * sizeof(IDirect3DRMFrame3*)); > + HeapFree(GetProcessHeap(), 0, This->children); HeapReAlloc is your friend. Also you should grow the buffer quadratically. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: kernel32/tests: Add a test for creating named mapping after closing without unmapping.
by Dmitry Timoshkov 12 Apr '12

12 Apr '12

Alexander Morozov <amorozov(a)etersoft.ru> wrote: > + ptr = MapViewOfFile(mapping, FILE_MAP_WRITE, 0, 0, 0); > + ok( ptr != NULL, "MapViewOfFile failed with error %d\n", GetLastError() ); > + CloseHandle(mapping); > + > + SetLastError(0xdeadbeef); > + mapping = CreateFileMappingA(INVALID_HANDLE_VALUE, NULL, PAGE_READWRITE, 0, MAPPING_SIZE, name); > + ok( mapping != INVALID_HANDLE_VALUE, "CreateFileMappingA failed\n" ); It would be interesting to add OpenFileMapping before and after CloseHandle and test what it returns. -- Dmitry.

1 0

Re: [PATCH] d3drm: Implement IDirect3DRMFrameX_GetTransform.
by Marvin 12 Apr '12

12 Apr '12

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

1 0

Re: GDI+ pageoffset
by Stepa Nick 11 Apr '12

11 Apr '12

> > Run with `WINEDEBUG=loaddll wine my.exe` and ensure that builtin gdiplus > is being used. I run `WINEDEBUG=loaddll wine my.exe` and get such output: > trace:loaddll:load_builtin_dll Loaded L"KERNEL32.dll" at 0x7b810000: builtin > trace:loaddll:load_native_dll Loaded L"Z:\\home\\user\\tmp\\test\\CalculateCPP.exe" at 0x400000: native > trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\msvcrt.dll" at 0x72540000: builtin > trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\advapi32.dll" at 0x68550000: builtin > trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\gdi32.dll" at 0x684b0000: builtin > trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\version.dll" at 0x6e960000: builtin > trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\user32.dll" at 0x68380000: builtin > trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\rpcrt4.dll" at 0x70d00000: builtin > trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\ole32.dll" at 0x685c0000: builtin > trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\gdiplus.dll" at 0x4ec50000: native > trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\MSVCR100.dll" at 0x78aa0000: native > trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\shlwapi.dll" at 0x686c0000: builtin > trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\comctl32.dll" at 0x68720000: builtin > trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\msimg32.dll" at 0x68810000: builtin > trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\mfc100u.dll" at 0x785f0000: native > trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\imm32.dll" at 0x68bc0000: builtin > trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\winex11.drv" at 0x68980000: builtin > trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\uxtheme.dll" at 0x68c10000: builtin > trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\dwmapi.dll" at 0x68c40000: builtin > trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\MFC100ENU.DLL" at 0x5d360000: native > fixme:heap:HeapSetInformation (nil) 1 (nil) 0 > fixme:win:EnumDisplayDevicesW ((null),0,0x32f744,0x00000000), stub! So, non-native gdiplus.dll used?! Hmm... Can I see into gdiplus.dll anyway? I really need to understand how pixeloffset works.

2 1

Re: ws2_32/tests: Update hostent struct tests
by Austin English 11 Apr '12

11 Apr '12

On Tue, Apr 10, 2012 at 21:13, Bruno Jesus <00cpxxx(a)gmail.com> wrote: > * Added a final required test for the h->h_addr_list[0] to show we > must put it in the right place. > * Removed the cached use of older gethostbyname result since the > memory is static and turned into garbage in windows if the current > call fails. > * Added a skip if we hit older OS allowing we to avoid using broken() > on each test. + if(h->h_addr_list == addr.mem) /* <= W2K */ + { + skip("Skipping hostent tests since this OS is unsupported\n"); + return; + } + You should use win_skip so that the tests will only be skipped on windows (we'd want the failure to be exposed on wine). -- -Austin

2 2

Re: gdi32/dibdrv: don't add_join if points are coincident in wide_line_segments
by Alexandre Julliard 11 Apr '12

11 Apr '12

Daniel Lehman <dlehman(a)esri.com> writes: > This fixes a crash in PolyPolyline if points are in the same spot > > There were timeouts in the Testbot but were unrelated to anything I changed > > From 23edf2c2b89b98ef18849806e74b5d77f7889160 Mon Sep 17 00:00:00 2001 > From: Daniel Lehman <dlehman(a)esri.com> > Date: Wed, 25 Jan 2012 13:47:31 -0800 > Subject: gdi32/dibdrv: don't add_join if points are coincident in wide_line_segments > > if 2 points coincide (dx == dy == 0), wide_line_segments returns immediately > in that case, face_1 is not changed. it is not initialized so junk values on the > stack are used. when passed to add_join they create a region that causes a huge > amount of memory to be allocated. depending on the values, all available/rlimit > memory is exhausted and the program crashes. reverting to 1.3.26 works fine > > the test case submitted is a drastically reduced, simplest possible form of what our > internal test does, based on real map data You should integrate the test with the other graphics tests, to reuse all the infrastructure and also verify the graphics results. Also there is probably the same problem with the first and last points. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: d3drm: Some includes are useless
by Alexandre Julliard 11 Apr '12

11 Apr '12

Nozomi Kodama <nozomi.kodama(a)yahoo.com> writes: > From 9772529c63a9c11bc169545b6d68722308591a2f Mon Sep 17 00:00:00 2001 > From: Nozomi Kodama <nozomi.kodama(a)yahoo.com> > Date: Tue, 10 Apr 2012 10:50:31 +0200 > Subject: Some includes are useless That sort of change is not useful, the headers will be included anyway. -- Alexandre Julliard julliard(a)winehq.org

1 0

GDI+ pageoffset
by Stepa Nick 11 Apr '12

11 Apr '12

Hello. I have following code: > Bitmap * bmp = new Bitmap(500, 500, PixelFormat32bppARGB); > { > Graphics gr(bmp); > > //FIRST LINE > PointF* local1PointF = new PointF(17.823631, 89.429169); > PointF* local2PointF = new PointF(17.823631, 87.577080); > > //SECOND LINE > PointF* local3PointF = new PointF(14.933444, 89.429169); > PointF* local4PointF = new PointF(14.933444, 87.577080); > Pen * pen = new Pen(Color(255, 0, 0), 0.1); > gr.SetPageUnit(UnitMillimeter); > > gr.SetPixelOffsetMode(PixelOffsetModeHalf); //PROBLEM! > > gr.DrawLine(pen,(*local1PointF),(*local2PointF)); > gr.DrawLine(pen,(*local3PointF),(*local4PointF)); > } When I run it without SetPixelOffsetMode i get equal line, but with it line are not identical(first line is longer). I explore "dlls/gdiplus/graphics.c" and i find this comment: "/* FIXME: Pixel offset mode is not used anywhere except the getter/setter. */". So, I what to understand why I have different images(how pixeloffset affect on drawing lines)? I try to run windbg, run `WINEDEBUG=gdiplus,gdi,ddraw,graphics wine ./my.exe`, but analyzing output didn`t give my any results. Thanks!

2 1

Re: [PATCH 3/3] comctl32: Truncate the info tip text when using ANSI version messages.
by Marvin 11 Apr '12

11 Apr '12

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=17802 Your paranoid android. === WNT4WSSP6 (32 bit tooltips) === tooltips.c:755: Test failed: lpszText has 0 chars

1 0

Re: [PATCH 2/3] comctl32/tests: Add tests for long info tip texts.
by Marvin 11 Apr '12

11 Apr '12

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=17801 Your paranoid android. === WNT4WSSP6 (32 bit tooltips) === tooltips.c:755: Test failed: lpszText has 0 chars

1 0

Re: [PATCH 1/2] server: Add mechanism to retrieve the connect time of a socket (try 2).
by Dmitry Timoshkov 11 Apr '12

11 Apr '12

"Erich E. Hoover" <ehoover(a)mines.edu> wrote: > +/* Get information about a socket */ > +DECL_HANDLER(get_socket_info) > +{ > + struct sock *sock; > + > + sock=(struct sock *)get_handle_obj( current->process, req->handle, FILE_WRITE_ATTRIBUTES, &sock_ops ); Shouldn't the required access be FILE_READ_ATTRIBUTES or FILE_READ_PROPERTIES? Why write access is requied in order to read the socket connect time? Also please avoid including auto generated code in the patch. -- Dmitry.

2 1

Re: [PATCH 1/6] msvcrt: Rewrite asctime function
by Alexandre Julliard 11 Apr '12

11 Apr '12

Piotr Caban <piotr(a)codeweavers.com> writes: > @@ -48,7 +49,7 @@ static const int MonthLengths[2][12] = > > static inline int IsLeapYear(int Year) > { > - return Year % 4 == 0 && (Year % 100 != 0 || Year % 400 == 0); > + return (Year % 4 == 0 && (Year % 100 != 0 || Year % 400 == 0)) ? 1 : 0; Maybe you should do something like: return (((Year % 4 == 0 && (Year % 100 != 0 || Year % 400 == 0)) ? 1 : 0) ? 1 : 0) ? 1 : 0; to make really sure you get 0 or 1, you never know what might happen ;-) -- Alexandre Julliard julliard(a)winehq.org

3 2

Re: [1/2] comctl32/tests: Added tests for mouse events handling (try 5)
by Marvin 10 Apr '12

10 Apr '12

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=17777 Your paranoid android. === WNT4WSSP6 (32 bit treeview) === treeview.c:1894: Test failed: right click (parent): the msg sequence is not complete: expected 0000 - actual 0133 treeview.c:1895: Test failed: right click (tree): the msg sequence is not complete: expected 0000 - actual 000f treeview.c:1902: Test failed: right drag (parent): the msg sequence is not complete: expected 0000 - actual 0133 treeview.c:1903: Test failed: right drag (tree): the msg sequence is not complete: expected 0000 - actual 000f

1 0

Re: [1/2] comctl32/tests: Added tests for mouse events handling (try 4)
by Marvin 10 Apr '12

10 Apr '12

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=17772 Your paranoid android. === WNT4WSSP6 (32 bit treeview) === treeview.c:1892: Test failed: right click (parent): in msg 0x004e expecting id 0xfffffffb got 0xfffffff4 treeview.c:1892: Test failed: right click (parent): the msg sequence is not complete: expected 0000 - actual 004e treeview.c:1893: Test failed: right click (tree): the msg 0x000f should NOT have been sent by DefWindowProc treeview.c:1893: Test failed: right click (tree): the msg sequence is not complete: expected 0000 - actual 000f treeview.c:1900: Test failed: right drag (parent): in msg 0x004e expecting id 0xfffffe68 got 0xfffffff4 treeview.c:1900: Test failed: right drag (parent): the msg sequence is not complete: expected 0000 - actual 004e treeview.c:1901: Test failed: right drag (tree): the msg 0x000f should NOT have been sent by DefWindowProc treeview.c:1901: Test failed: right drag (tree): the msg sequence is not complete: expected 0000 - actual 000f

1 0

Re: [PATCH 1/6] msvcrt: Rewrite asctime function (try3)
by Alexandre Julliard 10 Apr '12

10 Apr '12

Piotr Caban <piotr(a)codeweavers.com> writes: > + || !MSVCRT_CHECK_PMT(asctime_buf(time, mstm) != NULL)) { You don't want to use MSVCRT_CHECK_PMT this way, the error won't make sense. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH 1/2] server: Add mechanism to retrieve the connect time of a socket (resend 2, deferred, rebased).
by Alexandre Julliard 10 Apr '12

10 Apr '12

"Erich E. Hoover" <ehoover(a)mines.edu> writes: > Real Name: > Erich Hoover > > Description: > This patch implements storing the connect time of a socket for > retrieval with the SO_CONNECT_TIME socket option (part 2). > > Changelog: > server: Add mechanism to retrieve the connect time of a socket. You should make it a generic get_info request, and return the time in standard server format. -- Alexandre Julliard julliard(a)winehq.org

2 2

Re: msvcrt: Add bsearch_s implementation by reusing code and tests from ntdll (try 4)
by Alexandre Julliard 10 Apr '12

10 Apr '12

André Hentschel <nerv(a)dawncrow.de> writes: > /********************************************************************* > + * bsearch_s (msvcrt.@) > + */ > +void* CDECL MSVCRT_bsearch_s(const void *key, const void *base, > + MSVCRT_size_t nmemb, MSVCRT_size_t size, > + int (__cdecl *compare)(void *, const void *, const void *), void *ctx) > +{ > + ssize_t min = 0; > + ssize_t max; > + > + if (!MSVCRT_CHECK_PMT(key != NULL) || !MSVCRT_CHECK_PMT(base != NULL) || > + !MSVCRT_CHECK_PMT(size != 0) || !MSVCRT_CHECK_PMT(compare != NULL)) > + { > + *MSVCRT__errno() = MSVCRT_EINVAL; > + return NULL; > + } > + > + if (!MSVCRT_CHECK_PMT(nmemb != 0) || !MSVCRT_CHECK_PMT(ctx != NULL)) > + { > + *MSVCRT__errno() = 0; > + return NULL; > + } That looks even more suspicious... -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH 6/6] msvcrt/tests: Added more strftime tests
by Marvin 10 Apr '12

10 Apr '12

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=17760 Your paranoid android. === WNT4WSSP6 (32 bit time) === time.c:605: Test failed: errno = -559038737 time: unhandled exception c0000005 at 78013981 === W2KPROSP4 (32 bit time) === time.c:605: Test failed: errno = -559038737 time: unhandled exception c0000005 at 7801124A === WXPPROSP3 (32 bit time) === time.c:605: Test failed: errno = -559038737 time: unhandled exception c0000005 at 77C4900F === W2K3R2SESP2 (32 bit time) === time.c:605: Test failed: errno = -559038737 time: unhandled exception c0000005 at 77BD9F8B

1 0

Re: [PATCH 1/6] msvcrt: Rewrite asctime function
by Marvin 10 Apr '12

10 Apr '12

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=17759 Your paranoid android. === WNT4WSSP6 (32 bit time) === time.c:646: Test failed: asctime returned time.c:647: Test failed: errno = -559038737 time.c:658: Test failed: asctime returned Wed Feb 30 02:58:41 1979 time.c:659: Test failed: errno = -559038737 === W2KPROSP4 (32 bit time) === time.c:646: Test failed: asctime returned time.c:647: Test failed: errno = -559038737 time.c:658: Test failed: asctime returned Wed Feb 30 02:58:41 1979 time.c:659: Test failed: errno = -559038737 === WXPPROSP3 (32 bit time) === time.c:646: Test failed: asctime returned time.c:647: Test failed: errno = -559038737 time.c:658: Test failed: asctime returned Wed Feb 30 02:58:41 1979 time.c:659: Test failed: errno = -559038737 === W2K3R2SESP2 (32 bit time) === time.c:646: Test failed: asctime returned time.c:647: Test failed: errno = -559038737 time.c:658: Test failed: asctime returned Wed Feb 30 02:58:41 1979 time.c:659: Test failed: errno = -559038737

1 0

'Pending' patches state
by Dmitry Timoshkov 10 Apr '12

10 Apr '12

Hello, http://source.winehq.org/patches has the following legend for the Pending patch status: Pending * The patch is not obviously correct at first glance. Making a more convincing argument, preferably in the form of a test case, may help. * Waiting for feedback from the main developer in that area. It's very confusing, and absolutely not clear what is required from the patch submitter, especially since *there is no any feedback on the patch*. 'Rejected' at least requies some sort of feedback, while 'Pending' doesn't. To me 'Pending' looks like a silent case of 'Reject', but without any obligation to explain why. I find myself on somewhat shaky ground when I see a bunch of my patches in the pending state, especially if they already contain the tests and main developer in the area I'm changing is Alexandre :). Is it possible to get at least some feedback for pending patches? Pretty please? -- Dmitry.

6 13

RFC: KUSER_SHARED_DATA update patch to fix bug 29168
by Joey Yandle 10 Apr '12

10 Apr '12

Hi everybody, As originally discovered by Carsten Juttner, Star Wars: The Old Republic uses the time values in KUSER_SHARED_DATA to trigger network send buffers. wine does not currently update these values, so TOR does not make it past an initial server handshake. I'm attaching my current patch which fixes this. It updates the values every 15600000 nanoseconds as does Windows 7, and presumably all Windows versions. The words of the timers are written in the correct order for applications to detect clock tick. It uses a separate thread which does nothing else; a previous attempt at an NtTimer based solution did not work, presumably due to irregularity in the exact callback times. Attempts at setting thread priority were also abandoned after many people were unable to run the code. The patch does not check the return code of nanosleep; I could add code to nanosleep again for the remaining time in the case of an interrupt, but didn't think it was necessary. I could also change it to use clock_nanosleep, which would allow for more absolute timing. Please let me know what you think. cheers, Joey

9 34

Re: [PATCH 2/2] wininet/tests: Added checks for bad return values and skip tests when it happens. (try 2)
by Alexandre Julliard 09 Apr '12

09 Apr '12

Morten Rønne <morten.roenne(a)tdcadsl.dk> writes: > diff --git a/dlls/wininet/tests/urlcache.c b/dlls/wininet/tests/urlcache.c > index 02d8d28..1bf3f23 100644 > --- a/dlls/wininet/tests/urlcache.c > +++ b/dlls/wininet/tests/urlcache.c > @@ -60,7 +60,20 @@ static void test_find_url_cache_entriesA(void) > hEnumHandle = FindFirstUrlCacheEntry(NULL, NULL, &cbCacheEntryInfo); > ok(!hEnumHandle, "FindFirstUrlCacheEntry should have failed\n"); > ok(GetLastError() == ERROR_INSUFFICIENT_BUFFER, "FindFirstUrlCacheEntry should have set last error to ERROR_INSUFFICIENT_BUFFER instead of %d\n", GetLastError()); > + if (GetLastError() != ERROR_INSUFFICIENT_BUFFER) > + { > + skip("Find*UrlCacheEntry tests skipped, due to wrong return value\n"); > + return; > + } You don't need to add skip() for that sort of thing, it's not supposed to happen, and if it does there will already be a test failure in the report. -- Alexandre Julliard julliard(a)winehq.org

2 2

Re: [1/3] shell32: Add test for GetCurrentProcessExplicitAppUserModelID.
by Alexandre Julliard 09 Apr '12

09 Apr '12

Vincent Povirk <madewokherd(a)gmail.com> writes: > @@ -3,6 +3,7 @@ IMPORTS = shell32 ole32 oleaut32 user32 advapi32 > > C_SRCS = \ > appbar.c \ > + appusermodel.c \ > assoc.c \ > autocomplete.c \ > brsfolder.c \ I don't think you need a new file for that. -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: msvcrt: Add bsearch_s implementation by reusing code and tests from ntdll (try 3)
by Alexandre Julliard 09 Apr '12

09 Apr '12

André Hentschel <nerv(a)dawncrow.de> writes: > @@ -124,6 +124,39 @@ void* CDECL _lsearch(const void* match, void* start, > } > > /********************************************************************* > + * bsearch_s (msvcrt.@) > + */ > +void* CDECL MSVCRT_bsearch_s(const void *key, const void *base, > + MSVCRT_size_t nmemb, MSVCRT_size_t size, > + int (__cdecl *compare)(void *, const void *, const void *), void *ctx) > +{ > + ssize_t min = 0; > + ssize_t max; > + > + if (!MSVCRT_CHECK_PMT(key != NULL) || !MSVCRT_CHECK_PMT(base != NULL) || > + !MSVCRT_CHECK_PMT(nmemb != 0) || !MSVCRT_CHECK_PMT(size != 0) || > + !MSVCRT_CHECK_PMT(compare != NULL) || !MSVCRT_CHECK_PMT(ctx != NULL)) > + { Some of these look suspicious, you need more tests. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: jscript: Replace only the first match for non-regexp pattern in String.replace
by Marvin 09 Apr '12

09 Apr '12

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=17730 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

1 0

Re: ws2_32/tests: Add hostent struct tests for gethostbyname
by Marvin 08 Apr '12

08 Apr '12

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=17727 Your paranoid android. === WXPPROSP3 (32 bit sock) === sock.c:509: Test failed: oob_server (1ac): unexpectedly at the OOB mark: 0 sock.c:519: Test failed: oob_server (1ac): unexpectedly at the OOB mark: 0

3 4

Re: [2/2] comctl32: Fix message sequence on right mouse click
by Marvin 07 Apr '12

07 Apr '12

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=17723 Your paranoid android. === WNT4WSSP6 (32 bit treeview) === treeview.c:1886: Test failed: right click (parent): the msg 0x004e was expected, but got msg 0x0133 instead treeview.c:1886: Test failed: right click (parent): the msg sequence is not complete: expected 0000 - actual 004e treeview.c:1887: Test failed: right click (tree): the msg 0x0215 was expected, but got msg 0x000f instead treeview.c:1887: Test failed: right click (tree): the msg sequence is not complete: expected 0000 - actual 0215 treeview.c:1894: Test failed: right drag (parent): the msg 0x004e was expected, but got msg 0x0133 instead treeview.c:1894: Test failed: right drag (parent): the msg sequence is not complete: expected 0000 - actual 004e treeview.c:1895: Test failed: right drag (tree): the msg 0x0215 was expected, but got msg 0x000f instead treeview.c:1895: Test failed: right drag (tree): the msg sequence is not complete: expected 0000 - actual 0215

1 0

Re: [1/2] comctl32/tests: Added tests for mouse events handling
by Marvin 07 Apr '12

07 Apr '12

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=17721 Your paranoid android. === WNT4WSSP6 (32 bit treeview) === treeview.c:1888: Test failed: right click (parent): the msg 0x004e was expected, but got msg 0x0133 instead treeview.c:1889: Test failed: right click (tree): the msg 0x0215 was expected, but got msg 0x000f instead treeview.c:1896: Test failed: right drag (parent): the msg 0x004e was expected, but got msg 0x0133 instead treeview.c:1896: Test failed: right drag (parent): the msg sequence is not complete: expected 0000 - actual 004e treeview.c:1897: Test failed: right drag (tree): the msg 0x0215 was expected, but got msg 0x000f instead treeview.c:1897: Test failed: right drag (tree): the msg sequence is not complete: expected 0000 - actual 0215

1 0

Re: [PATCH 2/3] wininet/tests: Added more tests for urlcache, including a new flag in CacheEntryType.
by Piotr Caban 07 Apr '12

07 Apr '12

Hi, On 04/05/12 08:50, Morten Rønne wrote: diff --git a/include/wininet.h b/include/wininet.h #define URLHISTORY_CACHE_ENTRY 0x00200000 +#define DELETED_CACHE_ENTRY 0x00400000 #define TRACK_OFFLINE_CACHE_ENTRY 0x00000010 DELETED_CACHE_ENTRY is not defined in native wininet.h header that I have. Did you find a header with it? If not, it should not be defined there. Cheers, Piotr

2 2

Re: winealsa: Fix an uninitialized variable compiler warning.
by Andrew Eikum 07 Apr '12

07 Apr '12

Thanks. GCC 4.7 must be smart enough to detect the same if-conditions, and doesn't issue a warning for me. Kind of impressive, actually. Andrew On Fri, Apr 06, 2012 at 02:49:38AM +0200, Józef Kucia wrote: > --- > dlls/winealsa.drv/mmdevdrv.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/dlls/winealsa.drv/mmdevdrv.c b/dlls/winealsa.drv/mmdevdrv.c > index c99186b..1438f5b 100644 > --- a/dlls/winealsa.drv/mmdevdrv.c > +++ b/dlls/winealsa.drv/mmdevdrv.c > @@ -343,7 +343,7 @@ static WCHAR *construct_device_id(EDataFlow flow, const WCHAR *chunk1, const cha > { > WCHAR *ret; > const WCHAR *prefix; > - DWORD len_wchars = 0, chunk1_len, copied = 0, prefix_len; > + DWORD len_wchars = 0, chunk1_len = 0, copied = 0, prefix_len; > > static const WCHAR dashW[] = {' ','-',' ',0}; > static const size_t dashW_len = (sizeof(dashW) / sizeof(*dashW)) - 1; > -- > 1.7.8.5 > > >

2 1

RFC: Getting CorelDraw 12 installation done - was: A donation for Corel Draw 12 - support.
by Gerold Jens Wucherpfennig 06 Apr '12

06 Apr '12

Hi can someone give me some hints about fixing wine for Corel 12 support? The installation seems to succeed at first glance, but comparing the installation folder to the folder of an installation on Windows XP reveals that only 2/3 of the installation was done. I updated the APPDB: http://appdb.winehq.org/objectManager.php?sClass=version&iId=2390 On 03/26/2012 09:52 AM, Frédéric Delanoy wrote: > On Sat, Mar 24, 2012 at 19:45, Gerold Jens Wucherpfennig > <gjwucherpfennig(a)gmx.net> wrote: >> http://appdb.winehq.org/objectManager.php?sClass=version&iId=2390 >> >> Installation worked, but Corel is not usable and only reports: >> >> "Registry Corrupt - The UI Language registration list is invalid" > > That page indicates the last tested version. > > Did you try Core Draw 12 with 1.4 or 1.5 and get the same errors? > > If you did, you might want to add test data in the AppDB entry, so > other people don't spend time duplicating your test. > If you didn't, maybe will retesting with 1.4 or 1.5 reveal it works > correctly for your needs? > > Frédéric I want to make a small donation to winehq, if we can get Corel 12 running on Wine... Here is the installation log: gerold@gerold-AOD270:/media/6B35-950F/Corel$ wine ./setup.exe wine: created the configuration directory '/home/gerold/.wine' fixme:storage:create_storagefile Storage share mode not implemented. err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot fixme:iphlpapi:NotifyAddrChange (Handle 0xede318, overlapped 0xede2e0): stub fixme:storage:create_storagefile Storage share mode not implemented. err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot fixme:iphlpapi:NotifyAddrChange (Handle 0xfee8ec, overlapped 0xfee8d0): stub wine: configuration in '/home/gerold/.wine' has been updated. fixme:storage:create_storagefile Storage share mode not implemented. fixme:storage:create_storagefile Storage share mode not implemented. fixme:vbscript:parse_script parser failed on parsing L"(\"SERIALNUMBER\") = \"DR12WTX-9999998-YSP\"\r\n\tSession.Property(\"TypeB\") = \"1\"\r\nEnd If\r\n\r\n'///////////////////////////////////////////////\r\nFunction IsFeatureExists(sFeature)\r\nOn Error Resume Next\r\n\r\n\tDim objDB: Set objDB = Session.Database\r\n\r\n\tDim sQuery: sQuery = \"SELECT"... err:ole:ClientRpcChannelBuffer_SendReceive called from wrong apartment, should have been 0x2a0000003d err:ole:xCall RpcChannelBuffer SendReceive failed, 8001010e fixme:ntdll:NtFsControlFile FSCTL_PIPE_IMPERSONATE: impersonating self fixme:vbscript:parse_script parser failed on parsing L"(\"ShowLanguagePackDialog\") = \"1\"\r\nElse\r\n\tIf (IsFeatureExists(\"EN\") = \"1\") Then\r\n\t\tSession.Property(\"ENLANG\") = \"1\"\r\n\tEnd If\r\n\tIf (IsFeatureExists(\"DE\") = \"1\") Then\r\n\t\tSession.Property(\"DELANG\") = \"1\"\r\n\tEnd If\r\n\tIf (IsFeatureExists(\"FR\") = \"1\") Then\r\n"... err:ole:ClientRpcChannelBuffer_SendReceive called from wrong apartment, should have been 0x2a0000003d err:ole:xCall RpcChannelBuffer SendReceive failed, 8001010e fixme:ntdll:NtFsControlFile FSCTL_PIPE_IMPERSONATE: impersonating self err:ole:ClientRpcChannelBuffer_SendReceive called from wrong apartment, should have been 0x2a0000003d err:ole:xCall RpcChannelBuffer SendReceive failed, 8001010e fixme:ntdll:NtFsControlFile FSCTL_PIPE_IMPERSONATE: impersonating self err:ole:ClientRpcChannelBuffer_SendReceive called from wrong apartment, should have been 0x2a0000003d err:ole:xCall RpcChannelBuffer SendReceive failed, 8001010e fixme:ntdll:NtFsControlFile FSCTL_PIPE_IMPERSONATE: impersonating self err:ole:ClientRpcChannelBuffer_SendReceive called from wrong apartment, should have been 0x2a0000003d err:ole:xCall RpcChannelBuffer SendReceive failed, 8001010e fixme:ntdll:NtFsControlFile FSCTL_PIPE_IMPERSONATE: impersonating self err:ole:ClientRpcChannelBuffer_SendReceive called from wrong apartment, should have been 0x2a0000003d err:ole:xCall RpcChannelBuffer SendReceive failed, 8001010e fixme:ntdll:NtFsControlFile FSCTL_PIPE_IMPERSONATE: impersonating self fixme:vbscript:parse_script parser failed on parsing L"1\r\nConst msiInstallStateAdvertise = 1\r\nConst msiInstallStateAbsent = 2\r\nConst msiInstallStateLocal = 3\r\nConst msiInstallStateSource = 4\r\nConst msiInstallStateDefault = 5\r\nDim nRemoveVBAEN:nRemoveVBAEN = 0\r\nDim nRemoveVBACZ:nRemoveVBACZ = 0\r\nDim nRemoveVBANL:nRemoveVBAPL = 0\r\n\r\nOn "... fixme:vbscript:parse_script parser failed on parsing L"1\r\nConst msiInstallStateAdvertise = 1\r\nConst msiInstallStateAbsent = 2\r\nConst msiInstallStateLocal = 3\r\nConst msiInstallStateSource = 4\r\nConst msiInstallStateDefault = 5\r\n\r\nOn Error Resume Next\r\n\r\nIf (IsFeatureSelected(\"FontNav\") = True) Then\r\n If ((Session.Property(\"PLLANG\""... err:ole:ClientRpcChannelBuffer_SendReceive called from wrong apartment, should have been 0x2a0000003d err:ole:xCall RpcChannelBuffer SendReceive failed, 8001010e fixme:ntdll:NtFsControlFile FSCTL_PIPE_IMPERSONATE: impersonating self fixme:vbscript:parse_script parser failed on parsing L"1\r\nConst msiInstallStateAdvertise = 1\r\nConst msiInstallStateAbsent = 2\r\nConst msiInstallStateLocal = 3\r\nConst msiInstallStateSource = 4\r\nConst msiInstallStateDefault = 5\r\n\r\nOn Error Resume Next\r\n\r\nIf (IsFeatureSelected(\"FontNav\") = True) Then\r\n If ((Session.Property(\"PLLANG\""... err:ole:ClientRpcChannelBuffer_SendReceive called from wrong apartment, should have been 0x2a0000003d err:ole:xCall RpcChannelBuffer SendReceive failed, 8001010e fixme:ntdll:NtFsControlFile FSCTL_PIPE_IMPERSONATE: impersonating self err:ole:ClientRpcChannelBuffer_SendReceive called from wrong apartment, should have been 0x2a0000003d err:ole:xCall RpcChannelBuffer SendReceive failed, 8001010e fixme:ntdll:NtFsControlFile FSCTL_PIPE_IMPERSONATE: impersonating self fixme:vbscript:parse_script parser failed on parsing L"1\r\nConst msiInstallStateAdvertise = 1\r\nConst msiInstallStateAbsent = 2\r\nConst msiInstallStateLocal = 3\r\nConst msiInstallStateSource = 4\r\nConst msiInstallStateDefault = 5\r\n\r\nOn Error Resume Next\r\n\t\r\nIf (IsFeatureExists(\"LocalInstallsOnly\")=\"1\") Then\r\n\tIf ((Session.Property(\""... err:ole:ClientRpcChannelBuffer_SendReceive called from wrong apartment, should have been 0x2a0000003d err:ole:xCall RpcChannelBuffer SendReceive failed, 8001010e fixme:ntdll:NtFsControlFile FSCTL_PIPE_IMPERSONATE: impersonating self err:ole:ClientRpcChannelBuffer_SendReceive called from wrong apartment, should have been 0x2a0000003d err:ole:xCall RpcChannelBuffer SendReceive failed, 8001010e fixme:ntdll:NtFsControlFile FSCTL_PIPE_IMPERSONATE: impersonating self fixme:msi:ITERATE_CreateShortcuts poorly handled shortcut format, advertised shortcut fixme:msi:ITERATE_CreateShortcuts poorly handled shortcut format, advertised shortcut fixme:msi:ITERATE_CreateShortcuts poorly handled shortcut format, advertised shortcut fixme:msi:ITERATE_CreateShortcuts poorly handled shortcut format, advertised shortcut fixme:msi:ITERATE_CreateShortcuts poorly handled shortcut format, advertised shortcut fixme:msi:ITERATE_CreateShortcuts poorly handled shortcut format, advertised shortcut fixme:msi:ITERATE_CreateShortcuts poorly handled shortcut format, advertised shortcut err:ole:ClientRpcChannelBuffer_SendReceive called from wrong apartment, should have been 0x2a0000003d err:ole:xCall RpcChannelBuffer SendReceive failed, 8001010e fixme:ntdll:NtFsControlFile FSCTL_PIPE_IMPERSONATE: impersonating self gerold@gerold-AOD270:/media/6B35-950F/Corel$ Thanks in advance! Gerold

1 0

Re: ddraw: Improve GetScanLine stub so it's usable for timing related tasks
by Christian Costa 06 Apr '12

06 Apr '12

Le 06/04/2012 12:35, Piotr Caban a écrit : > + /* Simulate a 60Hz display */ > + time = GetTickCount(); > + frame_progress = time& 15; /* time % (1000 / 60) */ > + if (!frame_progress) > + { > + *Scanline = 0; > + return DDERR_VERTICALBLANKINPROGRESS; > + } > + > + /* convert frame_progress to estimated scan line */ > + lines = mode.height / 15; > + *Scanline = (frame_progress - 1) * lines + time % lines; > return DD_OK; > } Is time % lines here is to generate a random values (sort of noise) ?

2 2

Re: [GSoC] Control panel proposal
by Magdalena Nowak 06 Apr '12

06 Apr '12

On 6 April 2012 11:06, André Hentschel <nerv(a)dawncrow.de> wrote: > Am 06.04.2012 01:35, schrieb Magdalena Nowak: >> Hey André, >> >> On 5 April 2012 22:46, André Hentschel <nerv(a)dawncrow.de> wrote: >>> >>>> The second solution would be to have a separate applet for >>>> per-application settings. The screens would be stored in a DLL, for >>>> example, as to avoid duplication. >>> >>> I dislike that, that seems just like a new view of winecfg. Further i doubt that you can store Wine specific things in a Wine specific DLL. >> >> I didn't like this idea either, but I have included it for the sake of >> completeness. > > That's good :) > >>> I think this project is doable, but might be hard to get the patches accepted i guess. >> >> What makes you say that? > > One or two people already tried IIRC and failed, but most likely they missed the part with the per-app configuration that you have seen. I think it's a great feature, but very hard to implement. That's why I've had a few ideas in mind. > Further you have to keep in mind that winecfg is a historical app, you'll need a nice and clean incremental way of patching it out. That's why I want to work incrementally, (c.f. the timeline on my proposal). > For further communication please CC wine-devel. Oops! BTW, the proposal can be found on http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/magdalen…

1 0

Re: winedump: Add basic support for dumping the property store in lnk files.
by Dmitry Timoshkov 06 Apr '12

06 Apr '12

Vincent Povirk <madewokherd(a)gmail.com> wrote: > +typedef struct tagLINK_PROPERTYSTORAGE_VALUE > +{ > + DWORD size; > + DWORD pid; > + BYTE unknown8; > + DWORD vt; > + DWORD unknown25; > +} LINK_PROPERTYSTORAGE_VALUE; You probably need an appropriate packing for this structure. -- Dmitry.

2 2

[GSoC] Control panel proposal
by Magdalena Nowak 05 Apr '12

05 Apr '12

Hi, my name is Magdalena Nowak and I'd like to apply for this year's Summer of Code with Wine. My proposal is to merge the two control panel suggestions (Tools - Merge winecfg and control panel and Tools - Implement new control panel applets) into one project. I would start off with splitting winecfg into several applets. Roughly, each tab would become a new applet. The Applications applet would only be used to register applications with the control panel to allow the user to specify custom settings for that application. I would like to merge the Graphics tab with the Appearance section of Desktop Integration (and this applet would be the place where the 3D settings would go later) and merge the Folders section with the Drives tab into one applet. Later on, I will start implementing new applets. For example, create a Networking applet for the network-related settings, maybe a simple diagnostics tool (a read-only applet with information regarding build options and system resources), Fonts (both list of fonts available to Wine as well as hinting and DPI settings), a System applet for settings like owner name, Windows version, libraries etc. There is a problem with per-application settings. I have three possible solutions to this problem. I have made pictures to illustrate what I mean. One would be to simply add a drop-down list to each applet that contains settings that can be per-application settings. The drop-down list would contain a "global" entry, as well as entries for each application registered through the Applications applet. Upon selecting an entry, the applet would load the settings for this program. The second solution would be to have a separate applet for per-application settings. The screens would be stored in a DLL, for example, as to avoid duplication. The third, and my favourite, solution, is to create a virtual control panel for each registered application. The user would be able to select the application or global settings from some kind of list, and the applets would be passed an argument to indicate the selected application. If a specific setting was global-only, it would be highlighted appropriately. Here are the promised images: http://imgur.com/T4pUV - Showing the drop-down menu at the top of the applet window. http://imgur.com/vA1Vq - Showing the per-application settings applet. http://imgur.com/is63I - Showing the control panel with an application selected, and a Graphics applet showing a global-only setting. Of course these are only examples, I welcome any comments. I will post a proposal on Melange soon. Yours, 'Lena.

2 2

[3/3] shell32: Add test for STARTF_TITLEISAPPID flag.
by Vincent Povirk 05 Apr '12

05 Apr '12

1 1

urlcache: what all are you working on?
by Juan Lang 05 Apr '12

05 Apr '12

Hi Morten and Piotr, I notice both of you are working on wininet's url cache. That's great: it's largely bitrot, and has been for years. My question is, what are you planning to fix? It seems like you're both running into some of the same issues right now, and it would be nice if you could coordinate a little. Ok, I lie: it'd be nice to get code from both of you ;) If I were to guess, it looks like you're both working on eliminating corruption and deadlocks, both of which can occur right now. Fantastic. Another thing that'd be nice to see is reducing the amount of disk space used. Morten, some of the patches you sent me do some of that, by removing files once they're no longer in use. (The patches I have do that too.) Piotr, were you planning to address this too? A question that I have to ask is, would be better to eliminate the url cache altogether? Right now its only utility is to pass test cases, and conveniently fill up your disk. No requests are ever fulfilled from the cache. Either of you have any plans to tackle that? Thanks, --Juan

3 2

qemu still can't run x86 wine
by Dan Kegel 05 Apr '12

05 Apr '12

http://wiki.winehq.org/ARM says commands like $ qemu-i386 /usr/local/qemu-i386/wine/bin/wine /usr/local/qemu-i386/wine/c/Program\ Files/putty.exe used to work, but doesn't anymore. I gave it a shot anyway, just trying to run x86 apps inside wine inside qemu: wget http://wiki.qemu.org/download/qemu-1.0.1.tar.gz tar -xzvf qemu-1.0.1.tar.gz cd qemu-1.0.1 ./configure --prefix=/usr/local/qemu --target-list=i386-linux-user make # Compilation fails; to work around, edit linux-user/syscall.c and # replace soundcard.h with soundcard.h.oss3 make sudo make install # Verify that qemu can run a trivial binary /usr/local/qemu/bin/qemu-i386 /bin/uname -a # Verify you can run wine a little /usr/local/qemu/bin/qemu-i386 /usr/bin/wine --version # Now run a real app /usr/local/qemu/bin/qemu-i386 /usr/bin/wine cmd /c echo hi qemu: Unsupported syscall: 240 # Huh. That didn't work. OK, try sh: /usr/local/qemu/bin/qemu-i386 /bin/sh $ ls /bin/sh: 1: Cannot fork The syscall error seems to be https://bugs.launchpad.net/ubuntu/+source/qemu-linaro/+bug/758424 "We only implement the futex syscalls if CONFIG_USE_NPTL. This isn't defined for the i386 target (the necessary support in target-i386 for pushing atomic insns up to the linux-user top level loop isn't implemented). The upshot is that running multithreaded programs in linux-user i386-target isn't supported and this is just one of the symptoms." Dunno about the fork error. So it looks like anyone hoping to run x86 wine in qemu would need to fix qemu first and/or go back to an old wine that doesn't use nptl?

1 0

Google Summer of Code Project: Implement missing D3DX libraries
by Alexander Mezin 05 Apr '12

05 Apr '12

Hello. I want to participate in GSoC and work on project "Direct3D: Implement missing D3DX libraries", listed at http://wiki.winehq.org/SummerOfCode. I have experience of developing for Windows using Direct3D 9 and D3DX, so I think I'm the one who you need for this project. About two years ago I reimplemented some D3DX functionality using Direct3D for a casual game, because these D3DX_XX libraries caused problems with distribution. Sadly, all this code is lost, but there was nothing hard to implement, or, at least no such things was used in the game. Usually only D3DXSprite, D3DXFont and, maybe, effect framework are used. And also nothing really changes between D3DX versions, usually only some methods are renamed or their parameters are reordered. I want to contact possible mentor to discuss what parts of the libraries must be implemented, but I can't find his e-mail, wiki says that his page isn't created.

2 1

My GSoC proposition: Raw Input
by Eryk Wieliczko 05 Apr '12

05 Apr '12

I've been thinking about joining GSoC as a student this year. As an idea I propose Raw Input, and I seek your advise. Is this topic good, what are possible catches, etc. I think that it might be possible to finally do a decent implementation, that would (besides mouse and keyboard) also support joysticks and possibly some other input devices - tablets and multiple mice and keyboards. What do you think about this topic? Links: http://msdn.microsoft.com/en-us/library/windows/desktop/ms645536(v=vs.85).a… http://appdb.winehq.org/viewbugs.php?bug_id=20395 http://bugs.winehq.org/show_bug.cgi?id=20395

3 3

Re: [PATCH 1/1] ntdll: Fix section header heap deadlock (try 2).
by Alexandre Julliard 05 Apr '12

05 Apr '12

"Erich E. Hoover" <ehoover(a)mines.edu> writes: > Description: > Free the section header memory outside of the uninterrupted > section lock. Changing the order here stops the process heap from > potentially deadlocking (Bug #30356). The allocation will still be an issue. I think a better approach would be to avoid any memory allocation in there. -- Alexandre Julliard julliard(a)winehq.org

2 2

Re: [PATCH 2/5] wined3d: Enable "AlwaysOffscreen" by default.
by Alexandre Julliard 05 Apr '12

05 Apr '12

Henri Verbeet <hverbeet(a)codeweavers.com> writes: > --- > dlls/wined3d/wined3d_main.c | 8 ++++---- > 1 files changed, 4 insertions(+), 4 deletions(-) It doesn't work here (GeForce 8500, driver 295.20): ../../../tools/runtest -q -P wine -M d3d8.dll -T ../../.. -p d3d8_test.exe.so visual.c && touch visual.ok visual.c:1385: Tests skipped: D3DFMT_P8 textures not supported visual.c:2011: Test failed: Expected color 0x000000ff at 80,60, got 0x00ff0000. visual.c:2011: Test failed: Expected color 0x000000ff at 240,60, got 0x00ff0000. visual.c:2011: Test failed: Expected color 0x0000ff00 at 400,60, got 0x00ff0000. visual.c:2011: Test failed: Expected color 0x000000ff at 80,180, got 0x00ff0000. visual.c:2011: Test failed: Expected color 0x000000ff at 240,180, got 0x00ff0000. visual.c:2011: Test failed: Expected color 0x0000ff00 at 400,180, got 0x00ff0000. visual.c:2011: Test failed: Expected color 0x0000ff00 at 80,300, got 0x00ff0000. visual.c:2011: Test failed: Expected color 0x0000ff00 at 240,300, got 0x00ff0000. visual.c:2011: Test failed: Expected color 0x0000ff00 at 400,300, got 0x00ff0000. visual.c:2111: Test failed: Expected color 0x0000ff00 80,60, got 0x00ff0000. visual.c:2111: Test failed: Expected color 0x0000ff00 240,60, got 0x00ff0000. visual.c:2111: Test failed: Expected color 0x0000ff00 400,60, got 0x00ff0000. visual.c:2111: Test failed: Expected color 0x0000ff00 560,60, got 0x00ff0000. visual.c:2111: Test failed: Expected color 0x0000ff00 80,180, got 0x00ff0000. visual.c:2111: Test failed: Expected color 0x0000ff00 240,180, got 0x00ff0000. visual.c:2111: Test failed: Expected color 0x0000ff00 400,180, got 0x00ff0000. visual.c:2111: Test failed: Expected color 0x0000ff00 560,180, got 0x00ff0000. visual.c:2111: Test failed: Expected color 0x0000ff00 80,300, got 0x00ff0000. visual.c:2111: Test failed: Expected color 0x0000ff00 240,300, got 0x00ff0000. visual.c:2111: Test failed: Expected color 0x0000ff00 400,300, got 0x00ff0000. visual.c:2111: Test failed: Expected color 0x0000ff00 560,300, got 0x00ff0000. visual.c:2111: Test failed: Expected color 0x0000ff00 80,420, got 0x00ff0000. visual.c:2111: Test failed: Expected color 0x0000ff00 240,420, got 0x00ff0000. visual.c:2111: Test failed: Expected color 0x0000ff00 400,420, got 0x00ff0000. visual.c:2111: Test failed: Expected color 0x0000ff00 560,420, got 0x00ff0000. visual.c:2824: Tests skipped: No RESZ support, skipping RESZ test. make: *** [visual.ok] Error 25 -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: (try 2)quartz: add control.idl as a typelib resource
by Huw Davies 05 Apr '12

05 Apr '12

On Thu, Apr 05, 2012 at 07:51:13AM -0500, Aric Stewart wrote: > > revised based on comments from Jacek Caban > --- > dlls/quartz/Makefile.in | 1 + > dlls/quartz/control_v2.idl | 17 +++++++++++++++++ > 2 files changed, 18 insertions(+), 0 deletions(-) > create mode 100644 dlls/quartz/control_v2.idl Calling this control_v2.idl seems a little odd. control_tlb.idl may be better. Huw.

1 0

Re: gdi32: Constification.
by Alexandre Julliard 05 Apr '12

05 Apr '12

Kusanagi Kouichi <slash(a)ac.auone-net.jp> writes: > @@ -6407,7 +6409,7 @@ static BOOL get_text_metrics(GdiFont *font, LPTEXTMETRICW ptm) > return TRUE; > } > > -static BOOL face_has_symbol_charmap(FT_Face ft_face) > +static BOOL face_has_symbol_charmap(const FT_Face ft_face) > { > int i; > > @@ -6729,7 +6731,7 @@ end: > static DWORD freetype_GetGlyphOutline( PHYSDEV dev, UINT glyph, UINT format, > LPGLYPHMETRICS lpgm, DWORD buflen, LPVOID buf, const MAT2 *lpmat ) > { > - struct freetype_physdev *physdev = get_freetype_dev( dev ); > + const struct freetype_physdev * const physdev = get_freetype_dev( dev ); > DWORD ret; > > if (!physdev->font) You are overdoing it. There's no reason to change per-value parameters or local variables like the physdev. -- Alexandre Julliard julliard(a)winehq.org

3 2

Re: [PATCH 3/3] wininet/tests: Added checks for bad return values and stop tests when it happens.
by Alexandre Julliard 05 Apr '12

05 Apr '12

Morten Rønne <morten.roenne(a)tdcadsl.dk> writes: > @@ -29,6 +29,8 @@ > > #include "wine/test.h" > > +#define bail_out { ok(0, "Bailing out\n"); return; } Please avoid that sort of thing. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: quartz: add control.idl as a typelib resource
by Jacek Caban 05 Apr '12

05 Apr '12

Hi Aric, On 04/04/12 20:38, Aric Stewart wrote: > --- a/dlls/quartz/Makefile.in > +++ b/dlls/quartz/Makefile.in > @@ -32,6 +32,7 @@ RC_SRCS = version.rc > IDL_H_SRCS = fil_data.idl > IDL_P_SRCS = quartz_strmif.idl > IDL_R_SRCS = quartz_strmif.idl > +IDL_TLB_SRCS = ../../include/control.idl This is not the right way. A simple IDL file in DLL directory that does nothing but #include will do the trick. See dlls/stdole2 for example. Jacek

1 0

About the "Implement Common Windows Scripting Classes"
by Lucas Zawacki 05 Apr '12

05 Apr '12

Hello, regarding the "Implement Common Windows Scripting Classes" gsoc idea. How many of these classes would be fine for the length of the program? I'm thinking that maybe 3 classes with thorough would be cool for a proposal. Some of them like "Dictionary" seem to be pretty straight forward and small, the others I'm not sure. Looking at dlls/scrrun/scrrun.idl I see there are a lot more of classes, but according to the idea page, Dictionary and FileSystemObject block multiple applications so they're higher priority. Are there other ones that are important?

1 0

Re: [PATCH 1/2] Revert "gdi32: Load fonts from default Mac external font paths."
by Ken Thomases 04 Apr '12

04 Apr '12

Forgot to note that this is a resend. On Apr 4, 2012, at 5:40 PM, Ken Thomases wrote: > > This reverts commit 85a71387dac1ca3ad47970800c8c01743681b528. > --- > dlls/gdi32/freetype.c | 17 +---------------- > 1 files changed, 1 insertions(+), 16 deletions(-) > > <0001-Revert-gdi32-Load-fonts-from-default-Mac-external-fo.patch>

1 0

Re: [PATCH] d3drm: Retreive mesh name at loading time. Implement GetName and SetName.
by Henri Verbeet 04 Apr '12

04 Apr '12

You should use debugstr_a() for printing strings like that. Also, where does the 128 char limit come from?

2 1

Re: [PATCH 2/4] amstream: Add IAudioMediaStream stub implementation.
by Henri Verbeet 04 Apr '12

04 Apr '12

On 4 April 2012 21:57, Christian Costa <titan.costa(a)gmail.com> wrote: > +static HRESULT WINAPI IAudioMediaStreamImpl_QueryInterface(IAudioMediaStream *iface, > + REFIID riid, void **ppv) > +{ > + IAudioMediaStreamImpl *This = impl_from_IAudioMediaStream(iface); > + > + TRACE("(%p/%p)->(%s,%p)\n", iface, This, debugstr_guid(riid), ppv); > + > + if (IsEqualGUID(riid, &IID_IUnknown) || > + IsEqualGUID(riid, &IID_IMediaStream) || > + IsEqualGUID(riid, &IID_IAudioMediaStream)) > + { > + IUnknown_AddRef(iface); > + *ppv = This; That's wrong. > + return S_OK; > + } > + > + ERR("(%p)->(%s,%p),not found\n", This, debugstr_guid(riid), ppv); > + return E_NOINTERFACE; > +} QueryInterface() should generally set "*ppv" to NULL on failure.

1 0

Re: [PATCH 4/4] d3drm: Implement IDirect3DRMFrameX_GetChildren method and IDirect3DRMFrameArray interface. (resend)
by Marvin 04 Apr '12

04 Apr '12

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=17650 Your paranoid android. === WNT4WSSP6 (32 bit d3drm) === d3drm.c:472: Test failed: Invalid refcount. Expected 3 got 2 d3drm.c:480: Test failed: Invalid refcount. Expected 4 got 3 d3drm.c:482: Test failed: Invalid refcount. Expected 3 got 2

2 2

Re: amstream: IAMMultiMediaStreamImpl_SetState: correct ifs
by Christian Costa 04 Apr '12

04 Apr '12

Le 04/04/2012 21:22, Joris Huizer a écrit : > Correcting a mistake in 27c4ad3bec1229020ab38ab5b45f0969204192ef > > Oupsssssss...... :(

1 0

Re: user32/tests: Add DlgDirList tests
by Alexandre Julliard 04 Apr '12

04 Apr '12

Bruno Jesus <00cpxxx(a)gmail.com> writes: > Based on original patch from Christian Lupien from bug 8226. > > Tests required to later fix http://bugs.winehq.org/show_bug.cgi?id=8226 This should be added to the existing DlgDirList tests, making sure that these things are not already being tested. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [2/2] advapi32: Do not terminate a regular program if it calls StartServiceCtrlDispatcher.
by Alexandre Julliard 04 Apr '12

04 Apr '12

Alexander Morozov <amorozov(a)etersoft.ru> writes: > This patch partially fixes #30290. > > Pipe is renamed to spipe (service pipe) to prevent compilation error: > service.c:88:15: error: ‘pipe’ redeclared as different kind of symbol > /usr/include/unistd.h:414:12: note: previous declaration of ‘pipe’ was > here You shouldn't need to add global variables, just pass the handle to the thread. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: msi: fixed MsiGetFileHashW for empty files (try 2)
by Alexandre Julliard 04 Apr '12

04 Apr '12

Robert van Herk <mijnspamboxje(a)hotmail.com> writes: > @@ -493,6 +493,45 @@ static void test_MsiGetFileHash(void) > } > } > > +static void test_MsiGetFileHashForEmptyFile(void) { > + char path[MAX_PATH]; > + MSIFILEHASHINFO hi; > + char file[MAX_PATH]; > + UINT res; > + > + /* Create empty temp file */ > + GetTempPath( > + MAX_PATH, > + path > + ); You should add that to the existing MsiGetFileHash tests, there's no need for a separate function. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH 2/2] ntdll: Fix section header heap deadlock.
by Alexandre Julliard 04 Apr '12

04 Apr '12

"Erich E. Hoover" <ehoover(a)mines.edu> writes: > Real Name: > Erich Hoover > > Description: > Using the process heap for the section headers can cause a > deadlock (Bug #30356), this patch uses the virtual heap instead. I don't think we want to use the virtual heap for that sort of thing, it should be used only for memory views. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH 2/3] wininet: Don't delete locked entry in DeleteUrlCacheEntry
by Alexandre Julliard 04 Apr '12

04 Apr '12

Piotr Caban <piotr(a)codeweavers.com> writes: > --- > dlls/wininet/urlcache.c | 9 +++++++++ > 1 files changed, 9 insertions(+), 0 deletions(-) It doesn't work here: ../../../tools/runtest -q -P wine -M wininet.dll -T ../../.. -p wininet_test.exe.so urlcache.c && touch urlcache.ok urlcache.c:557: Test succeeded inside todo block: Expected failure urlcache.c:559: Test succeeded inside todo block: Expected ERROR_SHARING_VIOLATION, got 32 urlcache.c:568: Test succeeded inside todo block: UnlockUrlCacheEntryFileA failed: 0 urlcache.c:581: Test failed: Expected failure urlcache.c:582: Test failed: expected ERROR_FILE_NOT_FOUND, got 0 make: *** [urlcache.ok] Error 5 -- Alexandre Julliard julliard(a)winehq.org

1 0

Tools under the <>tools/winapi directory
by Roger Cruz 03 Apr '12

03 Apr '12

How are the tools under the winapi directory used? I've tried running them but they all complain about the same error. ~/sandbox/wine/sources/wine-1.3.36/dlls/kernel32$ ~/sandbox/wine/sources/wine-1.3.36/tools/winapi/winapi_extract winapi_extract: You must run this tool in the main Wine directory or a sub directory

2 1

OT: Looking for (paid) help with Wine development.
by Roger Cruz 03 Apr '12

03 Apr '12

Hello fellow Wine developers, I am looking for paid programming help to help me finish a proof of concept application that utilizes Wine. This is a short-term contract project with terms negotiated based on your experience and ability to finish tasks in a timely manner. The right person should have the following skills 1) Has worked extensively with Wine in the past. Being a contributor to Wine is a plus but not a requirement. However, you must know the internals of Wine and be able to cross-compile for other platforms. Knowledge of shared libraries and linking is a huge plus. 2) Have extensive programming experience in Windows and know its compilers and intricacies. 3) Must have a great understanding of calling conventions in Windows and Linux environments. In particular, you need to know where compilers place arguments to a function and how to extract them from the stack and registers. 4) Must know how to use debuggers effectively, as well as the internals of how a compiler keeps its debug information. DWARF knowledge is a huge plus. 5) Must be an expert in C and have good knowledge in C++. Other languages are desireable. 6) Having internal knowledge of QEMU, specially in the TCG area, is a huge plus as well. 7) SDL, OpenGL and graphics knowledge is a plus. You must not be precluded by any current employment from working on this side project. There should not be any conflict of interest that would taint your work. You will be required to sign a non-disclosure and non-compete agreement before proceeding. If this is something that interests you, please email me privately at roger_r_cruz AT yahoo dot com Warm Regards Roger R. Cruz

1 0

Re: gdiplus: GdipDrawString is not supposed to use the layout rectangle for clipping. Take 2.
by Vincent Povirk 03 Apr '12

03 Apr '12

I tried making a testcase for this, and I'm consistently seeing that native only draws text that lies inside the rectangle if a positive width or height are given. If I specify StringFormatFlagsNoClip then I see a slight difference. Without the flag, the last line of text is clipped at the given height; with the flag, it is fully shown as long as the top of that line lies inside the rectangle. The test cases you linked appear to leave the width and height uninitialized, and they do not specify StringFormatFlagsNoClip. My guess is that they either default to 0 or undefined depending on how the language works. Since we already handle the case where width and height are 0, and an undefined width/height could work or not by coincidence, I don't think your test cases show anything new. Due to the way we (like native) calculate the text layout independent of clipping, so that characters that lie entirely outside the rectangle are not drawn, it's not even clear to me why this patch might have helped. I think this needs more investigation.

2 1

Re: [website] Add Portuguese translation for release 1.5.1
by Bruno Jesus 03 Apr '12

03 Apr '12

2012/4/2 Lucas Fialho Zawacki <lfzawacki(a)gmail.com>: >> + <li>Suporte a fontes redimensionáveis em recursos.</li> A more correct translation for: - Support for scalable font resources. Would be: - Suporte para recursos de fontes escaláveis. Instead of: - Suporte a fontes redimensionáveis em recursos. Maybe "redimensionáveis" instead of "escaláveis" as you first used. Best wishes, Bruno

2 1

Re: [PATCH 3/4] winspool/tests: Add some tests for OpenPrinter with non-NULL defaults.
by Marvin 03 Apr '12

03 Apr '12

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=17661 Your paranoid android. === WINEBUILD (build) === Can't determine base name

2 1

Re: [1/2] kernel32/tests: Add tests for LCMapStringEx
by Alexandre Julliard 03 Apr '12

03 Apr '12

André Hentschel <nerv(a)dawncrow.de> writes: > /* test srclen = 0 */ > SetLastError(0xdeadbeef); > - ret = LCMapStringW(LOCALE_USER_DEFAULT, 0, upper_case, 0, buf, sizeof(buf)/sizeof(WCHAR)); > - ok(!ret, "LCMapStringW should fail with srclen = 0\n"); > + ret = LCMapStringU(0, upper_case, 0, buf, sizeof(buf)/sizeof(WCHAR)); > + ok(!ret, "LCMapStringU should fail with srclen = 0\n"); This is very confusing, there's no such API as LCMapStringU. You should display the correct function being tested in all the error messages, and pick a better name for the function pointer. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [PATCH 1/3] amstream: Add CLSID_AMAudioData implementation. (try 2)
by Michael Stefaniuc 03 Apr '12

03 Apr '12

Hello Christian, On 04/03/2012 07:53 AM, Christian Costa wrote: > +/*** IUnknown methods ***/ > +static HRESULT WINAPI IAudioDataImpl_QueryInterface(IAudioData *iface, REFIID riid, void **ppv) > +{ > + AMAudioDataImpl *This = impl_from_IAudioData(iface); > + > + TRACE("(%p/%p)->(%s,%p)\n", iface, This, debugstr_guid(riid), ppv); > + > + if (IsEqualGUID(riid, &IID_IUnknown) || > + IsEqualGUID(riid, &IID_IMemoryData) || > + IsEqualGUID(riid, &IID_IAudioData)) > + { > + IUnknown_AddRef(iface); > + *ppv = This; even though MS loves to call ppv ppvObject it isn't an object but a pointer to an interface. As this object has just one interface you can get rid of This and just assign iface to *ppv. > + return S_OK; > + } > + > + ERR("(%p)->(%s,%p),not found\n", This, debugstr_guid(riid), ppv); > + return E_NOINTERFACE; > +} > + bye michael

2 1

Re: [PATCH 2/3] dmsynth: Check the rigth CLSID to create the DirectMusicSynthSink object. (resend)
by Marvin 03 Apr '12

03 Apr '12

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

1 0

Programmatically determining arguments to a WinAPI function
by Roger Cruz 03 Apr '12

03 Apr '12

I'm looking for a way to determine programmatically what the arguments to a Win32 API implemented in Wine are. I'm trying to implement an API redirection stub that I can use to trace calls into all of the Wine-implemented DLLs. My stub needs to know what each argument passed into the Win32 API, their types and sizes, and whether they reside on the stack or register when calling the routine and finally their return value. In researching Wine, I have come to find out two tools, winedump and winebuild that may be helpful in doing this but I have yet to find out how to use them correctly to get the information I seek. Maybe they just don't have that capability or maybe I just haven't played with them enough to find all of its uses. For example, I found that each DLL has a *.spec file which looks to have some of the info I need: @ stdcall GetSystemTimeAsFileTime(ptr) Looking at the man pages, this tells me that GetSystemTimeAsFileTime takes in an argument as a pointer but I don't see any return value information here. Also, does this file ever represent arguments passed by value on the stack, like a structure? If so, does it capture how big the structure is? What about function prototypes with variable arguments (similar to printf(...)).. are those capture in the file? Can I also assume (based on the calling convention listed as stdcall) which arguments will be on registers and which will be on the stack? I know that the DWARF debug info can give me some of what I need but I would have to write a big parser for which I lack the time now. Are there other tools that may make this easier if winedump and winebuild can't help me? I know this is a lot to ask here but I'm just getting started with Wine and need to come up to speed very fast. Thanks in advance for any help you can provide me. Roger R. Cruz

2 2

GSoC: Encryption - implement a DSS provider
by Alexander Sulfrian 02 Apr '12

02 Apr '12

Hi, I am Alexander Sulfrian and I am currently studding computer science at the "Freie Universität Berlin". I recently got my bachelor degree and currently attending the second semester to get my master. Last year, I took part in the GSoC for vlc and successfully implemented a library to communicate with a sony minidisk player under linux. So I am familiar with the general GSoC procedure. This year, I like to attend the GSoC program of wine. Looking through the ideas wiki page, the dss provider task looks very interesting. I know C at an advanced level and think, that I am able to work on this task. Additionally to that, I also done something in C# with .NET. Sadly I am not very familiar with the wine source code and I do not know where to implement this DSS providers. Could you guide me to the correct location? What do you think are the next steps, if I want to attend the GSoC program? Thanks, Alex

1 0

Re: [PATCH 3/5] ddraw/tests: Add some QueryInterface() tests for surfaces.
by Marvin 02 Apr '12

02 Apr '12

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=17644 Your paranoid android. === W7PROX64 (64 bit ddraw4) === ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 0. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 1. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 0. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 1. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 9. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 10. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 11. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 12. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 13. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 14. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 15. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 16. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 17. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 18. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 19. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 20. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 21. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 22. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 23. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 24. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 25. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 26. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 27. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 28. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 29. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 30. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 31. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 32. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 33. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 0. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 1. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 9. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 10. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 11. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 12. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 13. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 14. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 15. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 16. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 17. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 18. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 19. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 20. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 21. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 22. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 23. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 24. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 25. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 26. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 27. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 28. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 29. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 30. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 31. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 32. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 33. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 0. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 1. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 9. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 10. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 11. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 12. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 13. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 14. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 15. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 16. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 17. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 18. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 19. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 20. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 21. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 22. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 23. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 24. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 25. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 26. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 27. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 28. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 29. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 30. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 31. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 32. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 33. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 0. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 1. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 9. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 10. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 11. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 12. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 13. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 14. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 15. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 16. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 17. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 18. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 19. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 20. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 21. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 22. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 23. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 24. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 25. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 26. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 27. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 28. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 29. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 30. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 31. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 32. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 33. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 0. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 1. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 9. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 10. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 11. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 12. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 13. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 14. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 15. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 16. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 17. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 18. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 19. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 20. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 21. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 22. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 23. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 24. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 25. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 26. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 27. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 28. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 29. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 30. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 31. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 32. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 33. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 0. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 1. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 9. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 10. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 11. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 12. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 13. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 14. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 15. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 16. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 17. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 18. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 19. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 20. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 21. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 22. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 23. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 24. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 25. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 26. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 27. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 28. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 29. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 30. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 31. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 32. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 33. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 9. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 10. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 11. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 12. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 13. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 14. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 15. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 16. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 17. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 18. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 19. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 20. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 21. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 22. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 23. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 24. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 25. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 26. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 27. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 28. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 29. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 30. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 31. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 32. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 33. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 0. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 1. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 9. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 10. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 11. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 12. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 13. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 14. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 15. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 16. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 17. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 18. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 19. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 20. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 21. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 22. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 23. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 24. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 25. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 26. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 27. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 28. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 29. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 30. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 31. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 32. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 33. === TEST64_W7SP1 (64 bit ddraw4) === ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 0. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 1. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 0. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 1. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 9. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 10. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 11. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 12. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 13. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 14. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 15. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 16. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 17. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 18. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 19. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 20. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 21. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 22. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 23. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 24. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 25. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 26. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 27. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 28. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 29. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 30. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 31. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 32. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 33. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 0. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 1. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 9. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 10. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 11. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 12. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 13. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 14. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 15. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 16. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 17. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 18. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 19. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 20. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 21. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 22. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 23. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 24. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 25. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 26. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 27. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 28. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 29. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 30. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 31. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 32. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 33. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 0. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 1. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 9. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 10. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 11. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 12. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 13. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 14. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 15. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 16. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 17. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 18. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 19. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 20. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 21. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 22. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 23. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 24. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 25. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 26. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 27. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 28. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 29. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 30. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 31. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 32. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 33. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 0. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 1. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 9. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 10. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 11. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 12. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 13. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 14. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 15. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 16. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 17. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 18. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 19. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 20. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 21. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 22. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 23. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 24. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 25. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 26. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 27. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 28. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 29. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 30. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 31. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 32. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 33. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 0. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 1. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 9. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 10. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 11. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 12. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 13. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 14. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 15. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 16. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 17. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 18. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 19. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 20. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 21. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 22. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 23. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 24. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 25. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 26. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 27. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 28. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 29. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 30. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 31. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 32. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 33. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 0. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 1. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 9. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 10. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 11. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 12. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 13. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 14. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 15. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 16. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 17. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 18. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 19. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 20. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 21. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 22. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 23. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 24. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 25. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 26. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 27. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 28. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 29. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 30. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 31. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 32. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 33. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 9. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 10. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 11. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 12. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 13. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 14. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 15. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 16. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 17. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 18. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 19. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 20. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 21. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 22. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 23. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 24. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 25. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 26. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 27. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 28. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 29. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 30. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 31. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 32. ddraw4.c:1637: Test failed: Got hr 0x80004002 for test "surface_qi" 33. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 0. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 1. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 9. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 10. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 11. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 12. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 13. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 14. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 15. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 16. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 17. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 18. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 19. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 20. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 21. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 22. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 23. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 24. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 25. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 26. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 27. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 28. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 29. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 30. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 31. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 32. ddraw4.c:1643: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 33. === W7PROX64 (64 bit ddraw2) === ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 0. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 1. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 0. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 1. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 9. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 10. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 11. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 12. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 13. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 14. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 15. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 16. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 17. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 18. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 19. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 20. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 21. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 22. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 23. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 24. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 25. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 26. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 27. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 28. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 29. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 30. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 31. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 32. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 33. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 0. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 1. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 9. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 10. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 11. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 12. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 13. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 14. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 15. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 16. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 17. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 18. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 19. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 20. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 21. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 22. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 23. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 24. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 25. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 26. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 27. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 28. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 29. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 30. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 31. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 32. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 33. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 0. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 1. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 9. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 10. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 11. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 12. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 13. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 14. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 15. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 16. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 17. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 18. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 19. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 20. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 21. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 22. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 23. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 24. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 25. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 26. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 27. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 28. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 29. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 30. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 31. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 32. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 33. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 0. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 1. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 9. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 10. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 11. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 12. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 13. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 14. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 15. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 16. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 17. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 18. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 19. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 20. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 21. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 22. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 23. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 24. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 25. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 26. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 27. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 28. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 29. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 30. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 31. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 32. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 33. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 0. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 1. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 9. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 10. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 11. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 12. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 13. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 14. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 15. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 16. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 17. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 18. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 19. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 20. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 21. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 22. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 23. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 24. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 25. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 26. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 27. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 28. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 29. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 30. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 31. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 32. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 33. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 0. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 1. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 9. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 10. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 11. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 12. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 13. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 14. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 15. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 16. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 17. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 18. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 19. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 20. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 21. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 22. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 23. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 24. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 25. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 26. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 27. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 28. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 29. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 30. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 31. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 32. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 33. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 9. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 10. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 11. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 12. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 13. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 14. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 15. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 16. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 17. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 18. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 19. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 20. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 21. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 22. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 23. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 24. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 25. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 26. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 27. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 28. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 29. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 30. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 31. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 32. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 33. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 0. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 1. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 9. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 10. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 11. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 12. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 13. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 14. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 15. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 16. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 17. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 18. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 19. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 20. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 21. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 22. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 23. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 24. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 25. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 26. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 27. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 28. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 29. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 30. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 31. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 32. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 33. === TEST64_W7SP1 (64 bit ddraw2) === ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 0. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 1. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 0. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 1. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 9. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 10. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 11. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 12. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 13. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 14. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 15. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 16. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 17. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 18. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 19. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 20. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 21. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 22. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 23. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 24. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 25. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 26. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 27. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 28. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 29. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 30. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 31. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 32. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 33. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 0. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 1. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 9. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 10. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 11. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 12. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 13. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 14. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 15. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 16. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 17. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 18. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 19. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 20. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 21. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 22. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 23. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 24. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 25. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 26. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 27. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 28. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 29. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 30. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 31. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 32. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 33. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 0. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 1. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 9. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 10. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 11. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 12. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 13. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 14. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 15. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 16. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 17. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 18. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 19. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 20. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 21. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 22. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 23. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 24. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 25. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 26. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 27. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 28. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 29. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 30. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 31. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 32. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 33. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 0. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 1. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 9. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 10. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 11. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 12. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 13. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 14. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 15. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 16. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 17. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 18. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 19. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 20. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 21. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 22. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 23. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 24. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 25. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 26. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 27. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 28. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 29. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 30. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 31. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 32. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 33. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 0. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 1. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 9. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 10. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 11. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 12. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 13. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 14. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 15. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 16. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 17. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 18. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 19. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 20. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 21. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 22. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 23. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 24. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 25. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 26. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 27. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 28. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 29. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 30. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 31. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 32. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 33. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 0. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 1. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 9. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 10. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 11. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 12. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 13. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 14. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 15. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 16. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 17. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 18. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 19. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 20. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 21. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 22. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 23. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 24. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 25. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 26. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 27. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 28. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 29. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 30. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 31. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 32. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 33. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 9. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 10. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 11. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 12. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 13. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 14. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 15. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 16. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 17. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 18. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 19. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 20. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 21. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 22. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 23. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 24. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 25. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 26. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 27. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 28. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 29. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 30. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 31. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 32. ddraw2.c:1554: Test failed: Got hr 0x80004002 for test "surface_qi" 33. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 0. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 1. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 9. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 10. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 11. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 12. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 13. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 14. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 15. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 16. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 17. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 18. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 19. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 20. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 21. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 22. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 23. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 24. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 25. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 26. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 27. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 28. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 29. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 30. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 31. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 32. ddraw2.c:1560: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 33. === W7PROX64 (64 bit ddraw1) === ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 0. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 1. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 0. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 1. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 9. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 10. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 11. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 12. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 13. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 14. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 15. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 16. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 17. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 18. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 19. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 20. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 21. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 22. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 23. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 24. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 25. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 26. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 27. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 28. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 29. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 30. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 31. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 32. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 33. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 0. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 1. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 9. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 10. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 11. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 12. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 13. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 14. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 15. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 16. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 17. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 18. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 19. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 20. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 21. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 22. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 23. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 24. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 25. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 26. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 27. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 28. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 29. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 30. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 31. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 32. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 33. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 0. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 1. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 9. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 10. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 11. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 12. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 13. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 14. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 15. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 16. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 17. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 18. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 19. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 20. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 21. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 22. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 23. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 24. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 25. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 26. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 27. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 28. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 29. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 30. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 31. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 32. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 33. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 0. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 1. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 9. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 10. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 11. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 12. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 13. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 14. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 15. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 16. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 17. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 18. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 19. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 20. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 21. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 22. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 23. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 24. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 25. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 26. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 27. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 28. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 29. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 30. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 31. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 32. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 33. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 0. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 1. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 9. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 10. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 11. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 12. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 13. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 14. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 15. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 16. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 17. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 18. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 19. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 20. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 21. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 22. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 23. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 24. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 25. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 26. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 27. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 28. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 29. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 30. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 31. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 32. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 33. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 0. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 1. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 9. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 10. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 11. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 12. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 13. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 14. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 15. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 16. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 17. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 18. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 19. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 20. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 21. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 22. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 23. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 24. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 25. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 26. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 27. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 28. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 29. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 30. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 31. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 32. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 33. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 9. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 10. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 11. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 12. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 13. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 14. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 15. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 16. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 17. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 18. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 19. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 20. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 21. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 22. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 23. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 24. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 25. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 26. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 27. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 28. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 29. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 30. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 31. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 32. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 33. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 0. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 1. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 9. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 10. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 11. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 12. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 13. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 14. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 15. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 16. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 17. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 18. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 19. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 20. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 21. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 22. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 23. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 24. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 25. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 26. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 27. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 28. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 29. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 30. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 31. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 32. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 33. === TEST64_W7SP1 (64 bit ddraw1) === ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 0. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 1. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 0. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 1. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 9. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 10. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 11. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 12. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 13. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 14. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 15. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 16. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 17. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 18. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 19. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 20. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 21. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 22. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 23. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 24. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 25. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 26. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 27. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 28. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 29. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 30. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 31. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 32. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 2, 33. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 0. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 1. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 9. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 10. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 11. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 12. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 13. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 14. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 15. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 16. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 17. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 18. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 19. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 20. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 21. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 22. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 23. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 24. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 25. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 26. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 27. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 28. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 29. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 30. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 31. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 32. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 4, 33. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 0. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 1. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 9. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 10. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 11. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 12. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 13. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 14. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 15. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 16. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 17. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 18. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 19. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 20. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 21. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 22. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 23. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 24. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 25. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 26. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 27. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 28. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 29. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 30. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 31. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 32. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 5, 33. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 0. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 1. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 9. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 10. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 11. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 12. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 13. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 14. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 15. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 16. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 17. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 18. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 19. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 20. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 21. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 22. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 23. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 24. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 25. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 26. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 27. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 28. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 29. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 30. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 31. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 32. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 6, 33. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 0. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 1. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 9. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 10. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 11. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 12. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 13. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 14. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 15. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 16. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 17. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 18. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 19. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 20. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 21. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 22. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 23. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 24. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 25. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 26. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 27. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 28. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 29. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 30. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 31. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 32. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 7, 33. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 0. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 1. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 9. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 10. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 11. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 12. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 13. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 14. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 15. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 16. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 17. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 18. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 19. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 20. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 21. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 22. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 23. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 24. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 25. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 26. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 27. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 28. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 29. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 30. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 31. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 32. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 8, 33. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 9. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 10. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 11. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 12. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 13. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 14. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 15. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 16. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 17. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 18. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 19. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 20. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 21. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 22. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 23. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 24. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 25. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 26. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 27. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 28. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 29. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 30. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 31. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 32. ddraw1.c:1344: Test failed: Got hr 0x80004002 for test "surface_qi" 33. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 0. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 1. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 9. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 10. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 11. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 12. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 13. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 14. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 15. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 16. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 17. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 18. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 19. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 20. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 21. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 22. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 23. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 24. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 25. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 26. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 27. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 28. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 29. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 30. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 31. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 32. ddraw1.c:1350: Test failed: Got hr 0x80004002 for test "surface_qi" 34, 33. === W7PROX64 (64 bit ddraw7) === ddraw7.c:1557: Test failed: Failed to create surface, hr 0x80004002. === TEST64_W7SP1 (64 bit ddraw7) === ddraw7.c:1557: Test failed: Failed to create surface, hr 0x80004002.

1 0

Re: gdi32: Refuse to load a large .fot file earlier.
by Kristoffer Eklund 02 Apr '12

02 Apr '12

Stop e-mail me! 2 apr 2012 kl. 07.40 skrev Dmitry Timoshkov: > --- > dlls/gdi32/font.c | 10 +++++++--- > 1 file changed, 7 insertions(+), 3 deletions(-) > > diff --git a/dlls/gdi32/font.c b/dlls/gdi32/font.c > index 230d421..f5c44d8 100644 > --- a/dlls/gdi32/font.c > +++ b/dlls/gdi32/font.c > @@ -3454,10 +3454,15 @@ static void *map_file( const WCHAR *filename, LARGE_INTEGER *size ) > file = CreateFileW( filename, GENERIC_READ, 0, NULL, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL ); > if (file == INVALID_HANDLE_VALUE) return NULL; > > - GetFileSizeEx( file, size ); > + if (!GetFileSizeEx( file, size ) || size->u.HighPart) > + { > + CloseHandle( file ); > + return NULL; > + } > + > mapping = CreateFileMappingW( file, NULL, PAGE_READONLY, 0, 0, NULL ); > CloseHandle( file ); > - if (mapping == NULL) return NULL; > + if (!mapping) return NULL; > > ptr = MapViewOfFile( mapping, FILE_MAP_READ, 0, 0, 0 ); > CloseHandle( mapping ); > @@ -3478,7 +3483,6 @@ static WCHAR *get_scalable_filename( const WCHAR *res ) > > if (!ptr) return NULL; > > - if (size.u.HighPart) goto fail; > if (size.u.LowPart < sizeof( *dos )) goto fail; > dos = (const IMAGE_DOS_HEADER *)ptr; > if (dos->e_magic != IMAGE_DOS_SIGNATURE) goto fail; > -- > 1.7.9.4 > > >

2 1

Re: [PATCH 2/3] winspool/tests: Add some tests for OpenPrinter with non-NULL defaults.
by Alexandre Julliard 02 Apr '12

02 Apr '12

Huw Davies <huw(a)codeweavers.com> writes: > --- > dlls/winspool.drv/tests/info.c | 110 ++++++++++++++++++++++++++++++++++++++++ > 1 files changed, 110 insertions(+), 0 deletions(-) It doesn't work here: ../../../tools/runtest -q -P wine -M winspool.drv -T ../../.. -p winspool.drv_test.exe.so info.c && touch info.ok info.c:2302: Tests skipped: Level 1 not supported info.c:2302: Tests skipped: Level 3 not supported info.c:2302: Tests skipped: Level 8 not supported info.c:2969: Test failed: got 0 wine: Unhandled page fault on read access to 0x00000028 at address 0x687e23fa (thread 002a), starting debugger... Unhandled exception: page fault on read access to 0x00000028 in 32-bit code (0x687e23fa). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:687e23fa ESP:0032fb50 EBP:0032fc58 EFLAGS:00010246( R- -- I Z- -P- ) EAX:00000000 EBX:687ec60c ECX:687e7eac EDX:0011e180 ESI:687e7ae5 EDI:0011deb0 Stack dump: 0x0032fb50: 687e7ae5 00000b9b 00000000 0011e180 0x0032fb60: 0000012e 0032fc3c 00000012 6833fef5 0x0032fb70: 683d88e8 00000000 0011e180 0001fc40 0x0032fb80: 0011dcd0 687e7e99 687e7c3c 00000001 0x0032fb90: 00000000 00000000 00000000 00000000 0x0032fba0: 00000000 00000000 00000000 00000000 Backtrace: =>0 0x687e23fa test_OpenPrinter_defaults+0x83a() [/home/julliard/wine/wine/dlls/winspool.drv/tests/info.c:2971] in winspool.drv_test (0x0032fc58) 1 0x687e561e func_info+0x22fd() [/home/julliard/wine/wine/dlls/winspool.drv/tests/info.c:3031] in winspool.drv_test (0x0032fd18) 2 0x687e6e70 run_test+0x11f(name="info.c") [/home/julliard/wine/wine/dlls/winspool.drv/tests/../../../include/wine/test.h:556] in winspool.drv_test (0x0032fd68) 3 0x687dadf3 main+0x152(argc=0x20746f67, argv=0x78383025) [/home/julliard/wine/wine/dlls/winspool.drv/tests/../../../include/wine/test.h:624] in winspool.drv_test (0x0032fe28) 4 0x687e79d5 __wine_spec_exe_entry+0x74(peb=0x7ffdf000) [/home/julliard/wine/wine/dlls/winecrt0/exe_entry.c:36] in winspool.drv_test (0x0032fe70) 5 0x6848fdbc call_process_entry+0xb() in kernel32 (0x0032fe88) 6 0x68490f3f start_process+0x5e(peb=0x7ffdf000) [/home/julliard/wine/wine/dlls/kernel32/process.c:1083] in kernel32 (0x0032fec8) 7 0x6837d200 call_thread_func_wrapper+0xb() in ntdll (0x0032fed8) 8 0x6837ff0d call_thread_func+0x7c(entry=0x68490ee0, arg=0x7ffdf000, frame=0x32ffc8) [/home/julliard/wine/wine/dlls/ntdll/signal_i386.c:2532] in ntdll (0x0032ffa8) 9 0x6837d1de call_thread_entry_point+0x11() in ntdll (0x0032ffc8) 10 0x6835530e start_process+0x1d(kernel_start=0x68490ee0) [/home/julliard/wine/wine/dlls/ntdll/loader.c:2653] in ntdll (0x0032ffe8) 11 0x68028a9d wine_call_on_stack+0x1c() in libwine.so.1 (0x00000000) 12 0x68028b5b wine_switch_to_stack+0x2a(func=0x683552f0, arg=0x68490ee0, stack=0x330000) [/home/julliard/wine/wine/libs/wine/port.c:59] in libwine.so.1 (0xff917048) 13 0x6835ae86 LdrInitializeThunk+0x3b5(kernel_start=0x68490ee0, unknown2=0, unknown3=0, unknown4=0) [/home/julliard/wine/wine/dlls/ntdll/loader.c:2709] in ntdll (0xff9170b8) 14 0x68496e02 __wine_kernel_init+0x9e1() [/home/julliard/wine/wine/dlls/kernel32/process.c:1255] in kernel32 (0xff918258) 15 0x6835b5db __wine_process_init+0x25a() [/home/julliard/wine/wine/dlls/ntdll/loader.c:2918] in ntdll (0xff9182d8) 16 0x68025fe8 wine_init+0x277(argc=0x3, argv=0xff918834, error="", error_size=0x400) [/home/julliard/wine/wine/libs/wine/loader.c:831] in libwine.so.1 (0xff918338) 17 0x7bf00e5b main+0x7a(argc=0x3, argv=0xff918834) [/home/julliard/wine/wine/loader/main.c:230] in <wine-loader> (0xff918788) 18 0x681bce46 __libc_start_main+0xe5() in libc.so.6 (0xff918808) 0x687e23fa test_OpenPrinter_defaults+0x83a [/home/julliard/wine/wine/dlls/winspool.drv/tests/info.c:2971] in winspool.drv_test: movl 0x28(%eax),%eax 2971 ok( job_info->pDevMode->dmFields == DM_PAPERSIZE, "got %08x\n", -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [04/09]strmbase: implement renderer quality control into the base renderer
by Alexandre Julliard 02 Apr '12

02 Apr '12

Aric Stewart <aric(a)codeweavers.com> writes: > --- > dlls/quartz/dsoundrender.c | 28 ++++++++++------------------ > dlls/quartz/nullrenderer.c | 2 +- > dlls/strmbase/renderer.c | 41 > ++++++++++++++++++++++++++++++++++++++++- > include/wine/strmbase.h | 4 ++++ > 4 files changed, 55 insertions(+), 20 deletions(-) It doesn't work here: ../../../tools/runtest -q -P wine -M quartz.dll -T ../../.. -p quartz_test.exe.so dsoundrender.c && touch dsoundrender.ok dsoundrender.c:155: Test failed: IUnknown_Release should return 1, got 0 wine: Unhandled page fault on execute access to 0x00110118 at address 0x110118 (thread 002b), starting debugger... Unhandled exception: page fault on execute access to 0x00110118 in 32-bit code (0x00110118). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:00110118 ESP:0032fccc EBP:0032fd58 EFLAGS:00010202( R- -- I - - - ) EAX:0012e9c0 EBX:687ee314 ECX:687ea900 EDX:0012f630 ESI:687e8269 EDI:00000000 Stack dump: 0x0032fccc: 687dd8c1 0012e9c0 687ea900 0032fd38 0x0032fcdc: 00000000 687eea78 00000000 00125338 0x0032fcec: 683bd30c 687ec163 683bd30c 0032fd18 0x0032fcfc: 00000000 687ea900 687e8490 687e7e01 0x0032fd0c: 687e82c0 683702d9 684d85f0 0032fd58 0x0032fd1c: 0012e9c0 0012ebe0 00000000 0012a298 Backtrace: =>0 0x00110118 (0x0032fd58) 1 0x687db392 main+0x3a1(argc=0x56a86895, argv=0x11ce0ad4) [/home/julliard/wine/wine/dlls/quartz/tests/../../../include/wine/test.h:556] in quartz_test (0x0032fe28) 2 0x687e7c85 __wine_spec_exe_entry+0x74(peb=0x7ffdf000) [/home/julliard/wine/wine/dlls/winecrt0/exe_entry.c:36] in quartz_test (0x0032fe70) 3 0x6848fdbc call_process_entry+0xb() in kernel32 (0x0032fe88) 4 0x68490f3f start_process+0x5e(peb=0x7ffdf000) [/home/julliard/wine/wine/dlls/kernel32/process.c:1083] in kernel32 (0x0032fec8) 5 0x6837d200 call_thread_func_wrapper+0xb() in ntdll (0x0032fed8) 6 0x6837ff0d call_thread_func+0x7c(entry=0x68490ee0, arg=0x7ffdf000, frame=0x32ffc8) [/home/julliard/wine/wine/dlls/ntdll/signal_i386.c:2532] in ntdll (0x0032ffa8) 7 0x6837d1de call_thread_entry_point+0x11() in ntdll (0x0032ffc8) 8 0x6835530e start_process+0x1d(kernel_start=0x68490ee0) [/home/julliard/wine/wine/dlls/ntdll/loader.c:2653] in ntdll (0x0032ffe8) 9 0x68028a9d wine_call_on_stack+0x1c() in libwine.so.1 (0x00000000) 10 0x68028b5b wine_switch_to_stack+0x2a(func=0x683552f0, arg=0x68490ee0, stack=0x330000) [/home/julliard/wine/wine/libs/wine/port.c:59] in libwine.so.1 (0xff90f428) 11 0x6835ae86 LdrInitializeThunk+0x3b5(kernel_start=0x68490ee0, unknown2=0, unknown3=0, unknown4=0) [/home/julliard/wine/wine/dlls/ntdll/loader.c:2709] in ntdll (0xff90f498) 12 0x68496e02 __wine_kernel_init+0x9e1() [/home/julliard/wine/wine/dlls/kernel32/process.c:1255] in kernel32 (0xff910638) 13 0x6835b5db __wine_process_init+0x25a() [/home/julliard/wine/wine/dlls/ntdll/loader.c:2918] in ntdll (0xff9106b8) 14 0x68025fe8 wine_init+0x277(argc=0x3, argv=0xff910c14, error="", error_size=0x400) [/home/julliard/wine/wine/libs/wine/loader.c:831] in libwine.so.1 (0xff910718) 15 0x7bf00e5b main+0x7a(argc=0x3, argv=0xff910c14) [/home/julliard/wine/wine/loader/main.c:230] in <wine-loader> (0xff910b68) 16 0x681bce46 __libc_start_main+0xe5() in libc.so.6 (0xff910be8) 0x00110118: subb %al,0x0(%ecx) -- Alexandre Julliard julliard(a)winehq.org

1 0

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