Just FYI here are some tests I made in November:
http://www.reactos.org/archives/public/ros-dev/2005-November/006273.html
Casper
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Steven Edwards
Sent: 13. januar 2006 17:01
To: Rolf Kalbermatter
Cc: wine-dev
Just FYI here are some tests I made in November:
http://www.reactos.org/archives/public/ros-dev/2005-November/006273.html
Casper
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Steven Edwards
Sent: 13. januar 2006 17:01
To: Rolf Kalbermatter
Cc: wine-dev
+COPYFILEDLGORD DIALOG LOADONCALL MOVEABLE DISCARDABLE 20, 20, 208, 105
+STYLE DS_MODALFRAME | DS_SETFONT | WS_POPUP | WS_VISIBLE | WS_CAPTION
+CAPTION "Overførere Filer..."
+FONT 8, "MS Shell Dlg"
+BEGIN
Should be:
+CAPTION "Overfører Filer..."
> -Original Message-
> From: [EMAIL PROTEC
In copyright law it's the result that matter, not the process. To be
protected by copyright law, it must be in tangible form. Looking at
disassembled code is permitted by copyright law so it's only a problem
if the person doing it lacks self-discipline and uses the disassembled
code in a way that v
lection of wine tools on windows
>
> Hi,
>
> --- Casper Hornstrup <[EMAIL PROTECTED]> wrote:
> > I might vote for using WINE headers in ReactOS if WINE
> relicensed its
> > headers to a w32api or BSD like license that will allow use in a
> > non-free appl
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Ivan Leo Puoti
> Sent: 21. februar 2005 09:26
> To: wine-devel@winehq.com
> Cc: [EMAIL PROTECTED]
> Subject: Re: Collection of wine tools on windows
>
> Dimitrie O. Paun wrote:
> > Heh, the MinGW
> -Oprindelig meddelelse-
> Fra: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] På vegne af Steven Edwards
> Sendt: 8. december 2003 23:05
> Til: [EMAIL PROTECTED]
> Emne: rpcrt4 and rpcss with WINE and ReactOS
>
>
> Hello,
> Ok I know this going to start YALD (Yet Another Long
> Discu
> -Oprindelig meddelelse-
> Fra: Dmitry Timoshkov [mailto:[EMAIL PROTECTED]
> Sendt: 6. december 2003 14:00
> Til: Casper Hornstrup
> Cc: [EMAIL PROTECTED]
> Emne: Re: LockResource16 in ole32.dll
>
>
> "Casper Hornstrup" <[EMAIL PROTECTED]>
I would like to have the call to the Win16 API LockResource16
removed from ole32.dll. I guess there is a reason for it being
LockResource16 and not LockResource. What is the reason?
How can the call be removed?
Casper
chorns-IsAccelerator.diff
Description: Binary data
Great. I have a few more patches at http://212.242.245.122/patches/.
Maybe you can review them?
Casper
> -Oprindelig meddelelse-
> Fra: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] På vegne af Eric Pouech
> Sendt: 30. november 2003 20:57
> Til: Casper Hornstrup
> Cc
> -Oprindelig meddelelse-
> Fra: Eric Pouech [mailto:[EMAIL PROTECTED]
> Sendt: 30. november 2003 16:39
> Til: Casper Hornstrup
> Cc: [EMAIL PROTECTED]
> Emne: Re: Mmsystem API timeGetTime
>
> I see two ways of doing it:
> - either use a function
> -Oprindelig meddelelse-
> Fra: Eric Pouech [mailto:[EMAIL PROTECTED]
> Sendt: 30. november 2003 16:35
> Til: Casper Hornstrup
> Cc: 'wine-devel'
> Emne: Re: Splitting out shared Win16/Win32 code
>
>
> Casper Hornstrup wrote:
> > Dlls/win
How can this API be implemented so it does not have to use
ReleaseThunkLock and RestoreThunkLock (at least the Win32
version)?
DWORD WINAPI timeGetTime(void)
{
/* FIXME: releasing the win16 lock here is a temporary hack (I hope)
* that lets mciavi.drv run correctly
*/
DWORD coun
should it be handled?
Casper Hornstrup
14 matches
Mail list logo
