Post subject: Re: Dissecting a Windows build tag Posted: Wed Jan 18, 2012 6:54 pm
Newbie Beta Collector
Joined Thu Jan 12, 2012 9:04 pm
Posts 26
Yes sorry, those were years. The NT OS/2 project started in 11/88 with the first lines of code written in 02/89.
An additional few notes on some of the fields in the original article:
The minor version isn't just used to identify a minor increment, it's also used to avoid changing the major version. Such a change was done for Windows 7 and also for Windows 8; the reason being application compatibility.
In regards to using the checked build, it's not a requirement to have a debugger attached. Prior to Windows Vista, if a debugger wasn't attached and an assertion failed, the system would bugcheck. Now if an assertion fails and there's no debugger, it's not reported which is not of great use for a developer.
As for build architectures, the values are x86, amd64 and woa. You could also see ia64 for versions earlier than Windows Server 8.
Post subject: Re: Dissecting a Windows build tag Posted: Tue Feb 07, 2012 11:41 pm
Newbie Beta Collector
Joined Thu Feb 11, 2010 6:19 pm
Posts 36
linuxlove wrote:
kni wrote:
And... Rights Account Certificate GUID... is this something like disabling Windows features in some build labs so if they are leaked, only the lab-related features are leaked?
As far as I can tell, the RAC GUID is just used for tracking Windows 8 builds as they go around.
arseny92 wrote:
9. Enforcement or excludenent of features' policies (fully customizable, example policy: Shell-InBoxGames-Solitaire-EnableGame), for the given Application ID and SKU ID. This is where SLC calls for RP-permissions for locked features.
One lab don't know about the features of an other lab. All labs are building based on a recent code from WinMain, where all the labs' code is consolidated. If the lab's key is used, the features of that lab activate and become usable per above RAC system, ELSE the build is no difference from the corresponding WinMain code, that this lab's build was built against at it's time. Meaning: if fbl_srv_wdacxml (Windows Server Data Access Components XML) is installed with the default key, it isn't differ from the corresponding winmain build and you cannot know which changes are tweaked to precisely that component and how that component differ from WinMain code.
Note: not an official statement, just my opinion based on my digging in the SLC system that described before.
Post subject: Re: Dissecting a Windows build tag Posted: Sun Mar 25, 2012 6:05 pm
Newbie Beta Collector
Joined Sun Mar 25, 2012 3:44 am
Posts 30
Favourite OS Windows Me!
I already knew some of that basic information, but the rest was all new. Some great information here for new windows users that just like to mess around with those beta builds.
Post subject: Re: Dissecting a Windows build tag Posted: Tue Feb 05, 2013 4:33 pm
Newbie Beta Collector
Joined Thu Jan 31, 2013 9:29 pm
Posts 41
Favourite OS Windows Longhorn 4074
pizzaboy192 wrote:
Coppermine wrote:
linuxlove wrote:
If not, very close to that many.
There was some discussion that Windows build's numeration isn't continuous but discrete.
It's known that they decided to jump builds for public release, but what isn't known is whether or not they still keep compiling behind the scenes after RTM to see what else they can do to their code. Post-RTM compiles are known to exist of 7, with build tags of around the 77xx range.
if it is post RTM builds of the os, it is either never used, put in a service pack, or put into a new OS; at least that is what i believe... for example, the early 'win8' probably wasn't win8 but the staff messing around with new ideas (ex. the user pic in start bar wasn't in the final build)
Post subject: Re: Dissecting a Windows build tag Posted: Fri Feb 22, 2013 8:36 am
1337 Beta Collector
Joined Sat May 12, 2007 1:05 pm
Posts 5226
Location The Collection Book
Favourite OS Everything Microsoft!
That is indeed correct DeFacto, it is a straight copy of this information, since it is relevant to the MCB. Ofcourse it isn't mine and Linuxlove, Daniel, arseny92 are properly credit at the beginning of the article.
Post subject: Re: Dissecting a Windows build tag Posted: Sun Mar 17, 2013 4:42 am
Newbie Beta Collector
Joined Fri Mar 15, 2013 7:24 am
Posts 12
Location Beta Archive
Favourite OS Longhorn
Interesting. I never knew that before. Although I did know about the Compilation Date, and the NT major and minor numbers, plus the Build Number. But the rest seemed like random numbers, but I guess they aren't.
Users browsing this forum: Bing [Bot], roytam1 and 14 guests
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum
All views expressed in these forums are those of the author and do not necessarily represent the views of the BetaArchive site owner.