Aloha Keith,
> The reason that you think the 64-bit PowerShell is working is because
> actually the 32-bit PowerShell is still being used.
>
> When a 32-bit application (in this case 4D) accesses the system32 directory,
> those accesses are automatically redirected to the SysWow64 directory.
>
> So when you use LEP to launch PowerShell and you think you've specified the
> 64-bit version in system32, the OS is just launching the one from SysWow64.
That is the only thing that makes sense to me. Do you know this for
certain. I was suspecting that this was the case but could not find anything
that documents this behavior.
I had hoped that by having LEP display the console, I could tell which
version of PowerShell was run. But the console only displays a path above an
empty command window. When the 64bit version of PowerShell is launched by 32bit
4D the path displayed in the console is in fact to PowerShell in the System32
folder not SysWow. But I think that path only reflects the requested path from
LEP, not which version of PowerShell is actually running. If LEP launches the
32bit version the path is to PowersShell in the SysWow folder, otherwise the
consoles looks exactly the same.
Thanks for your input. I think your spot on. It’s interesting to me
that the OS is making the decision based on the architecture of the requesting
application not the architecture of the dll. How does the OS otherwise know
which to launch? Does that mean a 32bit 4D will not launch 64 bit PowerShell
ever? When PowerShell is launched I do not think that the OS knows which or
even if a dll is going to be addressed.
Enough already. I think I am beating a dead horse here. I am moving
on, but really do appreciate your input and all who have tried to straighten
out this far too curious old fart’s brain.
John
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************
