System Requirements ---------------------------------------------------- Windows 7 x86 or Windows 7 x64 with default shell (i.e. Windows Explorer.)
Note: not tested on Windows Server 2008 R2.
Features ---------------------------------------------------- 1. Change your start orb WITHOUT changing explorer.exe. This prevents unnecessary UAC prompts. 2. Choose different start orb for each user. 3. DPI-aware.
Install/Uninstall Guide ---------------------------------------------------- Uninstall of version 1.0: run the loader (renamed to explorer.exe), press 'Unload' button, and delete it. Current version is not compatible with ver. 1.0, so uninstall old loader before using current release.
Install of version 1.1: run the loader (w7soldr.exe in the zip, and you can rename it as you want), check 'Options' > 'Enable start orb loader' and press 'Save changes' button. Read usage section for details.
Uninstall of version 1.1: run the loader, uncheck 'Options' > 'Enable start orb loader', uncheck 'Options' > 'Shell integration' and press 'Save changes' button. This will restore all changes done to your system. Delete the loader then you're done.
Summary of Usage (Check details in readme.txt!) ---------------------------------------------------- 1. Extract w7soldr.exe and run w7soldr.exe. 2. Check 'Options' > 'Enable start orb loader'. 3. Press 'Browse' button to choose the location that contains start orbs you want to use. 4. Choose a start orb you want to use. 5. Press 'Save changes' button to save changes.
* Checking 'Options' > 'Shell integration' appends a menu item labed 'Start orb' on the context menu of desktop background.
* .resources files are language files. If there's no .resources files, English is displayed by default. See Localization Guide for details.
Yes, it is a false positive. If the loader is set enabled, it extracts a loader for the Windows Explorer into that location. Well, a trojan virus typically does a similar thing. What is extracted by the virus may be a copy of itself, which is harmful to the system. Your BitDefender guesses from this behavior, that w7soldr is a trojan virus.
I'm really impressed. I looked a long time for a way to customize the Start Orb without modify Explorer (because this way generate a lot of UAC alerts, as you said in the ReadMe file). Thank you very much for that!
I've something to ask. I'm working on a theme for Windows 7 (using the official Aero theme, but with other changes which do not modify system files). I want to make the installation fully automatized, and also to add a custom Start Orb. I know what your software does to change the Orb. Could I integrate your "Windows 7 Shell Loader" (the explorer.exe file created in Windows\System32) into my installation file? I will credit you without problem. Thank you in advance.
Note that UAC popups are also generated by modified shell32.dll, when you copy/move some files. It is difficult to hack them because dll files can be dynamically loaded/unloaded into the memory while exe files are loaded into the memory just once. Also dll files can be shared among several processes.
I tried to redirect copy/move operations so that the modified resources of shell32.dll are still being used and the operations use the unmodified copy of shell32.dll to solve the UAC popups, by modifiying the registry. Unfortunately I failed I should have modified more registry keys.
Currently I am not working on this project. =Kishan-Bagaria adopted this memory patch method to his program and he is still active. If you need to get some help, you may ask him.
BitDefender has blocked a virus!
Virus Name: Trojan.Generic.6493520
Accessed by: w7soldr
Loacation: C:\Windows\System32\explorer.exe
This is a false positive and is safe right?
I've something to ask. I'm working on a theme for Windows 7 (using the official Aero theme, but with other changes which do not modify system files). I want to make the installation fully automatized, and also to add a custom Start Orb.
I know what your software does to change the Orb. Could I integrate your "Windows 7 Shell Loader" (the explorer.exe file created in Windows\System32) into my installation file? I will credit you without problem. Thank you in advance.
It is difficult to hack them because dll files can be dynamically loaded/unloaded into the memory while exe files are loaded into the memory just once. Also dll files can be shared among several processes.
I tried to redirect copy/move operations so that the modified resources of shell32.dll are still being used and the operations use the unmodified copy of shell32.dll to solve the UAC popups, by modifiying the registry. Unfortunately I failed
Currently I am not working on this project. =Kishan-Bagaria adopted this memory patch method to his program and he is still active. If you need to get some help, you may ask him.
i browse
i select the folder
no start orbs appear in the location allotted
--
<insert cryptic quote from famous person here>