December edition MASM32 version 9.00 BETA

[Human]

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.

[Vortex]

because masm32 becomes really outdated

Hutch is updating regulary the masm32 package. What are you talking about?

[Human]

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

[Vortex]

add PE exe strcutures etc include,it

Did you check windows.inc for all those structures below related to the PE format?

Code Select Expand

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

[rwalt]

Hutch, if Pelle's assembler pans out to your liking, will you dump MASM for POASM in version 9?

[hutch--]

:bg

I am much more interested in the making of history than predicting it.

[GM]

Hutch,

StrToFloat doesnt preserve some registers esi, ebx, edi
This is old stuff, but still in.

[hutch--]

Thanks GM.  :U

[PBrennick]

"making of history"...  A bit ambitious, I think...  for myself, I will just "live" with history.

Paul

[jdoe]

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

Code Select Expand


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

[Mincho Georgiev]

Interesting, jdoe.

Code Select Expand


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.

[Mark Jones]

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...

[rags]

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

[hutch--]

Rags,

Thanks, I mised that one. It should have the replacement in the line with LINK inline.

Code Select Expand


; «««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««««
; 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


[l_d_allan]

<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>