MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically.
I submitted a patch for this... If (or when) it gets added to the main branch it will be possible to specify in the ini file what path to start the application in using "startin.<number>=<path>" Hopefully it should fix your problem. eg: [Development] command.0=cmd.exe description.0=Command Prompt - wihu path (default, reverse compatable) selected.0=1 command.1=cmd.exe startin.1=. description.1=Command Prompt - Relitive to install.ini file selected.1=1 command.2=cmd.exe startin.2=C:\ description.2=Command Prompt - Fixed Path selected.2=1 command.3=cmd.exe startin.3=%HOMEDRIVE%%HOMEPATH% description.3=Command Prompt - Enviroment (C:\Documents and Settings\<Username>) selected.3=1
I've already started implementing this (though the code on the wihu web site may be out of date) I just want some feedback on the idea ... I thought that it would be good if WIHU could build the tree of applications to install at runtime (not hard coded in the INI file). Here is my reasoning: To make a small tree with only 2 applications (and 2 add-ons) like this: . [x] Main . \- [x] Common Applications . |- [x] Textpad 4.7.3 . \- [x] Opera 7.23 . |- [x] ASpell 0.50.3.3 . \- [x] ASpell English Dictionary Currently your install.ini would contain something like this: [Main] command=* selected=1 description.0=Common Applications command.0=* selected.0=1 description.0.0=TextPad 4.7.3 command.0.0=.\Applications\Textpad\txpeng473.exe /S /v/qn /Reboot=Suppress selected.0.0=1 description.0.1=Opera 7.53 command.0.1=.\Applications\Opera\ow32enen753.exe /s selected.0.1=1 description.0.1.0=ASpell 0.50.3.3 command.0.1.0=.\Applications\Opera\Aspell-0-50-3-3-Setup.exe selected.0.1.0=1 description.0.1.1=ASpell English Dictionary command.0.1.1=.\Applications\Opera\Aspell-en-0.50-2-3.exe selected.0.1.1=1 If your going to keep your install files in subdirectory why not keep the ini section needed to run the install file in the same folder... And use the existing hierarchy in the file system can be used to help build the tree... that way you can delete, add or rearrange applications in your Install folder without having to keep the install.ini up to date.. So you could have your install.ini (with the users and environment etc) and have a small ini files located with each application. With my change you could have files arranged like this: \Install.ini Contains the normal users and environment configuration and a separate section to trigger search. eg: ; Search Sub folders for wihu.ini files [Main] findini=wihu.ini \Applications\wihu.ini Only the name for displaying in tree as a header eg: [Common Applications] Note: if this ini file was missing Textpad and Opera would be moved up the tree. \Applications\Textpad\wihu.ini Contains just enough to specify install of textpad eg: [TextPad] description=TextPad 4.7.3 command=txpeng473.exe /S /v/qn /Reboot=Suppress selected=1 \Applications\Opera\wihu.ini Contains just enough to specify install of opera and using the current nested syntax the spell checker and dictionary eg: [Opera] description=Opera 7.53 command=ow32enen753.exe /s selected=1 description.0=ASpell 0.50.3.3 command.0=Aspell-0-50-3-3-Setup.exe /silent selected.0=1 hidden.0=0 description.1=ASpell English Dictionary command.1=Aspell-en-0.50-2-3.exe /silent selected.1=1 hidden.1=0 Soo.... What do you think? Do you store installs in a tree of folders ? if so, how many folders/subfolders do you have ? (I need to get an idea of how much I would have to search) Do you think you it would be good if you could move, delete, add or rename files in your install folder and not need to update the install.ini?