From 67dca1b79445de9c47d590649f9dce54d5a7d7db Mon Sep 17 00:00:00 2001
From: Alexandre Julliard <julliard@winehq.org>
Date: Mon, 21 Jul 2003 23:50:39 +0000
Subject: [PATCH] Fixed prototypes of VTableProcStruc callback functions.

---
 dlls/advapi32/crypt.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/dlls/advapi32/crypt.c b/dlls/advapi32/crypt.c
index dc48045032a..83d844b0d00 100644
--- a/dlls/advapi32/crypt.c
+++ b/dlls/advapi32/crypt.c
@@ -142,7 +142,7 @@ static inline BOOL CRYPT_ANSIToUnicode(LPCSTR str, LPWSTR* wstr, int wstrsize)
 }
 
 /* These next 2 functions are used by the VTableProvStruc structure */
-BOOL CRYPT_VerifyImage(LPCSTR lpszImage, BYTE* pData)
+static BOOL CALLBACK CRYPT_VerifyImage(LPCSTR lpszImage, BYTE* pData)
 {
 	if (!lpszImage || !pData)
 	{
@@ -153,7 +153,7 @@ BOOL CRYPT_VerifyImage(LPCSTR lpszImage, BYTE* pData)
 	return TRUE;
 }
 
-BOOL CRYPT_ReturnhWnd(HWND *phWnd)
+static BOOL CALLBACK CRYPT_ReturnhWnd(HWND *phWnd)
 {
 	if (!phWnd)
 		return FALSE;
@@ -210,8 +210,8 @@ PCRYPTPROV CRYPT_LoadProvider(PSTR pImage)
 	 *        Does it need memory allocation?
          */
 	provider->pVTable->Version = 3;
-	provider->pVTable->pFuncVerifyImage = CRYPT_VerifyImage;
-	provider->pVTable->pFuncReturnhWnd = CRYPT_ReturnhWnd;
+	provider->pVTable->pFuncVerifyImage = (FARPROC)CRYPT_VerifyImage;
+	provider->pVTable->pFuncReturnhWnd = (FARPROC)CRYPT_ReturnhWnd;
 	provider->pVTable->dwProvType = 0;
 	provider->pVTable->pbContextInfo = NULL;
 	provider->pVTable->cbContextInfo = 0;