First screen of installer inaccessible to screen readers.

[shantanu]

Found the old thread; it was indeed more than a decade, nineteen years to the month!   

Code Select Expand

https://masmforum.com/board/index.php/topic,4767.msg35668.html#msg35668
If someone has access to the old attachments, it could be a viable starting point.
(I have no idea where my original script is)

[Quin]

An NSIS installer would be amazing, I personally love the NSIS syntax and it's much simpler and easier to maintain.

[stoo23]

If someone has access to the old attachments, it could be a viable starting point.
(I have no idea where my original script is)

Well, that is perhaps unfortunate.
As can be noted by;

[attachment deleted by admin]

placed at the bottom of your initial post on the old forum, https://masmforum.com/board/index.php/topic,4767.msg35668.html#msg35668 an action taken by Hutch at some time in the past, the File/Attachment, would no longer Exist on the server :(

Sorry

[zedd]

@stoo
Hutch removed ALL attachments from that forum. Not specifically targeting anyone from what I understand. But for other reasons.

The attachment you are looking for *might* be in the 2012 archive. This one, https://masm32.com/board/index.php?board=39.0]
If not, check the other one.... from 2005...  https://masm32.com/board/index.php?board=38.0 It could have been placed there instead possibly.

Shantanu, do you remember the name of the missing attachment??

[sinsi]

@shantanu, the attachments were a problem for hutch (too many GB iirc) so they were put into archives under Forum Links, so if you remember the attachment name you should be able to find it.

As for the installer, hutch fought many battles to keep MASM32 free of any kind of licencing and I think we should respect that.

How many people can say that they took on Microsoft and won?

[zedd]

shantanu, does this look like it??
This is #2446 at Archive 2
And is also attached Here!

Code Select Expand

SetCompressor /FINAL /SOLID lzma
SetCompressorDictSize 32

!define SW_NAME MASM32

name 'test abc dir'
outfile 'test.exe'
showinstdetails show

InstallDir "C:\MASM32"
DirText "Choose the drive on which you want to install ${SW_NAME}."

section -
Setoutpath '$INSTDIR'
File /r ".\INSTALL\*.*"
sectionend

Function .onVerifyInstDir
  ;try to COPY 7 letters, should NOT get seven letters!!!
  ;copy the (expected) letters "MASM32" from the path: X:\MASM32
  StrCpy '$R0' '$INSTDIR' 7 3
  StrCmp $R0 'MASM32' PathOK
    Abort ; if $INSTDIR is not the expected path, don't install there
PathOK:
FunctionEnd


[NoCforMe]

As for the installer, hutch fought many battles to keep MASM32 free of any kind of licencing and I think we should respect that.

Yes, absotively.

Should be doable with a re-write.

[Quin]

As for the installer, hutch fought many battles to keep MASM32 free of any kind of licencing and I think we should respect that.

Yes, absotively.

Should be doable with a re-write.

+1, I wouldn't want to go against the philosophy of the masm project at all. But I don't see why this wish can't be upheld with a rewrite.

[NoCforMe]

You'll have to forgive the "respected members" here.
They mean well. But they tend to be conservative, which is to say likely to object to anyone who suggests "moving their cheese".
I find that quite annoying, and an impediment to moving forward with the whole MASM package. Which is an incredibly useful thing, worth not only preserving but improving.
But, to use the well-known tautology, it is what it is.

[stoo23]

Hutch removed ALL attachments from that forum.

Well, Not completely it would seem, as I Have found the odd attachment there AND there Are still quite a few .zip files referred to in the Attachments Folder on the server with listings in phpMyAdmin as well, .... sadly, not that one obviously 

[zedd]

Hutch removed ALL attachments from that forum.

Well, Not completely it would seem, as I Have found the odd attachment there AND there Are still quite a few .zip files referred to in the Attachments Folder on the server with listings in phpMyAdmin as well, .... sadly, not that one obviously 

obviously I did not know that, thanks. From what hutch had said in the past, I thought all of them had been removed. I rarely visit the U.K. forum since I was never a member there during its lifespan.

I believe though that I found shantanu's missing attachment... in post #20. It is a sample install script for NSIS. That script though, may not work with a modern version of Nullsofts software. I have no way of testing it, so I cannot confirm.

[NoCforMe]

So how complicated is that installation program really?

Does it really require that scripting language to rewrite it?

Another possibility would be to write it in something besides assembly language, which should sidestep the AV issue.

Someone could write it in (cough, cough), say, C ...

[sinsi]

You'll have to forgive the "respected members" here.
They mean well. But they tend to be conservative, which is to say likely to object to anyone who suggests "moving their cheese".
I find that quite annoying, and an impediment to moving forward with the whole MASM package. Which is an incredibly useful thing, worth not only preserving but improving.
But, to use the well-known tautology, it is what it is.

I can't follow the logic here, it seems so contradictory :shrug:

The biggest impediment to both 32 and 64 bit SDKs is translating the Windows SDK header files, specifically equates and structures. The API calls are easy, the .lib files have all the definitions.

Even hutch had problems with the Windows 7 headers (before the win8 UWP crap), he had a program
that could do the basic parsing but still needed to go through every .inc file to fix it.

[TimoVJL]

install.exe uses 7zWin.sfx v4.23