[PATCH v2 2/6] dplayx: Use the documented reply layout in DP_MSG_SendRequestPlayerId().

[Anton Baskanov]

From: Anton Baskanov

---
 dlls/dplayx/dplayx_messages.c | 8 --------
 dlls/dplayx/dplayx_messages.h | 8 ++++----
 2 files changed, 4 insertions(+), 12 deletions(-)

diff --git a/dlls/dplayx/dplayx_messages.c b/dlls/dplayx/dplayx_messages.c
index 0568a74cb3d..e851d881c7f 100644
--- a/dlls/dplayx/dplayx_messages.c
+++ b/dlls/dplayx/dplayx_messages.c
@@ -286,14 +286,6 @@ HRESULT DP_MSG_SendRequestPlayerId( IDirectPlayImpl *This, DWORD dwFlags, DPID *

TRACE( "Received reply for id = 0x%08lx\n", lpcReply->dpidNewPlayerId );

-    /* FIXME: I think that the rest of the message has something to do
-     *        with remote data for the player that perhaps I need to setup.
-     *        However, with the information that is passed, all that it could
-     *        be used for is a standardized initialization value, which I'm
-     *        guessing we can do without. Unless the message content is the same
-     *        for several different messages?
-     */
-
     free( msgHeader );
     free( lpMsg );
   }
diff --git a/dlls/dplayx/dplayx_messages.h b/dlls/dplayx/dplayx_messages.h
index ac0850ef170..f29b52b5ae1 100644
--- a/dlls/dplayx/dplayx_messages.h
+++ b/dlls/dplayx/dplayx_messages.h
@@ -209,10 +209,10 @@ typedef struct tagDPMSG_NEWPLAYERIDREPLY

DPID dpidNewPlayerId;

-  /* Assume that this is data that is tacked on to the end of the message
-   * that comes from the SP remote data stored that needs to be propagated.
-   */
-  BYTE unknown[36];     /* This appears to always be 0 - not sure though */
+  DPSECURITYDESC secDesc;
+  DWORD sspiProviderOffset;
+  DWORD capiProviderOffset;
+  HRESULT result;
 } DPMSG_NEWPLAYERIDREPLY, *LPDPMSG_NEWPLAYERIDREPLY;
 typedef const DPMSG_NEWPLAYERIDREPLY* LPCDPMSG_NEWPLAYERIDREPLY;