BenjaminKalytta

Hi midiboy, Ok I'll see what I can do. Benjamin Kalytta

But I'll do a little rework next days because there could be some incompatibilities in conjunction with calling WIHU within T-12 stage. I'll then write detailed information about this in change log. Benjamin

XPect you are right, thx test.eval command should be used in conjunction with test command, wherby test may be used to compare against file existence, fileversion, filetime, registry key/value (existence). Please refer my manual or example install.ini for detailed information about how to use it. Benjamin

Hi victor888, please verify that selected.1.0 = 1. I can't find a bug there. Please also note, subcommands will only be called if it's parent commands are checked. I never said WIHU can't be run on T-12. As many users here verified WIHU can be started from within cmdlines.txt. if /UseCurrent switch is used, everything works. Benjamin

No, this is very bad ... you may lock WIHU with such an option. If user interaction is required (which may always the case) hidding popus is very critical. I wont add this. Benjamin

It seems that every change in this key will not saved back to default profile, don't know why. But this was not my intention with my answer. I've never tested WIHU on T-12 so if some one here encounter any problem (excepted this stated out before) I'll fix this as soon as possible. But I require more feedback. "Secondary Logon" Service isn't running at this stage, this is certain. With consequence that creating user account at this stage and using some of this as primary user wan't work. But creating user account and setting profile data should work at this stage since I changed my code in release 2.1.x.x as I verifyied this. Developer, Benjamin Kalytta

(please delete) Benjamin

In this case, I think it could be possible to change any profile data. I've to rewrite WIHU a bit. benjamin

Hmm, does it mean that you are logged in as SYSTEM but %USERPROFILE%\Default User profile is used at this stage? If yes, please "smood1" show me the complete path of your log quote Error 2: localuser 's profile settings can't be changed. (Profile: C:\Documents....). The path part is important. Please show me also your ini file which you used at T-12. Did you create any user account at this stage? Benjamin

At T-12 you are always logged on as SYSTEM. Changing any profile specific things like shellfolders, environment variables and so on, wont work at this stage because this account don't own an profile. Please tell me how you WIHU call and which settings did you make. Benjamin

Thanks "Kleidemos" for your italian translation of WIHU. It's available for download on my site. Benjamin

Some hint on how to delete an item: command.0 = cmd.exe description.0 = Item to be deleted <= delete this command.1 = cmd.exe description.1 = Item 1 command.2 = cmd.exe description.2 = Item 2 command.3 = cmd.exe description.3 = Item 3 Instead renumber each item you should do following: command.1 = cmd.exe description.1 = Item 1 command.2 = cmd.exe description.2 = Item 2 command.0 = cmd.exe description.0 = Item 3 => become Item 0 Yes, but this could make things easier. May be I'll support both in future. With and without numbering. Im currently working on such an ini file parser. There will also no more section per software item, only one [software] section which contains each software entry below it. Benjamin Kalytta

MS Word 2003 is ok, but please note, use UTF-8 or ANSI, no UNICODE characters. If this isn't the problem, please send me your rtf file. Benjamin

Each time when my web site goes down, I'll attach new WIHU binary here. Benjamin

Hmm, Im personally don't like XML ... morever it is very elaborately to use MS XML Interface. I like the kind of ini files. What about using spaces or tabs to form indentation? command = xyz.exe description = Item command = xyz.exe description = Sub Item command = xyz.exe description = Sub Sub Item command = xyz.exe description = Sub Item command = xyz.exe description = Item would be [x] Item [x] Sub Item [x] Sub Sub Item [x] Sub Item [x] Item and so on Benjamin

Yes this is a bit inconsistency. I should change this. hmm, what if more than one is selected (which is theoretically possible)? Isn't it better to select first item by default? Danke Ich antworte mal weiter auf englisch, wir wollen ja keinen hier ausschließen There was already one who asked to combine xplode and WIHU. But I think wraith don't really want this. And also, WIHU uses a completely different config file structure. Benjamin

@Morkeleb: Please show me the logfile. You could use /log=filename.log /verbose=1 Benjamin

Sorry, I fixed this. Benjamin

Yes nice idea ... I also tought about this. I changed it this way that Button will be showed after 1 minute for each process. (timout is 1 minute) Benjamin

1.) Problem is fixed now, please download new WIHU version. 2.) I changed it this way. Benjamin

I changed this, please download new WIHU version. There is a "Cancel" button near the progress bar which may be pressed to cancel current running process. Please note, interrupting currently running software installation may cause serious system errors! Benjamin

I changed this, please download new WIHU version. Currently running process will not be suspended but no new process will be started, i.e. no additional software item will be installed until "Yes" or "No" is pressed, whereby "Yes" will cancel a running process. Benjamin

Date: 14th January 2005: version 2.1.12.21 Fixed bug in current user AutoLogon code Date: 04th January 2005: version 2.1.12.18 Informative "About" Dialog was added. Date: 03th January 2005: version 2.1.12.17 [users] Home keyword to set users profile default home path didn't work as excepted. Date: 08th December 2004: version 2.1.12.15 Added /Group=Administrators|Users switch to set primary user group membership. Added /DisableLoadMenu=0|1 switch to prevent users to load external ini files from within WIHU UI. Date: 12th November 2004: version 2.1.12.13 Profile data wasn't handled correctly at T-12 during windows installation. Date: 9th November 2004: version 2.1.12.8 Profile path wasn't detected correctly at T-12 stage of Windows Installation. Update: There is still a bug inside this code. Profile settings can't be changed because some registry hives can't be found at this stage. I'll find a solution, may be some registry keys in default user profile doesnt exists at this stage. Date: 26th October 2004: version 2.1.12.7 "Abort" button was disabled. Date: 23th October 2004: version 2.1.12.6 Added Process "Abort" Button + Button-Show Timeout. Date: 22th October 2004: version 2.1.12.5 Various bugs were fixed. /verbose = 2 isn't available any more.

Please use /verbose=1 switch and show me the extact command line that was executed by WIHU. Benjamin

Thats no bug because worker thread is running parallel to WIHU UI windows. But I could change this. Of course this make sense to abort processing of rurther items in background. Benjamin