In Protected Mode Memory section of asmintro.chm, there's a line of code:
mov [edx], al ; copy ascii zero to address in EDII think it should be corrected to:
mov [edx], al ; copy ascii zero to address in edxIn Working With Macros section of asmintro.chm, there's a line:
QuoteMacros differ from library modules n a number of important ways...
which should be corrected to:
QuoteMacros differ from library modules in a number of important ways...
:bg
EDX.
Also, in masm32.chm under Calling Conventions the table fails to indicate that SYSCALL is caller stack cleanup, as is the actual case (tested for ML 6.15 only).
In Working With Macros section of asmintro.chm, there's a line:
QuoteThe convention is not without purpose as it provides a method where the least number of register preservations need to occur between procedures calling other procedures or systme function in the Windows APIs.
which should be corrected to:
QuoteThe convention is not without purpose as it provides a method where the least number of register preservations need to occur between procedures calling other procedures or system functions in the Windows APIs.
In Working With Structures section of asmintro.chm, there's a line:
QuoteIf for example you needed to pass the adress of a RECT structure to a procedure, you would normally make the call in the following manner
which should be corrected to:
QuoteIf for example you needed to pass the address of a RECT structure to a procedure, you would normally make the call in the following manner
with http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=21138
the html help worksop ,every one can made modify on an .chm help file.
good idea is to put here the corrected chm.
Quote from: ToutEnMasm on October 19, 2011, 12:33:01 PM
with http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=21138
the html help worksop ,every one can made modify on an .chm help file.
good idea is to put here the corrected chm.
I would argue that better that one person modifies the document as otherwise different versioning issues are muddled, if someone mistakenly deletes a page all hell would break loose.... You might end up with 3 different versions with different updates all uploaded at the same time meaning someone has to go through all 3 documents to find the updates and amend one single version....
MT updating requires a MT comptible updating system
When I get around to the documentation I will fix the typos but at the moment I am working on macros and library modules and will not put it aside for a trivial matter of spelling.
we muddle through on the typos :P
Quote from: dedndave on October 20, 2011, 02:35:36 PM
we muddle through on the typos :P
* We muddle through on the typos. :P
actually, if there were no typos, i'd be inclined to suspect forgery
Hutch is infamous for his typos :bg
:bg
MASM is an excellent spell checker. :P