Jump to content

Rate this topic

Recommended Posts

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
  • 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,




ıllıllı [  ...AO 3.00 IS HERE... ] ıllıllı


Shop | Core Audio Music Server | Reviews | Reference System | AudiophileOptimizer 3.00 | PDF Guide


Share this post

Link to post
Share on other sites

Phil — I am using my server to run Roonserver for Roon and also JRiver MC25 for remote access outside of home to my music library through JRemote. I note that in my AO 3.00 install, Roon as a shell is available, but not Roonserver separately. Now, I selected Roon as my shell and the result is a black screen with only the AO menu in the center. This looks like the Roonserver shell (which is fine) and not the Roon shell (which I presume would show the Roon GUI that I don’t need on the server anyway?). Wondering, however, if selecting JRiver as the shell would still allow access to the AO menu and produce better sound than with Roon/Roonserver as shell. 


Separate question on WS2019 Standard GUI mode, which is what I have installed. If I disable network related services in AO — which you describe as important to good sound — you are saying that my Synology NAS (where my music is located) will no longer function?  No workaround for that?  I’m also finding that even with network related services running still, my NAS connection is not persistent. That is, it requires manual re-entry of the NAS password, despite selecting to save password, upon any server reboot.  I used “/persistent:yes” in my setup. Thoughts?  JCR 

Share this post

Link to post
Share on other sites



Of course RoonServer is available as shell replacement? Much more than that, see the entire list of Roon shell replacements here:




Either way, for what you want you need to create your custom shell. See detailed steps here -> https://audiophilestyle.com/forums/topic/56327-how-to-customshell-as-shell-replacement/


A mapped network drive does still work even when you select to disable network related services. But you have to use static IP configuration and need to map the drive using an IP instead of a hostname. The password issue I have never heard of, sorry.






ıllıllı [  ...AO 3.00 IS HERE... ] ıllıllı


Shop | Core Audio Music Server | Reviews | Reference System | AudiophileOptimizer 3.00 | PDF Guide


Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Create New...