More Darwine news (was Re: New Darwine Binary Released)

2004-08-21 Thread Jim White
Sanjay Connare wrote: Hey All, I am proud and happy to announce the release of a new binary labeled Darwine 20040820 DP. This binary is based upon the 20040813 wine release. ... Thought I would post a follow-up as Sanjay neglected to include a link to the new binary: http://darwine.opendarwin.or

Re: Wrong call convention for SHAllocShared & co?

2004-08-21 Thread Ivan Leo Puoti
>Hence my confusion and my call for help. The solution that comes in mind is write a test program and find out. Ivan.

Re: Wrong call convention for SHAllocShared & co?

2004-08-21 Thread Francois Gouget
On Sun, 22 Aug 2004, Ivan Leo Puoti wrote: > > So who's right? The platform SDK that says this is a cdecl function or > > Wine's headers? > If the SDK is wrong and is diffrent from the windows implementation, then > programs calling that function will have > problems bacause of imcompatible header

Re: Wrong call convention for SHAllocShared & co?

2004-08-21 Thread Ivan Leo Puoti
> So who's right? The platform SDK that says this is a cdecl function or > Wine's headers? If the SDK is wrong and is diffrent from the windows implementation, then programs calling that function will have problems bacause of imcompatible headers between the ones used to build windows and the SDK o

Re: Wrong call convention for SHAllocShared & co?

2004-08-21 Thread Francois Gouget
Still looking in undocshell.h, I see we have: BOOL WINAPI GetFileNameFromBrowse( HWND hwndOwner, LPSTR lpstrFile, DWORD nMaxFile, LPCSTR lpstrInitialDir, LPCSTR lpstrDefExt, LPCSTR lpstrFilter, LPCSTR lpstrTitle); But in the Platform SDK's

Wrong call convention for SHAllocShared & co?

2004-08-21 Thread Francois Gouget
In the platform SDK's shlobj.h I find: HANDLE _SHAllocShared(LPCVOID pvData, DWORD dwSize, DWORD dwDestinationProcessId); Notice the lack of a WINAPI and the leading underscore. So this would indicate a cdecl API. But in dlls/shell32/undocshell.h I see: HANDLE WINAPI SHAllocShared(LPVOID pv, U

Re: Re: make CryptSetProviderEx update the provider Name and TypeName to registry

2004-08-21 Thread James Hawkins
I just ran a test programming in windows to see how the registry is changed by called CryptSetProviderEx with the CRYPT_DELETE_DEFAULT flag. When the CRYPT_DELETE_DEFAULT flag is used, the Name value of the Type XXX key is removed, but not the TypeName, which solves the problem of not being able t

Re: Optimize Critical Section Functions

2004-08-21 Thread Alexandre Julliard
Robert Shearman <[EMAIL PROTECTED]> writes: > Yes, I agree. In fact the patch actually decreases performance. > Test: 10,000,000 calls to EnterCriticalSection & LeaveCriticalSection, > simulating fast path on critical sections. > Results: > Win2k - 1000ms > Wine w/ patch - 1346ms > Wine w/o patch

Re: MS Project 2000 not working in wine.

2004-08-21 Thread Tom
James Courtier-Dutton wrote: Has anyone got MS Project 2000 working in wine? James I tried it a couple times and get about 80% into the install. It stops at the same spot each time. fixme:powermgnt:SetThreadExecutionState (0x0): stub, harmless. fixme:ntdll:NtAdjustPrivilegesToken (0x4c,0x

Re: Optimize Critical Section Functions

2004-08-21 Thread Robert Shearman
Alexandre Julliard wrote: Michael Stefaniuc <[EMAIL PROTECTED]> writes: Andreas Mohr wrote: Umm, this should go into a global header file, right? The theory being that it would be useful at many more performance critical Wine places... But I have to admit that I don't know which header file

Re: MS Visio 2000 not working with wine.

2004-08-21 Thread Tom
James Courtier-Dutton wrote: Has anyone got MS Visio 2000 working with wine? James Yes. Tom

MS Project 2000 not working in wine.

2004-08-21 Thread James Courtier-Dutton
Has anyone got MS Project 2000 working in wine? James

MS Visio 2000 not working with wine.

2004-08-21 Thread James Courtier-Dutton
Has anyone got MS Visio 2000 working with wine? James

Re: Added path settings to winecfg

2004-08-21 Thread Marcelo Duarte
Jacek Caban escreveu: But what about other languages, which nobody updates as you do? I have one more question: where can I find this script? I see that polish translation is far from complete and I thought I could work aroun dit. Thanks, Jacek Sorry for the delay. Atached is the patch to create

[Fwd: Re: [ck] Re: Threading issues? [ck-request@vds.kolivas.org: ck Digest, Vol 3, Issue 16]]

2004-08-21 Thread Mike Hearn
Forwarded Message From: Con Kolivas <[EMAIL PROTECTED]> To: Mike Hearn <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: [ck] Re: Threading issues? [EMAIL PROTECTED]: ck Digest, Vol 3, Issue 16] Date: Sat, 21 Aug 2004 10:39:21 +1000 Mailer: Mozilla Thunderbird 0.7.1 (X11/2004

Re: Limit number of DirectDrawClipper_SetClipList FIXMEs

2004-08-21 Thread James Hawkins
> the program starts, but the difference between this and a regular > non-static variable is that this static variable holds whatever value > it contains That wasnt very clear so I'll try to explain better. The bottom line is that the value of the static variable is retained between repeated fun

Re: Limit number of DirectDrawClipper_SetClipList FIXMEs

2004-08-21 Thread James Hawkins
Tobias wrote: > > +if (warned++ < 10 && lprgn != NULL) Stefan wrote: > for me this looks like > > if (0 < 10 && lprgn != NULL) The variable 'warned' doesn't actually turn out to be zero all of the time. It is a static variable, so it is initialized once to zero when the program starts,

Re: Limit number of DirectDrawClipper_SetClipList FIXMEs

2004-08-21 Thread Andreas Mohr
Hi, On Sat, Aug 21, 2004 at 11:08:09AM +0200, Stefan Leichter wrote: > Am Freitag, 20. August 2004 18:37 schrieb Tobias Burnus: > > + > > HRESULT WINAPI Main_DirectDrawClipper_SetClipList( > > -LPDIRECTDRAWCLIPPER iface,LPRGNDATA lprgn,DWORD pdwSize > > +LPDIRECTDRAWCLIPPER iface,LPRGNDA

Re: Limit number of DirectDrawClipper_SetClipList FIXMEs

2004-08-21 Thread Stefan Leichter
Am Freitag, 20. August 2004 18:37 schrieb Tobias Burnus: > + > HRESULT WINAPI Main_DirectDrawClipper_SetClipList( > -LPDIRECTDRAWCLIPPER iface,LPRGNDATA lprgn,DWORD pdwSize > +LPDIRECTDRAWCLIPPER iface,LPRGNDATA lprgn,DWORD pdwFlag > ) { > ICOM_THIS(IDirectDrawClipperImpl,iface);