Oh... 1. Yes, one way is to parse the exe. (offset, offset, check for "PE\0\0", next two bytes)
2. Check for WoW64 redirection. (I'm not sure how, though.) > On Aug 30, 2019, at 6:10 PM, Tom Glod via use-livecode > <use-livecode@lists.runrev.com> wrote: > > I think he is asking to find out if the BUILD is 32 or 64 bit. In that > case the platform() function really has to be updated. but there is > porobably a way by reading the magic (file header) bytes of the > standalone. But can't be sure. > > On Fri, Aug 30, 2019 at 5:43 PM Dar Scott Consulting via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> 1. Check for files and folders that are are required on one or do not >> exist on one. >> >> Program Files (x86) >> SysWOW64 >> >> 2. systeminfo >> >> >> >>> On Aug 30, 2019, at 1:22 PM, Devin Asay via use-livecode < >> use-livecode@lists.runrev.com> wrote: >>> >>> Hi all, >>> >>> I know we can get all manner of information about the host system our >> stack or application is running on, including platform(), processor(), and >> machine() but is there a way to check to see whether the host OS is 32 or >> 64 bit? The platform function on Windows always returns Win32 regardless of >> which version of Windows is running, and the processor reports x86_32 or >> x86_64, depending on the host machine’s CPU. >>> >>> Now that we can build both 32 and 64 bit applications for Windows, it’s >> important to be able to tell whether the host OS is 32 or 64 bit. But I >> can’t work out if these functions let us get that information. For >> instance, on my Windows 10 64-bit system I get: >>> >>> The platform: Win32 >>> The processor: x86_64 >>> The machine: x86_64 >>> >>> But I just had a user report that they were unable to run a new build of >> one of my Windows applications, which I had built as 64 bit. I’m sending >> them a 32-bit build, but I got to thinking, would there be a way to check >> that from within LiveCode? >>> >>> Any ideas? >>> >>> Devin >>> >>> Devin Asay >>> Brigham Young University >>> _______________________________________________ >>> use-livecode mailing list >>> use-livecode@lists.runrev.com >>> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >>> http://lists.runrev.com/mailman/listinfo/use-livecode >>> >> >> >> _______________________________________________ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode >> > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
