MASM32 Version 9 Release

[hutch--]

I have temporarily posted the two different versions of the installation at the 2 following URLs. The main install is for Windows versions from Win2000 upwards, the second is for win9x versions. I still have to do the web pages for the main download referral site which I will have done in a day or so.

www.website.masmforum.com/masm32/m32v9r.zip  Release version for Win2000 and later
www.website.masmforum.com/masm32/legacy.zip   Legacy version for win9x.

[GregL]

Thanks Hutch, it is appreciated  :U

[PBrennick]

It installed with no problems on my XPHE w/SP2

I will install it on WinME in about 6 hours - 40 minutes.

Paul

[Vortex]

Hutch, that's great, thanks :U

[shankle]

Hi Hutch,
www.masm32.com is pointing to masm32 8.2. Thought you might want to know.
I assume a new version is ready to go. Many thanks for all your hard work.
Regards,
JPS

[hutch--]

Thanks Jack, I mentioned in the first post that the web page has not yet been done as i wanted any useful feedback before I download the project to all of the different web sites that help carry the bandwidth load.

[Mincho Georgiev]

I had reorganize the Workstation Directory on my PC with the new version,and now i can sit back for 1 cigarette time,satisfied by that  :U

[Mark Jones]

Hi Hutch, just FYI but building the libraries still generates some warnings:

...
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
dtcuis.def : warning LNK4104: export of symbol "DllGetClassObject" should be PRIVATE
...
   Creating library framedyd.lib and object framedyd.exp
input file must have .inc extension
input file must have .inc extension
...
logmgr.def : warning LNK4104: export of symbol "DllGetClassObject" should be PRIVATE
logmgr.def : warning LNK4104: export of symbol "DllRegisterServer" should be PRIVATE
logmgr.def : warning LNK4104: export of symbol "DllUnregisterServer" should be PRIVATE
...
msdtctm.def : warning LNK4104: export of symbol "DllGetClassObject" should be PRIVATE
...
strmbasd.def : warning LNK4104: export of symbol "DllCanUnloadNow" should be PRIVATE
strmbasd.def : warning LNK4104: export of symbol "DllGetClassObject" should be PRIVATE
...
strmbase.def : warning LNK4104: export of symbol "DllCanUnloadNow" should be PRIVATE
strmbase.def : warning LNK4104: export of symbol "DllGetClassObject" should be PRIVATE
...
C:\masm32\include\wsnmp32.lib
C:\masm32\include\wsock32.lib
C:\masm32\include\wtsapi32.lib
Could Not Find C:\masm32\m32lib\masm32.lib

The rest of the installation went smoothly except for the TESTINST. It compiled and ran fine, showing "Installation success" but then crashed at "Offset: 10141FBD." AMD XP 2500, XP Pro SP2. The error is repeatable at the call to DispatchMessageA.

Also note that Pelle.txt lists older versions of POLINK and POLIB. The new versions are 4.00.2 and 4.00.0, respectfully.

[diablo2oo2]

whats new in this version? is there any changelog?

[Ghirai]

Updated my mirror: http://ghirai.com/hutch/mmi.html

[skywalker]

I have temporarily posted the two different versions of the installation at the 2 following URLs. The main install is for Windows versions from Win2000 upwards, the second is for win9x versions. I still have to do the web pages for the main download referral site which I will have done in a day or so.

www.website.masmforum.com/masm32/m32v9r.zip  Release version for Win2000 and later
www.website.masmforum.com/masm32/legacy.zip   Legacy version for win9x.

I noticed this version is slightly bigger than the beta version. Should the other version be replaced ?

[GregL]

Hutch,

My installation experience was identical to Mark Jones'. The package is working fine after installation.

Note: I'm running Windows XP Pro SP2.

[hutch--]

Mark, Greg,

Thanks for the info on testinst. I can't get it to misbehave on my win2k but its possible that there is some change in how the messaging is set up in xp with late service packs. Could I ask a favour and get you to test a very simple mod on the source file.

Replace the message loop in the Main proc with the following.

Code Select Expand


    jmp @F

  StartLoop:
    invoke TranslateMessage,ADDR msg
    invoke DispatchMessage, ADDR msg
  @@:
    invoke GetMessage,ADDR msg,NULL,0,0
    test eax, eax
    jnz StartLoop



All I have added is the jump into the loop instead of falling through the DispatchMessage to see if this is the problem. Just as an additional test, could you test the masm1k example in the exampl08 directory and see if it builds and runs OK ?

[hutch--]

For the amount of time it took, I just coded another simple indicator program that shows if the installation has succeeded.

If you have the time, it would be appreciated if you could test it on a machine that showed a fault with the older one.

[attachment deleted by admin]

[GregL]

Hutch,

I assembled a debug version of testinst.asm and stepped through it. You got it right, your replacement code fixed the problem. The problem was happening in the call to DispatchMessage. I believe it was because GetMessage needed to be called before calling DispatchMessage (the MSG structure didn't contain a valid message), which is the case in the new code.

The new testinst.exe you just posted works fine too.

Greg