win64 | 易学教程

How do I make a 64 bit MSI?

阅读更多关于 How do I make a 64 bit MSI?

问题 I've specified: -arch x64 when running candle.exe . Platform=x64 on the Package . ProgramFiles64Folder as the Directory id where things get installed. and still, when the app gets installed, it goes to C:\Program Files (x86) . There are some other wxs generated by heat.exe . I tried adding -platform x64 and -platform win64 to the calls to heat.exe , but it made no difference. I read https://msdn.microsoft.com/en-us/library/gg513929.aspx The section on 64 bit installer in the Wix Cookbook How

C/C++ returning struct by value under the hood

阅读更多关于 C/C++ returning struct by value under the hood

(This question is specific to my machine's architecture and calling conventions, Windows x86_64) I don't exactly remember where I had read this, or if I had recalled it correctly, but I had heard that, when a function should return some struct or object by value, it will either stuff it in rax (if the object can fit in the register width of 64 bits) or be passed a pointer to where the resulting object would be (I'm guessing allocated in the calling function's stack frame) in rcx , where it would do all the usual initialization, and then a mov rax, rcx for the return trip. That is, something

Executing 32bit and 64bit mshta.exe (bypass default handler)

阅读更多关于 Executing 32bit and 64bit mshta.exe (bypass default handler)

I'd like to be able to launch a page.hta in 32bit and 64bit versions of the mshta.exe. Create the file c:\page.hta <body onclick="if(confirm('Close? (onclick)')){self.close();}"> <h1>Test Page</h1> <script type="text/javascript"> var elem = [ "UserAgent="+window.navigator.userAgent, "Platform="+window.navigator.platform ]; var taBegin = "<textarea style='width:100%' rows='"+((elem.length+1)*1.5)+"'>"; var taEnd = "</textarea>"; document.write(taBegin+elem.join("\n")+taEnd); </script> </body> Now here is the batch file to attemp to load the page differently. @echo off rem Launch 32bit c:

Write large file

阅读更多关于 Write large file

问题 I try to write to a large file, but it seems like it does not work for files larger than 2GB. I have tried with boost::iostreams::file_sink. Is this just a limit with the boost stream? Is there some other way I can write a large file on Win64 and win32? 回答1: This depends on: The file system which you're using. Old file systems like FAT allow only files up to 2GB. Use NTFS. Your library must be compiled to allow large files (64bit seek offsets). If they use 32bit ints to seek in file (check

x64 calling convention (stack) and varargs

阅读更多关于 x64 calling convention (stack) and varargs

I've read Microsoft's documentation , but the scheme is so awkward, I thought I'd double-check to make sure I'm understanding it correctly... My understanding is the generic method by which parameters are passed is this: --- bottom of stack --- (return address) [shadow space for arg 1] [shadow space for arg 2] [shadow space for arg 3] [shadow space for arg 4] arg N arg N - 1 arg N - 2 ... arg 6 arg 5 ---- top of stack ----- It seems so awkward when implementing va_arg and such... is this actually correct? Raymond Chen The correct diagram is --- Bottom of stack --- RSP + size (higher addresses)

psql: FATAL: password authentication failed for user windows 8

阅读更多关于 psql: FATAL: password authentication failed for user windows 8

I installed postgresql on windows and while the installation it asks to make a user for the account.This made a new windows user in my computer called postgres, I have created a password for it as well. Now I want to run psql on windows command line, it asks for a password (without mentioning the user) and always gives me back the error: psql: FATAL: password authentication failed for user "Ash". Even though I have put my accounts password many times. using pgadmin I changed the user "postgres" to "Ash" but I have yet to remake the password. I followed the steps here: I forgot the password I

Unresolved external symbols in compiling 32 bit application in Windows 64

阅读更多关于 Unresolved external symbols in compiling 32 bit application in Windows 64

问题 So I am trying to compile legacy app from 32 bit to 64 bit.. I re-compiled all of the libs it used and made it look into WIN SDK6.0A x64 bit for libs.. I am using: Visual Studio Professional Edition 2008 Visual C++ dotNet Framework 3.5 SP1 Windows Server 2008R2 Windows SDK is 6.0A Everythings finally coming up but I am getting these weird undefined symbol errors: error LNK2019: unresolved external symbol InterlockedDecrement referenced in function ... error LNK2019: unresolved external symbol

How do I make a 64 bit MSI?

阅读更多关于 How do I make a 64 bit MSI?

I've specified: -arch x64 when running candle.exe . Platform=x64 on the Package . ProgramFiles64Folder as the Directory id where things get installed. and still, when the app gets installed, it goes to C:\Program Files (x86) . There are some other wxs generated by heat.exe . I tried adding -platform x64 and -platform win64 to the calls to heat.exe , but it made no difference. I read https://msdn.microsoft.com/en-us/library/gg513929.aspx The section on 64 bit installer in the Wix Cookbook How do I get WiX to generate a 64-bit MSI? and I think I'm doing everything that was described there. What

What's an alternative to GWL_USERDATA for storing an object pointer?

阅读更多关于 What's an alternative to GWL_USERDATA for storing an object pointer?

问题 In the Windows applications I work on, we have a custom framework that sits directly above Win32 (don't ask). When we create a window, our normal practice is to put this in the window's user data area via SetWindowLong(hwnd, GWL_USERDATA, this) , which allows us to have an MFC-like callback or a tightly integrated WndProc , depending. The problem is that this will not work on Win64, since LONG is only 32-bits wide. What's a better solution to this problem that works on both 32- and 64-bit

MySQL ODBC 32 vs 64 bit

阅读更多关于 MySQL ODBC 32 vs 64 bit

I have a 32-bit application that must run on a Windows x64 server using a 64-bit version of MySQL. Should I use a 32-bit ODBC driver or a 64-bit ODBC driver? Or should I install a 32-bit version of MySQL too? Justin Gregoire You would need to install a 32-bit SQL and ODBC driver seeing as how your application is in 32-bit. For compatibility reasons. I am still searching, will edit. ** EDIT To work around this problem, use the appropriate version of the ODBC Administrator tool. If you build and then run an application as a 32-bit application on a 64-bit operating system, you must create the