I have been nitpicking at the beta for the last couple of months and I am running out of things to do to it. There is a known errata thanks to JimG where I have misspelt a word in the help files but there does not appear to be much else.
This version has POASM included whch is an important addition to the project and it has a matching compatible WINDOWS.INC that both MASM and POASM use. The 16 bit Microsoft linker is icluded for people who have some need to build 16 bit applications. All of the binaries have been rebuilt so they are DEP safe and with thanks to Microsoft for releasing Vista without winhelp support, the main help files have been converted to CHM format so they will run on Vista.
The QE and VKDEBUG help files have not yet been coverted to CHM yet. Windows.inc is a much larger file that is now split into two files to avoid a limit in MASM of the number of lines for an include file. here are additional examples including some simpler POASM examples that build from the supplied batch files. The project contains the latest version of Ray Filiatreault's FP library and had a new addition af an extensie date / time library writen by Greg Lyons.
I need some reliable testing done by people who have properly configured computers and actually know what they are doing. Correctness testing, anything that is not working correctly, anything missing etc ....
I would like to be able to relase this version reasonably soon as the DEP problem for inexperienced users has not been an easy one to solve with the earlier version even though it does work correctly when the OS is configured for non DEP safe binaries.
It wold be very useful for anyone who owns a late enough machine that supports hardware DEP while running Vista to test if the install works correctly.
I would ask this much, I am not interested in redesigns, Nullsoft installers, conceptual changes to .NET or debugging applications that may have problems, I need experienced programmers who know what they are doing to do some testing so that this version can be released.
www.masm32.com/download/beta10e.zip
hutch,
Thanks. I just installed it on Vista Home Premium, with DEP turned on (my CPU supports hardware DEP). No problems. I'll be trying it out.
Installation successfull on my machine with DEP turned on ( CPU supports hardware DEP )
OS : Win XP Pro SP2
WinXP SP2 MCE Eng at Core2 Duo laptop: all is ok
I would remark a little problem :
ifdef UNICODE
INVOKE GetCommandLineW
else
INVOKE GetCommandLine
endif
it's in kernel32.inc, but with release of VS 2008 is time to accept UNICODE in runtime.
So could suggest such abbreviation of character type :
ifdef UNICODE
CAP_T TYPEDEF WORD ; символ
For documentation in chm also much thanks :cheekygreen:
e:\archives\masm32\include\windows.inc(35) : error A2111: conflicting parameter definition
due
wsprintfA PROTO C :VARARG
in masm9 there was
wsprintfA PROTO C :DWORD,:VARARG
next kernel32.inc misses a lot of apis
compare by content in total commander shows 73 differences.
those for example are missing:
AddConsoleAliasA PROTO :DWORD,:DWORD,:DWORD
AddConsoleAlias equ <AddConsoleAliasA>
AddConsoleAliasW PROTO :DWORD,:DWORD,:DWORD
AddLocalAlternateComputerNameA PROTO :DWORD,:DWORD
AddLocalAlternateComputerName equ <AddLocalAlternateComputerNameA>
AddLocalAlternateComputerNameW PROTO :DWORD,:DWORD
AddRefActCtx PROTO :DWORD
AddVectoredContinueHandler PROTO :DWORD,:DWORD
AddVectoredExceptionHandler PROTO :DWORD,:DWORD
and many more
wsprintfA isa defined twice in the masm32 project, in windows.inc and with and IFDEF in user32.inc, both are the same and with the IFDEF you cannot have both included, thats what the duplicate guard is for. If you have a conflict you are multiply defining the wsprintfA prototype apart from the main windows.inc include file so the answer is simple, fix it. It is a C VARARG prototype so there is no simple rule for the argument count.
RE the missing prototypes in kernel32.lib, the current version is based off an older version of kernel32. All you need to do to get a current set is pick kernel32.lib out of a Vista, server2003 or XP PLATFORMSDK and run the l2inc.exe tool to get all of the newer ones. Noting that I added over 400k of extra data to windows.inc some months ago, no-one is doing me a favour when they contribute nothing while I work on include files then whinge about it later.
The APPI functions you listed are in the header file wincon.h.
Just convinced myself that it was time for a change. www.masm32.com/download/beta10e.zip works like a charm - compliments!
Hi Hutch
This is an annoyance that has been ongoing but caused me to screw up a client binary file last week ::):
When using qeditor opening binary as HEX, and save with "save" rather than "Save Hex as binary", then the HEX display image is saved instead of the binary. Is it possible that "save" can be inhibited in a future release to stop dummies like me from screwing things up!
Regards
Chris
Hutch---
When using PoAsm with your Windows.Inc, can I go by the more liberal Pelle license for PoAsm, or am I bound by the more restrictive Masm32 license?
I asked here because on a search, they are both mentioned in your original post, but apologies if this is not the right place.
Jim,.
With POASM you are using Pelle's licence which allows you to do anything with it. If you want to distribute POASM or any of Pelle's tools you have to ask him as I cannot delegate the versions I have permission to distribute.
Hi Hutch. I was just asking about windows.inc, does the license for masm32 apply to windows.inc also? Or is windows.inc free to use however one wants?
Jim,
Because I produce the windows.inc file you are welcome to use it for anything you like but it must not be redistributed.
Thank you Hutch, that answers my question.
Just for clarification... Does this hold true for the rest of the masm32 package excluding the actual Microsoft copyrighted software? (masm32.lib, macros, etc.)
Hello,
Instal right but,error at link time
couldn't find _lstrlen ......
seem to be one error in the library kernel32.lib
Yves,
Its right at the end of kernel32.inc.
lstrcpynW PROTO :DWORD,:DWORD,:DWORD
lstrlenA PROTO :DWORD
lstrlen equ <lstrlenA>
lstrlenW PROTO :DWORD
ELSE
echo -----------------------------------------
echo WARNING Duplicate include file kernel32.inc
echo -----------------------------------------
ENDIF
Here is a small test p[iece.
; «««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««
include \masm32\include\masm32rt.inc
; «««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««
comment * -----------------------------------------------------
Build this template with
"CONSOLE ASSEMBLE AND LINK"
----------------------------------------------------- *
.data?
value dd ?
.data
txt db "1234567890123456",0
.code
start:
; «««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««
call main
inkey
exit
; «««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««
main proc
LOCAL padd :DWORD
LOCAL plib :DWORD
mov plib, rv(LoadLibrary,"kernel32.dll")
mov padd, rv(GetProcAddress,plib,"lstrlen")
push OFFSET txt
call padd
print str$(eax),13,10
invoke FreeLibrary,plib
invoke lstrlen,OFFSET txt
print str$(eax),13,10
ret
main endp
; «««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««
end start
Jim,
Quote
Just for clarification... Does this hold true for the rest of the masm32 package excluding the actual Microsoft copyrighted software? (masm32.lib, macros, etc.)
No, this is why the project is covered by its own licence. I have added POASM to support Pelle and his tools and to make an alternative available to people who want to write software beyond the restrictions of the use of MASM.
The MASM32 library and the SDK libraries are built with MASM and cannot be used outside of its licence. The macro file for masm will not work with POASM and there is a seperate macros file for POASM which is not connected to MASM or its licence.
Pelle's tools are capable of producing the entire SDK library set so that is not a problem. I produce the files in the include directory so there is no problem using them with POASM in much the same way as the windows.inc file.
You are welcome to modify the source for the masm32 library so it will build with POASM but many use the masm32 macros so they will not build directly with POASM. A year or so ago I posted a test version of POASM that had some of the masm32 library converted to build with POASM which may save some of the hack work doing the conversion.
<author edited. supplied new text>
I found the following post clear in relation to what you can do with the MASM binaries and with your own code. http://www.masm32.com/board/index.php?topic=171.0
and just for clarification .... read the licence for masm32, thats what its there for.
Quote from: hutch-- on March 20, 2008, 09:13:55 AM
and just for clarification .... read the licence for masm32, thats what its there for.
And just to clarify, I only wanted to know what parts of the masm32 package I could use with assemblers other than Microsoft masm without restrictions, e.g. writing programs for Linux.
The license states:
Quote4. You cannot use the MASM32 Project to write software for Non-Microsoft Operating Systems.
I assumed this was if I was using Microsoft copyrighted software (ml.exe, link.exe, etc.) but not other parts of the Masm32 package, but I wanted to know for sure rather than guessing. Passing along this restriction to non-Microsoft parts of the package is very similar to the hated GPL. And speaking of which.....
QuoteThe MASM32 project cannot be used to create open source software or any other project under any form of licence that requires the user of the MASM32 project to surrender the rights they are afforded under the MASM32 licence. In particular the MASM32 licence completely excludes projects licenced under the GNU organisation's published GPL licence and/or variants.
has always baffled me. I know several very highly regarded members of this forum are vehemently opposed to gpl, I just never could understand why, and I really don't want to get into an emotional debate on the issue here.
But, ultimately, my real (if somewhat unrealistic) goal is to some day write my own assembler, and I just wanted to know what parts of the Masm32 package could be used with it, without passing along the above restrictions. The information should also be of interest to users of PoAsm, SolAsm, etc.
Jim,
My last post was pointed at thomas. As far as using any part of the masm32 project to write an assembler, I don't see any reason why you cannot use ALL OF IT as you would be writing a freesatnding tool as long as the production of the assembler is not licenced as an open source project under the GPL or similar.
RE GPL, I have had nothing but grief from the sum total of GPL authors who put their hand out for anything they can get while hiding behind GPL for never contributing anything back. In contrast Microsoft always did deliver and they have been very helpful and have contributed a reasonable amount of effort with the masm32 project.
To satisfy people who want to write software that is prohibited under the enclosed Microsoft EULA, I have included Pelle's assembler to support his tool set which are in fact very good tools which can produce all of the necessary compoents like SDK libraries and any library module you wish to write in that format which is only marginally different to masm but there is no way to use any binary created with masm for projects licenced under the GPL.
Thank you for your patience, Hutch.
I think I got it. One thing that bothers me is I have run across several interesting projects over the years that were under GPL. I would have liked to work on them, but couldn't because of the license issues. While I am neutral on GPL myself, I understand your frustration.
So if I understood you correctly, if I wanted to work on a GPL project, and I used PoAsm, Polink, etc., I could use windows.inc but no other part of the Masm32 package.
Jim,
You can use any of the text based files that I have produced, windows.inc, the complete include file set, the macros that work with POASM etc but nothing produced with masm can be used. Also note that use does not permit redistribution or relicencing of the text based files that I have produced.
Good luck with a new assembler, its a massive amount of work but like Bogdan, a noble endeavour.
Excellent. Thank you very much :U
Hello,
Missing in the kernel32.lib and include files
Quote
AddVectoredExceptionHandler
RemoveVectoredExceptionHandler
support :clap:
Was wondering when MASM 10 will be out of beta testing?
Thanks in advance for all your efforts.
JPS
so far
it works well
Maybe it would be useful append to dialogs.inc file this macro to create a Modeless Dialog:
; ------------------------------------
; create a modeless dialog from the data
; written to the memory template.
; ------------------------------------
CallmodelessDialog MACRO Instance,Parent,DlgProc,lpExtra
invoke CreateDialogIndirectParam,Instance,esi,Parent,
ADDR DlgProc,lpExtra
push eax ;; preserve return value
invoke GlobalFree,esi ;; free memory
pop eax ;; restore return value
pop edi
pop esi
ENDM
Best Regards!
Thanks for the comment, I had forgotten to put the later version into the project build. Done !
I have run into some installation issues with the beta10e release. I'm running XP Pro SP2, Pentium D, 2GB memory, AVG Free 8.0, and all XP and AVG updates current.
I downloaded beta10e.zip,
MD5:f70de3323b93c79808479d4e931efdb7 *beta10e.zip,
extracted install.exe,
MD5:b3fb871d3f87bcb26b0b19007165d83e *install.exe,
and run it.
Thereupon, AVG Free 8.0 decided the following seven files were virus or malware enabled. Note that AVG Free 8.0 is their latest version that I just installed.
\masm32\ablockc.dll
\masm32\include\hcompact.exe
\masm32\indenta.dll
\masm32\l2def.exe
\masm32\macros\lst.exe
\masm32\mnutoasm.exe
\masm32\tproc.exe
Thinking "False Positives", I searched the Masm32 Forum and found some discussion on this issue where FPs were claimed to be based on various scanner's heuristics, etc. Not being completely satisfied, I tried to submit the seven files to online scanning services such as http://virusscan.jotti.org/. I was not able to directly upload any of the seven files due to some access violation. I was finally able to submit them by booting to XP safe mode, copying the files to a floppy, reading the floppy on a Win98SE machine, and submitting them to http://virusscan.jotti.org/ from Win98SE.
Although AVG 8.0 on my XP machine flags all seven as infected, nothing was found on the scanning service except for two files, l2def.exe and lst.exe (I have not listed all the scanners that found nothing).
l2def.exe
Status: POSSIBLY INFECTED/MALWARE (Note: this file was only flagged as malware by heuristic detection(s). This might be a false positive. Therefore, results of this scan will not be stored in the database)
MD5: dc4c993c32e8793525c2b8b4fa4b55bb
VBA32 Found Trojan-PSW.Game.42 (paranoid heuristics) (probable variant)
lst.exe
Status: INFECTED/MALWARE
MD5: 046ad09cd503fec32c2b21802477bc02
F-Prot Antivirus Found Possibly a new variant of W32/MalwareHiderPatched-based!Maximus
VBA32 Found Trojan-PSW.Game.42 (paranoid heuristics) (probable variant)
Based on the foregoing, it may well be an FP phenomenon. However, there are other things at work I find puzzling. I cannot access any of the seven files in the normal way. In my whole masm32 installation, I can access all files except these seven. In trying to generate an md5sum digest for my masm32 installation, I get the following error messages:
md5sum: ablockc.dll: cannot read [Permission denied]
md5sum: hcompact.exe: cannot read [Permission denied]
md5sum: indenta.dll: cannot read [Permission denied]
md5sum: l2def.exe: cannot read [Permission denied]
md5sum: lst.exe: cannot read [Permission denied]
md5sum: mnutoasm.exe: cannot read [Permission denied]
md5sum: tproc.exe: cannot read [Permission denied]
Also, trying to access them by any other means, except direct execution which I did not do, I get similar results. Running as Administrator and taking ownership of the files made no difference.
Has anyone experienced this problem, verify it, or give an explanation for it?
Thanks,
spummeler,
The files listed are all produced by a particular compiler I use for some tools and it has been known in the past that an occasional heuristic scanner in some of the lesser AV products trigger on the valid executable format that these files have. The better end of AV scanners do not have this problem, Nod32 or Kaspersky for example as the simple fact is the files have no infections at all. The other consideration is that they run perfectly on some millions of computers that have downloaded the project over the last 10 years.
Its a bit hard to connect to AV product makers that they need to properly comform to the 32 bit PE file specifications provided by Microsoft and not try and reduce the specification to a subset that they may understand. The problem is with the AVG product you are using, they need to improve their heuristic scaning from simplistic asumptions to ones that conform to the Microroft specifications. All executable code in version 10 is DEP safe code as it was all rebuilt from source after Microsoft changed the PE specifications for ater OS versions.
Hello, Steve.
I haven't used masm32 for a long time. Just wondering if thes package provides headers for driver developement?
hutch,
Thanks for your reply and clarification. I did some further digging and now better understand my installation problem with beta10.
I offer the following in hopes it will help others who stumble onto this type of problem. Also, what follows is based on the assumption
that "masm32" is not infected with virus or malware.
My particular problem is related directly to AVG Free 8.0 so other's mileage may vary. When I installed beta10, AVG was running and
flagged the following files as infected:
\masm32\ablockc.dll
\masm32\include\hcompact.exe
\masm32\indenta.dll
\masm32\l2def.exe
\masm32\macros\lst.exe
\masm32\mnutoasm.exe
\masm32\tproc.exe
As explained previously (by you) these are false positives out of AVG. However, since I had AVG's "Resident Shield" running, it would
not let me access these files. This explains why I could not run the .exe files, generate an md5sum digest, nor otherwise access these
files. To fix this, what I had to do was:
Open AVG User Interface and go to Components . Resident Shield . Manage exceptions . Resident Shield Exceptions .
'check' Use excludes for the Resident Shield . Add Path
and enter c:\masm32\ (replace c: by appropriate drive letter). Now I can access the files and AVG quits whining about infections.
Regards,
I just run across this problem again- conflicts in protos when including some files. I don't know if there is a solution since someone is obviously using one or more of these and wouldn't appreciate the routine names being changed, but I thought I'd bring it to your attention:
"K:\beta10e\include\mswsock.inc"
9: EnumProtocolsA PROTO :DWORD,:DWORD,:DWORD
10: EnumProtocols equ <EnumProtocolsA>
"K:\beta10e\include\nmapi.inc"
59: EnumProtocols PROTO
"K:\beta10e\include\wsock32.inc"
9: EnumProtocolsA PROTO :DWORD,:DWORD,:DWORD
10: EnumProtocols equ <EnumProtocolsA>
-------------------------------
"K:\beta10e\include\mapi32.inc"
14: CreateTable PROTO :DWORD,:DWORD,:DWORD,:DWORD,:DWORD,:DWORD,:DWORD,:DWORD,:DWORD
"K:\beta10e\include\rtm.inc"
10: CreateTable PROTO :DWORD,:DWORD
-------------------------------
"K:\beta10e\include\trnsdt.inc"
9: WEP PROTO :DWORD
"K:\beta10e\include\ws2_32.inc"
8: WEP PROTO
"K:\beta10e\include\wsock32.inc"
37: WEP PROTO