wine-devel September 2004

wine-devel@winehq.org

131 participants
282 discussions

shell32 unicodefy question
by Vitaliy Margolen 05 Sep '04

05 Sep '04

First of all I would like to check if there are any one working on this. Second Q: Some methods of IFSHelper interface defined as taking LPCSTR params. Is this right? I was unable to find any information in regards to this. And because this is exported interface I don't want to brake something that is already working. -- Best regards, Vitaliy

1 0

Re: Compile fix forinclude files from linux 2.6.7
by Marcus Meissner 05 Sep '04

05 Sep '04

On Sun, Sep 05, 2004 at 05:38:03PM +0200, Rein Klazes wrote: > Hi, > > Fix for bugzilla bug#2354, compile failure on Slackware 10. > > The include <linux/fd.h> uses since Linux 2.6.7 a macro defined in > <linux/compiler.h>. Compiler.h is new in linux 2.4.4, old but not very > old, so I added an autoconf check for such systems. > > Need to run autoheader & autoconf after applying. No, if it is missing __user, just #define __user at the beginning of the file. Or try not to use linux kernel headers at all. Ciao, Marcus

2 1

Re: Critical Sections Documentation Update
by Hans Leidekker 05 Sep '04

05 Sep '04

On Sunday 5 September 2004 13:26, Robert Shearman wrote: > - * Initialise a new RTL_CRITICAL_SECTION. > + * Initializes a new critical section. I'm afraid this critical section from your critical section patch will upset people in the critics' section ;-) -Hans

1 0

Re: weird ?clipping? errors
by Filip Navara 05 Sep '04

05 Sep '04

Filip Navara wrote: > James Hawkins wrote: > >>> If the error disappears, then you're dealing with a bug in Wine's >>> comctl32.dll. >>> >> >> >> I used native comctl32.dll and both of the errors disappeared, so I >> will take your advice and search around in comctl32. >> >> > It's regression in dlls/comctl32/propsheet.c that happend between > revision 1.105 and 1.112. To be more specific, it's this patch: Mike McCormack <mike(a)codeweavers.com <mailto:mike@codeweavers.com>> Adjust the tab contents to fix the propsheet between PSM_KILLACTIVE and PSM_SETACTIVE. Regards, Fi;lip

3 3

fixme:msi:MsiLocateComponentA installing dotnetredist.exe
by Dan Kegel 05 Sep '04

05 Sep '04

I installed wine-20040813 from source, then tried installing http://msdn.microsoft.com/visualc/vctoolkit2003/ (I think this gets a ways further than it did last time I tried it, yay.) Now it fails with the error I: Error installing Microsoft(R) .NET Framework. http://download.microsoft.com/download/e/b/2/eb247c2a-e6b3-4694-98a2-b27111… On the console, I saw only the four warnings/errors: fixme:msi:MsiInstallProductW L"/iH:\\IS3123.tmp\\netfx.msi" L"" fixme:msi:MSI_OpenDatabaseW open failed r = 80004005! Installation of /iH:\IS3123.tmp\netfx.msi () failed. err:dc:DCE_FreeWindowDCE [0x10026] GetDC() without ReleaseDC()! So I downloaded dotnetredist.exe and ran that by hand, and then ran the executable that unpacked. This failed with fixme:msi:MsiLocateComponentA "{A1B926EF-7FD9-11D2-A429-00A0C9E80AFB}" 0x4051ec84 00000105 fixme:msi:MsiLocateComponentA "{173A6EB3-6403-11D4-A53F-0090278A1BB8}" 0x4051ec84 00000105 That function, at least in my tree, is just a pseudostub: INSTALLSTATE WINAPI MsiLocateComponentA(LPCSTR szComponent, LPSTR lpPathBuf, DWORD *pcchBuf) { FIXME("%s %p %08lx\n", debugstr_a(szComponent), lpPathBuf, *pcchBuf); return INSTALLSTATE_UNKNOWN; } Sooo... what's the best way around this? Anyone tackle this before? Thanks, Dan -- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change

3 2

Wine bug with delphi Menus
by Robert van Herk 05 Sep '04

05 Sep '04

Hi people, I think I discovered a wine bug. In a delphi program, changing the visibility of a menuitem (TMenuItem) causes the whole menu of that form to stop working, when the program is run under Wine. Behind the screens, the setVisible of a menu item calls MenuChanged. This seems to put the menu in such a state that, in wine, all menu components stop doing anything. I've written a small application (455 kb EXE) to show what goes wrong. Would anybody be interested to help me in solving this bug? Would a message trace from Winsight (for example) be of any help? Greetings, Robert

2 1

Re: Running valgrind with Wine
by Saulius Krasuckas 05 Sep '04

05 Sep '04

On Sat, Sep 04 2004, Mike McCormack wrote: > Valgrind stopped working with Wine a while back due to the way Wine > reserves memory above address 0x80000000. > > The following patch allows valgrind to work with wine again. You need to > start wine-pthread or wine-kthread instead of starting the wine binary > depending on whether your system uses NPTL or not. eg. my system uses > kthreads so: > > valgrind wine-kthread notepad.exe I am very glad to hear this, Mike. Thanks. > I'm not sure if Alexandre wants to commit this or not, but it should be > of use to those that want to use valgrind again. Hm, still, for me valgrind doesn't work: [s2@katleriai wine]$ valgrind --tool=memcheck wine-pthread notepad.exe Executable range 0x77f00000-0x77f02370 is outside the acceptable range (nil)-0x52c00000 valgrind: do_exec(/usr/local/bin/wine-pthread) failed: Cannot allocate memory [s2@katleriai wine]$ Ideas?

2 5

regression: listbox stays disabled in created dialog-window
by Saulius Krasuckas 05 Sep '04

05 Sep '04

The [1] patch brings some regression. I have filled a bugreport: [2]. Here are two png screenshots: [3] [4], one made before the patch is applied, another made after the patch is applied. [1] http://www.winehq.org/hypermail/wine-cvs/2004/08/0341.html [2] http://bugs.winehq.org/show_bug.cgi?id=2454 [3] http://bugs.winehq.org/attachment.cgi?id=681&action=view [4] http://bugs.winehq.org/attachment.cgi?id=682&action=view

6 15

EINTR vs. WSAEINTR
by Shachar Shemesh 05 Sep '04

05 Sep '04

Hi list, When calling "select" (or any other socket function, for that purpose), there is a chance that a signal will arrive while we are blocking on the socket. This will cause the blocking function to return with EINTR. The usual recommendation is to retry the operation if that is the case. http://www.wlug.org.nz/EINTR Our current behavior, at least in "WS_select", is to convert it to WSAEINTR, and return the error. I think this behavior is wrong. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winsock/wi… MSDN says that WSAEINTR is only returned if WSACancelBlockingCall is received during the wait. I have a program for which I can affect the source that fails because of a select call being interrupted. I'm wondering whether it's better to fix the program to retry on WSAEINTR, or to fix wine. One possible fix to Wine is to mask all signals right before calling "select", and restore the signal mask when returning. This will ensure that EINTR will not be received. Can someone more versed in winsock voice an opinion about whether this is indeed a problem in Wine? Shachar

1 0

Re: Running valgrind with Wine
by Mike Hearn 05 Sep '04

05 Sep '04

On Sun, 05 Sep 2004 12:55:33 +0900, Mike McCormack wrote: > - wine_init( argc, argv, error, sizeof(error) ); > + wine_init( argc, argv, error, sizeof(error), reserve ); It's worth noting that any change to this functions prototype breaks the Ardour/Wine VST plugin bridge. Last time this issue was raised the change was reverted. While we're technically not API stable yet, it's painfully obvious that 1.0 is still a long way away. Stability is a policy rather than a target, so we've got to start at some point ....

2 1

← Newer
1
...
22
23
24
25
26
27
28
29
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel September 2004