romserg
New Member
Posts: 21
OS: W10
Theme: Classic
|
Post by romserg on Aug 3, 2020 9:56:46 GMT -8
|
|
|
|
Post by leet on Aug 3, 2020 10:29:37 GMT -8
Make sure SCT is ENABLED before you reboot
Use /boot
And finally increase taskbar delay if it still doesn't work.
|
|
|
|
Post by leet on Aug 3, 2020 10:32:12 GMT -8
If it STILL doesnt work, create a bug report on github
|
|
|
|
Post by leet on Aug 3, 2020 11:13:16 GMT -8
Sorry, my bad, it seems that I have removed this functionality at some point. SCT 1.10.0 will regain this option and will most bug fixed. I will release this version today
|
|
|
|
Post by leet on Aug 3, 2020 12:17:49 GMT -8
It's been 7 months but... UPDATE: 1.1.0
- Support for Windows 8.1 (not 8) while still working for Windows 10
- Fixed startup for the 50th time
- Fixed random bugs
- Re-based code from 1.0.6 instead of 1.0.5
|
|
romserg
New Member
Posts: 21
OS: W10
Theme: Classic
|
Post by romserg on Aug 3, 2020 12:30:17 GMT -8
Thank you for your support. I think I've figured it out. There is such a process ApplicationFrameHost.exe in system32, so I found out that this process (necessary for metro apps, it always runs with them and hangs in memory) must be started BEFORE activating the classic theme. Then metro apps will work correctly. Otherwise, it is the bug described above.
When loading the OS ApplicationFrameHost.exe it doesn't start immediately. But the classic theme is launched immediately, BEFORE it. This is why the bug occurs.
But if the default browser is edge, then ApplicationFrameHost.exe it starts very early, so the classic theme in the scheduler always starts later. Therefore, there is no bug.
ApplicationFrameHost.exe you can also run it manually, up to the classic theme. Maybe your program should run it first, before activating the theme?
PS. taskbar I have from the program Startisback, so I do not include it in SCT.
|
|
romserg
New Member
Posts: 21
OS: W10
Theme: Classic
|
Post by romserg on Aug 3, 2020 12:41:58 GMT -8
I'm sorry, this window crashes in 1.1.0 if the program is not in C:\SCT\SCT.exe (for example, it is located somewhere else).  But otherwise, the program works correctly, and metro apps are displayed correctly. Attachments:
|
|
|
|
Post by leet on Aug 3, 2020 14:00:24 GMT -8
I added starting ApplicationFrameHost before classic theme to the program. But through the power of broken github repositories, that didn't get into 1.10.0.
About the error: I'm stupid, just click continue and hit Install. This will create a perfectly configured task for SCT
|
|
|
|
Post by antidote153 on Aug 11, 2020 12:28:33 GMT -8
works for 1909?
|
|
|
|
Post by ihatemetro on Aug 19, 2020 16:57:48 GMT -8
Another problem has appeared. The classic theme starts when I boot Windows. But at the same time, Metro applications and even Settings stop working: when they are opened, an empty window opens. I turned off the classic theme, launched the Settings - they opened normally. Then I closed them, turned on the classic theme and reopened the Settings - they are still displayed normally. That is, an empty Settings window is displayed while they have never been launched and the classic theme is launched. How to get rid of the bug? I also have the same issue, just that metro applications (including settings) all stay at the splash screen with the exception of the UAC dialog and metro taskbar flyouts. In the splash screen you can still navigate but blindly. I use my own scheduled task based on the built-in scheduled task but runs a batch file so that it can load in what I need. Even with ApplicationFrameHost set to run before SimpleClassicTheme in the batch file, metro applications still stay at the splash screen and can only be navigated blindly. I'm running SimpleClassicTheme 1.1.0. |
|
romserg
New Member
Posts: 21
OS: W10
Theme: Classic
|
Post by romserg on Aug 20, 2020 2:54:48 GMT -8
ihatemetro, just create a task in the Scheduler to launch ApplicationFrameHost, and for the Classic Themes task, set a launch delay of 3 seconds (on the "triggers" tab). Another problem is that the titles of some windows, when the classic theme is activated, become translucent, the system buttons on them can disappear, for example Internet Explorer, Thunderbird ... What to do? And further. ʇǝǝๅ ftw, how can you prevent the program from being updated? I want to experiment with 1.0.6, but it's constantly updated.
|
|
|
|
Post by leet on Aug 20, 2020 2:59:50 GMT -8
ihatemetro, just create a task in the Scheduler to launch ApplicationFrameHost, and for the Classic Themes task, set a launch delay of 3 seconds (on the "triggers" tab). Another problem is that the titles of some windows, when the classic theme is activated, become translucent, the system buttons on them can disappear, for example Internet Explorer, Thunderbird ... What to do? And further. ʇǝǝๅ ftw, how can you prevent the program from being updated? I want to experiment with 1.0.6, but it's constantly updated.
Ok, first if all: There’s an issues page on github! Secondly the problem you’re getting has nothing to do with SCT itself, it’s just an issue with classic theme. If I recall there’s a thread dedicated to that issue so I would look for that. EDIT: Currently the only way to disable updates is to pull out your network cable/disable wifi. |
|
|
|
Post by ihatemetro on Aug 20, 2020 6:03:09 GMT -8
ihatemetro, just create a task in the Scheduler to launch ApplicationFrameHost, and for the Classic Themes task, set a launch delay of 3 seconds (on the "triggers" tab). Another problem is that the titles of some windows, when the classic theme is activated, become translucent, the system buttons on them can disappear, for example Internet Explorer, Thunderbird ... What to do? And further. ʇǝǝๅ ftw, how can you prevent the program from being updated? I want to experiment with 1.0.6, but it's constantly updated.
The Classic Theme task runs a batch file that starts applicationframehost before SimpleClassicTheme. It also runs DwmUnExtendFrame, which is here: www.winclassic.net/thread/215/dwmunextendframe-extended-glass-titlebar-removerIt basically just turns the translucent titlebars to black areas. There's no solution for that except turning off DWM, which is unstable and metro applications stop working.
Edit: Nevermind I got everything working, it was just that I didn't add the batch file into the scheduled task. I also added delay. Everything works perfectly. Now the only things that will complete my setup is a Classic Taskbar that supports DPI Scaling (I use 250% dpi with Classic Theme), and the taskbar that I have currently is Spitfire_x86's. It doesn't match my theme colours, and all other Classic Taskbar options don't play nicely with High-DPI scaling. I also need explorer bitmaps and to complete my toolbar.
|
|
romserg
New Member
Posts: 21
OS: W10
Theme: Classic
|
Post by romserg on Aug 20, 2020 11:32:36 GMT -8
If I recall there’s a thread dedicated to that issue so I would look for that. Found it? And I didn’t find it, unfortunately. |
|
|
|
Post by leet on Sept 12, 2020 4:13:25 GMT -8
- Fixed startup for the 51th time
- Fixed first time load
|
|
|
|
Post by ihatemetro on Oct 10, 2020 17:39:40 GMT -8
I'm trying to get into classic theme again after about a month of Windows 7 theme, but SCT 1.1.2 just doesn't work and throws an error. It only flashed for a brief second when I ran it from explorer, so I had to run it from cmd. Here's the error: Edit: BTW it doesn't have to do with being on a different drive, I tested it on the C drive and it doesn't work there either. Attachments:
|
|
|
|
Post by leet on Oct 11, 2020 3:19:57 GMT -8
I'm trying to get into classic theme again after about a month of Windows 7 theme, but SCT 1.1.2 just doesn't work and throws an error. It only flashed for a brief second when I ran it from explorer, so I had to run it from cmd. Here's the error: Edit: BTW it doesn't have to do with being on a different drive, I tested it on the C drive and it doesn't work there either. Looks like it’s failing to turn a string into an integer. Maybe try removing the SCT registry? (HKCU/SOFTWARE/1337ftw/SimpleClassicTheme) |
|
|
|
Post by ihatemetro on Oct 11, 2020 7:32:39 GMT -8
I'm trying to get into classic theme again after about a month of Windows 7 theme, but SCT 1.1.2 just doesn't work and throws an error. It only flashed for a brief second when I ran it from explorer, so I had to run it from cmd. Here's the error: Edit: BTW it doesn't have to do with being on a different drive, I tested it on the C drive and it doesn't work there either. Looks like it’s failing to turn a string into an integer. Maybe try removing the SCT registry? (HKCU/SOFTWARE/1337ftw/SimpleClassicTheme) Still no effect. Same error. |
|
|
|
Post by leet on Oct 11, 2020 8:05:44 GMT -8
Looks like it’s failing to turn a string into an integer. Maybe try removing the SCT registry? (HKCU/SOFTWARE/1337ftw/SimpleClassicTheme) Still no effect. Same error. Then there is probably something wrong with checking the Windows version as I don’t see the version info printing. What version of Windows are you using? |
|
|
|
Post by ihatemetro on Oct 11, 2020 8:14:42 GMT -8
Still no effect. Same error. Then there is probably something wrong with checking the Windows version as I don’t see the version info printing. What version of Windows are you using? During my switching to a Windows 7 theme I changed the build number and the version number from 1903 to 6.1, so that's what's probably causing the error. Oh well, I found another solution for Classic Theme anyways. |
|
