Getting ML64

[caballero]

Hello. Any way to obtain ML64 without the need of install any garbage like visual studio etc?

[TWell]

If you have iso image or disk, extract it from msi/cab-file.
 Visual C++ Build Tools 2015 have it too.
With /layout option you can download install packages (Win 7 SP1 ->).

[caballero]

Thank you TWell, but this executable gave me a .net version error. I've just gotten from  here with the help of 7zip. Though I don't have yet link64, maybe I should use any other linker :icon_rolleyes:

[User_1960]

Hello
This is a two month old post but if you still want an answer ...

Asking for ML64.EXE means that you are targeting 64-bit editions of Windows - right ?
Then comes a question, are you using 32-bit or 64-bit edition of Windows ?
Also, for LINK64.EXE, this is another thing. Read further down.

In any case, Visual Studio 2015 Community Edition has ML??.EXE and LINKxx.EXE for any case.
There are 4 cases, where one has to distinguish between the operating system edition in use, I will call it the HOST OS, and the operating system targeted by the Assembly-Link process - I will call it the TARGET OS.

If you have the .ISO here is a list :

HOST OS 32bit - TARGET OS 32bit:
-------------------------------------------
ml.exe_1uYfHxlp75MEqUGG1Z1ezUgRcAA_x86
Size : 447120 Bytes
File version : 14.00.23506.0
In /Packages/VisualC_D14/VC_Tools.X86.Nat/cab1.cab

HOST OS 32bit - TARGET OS 64bit:
-------------------------------------------
ml64.exe_JHpXkUI_sP3g15MVHwWO10gjYzo_x86
Size : 401552 Bytes
File version : 14.00.23506.0
In /Packages/VisualC_D14/VC_Tools.X86.X64/cab1.cab

HOST OS 64bit - TARGET OS 32bit:
ml.exe_H18MkSlNhEBm0k4RbA9TyUc2BSQ_x86
Size : 579216 Bytes
File version : 14.00.23506.0
In /Packages/VisualC_D14/VC_Tools.X64.X86/cab1.cab

HOST OS 64bit - TARGET OS 64bit:
ml64.exe__KsGyXB1mrE_Ah3fibPFNGDezSo_x86
Size : 526488
File Version : 14.00.23506.0
In /Packages/VisualC_D14/VC_Tools.X64.Nat/cab1.cab

LINK.EXE
=======
As for the linker, there is NO LINK64.EXE. I assume your question is for a linker producing 64bit executables, and if I so, the answer is it is the same program. It depends on the /MACHINE:xxxxx switch :

/MACHINE:{ARM|ARM64|EBC|X64|X86}

That said, these are the versions of LINK.EXE :

HOST OS 32bit :
--------------------
link.exe_fau8ANs.ZiZ9utwPB5Mt0eFdioI_x86
Size :
File Version :
In : /packages/VisualC_D14/VC_Tools.X86.X64/cab1.cab

HOST OS 64bit :
--------------------
link.exe_A0rWXUBJyxR68pl9kNoJpuCBkCM_x86
Size :
File Version :
In : /packages/VisualC_D14/VC_Tools.X64.X86/cab1.cab

[User_1960]

 :icon_redface: Sorry for the omissions and the wrong path in the previous post  :icon_redface:

LINK.EXE :

HOST OS 32bit :
--------------------
link.exe_fau8ANs.ZiZ9utwPB5Mt0eFdioI_x86
Size : 982312
File Version : 14.00.23506.0
In : /packages/VisualC_D14/VC_Tools.X86.X64/cab1.cab

HOST OS 64bit :
--------------------
link.exe_A0rWXUBJyxR68pl9kNoJpuCBkCM_x86
Size : 1143592
File Version : 14.00.23506.0
In : /packages/VisualC_D14/VC_Tools.X64.ARM/cab1.cab

[K_F]

Why the F.. does MS hide this stuff...

Thanks SameAge
 

[Vortex]

Why the F.. does MS hide this stuff...

Thanks SameAge
 

They try to keep away people from the assembly language.

[User_1960]

Why the F.. does MS hide this stuff...

Thanks SameAge
 

They try to keep away people from the assembly language.

You are partly right, Vortex
They are trying to turn people to other "technologies" eg .NET, *# etc.
Else, they will stop selling training, certifications and all that stuff to "MS Certified" ones. It's a big business to abandon.
If anyone had to stop thinking of Classes, Sub-classing, Constructors, Destructors, Member-Functions and all the other haut-parlance, where would their prestige, and, subsequently, MS business would stand ?

[jj2007]

If anyone had to stop thinking of Classes, Sub-classing, Constructors, Destructors, Member-Functions and all the other haut-parlance, where would their prestige, and, subsequently, MS business would stand ?

You might like the rant part here. But beware of qWord, he might eat you alive 8)

[User_1960]

If anyone had to stop thinking of Classes, Sub-classing, Constructors, Destructors, Member-Functions and all the other haut-parlance, where would their prestige, and, subsequently, MS business would stand ?

You might like the rant part here. But beware of qWord, he might eat you alive 8)

I bet he won't as long as the censuring  of the site allows me to log in

[User_1960]

And, by the way - or BTW - if you prefer, I talk about Assembly, not what some could say is assembly  ...

[qWord]

be happy, I'm not hungry.

[User_1960]

be happy, I'm not hungry.

??? where are the fried chicken ?

[hutch--]

 

I have terrible news for any that don't know, API code is C/C++ code, much the reason why I deal with it as any other high level code. If you are ever going to do something useful in assembler, it is done at the algorithm level in crude Intel mnemonics, the rest is padding and packaging.  :P