I made my mistake by pointing PL to the 32 bit version of PSP. Not the wrong plugins but the wrong External program version.
So when I opened PSP as an External program from PL, it opened the 32 bit version of PSP which couldn't see the 64 bit plugins. OK!
However if I had PSP already running, (I always use the 64 bit version with the 64 bit plugins), and from PL opened External program it opened the 64 bit version of PSP! Even though the ONLY External program in PL was the 32 bit version of PSP, PL opened the 64 bit version if PSP was already running!
So why if I only had the 32 bit version of PSP in External programs does PL ignore that and open the 64 bit version of PSP if the 64 bit version is already running?
brucet hat geschrieben: So why if I only had the 32 bit version of PSP in External programs does PL ignore that and open the 64 bit version of PSP if the 64 bit version is already running?
I think it's a Windows thing -- if a process is already running, that will be used instead of starting a new instance of the process.
You'll need to use Process Explorer to check the actual process name of the process used by PSP when you launch the 32-bit and 64-bit versions.
Ken Yes, I think it can be eeeeeasily done....
Just take everything out on Highway 61.
Ken if it was Windows controlling it then I would have thought it would have opened the 64 bit version as that is my default go to image software.
Why would PL open the 32 bit version if PSP isn't already running but then open the 64 bit version if it was already running. Keeping in mind that I didn't have the path to the 64 bit version listed in the External programs. So if the 64 bit version is running why does PL ignore the nominated External program in favor of another version???
I have it all sorted now by deleting the 32 version from the list and only having the 64 bit version listed.
Just an interesting/perplexing issue.