BenjaminKalytta

Thanks, but I use a default one for the moment from the site you mentioned. I modified it a bit. Benjamin

Following new INI keywords are available in version 2.1.11: test.x.n = [!]<file>/<key>[?version][><!=]<version/data> test.eval.x = <index>[&|!=]<index>... evaluates the "test.x.n" results disabled.x = if.true/if.false/0/1[,inherit] Example File comparison (Test if version of wmp.dll is greater 9.0.0.3196) test.0.0 = %SystemRoot%\System32\wmp.dll?version>9.0.0.3196 Example File Existence Check (Test if wmp.dll exists) test.0.1 = %SystemRoot%\System32\wmp.dll Example File Non Existence Check test.0.2 = !%SystemRoot%\System32\wmp.dll Example Registry Value Comparison test.0.3 = HKLM:Software\Microsoft\DirectX\Version?>4.09.00.0902 Example Registry Default Value Comparison test.0.4 = HKLM:Software\Microsoft\DirectX\?=Test Example Registry Path Existence Check test.0.5 = HKLM:Software\Microsoft\DirectX\ Example Registry Key Existence Check test.0.6 = HKLM:Software\Microsoft\DirectX\Version Each expression may be negated by prepending ! operator. test.eval.0 = 0 & 1 | 5 & 3 & 2 Above will return true, if test.x.0 AND test.x.1 are true, OR if test.x.5 AND test.x.3 AND test.x.2 are _true_. Remark: Although no braces are supported currently, braces will be implied as follows: test.eval.0 = ((((0 & 1) | 5) & 3) & 2) Following keys may have additional new values "if.true" and "if.false" (also "inherit"): selected.x locked.x hidden.x collapsed.x group.x disabled.x Example: (Will disable item 0 and all it's subitems if comparison result was true) disabled.0 = if.true, inherit Default behaviour: test.eval.x: Is always true if no check.x is specified, i.e. in this case disabled.x = if.true is the same as disabled.x = 1 Remark: locked.x and disabled.x can't be combined! This keywords are intended to replace current file/registry comparison in future. It's also possible to load riched text help files for each software item which will be showed in right pane in software selection dialog. Expectable there will be a keyword help.x = <.rtf file> for this purpose. Note: This is expectable available in version 2.1.11.2 Benjamin

What was your intention again? You could just remove hidden.x key or add another subkey in this way: command.4.0 = %systemdrive%\install\nero\Nero63120.exe /silent /noreboot description.4.0 = Nero Burning ROM 6.3120 Application selected.4.0 = 1 command.4.1 = %systemdrive\install\nero\Nero63120DEU.exe /silent /noreboot description.4.1 = Nero Burning ROM 6.3120 Paket für deutsche Sprache selected.4.1 = 1 command.4 = REGEDIT /S %systemdrive%\install\nero\nero6.reg description.4 = Nero Burning ROM 6.3120 selected.4 = 1 Ordering is TOTALLY unimportant here, it can have any order! file.1.0 = %systemroot%\system32\drivers\ctaud2k.sys?>5.12.1.322 Will check if version of current ctaud2k.sys is less/equal than 5.12.1.322. If greater, it will return false (unchekced, striked out) ... or in other words check if 5.12.1.322 is greater than version of ctaud2k.sys. I know that's a bit confusing, but I once introduced it so, would make some trouble if I would change this behaviour now. Since you want compare 2 entries, you have to append correct sub index here. There can't be file.1.0 multiple times! Please use: Note: key.x.n and file.x.n have an additional index "n" Benjamin

You are right, I doesn't work at this moment because I'm currently not able to fully load rtf data (images, text and other objects) There will be a new keyword help.x=file.rtf Yes greyed means it is checked, but some of it's subitems may be (not necessarily) unchecked. I would do following: command.4.0.0 = %systemdrive%\install\nero\Nero63120DEU.exe /silent /noreboot description.4.0.0 = Nero Burning ROM 6.3120 Paket für deutsche Sprache selected.4.0.0 = 1 hidden.4.0.0 = 1 command.4.0 = REGEDIT /S %systemdrive%\install\nero\nero6.reg description.4.0 = Nero Burning ROM 6.3120 (Keys & Others) selected.4.0 = 1 hidden.4.0 = 1 command.4 = %systemdrive%\install\nero\Nero63120.exe /silent /noreboot description.4 = Nero Burning ROM 6.3120 Applikation (Main Item) selected.4 = 1 Benjamin

Yes indeed there was a bug inside. Please not, I changed meaning of ?! and ?=. file?! test for non existence of a file (it's more logical) file?= test for existence of a file Please download 2.1.11.x version Benjamin

Use wihu /encryptini and /decryptini Benjamin

Sorry, yes I meant 2.1.10.7 (2.1.10.x) Benjamin

Thank you for taking time to create this logos. Some comments: Logo 3 is too overloaded I think. Logo 7 peoples are cut too much. Logo 1, software installation specific image is too hidden. Hmm, logo 4 and 5 looks ok, but I miss something there, don't know what CD looks always nice;) May be some settings specific things is missing? Benjamin

How can I disable the windows-own user-cereation dialogs? I don't know the answer. Do these clash with those of WIHU? No, there are no problems using WIHU to modify this account, to add new one and delete exiting one. What about the ability to do user configuration in the config file? Each user in [users] section will be created/modified/deleted by WIHU, except you remove this entries within WIHU UI. Benjamin

Yes sounds nice ... if I get time, I'll implement this. Btw. did you create the symbol on your example screenshot. I like this kind ... CD looks very nice. Would you create a logo for WIHU? It must be 49x49 pixel. Benjamin

There is an example ini file included! Just take a look at that. But I'll describe it shortly (btw. there is a help section on my web page). Settings are either organized in INI file, per command line switches or in WIHU GUI. Ini file may contain following predefined sections: [Environment] [settings] [users] [environment.x] whereby x is an index 0 ... 65535 which correspondences with user.x index. EACH OTHER SECTION NAME may contain software installation commands. (described later) First of all, let me say, EACH section is optional, i.e. not required. 1. [Environment] section This section may contain environment variables which will be _ONLY_ available while WIHU is running. One special thing is, that this environment variables may also reference regsitry values like following: DefaultProfilesDir = HKLM:SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\ProfilesDirectory This will read the above key from registry and saves it in environment variable DefaultProfilesDir which will be accessable later with %DefaultProfilesDir% somewhere. 2. [settings] section This section may conatin settings as the name implied. ; Write windows size back to ini file after exit dimension.update=1 ; set window size dimension.width=900 dimension.height=500 ; PageHeaderTitle.x and PageHeaderSubTitle.x sets the header title or subtitle of specified page. First page is page 0. PageHeaderTitle.0=Title0 PageHeaderSubTitle.0=SubTitle0 PageHeaderTitle.1=Title1 PageHeaderSubTitle.1=SubTitle1 ; Set computer name to xyz computer=xyz ; Skip settings dialog skipsettings=1 Take a look at command line switches (WIHU /?) for detailed description of each of this keyword. 3. [users] section Here you may create new user accounts or modify existing one. See example install.ini or my web page for more information how to do this. ;Disable Administrator account user.0=Administrator status.0=0x002 Group.0=1 password.0=1A6178031B607F041A617C071B6073081A61700B1B60770C1A61740F1B601B60D0 crypted.0=32 4. [environment.x] section This contains permanent environment variables which will be stored in registry for corresponding user. x is the index specified in [users] section in user.x keyword. In above example there _could_ be a [environment.0] section. Please note, registry references as in [environment] section are not allowed here! 5. software specific sections. This may contain many keywords. Most important one is command.x and description.x. [My New Software] command.0 = myapp.exe description.0 = My first application Please don't forget to append valid index. There may no holes in indixes, i.e. following isn't possible: command.0=... command.1=... command.3=... In this case WIHU will stop execution at command.1. To organize software items in a tree structure you may append sub indixes like: command.0.0 = mysubapp.0.exe description.0.0 = First sub item of "My first application" command.0.1 = mysubapp.1.exe description.0.1 = Second sub items of "My first application" command.0.0.0 = mysubapp.0.0.exe description.0.0.0 = First sub item of sub item 0.0 selected.0.0.0 = 1 WIHU will show above example as: [x] My New Software [ ] My first application [ ] First sub item of "My first application" [x] First sub item of sub item 0.0 [ ] Second sub items of "My first application" For detailed information about allowed keywords please take a look at example install.ini or at my web page. Here your example: [ATI specific things] command.0 = "%systemdrive%\drivers\radeon_catalyst_4.9\Setup.exe -s -f1 setup.iss" description.0= ATI Display Driver file.0.0 = %systemroot%\system32\atiddc.dll?! selected.0=1 command.1="%systemdrive%\install\radeon_catalyst_panel_4.9\Setup.exe -s -f1 setup.iss" description.1= Control Panel 4.9 with SmartGART file.1.0 = %systemroot%\system32\atiddc.dll?! selected.1=1 [Power Toys] command.0 = "%systemdrive%\install\powertoys\CmdHerePowertoySetup.exe /S /v /qn" description.0=<Will never be showed since hidden> hidden.0=1 selected.0=1 command.1="%systemdrive%\install\powertoys\TweakUiPowertoySetup.exe /S /v /qn" description.1=<Will never be showed since hidden> hidden.1=1 selected.1=1 [Adobe Acrobat Reader 6.0.1] hidden.0=1 command.0="%systemdrive%\install\adobe\acrobatreader\Adobe Reader 6.0.1 - Deutsch.msi" /qn" description.0=<Will never be showed since hidden> selected.0=1 [MSN Messenger 6.2] hidden.0=1 command.0=%systemdrive%\install\msnmessenger\MsnMsgs.msi IAGREE="Yes" ADDEXPLORERTOOLBAR="" SETSEARCHENGINE="" SETHOMEPAGE="" /q" description.0=<Will never be showed since hidden> selected.0=1 [Winamp 5.0.5] hidden.0=1 selected.0=1 command.0="%systemdrive%\install\winamp\winamp.msi INI="%systemdrive%\install\winamp\winamp.ini" /qn" description.0=<Will never be showed since hidden> ... or you could do (prefered): [Drivers] command.0 = "%systemdrive%\drivers\radeon_catalyst_4.9\Setup.exe -s -f1 setup.iss" description.0= ATI Display Driver & Control Panel 4.9 with SmartGART file.0.0 = %systemroot%\system32\atiddc.dll?! selected.0=1 command.0.0="%systemdrive%\install\radeon_catalyst_panel_4.9\Setup.exe -s -f1 setup.iss" description.0.0= Control Panel 4.9 with SmartGART selected.0.0 = 1 hidden.0.0 = 1 [Applications] command.0.0 = "%systemdrive%\install\powertoys\CmdHerePowertoySetup.exe /S /v /qn" description.0.0 = Power Toys (Helper or whatever) hidden.0.0 = 1 selected.0.0 = 1 command.0 = "%systemdrive%\install\powertoys\TweakUiPowertoySetup.exe /S /v /qn" description.0 = Power Toys selected.0 = 1 command.1 = "%systemdrive%\install\adobe\acrobatreader\Adobe Reader 6.0.1 - Deutsch.msi" /qn" description.1 = Adobe Acrobat Reader 6.0.1 selected.1 = 1 command.2=%systemdrive%\install\msnmessenger\MsnMsgs.msi IAGREE="Yes" ADDEXPLORERTOOLBAR="" SETSEARCHENGINE="" SETHOMEPAGE="" /q" description.2 = MSN Messenger 6.2 selected.2 = 1 selected.3 = 1 command.3 = "%systemdrive%\install\winamp\winamp.msi INI="%systemdrive%\install\winamp\winamp.ini" /qn" description.3 = Winamp 5.0.5 This will unselect this item only if atiddc.dll doesn't exists, otherwise this item will be selected and installed by default. To prevent some one from selecting this item anyway, you could add locked.0=1 Or in case you don't want some one changing any item in [ATI specific things] section you could add top level locked=1 (without indixes) btw. file.0.0=%systemroot%\system32\atiddc.dll?= would be the inverse meaning of ?!. Note: There is currently a bug in file existence check implementation. Please download new version 2.1.11.1 Benjamin

Hehe, but I've currently no time. If I've got time again, WIHU is outdated Btw. does XPLODE support AutoLogon? I created a nice autologon code in WIHU, may be this can be integrated in xplode. Autologon password wont be saved in plain text in registry there. Benjamin

@Wraith: Wow, I took a look at your last development snapshot ... looks nice ... seems that my WIHU wont needed any more Benjamin

NO. Please reread my small manual again! You have to append indixes like command.0=... and also have to specify description.x keyword here. Please take a look at http://unattended.msfn.org/xp/oemfolders.htm Benjamin

@Morkeleb: Hi. Yes WIHU is able to create users. In fully unattended installation Windows XP will not create a default user AFAIK. In this case WIHU is usefull. I created a folder $OEM$\$1\OemData which will cause Windows Installation to copy it to folder "OemData" on System drive. You have to select something like [Data] UnattendedInstall=Yes [Unattended] UnattendMode=DefaultHide UnattendSwitch=Yes in winnt.sif. Best place to run WIHU is in GuiRunOnce in winnt.sif. [GuiRunOnce] "%systemdrive%\OemData\wihu.exe /autologon" Of course you could start WIHU eralier at T-12 or so, but it isn't recommended because there are some restrictions at this stage. Benjamin

So I implemented registry shell\open\command execution as I said. command.x will be checked against registry if command is found there it will be used and each %1 ... %x placeholder in registry HKCR\<key>\shell\open\command will be replaced by corresponding specified arguments. for example you'll find following command for .exe files in registry: HKEY_CLASSES_ROOT\exefile\shell\open\command "%1" %* So if you would create a command.0 = test.exe 1 2 3 this will be replaced by "test.exe" 1 2 3 Inexplicably the command for .cmd and .bat files are the same which mean it should be executable directly too, which isn't the case during windows installation as I tested it once. So it is better to still use cmd.exe /c here. Benjamin

So I implemented registry shell\open\command execution as I said. command.x will be checked against registry if command is found there it will be used and each %1 ... %x placeholder in registry HKCR\<key>\shell\open\command will be replaced by corresponding specified arguments. for example you'll find following command for .exe files in registry: HKEY_CLASSES_ROOT\exefile\shell\open\command "%1" %* So if you would create a command.0 = test.exe 1 2 3 this will be replaced by "test.exe" 1 2 3 Inexplicably the command for .cmd and .bat files are the same which mean it should be executable directly too, which isn't the case during windows installation as I tested it once. So it is better to still use cmd.exe /c here. Benjamin

Was there any user account showed in user accounts dialog? Could you test it again please? Error code showed there wasn't correct. Or just send me your install.ini. Thx Benjamin

Yes, but before many other complains about it here I think this will not take entire weekend to implement. Benjamin

Please can some one verify this? I'll test it on my Windows 2003 next days. Otherwise I need detailed bug report (turn off sending microsoft error report) and see my stack dump and so on. Edit: I checked it here on my server, there was no such problem. Seems not to be WIHU dependent. Benjamin

@my2001: Please send me a mail with your 2 install.ini and explain what you have done in detail. Benjamin

Let me clarify: workdir.x will only set current working directory during execution of the specified command, NOT before. Benjamin

That's not as easy as you think, but I'll change the code next days. Sorry for not beeing here last days, but I had 1 harddisk failure, it's damaged now and many data were lost. So I had no time to take a look at this forum. Benjamin

Yes, but since .msi files are not native windows executable files this isn't possible here. The same thing concerns batch files. But let me say, I'll rework some code by readin the "command interpreter" from registry. What workdir.x actually do and what not just read it by your self. http://msdn.microsoft.com/library/default....eateprocess.asp Take a look at "lpCurrentDirectory" parameter. workdir.x only sets the "current working directory" for the new running process i.e. after command.x is executed. This does not change the relative directory where WIHU searchs for application files, so it wont change %WIHU% or %CURDIR% environment variables! Benjamin

I fixed this bug now. Just test it again. Benjamin