February 2007 - Wine-devel - list.winehq.org

Update on msi JScript/VBScript support functions
by Misha Koshelev 24 Feb '07

24 Feb '07

Hi, just wanted to update everybody on my work with this, sorry I have not been good at replying to personal emails lately. I am not currently attaching any code but will clean things up and then submit my patches to wine-patches soon. So, the good news is that, as a proof of concept, I have gotten the Vector NTI installer to work successfully, which requires the JScript functionality. Specifically, this tests custom actions 5/6 and 37/38, there are two other sets that would be nice to test (but it is all the same script handler so it should work). Also, to make this work, I had to implement the OLE automation interface. Now, I have not implemented the entire interface yet, but I have made the entire .tlb file for this and made a framework which makes implementing everything fairly straightforward (and everything is a wrapper around the existing MSI database functions, so there is no actual functionality, it is just adding new cases to the switch statements that call the MSI database functions appropriately). Basically, because of the MSI design where everything that is an object has an MSIHANDLE, I have made one Automation Object that each specific object "inherits" from by implementing its invoke function (minus basic parameter checking, etc. which is all done by the automation object) and passing it to create_automation_object with its CLSID. It is pretty easy to implement more functions, and I will try to keep on adding more, probably as patches that I will periodically send to wine-patches. Anyhow, look for my first patches in the next couple of days. Misha

1 3

Re: [1/2] comctl32: add WM_PAINT message sequence tests
by James Hawkins 24 Feb '07

24 Feb '07

On 2/23/07, Felix Nawothnig <flexo(a)holycrap.org> wrote: > Passed on XP SP2. > --- > dlls/comctl32/tests/listview.c | 209 > +++++++++++++++++++++++++++++++++++++++- > dlls/comctl32/tests/msg.c | 3 + > dlls/comctl32/tests/msg.h | 3 +- > 3 files changed, 211 insertions(+), 4 deletions(-) > This is wrong: +static LRESULT WINAPI header_subclass_proc(HWND hwnd, UINT message, WPARAM wParam, LPARAM lParam) +{ + struct subclass_info *info = (struct subclass_info *)GetWindowLongA(hwnd, GWL_USERDATA); + static long defwndproc_counter = 0; + LRESULT ret; + struct message msg; + + trace("header: %p, %04x, %08x, %08lx\n", hwnd, message, wParam, lParam); + + msg.message = message; + msg.flags = sent|wparam|lparam|hdr; + if (defwndproc_counter) msg.flags |= defwinproc; + msg.wParam = wParam; + msg.lParam = lParam; + add_message(sequences, LISTVIEW_SEQ_INDEX, &msg); + + defwndproc_counter++; + ret = CallWindowProcA(info->oldproc, hwnd, message, wParam, lParam); + defwndproc_counter--; + return ret; +} If you're subclassing the header control and checking messages from the header control, then you need to add another message sequence, HEADER_SEQ_INDEX. --- a/dlls/comctl32/tests/msg.c +++ b/dlls/comctl32/tests/msg.c @@ -158,6 +158,9 @@ void ok_sequence_(struct msg_sequence ** ok_(file, line) ((expected->flags & winevent_hook) == (actual->flags & winevent_hook), "%s: the msg 0x%04x should have been sent by a winevent hook\n", context, expected->message); + ok_(file, line) ((expected->flags & hdr) == (actual->flags & hdr), + "%s: the msg 0x%04x should have been sent by the header control\n", + context, expected->message); expected++; actual++; } msg.c is the message sequence testing code abstracted...keyword is abstraction. Nothing in msg.c should know anything about specific types of controls. -- James Hawkins

2 2

Message spy log viewer
by Felix Nawothnig 23 Feb '07

23 Feb '07

Hi. I just figured I never told anyone (did I?) - a while ago I wrote a Ruby/GTK2 tool to parse +message logs (along with other channels mixed in) and display them in a treeview - makes debugging message related problems much easier. I suppose others wrote similar scripts for their own use - but maybe someone will find it useful nevertheless: http://users.holycrap.org/flexo/spy.rb Use like: $ WINEDEBUG="+message" wine foo.exe 2>log $ ruby spy.rb log Felix

1 0

Sound problems with Alice
by gslink 23 Feb '07

23 Feb '07

In the past I have always used the demo version of the game Alice to test Wine. Recently I loaded a Wine installation and found the game had no sound. After considerable testing it appears that about a year ago a change was made in Wine that killed the sound. Has anyone else had this problem and does it affect anything else? On my loads most other things seem to have sound.

2 1

Re: msi: Free the data for type msidbCustomActionTypeContinue custom actions after DllThread executes
by James Hawkins 23 Feb '07

23 Feb '07

On 2/23/07, James Hawkins <truiken(a)gmail.com> wrote: > Hi, > > This fixes bug 7461. http://bugs.winehq.org/show_bug.cgi?id=7461 > > Changelog: > * Free the data for type msidbCustomActionTypeContinue custom actions > after DllThread executes. > > dlls/msi/custom.c | 6 +++--- > 1 files changed, 3 insertions(+), 3 deletions(-) > Please ignore this patch. It's not exactly correct. -- James Hawkins

1 0

RE: unicoding xcopy - question on wcschr
by Ann & Jason Edmeades 23 Feb '07

23 Feb '07

For reference: 'obviously'... adding this line to the makefile solves it MODCFLAGS = -fno-builtin (Copied from msvcrt\tests) Jason

1 0

unicoding xcopy - question on wcschr
by Ann & Jason Edmeades 23 Feb '07

23 Feb '07

Hi, Trying to convert my xcopy to Unicode proved simple on windows, but when putting into wine has proved more interesting. Most of the wide string calls are like lstrcmpW and they all work fine, but I really need the Unicode equivalent to strchr and strrchr. As far as I can tell my only option is wcschr. If I build as-is, I get errors saying wcschr is implicitly defined but the link etc is all ok (from a url http://fgouget.free.fr/wine/PrgApps/Chap7.shtml#filerev it implies this is because I am using the GNU C headers, and they don't define it in string.h). Grepping the source, I can only find a hit inside the msvcrt/string.h or wchar.h. If I add to the makefile EXTRAINCL = -I$(TOPSRCDIR)/include/msvcrt, to ensure I pick up the wine headers, I now get warnings like: ./../include/msvcrt/ctype.h:72: warning: conflicting types for built-in function 'iswalnum' How do I #include / link a program using this function? It all just worked under windows :-) Jason

1 0

Progress in implementation of Direct3D
by Mirek 23 Feb '07

23 Feb '07

Hi, i would like to say "Thanks for your work!" to all wine developers. In past months there was realy big progress in implementation of Direct3D in wine (that part is most important for me) and other parts such Dinput, so I would like to introduce you some more sreenshots from latest Direct3D applications. I will try to post them on official wine website. To run third benchmark in 3DMark 2005 I used wined3d_3dmark05.diff.txt patch (from H. Verbeet) To run Call of Dutty 2 I used cod2.diff patch (my latest modification of patch against current CVS) All screenshots are from today CVS 20.02.2007 without patch "[9/10] WineD3D: Use VBOs for index buffers" which caused some regressions. http://headline.czela.net/Mirek/wine/ or via IP: http://62.240.181.87/Mirek/wine/ --- dlls/wined3d/directx.c | 7 ++++--- 1 files changed, 4 insertions(+), 3 deletions(-) diff --git a/dlls/wined3d/directx.c b/dlls/wined3d/directx.c index 841e16f..ca3eaaf 100644 --- a/dlls/wined3d/directx.c +++ b/dlls/wined3d/directx.c @@ -585,7 +585,7 @@ BOOL IWineD3DImpl_FillGLCaps(IWineD3D *iface, Display* display) { glGetIntegerv(GL_MAX_TEXTURE_UNITS_ARB, &gl_max); TRACE_(d3d_caps)(" FOUND: ARB Multitexture support - GL_MAX_TEXTURE_UNITS_ARB=%u\n", gl_max); gl_info->supported[ARB_MULTITEXTURE] = TRUE; - gl_info->max_textures = min(MAX_TEXTURES, gl_max); + gl_info->max_textures = 8; gl_info->max_texture_stages = min(MAX_TEXTURES, gl_max); gl_info->max_samplers = max(gl_info->max_samplers, gl_max); } else if (strcmp(ThisExtn, "GL_ARB_texture_cube_map") == 0) { @@ -2196,7 +2196,7 @@ static HRESULT WINAPI IWineD3DImpl_GetDeviceCaps(IWineD3D *iface, UINT Adapter, *pCaps->MaxVertexBlendMatrixIndex = 1; *pCaps->MaxAnisotropy = GL_LIMITS(anisotropy); - *pCaps->MaxPointSize = GL_LIMITS(pointsize); + *pCaps->MaxPointSize = 64.0f; *pCaps->VertexProcessingCaps = WINED3DVTXPCAPS_DIRECTIONALLIGHTS | @@ -2294,7 +2294,8 @@ static HRESULT WINAPI IWineD3DImpl_GetDeviceCaps(IWineD3D *iface, UINT Adapter, *pCaps->NumSimultaneousRTs = GL_LIMITS(buffers); - *pCaps->StretchRectFilterCaps = 0; + *pCaps->StretchRectFilterCaps = WINED3DPTFILTERCAPS_MINFLINEAR | + WINED3DPTFILTERCAPS_MAGFLINEAR; *pCaps->VertexTextureFilterCaps = 0; if(*pCaps->VertexShaderVersion == WINED3DVS_VERSION(3,0)) {

3 2

0.9.31 not suitable for gaming
by Pavel Troller 23 Feb '07

23 Feb '07

Hi! I've tried 0.9.31 and it seems that there is a regression in at least two games: - Fallout Tactics (BOS.exe): Shows a dialog stating "C:\dev\phoenix\display\win32\win32_window.cpp(873): **fatal error**: Could not create display buffers" and then another one about abnormal termination of the program and quits. - Steam based games, mainly HL2: During game load, the screen goes black. Moving the cursor causes sound effects as it hovers across the menus and buttons, so the program runs, but nothing can be seen. Both those games are known to work with wine at about a half between .29 and .30. I tried it with basic .31 as well as with today's git update. Are those regressions known and is it a work in progress, or should I make a bisecting session to find the problem ? With regards, Pavel Troller

5 19

Re: How complete will Wine ever be for older apps?
by Juan Lang 23 Feb '07

23 Feb '07

> I'm just trying to build up a picture in my head of whether there > will come a day when Wine users can pick an app designed for a > previous generation of Windows and expect it to work flawlessly > (ignoring things that try to manipulate the hardware directly, I > suppose)? Or will there always be incompatibilities? There will (likely) always be incompatibilities. Wine development has always been driven by app compatibility - someone picks an app and tries to run it, and tries to fix problems they come across. We don't aim for feature completeness - Windows is far, far too big to replicate with the resources we have. So, some apps (the ones developers have worked on, and likely others) will work quite well, while others (those that haven't been worked on) may not work as well. --Juan ____________________________________________________________________________________ TV dinner still cooling? Check out "Tonight's Picks" on Yahoo! TV. http://tv.yahoo.com/

2 1