I have added additional macros to the main macro file, there are some new library modules and the documentation has been upgraded to match. As per suggestion I have rewritten the register preservation section that used to be in the MASMLIB help file in the ASMINTRO help file. I have also added a couple of new examples in the example code.
http://www.website.masmforum.com/masm32/m32beta9.zip
This version is reasonably close to release so any feedback will be welcome to catch the bits and piece that I may have missed.
I haven't downloaded it yet, but isn't there already a register preservation section in the ASMINTRO help file? A much more complete one than in the MASMLIB help file?
No, I wrote the current one about 2 days ago. The MASMLIB help file had to be broken up as it was unmaintainable and the area of register preservation needed to be written somewhere else.
Hutch,
I installed 9.00 beta and assembled a few programs with it, so far so good.
Thanks Hutch, I will try the latest release :U
why there are still old compiler and linker? there are newer versions. isnt it allowed to add them to the masm package?
http://rapidshare.de/files/8763661/Bin7.0.9466.rar.html
Quote from: diablo2oo2 on December 07, 2005, 03:16:38 PM
why there are still old compiler and linker? there are newer versions. isnt it allowed to add them to the masm package?
Concerning the package, you cannot include other versions of the assembler and linker according to the licesing documents. Check the
C:\masm32\licence directory.
diablo2oo2,
There are later versions of ML but licencing is specific to what you are allowed to distribute. A later version of ML would be OK but it is only for those that are writing SSE2. The linker is the version I want for MASM but note that the project includes Pelle's linker which is a later design high performance tool.
Thanks Hutch: 9.00b works fine for me; I just tried it with some of my programs. :U
*ps: will there be a example for using UNICODE API in the future?
... generated warnings in /include such as
Assembling: adme.asm
Microsoft (R) Incremental Linker Version 5.12.8078
Copyright (C) Microsoft Corp 1992-1998. All rights reserved.
adme.def : warning LNK4104: export of symbol "DllRegisterServer" should be PRIVATE
adme.def : warning LNK4104: export of symbol "DllUnregisterServer" should be PRIVATE
, on Win98...and overall did not configure and suggested run the .bat's again.
You can safely ignore the warnings.
The build failure is usually associated with OS installation damage or viral damage. When I have this in release form I will post a seperate version as an archive for the odd machines that have problems.
Version 9.00 beta works fine :U
All my masm project assemble voila! :U
Works great!!!!
thanx Hutch, try it within the next few days. i wait final version of MASM 9.0 :))
hutch i know i can add it alone, but you are project admin so can you add to masm32 DebugActiveProcessStop and EXCEPTION_GUARD_PAGE EQU 080000001h
so it can be standarized inside masm?
because masm32 becomes really outdated and xp is standard today.
Quotebecause masm32 becomes really outdated
Hutch is updating regulary the masm32 package. What are you talking about?
well its outdated for things that come with win xp, like Detach from process, or guard_page exception and many others, good thing would be also add PE exe strcutures etc include, if nobody wants to write it from scratch, pumqara pelib or just edit MSVC++ include. i dont force anyone to do it, it is just mine suggestion. that i think many will apriciate
Quote from: Human on January 06, 2006, 06:24:49 PM
add PE exe strcutures etc include,it
Did you check windows.inc for all those structures below related to the PE format?
IMAGE_DATA_DIRECTORY STRUCT
.
.
IMAGE_DATA_DIRECTORY ENDS
IMAGE_OPTIONAL_HEADER32 STRUCT
.
.
IMAGE_OPTIONAL_HEADER32 ENDS
IMAGE_FILE_HEADER STRUCT
.
.
IMAGE_FILE_HEADER ENDS
IMAGE_NT_HEADERS STRUCT
.
.
IMAGE_NT_HEADERS ENDS
IMAGE_EXPORT_DIRECTORY STRUCT
.
.
IMAGE_EXPORT_DIRECTORY ENDS
IMAGE_DOS_HEADER STRUCT
.
.
IMAGE_DOS_HEADER ENDS
Hutch, if Pelle's assembler pans out to your liking, will you dump MASM for POASM in version 9?
:bg
I am much more interested in the making of history than predicting it.
Hutch,
StrToFloat doesnt preserve some registers esi, ebx, edi
This is old stuff, but still in.
Thanks GM. :U
"making of history"... A bit ambitious, I think... for myself, I will just "live" with history.
Paul
Hi hutch,
In the user32 lib there is a function called FlashWindowEx but this function need a FLASHWINFO structure.
May I suggest this addition to windows.inc
FLASHWINFO STRUCT
cbSize DWORD ?
hwnd DWORD ?
dwFlags DWORD ?
uCount DWORD ?
dwTimeout DWORD ?
FLASHWINFO ENDS
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/flashwinfo_str.asp
Interesting, jdoe.
FLASHW_ALL equ 00000003h ;Flash both the window caption
;and taskbar button.
;This is equivalent to setting
;the FLASHW_CAPTION | FLASHW_TRAY flags.
FLASHW_CAPTION equ 00000001h ;Flash the window caption.
FLASHW_STOP equ 00000000h ;Stop flashing. The system restores the window to its original state.
FLASHW_TIMER equ 00000004h ;Flash continuously, until the FLASHW_STOP flag is set.
FLASHW_TIMERNOFG equ 0000000Ch ;Flash continuously until the window comes to the foreground.
FLASHW_TRAY equ 00000002h ;Flash the taskbar button.
Aaahaa! That's the annoying "blinking-task" "feature" of WinXP which drives me crazy. It must use "FLASHW_TIMERNOFG." Hmm, wonder if it's changable...
Hutch,
The makelib bat produces libs with the name "default.lib", indifferent of the name given the lib in the' bldlib.bat' script.
A problem with the libbat.qsc?
regards,
Rags
Rags,
Thanks, I mised that one. It should have the replacement in the line with LINK inline.
; «««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««
; This script builds a batch file named "makelib.bat" that builds the
; library of the name you choose from the ASM files in the current directory.
; «««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««
yesno Is the current directory where you wish to build your library ?**Create Library Batch File
jmp nxt
exit
nxt:
input Enter your library name with NO extension**default
fcreate makelib.bat
fprint {comment} ------------------------------------------------------------
fprint : This batch file creates a response file for both ML and LINK
fprint {comment} ------------------------------------------------------------
fprint @echo off
fprint cls
fprint echo.
fprint echo ** Assembling {str0}.lib library modules.
fprint echo.
fprint dir /b *.asm > _tmp.rsp
fprint \masm32\bin\ml /c /coff @_tmp.rsp
fprint echo.
fprint echo ** Linking {str0}.lib
fprint echo.
fprint dir /b *.obj > _lnk.rsp
fprint \masm32\bin\link -lib @_lnk.rsp "/out:{str0}.lib"
fprint dir *.lib
fprint del *.obj
fprint del _tmp.rsp
fprint del _lnk.rsp
fprint pause
fclose
msgbox Run MAKELIB.BAT to build the {str0}.lib**Batch file written to disk
<alert comment="masm32 newbie">
Perhaps it is useful to have the beta "dummy checked" .... or at least "newbie checked"
The installation encountered a number of LNK4104 warnings .... they don't mean anything to me, but here is what was reported, and may or may not be meaningful:
adme.def : warning LNK4104: export of symbol "DllRegisterServer" should be PRIVATE
adme.def : warning LNK4104: export of symbol "DllUnregisterServer" should be PRIVATE
dtcuic.def : warning LNK4104: export of symbol "DllGetClassObject" should be PRIVATE
dtcuic.def : warning LNK4104: export of symbol "DllRegisterServer" should be PRIVATE
dtcuic.def : warning LNK4104: export of symbol "DllUnregisterServer" should be PRIVATE
and some more similar to above and below
strmbased.def LNK4104
strmbase.def : warning LNK4104: export of symbol "DllCanUnloadNow" should be PRIVATE
strmbase.def : warning LNK4104: export of symbol "DllGetClassObject" should be PRIVATE
With WinXp-SP2, it seems to otherwise build ok, but right at the very end, I get a Microsoft message box indicating that an error was detected:
"testinst.exe has encountered a problem and needs to close. We are sorry for the inconvenience.
...
Please tell Microsoft about this problem.
Debug? Send Error Report? Don't Send?
The final masm32 windows dialog has appeared when the above warning/error appears:
"Press any key to continue ..." is showing, with "Installation Success" showing.
I wonder if this is related to account privileges or scripting security or Norton SystemWorks?
FWIW, I recall getting these same warnings and final Microsoft warning/error message with Masm32 8.2
</alert>
ld,
You can safely ignore the warnings, if Microsoft did not want the functions exported, they could have kept them as local functions but it does not effect the library build.
I don't know what is happening with the testinst.exe file as it does nothing unusual. It is in a seperate directory off the masm32 installation directory so its easy enough to check if it builds OK. There is almost nothing I can do about additional software that is running that may restrict what happens during an installation. if I had the space, its a lot easier to distribute the entire project with all of the libraries built but its a fair bit larger by doing this.
Minor nits .... this newbie-trying-to-be-helpful 2¢ worth ...
In the file: include\bldlibs.bat
There are references to:
inc2l RESOURCE.h
inc2l INC2L.EXE
inc2l bldlibs.bat
which give warnings because they don't have .inc extension. I suppose this is the result of something like:
dir /b >BldLibs_bat.txt
Perhaps you should use something like:
dir /b *.inc >BldLibs_bat.txt
Also, the last statement perhaps should use something like the following to avoid an irrelevant/extraneous warning:
move *.lib \masm32\lib > nul
(may not apply when called from ..\makelibs.bat .... )
I would also suggest using something like the following at the top of bldlibs.bat:
if "%mdir%"=="" goto past_mdir_echo
@echo mdir is set to: %mdir%
:past_mdir_echo
just to confirm exactly what version of ml and link are being used (in case it matters? .... I was doing some testing of masm32 beta-9 when built with ml and link from Microsoft's toolkit-2003)
ld,
Just watch the later versions of ML have broken command line support for *.asm. You are stuck with using a response file which works OK but is a bit more mesing around. One of the problems with the installation builds is that command.com and cmd.exe respond differently on some things. I will probably rebuild the installation to use Pelle's library manager as it seems a lot more reliable than the method I have used with Microsoft link.
I have used the technique on the testbed for POASM and it appears to be both more reliable and faster.
Quote from: hutch-- on February 23, 2006, 12:11:43 AM
There is almost nothing I can do about additional software that is running that may restrict what happens during an installation.
Ok. Probably just my setup.
The testinst.exe that was built worked ok on another computer with Win2k-Sp4 and another with WinXp-Home-Sp2, so I suppose it is something non-standard about my development computer .... imagine that <g>.
I turned off/disabled NortonAntiVirus script checking and the WinXp-Sp2 firewall, and still got the MS exception message-box on the development computer, so I don't know what else to try to get the MS exception message-box to go away. It is disconcerting for someone evaluating masm32 to get a MS exception during installation, but perhaps I'm the only one reporting this. I'll send this post, run chkdsk, reboot, and try again.
Quoteif I had the space, its a lot easier to distribute the entire project with all of the libraries built but its a fair bit larger by doing this.
I am profoundly ignorant about masm32, but so far, my main interest has been getting up to speed with masm32.lib. The 8.2 version is only about 80kb, and the 9-beta is about 130kb. Would a person wanting to evaluate masm32 be able to more or less get started trying out tutorial\console with a greatly reduced subset of masm32 ... perhaps with only masm32.lib and kernel32.lib (about 490kb) pre-built?
As I recall, the asm files in tutorial\console references masm32.lib, gdi.lib, user32.lib, and kernel32.lib, but only really need masm32.lib and kernel32.lib
I've used the nsis freeware installer quite a bit on four separate freeware apps, and could perhaps put together a masm32_evaluation_starterkit_setup.exe and tutorial oriented to newbies using vc6/vc7.1/vc8 (while it is still relatively fresh in this newbie's brain). I can understand that anyone seriously trying out masm32 is expected to be a relatively experienced developer (understatement), but there are perhaps some things that could be simplified for a person evaluating whether they want to put in the time and effort to get up to speed with masm32.
ld,
To make simple installs, I use Winrar SFX files that do the job fine. I have seen the nullsoft installer but I am not impressed with the general style of installation and don't use them. The masm32 project does not write anything at all in the registry so that it is properly registry safe and all you ever need to do to uninstall it is delete the directory tree.
This much, the entire project is copyrighted so don't redistribute any of it. I have obtained permission to distribute any of the stuff I did not write myself and among the conditions of doing so is that it is not subject to redistribution. I have had to licence it very tightly so it is not commercially exploited or bits of it relicenced under different licencing systems.
I still support windows versions fom win95b upwards but its becoming ever more difficult to make an installation that works across this range because Microsoft keep changing the rules so I may have to make 2 installs, one for legacy machines running old OS versions and a later one for NT and upwards based systems.
Quote from: hutch-- on February 23, 2006, 03:25:03 AM
This much, the entire project is copyrighted so don't redistribute any of it.
Ooops .... I suspect that I was unclear in my statement about putting a nsis installer together. I intended it as a helpful offer if you thought a "training wheels subset" might be of assistance for vc6/7/8 programmers to evaluate and get up-to-speed with masm32 .... I meant the opposite of an intention to package an unauthorized subset of masm32.
Sorry .... this newbie is very impressed with masm32 and grateful for all your patient help .... and thought maybe there was something I might be able to "roll up my sleeves" and pitch in to "give something back" rather than only being the recipient of help.
Lynn D. Allan
Quote from: hutch-- on February 23, 2006, 12:11:43 AM
I don't know what is happening with the testinst.exe file as it does nothing unusual.
After the following:
* reboot-with-chkdsk,
* turn off a number of security features
* delete C:\masm32\*.*
* re-install 9-beta to C:\masm32 and accept all defaults
(mdir not defined so c:\masm32\bin\ml and c:\masm32\bin\link used)
I am still getting this exception message-box each time testinst.exe runs:
Unhandled exception at 0x0422b57 in testinst.exe: 0xC0000005: Access violation writing location 0x00000028
which seems to be this instruction:
00422B57 add byte ptr ds:[28h],al
This may be "operator error" on my part or something flawed about my computer setup. If so, please ignore and sorry for the false alarm. Just trying to help.
It wouldn't be happening because of a cmos-bios setting, because testinst.exe works ok when I reboot to another partitiion. NAV, AdAware, and SpyBot report that C:\masm32 is clean.
Looks like stack corruption - ie. returning to the wrong address.
I couldn't find testinst.exe and I'm on a slow connection atm so can't download beta 9 (btw. three months on and still beta? Why?).
Olly gave me this:
0005 28000000 add byte ptr [28], al
Also, I don't believe the .text segment for the testinst program would extend from 00400000 (base address, unless something is built differently) all the way to 0042xxxx. That's 128kb worth of code! The question is, though, why hasn't this happened for other people?
Quote from: zooba on February 23, 2006, 07:18:29 AM
The question is, though, why hasn't this happened for other people?
I wonder that also. What is different about my setup?
The testinst.asm code looks to be the same since 8.2. The CreateWindowEx looks like it just possibly might have something to do with what is going on .... with the next to last parameter being 0x00400000, which doesn't seem like what I would expect for HINSTANCE (and suspiciously similar to the IP of the exception 0x00422b57) ... but the documentation says this is ignored by NT/2000/XP and only applicable to Win9x/Me
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/winui/windowsuserinterface/windowing/windows/windowreference/windowfunctions/createwindowex.asp
invoke CreateWindowEx,WS_EX_LEFT,
ADDR szClassName,
ADDR szDisplayName,
WS_OVERLAPPEDWINDOW,
150,150,500,300,
NULL,NULL,
400000h,NULL
When I change the 400000h to 0h, then it assembles+links and runs ok (but I am only guessing .... I am pretty ignorant about WinApi gui calls also)
00400000h is probably the correct value for hInstance, though (as you said) it's not required as of Windows NT. I don't like seeing it hard-coded though :eek
If it ran fine without it, that's probably the problem :bg Maybe some other program has taken that slot and so Windows has relocated it...
Can we short circuit this guesswork, 400000h is the instance handle for almost every running executable, only DLLs run at different address depending on what is available at load time. The testinst.exe program has run on some massive number of computers so its not the problem and it is a very simple orthodox win32 application in terms of how it creates a window and processes its messages in the WndProc.
It does not require any environment settings so there is no reason for an "mdir" variable. It appears to install and run on two of your other machines so I guess its telling you something about how your dev box is set up. I have not heard of it before but there may be some other system environment setting that interferes with the correct version of link but I don't know of other people having this problem and this is why the paths are hard coded to ensure it does not pick up the wrong binaries when building programs.
I hope you can get this stuff going as its a ton of fun once you get the swing of it. Its like having a sharp axe instead of a haybale to address a problem. :bg