MASM32 Version 11 Release posted.

[dedndave]

there is a point during the installation where a message comes up and warns about running other processes during LIB build
that would seem to be a perfect time to substitute the linker with a newer version, if desired   :U
(or any other modifications)

[hutch--]

 :bg

One thing you don't do with an installation is build in a method for it to fail. If anyone wants to try building the import libraries with another linker, they can do it AFTER the install is finished.

[MichaelW]

IIABDFI

[dedndave]

yah - my dad tried for many years to teach me that
that's how i became an engineer   :bg

for shits and giggles, i just tried it out
when the "Build Libraries" message box came up, i deleted link.exe and lib.exe from the masm32\bin folder
then, i copied link.exe, lib.exe, and mspdb80.dll from masm version 9.00.30729.01 into that folder and clicked "OK"
it built the libraries just fine   :U

so, for all you nay-sayers, i say, "poop to that!"   :lol

[GregL]

Hutch,

That's fine with me.  If you would like, I'll post the updated file and an explanation of the change.

[Edit] I see you already posted it.  Thank you.

[hutch--]

 :bg

> so, for all you nay-sayers, i say, "poop to that!"

Here is a man who has not had to explain a million or so times that the early versions had to be put in the MASM32 directory, not the MASM directory. Then there were the problems of so many people trying to run the install as a background process and wondered why the libraries did not always build correctly, then there were those who thought something was wrong when they used the wrong version of LINK that defaulted to a much larger section size and their minimum sized EXE was 16k and so on and so on etc etc etc .......

Add to this those folks who try and run a development computer that is set up like a domestic PC with all of its OS settings and a free crappy AV scanner that silently deleted some files as they were installed or displayed messages that something in the install had GENERIC ###(who gives a PHUK) trojan in it and you will understand why you write an installation that is PHUKUP proof and even then someone will find a way to mess it up.  :P

[dedndave]

 :P
i have never had any of those problems, Hutch - lol
of course, i know how to close other processes, set environment variables, and avoid shitty av scanners, too   :bg

my feeling is - if you can't get past that stuff, then assembler may not be the language for you, anyways

[xandaz]

    Lol hutch. The AV thing happened to me once, with AVG. Deleted all the masm examples, plus iczellions tutes and some .EXEs from \bin.

[dedndave]

i was all excited to see that there were a bunch of new examples added to this version
still am excited - just not as much - lol

i noticed that there was ~20 MB in the Bill Cravener folder   :dance:
then, i noticed that 15 MB of that is in .LST files   :'(

you may not have intended to include those

append
calendar
controls

EDIT:
i also see that there is a "wininc.inc" file in the "examples\unicode_generic\diskfile" folder - 873 KB
and a "winequ.inc" file in the "examples\advanced\wrep" folder - 402 KB
they don't appear to be used for anything

[hutch--]

I am the guilty party here. i did not take notice that Bills examples used a LST file and after testing the entire example set after every major change to the WINDOWS.INC file its easy enough to forget to clean out the mess.

LATER : remove the LST files and the build drops by half a meg. Must keep that in mind for any updates.  :bg

[dedndave]

i went to Search for *.* on the masm32 folder, then ordered the list by size
skipping over the desired EXE's, INC's, etc by folder - the boggies pop out like a sore thumb   :P

[Bill Cravener]

No Steve that's entirely my fault. One asks for forgiveness. There are times when I have to track down an error in one of my creations and when one has a PC with room to spare one doesn't give any thought in removing the need for the lst file after the error has been tracked down. One will have to start checking that one has removed the /Fl command from the build file from here on before one zips up the files. One can easily overlook this when one is a bit too buzzed when one is having so much fun when one is putting an example together. One is now going to go pour himself. . .well. . .another one!

[vanjast]

Niiiiccccce.... installed like a dream  :U
Playtime...  :bg

[Howard]

Hi guys

Not sure what's wrong here - I can only find the v10 - have downloaded it twice. The link from Hutch's first message goes to the v11 announcement (no download links there), selecting 'Download' on the toolbar says 'MASM32 Version 10 Downloads' and the file from any of the sites is m32v10r.zip. Suggestions?

Thanks
Howard

[dedndave]

http://masm32.com/masmdl.htm