32bit-64bit

Why is Windows 32-bit called Windows x86 and not Windows x32?

陌路散爱 提交于 2020-06-24 07:01:19
问题 The Windows operating system can be either 32 bit or 64 bit. The 64 bit version is called Windows x64 but the 32 bit version is called Windows x86 . Why isn't it called Windows x32 ? What is the reason? 回答1: x86 is the name of the architecture that it's built to run on (the name comes from a series of old Intel processors, the names of which all ended in 86, The first of which was the 8086). Although x86 was originally a 16-bit architecture, the version in use today is the 32-bit extension.

How to read from a 32 bit .mdb with 64 bit python and odbc driver

感情迁移 提交于 2020-06-17 05:20:42
问题 Hello again community, I'm looking for a solution to 32 bit .mdb's conflicting with my 64 bit environment: 64 bit Windows 7, with a 64 bit MS Access Database driver running 64 bit python. I want to write data from these .mdb's into a 64 bit PostgreSQL database and possibly also to .csv files. However, I would like this tool to not only work on my machine but also those of colleagues so it would ideally be able to handle other environments as well. Initially I had a script writing to .csv with

Checking if an executable is 32-bit or 64-bit with a python3 script on Windows/Linux

半城伤御伤魂 提交于 2020-06-17 02:03:30
问题 I'm writing software in Python3 (more specifically: Python 3.8.1 ). At some point, the software needs to check if some arbitrary executable is 64-bit or 32-bit. After some research, I found the following post: Checking if an exe is 32 bit or 64 bit In this post, the following solution is offered: subprocess.call(['dumpbin', '/HEADERS', 'test2.exe', '|', 'find', '"machine"']) Unfortunately, this doesn't work in Python 3.8.1 . That post is almost 8 years old and dates back to the Python 2.x

Setting task value based on active file type associations when upgrading

跟風遠走 提交于 2020-06-13 08:49:26
问题 I have the following tasks as part of my installer: [Tasks] Name: register32; Description: "Meeting Schedule Assistant (32 bit)"; \ GroupDescription: "{cm:FileAssociations}"; flags: unchecked exclusive; Name: register64; Description: "Meeting Schedule Assistant (64 bit)"; \ GroupDescription: "{cm:FileAssociations}"; Check: IsWin64; Flags: exclusive; By design, Inno Setup has UsePreviousTasks set to Yes . However, my software installs both bit editions and the user may subsequently override

Setting task value based on active file type associations when upgrading

一曲冷凌霜 提交于 2020-06-13 08:46:07
问题 I have the following tasks as part of my installer: [Tasks] Name: register32; Description: "Meeting Schedule Assistant (32 bit)"; \ GroupDescription: "{cm:FileAssociations}"; flags: unchecked exclusive; Name: register64; Description: "Meeting Schedule Assistant (64 bit)"; \ GroupDescription: "{cm:FileAssociations}"; Check: IsWin64; Flags: exclusive; By design, Inno Setup has UsePreviousTasks set to Yes . However, my software installs both bit editions and the user may subsequently override

Inno Setup - Register for both 32 bit and 64 bit

本小妞迷上赌 提交于 2020-05-23 10:56:30
问题 This issue has only raised itself now that I am registering my file types: ; Register File Types 32 bit Root: HKCR; SubKey: ".mwb"; ValueType: string; ValueData: "MeetingScheduleAssistant.MeetingWorkBook"; Flags: uninsdeletekey Root: HKCR; SubKey: "MeetingScheduleAssistant.MeetingWorkBook"; ValueType: string; ValueData: "Meeting Workbook"; Flags: uninsdeletekey Root: HKCR; SubKey: "MeetingScheduleAssistant.MeetingWorkBook\Shell\Open\Command"; ValueType: string; ValueData: """{app}

Inno Setup - Register for both 32 bit and 64 bit

荒凉一梦 提交于 2020-05-23 10:55:08
问题 This issue has only raised itself now that I am registering my file types: ; Register File Types 32 bit Root: HKCR; SubKey: ".mwb"; ValueType: string; ValueData: "MeetingScheduleAssistant.MeetingWorkBook"; Flags: uninsdeletekey Root: HKCR; SubKey: "MeetingScheduleAssistant.MeetingWorkBook"; ValueType: string; ValueData: "Meeting Workbook"; Flags: uninsdeletekey Root: HKCR; SubKey: "MeetingScheduleAssistant.MeetingWorkBook\Shell\Open\Command"; ValueType: string; ValueData: """{app}

Referencing x86 COM wrapper from 64 bit project

主宰稳场 提交于 2020-04-16 02:59:05
问题 I have created an x86 "wrapper" for an x86 library we have from a vendor. I've been following the steps mostly from this post as well a couple links for calling COM here and here. I marked the project as "Register for COM interop". I was able to find by COM interface using oleview and marked it as "Use Surrogate Process". So hopefully I'm good to this point as far as the DllSurrogate registry settings go. Now I can't seem to get the reference correct to consume the x86 COM. Supposedly I can

How can I determine whether a process is 32 or 64 bit?

风格不统一 提交于 2020-04-08 09:28:05
问题 Given a Windows process handle, how can I determine, using C++ code, whether the process is 32 bit or 64 bit? 回答1: If you have handle to the module then you can do this: IMAGE_NT_HEADERS * headers = ImageNtHeader(handle); if ( headers->FileHeader.Machine == IMAGE_FILE_MACHINE_I386 ) { //module is x86 } else if ( headers->FileHeader.Machine == IMAGE_FILE_MACHINE_AMD64 ) { //module is x64 } I took help from my own answer. 回答2: If you have a process handle, use IsWow64Process(). If

/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/9/libstdc++.a when searching for -lstdc++ /usr/bin/ld: cannot find -lstdc++

会有一股神秘感。 提交于 2020-03-16 07:34:24
问题 why am i getting this error? g++ -m32 func.o test.o -o prgram /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/9/libstdc++.so when searching for -lstdc++ /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/9/libstdc++.a when searching for -lstdc++ /usr/bin/ld: cannot find -lstdc++ collect2: error: ld returned 1 exit status my code is as follows: #include<stdio.h> 2 3 4 extern "C" int calcsum(int a, int b, int c); 5 6 int main(int argc,char* argv[]) 7 { 8 int a =