BenjaminKalytta

I changed WIHU behaviour here, i.e. when /ini= is specified and /users= isn't specified, /users= will be initialiazed with new /ini= value. Benjamin

I know my manual isn't the best to understand ... it's very confusing. May be some one could help me to create an better manual in english language. But if you have any specific question KoppieKoffie, just ask here. Benjamin

Ok, I fixed this, was a bug here. @my2001: Btw. each operation got it's own index here Benjamin

@my2001: You're right. @kalavera: I'll of course implement such GUI specific things to modify/add/delete users.operation ... but let me release final 2.1 first. And of course, users.operation can be extended, just make suggestions what I should add there. Btw. I wont change rename.x ... it's just good as it is, in one line. Btw. what do you mean with random? You never can't login if you don't know your random password And btw. modifying already existing user account is still possible with WIHU ... only renaming them isn't possible. (May be I should take a look if the new password will applied) See Administrator example in [users] section. Benjamin

Sorry, I'm so stupid ... I forget to implement reading it from ini file. I fixed this. Btw. to cancel a shutdown in progress just start "cmd.exe /c @shutdown -a" to cancel this. Benjamin

See this Screenshot. It's possible. But note, this wont create a primary user, BUT it will create each user which is specified in [users] section (if any). Benjamin

Sorry, is fixed now. Benjamin

/UseCurrent skips user creation, but don't skip settings. You should use this switch. Benjamin

Yes, but that's no solution. We really need one who either translate this, or creates an own manual ... hehe may be I got the time to do this, but my english knowledge isn't enough to write a good manual. Besides wo fixes WIHU bugs then? Benjamin

The problem here is, that you missed to specify a command.0=program or command.0=* The same applies to your other 1st level commands. Benjamin

Yes opensurf you're right ... I missed to set UseCurrent=1 when reading this from ini file. Benjamin

Sorry, that's not possible. As the source is free just modify it for your purpose. Benjamin

Oh, don't be so pessimistic ... I won't change this again. Benjamin

Ohh, now I understand you. It's was showed in software selection ... this was NOT intended ... it's a bug. I'll fix this soon. Benjamin

May be in future versions I'll add an extra window where this operations can be edited. But not before final 2.1. benjamin

No command.x=* is always bold. But please tell me what you are intended to do? Benjamin

Will be added ... each other requests will be may be implemented in future versions. I want to release final version 2.1 next days. Benjamin

Yes it is bold to distinguish it from normal command ... if command.x=* is specified WIHU will recognize it as informational Header. Benjamin

Please use /Verbose=0 Benjamin

As I said ... I'll revise entire user account behaviour which causes the problem here. May be tommorow I'll release revised version 2.0.42.0. Just take a look at "Changelog" thread for alternative feature I'll add instead. Benjamin

Edit: Hmm, there are many problems with user creating settings ... I decided to remove entire existing user loading things. Benjamin

I fixed this bug. Thx. Benjamin

What speak against creating sub commands? command.0 and command.0.0 ? What I can do is to add a /supress=level switch, to hide sub commands description logging. Benjamin

No, INI Script ... sounds interessting, but hey, this isn't a scripting language . What I can do here is to add %OWNER%, %ORG% and other environment variables which correspondends WIHU GUI settings. Benjamin

What do you mean with ini instructions? Benjamin