Jump to content

NoelC

Member
  • Posts

    5,142
  • Joined

  • Last visited

  • Days Won

    9
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by NoelC

  1. I personally think Big Muscle's model is fine. I have been using this software since the very beginning on several systems - hardware and virtual - and I just don't see any problems with it. I donated testing time, some theme atlas resources, and a few $$ a while back. I've taken the time to understand the expectations and restrictions on every version - that's been a simple matter of reading a few forum posts. Sometimes I have had to deal with watermarks and debug consoles, and those were expected. Minimizing a few windows is no big deal. People making watermarks and pop-up windows out to be serious problems must be living charmed lives indeed. Or are 12 and think the world owes them something. All it takes is to just read what's posted and to THINK just a little bit. The ONLY thing I can recall that's ever gone wrong for me is that not long ago I forgot my password on Big Muscle's site, and I ultimately had to ask him to reset it for me - which he did graciously, in less than a day. That's pretty darned good support if you ask me. At the moment the desktop of my Win 8.1 workstation, which I use every day for many hours, is graced with Aero Glass and an alternate Aero7 theme (possible to load courtesy of Big Muscle's UXThemeSignatureBypass DLLs) that is pleasant to use, instead of Microsoft's ridiculously frustrating lifeless, flat look. And it just runs and runs, without faults. I've paid thousands of dollars for other software that isn't this reliable. What an awesome little product Aero Glass for Win 8+ is for making our every day of computer use just a little bit more tolerable. Perhaps there's something special about me, but from where I sit, it's all good. -Noel
  2. I'm not in a position to examine/test the Emsa Advanced Port Blocker software, but generally speaking any package that allows you to know about communications and block selected ones could be useful for monitoring / controlling / limiting communications. The pertinent questions are: Does it introduce any problems of its own? Can it specifically be made to block communications with Microsoft's various telemetry servers without interfering with normal operations? Tools such as O&O ShutUp10, W10Privacy, and a few others (my own script included) do a good job of shutting telemetry down. But of course without something that allows you to monitor the comms it's hard to be confident. I use - and am excited about - the Sphinx firewall package myself. The author has created a really nice setup management process that uses server names in the upcoming version 8 (betas available here). Also, I run a copy of Dual DHCP DNS Server on my always-on Windows 7 server and it gives me control over what names get resolved (vs. blacklisted and never resolved) as well as logging what's resolved for all the systems on my LAN. Every DNS request goes first to my server, then to the internet DNS system if it's not blacklisted. Its claims to fame are the ability to use wildcards in blacklists and fast operation. -Noel P.S., Besides deconfiguring telemetry in every way possible, my current Microsoft blacklist entries from my DNS server lists include these Microsoft servers. Addresses that match these will not be resolved, thus no communications will be attempted. That is, of course, unless Microsoft builds them into the software as addresses instead of names, or uses some other means to resolve them (which they do). Hence also the need for a firewall. Note that this list serves not only Win 10 systems but also Win 7 and 8.1. # Unwanted Microsoft contacts iecvlist.microsoft.com=0.0.0.0 ieonline.microsoft.com=0.0.0.0 r20swj13mr.microsoft.com=0.0.0.0 spynet2.microsoft.com=0.0.0.0 spynetalt.microsoft.com=0.0.0.0 bn2.skype.msnmessenger.msn.com.akadns.net=0.0.0.0 client-s.gateway.messenger.live.com=0.0.0.0 win10.ipv6.microsoft.com=0.0.0.0 # Special Microsoft sync, telemetry, and privacy addresses to block vortex*=0.0.0.0 *vortex.data.microsoft.com=0.0.0.0 *vortex-win.data.microsoft.com=0.0.0.0 *settings-win.data.microsoft.com=0.0.0.0 *vo.msecnd.net=0.0.0.0 *telemetry*microsoft*=0.0.0.0 a-*.a-msedge.net=0.0.0.0 *smartscreen*microsoft*=0.0.0.0 # Blacklist entries suggested by Spybot Anti Beacon, updated July 1, 2016 choice.microsoft.com=0.0.0.0 choice.microsoft.com.nstac.net=0.0.0.0 settings-sandbox.data.microsoft.com=0.0.0.0 watson.live.com=0.0.0.0 watson.microsoft.com=0.0.0.0 feedback.search.microsoft.com=0.0.0.0 feedback.windows.com=0.0.0.0 corp.sts.microsoft.com=0.0.0.0 diagnostics.support.microsoft.com=0.0.0.0 i1.services.social.microsoft.com=0.0.0.0 i1.services.social.microsoft.com.nsatc.net=0.0.0.0 ac3.msn.com=0.0.0.0 cm.ac3.msn.com=0.0.0.0 compatexchange.cloudapp.net=0.0.0.0 corpext.msitadfs.glbdns2.microsoft.com=0.0.0.0 cs1.wpc.v0cdn.net=0.0.0.0 m.hotmail.com=0.0.0.0 blu405-m.hotmail.com=0.0.0.0 pre.footprintpredict.com=0.0.0.0 s.gateway.messenger.live.com=0.0.0.0 bn2-s.gateway.messenger.live.com=0.0.0.0 survey.watson.microsoft.com=0.0.0.0
  3. Hurricane Matthew was basically a non-event here in south Florida, but one thing it DID do was knock the power out with a couple of really dirty power hits (branches in power lines?) that lasted a minute or so. Unfortunately that was just enough to reset my Windows 7 machine, which performs primarily as a server, and which had run almost 2 months since the last reboot to install software. Maybe the small UPS battery was weak or maybe it just didn't handle the dirty power transitions well enough. Unfortunately, this cut short my bid to see how long Win 7 could run on it. Uptime was 56 days before the reset. So now I have outfitted it with a new APC BR1000G UPS, pictured below, that promises 3 hours backup power and better sensitivity to power hits. By contrast, my Win 8.1 workstation survived the power hits, as it already had a bigger, newer, better BR1500G UPS with fresh (and extra) batteries. I'm still looking to see how long it will run under daily use without any problems. 39 days and AOK at the moment... Moral of the story: You get what you pay for with UPS devices. -Noel
  4. I'm a bit late to reply here, but the thing I most remember is measuring a BIG degradation in File Explorer performance between 8.0 and 8.1. Basically, if you select all files/folder in the root of C: and choose Properties, they will count up MUCH faster on 8.0 (and 7) than 8.1. In my case I chose to go ahead with 8.1 anyway (having skipped 8.0), since I have a pretty rompin stompin system (my C: volume is a RAID 0 array of SSDs) and the slowdown didn't cut noticeably into usability. I believe Microsoft explained the slowdown back then as NTFS having been given some self-healing capabilities. Interestingly, other operations - such as searching the entire volume for file data with a 3rd party program like grepWin - didn't seem to slow down equivalently. For what it's worth I never had any file system problems before or after the change. -Noel
  5. I suggest not sharing your own uploads of software Big Muscle presently doesn't offer on his download site. He's clearly working on a version for release. The only one so far to work with build 14393 was a debug build, which put up an extra console window, and he's since taken that one offline. We don't know why; it might have had problems, or he might just be almost done with a new one. Be patient. -Noel
  6. Try the using the Accent tab for setting the colors in Win 10. -Noel
  7. The only time I saw them reinstalled was with 10586 and 14393 in-place upgrades. I doubt seriously they will under any conditions avoid that opportunity to reinstall the Apps during the next in-place upgrade. -Noel
  8. I have no idea whether that's intentional, but without spending the GPU cycles needed to combine adjacent pixels (blurring) whatever miniscule power savings there can be HAS been accomplished. Also bear in mind I have NEVER come across any objective evidence that blurring taskbars and borders uses enough additional power to make ANY measurable difference in battery life. I'd just leave it on if I were you. -Noel
  9. The separation of all those services into individual svchost instances - beyond the obvious waste of resources - is claimed to prevent co-hosted services from being crashed along with services that crash. Do you think they're doing it for OUR benefit? Or do you think that will give them license to release poorer quality services? When's the last time you had a service crash in Win 8 or older? -Noel
  10. Feed the Machine ID from each system into Big Muscle's web site and you'll get a download.key for each one. Place the download.key file in the same folder as DWMGlass.dll, then log off/on. Simple as that. -Noel
  11. Please read the text it puts up carefully and be very sure you want to proceed with what it prompts you to do. -Noel
  12. There is a separate component, ModernFrame.dll, that has to be loaded via the registry AppInit_DLLs value. For a while there was a debug version of this DLL available that would work with Win 10 build 14393 but I see no way to download it at this time. We have to assume it's work-in-progress by the author and that there will be a new ModernFrame.dll release in the future. -Noel
  13. @Painkilleraxel, you are apparently using a theme atlas with square corners. In the Aero Glass for Win 8.x+ configuration tool, set the Glass geometry radius to 0 or choose Win 8 style. That'll clean up your corners. -Noel
  14. As far as I know no part of the desktop / App environment uses OpenGL. Things like Photoshop and games use OpenGL. -Noel
  15. Look in debug.log for the Machine ID DWMGlass.dll generates. -Noel
  16. I think the thing that burns my behind the most is that Microsoft is doing no less than attempting to change what's considered "normal". For example, they're trying to make everyone feel it's "normal" for them to take over control - an act that only a few short years ago would have earned the label "malware". The only thing that's different now is that people are getting tired of pointing out that Windows 10's update policy is essentially that of malware ("get a foot in the door then NEVER pull back")... When they go too far, and there's a bit too much outcry, they back off - as little as is possible! - then continue their relentless march right back in the same direction. Good examples can be found in the latest pre-release build... People have been pining for the return of control over when their own systems download updates and reboot... So what does Microsoft give them in return? Cumulative ("our way or the highway") updates and... Latest announcement Too limited indeed. Are we ready for our systems to download updates and reboot EVERY SINGLE NIGHT? Is a 6 hour window really any better than a 12 hour window? Hello, Microsoft, people want full control back! Remember, these are the same updates that we used to have to pay attention to monthly, then delay (sometimes for weeks) until we were at a good breakpoint so that the updates could possibly destabilize our systems. There is still a way to take more control, but that's just because of Microsoft's good graces. If you extrapolate their path, there will come a time when those registry settings don't work. -Noel
  17. http://www.glass8.eu/donate -Noel
  18. I've only done it on a live system. And no, there's no problem with WinSxS as far as I can see. -Noel
  19. It's hardly surprising. The thing they NEVER brought back was hierarchy - which is what a menu structure excels at and what is needed to organize complexity. Not to mention performance, data density, elegance. Bringing back a flaky, scrolling, linear, underperforming alphabetic start menu side by side with ads and distracting tiles isn't exactly giving users what they were missing. I imagine they continued to get negative feedback for all the "start menu" replacements they've coded so far. Now they're basically saying "See? I guess you didn't want a start menu after all." It's become clear that Microsoft doesn't strive to give users functionality they want any more. Instead they strive to see what's the quickest they can change things to what MICROSOFT wants. Sometimes they do it too quickly, and that causes much outrage so they "bring back" some half-baked thing that's almost what they changed the system to anyway (but with downsides) - presumably to placate the whiners and complainers. Then they return to their original path before long. How anyone could be so arrogant to think they've got their design so right that they exclude the actual needs of users is beyond me. -Noel P.S., See the description of "Hide app list in Start menu" here: https://blogs.windows.com/windowsexperience/2016/10/07/announcing-windows-10-insider-preview-build-14942-for-pc/ P.P.S., note in the above page the wording: Doesn't this illustrate what I was saying very nicely? People complain that Microsoft's forced update policy isn't providing them enough control over their own systems, so they narrow down the allowed time for automatic reboot from 12 hours each day to 6 hours. Yeah, that's really what they are asking for. Not.
  20. A while back I published an experimental script that does the job... http://win10epicfail.proboards.com/thread/100/interested-participating-tweaker-development-test -Noel
  21. There's an App called Edge? There's a Windows Store? Assuming you still have one or both installed on your system, please describe what benefits either has brought you. -Noel
  22. Congrats on the release, Big Muscle. Please feel free if you'd like to include my RoundedCorners and/or RoundedCornersNoExtraColor theme atlas file sets with your released package or share the links on your web site. Apparently a number of folks like them. FYI, a small visual glitch I still see is a slight darkening of vertical areas near the ends of the title bar. The width of the darkening varies as per the Blur effect radius setting. I suspect somehow you've told the GPU to blur a dark or fully opaque pixel in there somehow. It's not a very big deal. -Noel
  23. The wording I saw made me think that they want to characterize the older systems for compatibility so that they can push patches or borderline feature enhancements that not everyone can take advantage of. You can imagine that fracturing the Win 7 and 8.1 user base. -Noel
  24. I doubt that it will stay activated after such a change, but according to some sources Windows 10 doesn't actually NEED to be activated at all to run indefinitely. I haven't tested that myself. -Noel
  25. Well, to be fair it's probably OK to update Windows with most updates published before mid to late 2016. With a few documented exceptions of course. But now... Cumulative updates are coming for the older systems, presumably because Microsoft gains more control over you with them. Imagine getting 0.2% more control over half a billion users. That would be like taking complete control over a million more users. Be afraid. Be very afraid of what today's Microsoft wants you to do. -Noel
×
×
  • Create New...