Recommended Posts

Not the leak itself, but they handed this build out of MS to a few people months ago. It's how Paul got it and also got the OK from MS to post screenshots of it on his website.

Bzzzt wrong. Try again.

I think it just seems silly to have these included in such an early build. Maybe they should focus on fixing Vista somewhat, then work on all the fixes and core elements for Windows 7. Add the crazy UI in builds that are a little later in the development or use them for internal testing, I don't think changing the Screen Saver is really necessary right now No...

Nobody changed any screensaver code... Dropping in a different image takes 2 minutes and a monkey could do it.

If UI features waited til the end they'd never finish on-time. Or they'd never be able to do anything cool.

  • 2 weeks later...
  • 3 weeks later...
Nor was it implied, but the guy asked whats the point of the leak?

You said to test bugs... I said Microsoft are really gonna appreciate that feedback arent they?

I can actually give you two datapoints where builds that were unavailable leaked and Microsoft actually did incorporate feedback over the bugs in the leaked code.

Nashville II: This leak of an early alpha of what became Windows 98 actually leaked off Microsoft's own FTP server. A lot of the feedback from those that posted feedback on this build (I actually wrote a multi-page review and posted it on Microsoft's *public* NNTP server) has been incorporated into not just Windows 98, but other later versions of Windows.

Codename "Longhorn" 4074: This Vista build leak actually resulted in some of the features being merged into what has become Windows XP's Service Pack 3 (again, because of feedback from folks that got the leaked code).

While Microsoft may or may not intentionally leak builds, like most larger software companies, they use *all* feedback, regardless of source. (Other examples: Symantec, IBM, even Oracle.)

Eh its just Vista with small enhancements right now, whats the point.

You are probably the same age as the guy who said "Eh its just 2000 with small enhancements right now, whats the point" mentioning about XP's pre-alpha. When you get older, you'll understand. This is setting the stage for the next OS :-) Can't you feel that geeky feeling bubbling up inside you? If not, you will NEVER understand :p

Edited by PharosBR

So many people look at the screenshots and go "oh it's Vista all over again." etc. I wish these people didn't even post because they have really NO idea what they are talking about. Vista is used as a base for Windows 7, how else would you expect it to look in early alphas/betas/milestones?

Also, because you don't SEE any difference in the latest leak doesn't mean Microsoft teams aren't working on new things / fixing things... Just wait for it to progress a little... Sometimes it's not only the things you see but the underlying code aswell that's being worked on :)

Is this the most recent build out?

Why is it when they release new "Alpha/Beta" releases of upcoming Windows OS's, they Always change the ScreenSaver...

The screensaver, etc do need to reflect the OS though.

Edited by thealexweb

I remember being all excited about vista and submitting loads of comments which were ignored, its kind of funny now that the things that drive people mad about Vista are the same things everyone tried to tell MS in testing. Maybe its time to forget the hand picked focus groups and listen. Im not bothering this time to test any builds.

Seems ppl have bad experience with old Vista bulds, maybe MS could give you guys an incentive to test them? =P

Anyways, I wonder around what time in the development process do they start changing the UI.

Every product is different, and often every release is different. Besides, just because you don't see something doesn't mean it isn't being worked on...

Every product is different, and often every release is different. Besides, just because you don't see something doesn't mean it isn't being worked on...

Did he say that? no, he said he wonders when it will change... Duke Nukem Forever has been "being worked on" for YEARS.... doesn't mean jack till it hits the public. the poster obviously meant when changes will be implemented.

Did he say that? no, he said he wonders when it will change... Duke Nukem Forever has been "being worked on" for YEARS.... doesn't mean jack till it hits the public.

No, he very clearly was asking about the development process. That's why he used the words development process.

  • 4 weeks later...

Alpha's (and even not Beta's or RC's) never reveal 2 much of the new stuff.

I remember the day after Vista went RTM, I went to Brussels and was the first person here on Neowin to test Vista RTM (and leak out all the resources :p) Like everything I had seen before from the last RC released to public had changed, only in the positive way..

Let's see if I can still find that thread somewhere

*got the thread. after reading through it it is not suitable for re-reading :p

Edited by Ambroos
  • 3 weeks later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Are you going to do performance benchmarks comparing all states? I'd be interested in seeing that in the next "part".
    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
  • Recent Achievements

    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      78
  • Tell a friend

    Love Neowin? Tell a friend!