MSFT Engineers are signing off the RTM build of Windows 7


Recommended Posts

But if the RTM is to leak, then there'll be no timebomb, right? The keys will change, right? We won't be able to activate it, right?

Link to comment
Share on other sites

But if the RTM is to leak, then there'll be no timebomb, right? The keys will change, right? We won't be able to activate it, right?

yes , yes and YES !

;)

Link to comment
Share on other sites

So why people want it to leak so bad I don't know.

Some of us just want to get the RTM, finally stop following the releases, and then activate RTM when we buy a new computer in the coming months. Then, there is are some people who want to exploit activation flaws in ways that we are not allowed to discuss on this forum.

As for me, I fall into the first category since I plan on buying a new laptop that comes with Win7 sometime next year.

Link to comment
Share on other sites

Some of us just want to get the RTM, finally stop following the releases, and then activate RTM when we buy a new computer in the coming months. Then, there is are some people who want to exploit activation flaws in ways that we are not allowed to discuss on this forum.

As for me, I fall into the first category since I plan on buying a new laptop that comes with Win7 sometime next year.

I'd really like a new laptop that is x64 capable. But I don't think that will happen ANY time soon.

Link to comment
Share on other sites

How many posts are we going to have like this that contribute nothing to the thread and are merely whining. If you aren't interested in the thread, then why come in here at all? Why take the time to post? :rolleyes:
Exactly, why do people have to be so f...ing annoying. Don't like the thread then don't click on it let alone post useless rubbish.

I get interested in the thread because it mentions Windows 7 RTM information but when you read it, it's just like all other topics basically about the same announcement from Wzor, so the disappointment...

How about just keeping all in one?

Link to comment
Share on other sites

@ mattburles, yes you should be able to use it til Oct 22 with the re-arm method.

Anyone successfully get on Wzor's site yet? It's still down. Which might mean one thing! Updates? Maybe it's finally available? What do you guys think?

I know you may not know much about web servers, and site coding... but you know you dont actually have to take a site down to publish new files to it, or replace text or images, etc.

Link to comment
Share on other sites

What's the point. Even if it leaks won't the RTM be useless with RC/Beta keys?

Only to people who obtain it illegally ;)

To people with MSDN/Technet it will be ok

Link to comment
Share on other sites

This is all I can think of when I see thread titles like that...

capslock.jpg

:p

-Spenser

:rofl: True, caps lock really stinks :x

Improved version:

zaporoziancossackswin7.jpg

Wzor references the selection of the catholic pope procedure by talking about white or black smoke. As far as I remember a pope is confirmed by letting off white smoke from the chimney for all gathered followers to see.

They say that the first round of voting hasn't produced results, hence still black smoke.

I was already wondering, "Black smoke? Are they burning the candidates that didn't make it?" :laugh:

Link to comment
Share on other sites

On entering the command [slmgr.vbs -dlv]; you would find the script with the statement(2nd line from bottom, translated from my Chinese windows): remaining windows re-arm count: 3

It's common secret you can use 360 days, not allowed to talk here though.

Anyway, you can still go back to the previous versions and use it until 2010.march lol. :laugh:

Link to comment
Share on other sites

......

Anyway, you can still go back to the previous versions and use it until 2010.march lol. :laugh:

True, and there is not much of a difference between the builds anyway. I'm finding that 7229 and 7231 are rock solid. ;)

Link to comment
Share on other sites

True, and there is not much of a difference between the builds anyway. I'm finding that 7229 and 7231 are rock solid. ;)

Are either of those the same build as 7201? Obviously with a new build number, but didn't the tree split around that time?

7201 64-bit has been the quickest & most reliable for me. It will be the build I use until October if RTM doesn't leak.

The worst was 7127. No doubt about it. (N)

Link to comment
Share on other sites

Well yeah I get the re-arm argument. But there can't be any possible drastic changes between the builds except for a shiny new build string.

Not to mention by the end of July we'll be seeing a Baskin Robbins level of 31 flavors of the RTM images from the their partner OEM's being leaked. Just saying...its gonna be Win 7 Summer-Fall-Winter. :D

Link to comment
Share on other sites

Are either of those the same build as 7201? Obviously with a new build number, but didn't the tree split around that time?

.....

Build 6.1.7201.0.winmain_win7ids_sp.090601-1516 was leaked on June 3rd. That was a special internal developers (sp1) build. It leaked about a week after the first RTM branch began. That was shortly after they branched off 7141 to start the new service pack branch.

It is not really much different from those running 7229, 7231, and 7260. ;)

Link to comment
Share on other sites

Build 6.1.7201.0.winmain_win7ids_sp.090601-1516 was leaked on June 3rd. That was a special internal developers (sp1) build. It leaked about a week after the first RTM branch began. That was shortly after they branched off 7141 to start the new service pack branch.

It is not really much different from those running 7229, 7231, and 7260. ;)

The whole numbering/branching "thingy" is little hard to follow. I am just happy a quality final product is on it's way, slowly but surely, and appreciative that folks like yourself have been on the ball and around to provide, umm, "guidance" ;) for those of us with short attention spans.

It has been fun. Thanks.

Link to comment
Share on other sites

Build 6.1.7201.0.winmain_win7ids_sp.090601-1516 was leaked on June 3rd. That was a special internal developers (sp1) build. It leaked about a week after the first RTM branch began. That was shortly after they branched off 7141 to start the new service pack branch.

It is not really much different from those running 7229, 7231, and 7260. ;)

WRONG.

This was the build that leaked: 6.1.7201.0.winmain_win7ids.090601-1516(not from the sp1 branch). Furthermore, RTM branch didn't exist then. First build in the RTM branch was the 7260 that leaked (6.1.7260.0.win7_rtm.090612-2110). The rtm branch itself was created around the 15th of june (at least that's when we first heard of it)

Also, considering that the 7201 came from the idx branch and not winmain it actually had some new bugs that didn't exist in previously leaked 71xx builds. Bottom line, the most stable build with least amount of bugs that leaked is obviously the 7260.

Edited by vask
Link to comment
Share on other sites

WRONG.

This was the build that leaked: 6.1.7201.0.winmain_win7ids.090601-1516(not from the sp1 branch). Furthermore, RTM branch didn't exist then. First build in the RTM branch was the 7260 that leaked (6.1.7260.0.win7_rtm.090612-2110). The rtm branch itself was created around the 15th of june (at least that's when we first heard of it)

Also, considering that the 7201 came from the idx branch and not winmain it actually had some new bugs that didn't exist in previously leaked 71xx builds. Bottom line, the most stable build with least amount of bugs that leaked is obviously the 7260.

I may be wrong about the SP branch but here is what I have been tracking, using a number of good sources. Tell me where it is wrong and I will consider changes my records.

[b]
Pre-RTM Pre-RTM
6.1.7105.0.winmain.090404-1235 (Same as 7077)
6.1.7106.0.winmain.090408-1623 - Leaked April 13, 2009 Chinese
6.1.7107.0.winmain.090409-1840
6.1.7108.0.winmain.090410-1755
6.1.7109.0.winmain.090413-1552
6.1.7110.0.winmain.090414-1906
6.1.7111.0.winmain.090415-1920
6.1.7112.0.winmain.090416-1820
6.1.7113.0.winmain.090417-1710
6.1.7114.0.winmain.090420-1603
6.1.7115.0.winmain.090421-1650
6.1.7116.0.winmain.090422-1816
6.1.7117.0.winmain.090423-1737
6.1.7118.0.winmain.090424-1710
6.1.7119.0.winmain.090427-1750
6.1.7120.0.winmain.090428-1740
6.1.7121.0.winmain.090429-1835
6.1.7122.0.winmain.090430-1800
6.1.7123.0.winmain.090501-1720
6.1.7124.0.winmain.090504-1715
6.1.7125.0.winmain.090505-1530
6.1.7126.0.winmain.090506-1820
6.1.7127.0.winmain.090507-1820 - Leaked May 15, 2009 
6.1.7128.0.winmain.090508-1600
6.1.7129.0.winmain.090511-1440
6.1.7130.0.winmain.090512-1609
6.1.7131.0.winmain.090513-1755
6.1.7132.0.winmain.090514-1700
6.1.7133.0.winmain.090515-1635
6.1.7134.0.winmain.090518-1722
6.1.7135.0.winmain.090519-1845
6.1.7136.0.winmain.090520-1812
6.1.7137.0.winmain.090521-1745 - Leaked May 27, 2009 
6.1.7138.0.winmain.090522-xxxx
6.1.7139.0.winmain.090526-xxxx
6.1.7140.0.winmain.090527-xxxx
6.1.7141.0.winmain.090528-xxxx
6.1.7225.0.winmain.090529-1730

Server Branch:
6.1.7225.0.fbl_srv.090529-xxxx

Pre-RTM winmain branch:
6.1.7137.0.winmain.090521-1745 - Leaked May 27, 2009
6.1.7138.0.winmain.090522-xxxx
6.1.7139.0.winmain.090526-xxxx
6.1.7140.0.winmain.090527-xxxx
6.1.7141.0.winmain.090528-xxxx
6.1.7225.0.winmain.090529-1030
6.1.7227.0.winmain.090602-xxxx
6.1.7228.0.winmain.090603-19xx
6.1.7229.0.winmain.090604-1901 - Leaked June 11, 2009
6.1.7230.0.winmain.090605-1900 
6.1.7231.0.winmain.090608-1900 - Leaked June 11, 2009 (VHD)
6.1.7232.0.winmain.090610-1900 - Leaked June 15, 2009 (VHD)
6.1.7232.0.winmain.090613-0700 
6.1.7233.0.winmain.090614-1655 - RTM Escrow (7261 ?)
No further builds

RTM Branch
6.1.7260.0.win7_rtm.090612-2110 - Leaked June 17, 2009 (VHD)
6.1.7261.0.win7_rtm.090615-1900 - RTM Candidate - Voted no go (7233 ?)
6.1.7262.0.win7_rtm.090617-1900 - RTM Candidate - Voted no go
6.1.7263.0.win7_rtm.090619-1900 - RTM Candidate - Voted no go
6.1.7264.0.win7_rtm.090620-1900 - RTM Candidate

Service Pack winmain_sp branch:
6.1.7141.0.winmain_sp.090528-2045
6.1.7225.0.winmain_sp.090529-2022
6.1.7226.0.winmain_sp.090601-xxxx
6.1.7227.0.winmain_sp.090602-2110 - Leaked June 10, 2009
6.1.7228.0.winmain_sp.090603-20xx
6.1.7229.0.winmain_sp.090604-20xx
6.1.7230.0.winmain_sp.090607-2000

Service Pack winmain_win7ids_sp branch:
6.1.7138.0.winmain_win7ids_sp.090523-2200
6.1.7139.0.winmain_win7ids_sp.090526-1810
6.1.7140.0.winmain_win7ids_sp.090527-2145
6.1.7141.0.winmain_win7ids_sp-090528-2045
6.1.7200.0.winmain_win7ids_sp.090529-2355
6.1.7200.0.winmain_win7ids.090529-205x
6.1.7200.0.winmain_win7ids.090530-070x
6.1.7201.0.winmain_win7ids_sp.090601-1516 - Leaked June 03, 2009[/b]

Link to comment
Share on other sites

I may be wrong about the SP branch but here is what I have been tracking, using a number of good sources. Tell me where it is wrong and I will consider changes my records.

I told you where you were wrong, first you stated that the leaked build was: 6.1.7201.0.winmain_win7ids_sp.090601-1516 where in reality it was: 6.1.7201.0.winmain_win7ids.090601-1516.

Then you said: "It leaked about a week after the first RTM branch began." which is also not true as the RTM branch didn't exist till around the 15th of June.

Finally you said this: "It is not really much different from those running 7229, 7231, and 7260" which holds just as much merit as saying all builds post 7000 are not that much different. (Although this part is clearly a matter of opinion)

EDITED: If you still doubt which 7201 was leaked you can visit page 8 of wzor and see for yourself. They are still serving that build (which by the way was leaked by a russian poster from torrents.ru)

Edited by vask
Link to comment
Share on other sites

......... (Although this part is clearly a matter of opinion)

I am running 7260 now and it runs fine. It does run the one game (C&C Zero Hour) I play that wouldn't run under 7201, so that makes it a winner to me.

And as I don't think we are going to see anymore leaks, 7260 will have to suffice until I buy 7 in a box.

:)

Link to comment
Share on other sites

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

    • No registered users viewing this page.