Yeah, I kinda figured it out the first time. My question were about why there is a long path in my name, and on other unsigned installers, there is just the name.
Does this has to do with the bootstrapper?
Thank you both for the suggestions. But I guess that the tool isn't worth a certificate prices at $199,-.
How come that some installers have only the installers name, while mine has a very long path attached to it?
My installer is bundled as an .exe, with some prerequisites shipped with it. Then I notices that I could run the msiexec command on the .exe. And that is when I ask if I need to recreate the bundle with .msi option instead.
I got it to work almost. My new problem is that when it tries to start the installation, it get stuck on the "Computing space requirements". The error message is attached.
Also reads this in the log: DEBUG: Error 2716: Couldn't create a random subcomponent name for component 'AIShRegAnswer ...
I can see this has been done Really nice..
However, I would rather prefer that there were one admin user (?id=1), and the rest in a "Staff" group with a green color. Just my two cents
I tried doing so, but it doesn't seem to work at all.
How do I attach the script? As a attached custom action and in a .vbs file?
Function GetParentFolder() filePath = Session.Property("WAR3X_FILE") Set objFS = CreateObject("Scripting.FileSystemObject") If (objFS.FileExists(filePath)) Then ...