UCyborg
Content Type
Profiles
Forums
Events
Posts posted by UCyborg
-
-
1 hour ago, Hadden said:
So, for theming settings you need uxtsb?
You can only test "Use theme settings" properly if your theme has certain 2 values in it set properly. I wrote about it here. The first issue with size setting not being interpreted correctly should be easy to fix. The alignment problem might actually be bug in Windows.
Anyway, the point of "Use theme settings" is so called composited text glow; compared to the other type of glow, it doesn't use atlas image as the rendering source. It seems the best type to combine with the setting for centering caption, because the atlas image based glow looks like this then:
There's also a minor bug with resizing windows.
0 -
-
3 hours ago, cons013 said:
No news about when a fully released version for 1703 will release?
Nope, no news about the current state of the project in months.
So you got experimental version working now? You actually only need to bother with SDK Installer and the script I attached if you don't donate, if valid donation.key is present in Aero Glass folder, it downloads symbols on its own. They tell Aero Glass how to hook certain functions in Desktop Window Manager to provide glass effect when Microsoft changes something. It only works for smaller changes, when they rewrite some routine, Aero Glass code has to be updated as well.
0 -
In this case, it does, you need to manually get symbol files from MS server. To do that, download Windows SDK Installer and run it. When it asks which features to install, you only need Debugging Tools for Windows. When you got that installed, put the attached file in C:\AeroGlass and run it to download the symbols.
Which version of Aero Glass have you downloaded? Latest Win10 version is only supported by the debug build of Aero Glass available in Experimental versions section on the website, it has no installer and opens debug console on login along with a warning that this is debug build. There is an app for changing settings in Download section, under Others.
0 -
Haven't found a solution, the same problem was mentioned on some random Korean site and on extension's forums (the latter was dealing with MKV files, also Windows 8.1). There were also some hits about MediaElement from .NET Framework not working under certain circumstances, but compiling quick app with Visual Studio to test it haven't revealed any faults on my end, it worked. Nothing has been heard from extension's author for a while. This bug makes no sense.
0 -
-
On 28. 7. 2017 at 9:23 PM, Hadden said:
There is some new atlas/modernframe version to test?
0 -
1 hour ago, xpclient said:
What about 8.1? Does the command prompt raster fonts bug exist in 8.1?
Yes, it does, just try setting system locale to Slovenian here:
After reboot, log off and back on so the session number increases and the 8x12 option disappears:
Apparently picking a random language in said dialog may not reveal the bug and I haven't found the list of affected languages, I just know English US is not, Slovenian is and "windows 7 raster fonts 8x12" search term is known to Google. Coupled with the fact that the session number must be higher than 1; makes no sense at all, at least from the outsider perspective.Also noticed in Win10, Command Prompt windows maximize normally, even if you switch to legacy console.
11 minutes ago, jaclaz said:I remember this link, 10th of July. At this point, I'd also like to pinpoint another thing common to most NT systems, at least since Compatibility Engine is the thing. Process creation is a bit slower than it would be normally since the system scans the compatibility database to know which compatibility shims it should apply. There is a setting somewhere to turn it off, which might be desirable if only properly written software is run on the system. But it can be useful for some problematic legacy applications and games.
Another problem with the compatibility database, some entries in there are incomplete or redundant, in some cases even making the app crash. That's why you might have heard that someone fixed some app crashing by renaming its executable.
Interstate '82 comes to mind. Because Windows was applying a shim to it that it shouldn't. And not everyone knows about Compatibility Administrator. Also, compatibility modes exposed in .exe properties tend to apply tons of redundant shims.
We also have Metro style wizard for user account creation in dialog accessed by running netplwiz since Win8. It locks the desktop, but not the taskbar and tries to convince you to go MS account way.There's also something strange about the Task Scheduler, opening dialog for editing task's trigger takes few seconds to open the first time. It feels fastest on Vista, at least on my side, though it's still not instantaneous the first time.
0 -
Windows 7 introduced odd bug in Command Prompt windows when it comes to Raster Fonts. With certain system locale setting (language for non-Unicode programs) and when session ID is higher than 1 (it increases each time user logs on), size 8x12 for Raster Fonts just disappears, so it falls back to 7x12. I don't know which languages exactly except Slovenian are effected. Looks like it was fixed in Win10.
Another interesting issue on older Windows versions, spewing events with IDs 500 and 501 - The Desktop Window Manager is experiencing heavy resource contention. My 8.1 machine generates them on approximately 1-hour interval. Didn't happen on Win10, same graphics driver version. Video RAM usage is always below 512 MB (have total of 2 GB), not doing anything 3D heavy, warnings persist even though no performance degradation is apparent. I also see them on my two virtual machines with Win 7 and 8.1, but not on Win10 one.
On with the bad news, someone noticed another performance issue: https://stackoverflow.com/questions/45024029/windows-10-poor-performance-compared-to-windows-7-page-fault-handling-is-not-sc
0 -
11 hours ago, Raimoraimog said:
but it appears to be a debug beta with the watermark visible and a dwm.exe window visibly open doing it's thing...
Any hope for a new update for this? It would be very much appreciated, I still cannot stand the no aero look.Yes, that's the one and only version supporting Creators Update right now. Not much is heard from the author on these forums in recent months, so I wouldn't hold my breath.
0 -
9 hours ago, Raimoraimog said:
Um, could the rest of us get this funcioning "test version" as well? :/
0 -
12 hours ago, sonikdart1990 said:
You're missing a few elements in that shortcut.
True, insufficient for shortcut, but enough if using Run dialog.
You're specifying 2 GUIDs in your shortcuts, it seems the second one is sufficient.
12 hours ago, sonikdart1990 said:If you click any link you WILL be sent to the modern UI though.
If you replace themecpl.dll and themecpl.dll.mui with the ones from Windows 8.1, links open classic dialogs, but the Display link remains unfucntional, it just opens Libraries. You could probably set up those DLLs to live in peace with new ones with a trick I described in Restoring Manage Wireless Networks GUI on Windows 8+.
12 hours ago, sonikdart1990 said:Is this what you are trying to achieve?
Managed to bring back Display shortcut to the Control Panel itself, it just puzzles me why Personalization doesn't appear even though it's registered, everything is correct according to this. Maybe MS blacklisted that GUID. Win10 is mess either way.
Here's another shell command:
shell:::{ED834ED6-4B5A-4BFE-8F11-A626DCB6A921}\pageWallpaper0 -
Updated another laptop to CU. After a bit lengthy update process, things seemed fine at first glance, a bit slower at first; for some reason, OneDrive process was eating disk and CPU despite policy being in place that should prevent it from running, fortunately, it hasn't spawned since (one-time setup thing?). Settings for which security related things warnings should show up weren't preserved, and I had to flip a switch for preventing UWP apps from running in the background. If I remember correctly, AU didn't have it, just the switches for individual apps.
Now here comes the strangest thing, that either carried over the upgrade process or was introduced by it. The damned thing for some reason refuses to let user move any icon on the desktop to the bottom-left corner, anything placed there gets moved 2 places to the right. Haven't dealt with icon layout problems in a long time, looks like they can still occur.
I cleared Bags and BagMRU keys in registry, but the problem persists. What's funny, I once managed to get one of the icons to stick there for a while with the help of Sort by command, it even survived exiting the shell by holding SHIFT + CTRL, right-clicking the taskbar and selecting Exit Explorer. It didn't survive exiting Explorer for the second time.
0 -
Looks like those settings aren't completely gone yet (at least in current stable build 15063.483), they deleted references to them from registry. Importing DisplayCPL.reg brings them back. TrustedInstaller privileges required. They did replace the scaling slider with the link to the Settings app. TrueType tuner is there, font sizes can be changed, color calibrator works at first glance, also the link "Adjust brightness" that points to the power panel appears on supported devices eg. laptops.
Edit: Also noticed that reference to Personalization settings is present in registry, so I guess it doesn't appear in Control Panel because something about that specific panel is broken, though it can be invoked using Run dialog:
shell:::{ED834ED6-4B5A-4BFE-8F11-A626DCB6A921}Should be invokable with this one as well, but it doesn't budge...
control.exe /name Microsoft.Personalization
0 -
Updated wlanpref2.reg to add a shortcut to the Control Panel under Network and Internet. Can also be invoked with:
control.exe /name Microsoft.ManageWirelessNetworks
0 -
I'd try those two classic commands first in Command Prompt run as Administrator:
Dism /Online /Cleanup-Image /RestoreHealth sfc /scannow
Ideally, they would repair everything wrong with system files and certain registry entries and let the offending update to uninstall cleanly afterwards. There is a chance that when update uninstallation fails, that something useful might be written at the end of the log file C:\Windows\Logs\CBS\CBS.log
0 -
@NoelC
I can confirm it still happens on non-tweaked version 1703.0 -
6 hours ago, NoelC said:
UWP File Explorer... Ugh.
Indeed nothing to be excited about. Maybe it could work as a basic file manager on a phone.
6 hours ago, NoelC said:The time is approaching when it will either be necessary to abandon all hope of using Win 10 or embrace it for all its unwanted directions (cloud, poor efficiency, never finished).
I wonder what finished version of Win10 would be like.
6 hours ago, NoelC said:Who would imagine you could replace things with... lesser things and that could somehow be "acceptable"?
Re-inventing the wheel gone really bad. And you never know what they'll throw out next. Currently, they really hate the Control Panel. What's next?
1 hour ago, xpclient said:According to this blog post, XTS-AES was added in Microsoft Bob, Version 1511: https://blogs.technet.microsoft.com/dubaisec/2016/03/04/bitlocker-aes-xts-new-encryption-type/
Right, have to remember about version numbers. The days of counting service packs are gone.
0 -
On 15. 7. 2017 at 1:37 AM, vinifera said:
do these ... well i'll call them service packs hahaha
even bring something to winblows 10 ?They have more detailed list of additions here.
0 -
One of those things they don't mention in the highlights of the updates, given the emphasis on the UWP landscape, BitLocker got some enhancements with Windows 10, XTS-AES encryption algorithm and according to this, the encryption process is supposedly faster in Creators Update. I wonder if someone knowledgeable tested that claim.
Either way, the mindset behind Win10 development isn't the same like it was with Win7, one of the reasons the OS is still odd at places. 3D Paint and new emojis, one of those main highlights of the Creators Update. Gets one to think they're running comedy show at MS. I think highlighting actual core improvements would be a good idea. Maybe with the next feature update? No one would oppose if they fixed things they broke that worked in older versions.
Another thing that comes to mind. Will classic Explorer see any changes in the future? There's already UWP File Explorer present in Creators Update:
explorer shell:AppsFolder\c5e2524a-ea46-4f67-841f-6a9465d9d515_cw5n1h2txyewy!App
It needs some work before it would be equivalent functionality wise to the classic Explorer.
1 -
I do use PotPlayer for videos and AIMP for audio, just have those codecs installed for Windows' own media framework to be able to support as much formats as possible, in case they're needed by something else, in this case QTTabBar. Its preview feature allows hovering over the file and it will play without having to open it in external player. I assume it relies on whatever .NET Framework provides for media playback, so extra codecs are needed for otherwise unsupported formats.
Just in case, I also tried with minimum amount of codecs on fresh Windows 8.1 install in a virtual machine, just took the ones from https://www.xiph.org/downloads/ to add support for OGG and FLAC among others, but QTTabBar outputs the same error code. Repeat the same procedure on Windows 7 or 10 and it works.
0 -
There is an odd issue when it comes to Explorer extension QTTabBar's preview feature, specific to Windows 8.1 (maybe 8 as well). If you try to preview a media file, eg. FLAC or OGG, for which you need to install extra codecs/DirectShow filters, it spits out said error code instead of playing the file. Windows Media Player plays the file just fine. If the codecs aren't installed, you get generic "Failed to load media file.", as expected.
On both Windows 7 and 10, installing K-Lite Codec Pack enables playback of such files both in WMP and Explorer itself with the help of QtTabBar. There's something weird about Explorer on Windows 8.1 where the files don't play, expect those that don't require additional codecs.
Haven't found anything useful regarding the error code, it's mostly encountered in WMP itself. It seems as if something was missing when it comes to ability to utilize codecs from Explorer's side since formats with native support do play without a hitch.
Any idea what the issue is and how to solve it?
0 -
Diagnostic Tools do not work with disabled VsHub.exe.
PS: I'd like to note that the meaning of "server" depends on the context. It can be used for nothing more than inter-process communication. Though they do acknowledge that telemetry is also part of VS Hub.
VS2017's VS Hub hosts more functionality of the IDE, probably why it refuses to work without it. I'd say if you find the whole thing fishy, probably the best to not use the software at all, rather than worrying about what each process hosts. At least that would be good for sanity.
0 -
On 5. 7. 2017 at 11:45 PM, Hadden said:
but when it starts to hang, I notice is trying to "paint" a glass frame.
What you're seeing is DWM jumping in and replacing hung app's window with a ghost copy. Ghost copies have standard frame which will have glass effect if Aero Glass is installed. The app would hang irregardless of whether Aero Glass is installed or not. If the app hangs and doesn't process window messages (events) for at least 5 seconds, this happens, otherwise, you wouldn't be able to interact with the window at all, this way, you get to see last visual state in which the app was in before it hung and you can get the window out of the way (move it, minimize it or force close the app). You see the same thing if a modern version of Visual Studio or Office app hangs, which got some people thinking Aero Glass could somehow override the custom frame. Standard frame is there because at that point, the app's code providing custom frame isn't running anymore.
6 hours ago, Hadden said:Can be aeroglass paused via script? (Just to try without mess with its normal functions)
You can set opacity to maximum with Aero Glass GUI. The only other way is stopping Aero Glass's task via Task Scheduler then forcibly stopping Desktop Window Manager via Task Manager, which restarts it without Aero Glass loaded. There's no function that would unload Aero Glass at will.
As a point of interest for the geeks out there, it is possible to process window messages in a way that makes DWM itself think that the app is not responding, even though it works fine. Old games by Surreal Software have the main loop written somewhat like this (pseudo C code derived from disassembled code):while (1) { MSG msg; BOOL result; if (PeekMessage(&msg, NULL, WM_KEYFIRST, WM_KEYLAST, TRUE) || PeekMessage(&msg, NULL, WM_MOUSEFIRST, WM_MOUSELAST, TRUE)) { if (msg.message == WM_QUIT) break; TranslateMessage(&msg); DispatchMessage(&msg); continue; } result = PeekMessage(&msg, NULL, 0, 0, TRUE); if (msg.message == WM_QUIT) break; if (result == TRUE) DispatchMessage(&msg); Game_Frame(); }
If you run the game in windowed mode, then click outside the window to make it lose focus, it appears frozen after 5 seconds, even though it still runs its loop, can even see what's happening in-game in ghost window, it just doesn't respond to user input. Accent color change event can thaw it. Simplifying the loop to have one PeekMessage call without filtering, then TranslateMessage and DispatchMessage if the result from PeekMessage was positive, then finally running the game frame resolves the issue.
0
Interstate '82 comes to mind. Because Windows was applying a shim to it that it shouldn't. And not everyone knows about Compatibility Administrator. Also, compatibility modes exposed in .exe properties tend to apply tons of redundant shims.
Please List What Needs Fixing In Experimental Build 1.5.4.904
in Aero Glass For Windows 8+
Posted · Edited by UCyborg
I tried Aero Glass on Insider Build 16251, symbols are currently available only for ApplicationFrame.dll, so restoration of regular window frames for UWP apps seems to work just like on Build 15063. One issue worth mentioning, Edge behaves oddly, clicking anything inside its window makes its frame change like in the screenshot below, it's the same on Build 15063. This also makes frame buttons refuse to respond to clicks a lot of time. When it happens, only buttons get inactive look, but frame color indicating window with keyboard focus remains, even when it does lose focus.
All other functions of Aero Glass except transparency and watermark work. I wonder if it would still work if symbols for the rest of the modules were available. Or would it just crash? I'd say there's a good chance it works, but we can't know for sure.
Note that the glow on the text of Edge titlebar is from before I switched back to default Windows theme to give Aero Glass' theme atlas image loading function a spin. The atlas image was extracted from sagorpirbd's Aero 7 theme.