NoelC

Member
  • Content count

    4,907
  • Joined

  • Last visited

  • Days Won

    211

NoelC last won the day on March 12

NoelC had the most liked content!

Community Reputation

1,260 Excellent

3 Followers

About NoelC

  • Rank
    Software Engineer
  • Birthday

Profile Information

  • OS
    Windows 8.1 x64
  • Country
  1. Are you another one who thinks, as I do, that it's inevitable and just a matter of time? -Noel
  2. Results seem polarized. I'm not surprised. -Noel
  3. History tells us these things: Chances are that you'll be without Aero Glass effects for a little while (weeks or months), since major OS releases usually change the system enough that the undocumented interfaces Big Muscle uses change in ways he hasn't anticipated. Big Muscle doesn't like to be asked about support for unreleased systems. -Noel
  4. Thanks for the 1.5.3 update, Big Muscle. It seems to work with my just-updated Windows 10 build 14393.969 test system. By the way, the version resource you have built into DWMGlass.dll still shows 1.5.2.847, though the debug.log shows the proper 1.5.3.872 version. Since you may want to fix that and repackage... Please allow me to make a request, since I'm starting to lose track of what works with what: Could you please identify/confirm all the files that should work together now: Of course we have AeroHost.exe and DWMGlass.dll from the 1.5.3 update. Which UxTSB.dll should go with the above? (I have 1.1.0.0 dated October 21, 2016) Which AeroGlassGUI.exe should go with the above? (I have an unversioned one dated October 2, 2016) The above SEEM to work together, and I do get the expected translucent borders and caption buttons from the ThemeAtlas file on the Settings App. Could you please consider packaging your current set of files that work together in one .7z file when you build versions of Aero Glass for Win 8+? -Noel
  5. Post moved to 1.5.3 thread. -Noel
  6. And for THAT we hail Big Muscle as an amazing software designer. Imagine if all software was this capable of adapting. -Noel
  7. The first thing that comes to mind is: "That's not a bug, that's a feature!" It's getting hard to make the case that updates are positive things... -Noel
  8. I'm very sorry to hear it seemed to slow down your setup, Jody. I haven't noticed it in my test VM, but I don't honestly run it enough to feel subtle changes. I'll certainly keep an eye open for that kind of thing when I finally update my workstation. I did compare PassMark PerformanceTest results from my VM and the host system, and the Windows Interface tests do measure a fair bit slower in the VM - but that may just be typical. I don't have stored PerformanceTest results for the VM from before the update to test against, though I suppose I could restore a snapshot and test... Over on AskWoody.com there are sporadic reports of the March updates breaking a Microsoft application called "MS Dynamics CRM 2011". I don't use that so I can't test it for myself. There's another report that the updates broke System Restore, but I've created a restore point and restored it successfully on my Win 8.1 test system. Lots of people find System Restore fails for them I think because they don't run it through the bootup Windows Recovery Environment. -Noel
  9. Attempting to debug DWM.exe with Visual Studio nets a series of messages like the following. Note the large number of "Cannot find or open the PDB file" messages, especially for dwmcore.dll. That's a pretty good indication the symbols for the latest patch are not yet on Microsoft's servers. 'dwm.exe' (Win32): Loaded 'C:\Windows\System32\user32.dll'. Symbols loaded. 'dwm.exe' (Win32): Loaded 'C:\Windows\System32\uDWM.dll'. Cannot find or open the PDB file. 'dwm.exe' (Win32): Loaded 'C:\Windows\System32\win32u.dll'. Symbols loaded. 'dwm.exe' (Win32): Loaded 'C:\Windows\System32\dwmredir.dll'. Symbols loaded. 'dwm.exe' (Win32): Loaded 'C:\Windows\System32\dcomp.dll'. Symbols loaded. 'dwm.exe' (Win32): Loaded 'C:\Windows\System32\dwmcore.dll'. Cannot find or open the PDB file. 'dwm.exe' (Win32): Loaded 'C:\Windows\System32\dxgi.dll'. Cannot find or open the PDB file. 'dwm.exe' (Win32): Loaded 'C:\Windows\System32\combase.dll'. Cannot find or open the PDB file. 'dwm.exe' (Win32): Loaded 'C:\Windows\System32\ucrtbase.dll'. Symbols loaded. 'dwm.exe' (Win32): Loaded 'C:\Windows\System32\bcryptprimitives.dll'. Symbols loaded. 'dwm.exe' (Win32): Loaded 'C:\Windows\System32\kernel.appcore.dll'. Symbols loaded. 'dwm.exe' (Win32): Loaded 'C:\Windows\System32\oleaut32.dll'. Symbols loaded. 'dwm.exe' (Win32): Loaded 'C:\Windows\System32\msvcp_win.dll'. Symbols loaded. 'dwm.exe' (Win32): Loaded 'C:\Windows\System32\CoreMessaging.dll'. Cannot find or open the PDB file. 'dwm.exe' (Win32): Loaded 'C:\Windows\System32\imm32.dll'. Symbols loaded. 'dwm.exe' (Win32): Loaded 'C:\Windows\System32\uxtheme.dll'. Symbols loaded. For me the glass effects seem to work anyway, so it doesn't seem like too big a deal to ignore the message. -Noel
  10. FYI, a data point not directly related to the "manual" method discussed here nor to 8.0, but possibly interesting or useful... On my Win 8.1 test VM I applied the Win 8.1 updates the normal way, save for the telemetry update (KB2976978, which I hid) and rebooted. I had two unexpected errors implicating an error enabling logging for publisher "Microsoft-Windows-Kernel-ShimEngine/Operational" in the System event log, and a "Registry Hive Recovered" message stating Registry hive ntuser.dat was corrupted. My firewall didn't work right after startup and in general the system just felt wrong. However, after another reboot all was well. Moral: Something about the recent updates may need two reboots before it all works properly. -Noel
  11. I wonder how many % of users they catch each time they do that. Somewhere in Redmond must be a sign: We can't win 'em over with brilliance; just wear 'em down. -Noel
  12. I definitely agree, there is much uncertainty, and a lot of the non-Microsoft manufacturer support will ultimately evaporate. In my own case I have two computers that are critical to my needs... A small low-end server system and a big Win 8.1 system that's a circa 2012 design high-end workstation, that even in 2017 is as potent as all but the newest/fastest systems. The server is a low power usage 2015 design running Win 7 that can easily saturate a gigabit Ethernet link with data, and it already runs Win 7 without ongoing updates, so it should be good enough for at least 5 more years, possibly longer. Based on what I can do now, the workstation hardware will be good for another few years at least. Then after that I'll probably get another, newer high-end off-lease workstation system with a lot of cores that will delight and amaze for a while longer - conceivably all the way into the low 2020s. The key is that today's high-end workstation hardware is still capable of running Win 7 and 8.1. There are already drivers for current accessories, for example NVMe drives that can sustain 3+ gigabytes/second I/O and quite fast video cards. It's not a cheap path, but it's a possible path. -Noel
  13. I'm thinking 8.1 might be a safe haven because the powers that be aren't thinking we 8.1 users are a big group that needs to be pushed off our current systems as hard as Win 7 users. -Noel
  14. No worries. It's the Aero7 theme by Sagorpirbd (from DeviantArt) and my own theme atlas for Aero Glass for Win 8+, which changes the caption buttons to what you see above from something that looks like Windows 7. The nice thing from the Aero7 theme is that the controls in older software take on some needed skeuomorphism, and rounded corners. -Noel
  15. The .png and .png.layout files are in the zip files named above. Feel free to alter them. You have to figure out where and when the various parts composite. I do that by overlaying them in Photoshop with bright colored pixels, saving the .png, reloading the atlas via the Aero Glass GUI tool, then seeing what parts of the desktop are affected. -Noel