BenjaminKalytta

You have also to select parent items like description.2=Codecs et filtres command.2=* selected.2=1 Only if a parent item is selected it's sub items will be executed.

With command line you can't create any user except one primary user. You have to create an install.ini (http://www.kalytta.com/wihu.manual.php). Just take a look at the example install.ini. One hint, you have to create a [users] section within this initialization file. Benjamin Kalytta

Can you send me the error log? There shouldn't be any errors, only warnings. Benjamin

Your last sentence was perfect Currently the language is selected dependent of system language, but I added a /language=... switch to manually select the language. Benjamin Kalytta

So, languages.ini is now mandatory. It contains [de] and [en] section for german localization and english localization. If you want, you may send me the translated languages.ini. It shouldn't be too difficult to translate. Search order for languages.ini is following: 1. WIHU searches in working directory 2. WIHU searches in application directory (%wihu%) languages.ini may be saved in UNICODE or ANSI format. UTF-8 isn't allowed. Benjamin Kalytta

Im using Visual Studio 2005 (version 8.0), so you should be able to open it. May be one could port it to MinGW GCC? Benjamin Kalytta

Hehe, yes you are right, but only basic things like "J'mapelle Benjamin" or "J'habite au Allemange à ..." ... or something like this. Don't know if I succeeded the french exam. I need to add [en] section to the languages.ini, otherwise you won't be able to translate it because you have to translate german [de] messages. But after that, you're welcome to translate it. Benjamin Kalytta

Please download the final version WIHU 2.2. /TopMost switch was added there. Localization entirely changed, each localized string is now saved in a seperate languages.ini file which should make localization easier and less time consuming for me. I'll stop major development here as I wrote before, but may be I'll fix some bugs (if there) in this new version 2.2 because 15% of the code is new, so there is a chance that there are some bugs inside. Benjamin

[u]26th February, 2006: 2.2.0.3[/u] - Bug fix, Locale wasn't set in WorkerThread which causes WIHU not to display Log entries. [u]20th January, 2006: 2.2.0.0[/u] - This is the final version of WIHU - Known bugs were fixed from previous versions - Localization changed against previous version. Localized strings are now saved in seperate [b]languages.ini[/b] - /TopMost switch was added to set WIHU on top

Thank you very much Maelstorm, it seems to be a problem with older cpu's. Please try my new version WIHU 2.2 (Final), the bug should be fixed there. Benjamin Kalytta

Please can you show me your install.ini? Benjamin Kalytta

This progress bar will not be used currently, it was planed to add detail progress bar to show estimated remaining time of one application setup and also for internal operations like @mkdir, @copy, @rename and so one which however isn't implemented yet either. Benjamin Kalytta

Take a look at wihu.exe /? There is a switch /SkipRestart which unchecks the restart button by default. With /NoRestartChange you'll disable the check boix it self. Just try /AutoInstall=seconds Benjamin Kalytta

Just save your install.ini as UTF-16 (Unicode) Text file. Then you may use each character. Benjamin Kalytta

Google Translator is really awful, I'll provide you with the hand translated mail. Bad Kreuznach, 31th December 2005 Dear users of my "Windows Installation Helper Utilities", as you may noticed, there weren't any major changes on my tool since long time now. Because of private and temporal reasons Im not able to continue development of my tool. There are many things that can be improved. I made a list with things to improve, among other things the use of XML instead of INI. There are many people interessted in this tool and many helped actively to improve it.Even now some people still seems to use it although there are several similar projects, which are even easier to handle. Therefore I tried to move this project to Sourceforge, but they declined it. However I don't know the exact reason why. Some time ago, I write a similar letter, but because of objections on the part of the users I decided not to stop development. But since this time, I hadn't any time to considerably advance my project. It make no sense to pretend still continue developing. Futhermore I couldn't keep my promise - because the reasons I stated above - I gave in connection with the development of the project. I'll apologize for this in public. Futhermore, I think towards Windows Vista, it make no sense to continue this project or to do a rewrite as I aimed once. This tool was explicitely optimized and developed for Windows XP and therefore it won't work on Windows Vista. Nothing speaks against continue using this tool in Windows XP. Except for some known not critical bugs this tool is in stable state. Also the website will be still available. Every one who wants to continue this project is welcome to do this without almost no restriction. The only request which I have is only that the name of the original developer (thus I) is recognizable in the source code as well as in the Binary. Otherwise the source code is freely available and changeable. How did it originally come to this project? Approx. 1 year ago there was a report about "Unattendend Windows installation" in the german computer journal c't. I naturally always wanted this, because I installed Windows every few days anyway and I did not want each time to sit beside it around to enter whole data during installation. In this connection: I ask myself what is the intention of Microsoft to use such obligation registration. Afaik, after third on-line registration you have to call Microsoft by Phone. Thus as private user I had to call Microsoft every few days. Such is unreasonable! There should be a special computer tinker edition of Windows which need only registred once - if at all Anyway, I would have an option to select and install certain application automatically. For this reason the project was developed. The whole auxiliary functions such as user account creation, shell folder administration etc. was developed because of user wishes, I personally never needed one of this features. Thus hereby I thank you all again who advanced the project and supported me best wishes Benjamin Kalytta

How do you want to hide application setups other than using silent switches? Other than that makes no sense because the application will present some windows the user should interact with. Why do you need asynchronus commands? The can lead to problems, because many setup installers don't accept 2 installations running the same time, esspecially MSI ones. Top most isn't a problem ... should there be a switch (ini settings) or should WIHu always top most? Benjamin

If WIHU is called at T-12, there are some restrictions. "System" account is used for application install which means: 1. Every registry change goes to Default user profile 2. Some applications which requires administrator privileges don't work This also means, you can infact create new user accounts during T-12, but you can't set a primary user i.e. you can't run your setup's under one of this newly created user accounts. So I would recommend to start Wihu in [GuiRunOnce] section.

How does the log file look like? Are you sure you have access to \\bildung.deg\Netzlaufwerke$ ? Benjamin

Of course, path names with spaces are allowed. MAC-DUFF, where do you use spaces? Is "\\Notes 6.5.4de" a computer name? Since Windows doesn't support spaces in computernames, this case can't be handled, but Im not sure, may be this also works. Please can you post your INI file and the error message you'll get. Please run WIHU with /verbose=3 and /log=wihu.log switch. Benjamin

Yes, from time to time Im working on it;) It's already 80% ready for some weeks now. But I've to integrate it into WIHU. If I'll take time I''ll work on it. Benjamin

Just add a command.x= * and than command.x.0 = Microsoft Office 2000 and so on. Benjamin Kalytta

No there is now way doing this with WIHU. Benjamin Kalytta

Just use /SkipSettings switch. Benjamin Kalytta

No sorry, you can't change the window title. Benjamin

2nd November, 2005: 2.1.25.1 - Fixed bug in user creation: Passwort wasn't set after user was created 6th November, 2005: 2.1.25.2 - Fixed: User password expired wasn't set - Fixed: User created in UI never got admin rights