|
|
Post by leet on Dec 8, 2019 5:07:51 GMT -8
====================
BUG FOUND
====================
When starting a laptop with SCT installed, SCT will only load if the laptop is connected to power.
|
|
|
|
Post by powerplayer on Dec 9, 2019 2:31:01 GMT -8
I dont know how you would specify that ' ExplorerContextMenuTweaker' should load before anything else, or attach to every instance of Explorer. There must be a way. only way i know of is that its loaded already but need activation on real restart and by activation i mean just go to a folder in c and rightclick on it , it works ... Until you restart then you have to redo it |
|
|
|
Post by leet on Dec 10, 2019 13:25:24 GMT -8
Yup
BTW: Does anyone know how to make tasks start on login regardless of the power source on laptops?
|
|
|
|
Post by freddroger on Dec 20, 2019 6:09:39 GMT -8
Hello all, is there any possibility to exclude certain windows/application from "SimpleClassicTheme" ? I have a couple of Applications seem to do their own thing with the Window Title bar and sometimes the Classic Theme comes through for a short time making the Window Title flicker.
Cheers, Fred
|
|
|
|
Post by memphis on Dec 20, 2019 11:43:44 GMT -8
Your theme settings seem to be really messed up. I dont know, it seems like there is a bug in SCT where some settings are not applied. Yes Done Done ![]() There is a limit a of 3 attachments per post, drag & drop seems broken, and the editing GUI on this forum is kind of buggy. Continued in next message. ![]() I was not hoping for this to be fixed, I was only noting where I see transparent colors in case the information would be helpful in troubleshooting and theme development. Of course I dont use Internet Explorer or even Microsoft Edge -- those things are absolute rubbish. But here is the story with Photo Viewer: I wont allow any Microsoft accounts or telemetry on any hardware that I am responsible for, so I deleted the Windows store and all of those UWP apps which are bundled with Windows 10 that require a Windows store account. I would not want UWP apps even if I could get them -- and that includes the default W10 photo viewer. You know that UWP apps can't use any Windows API's, right? They are all cross platform apps which require that shitty UWP runtime environment which nobody wants to develop applications for because it totally sucks. This is why I use Windows Photo Viewer instead of that bloated, sluggish turd they call Photos. Millions of people feel the same way, and thats why there is a market for articles like this which tell the average user how to revert to the "classic" photo viewer: ccm.net/faq/44136-how-to-change-windows-10-s-default-photo-viewerwww.intowindows.com/how-to-make-windows-photo-viewer-default-in-windows-10/The Microsoft app store only allows UWP apps. That idea was brought to you by the same people who gave us Zune, Windows phone, and other failed technologies. This actually makes me happy because it will hasten Windows demise. Windows is a deeply flawed design that can only be fixed by breaking all of the native apps. That's what Apple did with Mac OS 20 years ago, but Microsoft is not willing to do the same in order to create a modern OS. This is why we are still using a fragile software platform based on 35 year old technologies like that stupid registry (which Bill Gates admits was a huge mistake.) Mac users never have to reinstall the OS unless they lose a disk drive. And the internet runs on Linux & BSD. So if you want to discuss what sucks, I can keep up.  Windows is a dead end, and that will become more apparent as time progresses. Of course Microsoft knows this -- its why they are starting to embrace Linux and diversify into cloud computing services. It's also why they tried to get developers to use garbage like UWP (which is even worse than Windows.) They want to create a migration path that keeps us tied to Microsoft platforms, but it aint gonna work on the desktop. They might just have to port MS Office to Linux or BSD some day, just as there are plans to run Mac apps on Linux and BSD. |
|
|
|
Post by memphis on Dec 20, 2019 12:07:39 GMT -8
Task Scheduler. [Who is the developer of SCT, this needs to be fixed on the installer.]
_ 
|
|
|
|
Post by memphis on Dec 20, 2019 13:20:12 GMT -8
is there any possibility to exclude certain windows/application from "SimpleClassicTheme" ? App developers can choose to support the classic title bar or Metro title bar, so this is really a problem. I heard that Stardock found a way to completely disable the Metro title bar on all apps, but I dont use their theming engine because it is a bloated resource hog that uses too much RAM and slows down the machine. Can you name the apps? --You could also try this:
|
|
|
|
Post by leet on Dec 22, 2019 5:38:11 GMT -8
Hello all, is there any possibility to exclude certain windows/application from "SimpleClassicTheme" ? I have a couple of Applications seem to do their own thing with the Window Title bar and sometimes the Classic Theme comes through for a short time making the Window Title flicker.
Cheers, Fred
No, because all theming is actually disabled. |
|
|
|
Post by memphis on Dec 22, 2019 14:09:52 GMT -8
|
|
|
|
Post by anixx on Dec 22, 2019 23:12:25 GMT -8
Hello all, is there any possibility to exclude certain windows/application from "SimpleClassicTheme" ? I have a couple of Applications seem to do their own thing with the Window Title bar and sometimes the Classic Theme comes through for a short time making the Window Title flicker.
Cheers, Fred
Try to put these dlls into the folder of the program in question: www.winclassic.net/thread/150/download-classictheme-exes-dwm-dllsAlternatively, start the programs in question from a bat file or script that would disable classic theme before they started and after they started, re-enable it. |
|
|
|
Post by anixx on Dec 22, 2019 23:15:58 GMT -8
==================== BUG FOUND ==================== When starting a laptop with SCT installed, SCT will only load if the laptop is connected to power. It seems the SCT creator forgot to check a checkbox when creating the tasks. |
|
|
|
Post by leet on Dec 23, 2019 4:17:25 GMT -8
First of all, memphis: SCT is ALMOST loading completely fine. (I'll come back to the context menu thing later in the comment) Even Open-Shell. But StartIsBack++ seems to break everything. Could you send me a zip file of the following directory: %localappdata%\StartIsBack\ And also a regbackup of the following key (Registry Editor -> Click the key -> File -> Export): Computer\HKEY_CURRENT_USER\SOFTWARE\StartIsBack
(NOTE: ExplorerContextMenuTweaker is not my DLL, nor do I have any knowledge of how it works. This is just me randomly trying some stuff out)
Next, after some inspection: Process Explorer indicates that ExplorerContextMenuTweaker is actually loaded when the explorer.exe process loads. So the first time broken thingy has to be fixed by either the author of the DLL (unlikely, hasn't done anything to it in a year) or someone has to clone the repo and edit it themselves.
But there's good news. The DLL isn't needed: When enabling the aerolite theme, even explorer uses system context menus. ( source) So if the aerolite AND Classic Theme are enabled, the context menus are Classic Themed. Tested this and it seems to work but I still need to investigate some inconsistencies.
Also anixx mentioned a DLL you can use to fix transparency issues. ( link). Sadly I didn't have any luck with them, but thats probably because I'm using them incorrectly. Where do you need to put them (I thought System32)
Finally, the task not loading without AC thing: I KNOW HOW TO DO IT IN TASK SCHEDULER. The thing is, SCT uses schtasks.exe and I can't find documentation on how to disable that option via schtasks.exe.
|
|
|
|
Post by memphis on Dec 24, 2019 4:05:48 GMT -8
Also anixx mentioned a DLL you can use to fix transparency issues. (link). That zip archive contains a batch file which does not work on current Windows 10 builds... and it deleted the following file: dwm_rdr.dllTo make matters worse, SCT and classictheme.exe both offer no way to reinstall it. They both think that all dependencies are satisfied, and I have not figured out how to convince them that this is not true. So I have no desktop window manager now. I can still run things from terminal by invoking Task Manager through CTL-ALT-DEL, but it's goddamn tedious, and I wasted a whole day troubleshooting this because I expected the solution to be simpler than it has turned out to be. If you had built a proper installer, I could have easily launched it from terminal and fixed everything in a minute. I need to know where you got 'dwm_rdr.dll' from (or how to make SCT believe it was never installed, so I can repeat the installation and place it in the proper path.)I will address the other issues you mentioned when I have a working desktop again. (And that fucking batch file needs to be taken down before it hurts somebody else.) |
|
|
|
Post by leet on Dec 24, 2019 5:55:13 GMT -8
That zip archive contains a batch file which does not work on current Windows 10 builds... and it deleted the following file: dwm_rdr.dllTo make matters worse, SCT and classictheme.exe both offer no way to reinstall it. They both think that all dependencies are satisfied, and I have not figured out how to convince them that this is not true. So I have no desktop window manager now. I can still run things from terminal by invoking Task Manager through CTL-ALT-DEL, but it's goddamn tedious, and I wasted a whole day troubleshooting this because I expected the solution to be simpler than it has turned out to be. If you had built a proper installer, I could have easily launched it from terminal and fixed everything in a minute. Don't blame me! SCT only runs Classic Theme. You ran that zipfile YOURSELF. dwm_rdr.dll has NOTHING to do with SCT, it's a DLL from the Desktop Window Manager and it's NEEDED to load DWM. Also, why didn't you make a full backup before running a random BATCH script with ADMIN PRIVILEGES. SCT isn't involved in fixing your Windows installation, it doesn't touch any DLL's. Updating Windows to 1909 is your only option, that recovers Windows. If you can't access Windows Update you can do this: 1. Use the Windows MCT to create a 1909 installer USB 2. Using Task Manager open setup.exe on the USB 3. "Upgrade" to Windows 10 1909
Taking the batch file down is not my problem.
|
|
|
|
Post by leet on Dec 24, 2019 6:29:45 GMT -8
Inspected the ZIP file a bit further. No way in hell that it could've deleted the file in any possible way. It just copies it. Where did you put the dll's in the zip?
|
|
|
|
Post by anixx on Dec 24, 2019 9:49:13 GMT -8
That zip archive contains a batch file which does not work on current Windows 10 builds... and it deleted the following file: |
|
|
|
Post by memphis on Dec 24, 2019 14:36:30 GMT -8
The object here is not to get someone to accept blame, it is to warn others not to run that file, and to restore a working desktop. And Classic Theme does two things: it installs DWM_RDR.DLL (as described here) and disables the Metro theme. You are contradicting what it says here about Classic Theme: - Install - Places the files: dwmapi.dll, dwmapi32.dll and dwm_rdr.dll under %SYSTEMROOT%
.....If SCT "only runs Classic Theme", and Classic Theme installs dwm_rdr.dll, then dwm_rdr.dll has EVERYTHING to do with SCT. In fact, it's actually the core component -- and once you disable Metro, this file is required to start Explorer. If it's already part of Windows 10, then why would Classic Theme need to install it? Dont you know how Classic Theme works? Please do me a little favor here: go to a Windows machine that does not have SCT or ClassicTheme installed and run a search on the entire hard drive for dwm_rdr.dll using this tool. Now tell me where that file resides on a normal Windows 10 installation -- then attach it to your post. (And also tell me where it resides on a system with SCT installed.) It was not "random" - it was recommended by you, and supplied by the administrator of this forum. Yes I made a mistake: I presumed that you both know what you are doing.  That was a declaration, not a directive. Another user actually complained about the same thing which happened to me, but nobody understood until it was too late. www.winclassic.net/post/3096 |
|
|
|
Post by leet on Dec 24, 2019 16:05:05 GMT -8
Don't tell me what my own program does. When I refer to "Classic Theme" I am talking about the theme. The program your talking about doesn't have a space in it's name  . What SCT does is simple: It removes access to the memory section used by DWM for theming. Doing that makes the system use the fallback theme: Classic Theme. It even does it in a way that metro is working. "ClassicTheme" does the same thing but it also copies those DLL's which are just meant to fix some transparency issues. Since SCT doesn't use those dwm_rdr.dll has NOTHING to do with SCT. It's the file "%systemdir%\System32\dwmapi.dll", renamed to "dwm_rdr.dll" and put into "%systemdir%". So yes, I actually do. Recommended? I literally only noted that anixx said it existed. I even stated that I wasn't sure if it worked or not.
|
|
|
|
Post by anixx on Dec 24, 2019 23:46:31 GMT -8
> "ClassicTheme" does the same thing A minor correction: it deletes the theme section rather than closing access to it, so the change is irreversible until re-logon. > It's the file "%systemdir%\System32\dwmapi.dll", renamed to "dwm_rdr.dll" and put into "%systemdir%". So yes, I actually do. No, it is the dlls created by the author of ClassicTheme program. These dlls make the calling program to think the DWM is disabled, otherwise they redirect to the system dlls in the System32 folder. So, one cannot replace the system dlls with these wrapper dlls. One can put these dlls into the Windows folder, then they will have priority over those in System32 folder for all programs, but I do not recommend doing this because 1. They have a known bug affecting Win8.1 taskbar, 2. They are very sensitive to Windows version and can make your system not working. So I put them into the folders of the programs that have problems with transparency (I fix this way Pale Moon for instance):  |
|
|
|
Post by anixx on Dec 24, 2019 23:51:01 GMT -8
> And Classic Theme does two things: it installs DWM_RDR.DLL (as described here) and disables the Metro theme.
You are confusing two different programs, SCT and ClassicTheme.exe by different authors. SCT does neither of the above. And there is no such thing as "Metro theme" at all.
|
|
. What SCT does is simple: It removes access to the memory section used by DWM for theming. Doing that makes the system use the fallback theme: Classic Theme. It even does it in a way that metro is working. "ClassicTheme" does the same thing but it also copies those DLL's which are just meant to fix some transparency issues. Since SCT doesn't use those dwm_rdr.dll has NOTHING to do with SCT. 
