Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Cryptor Registering Issue
Message
De
23/08/2007 17:01:36
 
 
À
23/08/2007 06:51:56
Information générale
Forum:
Visual FoxPro
Catégorie:
Contrôles ActiveX en VFP
Versions des environnements
Visual FoxPro:
VFP 9 SP1
Divers
Thread ID:
01249211
Message ID:
01250024
Vues:
112
>>>>>>>Hi All
>>>>>>>
>>>>>>>On a few machines running Vista or XP/SP2 I am getting an error when trying to register the Cryptor XICR50.DLL. The error message is "invalid access to memory location" and it occurs when trying to register the dll using regsvr32.exe. This only happens on a few machines but I cannot see the pattern or commonality between them. On kost of our end-user mahcines there i no problem at all. Users are logged on using admin rights or even with an administrators account. Can anyone shed some light on this one?
>>>>>>
>>>>>>Antivirus?
>>>>>
>>>>>I dont believe so Al. On one machine they have the same av as I do.
>>>>
>>>>Still, it might be an easy test to disable any real-time scanning component to see if that makes a difference.
>>>
>>>Hi Al. Yeah I did try it but no luck. The weird thing is that I cannot register the XICR50.DLL using regsvr32 on a particular machine. But if I run the Cryptor setup program which comes with Cryptor when you buy it then the dll is registered perfectly fine on the problem machine and I cna use it in my app. Normally we just need to register the dll and even the documentation says that for distribution simply distribute the dll and run regsvr32 on it. Any other ideas?
>>
>
>Hi Al.
>
>This issue has been resolved. The problem relates to the recent Windows Update patches and only occurs under Windows XP SP2, Vista, and other OS updates for the DEP fix (Data Execution Prevention). It only applies to CPU’s with the NX bit. AMD Athlon is fine but Sempron will fail and XD bit (Intel).
>
>The standard method to register a DLL in the past was to use the self registering function for DLL’s and OCX’s i.e. using regsvr32.exe. Now the MS recommended method is to extract the COM information and pre-enter it into the registry manually.
>
>The Windows installer and all modern installers support this feature. You can tell newer installers to *not* auto-register a dll but rather to extract the COM information and create the necessary registry entries. If you do this or create the registry entries yourself it works. You can no longer use the regsvr32.exe method on Cryptor with the cpu's mentioned above and DEP active.

Thanks for posting the solution.
Regards. Al

"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov

Neither a despot, nor a doormat, be

Every app wants to be a database app when it grows up
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform