I have the download for MASM32 Version 8 on 2 sites that are referred from my own site at www.masm32.com.
One is in the US and the other is in France. When I can contact a few of the other people who have been kind enough to help with the bandwidth, I will change the links to the other sites as well.
The new version has put together a lot of different things that have been done over the last year or so and it should be useful to programmers who are interested in writing MASM code.
1. Vladimir Kim's latest VKdebug.
2. Ray Filiatreault's new FP library.
3. Ernie Murphy's extra image handling procedures as library modules.
4. The latest version of Quick Editor with scripting support and improved display capacity while not requiring fancy graphic cards.
5. A new system for directly coding dialogs that don't require a dialog editor.
6. WINDOWS.INC 1.25e with corrections and additional equates for common controls.
7. New utilities for creating include files from libraries and creating libraries from include files.
8. Additional example code and examples for the new dialog system.
9. A number of scripts already set up in Quick Editor including simple wizards for dialogs.
10. Updated help files for the MASM32 library and a new help file for the dialog system for fast and easy reference.
I hope the new version is useful to assembler programmers.
Regards,
hutch@movsd.com
One is in the US and the other is in France. When I can contact a few of the other people who have been kind enough to help with the bandwidth, I will change the links to the other sites as well.
The new version has put together a lot of different things that have been done over the last year or so and it should be useful to programmers who are interested in writing MASM code.
1. Vladimir Kim's latest VKdebug.
2. Ray Filiatreault's new FP library.
3. Ernie Murphy's extra image handling procedures as library modules.
4. The latest version of Quick Editor with scripting support and improved display capacity while not requiring fancy graphic cards.
5. A new system for directly coding dialogs that don't require a dialog editor.
6. WINDOWS.INC 1.25e with corrections and additional equates for common controls.
7. New utilities for creating include files from libraries and creating libraries from include files.
8. Additional example code and examples for the new dialog system.
9. A number of scripts already set up in Quick Editor including simple wizards for dialogs.
10. Updated help files for the MASM32 library and a new help file for the dialog system for fast and easy reference.
I hope the new version is useful to assembler programmers.
Regards,
hutch@movsd.com
thanks hutch, btw, is the size was about 3MB? if i'm not forgot, the ver7 was about 5MB??
Thanks Hutch for uploading masm8
amr
amr
woohoo ! :grin:
The most interesting new
Hoping more source code to read. :) . Thank you very much for always successful assembling.
Hoping more source code to read. :) . Thank you very much for always successful assembling.
woohoo ! :grin:
Hutch,many thanks for the new version! :alright: :alright: :alright:
Regards,
Vortex
Regards,
Vortex
I like the way dialogboxes work. They help me with solving a lot of problems. Great work.
Best of regards.
Best of regards.
Thank for MASM32 Version 8 et merci beaucoup for all the help I got from you :grin:
I'm getting a number of errors installing MASM V8 on both my PCs:
[*]On my P1 166 MHz laptop running Win98se: assorted errors, which may be because of 584 k of free conventional memory - I'll have to setup memmaker again to install V8 and will get back with you.
[*]On my Athlon 1.4 MHz running Win2k Sp3: there seems to be an error in strmbasd.asm?
Assembling: strmbasd.asm
strmbasd.asm(9) : error A2008: syntax error : =
strmbasd.asm(11) : error A2008: syntax error : =
strmbasd.asm(12) : error A2008: syntax error : =
strmbasd.asm(14) : error A2008: syntax error : =
Microsoft (R) Incremental Linker Version 5.12.8078
Copyright (C) Microsoft Corp 1992-1998. All rights reserved.
LINK : fatal error LNK1181: cannot open input file "strmbasd.obj"
I dl'ed it this morning (local time, CET),but I haven't had time to start windows, yet, I think it's great that the next version is here :)
Masmer,
I tracked down strmbasd.asm and it is a library that is built from the include file of the same name.
Open up strmbasd.inc and delete out the first two lines that have the illegal characters in it. On everything I tested the install on the library built OK so let me know if the library built by default on your machines or if it failed on that build.
STRMBASD.LIB
Regards,
hutch@movsd.com
I tracked down strmbasd.asm and it is a library that is built from the include file of the same name.
Open up strmbasd.inc and delete out the first two lines that have the illegal characters in it. On everything I tested the install on the library built OK so let me know if the library built by default on your machines or if it failed on that build.
STRMBASD.LIB
Regards,
hutch@movsd.com
It had failed to build STRMBASD.LIB, but it did build strmbase.lib.
But upon commenting out
;!= PROTO :DWORD,:DWORD
;== PROTO :DWORD,:DWORD
and running makelibs.bat, the strmbasd.lib was built. Thank you.
=============================================
My P166 Win98 laptop was still reporting errors during the make phase of installation. It started with public should be declared private (or was it the other way around?) messages and towards the end it reported that there wasn't enough (conventional) memory to build some things.
I have VC++ 6 SP5 installed on this PC, and I'll have to rem out some of the bin/lib/include paths as that's probably part of the problem - I'll work on that after I sleep and get home from work. Would keeping the MASM path before the VC++ paths fix problems or should I just run VCVARS32.BAT when I wish to compile C programs via the command line?
BTW, even without VC++ 6 installed, I would receive out-of-memory errors in Win9x with MASM32 V7 on several different PCs.
I ended up copying the entire Masm32 V8 directory from my Athlon to my laptop and have been playing around with it.
PS: I got the book "IBM PC Assembly Language And Programming" by Peter Abel in the mail today and have been reading it. It's a nice 16-bit text book to work though.
But upon commenting out
;!= PROTO :DWORD,:DWORD
;== PROTO :DWORD,:DWORD
and running makelibs.bat, the strmbasd.lib was built. Thank you.
=============================================
My P166 Win98 laptop was still reporting errors during the make phase of installation. It started with public should be declared private (or was it the other way around?) messages and towards the end it reported that there wasn't enough (conventional) memory to build some things.
I have VC++ 6 SP5 installed on this PC, and I'll have to rem out some of the bin/lib/include paths as that's probably part of the problem - I'll work on that after I sleep and get home from work. Would keeping the MASM path before the VC++ paths fix problems or should I just run VCVARS32.BAT when I wish to compile C programs via the command line?
BTW, even without VC++ 6 installed, I would receive out-of-memory errors in Win9x with MASM32 V7 on several different PCs.
I ended up copying the entire Masm32 V8 directory from my Athlon to my laptop and have been playing around with it.
PS: I got the book "IBM PC Assembly Language And Programming" by Peter Abel in the mail today and have been reading it. It's a nice 16-bit text book to work though.
Don't lose any sleep over the warnings about internal functions needing to be private, it does not effect the build. It is based on procedures that start with DLL****. I had the choice of filtering this out with the utility that does the libraries but it involved risks of missing other IMPORT functions so I did not bother.
Out of conventional memory errors are from your setup in DOS. If you set up win95/b/98/se properly, you should get 624k of memory in DOS.
Make sure you use the NOEMS option in emm386.exe and it will probably help if you use the range exclusion i=B000-B7FF as well as this will give you enough upper memory to load everything you normally use as HIGH.
The rest is using LH in the autoexec.bat for things like mouse drivers and the like so that you end up with the maximum in DOS memory.
Regards,
hutch@movsd.com
Out of conventional memory errors are from your setup in DOS. If you set up win95/b/98/se properly, you should get 624k of memory in DOS.
Make sure you use the NOEMS option in emm386.exe and it will probably help if you use the range exclusion i=B000-B7FF as well as this will give you enough upper memory to load everything you normally use as HIGH.
The rest is using LH in the autoexec.bat for things like mouse drivers and the like so that you end up with the maximum in DOS memory.
Regards,
hutch@movsd.com
Yesss, finally :-)
Just a quick error report: for installations on both WinME and Win2k SP3, I found three of the batch files in \MASM32\BIN to be unusable (DASM.BAT, DASMD.BAT, and BRES.BAT). It should be easy to replace them with the .BAT files from the v7 distribution, so don't delete that one too quickly :-)
Regards, Frank
Just a quick error report: for installations on both WinME and Win2k SP3, I found three of the batch files in \MASM32\BIN to be unusable (DASM.BAT, DASMD.BAT, and BRES.BAT). It should be easy to replace them with the .BAT files from the v7 distribution, so don't delete that one too quickly :-)
Regards, Frank
Great new package!! :)
However I have a problem with the new quick-editor:
Every time I type the @-symbol, ( Alt Gr + 2 on my keyboard ) I get a messagebox with the caption
'No text selected' and the text 'Please select a block of text first'.
However I have a problem with the new quick-editor:
Every time I type the @-symbol, ( Alt Gr + 2 on my keyboard ) I get a messagebox with the caption
'No text selected' and the text 'Please select a block of text first'.
David,
Thanks for the feedback, I have just recently had a similar problem reported on a German keyboard with Ctrl + Q. Can you access the @ character by any other method on the keyboard you are using ?
Frank,
Thanks for finding these, there has been some binary overwrite of the files and I missed them as it is in the image I set up for the installation. They should be identical to the ones from version 7.00
Regards,
hutch@movsd.com
Thanks for the feedback, I have just recently had a similar problem reported on a German keyboard with Ctrl + Q. Can you access the @ character by any other method on the keyboard you are using ?
Frank,
Thanks for finding these, there has been some binary overwrite of the files and I missed them as it is in the image I set up for the installation. They should be identical to the ones from version 7.00
Regards,
hutch@movsd.com
hutch ->
Pity, no that's the only way to type it as I know of.
There is the same messagebox when typing these two signs as well:
$ ( alt gr + 4 )
[ (alt gr + 8 )
Pity, no that's the only way to type it as I know of.
There is the same messagebox when typing these two signs as well:
$ ( alt gr + 4 )
[ (alt gr + 8 )
David,
Thanks for testing this for me, it looks like I will have to do a modified version of QE for European keyboards by disabling the hotkeys that are hard coded into the editor.
Regards,
hutch@movsd.com
Thanks for testing this for me, it looks like I will have to do a modified version of QE for European keyboards by disabling the hotkeys that are hard coded into the editor.
Regards,
hutch@movsd.com
I have VC++ 6 SP5 installed on this PC, and I'll have to rem out some of the bin/lib/include paths as that's probably part of the problem - I'll work on that after I sleep and get home from work. Would keeping the MASM path before the VC++ paths fix problems or should I just run VCVARS32.BAT when I wish to compile C programs via the command line?
I have VS6 and VS.Net and MASM7 all installed on the same machine, and have no issues, i have my MASM paths listed first in the envvars. This *would* affect me if i was doing any C++ developing (which i'm not), in that case i would make sure i have no conflicting names between libaries and includes from each system, and only one instance of any biaries (link.exe, etc.)
hutch,
great job, although it will be a while before i upgrade as i am still happy with v7 ;)