1. if a path is passed via the arguments (IE --force-install 0 [otheroptions] --args-list [ev. otherletters; see readme]p [path to bg1], that path is checked and used (no prompt whether it is correct)
2. WeiDU, then, looks into the system registry for the path where BG1 is installed; if that is found, it prompts for comfirmation; if the user answers "n", it goes to step 3; if the user introduces his path here (eg input redirection), it will ask the question again and again until EOF is reached.
3. The user is prompted for his full path; only this step is repeated in case the path is incorrect.
So, the number of prompts could vary depending whether the path to BG1 is present in the registry, and whether the check for all game files finds them all.
The safest way is to pass it via arguments, eg putting the path inside a variable before and using --skip-at-view --args-list ops [variable with path] (that would even allow you to remove BGT from the smoothpack, or what's the name of that tool which removes all VIEW commands).
Besides, you can also use other options inside the arguments, EG --args-list ops [path] will move everything to the override folder (o; the question whether to biff will NOT be asked), don't show the final readme (s), and read the path from the second argument (2); you can use any combination of those two letters provided they are not separated by spaces.
Edited by Turambar, 27 February 2012 - 01:27 AM.