7137 leaked in both flavors


Recommended Posts

Do we know of any changes (I know we aren't expecting anything drastic, but, hey, might as well ask. :)), and where can we find this build?
You won't be able to download the build yet. Just wait for it to make its rounds. We're not allowed to give you links anyway.

No ones installed it yet, it's only leaked in the last 30 mins or so, so just wait. I'm downloading the x86 version, and I'm on 13.5%, but I'll have to stop soon and finish tomorrow.

Edited by Livin in a box
Link to comment
Share on other sites

Think I'll wait to see if there's any worthwhile bugs squashed before changing from 7127.

Link to comment
Share on other sites

You might as well if you feel like it. But the thing that stops you is the knowledge that quite probably another build will leak in the next month, so...My laptop's still on 7057. ??

Link to comment
Share on other sites

I seriously doubt I will use leaked betas again, considering all the debug code is back and no updated, I going to keep RC until RC2 or RTM.

Link to comment
Share on other sites

I seriously doubt I will use leaked betas again, considering all the debug code is back and no updated, I going to keep RC until RC2 or RTM.
There are updates. I've got updates for 7127 on my other PC through Windows Update. But then again, that build was distributed.
Link to comment
Share on other sites

I seriously doubt I will use leaked betas again, considering all the debug code is back and no updated, I going to keep RC until RC2 or RTM.

NO RC2

Link to comment
Share on other sites

Doesn't Windows Update do a sort of 'Branch Family' id as opposed to exact builds. Not to say they'll work 100% perfectly, but I think RC updates apply to 7127, (despite 7127 technically being RTM branch)

Chris

Link to comment
Share on other sites

I seriously doubt I will use leaked betas again, considering all the debug code is back and no updated, I going to keep RC until RC2 or RTM.

HAHA and you think RC (and previous BETA), that basickly is PUBLIC DEBUG dont involve DEBUG code? continue to live in your dreams.... im sure even RTM will have pretty much same DEBUG code as it is now.

Link to comment
Share on other sites

HAHA and you think RC (and previous BETA), that basickly is PUBLIC DEBUG dont involve DEBUG code? continue to live in your dreams.... im sure even RTM will have pretty much same DEBUG code as it is now.

then why some builds are 3.04gb and others are 3.24gb?

Link to comment
Share on other sites

HAHA and you think RC (and previous BETA), that basickly is PUBLIC DEBUG dont involve DEBUG code? continue to live in your dreams.... im sure even RTM will have pretty much same DEBUG code as it is now.

I have never seen Microsoft release a checked build as retail...

Link to comment
Share on other sites

I have never seen Microsoft release a checked build as retail...

yes and those dialoges in vista "send this error msg to MS for future reference" (or something similar) isnt actualy debug code? :)

i have no idea why some builds are bigger and some builds are smaller, however im sure its not the point in debug code (and no i cba to compare size to size of files, if someone can be, be my guest), however if it is and debug code and we will get 200mb less "crap" in RTM then more power to the people! but im still not convinced. Debug code is fine, if it actualy helps solve problems, no matter RTM or not, no matter how many testers they have, they still can test 101...th hardware combinations.

Link to comment
Share on other sites

Info on 7037 :cool:

MICROSOFT.WINDOWS.7.BETA.7137.0.090521-1745.X86.ENGLISH.DVD-ZUKONA

FILE: 7137.0.090521-1745_x86fre_client_en-us_Retail_Ultimate-GRMCULFRER_EN_DVD.iso

SIZE: 2,544,232,448 bytes

CRC: 3D4EEF0C

MD5: 2F7520915DFF55380E979E67AE4687DB

SHA1: FF9C8751095E77BE0FD4A0A0A937E3EAB0C18943

MICROSOFT.WINDOWS.7.BETA.7137.0.090521-1745.X64.ENGLISH.DVD-ZUKONA

FILE: 7137.0.090521-1745_x64fre_client_en-us_Retail_Ultimate-GRMCULXFRER_EN_DVD.iso

SIZE: 3,262,167,040 bytes

CRC: 06047573

MD5: 0D863472414EFC337D032E8ED33C347B

SHA1: 8E35D15281A554FD890AD682249E485B9B82278C

Link to comment
Share on other sites

yes and those dialoges in vista "send this error msg to MS for future reference" (or something similar) isnt actualy debug code? :)

i have no idea why some builds are bigger and some builds are smaller, however im sure its not the point in debug code (and no i cba to compare size to size of files, if someone can be, be my guest), however if it is and debug code and we will get 200mb less "crap" in RTM then more power to the people! but im still not convinced. Debug code is fine, if it actualy helps solve problems, no matter RTM or not, no matter how many testers they have, they still can test 101...th hardware combinations.

No, that's part of Error Reporting. It just does that when an app crashes to give you a chance to let Microsoft figure out what's causing the crash.

Debug (checked) builds have symbol file references in them and check every buffer used for overflows. It's very slow.

Checked and Free Build Differences Two distinct builds of the NT-based operating systems are available:

The free build (or retail build)The free build of Microsoft Windows is used in production environments. The free build of the operating system is built with full compiler optimizations. When the free build discovers correctable problems, it continues to run. Distribution media containing the free build of the operating system do not have any special labels ? in other words, the CD containing the free build will just be labeled with the Windows version name, and no reference to the type of build.

The b><checked buildb> (or b><debug buildb>)b>The purpose of the checked build of Microsoft Windows is to make identifying and diagnosing operating-system-level problems easier. The checked build differs from the free build in the following ways:

Distribution media containing the checked build are clearly labeled "Debug/Checked Build." The checked build distribution medium contains the checked version of the operating system, plus checked versions of HALs, drivers, file systems, and even many user-mode components. For information about obtaining this build, see Obtaining the Checked Build.

Because the checked build contains fewer optimizations and more debugging checks than the free build, the checked build is both larger in size and slower to execute than the free build. As a result, the free build is used in production environments unless it is necessary to use the checked build to identify serious problems.

http://msdn.microsoft.com/en-us/library/ms792442.aspx

If the build name has "fre" in it it doesn't have debug code in it except for the few extra feedback tools they turn on to catch bugs in the build.

Link to comment
Share on other sites

I got installed this build and there isn 't any square start button.......

No course what you see is a pinned shortcut or a running app my friend :)

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.