Installing the Masm64 SDK

[NoCforMe]

I still prefer 32-bit assembler, but this is a good tool to have.

Oh, me too. 

I know that 64-bit is the future and wanted to look at 64-bit assembly for that reason, but then I saw how parmarea works and how much more complicated the code looks and noped. :D

Yepper.

Take my advice and stick with 32-bit code.
64-bit is total overkill for 90% of applications. No, make that 95%.
Plus it is a pain in the ass to deal with.
Plus our 64-bit package is sadly deficient, as everyone here will tell you.

(The only real advantage I can see is that you get a lot more general-purpose registers to play with.)

[zedd]

Take my advice and stick with 32-bit code.
64-bit is total overkill for 90% of applications. No, make that 95%.
Plus it is a pain in the ass to deal with.
Plus our 64-bit package is sadly deficient, as everyone here will tell you.

(The only real advantage I can see is that you get a lot more general-purpose registers to play with.)

I stole this quote from someone else here (slightly modified)...
"This type of bitching, and sniping is what made me quit the forum before."


But seriously.. as there are more and more users here programming in 64 bit, it is nice to have a Masm64 SDK setup on your machine. This way you can help others with problems with their code.

That is how I mainly use ml64 anymore, aside from simple tests in 64 bit for other members like the one I posted today.

I did give 64 bit an earnest try, but I too stick with 32 for the most part. But I do not knock anyone for wanting to program in 64 bit, or dissuade them from learning it.

[NoCforMe]

Take my advice and stick with 32-bit code.
64-bit is total overkill for 90% of applications. No, make that 95%.
Plus it is a pain in the ass to deal with.
Plus our 64-bit package is sadly deficient, as everyone here will tell you.

(The only real advantage I can see is that you get a lot more general-purpose registers to play with.)

I stole this quote from someone else here (slightly modified)...
"This type of bitching, and sniping is what made me quit the forum before."


But seriously.. as there are more and more users here programming in 64 bit, it is nice to have a Masm64 SDK setup on your machine. This way you can help others with problems with their code.

That is how I mainly use ml64 anymore, aside from simple tests in 64 bit for other members like the one I posted today.

I did give 64 bit an earnest try, but I too stick with 32 for the most part. But I do not knock anyone for wanting to program in 64 bit, or dissuade them from learning it.

So what, exactly, is your point here, Zedd?
Are you politely trying to tell me to STFU?
If so, then no.

How is this remotely "bitching and sniping"?
I cast aspersion on nobody here.
Just giving my opinion, FWIW, on the use of 64-bit MASM (and the state of our package, which everyone knows is not very good).

Sheesh.

[zedd]

No. Just saying that 64 bit is sometimes useful to have/use. 

Nevermind the stolen quote, I was pretty much yanking your chain there.   

[NoCforMe]

Nevermind the stolen quote, I was pretty much yanking your chain there.   

Well, in case you were wondering, you succeeded.
Those stupid emojis don't make it any better, BTW.

[zedd]

You and your stupid emojis ...

[Quin]

Take my advice and stick with 32-bit code.
64-bit is total overkill for 90% of applications. No, make that 95%.
Plus it is a pain in the ass to deal with.
Plus our 64-bit package is sadly deficient, as everyone here will tell you.

(The only real advantage I can see is that you get a lot more general-purpose registers to play with.)

You get more general-purpose registers and can access the computer's entire address space (128 GB in my case) instead of just 2 GB. In practice, you almost never need that, though, and if you do, I'll assume you're an Electron app 
Windows 11 is now shipping only in 64-bit though, but I don't see 32-bit compatibility going anywhere in the next decade at the very least.

[Quin]

Nevermind the stolen quote, I was pretty much yanking your chain there.   

Well, in case you were wondering, you succeeded.
Those stupid emojis don't make it any better, BTW.

You tell people exactly how to antagonize you...and then get surprised when they do. 

[NoCforMe]

Nevermind the stolen quote, I was pretty much yanking your chain there.   

Well, in case you were wondering, you succeeded.
Those stupid emojis don't make it any better, BTW.

You tell people exactly how to antagonize you...and then get surprised when they do. 

Nope, no surprise here.

[sinsi]

I stole this quote from someone else here (slightly modified)...
"This type of bitching, and sniping is what made me quit the forum before."

[Quin]

Nope, no surprise here.

Well, you know what they say about throwing a rock and then hiding your hand...

[jj2007]

You and your stupid emojis ...

I can echo that

[Quan]

Hi, I'm having problems with installing and assembling with the MASM64 SDK. I believe I've followed all of the instructions in the message at the top of this thread. However, when I opened qeditor.exe, pasted in a piece of code I found here (whose include directory I have changed from "masm32\include64\masm64rt.inc" to "masm64\include64\masm64rt.inc") and then clicked on Project -> Assemble 64-bit Module, I receive this error.


I also tried again with teditor.exe and clicking on Assemble 64-bit Module triggered nothing. So I'm not sure if I did something wrong and which editor I'm supposed to use to make it work.

I also found the file \masm64\bin64\FileList.txt which seems to contain all of the files I need to put in the bin64 folder, which kinda goes against this in the original post.

The only additional ingredient you need is ml64.exe

So do I need those other files in FileList.txt, e.g. link.exe, cvtres.exe, dumpbin.exe, or is that optional?  I'm using a low-end laptop at work right now so I'd prefer to find other methods to install the Microsoft binaries. But so far none of the resources I've found in this forum worked for me.

I'd appreciate any help to make my installation works.

[Quan]

Funny because I've always told people to complain and everything will fall into place, and it kinda did this time, just a little bit after I sent that cry for help. 

To preface, I also did try out jj's GrabBin64.exe but got another error which I also mentioned underneath. So I got a friend of mine who has Visual Studio installed and to send me the files from FileList.txt. Copying the files over and assemble the programme seem to have fixed both of those errors on my computer.

However, there might still be some problems with my linker. Assembling the programme returns an .obj file but not a .exe file. There was no error message that popped up in a message box or appeared in the command prompt, so I'm still stuck here.


I'm not exactly sure how to link an .obj file to create an .exe file either so that could also be a workaround for me. If anyone can show me how, or point out what went wrong with my installation that would be great.

Oh and this is with qeditor.exe, while teditor.exe remains unresponsive as before.

Thanks y'all

[TimoVJL]

jj's download system don't even download 1033 resources.

Dependency Walker is good tool to check applications.