If you hexedit the xicr50.dll as discussed then you can just register the dll normally either via (1) your installer or (2) with regsvr32.exe or (3) by creating the registry entries via your program or setup program. Our apps check if Cryptor is registered and, if not, silently register them and continue.

This hexedit need comes about not becuase of any incompatibaility as such but because of changes in MS implementation of the DEP on certain CPUs that suppport DEP.

You can make the hexedit and it will work for all Windows versions. The hack is only required for Win 2003 and Vista if they are fully patched and running on a machine supporting the new DEP protections. But it works for all Windows versions from W2K onwards.

>Oh, so you needed to hex edit your XICR50.DLL to change '.xitech' to '.aspack', and also update keys in Windows registry. The DLL hex edit is no problem as we can do it at our end. The registry keys is another issue though as our application is distributed, and our end-users are not usually capable of registry edits.
>
>Do these changes only apply to Windows 2003 / Vista machines? If so, then we would need two installation versions of our app, one for XP or older and the other for 2003 and newer. This complicates distribution and installation a bit.
>
>Mon
>
>
>><snip>
>>easy to use COM interface."
>
>>1) Re: Installation of Cryptor 5.0 Thread #1251816 Message #1258388
>>
>>2) Re: Installation of Cryptor 5.0 Thread #1251816 Message #1252833
>>-