Windows Installer Helper Utility

[midiboy]

Ok,

just downloaded it again and now it works. I should be autodownloading from your website every 20 minutes or so

Thanks,

Alex

[BenjaminKalytta]

@midiboy: You can also do following:

[environment]
personal=%systemdrive%\%newusername%\eigene dateien
my music=%personal%\eigene musik
... and so on.

Benjamin

[my2001]

I guess, we'll need a project manager here soon to keep the overlook.

So many fixes, releases and wishes ... oh no, I gotta do the dishes.

[Alanoll]

i did a real system test today, and for some reason teh first two instances didn't stop, but the third one did (installing all the applications)...

I'll try to rereate it later today (reformating, wrong drivers loaded)

[BenjaminKalytta]

@Alanoll: didn't stop. how do you mean it didn't stop?

@all: A general question.

Example: There is this subtree:

SECTION DESCRIPTION
    [x] SUBTREE 1
        [x] SUBTREE 1.2
            [x] ITEM 1
            [ ] ITEM 2
    [x] SUBTREE 2
    ...

What should happen if ITEM 1 is unselected? Should SUBTREE 1.2 also be unselcted? (hint: SUBTREE 1.2 is also A COMMAND!) or should this do nothing in SUBTREE 1.2?

Benjamin

[Alanoll]

whoops, need to be clearer

It waited at the screen to press Next at Installation Selection. I used the AutoInstall switch (i believe, I double check when trying to recreate it later, don't have the source files or the drive to burn the ISO)

As for the tree structure....

I would think Subtree 1.2 shouldn't be deselected, if Subtree1.2 is it's own command. However, if Subtree1.2 didn't have a command, then it would be deselected.

Using the nero example from the other day, if Nero install was Subtree1.2 and the unregistering of the codecs were the sub-items, then by deselecting all the subitems wouldn't stop Nero from installing....

[BenjaminKalytta]

This lead to the next question. At present each sub tree contain a command to be executed. Should I add an option where a subtree is just a subtree i.e. just for describing purpose?

Benjamin

[Osmosis Jones]

i don´t know if there are to many options. wihu is quite cool because it´s easy. but indeed i think such an option would be greate.

so, yes, add an option where a subtree is just a subtree.

thanks for this greate prog again.

[Alanoll]

i don´t know if there are to many options. wihu is quite cool because it´s easy. but indeed i think such an option would be greate.

so, yes, add an option where a subtree is just a subtree.

thanks for this greate prog again.

ditto, it's always good to have descriptiong....except for when it's

[Nero]
    [*]Install Nero

like it is now

[BenjaminKalytta]

So I released first working pre beta. (Bug reports are welcome now)

Following INI keys have been added:

1. collapsed.x=1|0 (initially collapse entire subtree)

2. selected=1|0 (selects section to be installed or not. Note, this is not selected.x which can be set individually per item (subtree)) This keyword can only be once per section! If Selected=0, none of the items in this section will be installed also if each of them would be checked!

Following INI keys have been renamed:

1. hide.x will now be hidden.x

INI file syntax doesn't changed any way except hidden.x

Special behaviour:

If you don't want a subtree/item to be an executable command but just a descriptive header key, set command.x=*

In this case item texts will be bolded.

Note also, if a tree is unchecked none of its subtrees/items will be executed. (This also applys to descriptive keys which contains one or more subitems)

If a tree is hidden also each subtrees/items are invisible.

EDIT:

; NEW IN VERSION 2.1

; Default keys that will be used if not specified:

; selected = 1 (Note this is the selection key for entire section)

; hidden.x = 0

; description.x = <missing description>

; selected.x = 0

; key.comparison.x = and

; file.comparison.x = and

; collapsed.x = 0

; There can be theoretically up to 65535 entries per subtree

; Note: One key "key.a.b.c.d.e.f.g.h...=" must not exceed 255 characters entirely

; To create a sub tree just append sublevel indizes to commands like:

;

; command.0="command 1"

; command.1="command 2"

; command.0.0="sub command 0.0"

; command.0.0.0="sub command 0.0.0"

; command.0.0.1="sub command 0.0.1"

;

; ... Will create following sub tree:

;

; "command 1"

;     "sub command 0.0"

;         "sub command 0.0.0"

;         "sub command 0.0.1"

; "command 2"

EDIT: Other question. Take this example:

[ ] SUBTREE
    [ ] ITEM 1
    [ ] ITEM 2
    [ ] SUBTREE 1
        [ ] ITEM 1.1

If SUBTREE is Checked/Unchecked, should this also check/uncheck entire subtrees like this:

[x] SUBTREE
    [x] ITEM 1
    [x] ITEM 2
    [x] SUBTREE 1
        [x] ITEM 1.1

Good night, it's late now

Benjamin

[midiboy]

If SUBTREE is Checked/Unchecked, should this also check/uncheck entire subtrees like this:

CODE 

[x]SUBTREE

[x] ITEM 1

[x] ITEM 2

[x] SUBTREE 1

    [x] ITEM 1.1

I think it should, no ?

But that´s just my opinion ! :-)

Good Morning by the way !

Alex

[BenjaminKalytta]

@all:

I fixed last known bug in 2.1 now, and I hope there are no more bugs

Would be nice if you could test this version to find undetected may be critical bugs though. However, I'll add more features than current 2.1 beta 1 next days.

I think it should, no ?

because no one has any objections I changed it that way.

Benjamin

[Osmosis Jones]

[ ] SUBTREE
    [ ] ITEM 1
    [ ] ITEM 2
    [ ] SUBTREE 1
        [ ] ITEM 1.1

If SUBTREE is Checked/Unchecked, should this also check/uncheck entire subtrees like this:

[x] SUBTREE
    [x] ITEM 1
    [x] ITEM 2
    [x] SUBTREE 1
        [x] ITEM 1.1

i think it´s quite logical so do it like you said.

[Alanoll]

@all:

I fixed last known bug in 2.1 now, and I hope there are no more bugs 

Would be nice if you could test this version to find undetected may be critical bugs though. However, I'll add more features than current 2.1 beta 1 next days.

I think it should, no ?

because no one has any objections I changed it that way.

Benjamin

sure....right when I finalize the current incarnation of the disc, you come up with a new beta version....

looks like I'll be testing two programs on the next one, nLite and this

[Osmosis Jones]

Note also, if a tree is unchecked none of its subtrees/items will be executed. (This also applys to descriptive keys which contains one or more subitems)

this doesn´t work i tried it with some progs.

i have an tree with two subtrees and if i uncheck the tree both sub trees are executet.

note: the subtrees are hidden.