Recommended Posts

Edited on Jul. 12:

WZOR announced Win7 RTM: 7600.16384.win7_rtm.090710-1945

Now, the leaking race is on. :laugh:

~~~~~~~~~~~~~

I found the later posts on the thread about 7264 had actually focused on the coming RTM, with some updates I thought we'd rather start afresh, and hope the mods would let this thread stay.

On Jul. 3 Neowin News announced that Win7 will RTM on Jul.13, furthermore it stated:

So with that said TechNet, MSDN, and a few other partner connections will also be getting the RTM build on July 13. So let the countdown begin!

Just now, WZOR made another report, I don't want to jam the post with screen-shots, here's the Google translation:

And so, on the seventh of July, we are entering the final stage of assembly and selection sborkok the final RTM release of Windows 7 and Windows Server 2008 R2.

You reasonably ask, why in the seventh, but not with the sixth of June, from 4 to 7 June in the United States holidays, Microsoft is not working, assembly rests:)

By the tenth of July determined the final candidates and will begin closed on all major vote of two engineers, Microsoft, in order to determine which of the latest WIN7_RTM assemblies will be the final RTM release. This procedure starts with the 13-14 July and will end only on July 24 posting on the RTM release Connect'e. According to our data for 10 th July will be collected and the final candidate for this assembly may receive TAPy.

Suppose that such a candidate in the final assembly will be 7268 or 7270 from a branch assembly win7_rtm (7270 has not yet been collected, as well has not yet been collected and 7269 assembly), and assume that she will be signing (sign-off), then immediately after that happens rebuild this assembly to the final RTM release, but already in another assembly line, assume it will be build 7300, and only then we can confidently say that has the final release.

But even this can be repeated after the rebuild the final RTM release, but be sure to save the final assembly, how many times would not have had it with the re.

Here briefly is what we all expect in the coming weeks.

and on 7F we also have an "enquiry and reply" with WZOR, the site name is snipped because I am not sure if it's against Neowin regulations or not:

scr_39.jpg

Now, are we going to see a RTM release on Jul. 13, or Jul. 24??

Footnote:

- The dates on the RC release were: compilation-Apr.21; MSDN release-Apr.30, i.e. 10 days difference, and was leaked on Apr. 24.

It was based on the Neowin announcement and the RC schedule that led me to think the 7300.090703 build was a possibility and decided to post about the Connect download screenshot.

- The Worldwire Partner Conference on Jul. 13, everybody expected MS will confirm win7 RTM, now there would be a difference: MS might just announce RTM, and still hold back MSDN release until Jul. 24(WZOR); but if it is presented, then it should be release-ready(Neowin).

Edited by FaiKee

I expect it to be signed-off on the 13th of July. I also expect it to be made available to MSDN/TechNet subscribers a short while after.

For future reference: It's "quote" then /quote" (with square brackets).

100% wouldn't or everyone would be getting it, definitely a no for that question.

And why not? Whats the difference from Connect/MSDN/TechNet?

As an official "beta" tester of Windows 7 it wouldn't be a surprise if Microsoft gave its top testers a free copy of Windows 7. In the pass I received Vista with my own activation key. So I don't get the "or everyone would be getting it" comment.

I'd say that Rtm probably already has been built and is just undergoing some last checks to be able to be released at that conference on 13 July. Leak will be avaiable shortly after that.

Obviously. Every build in the RTM branch was considered for the final build until something is discovered that warranted changes and another compilation. Unless you meant the build that will end up being the final build (if no blockers are found) has already been compiled, of which there's a good chance.

I expect it to be signed-off on the 13th of July. I also expect it to be made available to MSDN/TechNet subscribers a short while after.

For future reference: It's "quote" then /quote" (with square brackets).

Thanks for reminding me the correct way to do it. :yes:

I ran over the comments on the Neowin News, somebody said Vista RTM was on MSDN etc within 48 hours after RTM announce, seems a 3rd speculation??

Also, I expect to get a free Win7U for the Windows Feedback Pro., I practically have to do nothing except being stuck with 7100RC, I guess MS wouldn't let the beta testers down, they are working so hard. :blink:

I ran over the comments on the Neowin News, somebody said Vista RTM was on MSDN etc within 48 hours after RTM announce, seems a 3rd speculation??

All of these are just educated guesses based on previous releases which have been made available through these paths shortly after RTM.

Also, I expect to get a free Win7U for the Windows Feedback Pro., I practically have to do nothing except being stuck with 7100RC, I guess MS wouldn't let the beta testers down, they are working so hard. :blink:

Vista's beta was a lot more restricted compared to Windows 7's public beta and RC builds. Due to the large number of people that got involved this time I think it's unlikely that there'll be the same kind of tester rewards as Vista. [my personal opinion]

I agree, I beta tested for vista and I know that it was very restricted. The reward for us was Free Vista Ultimate. I doubt with Windows 7 having very limited beta testers and a very open public beta that the tester reward will be free Windows 7 Ultimate. Microsoft is being very strict with Ultimate this time around, not even giving users a break on pricing let alone testers getting a free copy.

Just a correction, Vista was not released to MSDN within 48 hours of the RTM announcement by Microsoft.

They announced the RTM on 8th November 2006:

http://www.microsoft.com/presspass/feature...08VistaRTM.mspx

and it came to MSDN on 16th November 2006:

http://bink.nu/news/windows-vista-rtm-appears-on-msdn.aspx

I am tired of the wait, lol so I hope Neowin's [and a few others] saying it will appear on MSN on 13th, that is correct which would mean they have already compiled RTM. Keeping in view Vista's appearance on MSDN which I pointed above, Wzor's date also appears to be realistic, so nothing but wait till 13th =(

7300.0.090705-1900_x86fre_client_en-us_RTM_Ultimate-GRC1CULFRER_EN_DVD.iso

size: 2.6 GB

small exploding star, just up.

People of 7F working on it, not giving high hopes.

Also a HTTP dl, PCBeta working on both. repeat....don't give high hopes. :hmmm:

Edited by FaiKee

Thanks for posting that, The Patri0t. I hope Windows 7 RTM appears faster than Windows Vista RTM. In any case, I guess it wouldn't hurt to wait another week after the RTM build is signed-off and compiled. After all, it's still going to be made available to MSDN/TechNet subscribers much earlier than the purported release date of October 22.

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.
      78
  • Tell a friend

    Love Neowin? Tell a friend!