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

    • Kdenlive 26.04.2 by Razvan Serea Kdenlive is an acronym for KDE Non-Linear Video Editor. It works on GNU/Linux, Windows and BSD. Through the MLT framework, Kdenlive integrates many plugin effects for video and sound processing or creation. Furthermore Kdenlive brings a powerful titling tool, a DVD authoring (menus) solution, and can then be used as a complete studio for video creation. Kdenlive supports all of the formats supported by FFmpeg or libav (such as QuickTime, AVI, WMV, MPEG, and Flash Video, among others), and also supports 4:3 and 16:9 aspect ratios for both PAL, NTSC and various HD standards, including HDV and AVCHD. Video can also be exported to DV devices, or written to a DVD with chapters and a simple menu. Video editing features: Multi-track editing with a timeline and supports an unlimited number of video and audio tracks. A built-in title editor and tools to create, move, crop and delete video clips, audio clips, text clips and image clips. Ability to add custom effects and transitions. A wide range of effects and transitions. Audio signal processing capabilities include normalization, phase and pitch shifting, limiting, volume adjustment, reverb and equalization filters as well as others. Visual effects include options for masking, blue-screen, distortions, rotations, colour tools, blurring, obscuring and others. Configurable keyboard shortcuts and interface layouts. Rendering is done using a separate non-blocking process so it can be stopped, paused and restarted. Kdenlive also provides a script called the Kdenlive Builder Wizard (KBW) that compiles the latest developer version of the software and its main dependencies from source, to allow users to try to test new features and report problems on the bug tracker. Project files are stored in XML format. An archiving feature allows exporting a project among all assets into a single folder or compressed archive. Built-in audio mixer Kdenlive 26.04.2 changelog: Remove not needed actions from render info, fix rough size calculation for rendering. Fix clip sometimes not inserted in timeline when moving vertically in bin drag. Fix transcoding from clip properties. Cleanup render profile audio quality. Use percent based value for audio quality, and adjust the range accordingly per codec. Fixes bug #520750 Enforce even numbers for render width/height. Fixes bug #520737 Fix nightly flatpak - disable rnnoise until implemented. Fix missing initialization. Edit mediacapture.cpp. Fix document unnecessarily marked as modified on opening, triggering a backup request. Fix incorrect detection of missing and remote clips causing unwanted backups. Fixes issue #2194 Fix tests. Fix tmp files copied to wrong location when setting project folder. Fixes bug #467740 Fix color clips not selected on creation. Use QFileInfo instead of QUrl/QDir to try fixing Windows shared drives. Fixes bug #451413 Fix timeline preview incorrectly invalidated when a track with effect duration changed. Fixes bug #514541 Fix missing var. Display paths in native format in render widget. Fixes bug #520428 Simple splash: fix pressing return always triggered the same button. Minor update to simple splash. Fix unwanted clips added to timeline and cleanup. Fixes issue #2190 Minor layout improvements to welcome screen, add Quit and Open shortcuts. Fix broken welcome dialog layout in tiling compositors. (craft) Limit the number of CPU cores used during a Windows build with mingw as some .cpp files are memory intensive to build. (kde-ci) Limit the number of CPU cores used during a build as some .cpp files are memory intensive to build. (kde-ci) Cleanup old entries. Another fix for animation crash. Fix uninitialized function - crash on create animation. Another attempt to fix MacOS permissions. MacOS: fix bundle release version. Fix MacOS plist path. Fix MacOS build. Explicitely link against Qt::Core. Download: Kdenlive 26.04.2 | 128.0 MB (Open Source) Download: Standalone Executable View: Kdenlive Home page Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Here's how to watch the Xbox Games Showcase today and what to expect by Pulasthi Ariyasinghe The June games showcase week has been a packed one, with everything from major presentations like Sony and Summer Game Fest to indie-focused reveals coming in almost every day. Now, it's almost time for another big one, with Microsoft bringing its Xbox Games Showcase back later today. This is a double feature too, with a Gears of War E-Day deep dive also being attached to it. For anyone wanting to tune in online, the 2026 Xbox Games Showcase is kicking off at 10 AM PT | 1 PM ET | 6 PM BST | 7 PM CEST later today, June 7. The event will be available to watch on the official Xbox YouTube (4K 60FPS), Twitch, Facebook, Steam, Amazon Live, and other portals. Separate livestreams for American Sign Language and Audio Description will also be available. "This year marks 25 years of XBOX, and this Showcase is poised to be a true celebration, offering world premieres, new gameplay, fresh updates, and more for a swathe of projects we cannot wait to share," said Microsoft about this presentation. With a new CEO behind it that is pulling off some interesting moves, Xbox may have some surprises to reveal today. New looks at first-party games like Halo Campaign Evolved from Halo studios, Fable from Playground Games, InXile Entertainment's Clockwork Revolution, Mojang's Minecraft Dungeons II, and Call of Duty: Modern Warfare 4 from Infinity Ward are to be expected here. We may finally get to see the new Blade from Arcane Studios in action and a new Persona game from Atlus at the showcase too. Surprise announcements may also arrive from other Microsoft-owned studios like Bethesda, MachineGames, Ninja Theory, Obsidian, Rare, World's Edge, or Blizzard. Considering how every new release nowadays is staying away from November and December to avoid Grand Theft Auto VI's release, any launch dates Microsoft announces will probably skip those months as well. Once the Xbox Games Showcase ends, Microsoft will immediately kick off the Gears of War: E-Day Direct. This deep dive into the upcoming prequel from The Coalition should attach gameplay footage and perhaps a release window to the highly anticipated project.
    • People in the '50s and '60s had the same attitude, and we're still here over a half century later.
    • So after some fiddling I was able to get it to run at a pretty stable 30FPS. I'm slightly surprised about how much fiddling I had to do to get there though given what I thought was reasonable hardware: Processors: 16 × AMD Ryzen 7 7840HS w/ Radeon 780M Graphics Memory: 16 GiB of RAM Graphics Processor 1: AMD Radeon 780M Graphics Graphics Processor 2: AMD Radeon RX 7700S I think I could do it better if I use Linux rather than Windows, Windows RAM usage is stupid without stripping the system down. But once I got it working in a reasonable state, it was so awesome! I felt like a new Bond! If anyone has any advice to get things going a bit smoother FPS-wise, I'd appreciate it.
    • Something is rotten in the state of Denmark Australia
  • Recent Achievements

    • Dedicated
      Mark Spruce earned a badge
      Dedicated
    • Collaborator
      conkir earned a badge
      Collaborator
    • Rising Star
      olavinto went up a rank
      Rising Star
    • One Month Later
      lamborghiniv10 earned a badge
      One Month Later
    • Week One Done
      lamborghiniv10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      482
    2. 2
      PsYcHoKiLLa
      256
    3. 3
      Steven P.
      74
    4. 4
      +Edouard
      70
    5. 5
      FloatingFatMan
      69
  • Tell a friend

    Love Neowin? Tell a friend!