1. Use EXPAND.EXE to decompress the .DL_ file to .DLL
2. On Windows 2000 you cannot just replace the ADVAPI32.DLL file - the DLL-cache mechanism prevents this. One way of copying is to place the new version in the root directory, then start the computer using the recovery shell (use you setup CD), and copy the new DLL to both SYSTEM32 and DLLCACHE directories.
3. The latest version of ADVAPI32.DLL in the CSPDK corresponds to Windows 2000 SP2. It will not work with SP3 or Windows XP.
4. 0x80090006 is "Invalid signature". Either you are not using the test version of ADVAPI32.DLL (as above), or you have not signed your CSP with a debug signature as explained in the documentation.
- Shalom Crown
> -----Original Message-----
> From: lm [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 22, 2002 8:42 AM
> To: [EMAIL PROTECTED]
> Subject: help about CSPDK
>
> Is anybody familiar with CSP?
>
> I have download the CSPDK from www.microsoft.com. I follow the
> procedure in the readme.txt in Windows 2000 professional, but I met
> the following problems:
>
> 1.the advapi.dl_ is not a valid dll file.
> After I overlaod the apvapi.dll in system directory with advapi.dl_
> according to the procedure, the computer can not restart again.
> Additionally,I use the Visual Studio tool Dumpbin and Dependency, I
> find the dll file is not a valid dll file.
>
> 2.signature error
> Then I ignore the first problem, and go on testing the sample CSP
> Dll. I can compile and build the CSP DLL project, csp install project
> correctly. After I run the cspinstl.exe,I can find the items in the
> system register.But when I call the SPAcquireContext, it reture
> false,and GetLastError()=0x80090006.
>
> why does this happen? If you know,I appreciate your early reply.
> Thank you very much?
>
> yours
> Janet Lee
>
