Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/23/2016 in all areas

  1. Noel, I just want to say: 1. I use Aero 7 theme by sagorpirbd for Windows 10 14393. 2. With this theme it's no glow on text of ribbon-enabled windows titles. 3. For adding that glow I must use theme atlas. 4. I export theme atlas from Aero 7 theme by sagorpirbd for Windows 10 14393 using AeroGlass GUI tool. 5. At least I enabled using My new theme atlas and recieved glow on text of ribbon-enableв windows titles. Result: I use Aero 7 theme + theme atlas created from that theme. Is it not strange? Using theme+theme altas I mean... I always think that it need to use only one of this...
    1 point
  2. Currently yes. ModernFrame is only experimental hack so it requires non-standard steps. On the other side, SecureBoot does not really increase security in any way, it gives only false safety.
    1 point
  3. Do you mean on Woody's site? He did seem to have some initial issues with questionable advertisements being served by his ad broker, but supposedly that's been taken care of now. We'll see. Malvertising is going to be the downfall of ad-supported computing, unless sites and especially ad distributors get on the ball. I remember one magazine site started blocking people who used ad blockers, then those who unblocked ads for that site promptly got malware-infested ads. It simply can't go on like that. Wonder how long before we get a scenario where Microsoft cripples Windows 10 for users who block ads in the Start Menu and notification center, then as a reward for allowing ads the users get malvertising. --JorgeA
    1 point
  4. Yeah, since ModernFrame does not load at startup at all but only when explorer.exe or applicationframehost.exe is executed, and it does not even affect rendering in any way, than any black screen cannot be caused but this DLL.
    1 point
  5. And now a small thing for those who like experiments: http://glass8.eu/out/UxTSB-2016-10-22-dbg.7z Important info for this build: 1) Install Aero Glass (and stop it from Task Scheduler, or just kill aerohost.exe process) 2) Replace DWMGlass.dll and aerohost.exe with files from this archive 3) Put UxTSB.dll into the same directory 4) Remove old UxThemeSignatureBypass DLL from registry, i.e. do NOT use AppInit_DLLs method!!!! 5) Start AeroGlass (from Task Scheduler) It is experimental debug build to remove dependency on AppInit_DLLs! It may be unstable! It may corrupt your OS install! It displays the debug console! Do NOT use if you don't want to use experimental stuff!
    1 point
  6. Isn't it clear they have a particular goal (to ELIMINATE the "desktop" metaphor) and the ONLY time they pull back from single-mindedly pursuing it is when they've pushed too hard too fast and have to backpedal? They don't ever want us to have a good Start Menu (from them) ever again! And they WILL move on from the desktop! If they SAY they put a Start Menu back, but in fact did something that's worse than ever, then people will say, "well, Microsoft needs to get rid of the Start Menu and do something better". Hell, if their motives were genuine they *could* have just resurrected the stock Start Menu from Win 7 or pre-release Win 8. But no, they didn't do that. The number of people who don't yet see their game is staggering. That they continue to single-mindedly pursue some "future vision" that's not better than what we already have may be even more staggering. Single-mindedly. Like not being able to imagine a mobile device interface that's different from what's needed on a serious computer. -Noel
    1 point
×
×
  • Create New...