Recommended Posts

Well, MS confirmed that it's not final RTM. I just won 10 internets.

Nope, they have not confirmed that 7600 isn't the RTM. Neither have they said it will be.

Who cares anyway.

MSDN & TechNet Subscribers: Subscribers will be able to download the final version of Windows 7 a few weeks after we announce RTM.

This is what I care about, Now I have this build, that is near final, and a few weeks later, I will get it legally from Technet :)

you don't believe in numerology? the study of numbers? Everything in life happens because of number sequences...build 7600? you will become rich and live a meaningful life. Build 7601? The Mayans were right and the world ends in 3 years. see what i mean? It's all in the numbers dude.

Hey guiez my calandar endz at December 31st 2009 so da world is going to end der i dont see any 2010 calanderz!!!

Seriously. The Mayan's didn't really want to plan past a thousand years+ (or less) so they didn't create the calendar.

Seriously.

I'm starting to get annoyed with all these OMGOMGOMOGM ZOMFG ITS NOT RTM threads all over the net.

Jeez.

I'm more annoyed by people trying to brag about how they called it out on not being the final build. Like they should be rewarded. Even though they were far from the first to say it probably wasn't the actual final build.

They haven't confirmed anything about specific build numbers. Your title was wrong as it was "7600 is NOT RTM" so I have changed it. 7600 is still RTM.

They said RTM is not finished, right?

So if this one was leaked and they haven't finished the final rtm yet, that makes leaked build not final rtm, right?

They said RTM is not finished, right?

So if this one was leaked and they haven't finished the final rtm yet, that makes leaked build not final rtm, right?

Why are you so obsessed with this? It'll be done in a couple weeks anyway. Now you're just starting to get really dramatic over nothing.

They said RTM is not finished, right?

So if this one was leaked and they haven't finished the final rtm yet, that makes leaked build not final rtm, right?

No it does not. They have not finished the final RTM yet, it means what it means, they have not choosen the final build to be used, do you think they compile it, and then an hour later announce it ?

They probably take at least a few days to properly test it.

I doubt the leaked build will be the RTM, it still could easily be though.

They said RTM is not finished, right?

So if this one was leaked and they haven't finished the final rtm yet, that makes leaked build not final rtm, right?

No, that's a clueless statement just like your thread title here. Going around the forums spreading misinformation when you have no clue whatsoever to how the build process works is reckless. I am not saying I know every last detail about the build process but over the years I have visited the Redmond build labs, Windows team and various different teams involved in the build process for previous versions of Windows. Unless things have changed rapidly since the last Windows beta (Vista) then they compile the RTM build and test it vigorously, this doesn't mean that 7600.16384 has been ditched because they have said they are not ready to announce RTM, it simply means they might not be finished testing it fully. On the flip side it could mean that 16385 is on its way and will require the same testing. Either way from experience of past Windows betas it's a safe bet that 7600 is the RTM build number and we are just waiting confirmation on the specific subset build (the 16384) number.

In my own personal opinion I believe 16384 might not be RTM as I know that they had planned to announce it yesterday and they even put a press release out about it yesterday by mistake (more info about that here). Either they need to perform some additional checks on it or they decided Ballmer was best to announce it or that 16385 is on its way and they start the checks again. Time will tell :)

UPDATE: looks like 16385 could have been compiled but it's worth noting that it appears to be only the WDK at the moment and not the client. Unclear right now.

Edited by Tom W
No, that's a clueless statement just like your thread title here. Going around the forums spreading misinformation when you have no clue whatsoever to how the build process works is reckless. I am not saying I know every last detail about the build process but over the years I have visited the Redmond build labs, Windows team and various different teams involved in the build process for previous versions of Windows. Unless things have changed rapidly since the last Windows beta (Vista) then they compile the RTM build and test it vigorously, this doesn't mean that 7600.16384 has been ditched because they have said they are not ready to announce RTM, it simply means they might not be finished testing it fully. On the flip side it could mean that 16385 is on its way and will require the same testing. Either way from experience of past Windows betas it's a safe bet that 7600 is the RTM build number and we are just waiting confirmation on the specific subset build (the 16384) number.

In my own personal opinion I believe 16384 might not be RTM as I know that they had planned to announce it yesterday and they even put a press release out about it yesterday by mistake (more info about that here). Either they need to perform some additional checks on it or they decided Ballmer was best to announce it or that 16385 is on its way and they start the checks again. Time will tell :)

UPDATE: looks like 16385 could have been compiled but it's worth noting that it appears to be only the WDK at the moment and not the client. Unclear right now.

I couldn't see a good reason why you closed my thread, so this is the last post I am putting up on Neowin, bye!!

Bye

OK, I changed my mind, I understand your reason is to keep it in few and early threads, and there is this thread not only earliest on starting, but earliest in reporting and confirming the RTM build 7600.16384. I'll stick to it until the confirmed RTM Final Build(I expect to make the earliest report too). :D

https://www.neowin.net/forum/index.php?showtopic=793314

OK, I changed my mind, I understand your reason is to keep it in few and early threads, and there is this thread not only earliest on starting, but earliest in reporting and confirming the RTM build 7600.16384. I'll stick to it until the confirmed RTM Final Build(I expect to make the earliest report too). :D

https://www.neowin.net/forum/index.php?showtopic=793314

Yeah. It's just getting irritating and confusing for all seeing so many threads about the same thing.

Yeah. It's just getting irritating and confusing for all seeing so many threads about the same thing.

Mr. Tom W: just a matter of interest, how come my thread reporting and confirming the build 16385 with all kinds of facts were locked, and another new guy just starting a thread of 16385 with no supporting material were OK? :blink:

Edit: just saw another new guy started another new thread............

Edited by FaiKee
Well, Wzor was correct. Windows 7 is RTM (13 July).

http://www.microsoft.com/presspass/exec/wa...009keynote.mspx

Edit: ****, wrong thread.

The scheduled rtm build day was Friday and the sign off on monday. After some issues with build 7600.16384 the rtm release schedule is delayed.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • 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.
    • I think he means you haven't reviewed previous UFC games. Of course it doesn't matter... Every time you just report on something that involves the President even if just simply what happened you guys usually get accused of being anti-Trump. We live in fun times.
  • Recent Achievements

    • 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
    • Week One Done
      agatameier earned a badge
      Week One Done
  • Popular Contributors

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

    Love Neowin? Tell a friend!