my2001

Oh my God!

Gosh! You're **** right!

Same here.

@Benjamin Another question: Are the spaces in front of and behind the equal sign " = " allowed? [Environment] DefaultProfilesDir = HKLM:SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\ProfilesDirectory

Is this above really your install.ini?? Because when you leave out all of the comments the following remains: Just wondering. *hehe* And unfortunately I can't help you very much with your problem, but I had it once, too: WIHU crashed right after I clicked OK and it ought to start it's working process. But this was because of my let's say broken Windows system that time. I reinstalled Windows and everything worked out well again. What I want to say: I _guess_ the problem isn't related directly with WIHU.

Okay, German manual for WIHU is ready and released. See first posting in this thread.

@KoppieKoffie Cool! B) Hhm, but do you already know my "little" manual?!? I gave Benjamin my manual and he'll probably put it on his page in brief. I'd, of course, love to see it translated into Dutch and English as well.

You mean that group-command thing?

Yeah, that's absolutely right.

Oh! This will probably sound a bit disappointing for you but German isn't very suited for being translated automatically. Its grammar, word formation and word order is just a little bit too complicated, what is almost the same for most other languages. I really appreciate your effort (!!!) but the German translation you provided isn't comprehensible, for example your word "can" wasn't translated as "kann", it became "Dose" which means "tin". And "screenshots" got something that makes you think somebody is gonna shoot your screen. *hehe* Those translating machines interpret the texts word by word and that unfortunately won't succeed. I re-translated the correct version of your English text automatically and here you see the results: "If you could create a HTML version of the complete German assistance, make I, what I can, these into English to translate. Although the screen photos on an English computer would have to be provided, I believed, to be able to master the remainder. One can always look after in World Lingo and Google can likewise translate." We'd need somebody who can speak German and there's certainly no lack but the problem is I guess the time and the willingess. So your initiative is really great!

Hhm, just waiting for Benjamin's reply and a short while after the manual should be avaiable for the public.

Yeah ... and with /NoRestartChange in conjunction with /SkipRestart you can finally prevent the user to change the restart setting.

I'm just curious. Maybe u 2? In another thread there's a little discussion about what program is better, offers more advantages, etc. Now here's the poll if you feel like voting.

Compression Bin Nice utility, although I only needed to re-compress two files for my unattended cd and made this by cmd line.

Just a note: presumably only a few days left until publication.

It often helps very quickly to take the trouble and find a solution on your own.

Oh, fine! This would be a nice thing in conjunction with the /beep=<seconds> switch.

WIHU has been added to the list as well. "It is an easy to use tool for account creation and software installation. It is intended to be used for unattended windows installations."

Yes, [users] and [users.Operation]-section must always be in the file which you specify with /Users=<file>. If you don't use /Users=<file> directive they have to be in the usual configuration file or the file specified by /INI=<file>.

maybe wanna look here: http://www.msfn.org/board/index.php?showto...ndpost&p=166795

Yeah, sometimes people behave in a strange manner.

Well, what I really wanted to say is that I don't think this thread is made for asking and answering specific questions. And I just couldn't believe that one really decided to try it anyway. But now that it has happened, go on ... I don't mind, I guess I'm going to retire soon from here. *hehe*

What the heck is this??? I hope you don't really count on an answer in this particular thread?! And by the way there isn't a single "?" in your message.

(deleted due to Benjamin's following answer)

It's a normal program, so it can be put everywhere where programs can bet put. Regarding cmdlines.txt: Don't put it in cmdlines.txt directly, instead call a cmd-file in cmdlines.txt and call WIHU from that cmd-file. Hope this helps, generally it should work. But due to restrictions in Windows, i.e. not everything is working at such an early installation stage, there might/will be problems related to user account configuration. Again: this is because Windows doesn't offer full functionality at this stage. So, what can you do? It's simple: from cmdlines.txt you can run WIHU and install software, but don't use WIHU at this stage for configuring user accounts (/SkipSettings). You can call WIHU later a second time (when Windows is fully loaded) and apply your desired user settings then (/SkipSoftware) with WIHU. Ah, I almost forgot: for a very brief help you might want to start WIHU this way: "WIHU /?" The advantage of having a seperate USERS.INI-file? Well, this depends on your own needs. Normally there is no need to put you user settings in another file than your installation settings. WIHU only reads the settings it needs, everything else is ignored. So if you tell WIHU to install software but not to configure user accounts (/SkipSettings), all user related settings are ignored, no matter in which file you put them. But some people prefer having their settings in two or more files, it's just a habit, sometimes they need it due to their system structure, etc. P.S.: Don't drink so much coffee, maybe this is useful, too.