Classic Shell
http://www.classicshell.net/forum/

Run as a Service?
http://www.classicshell.net/forum/viewtopic.php?f=13&t=7266		 Page 1 of 1
Author:  beatyas [ Tue Jan 17, 2017 3:27 pm ]
Post subject:  Run as a Service?
I did NOT exhaustively seek out every possible forum post... Not going to...

Is there a way to get Classic Start to run under the \SVCHOST.EXE\RUNTIMEBROKER.EXE in Win10 by default...? It should not be a current user explorer.exe sub-process. Needs to be a local machine 'interactive' one... If you pull down a copy of the SysInternals suite, you can see the security ownership relationship of 'where' ClassicShell is running... At least on my machine, if it runs as a job process under RUNTIMEBROKER.EXE, it seems to respond much faster, than as a user-admin account...
Sorry if this does not make sense...
Author:  Ivo [ Tue Jan 17, 2017 3:31 pm ]
Post subject:  Re: Run as a Service?
All of the start menu functionality runs inside the Explorer.exe process. The ClassicStartMenu.exe process is not important for performance. You can even kill it and the menu will still work.
Author:  beatyas [ Tue Jan 17, 2017 3:32 pm ]
Post subject:  Re: Run as a Service?
Ivo wrote:
All of the start menu functionality runs inside the Explorer.exe process. The ClassicStartMenu.exe process is not important for performance. You can even kill it and the menu will still work.



Not true... Hold on.. graphics incoming...
Author:  beatyas [ Tue Jan 17, 2017 3:40 pm ]
Post subject:  Re: Run as a Service?
beatyas wrote:
Ivo wrote:
All of the start menu functionality runs inside the Explorer.exe process. The ClassicStartMenu.exe process is not important for performance. You can even kill it and the menu will still work.



Not true... Hold on.. graphics incoming...



Blocked from inserting images...
Author:  beatyas [ Tue Jan 17, 2017 3:44 pm ]
Post subject:  Re: Run as a Service?
beatyas wrote:
beatyas wrote:
Ivo wrote:
All of the start menu functionality runs inside the Explorer.exe process. The ClassicStartMenu.exe process is not important for performance. You can even kill it and the menu will still work.



Not true... Hold on.. graphics incoming...



Blocked from inserting images...



You can run the menu 'manually' as a system user and it will nest under \WININIT.EXE\SVCHOST.EXE\RUNTIMEBROKER.EXE as a process image... runs super-quick that way...
... Under the user EXPLORER.EXE.... seems to run slower...
Author:  Ivo [ Tue Jan 17, 2017 5:48 pm ]
Post subject:  Re: Run as a Service?
The code is designed to run inside the Explorer process. Otherwise some features will not work. For example the part that handles the Win key or replaces the start button.
Author:  Anixx [ Sat Feb 04, 2017 10:43 am ]
Post subject:  Re: Run as a Service?
Ivo wrote:
All of the start menu functionality runs inside the Explorer.exe process. The ClassicStartMenu.exe process is not important for performance. You can even kill it and the menu will still work.


What this process is for then? Why not just to kill it every time?

Is it possible to run Classic Shell without this process using some options?
Author:  Ivo [ Sat Feb 04, 2017 10:51 am ]
Post subject:  Re: Run as a Service?
It is the process that injects the DLL into Explorer. It also watches for Explorer being restarted to do the injection again. And it does some other non-essential work.
Author:  Splitwirez [ Sat Feb 04, 2017 11:32 am ]
Post subject:  Re: Run as a Service?
Ivo wrote:
It is the process that injects the DLL into Explorer. It also watches for Explorer being restarted to do the injection again. And it does some other non-essential work.


Question...does it assume that explorer is being run from a specific location? Because I noticed that, when I ran Windows Vista's explorer on Windows 10 out of a subfolder of the Documents userfolder, Classic Shell didn't do the thing. (And this was an old version of Classic Shell, from before Vista support was removed.)

Any workarounds? Or better still, ways to get a newer version to work on Vista's explorer on Windows 10 in this configuration? O:
Author:  Ivo [ Sat Feb 04, 2017 11:42 am ]
Post subject:  Re: Run as a Service?
The Explorer that's important is the one that runs the desktop and the taskbar. Individual Explorer windows that show specific folders are ignored. That's of course if we are talking about the Classic Start Menu.

If you are talking about Classic Explorer, then no, the location of the EXE doesn't matter as long as it is called "explorer.exe". However based on the detected Windows version, certain behavior is expected from Explorer. If you are running the Vista explorer.exe on Windows 10, you are deep into unsupported territory :)
Author:  Splitwirez [ Sat Feb 04, 2017 11:47 am ]
Post subject:  Re: Run as a Service?
Ivo wrote:
The Explorer that's important is the one that runs the desktop and the taskbar.

That's the one I meant. I was using Vista's explorer for Desktop/Taskbar and 10's for individual windows. All I want is any kind of Start Menu on Vista's taskbar... (the built-in one doesn't work on 10 for [INSERT REASON HERE] .-. )

Ivo wrote:
If you are talking about Classic Explorer, then no, the location of the EXE doesn't matter as long as it is called "explorer.exe".

Classic Explorer isn't really of any concern to mem for reasons stated above.

Ivo wrote:
However based on the detected Windows version, certain behavior is expected from Explorer. If you are running the Vista explorer.exe on Windows 10, you are deep into unsupported territory :)

...uh...that's basically your way of saying "good luck, you're on your own", isn't it? ._.
Author:  Ivo [ Sat Feb 04, 2017 11:57 am ]
Post subject:  Re: Run as a Service?
Yup, you are on your own :) I can't even begin to think of what can go wrong in such scenario...
Author:  Splitwirez [ Sat Feb 04, 2017 12:08 pm ]
Post subject:  Re: Run as a Service?
Ivo wrote:
Yup, you are on your own :) I can't even begin to think of what can go wrong in such scenario...


Oh, that's comforting...

...good think I'm doing all of this in a VM :lol:
Author:  Anixx [ Sun Feb 05, 2017 7:25 am ]
Post subject:  Re: Run as a Service?
Ivo wrote:
It is the process that injects the DLL into Explorer. It also watches for Explorer being restarted to do the injection again. And it does some other non-essential work.


So what if I put a bat file with it it into Autostart folder? It will start with Explorer, and then kill ClassicStartMenu.exe. Did you consider an option to put it into AutoStar and when the works is done make it exit?

If I am not mistaken, Autostart folder runs every time Explorer is restarted (may be wrong).

I also usually restart Explorer via Userinit because of other shell extensions such as ShellFolderFix.

Maybe there should be added an option to make this process exit after it have done its work?
Author:  Anixx [ Sun Feb 05, 2017 7:29 am ]
Post subject:  Re: Run as a Service?
Ivo wrote:
Yup, you are on your own :) I can't even begin to think of what can go wrong in such scenario...


Actually it is quite important thing to have a classic taskbar under Win10, and running Vista Explorer under Win10 is a solution, only if Classic Shell was working in this setup...
Author:  Splitwirez [ Sun Feb 05, 2017 8:56 am ]
Post subject:  Re: Run as a Service?
Anixx wrote:
Ivo wrote:
Yup, you are on your own :) I can't even begin to think of what can go wrong in such scenario...


Actually it is quite important thing to have a classic taskbar under Win10, and running Vista Explorer under Win10 is a solution, only if Classic Shell was working in this setup...


That's literally why I asked. Vista's explorer is largely functional on 10, the only crucial piece that's missing is the Start Menu. Classic Shell could provide that...please, Ivo...we're so close...
Page 1 of 1 All times are UTC - 8 hours [ DST ]
Powered by phpBB® Forum Software © phpBB Group
https://www.phpbb.com/