Fwd: [PATCH 1/3] winmm: Fix mciSendString command parsing on 64-bit.

2010-08-27 Thread Joerg-Cyril.Hoehle
Octavian, >I just looked in mmddk.h and they have this: >#define MCI_INTEGER64 13 It's good you found out about MCI_INTEGER64. Yet it's completely crazy because googling it yields 6 hits in total, all about Wine bug 22146. Bing shows nothing at all. How can such a name be that invisible? >So, d

Re: Fwd: [PATCH 1/3] winmm: Fix mciSendString command parsing on 64-bit.

2010-08-27 Thread Alexandre Julliard
Octavian Voicu writes: > The reason for which I opted for a BYTE* is so that I can use sizeof() > to increment the pointer correctly. DWORD_PTR has a different size of > 32- and 64-bit systems, so using DWORD* would make it more complicated > to increment with sizeof(DWORD_PTR). Another reason is

Fwd: [PATCH 1/3] winmm: Fix mciSendString command parsing on 64-bit.

2010-08-27 Thread Octavian Voicu
Same here. -- Forwarded message -- From: Octavian Voicu Date: Thu, Aug 26, 2010 at 3:12 PM Subject: Re: [PATCH 1/3] winmm: Fix mciSendString command parsing on 64-bit. To: joerg-cyril.hoe...@t-systems.com On Thu, Aug 26, 2010 at 2:15 PM, Octavian Voicu wrote: > I just looked in

Fwd: [PATCH 1/3] winmm: Fix mciSendString command parsing on 64-bit.

2010-08-27 Thread Octavian Voicu
For some reason I forgot to hit reply to all. -- Forwarded message -- From: Octavian Voicu Date: Thu, Aug 26, 2010 at 2:15 PM Subject: Re: [PATCH 1/3] winmm: Fix mciSendString command parsing on 64-bit. To: joerg-cyril.hoe...@t-systems.com On Thu, Aug 26, 2010 at 1:11 PM,   wrot