Windows 8

Well, it’s about that time again, boys and girls! The most exciting time for me as a Windows enthusiast and Microsoft journalist is the beginning stages of the next version of Windows. Though I’m certainly interested in other Microsoft products, Windows is the product I’m the most passionate about. As a matter of fact, I just wish Microsoft would do us both a favor and hire me on the Windows team to do what Robert Scoble did, *hint, hint*. ;)

 

But in all seriousness, our favorite Russian site WZor leaked to the web a number of post-RTM Windows 7 screen shots. The build is 7700 and — from what it looks like to me — could quite possibly mark the official beginning of Windows 8 development. For those of you unfamiliar with the process, Microsoft typically keeps the current version of Windows tagging in the early builds of the next version. The build string usually changes to reflect the next version prior to anything else (wallpapers are infamously changed throughout Milestone progressions during development), but if this is indeed the start of Windows 8 development, even the string has remained unchanged.

 

Build String: 7700.winmain.100122-1900
Windows 8 Build 7700

 

I certainly hope WZor decides to leak the build as I would love to begin my longtime tradition of dual-booting the latest leaked build along with my main OS! Should you decide to begin such a tradition yourself — or even more daring, decide to replace your main OS with the latest leaks — be aware that there may be consequences to contend with. Easily, the most detrimental consequence during Windows 7’s development was the bug that corrupted MP3s… and that was in an officially-released beta build, too! But I’m putting the cart just a little bit ahead of the horse as all we have at the moment are these screen shots (which may actually not be the official beginning of Windows 8, but since they’re from the winmain lab and don’t have SP1 in the string, I feel I’m making a fairly safe assumption). Oh, and to add to it, the “beta fish” wallpaper that hasn’t been seen since earlier beta builds of Windows 7 is back in this build (thanks for pointing that out @Gilly2468!). Make of that what you will!

 

I have divided all of these screen shots into 3 separate sections: Client, Server, and Client w/Office 2010 RTM screen shots (WZor posted all of these in separate posts but for the sake of concision, I’m putting them all in this one post).

 

Build 7700 Client


 

Build 7700 Server


 

Build 7700 Client with Office 2010 RTM






 

 

Anatomy of a Build String

 

Just to delve a bit deeper into the specifics of a build string, I want to shine a light on this really simple concept for those of you who aren’t quite sure what it means when you see one. This example is going to use the following build string: 7700.winmain.100122-1900

 

7700: This is the build number. It goes up incrementally with every build compiled. Sometimes, to mark a new milestone, Microsoft may skip a certain range of build numbers, i.e. moving from 7700 to 7710 without any builds compiled in-between.

 

winmain: This is the lab the build was compiled in. There are various labs where individuals, teams and branches can compile builds, but winmain is the main lab where all teams check their code in to have it all compiled into a more widely-distributed build.

 

100122: This is the date in format yyyy/mm/dd. So, in this string, the compile date is January 22, 2010.

 

1900: This is the time in military format. 1900 = 7:00 PM.

 

Altogether, the build string reads like a perfect little sentence: This is build 7700 and it was compiled in the winmain lab on January 22, 2010 at 7:00 PM.

 

Well, that does it for this extensive write-up. If you have any further questions regarding build strings or just some thoughts in general, please feel free to comment!

 

-Stephen
http://www.msftkitchen.com

25 Comments

  1. Cool thank you for information !

  2. This build isn’t the first Windows 7 post-RTM build of the winmain branch.
    A few days ago Wzor published this list of winmain builds which have been compiled before 7700:

    6.1.7650.0.winmain.090917-1843
    6.1.7651.0.winmain.090924-1802
    6.1.7656.0.winmain.091015-0833
    6.1.7658.0.winmain.091019-1850
    6.1.7659.0.winmain.091020-1830
    6.1.7660.0.winmain.091021-1736
    6.1.7661.0.winmain.091022-1755
    6.1.7662.0.winmain.091023-1645
    6.1.7664.0.winmain.091027-1825
    6.1.7691.0.winmain.100106-1825
    6.1.7692.0.winmain.100107-1735
    6.1.7693.0.winmain.100111-1820
    6.1.7694.0.winmain.100113-1753
    6.1.7695.0.winmain.100114-1855
    6.1.7696.0.winmain.100115-1725

    As you can see there have been plenty of winmain builds before 7700; Microsoft didn’t jump from 7600 to 7700 and because of this I don’t consider this build as a Windows 8 build. Most likely there are already some build labs which are compiling Windows 8 builds, but I think it is simply to early that Microsoft could have merged this code into winmain.

  3. Maybe its not Windows 8, but I can’t really think of what else it could be. There are already a number of 7601.winmain_sp builds accounted for, which would presumably be Windows 7 SP1, so I have to assume that the higher 76xx/7700 are Windows 8.

  4. I would assume that 7601 builds are the sp1 builds, with the revision number for increments in the sp1 builds themselves, 7602 sp2 builds and so on. MS has used this method before anyway. :)

  5. And yes, I think 7650+ is for future Windows versions. :) I wouldn’t be surprised if they give the first milestone build the appropriate build of 8000 or something.

  6. Stephen, great info!

    However, in your description of the build string: Instead of yyyy/mm/dd, it should be yy/mm/dd.

    Keep this wonderful info coming!

  7. Hi Stephen,

    I love your blog and your well reserached postings. But I have to correct one thing: The screenshots do not show Office 2010 RTM. Build 14.0.4734.1000 is the Release Candidate. The RC was released yesterday for selected testers. I can prove it with a screenshot if necessary.

    If you have any questions, plz contact me via mail.

  8. The acid substance produced after precipitation is
    known as “poisonous copper leachate” and it leaked into underground waterways
    reaching several miles and blending with river water.
    Once the brain signals the penis that it’s time for sex, bloodstream rushes into the erectile tissue, and exactly what was once smooth and hidden becomes pronounced and hard to ignore. Prostatis is an inflammation of the prostate gland.

  9. I take pleasure in, cause I discovered exactly what I was having a look for.

    You’ve ended my 4 day long hunt! God Bless you man. Have a nice day. Bye

  10. Right here is the right blog for everyone who really wants to understand this topic.
    You understand so much its almost hard to argue with you (not that I actually will need to…HaHa).
    You certainly put a new spin on a topic that’s been discussed for many years. Wonderful stuff, just excellent!

  11. Hi to every body, it’s my first go to see of this weblog; this blog consists of amazing and actually fine material for readers.

  12. That is really fascinating, You’re an excessively professional blogger.
    I have joined your rss feed and look ahead to in the hunt for more of your fantastic
    post. Also, I have shared your web site in my social networks

  13. When someone writes an piece of writing he/she maintains the plan of a user in his/her brain that how a user can be aware of it.

    Therefore that’s why this post is perfect. Thanks!

  14. whoah this blog is great i really like studying your posts.
    Keep up the good work! You understand, a lot of individuals are searching around for
    this information, you can help them greatly.

  15. It’s genuinely very complex in this full of activity life to
    listen news on Television, so I simply use world wide web for
    that reason, and take the most up-to-date news.

  16. Great post! We will be linking to this particularly great article on our site.

    Keep up the great writing.

Leave a reply