Prev: How to implement CImageList::DrawIndirect in MFC 4.2?
Next: Why is network reading slow?
From: absolute on 13 Jan 2010 20:42

> One of the most serious errors here is the error of actual BELIEVING the erroneous
> Microsoft documentation.  It makes no sense whatsoever to ever case a pointer to a DWORD,
> and in the modern Platform SDK, the actual cast should be
>         (DWORD_PTR)(LPVOID)&mciStatusParms
> or it won't compile or work in 64-bit mode.  

I changed the DWORD to DWORD_PTR, but the problem still remain
unchanged.

> In reporting errors like this, it is ESSENTIAL that you state
>         What version of VS you are using
>         What version of Windows you are using
>

I'm using VS2008 and 32bit windows xp sp3.

> Only after we see the values in hex, and preferrably, the memory contents of the entire
> MCI_STATUS_PARMS in hex (that would be 24 bytes) is it possible to determine if the error
> is in the mciSendCommand or in the application.

The memory of MCI_STATUS_PARMS is as below:(16bytes not 24bytes)
cc cc cc cc b0 6f 63 c9 01 00 00 00 cc cc cc cc
Little endian. As you see, b0 6f 63 c9 in unsigned int is 3378737072.

From: Alexander Grigoriev on 13 Jan 2010 22:10
MCI must die.

And, if my memory is correct, MS for some reason decided to localise
keywords in MCI strings. At least it was in some OS versions.

"Joseph M. Newcomer" <newcomer(a)flounder.com> wrote in message
news:evprk55p2d264qsvnh6jvi7rsld2e1047s(a)4ax.com...
> See below...
> On Wed, 13 Jan 2010 03:57:25 -0800 (PST), absolute <cool8511(a)gmail.com>
> wrote:
> One of the most serious errors here is the error of actual BELIEVING the
> erroneous
> Microsoft documentation. It makes no sense whatsoever to ever case a
> pointer to a DWORD,
> and in the modern Platform SDK, the actual cast should be
> (DWORD_PTR)(LPVOID)&mciStatusParms


From: David Ching on 13 Jan 2010 23:21
"Alexander Grigoriev" <alegr(a)earthlink.net> wrote in message
news:eW9MlcMlKHA.1540(a)TK2MSFTNGP06.phx.gbl...
> MCI must die.
>

Why? It's VCR style interface (play/stop/rewind, etc.) was simple and good
enough for many applications. I for one hate DirectDraw, the COM concept,
the confusing pins and filter graphs, what a crock.

-- David


From: absolute on 14 Jan 2010 00:04

> > MCI must die.
>
> Why?  It's VCR style interface (play/stop/rewind, etc.) was simple and good
> enough for many applications.  I for one hate DirectDraw, the COM concept,
> the confusing pins and filter graphs, what a crock.
>
> -- David

I agree. I use the MCI APIs because they are so simple.

I wonder are there other APIs as simple as MCI APIs.

Can anybody tell me a substitute?
First  |  Prev  | 
Pages: 1 2 3
Prev: How to implement CImageList::DrawIndirect in MFC 4.2?
Next: Why is network reading slow?