1st W7 RTM build 7600.16384: Did MS named it cause They like the nos?


Recommended Posts

Some time ago a friend had told me there was no build 7200 in the winmain branch, because the build no. 7200 was reserved for RTM, and win8(or whatever MS would name it later, so ATM we just have to call it win8) was started from build 7301, and will RTM at build 8000.

I had read something like it on WZOR for the build 7200 reservation, then later everybody was predicting RTM is 7300. It came as quite a surprise when RTM was actually 7600.

Recently I learned from another friend on the concept, it seems MS simply had no other better choice than to name the RTM as 7600. It all started with Vista, The Windows QFE Team(Quick Fix Engineering) had reserved the final 4 bits of the binary build string as indications of Service Packs, thus, SP0(i.e. the RTM itself) is [0000]. There are 16 combinations, so there can be 15 Service Packs(7601 thru7615) to fill the available slots, naturally nobody would dream of having so many Service Packs for a single OS.

Then, for a reason beyond my understanding(I am no developer, nor have any interest in it), this caused the necessity that the RTM number has to be a multiple of 16. Furthermore, MS has the tradition to round-up RTM numbers to 100's, so the first candidate for the win7RTM in the 7xxx region would be 7200. MS might have reserved this number for RTM, but had thought better of it, because it is awkward to have the RTM evolved from a earlier build bearing the numbers of 726x.

Now, 400 is the minimum 100-rounded 16-multiple, so after 7200, 7600 is the next candidate, and the next one is 8000. MS would hesitate to use 8000:

- They probably prefer to leave 8000 and 8xxx's for win8.

- Windows API GetVersion could only support the max. build number of 16383(1 number below 2^14), MS may want to leave more room for the later OS's.

- The current softwares can only support 4-digit build numbers, it's something like the 2K bug. If MS could push the requirement of 5-digit build numbers further back, let the software guys to develope 5-digit build number supporting softwares, then by the time a 5-digit build comes out, the "4-digit build only" softwares should all have become deep-buried fossils.

Therefore, MS probably had no choice, they just have to use 7600 as RTM, but compiling a 7600 could be voted down and they couldn't compile another 7600 as next candidate, that's what the "minor builds" come into play.

Now, the QFE sets another condition, in order for HotFix to validate, the first(minimum) minor build number must have the value of [1] for the 14th bit, i.e. the number has to be 2^14(2 to the power of 14) ,i.e. 16384. Therefore, for Vista, win7,win8...., until this system was changed, the minor build number just has to be 16384, and then the next minor build numbers has no further conditions, it could be any number larger than 16384.

So, the first RTM of win7 just has to be 7600.16384; and the next interesting question is: What about windows 8??

Some people had said that win8 couldn't have started when win7 was not RTM, then please note these facts:

- Vista was developed in 5 years, when XP RTM, Vista was almost beginning it's mid-phase of development.

- Win7's first known build was 6.1.5025.winmain.050111-2030; when Vista was RTM in Nov. 06, the nearest known builds(before and after) of win 7 were:6.1.5729.0.winmain.060914-1613 and 6.1.6415.0.debuggers(dbg).070404-1234.

If according to rumor, win8 was developing builds in the 73xx range, if MS wanted to have win8 RTM at 8000, they need to proceed within this range, there is no rule against it, but it would be very awkward to develop new build numbers smaller than 7600.

If they were to start the next win8 build with numbers beyond 7615; than it would be most unlikely that it could RTM at 8000, there is simply too little room to do that.

Personally I would speculate that, just as in the case of win7, win8 would Beta on 8000, the next RTM number candidate would be 8400; but I thought it would be the better choice of 8800.

Edited by FaiKee
Personally I would speculate that, just as in the case of win7, win8 would Beta on 8000, the next RTM number candidate would be 8400; but I thought it would be the better choice of 8800.

:)

nice, thank you for the write up. makes total sense if you are a nut head, ;). very nice.

On 2nd thought I edited the part about people doubting win8, just didn't want to start another fight. :rolleyes:

Absolutely. Mate, it's seriously time for you to have a break. You've been reporting every single thing thats happened with Win7 for months now, reckon it's time to look at other pursuits? ;)

Yeah, starting as of to-day(after this little discussion I mean) I am getting my life back LOL. :laugh:

As I said, I am stuck with 7100RC until the retail comes out, so I wouldn't care about wtf about RTM leaking.

FaiKee: 7600 could be a relative ratio : distance Earth to the Moon divided by 40 years calculated on the 20th July over the sum of the first 16 prime numbers...only through this tiny Window RTM will occur....

Eco must be ROTF on this one (Foucault's Pendulum)

Reserving the lower nybble for SP identification makes a lot of sense, actually, and sounds like something that MSFT would do. And it does explain their W7 version numbering. How they chose the subbuild number (start at 0x4000, or 16384, and just work up) was apparent back when Vista first came out.

Just one nit, though: the valid range for build numbers is 0-32767 (only the first bit of GetVersion()'s high-order word is reserved; not the first two bits).

Edited by code.kliu.org
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Linux 7.1 stable launch looms as Linus Torvalds releases the final release candidate by Paul Hill Linus Torvalds has just released what’s expected to be the final release candidate of Linux 7.1, rc7. The Linux founder said that this RC is not small, but smaller than recent releases, which is a good sign because he expects the stable version to drop next week if things continue on this trajectory. Linux kernels see a merge window for the first two weeks of their life, where developers add new features, then there are about seven or eight weeks of release candidates before the stable version. Typically, there are seven release candidates, but if more time is needed, then an eighth release candidate is released too. This week’s RC’s biggest area of fixes was for GPUs, with networking just behind. Torvalds said that the rest of the release was “pretty random and spread out” with some architecture fixes, driver fixes, filesystem improvements, and build fixes for more unusual configs. In terms of specific pieces of hardware receiving improvements in this update, we had more AMD Zen6 models supported and fixes for AMD SDMA 7.1 and GFX11. Hardware that got improvements includes Lenovo laptops, HONOR laptops, and MSI laptops. Here are the changelogs for those: ASoC: amd: acp: Add DMI quirk for Lenovo Yoga Pro 7 15ASH11 Input: atkbd - add DMI quirk for Lenovo Yoga Air 14 (83QK) Input: atkbd - skip deactivate for HONOR BCC-N's internal keyboard ASoC: amd: yc: Add MSI Raider A18 HX A9WJG to quirk table ASoC: amd: yc: Enable internal mic on MSI Bravo 17 C7VF When the stable Linux 7.1 is released, it will be up to distribution maintainers, such as Canonical and Red Hat, to release the update to their users via the update manager. Some versions of Linux will get it before others, and some will never get it at all. Fedora and Arch-based distros will be among the first to get it, though. If you don’t get it, the security fixes will be backported to your system’s kernel, so you won’t be at risk, but you won’t get newer hardware support, which is fine if your computer works now.
    • Ideally, the algorithm is smart enough to see the real sender ID and non-spoofed address to block it. Ideally.
    • Helium Browser 0.13.1.1 by Razvan Serea Helium is a private, fast, and honest Chromium-based web browser — built for people, with love. It offers the best privacy by default, unbiased ad-blocking, and a clean experience free from bloat and noise. Proudly based on Ungoogled-Chromium, Helium removes Google’s clutter while keeping a fast, efficient development pipeline. With thoughtful touches like native !bangs and split view, Helium is a people-first, fully open-source browser that puts control back in your hands. Privacy, security, and control come first. Ads, trackers, and third-party cookies are blocked automatically, HTTPS is enforced everywhere, and all Chromium extensions work seamlessly — while Google can’t track your activity. Helium’s 13,000+ offline-ready !bangs let you jump straight to sites or AI tools like ChatGPT instantly. Open-source, people-first, and unbiased, Helium delivers a browsing experience that’s fast, secure, and free from noise, ads, and compromises. Helium Browser key features: Performance Fast, efficient, and lightweight — built on Chromium’s optimized engine. Energy-saving and consistent — stays fast over time without slowing down. No bloat — stripped of unnecessary components for maximum speed. Minimalist interface — compact, clean, and distraction-free. Customizable toolbar — hide elements you don’t need. Smooth and stable — no flicker, lag, or animation glitches. Comfort-focused experience — intuitive and unobtrusive. Privacy & Security Best privacy by default — blocks ads, trackers, phishing, and third-party cookies. Unbiased ad-blocking — powered by community filters and uBlock Origin. No telemetry or analytics — zero background web requests on first launch. Strict HTTPS enforcement — warns for insecure sites. Passkeys supported — modern authentication made simple. No built-in password manager or cloud sync — your data stays yours. Extension Compatibility Full Chromium extension support — including MV2 extensions. Anonymized Chrome Web Store requests — Google can’t track extension installs. Extended MV2 support — maintained for as long as possible. Smart Features Native !bangs — browse faster using 13,000+ offline-ready shortcuts. AI integration — use !chatgpt and others directly from the address bar. Offline functionality — bangs work without an Internet connection. Philosophy People-first design — open source, transparent, and community-driven. No ads, no noise, no bias — privacy and honesty over profit. Helium Browser 0.13.1.1 changelog: Helium Windows e13ddd4 update: helium 0.13.1.1 (#285) 77ee94b helium/windows: winsparkle updater (built-in auto-update support on Windows) e501e98 helium/windows: refresh updater patches for m149 008faee helium/win: move versioning patches to separate file e114701 helium/updater: implement system install update notifications c9e3cda helium/winsparkle: verboser errors b8f787c helium/windows: more version migrations cd376ed ci: sign update helper with different description 5d2383a build: wire up winsparkle envs 3ff28ff helium/updater: init ca58f6f helium/change-branding: use helium version in more internal places 75b2625 .gitignore: add resources/generated abe78f2 downloads: add winsparkle dep 4ed4429 build: build mini_installer again fabf8e9 update: helium 0.13.1.1 Helium-Chromium 5bf45fed merge: update to chromium 149.0.7827.53 (#1857) 3bbe6a3c revision: reset to 1 e3525bb6 helium/zen: reorder patch hunks d48bc496 deps: update ublock to 1.71.0 (#1875) d4e58802 helium/ui: redesign infobar, optimize and rename zen (#1868) c20175cf helium/ui/infobar: redesign, draw proper borders, fix webview relations e8a1bfc1 helium/zen: rename Zen to Frameless in UI, remove feature gates bf560c6a helium/layout: optimize zen top reveal, move out of experiment dir 34ef5f26 patches/brave/chrome-importer: remove os_crypt-related dead code 99cef46c helium/ui: clean up patches, fix accidental string OS gates 5b7dd06c devutils/i18n: add clean command (#1869) 7a32267e helium/updater: add win scaffolding, tighten arch conditions (#1866) d856d800 ci: complete cirrus port to github actions (#1867) c362740d patches: update for chromium 149.0.7827.53 b8a66095 merge: update ungoogled-chromium to 149.0.7827.53 a3a5471d Update to Chromium 149.0.7827.53 c6a41202 helium/updates: decouple update url from helium services + reformat (#1827) 94344c47 Update to Chromium 148.0.7778.215 95f6fe1c Port CirrusCI jobs to github actions (#3776) Download: Helium 64-bit | Portable 64-bit |~100.0 MB (Open Source) Download: Helium ARM64 | Portable ARM64 Links: Helium Home Page | macOS | Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      248
    3. 3
      Steven P.
      71
    4. 4
      ATLien_0
      68
    5. 5
      +Edouard
      68
  • Tell a friend

    Love Neowin? Tell a friend!