BenjaminKalytta

Yes everything will be possible, I'll describe in detail later how to do this. No, at this time it isn't possible to delete a user in [users] section. This is currently only possible in [users.operation] section. This will be changed in version 2.1.8.0. I'll keep [user.operations] until at least newt main release. This is possible at the moment. You have to combine /UseCurrent and /Admin= switch. In new version 2.1.8.0 you have to select "[x] Use currently logged on user" and create a new account "Administrator" in second dialog. Why not? User account will disabled then on next logon only. Benjamin

I decided not to add this to UI because once I also said that this should be treated as temporary solution. It would be much nicer if this could be done with existing interface. Im currently working on it. What do you think about it? However, users operation would still be possible. Benjamin

First, users may call WIHU from cmdlines.txt for creating user accounts and modifying it's profile data (shell folders and environment variables for example) which wasn't possible till now. Primary user however can not be set here, i.e. creating new account and use this as primary user isn't possible at this stage. Secondly, folder security attributes are now Windows conform, i.e. there shouldn't be any problems any more with file security settings. There is another thing that was added, which wasn't mentioned in changelog. WIHU will always create new user profile directory in the form: %DefaultUserProfiles%\%UserName% %DefaultUserProfiles%\%UserName%.00000001 ... %DefaultUserProfiles%\%UserName%.99999999 if already exists otherwise. Profile directory creation will not be dependend on Windows any more. I could explain this in detail, but this isn't significant here to explain because these are internals. Benjamin

Date: 03.09.2004: Version 2.1.8.0 Fixed some bugs from 2.1.7.0 Added new ini [users] keyword deleted.x to delete existing user accounts. Added new Password.x meaning. By default password.x will always reset user account password if not specified. To keep current password one have to specify password.x=* To modify existing accounts from WIHU user interface just create a new account and type in the existing account name. After pressing "OK", new user will be initialized by current user settings like comment and full name etc. After that this account may be edited as usual. User Context Menu "Remove Entry" was added which removed a specified entry from user account list. "Delete user account" will mark account as deleted only which is undoable by unchecking this menu item. Date: 03.09.2004: Version 2.1.7.0 "Secondary Logon" Service isn't needed any more to modify new user account profile. Old user account profile loading interface was replaced by a much more reliable one which isn't dependend on LogonUser any more. Registry Key and Folder Security Attributes (NTFS Access Control Lists) settings were improved. This may moves arround certain file security (NTFS) concerned problems.

Yes, I'll add this as I said. But Im currently working on User Account Creation Interface which will be changed to be more relieable. Benjamin

Please be more specific. Which Windows Version do you use, is there any error message when you double click on it, if you double click on other exe files did they start (may be a virus modifed the registry ... happens often), may be file is corrupt, try to redownload WIHU. Which unpacker did you use to unpack the ZIP file? Benjamin

No DEP isn't the problem, I didn't disabled it and it worked. There must be another problem, may be this isn't a WIHU problem. Benjamin

The executable I provided is independent of your file btw. It's just if some one needs such a tool. No sorry, not really Benjamin

Of course, as many as you want Benjamin

Here, I created an executabler re-checksumer to correct checksum of modified executable (sys, exe, dll) files. Btw. my current tcpip.sys version is 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158), your's is 5.1.2600.2505 (xpsp.040806-1825). So whats the difference here? Why is you version higher, or did you change this? Benjamin Kalytta resum.zip

@nivek7: When you run WIHU from within Windows (after installation) with the same settings and install.ini, does it also crash then? Otherwise, is "Data Execution Prevention" on or off? Btw. in your settings ini, NO user will be created because the one and only user start with index 1, which isn't possible here. [environment.0] will also be ignored then, remains [settings] section. Benjamin

Just yesterday I also reinstalled Windows XP 32 Bit on my AMD 64 system. WIHU didn't crashed there. Please send me your install.ini and mention me when and from within you called WIHU (GuiRunOnce, cmdlines.txt etc.). Benjamin

Already done. Please use key.x.n for this purpose! See Changelog Thread for example. Already done. Benjamin

And indeed they have Very nice if you get time to do this. Benjamin

Yes this group.x command. Usage example can be found in changelog thread. Benjamin

@pastl: As you can see it at my changelog this was already added yesterday. Benjamin

WIHU will not prevent Windows from creating any user account. You may use WIHU only to modify or delete some existing Windows accounts. Benjamin

I don't know when RunOnceEx.cmd is called, but in case it is the same as GuiRunOnce there is no restriction calling WIHU. And yes, with /NoRestartChange you can prevent users from disabling restart. WIHU restarts the system by default. Benjamin

I correct my self: Creating users at this stage is possible but logon isn't possible, i.e. settings user shell folder and user environment variables and also installing software as this new created user isn't possible. Btw. I use [GuiRunOnce] section of winnt.sif to start WIHU. Benjamin

At this stage WIHU can't create and logon newly created users because system service "secondary logon" isn't started at this time. Please use /SkipSettings switch here and use software installation only. Benjamin

I presume here you are using windows 2000. if yes, there are problems when using WIHu in Windows 2000. if not please also send me your entire log file (/log=logile.log) Benjamin

I added On Screen Display for this purpose, just download the newest version to use this. Create OSDText in [settings] section to override default text. Please note, %d is used as a placeholder for the remaining seconds. Benjamin

Ok, I'll add this. Benjamin

Date: 30.08.2004: Version 2.1.6.0 Added "Secondary Logon" Service detection which is usefull if WIHU is called from within cmdlines.txt to prevent a user from installing software under secondary account which will fail at this state. Date: 29.08.2004: Version 2.1.5.0 description.x key may also contain environment variables now. Example: [environment] WinVer=HKLM:SOFTWARE\Microsoft\Windows NT\CurrentVersion\CurrentVersion [Application] description.0=Windows Version %WinVer% specific things command.0=* Date: 28.08.2004: Version 2.1.4.0 bug in hidden=0|1/collapsed=0|1 was fixed. Date: 27.08.2004: Version 2.1.3.0 Group (Option) Control behaviour was added in software selection control. For this purpose a new keyword Group.x=0|1 was added. This keyword can also be used at level 0. Example: [Test: Option-Group] group=1 command.0=cmd.exe /c @echo Option 0 command.1=cmd.exe /c @echo Option 1 command.2=cmd.exe /c @echo Option 2 description.0=Option 0 (will be called in Windows XP by default) description.1=Option 1 (will be called in Windows 2000 by default) description.2=Option 2 (will be called in Windows 98 by default) selected.0=1 selected.1=1 selected.2=1 key.0.0 = HKLM:SOFTWARE\Microsoft\Windows NT\CurrentVersion\CurrentVersion?=5.1 key.1.0 = HKLM:SOFTWARE\Microsoft\Windows NT\CurrentVersion\CurrentVersion?=5.0 key.2.0 = HKLM:SOFTWARE\Microsoft\Windows NT\CurrentVersion\CurrentVersion?=4.10 Date: 24.08.2004: Version 2.1.2.0 On Screen Display was added which shows the time left for user input before autoinstall/autoexit operation. This text is customizeable in [settings] section by specifying something like OsdText=%d seconds left Date: 24.08.2004: Version 2.1 (final) Existing user profile data (environment variables and shell folders) will be loaded now and may be modified within WIHU GUI. Bug in %ThisProfile% and %ThisHome% was fixed. If user didn't specified profile.x or home.x in [users] section, %ThisProfile% and %ThisHome% if used in software installation sections were not initialized with correct paths.

Thx at the_spide for his suggestion and patch. I added "WorkDir.x" key which could be used here to specify working directory. Please note, relative directories are relative to WIHU application directory! You may use %INIDIR% or %CURDIR% varaible to override this. Benjamin