Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Recommended Posts

My idea would that if it crashes three times in a row or whatever that it should automatically get to the fallback.

Share this post


Link to post
Share on other sites

I think it's way cool that Big Muscle built in a fallback that tries to give the proper effects (albeit with some artifacts) at all.

 

Win 10 build 10049 symbols should show up soon...

 

Seems like, since the Theme Atlas was essentially untouched, that Microsoft is slowing down the changes to the UI handling, which is good news - it implies that Aero Glass for Win 10 will be a workable reality.  I know I wouldn't touch the thing if it couldn't be reskinned.

 

-Noel

  • Upvote 2

Share this post


Link to post
Share on other sites

I think it's way cool that Big Muscle built in a fallback that tries to give the proper effects (albeit with some artifacts) at all.

 

Win 10 build 10049 symbols should show up soon...

 

Seems like, since the Theme Atlas was essentially untouched, that Microsoft is slowing down the changes to the UI handling, which is good news - it implies that Aero Glass for Win 10 will be a workable reality.  I know I wouldn't touch the thing if it couldn't be reskinned.

 

-Noel

Only thing Microsoft has changed on that build is the ModernFrame. ModernFrame worked for the 3 previous builds

Share this post


Link to post
Share on other sites

Win 10 build 10051 symbols not out yet either.  ModernFrame.dll not working.  The build is behaving same as 10049.

  • Upvote 1

Share this post


Link to post
Share on other sites

Windows 10 Leak Build 10051. Also Microsoft had mentioned it might release Build 10054 this week.

Edited by daveo76
  • Upvote 2

Share this post


Link to post
Share on other sites

Symbols are only available when public slow-ring build is delivered to Insiders.

Edited by Slifersky

Share this post


Link to post
Share on other sites

Windows 10 Leak Build 10051. Also Microsoft had mentioned it might release Build 10054 this week.

attachicon.gifAero.jpg

 

David, could you please show a full process list with Task Manager?

 

-Noel

Share this post


Link to post
Share on other sites

Here is a screenshot of one of my monitors with the native Start Menu open. I hovered over the maximize button to show the green!  This is build 10051!

 

Screenshot_5.jpg

Edited by dhjohns
  • Upvote 1

Share this post


Link to post
Share on other sites

 

stupid question
how close debugger window?

 

You don't.  You minimize it.

Share this post


Link to post
Share on other sites

 

Windows 10 Leak Build 10051. Also Microsoft had mentioned it might release Build 10054 this week.

attachicon.gifAero.jpg

 

David, could you please show a full process list with Task Manager?

 

-Noel

 

Here you go. Curious why you wanted to see this for

Share this post


Link to post
Share on other sites

 

stupid question
how close debugger window?

 

It sounds like you using the debug version. Which for me it doesn't work for Windows 10 Build 10049 and 10051. I use the v1.3.1 stable

Edited by daveo76

Share this post


Link to post
Share on other sites

 

It works for me in both builds.

Ok. For now it won't make any difference which version get used. Since ModernFrame isn't working

Edited by daveo76
  • Upvote 1

Share this post


Link to post
Share on other sites

Here you go. Curious why you wanted to see this for

 

Thanks, though I was hoping to see all of it.  I was just wanting to see the overall count and glance at the list to see if anything new has been added.  On my test Win 10 system the number of processes just running in the background has been growing with each new build.  Every build I return feedback asking Microsoft to trim the fat, and at least make the new "managers, brokers, hosts, etc." auto-exit when they're idle.

 

Here's what Process Hacker shows me on my system with a freshly booted system that's been allowed to settle for 10 minutes.  The list is a little bigger than a base Windows install because of some things I've installed, but take away the 7 or so processes running because of things I've installed or the way I'm running the system, and there are still almost 50 processes just to have a blank desktop - much more than with Win 8.1.

 

IdleProcesses.png

 

Seems like all they're doing is loading up Windows with fluff that will ultimately have to be cleaned out to make the system reasonable to run.  I've only just begun working out what doesn't actually need to run, but it's a moving target.

 

-Noel

Edited by NoelC

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...