When running with limited privilages, Shell Manager “Abalone” won’t add or update shells, despite having appeared to.
|Depends on||An error occurs when adding a startup item to the All Users group in StartupPN when running with limited privilages.|
|Bug report type||Non-fatal bug|
|Program affected||Project Nelson (v1.0 Build 020)|
If you try to add a new shell or provide the location of one that hasn’t been detected while running Shell Manager "Abalone" with limited privilages, it will set it as your shell, popping up with the message “Changes will take place when you next logon” (or launching the shell if it is the first time you have run it.) However, while your shell will have been changed to the selected program, the entry representing that program will not have been added or updated, as shown if you restart Shell Manager “Abalone”.
This occurs because the program paths for each shell is stored in the “All Users” registry (HKEY_LOCAL_MACHINE), and Shell Manager "Abalone" doesn't have the permissions to update it while running under limited privilages.
|Steps to reproduce|
|Workaround||In Windows Explorer or File Manager “Nemo”, navigate to the folder you installed Abalone to (usually C:\Program Files\MarkKB\Project Nelson.) Right-click the file labelled “Abalone” or “Abalone.exe” and click "Run as" (Windows XP) or “Run as administrator” (Windows Vista/7). If necessary, enter the username and password of an administrator. In any case, accept the dialog by clicking OK. Make the appropriate changes in Shell Manager "Abalone", and click OK. Run Shell Manager “Abalone” again with limited privilages to reselect the shell you want to use.|
|Status||WILL_FIX in v1.0 Build 021.|