64-bit

问题 I am attempting to build OpenSSL 1.0.1e static 64-bit libs with VC++ 2010. (The last one that I successfully built like this was 1.0.1c, if that might be a factor. And currently I am also able to successfully build the 32-bit flavor of 1.0.1e with no problems.) I am using ActiveState Perl, nasm, and all the correct tools to do this build, I believe. The INSTALL.W64 file only has instructions for building the DLL, which unfortunately I cannot use. I am calling the proper "%VS100COMNTOOLS%....

问题 I have a pretty generic 64bit driver based on bulkusb.sys in WDK. It's been working for years with an embedded program, but now it is needed to work on Vista 64. From all the documentation I've tried to look through there doesn't seem to be anything affecting it, except compiling it for the 64bit environment, and yet when I compile it with the AMD64 build environment, I get "driver not intended for this platform" error message when it's trying to open the sys. What could be the solution for

问题 What would be the negative effects of installing a legacy 32bit app into the C:\Program Files instead of the C:\Program Files(x86) ? 回答1: I don't think it matters. You can run a 64-bit from your Desktop, an external drive, etc. the same way you can run a 32-bit app. I think the difference is purely for organization. Or say you are developing a 32-bit and a 64-bit version of an application, you could install both of them and run them side by side by putting them in the separate Program Files

问题 Host OS is x64 Win 2003. Trying to load x64 iso (Ultrabac) and get the following: "Attempting to load an x64 operating system, however this CPU is not compatible with x64 mode. Please install a 32-bit X86 operating system. Setup cannot continue. Press any key to exit." So I ran Processor Check for 64-Bit Compatibility and it came up ok. Anyone have any ideas? 回答1: You also need a BIOS that supports virtualisation extensions - checkso a) that your BIOS has this setting b) that it is set to ON

问题 Why does the following piece of code gives 24 as an answer? That is, how is the total size of the object of following class X, 24 bytes? I'm using 64-bit machine. #include <bits/stdc++.h> using namespace std; class X { vector <bool> f; int b; public: X(){ f.push_back(true); } }; int main(){ X ob; cout<<sizeof(ob); return 0; } 回答1: That is, how is the total size of the object of following class X, 24 bytes? I'm using 64-bit machine. C++ makes few guarantees about type sizes and none about the

问题 I understand converting MMX 32bit mmx intrinsics no longer allows the __m64. So I was having great trouble upgrading this piece of code to SSE. I was told on another stack-Overflow post to post my code. Perhaps this exercise will help others as well. I commented out '_mm_empty' thinking that was the right thing to do. I found like functions in the emmintrin.h for all the other __m128i opertions, but something is still wrong. original 32-bit function code: DWORD CSumInsideHorizontalTask:

问题 What happens if I use SHGetFolderPath api call in a 32 bit system with CSIDL_PROGRAM_FILESx86 folder id instead of the CSIDL_PROGRAM_FILES id? Theoretically CSIDL_PROGRAM_FILESx86 should map to C:\program files (x86) in a 64 bit system but what does it map to in a 32 bit system where this path doesn't exist? 回答1: The different scenarios are described in this article on MSDN. Scroll down to remarks, "FOLDERID_ProgramFiles" OS Application KNOWNFOLDERID Default Path CSIDL Equivalent 32 bit 32

问题 Whats the correct way to build the setup installers for a Windows Forms app to install and run on a Windows 7 32 bit machine, using Visual Studio 2010 on a Windows 7 64 bit machine ? I've just brushed the dust off a 3yr old Visual Studio 2008 app, built on Windows XP, using SQL Express 2005. I've updated it to VS2010, SQL Express 2008, and rebuilt it on a Windows 7 64 bit machine. It needs to run on a Windows 7 32 bit platform. The setup project for database keeps failing (on startup) when

问题 I am writing an Visual C++ program in pure Win32 API. As per my understanding, I need to separately compile and generate executable for x86 and x64 architecture. How do I combine them into single executable and emit the x64 at runtime? I have seen Sysinternals tools doing the same , but don't know how it is done programmatically. Do I have to include my x64 version as a resource into x86 and then write to filesystem and do CreateProcess ? Any pointers ? 回答1: Yes, they embed the operating

问题 I am trying to get a valid MongoDB Timestamp, I have this: import {Timestamp} from "bson"; const ts = Timestamp.fromInt(Date.now() - 45000); console.log(ts); that logs: Timestamp { _bsontype: 'Timestamp', low_: 853265937, high_: 0 } that doesn't seem right, what am I doing wrong? Note that a valid timestamp instance is a 64bit thing: http://mongodb.github.io/node-mongodb-native/core/api/Timestamp.html 回答1: To get Timestamp 45 seconds ago: Timestamp((new Date().getTime()-45000)/1000,0) Date()