Upgrading MASM 6.14 to MASM 7.00etc

[MazeGen]

If is someone interested, I just discovered minor ML VS2005 beta2 bug:

http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?FeedbackID=FDBK32754

[MazeGen]

Got one new annoying bug:

http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackId=FDBK37281

[GregL]

OceanJeff32,

Regarding your original post:

Another way to do it is to just change the paths in the editor or IDE you are using to the version of ML and LINK you want to use. That way you can keep both versions in separate directories. I was able to copy ML.EXE and ML.ERR 6.15 into the MASM32\BIN directory and it works fine. With ML 7.10 I leave it in the Visual C directory and change the paths in the IDE or editor to point to it.

[GregL]

Something I had problems with, and finally figured out. I want to pass it along:

Visual Studio 6.x and Visual Studio 7.x have different formats for debug information. Visual Studio 7.x can handle 6.x debug info, but Visual Studio 6.x can not handle 7.x debug info. So, ML 6.x and ML 7.x output differently formatted debug information. If you use Visual Studio 6.x you need to use ML and LINK 6.x, if you use Visual Studio 7.x you need to use ML and LINK 7.x. Don't mix versions.

All this applies to CL (the C compiler) as well.

Pelle's C uses the 6.x debug format, and can not handle the 7.x debug format, so you should use ML 6.x with Pelle's C.

Visual Studio 8.x has yet another new format for debug information.  :dazzled: