I'm just curious...Why does MASM32 v10 use MASM v6.14.8444 when Microsoft is at v8 or v9? Is it a licensing issue, compatability reasons, or something else?
license.
Perhaps a little short as explain.
The iczelion site give the 6.15 version (really better than the 6.14).
Why not put the 6.15 in the masm32 package ?.
licence. :bg
So if I have a legitimate copy of the newer versions of ml, link, lib, etc., can I put them in \masm32\bin and use them? Will it break anything, and does it really matter?
i use a patched version of 6.15
i haven't needed to use one of the newer ones yet, but i don't use some of the syntax that others do
i haven't ran into anything that will not assemble that was written by others
i think they will all work with masm32 (6.14 +, that is)
scolby33,
ML version 9.0 works fine. You can get it directly from Microsoft with one of their VC downloads.
debug information will not be compatible with link.exe
Yes,
Drizz is right, to use debug info you will have to use the linker in the VC version that ML 9.0 comes with.
Work with further versions of ml can be done using further environments.
----------- Just write your code without paths for the include and library files --------------------
Doing that , you can use any versions of ml (vc++,ddk ...) and any versions of the libraries.
The ml 6.15 take place in the masm32 package.
The differents version of ml couldn't be placed anywhere.A old linker (masm32) couldn't work with ml 9.0 in debug version.
Quote
ERROR MESSAGE : Link : Incorrect pdb files
Only build in release versions can mix new ml and old linker or new linker and old ml.
Hi ToutEnMasm,
QuoteThe ml 6.15 take place in the masm32 package
It's V6.14 coming with the Masm32 installation.
i got version 6.15 from Iczelion's d/l page
there is also a minor patch there
i applied the patch, but promethee puts a line of text in there that messes up the screen
so, i patched the patch to eliminate the line
http://win32assembly.online.fr/download.html
the patched patched 6.15
http://www.4shared.com/file/-QIUp-BF/ml615.html
EDIT - updated the files and the link, 6-17-2010
:bg
When Microsoft come looking for the poster of a patch that illegally alters their software, can I point them to you ?
well, i was thinking they were too busy with the EU to worry about a patch that fixes their bug on masm 6.15 - lol
but, you can point them at promethee and Iczelion, as well
if they sue me, they will end up with less money than they have now, not more - lol
i will just explain that i am under mental duress due to the economy
When I was using masm, my ml.exe was a renamed jwasm.exe :green2
Version 6.14 coming with the Masm32 download is fine for most purposes but lacks SSE support. The MasmBasic (http://www.masm32.com/board/index.php?topic=12460) library, for example,is SSE2 and therefore needs 6.15 upwards or, alternatively, JWasm (http://www.japheth.de/JWasm.html). The latter is free of licence problems and a lot faster than ml but occasionally has little problems with error line reporting and highly complex macros. Many people here use JWasm for speedy development but keep a copy of ml in case they have debugging trouble.
ml.exe version 6.15 originally came with the Visual C++ 6.0 Processor Pack.