BenjaminKalytta

@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

@Alanoll: Oops, I forget to create english menu. I'll fix this tomorrow. I'll also add your NOT comparison. Some are expanded. Just use relative paths. Rel. Paths will always be exapnded to current wihu application path NOT current path! Benjamin

No only for the created user that will be used for software installation.

Ok I added this ... /Nocancel and /Ds (last one disables restart checkbox i.e. user can't change it) I decided currently not to add user specific shellfolders creation as you wished. There are mainly 2 reasons: - I've to code some other projects next weeks - Im so stupid and started to code with c ... it's became such a muddle and this after only 3200 lines of code ... such a shame I should had used c++ and MFC. May be I'll port WIHU to MFC in future ... yesterday I tried this, but it was too much work. Benjamin

@tinnef: indeed this was a bug ... it was hard to find it ... was a very bad mistake of mine Just download it again, hope everything is fixed now. @my2001: So nun zu dir. Vielen dank für dein Lob ... war heute schon fast am verzweifeln wegen Bugsuche und so. Nein momentan arbeite ich fast nur an dem WIHU Tool. Studium kommt etwas zu kurz, aber Klausuren sind eh vorbei. Initially I've created this tool for my self which should be used for my unattended setup if Winxp SP 2 will be released. Very nice of you two. But I think that's nothing what I've done so far. It's just a little tool. May be in future. @Alanoll: I'll see what I can do Benjamin

@Mr_Happy: No, please use /SkipSoftware @midiboy: Would make things harder ... don't know if I should change this. You know, if one bug is fixed, there are 2 new ones;) (in this case this isn't a bug but it make no big difference) Generally this is possible, but is this really necessary? Another reason not to add this, is the problem with Windows 2000. It wouldn't support it right now and indeed it wont work at the moment, because to change shell folders, you have to logon each of this new user with "LogonUser" API. This is problematic on Windows 2000 in sense it requires SE_TCB_NAME privilege (Act As Part Of The Operating System) which is disabled by default in Windows 2000. To enable this privilege you have to restart the system which is problematic after unattended installation. Benjamin

@midiboy: Sorry, this was indeed a bug. Please download it again... is fixed now. Yes it will. @Alanoll: WIHU can do string and number comparison. How it works: For key.x.y: WIHU determines if the data given after ? character is a string or a number. Accepted numeric characters are only 0-9 or (hex character in the way 0x0..9a..f). It will then read out the value from specified registry key and compare this against this with given value. If the found number is greater, WIHU will treat the installable software as older and will unselect this software in WIHU software selection control ... and also add a "Warn" icon before it. If WIHU determines a string (this also applys to File.x.y) WIHU will do a string greater/less compare. It will not just only compare against equalness. What does this mean: A file with version 1.2.3.4 is older than 2.3.4.5. This will corretly be evaluated by WIHU. This of course also applys to a registry key which may not only contain numbers. In this case WIHU do an alphabetical comparison. ABCD would be smaller than BCDE and so on. Is there a need for NOT comparison? Couldn't this be done with greater/less comparison? Benjamin

@WARTHOG: Yes you are right this is possible with WIHU. To change administrator name please use /admin=name or /adminpwd=password to set the administrator password. owner name can be chanbged via UI or with /owner=name also computer name can be changed via UI or with /computer=name. @all: I'll not post here when new Version of WIHU released in future. This will just create much traffic here. Just look for new version at my web page in future. I'll release version 2 now ... xml things will be may be added in future version. Benjamin

Update: There was a bug in User Creation Interface which is fixed now in beta 6. Benjamin

New beta 5 is out. I decided to add multiple user creation capability first because it is not so time consuming. It's late now (4:00 am) so I'll go to bed. May be tommorow (today) I'll modify user creation interface a bit i.e. remove user creation in first dialog and combine this one. WIHU also creates a folder for the new user if this doesn't exists yet. But note, at the moment the folder is created in current user context i.e. directory security doesn't include new user. Will be fixed tomorrow ... may be. Benjamin

What is a PST file and what is a MST file and what they are used for? 2. I'll create folders if they dosn't exists. Benjamin

@midiboy: very strange. Please take a look in install.ini ... may be you set it there? Otherwise, please send me your current environment strings. Run "cmd.exe /k set" grab it and send it to me. Please also logon as "Bernd" and open following key in registry editor: "HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders" and please also send it to me. benjamin

Point 2 was added now. @midiboy: ... EDIT: It seems that you are right ... there were indeed a bug if path was entered in edit box. Is fixed now. Benjamin

Shortly after my posting I added this by my self Please downlod it again;) Yes, but first I have to create XML loader and modify wihu so that it uses Tree View control. MSXML API isn't that easy, believe me CPL ... yes may be in future. EDIT: Of course will be added.benjamin

@midiboy: Frag doch gleich mich oder schau selber was sich hinter der Erweiterung für ein Command verbirgt: %SystemRoot%\system32\mmc.exe your.msc HKEY_CLASSES_ROOT\.msc -> MSCFile HKEY_CLASSES_ROOT\MSCFile\Shell\Open\Command Btw. midiboy bug is fixed now, thx again for testing it. Benjamin

@midiboy: Not it should change the shell folder of the new created user, but I haven't testet it yet. There must be a bug inside. I'll test it now. It will ONLY change the shellfolder of the current user, if you installs With checkbox "Use current user" (which shouldn't be enabled by default or if you'll create a user account which already exists (in this case currently logged on user will be used too). I'll fix the bug soon. Benjamin

@syntax_13: I know how a tree view looks like @hydex: There isn't much difference between 1.6 and 2.0. Btw. no popups. Benjamin

@midiboy: I'll try to implement on demand formating i.e. format unformatted drive. @mcardlej: I haven't tested it yet if this work. But should work. What about using XML files to store install data. I think it is more flexibel and suitable if Multiple commands support should be implemented. Here is an example file. This would allow infinite levels of depth (sub commands) ... if some one need this Disadvantage is that I have to use tree view control which doesn't support Group Headers. Benjamin

Please forgive me the late answer, but the telekom turned off my DSL connection (bill was not payed ) @simo1234: Please download the latest "beta 2". Should be fixed there. (Please don't forget to use command.x ) Some othe bugs are fixed and shellfolder rename dialog was added. @PoloDude: Use /log=logile.log. Please ensure that you enclose the path name in "" if it contains blanks like /log="A new Logfile.log" @Nendur: I know what you mean, I could use the same syntax as Windows INF file uses, but this is going to complex so that no one can understand it here. @syntax_13: Ok I'll add option to skip Software install, and also may be I'll add Expand/collapse. Btw. hide bug is fixed now. .MSI files don't need msiexec.exe prepend anymore. Just specify it as you do it with a executable ... if you want. Benjamin

I think one level of commands is enough. It would be really to complex otherwise so that no one can handle it. It doesn't make sense to add more. Benjamin

if /skiprestart is not set, wihu presumes auto restart i.e. default is restart. Ok, may be I'll add this in future version or may be in final 2.0. Benjamin

What about using windows shell for this purpose? Hmm, not very good. Purpose of this tool was software installation interface. If you don't want install any software just specify an empty install.ini There is already a switch for this "/skiprestart". "Home" will only set the local profile path for the new created user which also can be changed with windows "computer management" Why don't you use "Computer Management" (Systemsteuerung\Verwaltung\Computerverwaltung) for this purpose? I know windows (2000/XP) interface is a bit limited in contradiction to Windows 2003, but may be I could create a stand alone user creation tool? Benjamin

New first 2.0 beta is released today. Please note, install.ini has changed dramatically because of the need to support sub sections. Please take a look at install.ini for example until my web page is updated. Please also note that it is now possible to create multiple users which is specified in users.ini. There is also a little tool (wihuuser.exe) which only process users.ini i.e. create users only. But note, I will not add more features to this tool. This is intended for user creation only and will NOT be extended! There is exactly one command line argument to specify the path of the users.ini. @midiboy: Multiple user creation is now possible Benjamin

Here is a demo of my new interface. Who wants can take a look at it. Changing settings or install software will not work here. It will be released on weekend as far as I can say now. Benjamin

@Osmosis Jones: I'll add a kind of subsections ok? I don't like icons in it;) Your suggested layout is ok, but it is not possible to create it dynamically i.e. fit it with each data in install.ini. May be it will look something like this: Thx for asking. There are some that was very difficult. "Analysis" for example was not as easy as I thought before, but I think it was enough. On Friday the last exam for this semester (physics) I think I'll fail ... haven't learned enough. But I'll give it a try Benjamin