- One problem, one weekend, eight languages
- How to retrive Outlook default signature
- How to completely uninstall VFP 9.0
- Retrieving VFP runtime DLL name required by EXE or DLL
- Send email via MSN email account
- Send email via Yahoo mail account
- Remove Structural CDX or Memo flag from a table
- Deleting pages from PDF file through Acrobat automation
- GDIPLUS.DLL security updates for VFP 8.0 and VFP 9.0
- Powershell - Benchmark Command
How to detect 64-bit OS
On 64-bit Windows the 32-bit Windows-based applications run under WOW64 x86 emulator. WOW64 isolates 32-bit applications from 64-bit applications, which includes preventing file and registry collisions. Console, GUI, and service applications are supported. However, 32-bit processes cannot load 64-bit DLLs, and 64-bit processes cannot load 32-bit DLLs.
A 32-bit application can detect whether it is running under WOW64 by calling the IsWow64Process function. The application can obtain additional information about the processor by using the GetNativeSystemInfo function.
The IsWow64Process function is only included in Windows OS that have 64-bit versions. To avoid an error we have to check for it presence with GetProcAddress / GetModuleHandle WIN API functions before it can be called.
* First determine if IsWow64Process function exists in the OS we're running under DECLARE Long GetModuleHandle IN WIN32API STRING lpModuleName DECLARE Long GetProcAddress IN WIN32API Long hModule, String lpProcName llIsWow64ProcessExists = (GetProcAddress(GetModuleHandle("kernel32"),"IsWow64Process") <> 0) llIs64BitOS = .F. IF llIsWow64ProcessExists DECLARE Long GetCurrentProcess IN WIN32API DECLARE Long IsWow64Process IN WIN32API Long hProcess, Long @ Wow64Process lnIsWow64Process = 0 * IsWow64Process function return value is nonzero if it succeeds * The second output parameter value will be nonzero if VFP application is running under 64-bit OS IF IsWow64Process( GetCurrentProcess(), @lnIsWow64Process) <> 0 llIs64BitOS = (lnIsWow64Process <> 0) ENDIF ENDIF ? llIs64BitOS