Jump to content

Windows Installer Helper Utility


xper

Recommended Posts

Just alittle language error....

Sure do wish I could read German :)

Any progress on that NOT idea? If not, it's OK, i can keep with my current method till the next incarnation of the CD (week or two :rolleyes: )

How are the command line switches interpreted? Are they just imported as strings, and then WIHU then expands any variables and the uses them, or what?

Could you possibly make a variable for within WIHU for the PATH to the WIHU executable? as if the switches are read in as strings, /Users=\users1.ini won't work. (tried it) a %WIHU% variable would be good for that instance.

post-70-1090011570_thumb.jpg

Link to comment
Share on other sites


@Alanoll:

Oops, I forget to create english menu. I'll fix this tomorrow. I'll also add your NOT comparison.

How are the command line switches interpreted? Are they just imported as strings, and then WIHU then expands any variables and the uses them, or what?
Some are expanded.
Could you possibly make a variable for within WIHU for the PATH to the WIHU executable

Just use relative paths. Rel. Paths will always be exapnded to current wihu application path NOT current path!

Benjamin

Link to comment
Share on other sites

@Alanoll:

Everything is fixed now ... also fixed spell mistake :)

It added following comparion modifiers for "key.x.y/file.x.y":

?!1.2.3.4 = check against not euqalness

?=1.2.3.4 = check against equalness

?>1.2.3.4 = (is default) check if installable file is newer

?<1.2.3.4 = check if installable file is older

(if nothing is specified, > is used)

It's also possible to specify multiple key/file comparion types, i.e. AND or OR comparison for each key. In old version behaviour was following:

If one key.x.y or file.x.y was found which was older WIHU treats every key as older and unselect checkmark in software component list. (AND comparison)

With OR comparison only one key.x.y/file.x.y need to satisfy the version comparison. You can specify this each for key.x.y and for file.x.y:

Example:

key.comparison.0 = OR

file.comparison.0 = AND

Environment Strings specified in /log=, /ini= or /users= will be expanded now. Exception: None of the environment specified in install.ini will be expanded ... because ini file is not yet loaded at this stage.

There are some changes which also concerns key.x.y and file.x.y:

If file doesn't contain any version information, and ! modifier isn't specified in version data WIHU treat this software component as being older and wan't install this be default. If ! is specified this meaning will be inverted, i.e. WIHu will treat this software component as newer.

If specified file isn't found and ! modifier isn't specified WIHU will treat the software component as being newer, if specified this meaning will be inverted. (Same apply for key.x.y)

Some general information on users.ini:

Users.ini can also be used to disable for example an existing account, or to set new password, new flags ...

Example:

[users]

user.0=administrator

status.0=0x0002

Will disable Administrator account.

(Please note: Users.ini will be processed before administrator renaming when specified with /admin=name)

Benjamin

Link to comment
Share on other sites

@midiboy: I decided to add user specific shell folders.

Add this in users.ini like "My Video.0=path" as in install.ini.

users.ini shell folders overrides install.ini's global environment which will be used as default if no user specific shellfolder is set.

@Cretak: Autoscroll was added.

I also fixed some critical bugs.

Benjamin

Link to comment
Share on other sites

@midiboy: I decided to add user specific shell folders.
Oh! :rolleyes: I'm sure he'll be very pleased!! :D
I decided to add user specific shell folders.

Great, I also appreciate this. Just makes some tweaking utilities and registry hacks obsolete. :D

@midiboy

There is no "Kissing You" smiley but I very much appreciate it !!

But u can use that heart icon for the posting headline! :)

Link to comment
Share on other sites

Could someone test it please in unattended installation with some users in users.ini?

-What I want to know is if each user is created (should be)

-If each shellfolder specified in users.ini is created (should be)

-If new created user can login also if NO user password was specified.

Thx

Benjamin

Link to comment
Share on other sites

Correct me if I'm wrong....

If I set %KEY%?="Hitachi" if the drive is called "Hitachi" it won't install? But if I set %KEY%?!"Hitachi" it will install it to JUST the hitachi drive?

Blasted logic problems :) Hardest part of programming for me.

Link to comment
Share on other sites

alrighty. Alittle confused after reading the website. It said if found (File section) it considered it newer and deselcted. Oh well, thanks for the clarificaiton.

Drivers\Creative\setup.exe -s -f1".\Drivers\Creative\audigy.iss" -f2"C:\Windows\Temp\creative.log"

I have tried that with and without the .\ in the -f1 switch, but in either case it cannont find the ISS file. I could just rename them all setup.iss, and be done with it, but was curious why this didn't work. Perhaps not appending the path? Need for %WIHU% now? :)

Also, what environment variables are available within WIHU (the windows ones)? I tried %windir% in the above statement, and it didn't work properly, had to hard code it in.

Link to comment
Share on other sites

@all: I fixed a minor bug in registry key version comparison (only > and < comparison).

@Alanoll:

Wihu will start setup.exe, but it then is up to the setup.exe to find the correct path. I added %WIHU% for this purpose, may be it helps.

As environment variable you can specify those predefined by windows (yes %WINDIR% should work) and those which are specified in [environment] section also users.ini specified shellfolders (for each user only, not global).

%WIHU% points to the path of WIHU application directory. This can also be specified in command line.

Benjamin

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...