[How-To] How and why to configure a shell replacement?

[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

 

 

[jrobbins50]

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 

[AudioPhil]

Hello

 

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.

 

Best,

AudioPhil

 

 

[pyro]

So I finally got around to installing Server 2019 GUI.  I did the shell replacement for Jriver.  How do I load service tool again to disable the shell and return to default?  Can the command be run from a remote desktop connection?

 

Thank You.

[AudioPhil]

Hi

 

Simply press Ctrl-Alt-Del to either load the task manager or ServiceTool directly. Then you can choose to revert back to default shell.

 

Best,

AudioPhil

[pyro]

Loaded task manager, selected new task, command prompt, maneuvered to C:\AO and ran service tool from this location this morning.

 

[AudioPhil]

You can also directly type "st" in the launch menu from the task manager to start ServiceTool

[mourip]

For anyone on the fence regarding switching to Roon server as their AO shell replacement for Windows 2019 I can heartily recommend it.

 

My system is much more open and transparent now that I made the switch.

[dminches]

On 1/13/2020 at 7:47 PM, mourip said:

For anyone on the fence regarding switching to Roon server as their AO shell replacement for Windows 2019 I can heartily recommend it.

 

My system is much more open and transparent now that I made the switch.

 

Do you set the shell replacement before or after running AO?

 

[mourip]

It has been a while but I believe that I ran AO first and then ran it once more to enable the shell replacement.

[doors.sl]

Hi @AudioPhil,

I tried to set Fidelizer Pro (F) as a Shell but i get this error when the system boot:Does anyone have a solution?

Im using Windows 2019 Core Server + Jplay Femto + Fidelizer Pro.

Thanks!

 

 

[jcn3]

On 7/21/2020 at 6:10 PM, doors.sl said:

Hi @AudioPhil,

I tried to set Fidelizer Pro (F) as a Shell but i get this error when the system boot:Does anyone have a solution?

Im using Windows 2019 Core Server + Jplay Femto + Fidelizer Pro.

Thanks!

 

 

 

i get that error -- it's a fidelizer issue, not ao.  it also doesn't matter -- everything works regardless.

[AudioPhil]

15 minutes ago, jcn3 said:

 

i get that error -- it's a fidelizer issue, not ao.  it also doesn't matter -- everything works regardless.

@Windows X, do you have an idea?

 

Best,

AudioPhil

[AudioPhil]

On 7/17/2020 at 10:33 PM, dminches said:

 

Do you set the shell replacement before or after running AO?

 

Do AO first. Then launch the ServiceTool to configure the shell replacement as you need it.

 

This might also be interesting for you:
https://shop.highend-audiopc.com/blogs/audiophils-blog/how-and-why-to-configure-a-shell-replacement
https://shop.highend-audiopc.com/blogs/audiophils-blog/customshell-as-shell-replacement

 

Best,

AudioPhil

[Windows X]

7 hours ago, AudioPhil said:

@Windows X, do you have an idea?

 

Best,

AudioPhil

 

Fidelizer has its own startup procedure and working fine since Windows Server 2016. Setting up Fidelizer Pro as default shell can cause issues with duplicated startup. I recommend to leave Fidelizer Pro with its own startup.

 

Regards,

Keetakawee

[beajuju]

Hi @AudioPhil,

 

I recently started using AudiophileOptimizer 3.0 and I am amazed by the results in terms of sound quality.I want to go even further, using the shell replacement option. However, before going in that direction, I would like answers to these questions please :

 

1. Do I need to strip Windows 10 pro if I use shell replacement?

2. To improve the sound quality, I installed the following software on my computer: AudiophileOptimizer (ultimate mode), Fidelizer Pro 8.6 and Minimserver 2.0. How do I configure the shell replacement with that these three applications?

3. My Music library is installed in a Samsung 960 Evo 2TB SSD drive. Will I need to go back to the Windows desktop to drop new music in my SSD drive?

 

Thank you so much for your help!

[AudioPhil]

Hello beajuju

 

Thanks a lot for the feedback and the questions

 

1. No, not needed. But a nice additional step to have a cleaner windows installation with a lot less of bloat.

2. Please see here: https://shop.highend-audiopc.com/blogs/audiophils-blog/how-and-why-to-configure-a-shell-replacement

3. No. There are various ways to achieve that goal after using a shell replacement. One of them would be this one (page 28 of the PDF guide):

 

Instead of launching ServiceTool like in the example above you would simply start "explorer.exe". This will launch the entire windows desktop "on-demand" so to speak.

 

Best,

AudioPhil

[beajuju]

Thank you @AudioPhil!

 

It seems to be a bug or conflict if I am using a Shell for Fidelizer Pro (See post 15 from @Windows X). What would be the most appropriate solution?

 

[AudioPhil]

23 minutes ago, beajuju said:

Thank you @AudioPhil!

 

It seems to be a bug or conflict if I am using a Shell for Fidelizer Pro (See post 15 from @Windows X). What would be the most appropriate solution?

 

 

I'm wondering a bit about @Windows X answer because the combination of Fidelizer and the shell replacement feature has been working well for years now. As far as I remember there is a setting within Fidelizer which does not cause itself to start after login.

 

Very best,

AudioPhil

[Windows X]

15 hours ago, beajuju said:

Thank you @AudioPhil!

 

It seems to be a bug or conflict if I am using a Shell for Fidelizer Pro (See post 15 from @Windows X). What would be the most appropriate solution?

 

 

Hi. Since Fidelizer Pro has its own startup procedure, setting up as AO Shell can cause conflicts. I recommend to use Fidelizer with its own startup procedure since Windows Server 2016 and newer has startup feature implemented now.

[AudioPhil]

5 hours ago, Windows X said:

 

Hi. Since Fidelizer Pro has its own startup procedure, setting up as AO Shell can cause conflicts. I recommend to use Fidelizer with its own startup procedure since Windows Server 2016 and newer has startup feature implemented now.

Hi Kee

 

This is no good advice sorry. Fidelizer is using a similar to "autostart" function while the shell replacement is a completely different approach with a big effect on sound quality. Therefore it's not really advisable to just stick to the built in autostart feature, but to rather disable this and use the shell replacement with all it's advantages.

 

Best,

AudioPihl

[beajuju]

Hi @AudioPhil,

 

Finally, I dismissed Fidelizer and chose to keep only AudiophileOptimizer with Autologon and minimserver shell replacement. My God!! The difference in sound quality is...HUGE! I had an Innuos Zen mini music server MK II and AO reach the same sound quality for a fraction of the price. It sound fabulous with my Lumin A1 with Leeds processing.

 

Does Windows server 2019 bring a significant improvement in sound? Is it complicated to install on an Intel NUC? I am not a computer geek but only an audiophile : )

 

[Windows X]

On 8/5/2020 at 2:13 AM, AudioPhil said:

Hi Kee

 

This is no good advice sorry. Fidelizer is using a similar to "autostart" function while the shell replacement is a completely different approach with a big effect on sound quality. Therefore it's not really advisable to just stick to the built in autostart feature, but to rather disable this and use the shell replacement with all it's advantages.

 

Best,

AudioPihl

 

Fidelizer has reliable startup procedure with highest privilege enough to cover all tasks required for the optimizations. I think it'd be better to use shell replacement on audio player software to have maximum access level on high impact process. Well, users can try and decide for best optimizations.