>Thanks for the response Al. The DLL (same copy) works fine elsewhere. The problem machine isn't running any other "system checker" of any kind (a thought I had too). I did try (just for kicks) to rename it but no joy there either. Any other ideas?

I'm still not sure if you re-copied the DLL from the source, to make sure you have a good copy on the machine that's having the problems. Can you run the command-line FC utility to compare the copy on the problem machine, to a known good one elsewhere?

A SWAG, maybe you could try to unregister the DLL ( regsvr32 ... /u ), then try again to register it.

Another SWAG, are any processes running (other than AV) that might hook the file system and/or COM e.g. "real-time" backup etc.? One class of software that often does that is malware.

>BTW Al, your name sounds familiar to me... have we met?

Quite possibly, if you've ever attended any Vancouver FoxPro User Group meeting over the years... I went to most of them.

>>>Hi,
>>>
>>>Hoping someone can help with this.
>>>
>>>This is a legacy system written in VFP6 I haven't gotten around to updating to 9.
>>>
>>>I'm trying to register CRYPTPAK.DLL (which used to be a fairly common VB and Visual FoxPro encryption DLL). Never had a prob on any other install but:
>>>
>>>
>>>(ADMINISTRATOR CMD Window)
>>>
>>> c:\windows\system32>regsvr32 cryptpak.dll
>>>
>>>(DLL is in the dir)
>>>
>>>I'm getting the msg:
>>>
>>>"The module "cryptpak.dll" was loaded but the entry-point DLLRegisterServer was not found.
>>>
>>>Make sure that "cryptpak.dll" is a valid DLL or OCX file then then try this again."
>>>
>>>Normally, this happens if there's a permissions error I *think*. Same setup works fine on many other machines running a mix of OS's.
>>>
>>>FWIW, the client system is running Norton (with Sonar) and I did try to disable Norton completely just to see. No joy.
>>>
>>>I also tried issuing "secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose" based on a forum suggestion but nada. Though that DID generate some interesting, but seemingly unrelated, errors in the log.
>>
>>If it's just one computer, is it possible the copy of the DLL is corrupted?
>>
>>On a quick Google, most of the hits seem to think cryptpak.dll is, or is part of, malware. Although you've disabled Norton, maybe something else thinks it's malware. Just for grins, maybe you could create a copy named something different e.g. CoolStuff.DLL, and try registering that.