WindowsGuy
Freshman Member
Posts: 77
OS: Windows 10 pro
Theme: default
CPU: Intel Pentium Inside
RAM: 8,00 GB
GPU: Intel HD graphics, NVIDIA Geforce 610M
|
Post by WindowsGuy on Jun 17, 2024 7:55:38 GMT -8
Im using FindeXer, and i want to get bar from windows 2000
|
|
|
Post by ephemeralViolette on Jun 17, 2024 10:12:12 GMT -8
If you mean the HTML view on the left side of explorer folders, then that cannot be replicated by FindeXer. It simply isn't really possible.
|
|
WindowsGuy
Freshman Member
Posts: 77
OS: Windows 10 pro
Theme: default
CPU: Intel Pentium Inside
RAM: 8,00 GB
GPU: Intel HD graphics, NVIDIA Geforce 610M
|
Post by WindowsGuy on Jun 17, 2024 10:33:21 GMT -8
If you mean the HTML view on the left side of explorer folders, then that cannot be replicated by FindeXer. It simply isn't really possible. but with what i can do this?
|
|
|
Post by ephemeralViolette on Jun 17, 2024 11:53:54 GMT -8
If you mean the HTML view on the left side of explorer folders, then that cannot be replicated by FindeXer. It simply isn't really possible. but with what i can do this? I would say modifying the details pane DirectUI markup, like what's done for the XP sidebar.
|
|
WindowsGuy
Freshman Member
Posts: 77
OS: Windows 10 pro
Theme: default
CPU: Intel Pentium Inside
RAM: 8,00 GB
GPU: Intel HD graphics, NVIDIA Geforce 610M
|
Post by WindowsGuy on Jun 17, 2024 23:01:19 GMT -8
but with what i can do this? I would say modifying the details pane DirectUI markup, like what's done for the XP sidebar. but how? im on windows 10
|
|
|
Post by ephemeralViolette on Jun 18, 2024 11:29:57 GMT -8
I would say modifying the details pane DirectUI markup, like what's done for the XP sidebar. but how? im on windows 10 I believe the DirectUI files are stored in ExplorerFrame.dll.mun. You can modify it like what's done in this theme: www.deviantart.com/vaporvance/art/Luna10-907548273
|
|
WindowsGuy
Freshman Member
Posts: 77
OS: Windows 10 pro
Theme: default
CPU: Intel Pentium Inside
RAM: 8,00 GB
GPU: Intel HD graphics, NVIDIA Geforce 610M
|
Post by WindowsGuy on Jun 18, 2024 22:52:00 GMT -8
|
|
|
Post by ephemeralViolette on Jun 18, 2024 23:23:57 GMT -8
MUN files are separate resource libraries stored in C:\Windows\SystemResources since 1903. Prior to this version of Windows 10, there was no separation between code libraries and resource libraries, so resources were stored directly in the DLL files (usually in C:\Windows\System32 for 64-bit applications or C:\Windows\SysWOW64 for 32-bit applications).
|
|
|
Post by nonameneeded on Jun 19, 2024 19:53:24 GMT -8
It's in shellstyle.dll (like in the Luna 10 theme) You would have to modify the shellstyle.dll in the system32 directory. But it doesn't work, meaning you can't even have the XP like webview stuff of the Luna 10 theme in classic theme, let alone a Win2000-like webview.
I tried a lot. I copied the shellstyle.dll (and the corresponding mui file) from the theme to the system32 folder which kind of ruined folder windows (they were no longer usable, no file view and a white bar on the right hand side) Then I thought, I might try to import stuff from the theme's shellstyle.dll (and mui file) one by one to the existing shellstyle.dll (in system32) to see where the problem lies but even after having imported everything (that differs from the original shellstyle.dll in the system32 directory), there wouldn't be any difference, meaning that now the folder windows looked just like they did before I modified the file (so in this case no broken windows with no file view and white bars).
So all in all, it just doesn't seem to work.
|
|
Legofan
Sophomore Member
Embrace modernity? Nah, embrace tradition.
Posts: 171
OS: Windows 11 24H2
Theme: Default
CPU: AMD Ryzen 5 3600 / Intel Pentium Gold 4425Y
RAM: 64GB / 8 GB
GPU: NVIDIA GeForce GTX 1050 Ti / IGPU
Computer Make/Model: Custom Built / Surface Go 2
|
Post by Legofan on Jun 19, 2024 22:49:44 GMT -8
It's in shellstyle.dll (like in the Luna 10 theme) You would have to modify the shellstyle.dll in the system32 directory. But it doesn't work, meaning you can't even have the XP like webview stuff of the Luna 10 theme in classic theme, let alone a Win2000-like webview.
I tried a lot. I copied the shellstyle.dll (and the corresponding mui file) from the theme to the system32 folder which kind of ruined folder windows (they were no longer usable, no file view and a white bar on the right hand side) Then I thought, I might try to import stuff from the theme's shellstyle.dll (and mui file) one by one to the existing shellstyle.dll (in system32) to see where the problem lies but even after having imported everything (that differs from the original shellstyle.dll in the system32 directory), there wouldn't be any difference, meaning that now the folder windows looked just like they did before I modified the file (so in this case no broken windows with no file view and white bars).
So all in all, it just doesn't seem to work.
You probably need to rewrite the dui code for that manually.
|
|
|
Post by ephemeralViolette on Jun 20, 2024 14:39:48 GMT -8
It's in shellstyle.dll (like in the Luna 10 theme) You would have to modify the shellstyle.dll in the system32 directory. But it doesn't work, meaning you can't even have the XP like webview stuff of the Luna 10 theme in classic theme, let alone a Win2000-like webview.
I tried a lot. I copied the shellstyle.dll (and the corresponding mui file) from the theme to the system32 folder which kind of ruined folder windows (they were no longer usable, no file view and a white bar on the right hand side) Then I thought, I might try to import stuff from the theme's shellstyle.dll (and mui file) one by one to the existing shellstyle.dll (in system32) to see where the problem lies but even after having imported everything (that differs from the original shellstyle.dll in the system32 directory), there wouldn't be any difference, meaning that now the folder windows looked just like they did before I modified the file (so in this case no broken windows with no file view and white bars).
So all in all, it just doesn't seem to work.
Oh right, it's shellstyle.
You can use OldNewExplorer for its last remaining purpose, which is getting explorer to load shellstyle.dll from the theme instead of System32.
|
|
|
Post by nonameneeded on Jun 20, 2024 15:00:33 GMT -8
I already use OldNewExplorer. But I wouldn't know how to make it use the shellstyle.dll from the theme. Which theme would that be anyway (when you use the classic "theme")?
P.S: I just copied the luna theme's shellstyle.dll to the Aero themes directory but of course it doesn't change anything since I'm not using a Aero theme (I'm not even sure if Windows 10 even comes with a theme of this name)
P.P.S: I'm not sure where the classic "theme" on Windows 10 retrieves its details pane from but at least on Windows XP it was the shellstyle.dll found in the system32 directory. So I guess it might be the same on Windows 10. The shellstyle.dlls in the Resources directory are only used if you actually use an actual theme (which the classic "theme" is not).
|
|
|
Post by ephemeralViolette on Jun 20, 2024 17:47:11 GMT -8
I already use OldNewExplorer. But I wouldn't know how to make it use the shellstyle.dll from the theme. Which theme would that be anyway (when you use the classic "theme")?
P.S: I just copied the luna theme's shellstyle.dll to the Aero themes directory but of course it doesn't change anything since I'm not using a Aero theme (I'm not even sure if Windows 10 even comes with a theme of this name)
P.P.S: I'm not sure where the classic "theme" on Windows 10 retrieves its details pane from but at least on Windows XP it was the shellstyle.dll found in the system32 directory. So I guess it might be the same on Windows 10. The shellstyle.dlls in the Resources directory are only used if you actually use an actual theme (which the classic "theme" is not).
Oh, for classic theme, system32 is correct.
|
|