Yes I did install powerpro on the 64-bit version (as opposed to just copying the files) using the setup.exe. I can verify that HKLM/software/stilettoproducts registry key exists on both 32 and 64-bit machines. Is there some other registry keys that PP uses I can check for?
I don't think something is quite right about the DLL though. If I right click it and go to properties it does not show as a shell extension like the original file did (even on 64-bit). --- In [email protected], "brucexs" <bswit...@...> wrote: > > > > > The pproctx.dll file is created and I transfer it to my 64-bit machine and > > restart powerpro. Unfortunately it does not seem to work. > > > > On the 32-bit machine I run the listdlls.exe command and see that > > pproctx.dll is loaded by explorer.exe. I also see it creates the > > ctx_debug.txt file. On the 64-bit platform though pproctx.dll is not even > > loaded. > > > Explorer looks at certain registry keys to determine the dlls to load. > Possibly these have changed on the 64 bit version or possibly pproconf cannot > access. > > Did you install using PowerPro on the 64 bit version? > > Was PowerPro successful in loading the keys into the registry under the keys > where it wants them to do? It may be that because pproconf is 32 bit, then > some kind of registry redirection has happened. > > If above two are true, then need to confirm that this the right place for the > PowerPro to load the info for a shell extension under 64 bit. > > I don't have access to the code from where I am writing this note. I wanted > to give you an immediate heads up in case you wanted to pursue. >
