Hi John > That is the only thing that makes sense to me. Do you know this for certain?
Yes. Please see https://docs.microsoft.com/en-us/windows/desktop/winprog64/file-system-redirector > I had hoped that by having LEP display the console, I could tell which > version of PowerShell was run To tell if a running application is 32-bit or 64-bit, open Windows Task Manager (Processes tab). 32-bit applications have a *32 to the right of the executable name. >. 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 At the point you launch PowerShell, it has no idea what you’re going to do with it. You may access external 32-bit (or 64-bit) DLLs/COM objects or you may not. Quite simply, the OS knows the 32-bit application is trying to access “system32” and so translates that to SysWow64. This is transparent to the 32-bit application. > When PowerShell is launched I do not think that the OS knows which or even if > a dll is going to be addressed. Exactly, it doesn’t. It does however know that a 32-bit application is trying to access the system32 folder. > Does that mean a 32bit 4D will not launch 64 bit PowerShell ever? If you need to force a 32-bit application to launch 64-bit stuff from system32, you can use a special virtual directory “Sysnative”. Note that this virtual directory is only for 32-bit applications. This is detailed at the end of the article I’ve sent. Hope this helps. Best regards Keith White Synergist Express Ltd, UK. 4697775 ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
