NogginBoink
Diamond Member
- Feb 17, 2002
- 5,322
- 0
- 0
Originally posted by: glugglug
Like I posted in the similar thread in P&N:
This is an obvious hoax.
THe source code to all of windows does not exist in one single place. For example, messenger service would not be part of the same project or built by the same team as mmc, which would be built by a totally separate group from IE, etc. Even smaller pieces of Windows like IIS would have different subsections built by totally separate teams.
Actually, you're wrong on this point. The entire source code tree is stored in one central location. There's a daily check-in window for developers to submit new code for the daily build. (Actually, most Windows developers keep an entire copy of the source code so they can test their code on their own private builds before submitting code for check in.)
The [team that builds the "official" OS is known as the build lab. MS builds the operating system DAILY. Windows NT 4.0 was build 1381. W2K was build 2195. WinXP was build 2600. W2K3 is build 3790. Yes, the lineage really does go back that far.
Developers probably build a jillion private builds a day to test their corners of the OS and code they're working on. This should be an obvious point. "Breaking the build" is one of the worst sins a Windows developer can commit. If your checkin causes the daily build to fail to compile, you get a phone call at home at 3AM or so to drive your butt into the office and fix it.
There's a video that exists (actually one for W2K and one for WinXP) about the daily build process inside Microsoft. I don't know if the video is available outside MS, but it's a PR video so I expect it's out there somewhere. It's a fascinating video to watch the daily build cycle in MS.
Someone may have stolen the source to the Windows "kernel" (which oddly includes about a dozen 640x400 images as part of the binary), but the source to Windows in its entirety is built by many separate groups which all have their own source trees, and it would not ALL be sitting in one convenient spot to copy from.
As I said, it's ALL sitting on virtually every Windows developer's machine.
Not to mention that supposed "files.txt" has lots of mistakes like "source" for FONTS, no source or lib produced from many of the DLLs that are there as part of a standard install (essential stuff like msgina.dll has no source or even a lib in that list, I see no apparent source for ntoskrnl.exe in that list, plenty of others I didn't have to look very hard to find, and it has a WOW64 directory -- AFAIK M$ has no plans on making Win2K for AMD64). ALso there should be a lot more BMPs that get embedded as resources into some of the binaries.
Obviously the entire source hasn't been leaked.
Read documentation on IA64 versions of W2K3 to learn what WOW64 is. (And MS has announced support for AMD64 for W2K3.) It is interesting though that these files appear in the W2K source tree.
