| Windows 7: More From Wzor
|
Well, wzor.info has certainly been the center of attention over the past few days or so! Realizing this, they’ve responded to a lot of claims and rumors running around. It’s quite a lengthy post and much of the information reads like a Dr. Seuss book in a rear view mirror, but there’s some solid information here that I was able to discern (this is part Google translate and my translation): “Immediately after we announced the existence of different branches of assemblies 7138, 7200, 7225 on May 29-31, the worldwide Windows 7 enthusiast community has been booming. Over the past four days, information we posted has transformed into a surprising number of assumptions and myths. In this article, we will try to explain and clarify a our statements and declarations. First of all, I would like to say that the articles on the 29th and 31st of May were meant to clarify our initial posting, but the articles were apparently ignored. We ask that you please carefully re-read our earlier posts. Of course, we recognize that we didn’t correctly prepare all of the information before we posted it, but we didn’t have enough information from Microsoft at the time to post the specifics that we later posted. This also added to the perceived inaccuracies. The first thing I would like to discuss is the second release candidate of Windows 7 (RC2). If you remember back in January at the time of Windows 7 Beta 1, we stated that there would only be one beta and one release candidate. At the time we received that information, it was completely accurate but plans have since changed internally. The most recent plans included the date of assembly of RC escrow, the date of assembling RC2, and the date for the final RTM build. More than once, though, we heard Steven Sinofsky say that there would either be no further builds distributed past RC1, or if there were, that they wouldn’t be available to the general public. At the time, no such thing as an RC2 existed. As it turns out now, the build we call RC2 is internally released via a separate means: IDX (Internal Developer Release X, where X = Client or Server). Regardless, it is still consistent with RC2 but it is purely a private release for developers and partners. Here are some of the comments Microsoft has made regarding these assemblies: ——————————————————————————— “In addition there will be a Client SP released to a limited set of TechBeta participants (delivery via WU). SP will be based off the RC build and will go to a limited audience but not necessarily under NDA. It will be a .CAB file that installs on the RC build; WU detection dependent on a reg key available from the TechBeta site. The SP is edition-agnostic – it would install on either Server or Client, but Server will be turned off for this release. A Sensitive Asset test pass will be dependent on whether any SA components were touched (TBD). ” “This milestone is termed the, “Internal Developer Client and Server”(IDX) build – it’s an internal quality term we use meaning that the build is stable enough to deploy and evaluate, but may contain more minor bugs than a RC build.” Now, here’s the deal: We said on May 29 that the Windows 7 RC2 (IDX) release must have been signed off on. Well, indeed, on May 29, this build was compiled, but in the following winmain_win7ids IDX (RC2) branch: 7200.0.winmain_win7ids.090529-205x, Immediately after, a build was compiled on May 30th that had the same build string but obviously a different date (7200.0.winmain_win7ids.090530-070x). This is because the build number has been reserved for the upcoming release! (Don’t quote me on this, because this translation on Google wasn’t quite clear. I think it says the following, though) Build 7200 will be available to developers and partners on Connect on June 11th. But the internal 7200 build, the IDX build, could leak out of Microsoft sooner than the build is released, as we saw with RC1. In addition to the following build we announced: 7200.0.winmain_win7ids_sp.090529-xxxx There is a new build that has been compiled: 7201.0.winmain_win7ids_sp.090601-xxxx And lastly, the RC2 IDX release is not the last significant pre-release build (internally) before the final RTM release of Windows 7. The preparations for the RTM build will soon be in progress and that’s the last step in the sequence of releases. With this in mind, we will see the final RTM build of Windows 7 in July. Oh, and don’t forget that since Microsoft is already working on creating the first service pack for Windows 7, when it hits the market on the 22nd of October, you may immediately be getting a ton of updates. June 2, Microsoft confirmed that Windows 7 will be the stores on October 22. “Comments received from testers RC, very positive,” said Vegte. This information was confirmed both by him and Steve Guggenheimer, Corporate Vice President of OEM, during the exhibition Computex 2009. List of (pre-RTM) assemblies of Microsoft platforms, Windows 7 and Windows Server 2008 R2 on 3 June 2009, the latest leak from the network build’s pre-RTM winmain branch: 6.1.7137.0.winmain.090521-1745 – build leaked to web Screenshots assembly 6.1.7225.0.winmain.090529-1930 (see my previous post here for the following screenshots): 6.1.7225.0.winmain.090529-1930_1, Download 7225.0.amd64fre.winmain.090529-1930.client_en-us.ultimate_iexplore.exe: Rapidshare (~700KB)  winmain_win7ids IDX (RC2) branch: Service Pack winmain_sp branch: Service Pack winmain_win7ids_sp branch: Note: We will not public the exact times of build assemblies until the next builds are released internally. This will help to prevent fakes.” So… that’s a lot of information from wzor.info! Unfortunately, I wasn’t *quite* clear on some of this information as it was translated, so go check out their post yourself, translate it and see what you think. Source: wzor.info -Stephen  |
![WinRaR v3.92[Full]](http://rawcommunity.allgoo.net/users/2112/35/24/14/smiles/423269.png)
