Search the Community
Showing results for tags 'shell replacement'.
Found 3 results
The coming AO 3.00 offers a handy new feature called the "CustomShell". It is exactly what its name implies, you can create your own shell script which fits your needs for 100%. You can customize it to your own needs and finally set it as shell replacement using the ServiceTool's shell replacement feature. 1. Edit custom_shell.cmd in editor of choice 2. Thouroughly test your batch file so it does exactly what you want 3. Once verified all is working as expected launch ServiceTool 4. Select "Shell Replacement" and then "Custom shell" and reboot or log off and on again Detailed Step by Step Guide: In The C:\AO\Tools directory you will find a file called "custom_shell.cmd", highlight it with the right moose button and click on edit. Edit the batch file to your needs, you can add your own lines or combine several things from the other shell replacement cmd files you can find under C:\AO\Tools. Be sure to test your own batch file in detail so it behaves exactly like you need it. Save it under exactly the same name, „custom_shell.cmd“. Once you are sure it works perfectly fine for your needs, launch ServiceTool, select the shell replacement feature and press "F" to select your custom shell as shell replacement. Your custom shell will be launched after your next reboot or sign in. Feel free to post this thread if you need help shaping your own custom shell or want to share your ideas or launcher scripts with others Enjoy it, AudioPhil
A few years ago we introduced the "shell replacement" feature in our ServiceTool and since then we put a lot and continous effort into it. The ServiceTool in AO 3.00 now offers more than 35 different variations of the shell replacement, so why do we put so much effort and time into this little feature? And what after all is a shell replacement, and why should you use it in your setup? Let's start with a few explanations. A shell in the windows world is what you already know as your desktop environment or GUI (graphical user interface). It is your desktop, your start menu, all the basic functions you can see right after you log in to your windows machine. So basically this is the entire windows environment which gets loaded after the login. Of course there is a lot happening, many process and threads are started to present you the windows desktop and load all the features and functions of Windows. In the Windows Server world the shell can also have a different appearance, namely on Windows Server systems which are running in Server Core (core mode). On those setups you have no graphical user interface, all you will see after the logon is a command prompt window. It looks almost identical with the MS-DOS command prompt a few of you might still remember from days long gone. So a shell replacement is exactly what the name implies, we're going to replace the shell with something different. Let's say you mainly use Roon as your media player, wouldn't it be convenient having Roon launching automatically right after logon? Of course it would be convenient, but you could also simply put it in the Autostart folder right. So what's the difference? If you put in your Autostart Folder, Roon will just get loaded aside from the graphical user interface. It will be started together with the entire windows system and all its proccesses, threads and tasks in the background. But if you entirely replace the windows shell with Roon, only Roon and nothing else will be launched after logon. So the big advantage in this case is not the conveniece part of having it autimatically launched (you'll get that as free extra bonus ), the point of the shell replacment is to entirely bypass the entire windows desktop and just launch your media player of choice. This is not only very convenient, it'll reward you with a significant impovement in sound quality due to bypassing the entire windows desktop. Of course this works exactly the same way when you are on Windows Server in core mode, the difference in sound quality isn‘t just as big as it is on a system with a GUI. If you want to have even more convenience simply combine the shell replacement with the Autologon feature of ServiceTool. If you configure Autologon you will no longer have to press ctrl-alt-delete to enter your password, your machine will boot and logs iteslf in automatically. When you have additionally configured a shell replacement the media player of your choice will launch right after the automatic logon. So these two features basically transform your computer into a HiFi device. Simply press the power button and everything else will happen automatically, and you get a massive gain in sound quality! List of all available shell replacements in ServiceTool 3.00: JRiver Media Center 17 - 25 (both x86 and x64) Bug head emperor Total Commander Foobar2000 TIDAL Fidelizer Pro HQPlayer HQPlayer NAA Roon RoonServer RoonBridge Roon combined with HQPlayer RoonServer combined with HQPlayer AudiophileShell MinimServer MediaMonkey muso Kodi Alchemy Custom Shell Focusrite RedNet Control 2 Command Prompt Especially interesting is the new "Custom Shell" feature of ServiceToot. It allows you to create your own shell replacement which fits your needs 100%. See more details about this here -> https://audiophilestyle.com/forums/topic/56327-how-to-customshell-as-shell-replacement/ Of course a shell replacement can also easily be reversed using the ServiceTool. Just launch it again, select the shell replacement feature and select "R" for "Restore default shell". No matter if you where in GUI or core before, ServiceTool will automatically restore the right default shell for you. Enjoy it, AudioPhil
The AudiophileOptimizer 3.00 brings a completely new module called the AudiophileShell. It is a launcher tool which makes handling of several tasks a lot easier, especially if you are in core mode. You can do simple tasks like starting the command prompt, PowerShell, the AudiophileOptimizer or ServiceTool as well as reboot or shut down your music server. Of course, you can also launch the device manager, the sound control panel or SCONFIG (en-US core only). There are two ways of using it, you can either use it on-demand by typing "as" in a command prompt window or you can set it as shell replacement using the ServiceTool’s shell replacement feature. Depending on the Windows version you run and the mode you are in as well as other factors as like if FoD is installed or not, it will show more or less available options. This screenshot shows the AudiophileShell on Windows Server 2019 in core mode with Features on Demand (FoD) & WASAPI installed. Enjoy it, AudioPhil