BenjaminKalytta

Ok, habe den Bug gefixt. Benjamin Kalytta

I'll create a more advcaned help the next days.

Autologon is fixed now. You may specify either to disable auto logon, to enable or to leave it unchanged (default) [tri state check box]. I've created an autologon tool so you may change your invalid autologon settings caused by WIHU. You'll find this tool at my homepage in download section. http://www.kalytta.com/autologon.zip Benjamin Kalytta

1th July, 2005: 2.1.19.8 - Fixed some bugs in user account creation dialog - Changed "autologon" settings (tri state check box) - Added [users] Profile default settings

Yes it was also my opinion after I started my system today. I'll fix this in this way. Benjamin Kalytta

I've tested it but it wasn't here. New account was only member of "Users" Group. Of course this intended. Administrators includes all rights of Users. Benjamin Kalytta

Of course this is possible. [users] Profile = c:\Profiles\%Thisuser% ... should work. Update: It seems that I removed this feature some day ... don't know what my reason was. If you want I could add this again. Update 2: Just try version x.7, I added it again. Benjamin Kalytta

Your example code would set default shell folders to specified location, i.e. each new created user account will use this as default settings instead windows default. If this is your intention, you've to create at least one account to use this settings. Of course you could set only some of the shell folders to new locations. Prefered locations are the Windows Desktop, Personal folder and may be also application data folders. You are right, that's the way to do it. Benjamin Kalytta

I added 3 help tool tips on first account page.

I've created a changelog thread here in this forum. There you'll find every news about WIHU. However, there are not much new features in the last months. Benjamin

You have to use help.x not helptext.x. With helptext.x you may directly specify the helptext. Benjamin Kalytta

15th June, 2005: 2.1.19.4 - added ?version.x, ?productversion and ?fileversion comparison. - fixed some bugs concerning environment variables which wasn't properly set

Switches: /HasGaps: allow uncontinuous keyword indizes in ini file. (Note: loading takes more time) Features: ?productversion and ?fileversion tests are allowed, also ?version.x wherby x can be: Comments, InternalName, ProductName, CompanyName, LegalCopyright, ProductVersion, FileDescription, LegalTrademarks, PrivateBuild, FileVersion, OriginalFilename, SpecialBuild Note, ?version.ProductVersion isn't the same as ?prouctversion. ?version.ProductVersion is the raw version, i.e. is read out as it is without parsing. Some executables are broken which mean, reading version information with default Windows API function isn't possible. One example of such is winrar.exe Benjamin Kalytta

The problem here is as follows: Each executable file may contain 4 fields of version information, and not all of them are filled with content: 1. There are two fields which only store an integer version of the version number (one for product version and one for file version) 2. There may be one or two "string version" fields named "ProductVersion" and "FileVersion" which may also contain data but needent be the same. Problem is, what if integer version (which is always) present is different from "string version"? Ok, I added ?productversion and ?fileversion to explicitely select the one which is requested. Limitation: 1.2d for example however will be converted to 1.2.0.0 ... i.e. only integer values are allowed. Benjamin Kalytta

Thank you FierceRecon. I fixed this now. Also %USERNAME% may be used instead of %ThisUser% only. Benjamin Kalytta

Changes in Version *.2: /HasGaps switch may be used to support ini files with uncontinuous keyword indizes. But, note, this will slow down ini file loading process. Benjamin Kalytta

No this isn't a bug since each number have to be continuous numbered. If you remove .0.1 you have to fill the gap between the next entry. Recommended procedding: Deleting item 1.1 from List Before Example: 1 1.0 1.1 1.2 1.3 After deleting Example: 1 1.0 1.2 1.3 After adjustment Example: 1 1.0 1.2 1.1 If I remove this restriction, it would mean that loading ini file would take very long (some seconds) because each level s recursively loaded.

Please, just read the threads here. There you'll get the answer for all your questions. Benjamin Kalytta

You may use helptext.x = some text or help.x = some. rtf file

wmp.dll.version = %SystemRoot%\System32\wmp.dll?version Above is only an example code how to read out the version of wmp.dll. The version value in form of "1.2.3.4" is than stored in environment variable wmp.dll.version. Just delete it. Because "Group" isn't an environment specific thing, you have to add Group = 1 into [users] section, whereby Group.x = 1 only add admin rights to the user with index "x". Benjamin Kalytta

Home = %Personal% is ok, but either you should specifiy personal.x = d:\%ThisUser% or you should initialize "Personal" in [environment] section like personal = d:\%ThisUser% [environment] personal = d:\%ThisUser% [users] Home = %Personal% FullName = WIHU Test User user.0 = test user.1 = test2 Benjamin Kalytta

Yes, just try it without this scripts.

CODE 1 doesn't mean anything, just ignore this. What problems with autologin do you have? No there is no option, you have to reorder everything;)

What error did you get? Is the path in second example correct? is "BestCrypt" really a sub directory of WIHU executable directory?