Recommended Posts

I'm wondering if 6000 will be the lucky build number that Vista will be considered "complete" and released to manufacturerers. My guess is that the 5500-series will be RC1, with 5700-5800+ being RC2, but we'll see ;)

Sounds pretty cool :). I'm just wondering what day and what time we are expecting this build to be released?

Wait a minute, every build I tested on Windows Vista had no problems except compatibility and performance, I have only 512 MB RAM Memory, are you saying this will be as fast as Windows XP for me now because that performance improvement?

Another thing, has anybody else noticed were flying through the 5400s quickly, just as I remember it felt like yesterday I was testing build 5270 and now there going so fast through the 5300s and 5400s, we had only 2 builds in the 5400s and now were heading to the 5500s almost! The 5200s were the longest to me!

Well, MS branches the builds so that they can clean up milestone releases...so a while before 5384 (B2), they started work on the 5400s, with 5384 being the last build of the 5300s. After RC1, every build should be in the 5500 series, unless MS does 30+ builds before RC1 (some MS people are using 5475 right now). The 5200 series was created when the code was branched for B1, so everything from 5200 to 5384 is work on B2, which is 10 months of code, which is why it seemed so long. Hope this makes sense, though, it can get kinda confusing lol.

So...

Alpha < 5112

Beta 1 = 5112

Beta 2 Branch = 5200 to 5384

Beta 2 = 5384

RC1 branch = 5400

RC1 = somewhere around 5500, likely less though

RC2 branch = either 5500 or 5600, if MS runs over the 5500 series

RC2 = somewhere from late 5600 to 5800

RTM = somewhere around 6000

I think :wacko: lol

Well, MS branches the builds so that they can clean up milestone releases...so a while before 5384 (B2), they started work on the 5400s, with 5384 being the last build of the 5300s. After RC1, every build should be in the 5500 series, unless MS does 30+ builds before RC1 (some MS people are using 5475 right now). The 5200 series was created when the code was branched for B1, so everything from 5200 to 5384 is work on B2, which is 10 months of code, which is why it seemed so long. Hope this makes sense, though, it can get kinda confusing lol.

So...

Alpha < 5112

Beta 1 = 5112

Beta 2 Branch = 5200 to 5384

Beta 2 = 5384

RC1 branch = 5400

RC1 = somewhere around 5500, likely less though

RC2 branch = either 5500 or 5600, if MS runs over the 5500 series

RC2 = somewhere from late 5600 to 5800

RTM = somewhere around 6000

I think :wacko: lol

Numbers do not mean a single thing to Microsoft. The number just stands for how many times Windows Vista was compiled.

^^^ yeah the numbers mean how many times it was compiled. or think of it this way. every bug fixed, is a revision. so 5257 compared to 5256 only has one bug fixed. i think thats how they do it.

wow 5500 bugs already. and were not even at rc1 yet. plus that ads anoth 5000+ bugs after its finalized l ol

Numbers do not mean a single thing to Microsoft. The number just stands for how many times Windows Vista was compiled.

Um...I never said that they did. I was just explaining that they branch the code and start a new series depending on the milestone. Believe me, I've been following Vista ever since I heard about it...which was, oh, 3 or 4 years ago...I think I know what build numbers are

^^^ yeah the numbers mean how many times it was compiled. or think of it this way. every bug fixed, is a revision. so 5257 compared to 5256 only has one bug fixed. i think thats how they do it.

wow 5500 bugs already. and were not even at rc1 yet. plus that ads anoth 5000+ bugs after its finalized l ol

no, there isn't a new compilation for each bug...many bugs can be fixed in each build. Builds take several hours to compile, so theres usually about one every day, roughly. FYI, XP left of on build 2600, so Vista takes up from there, meaning there have been almost 2900 builds of vista/longhorn (the latest build I've seen is 5475). The build numbers denote the build of NT, as each OS after NT has been an update of the last, technically.

Edit: that 2900 builds of longhorn/vista isn't correct. I forgot to add the difference for the gap between XP (and its multiple versions) and longhorn, and I forgot about server 2003. So that number is way off. The earliest longhorn build I've found is 3646 from June 12, 2002. So it probably started at around 3600. I guess.

Edited by pipdo
^^^ yeah the numbers mean how many times it was compiled. or think of it this way. every bug fixed, is a revision. so 5257 compared to 5256 only has one bug fixed. i think thats how they do it.

wow 5500 bugs already. and were not even at rc1 yet. plus that ads anoth 5000+ bugs after its finalized l ol

1 bug fix isn't equivalent to 1 new build. Connect has over waaaaaaaay more than 5000 bug reports ;). And they don't start at build 0. Don't they round off to a nice final number anyways?

During the development stages they go up one build number for every time they compile. That's all there is to it. Once they go gold, however, they round it off to a nice clean number. It's been that way since at least Windows 9x. New versions of Windows are compiled internally only for a while before testers are brought on, so no beta tester's seen 2601 or will see (if Vista ends at 6000) 6001. I doubt Vista will RTM at 6000, though. My guess would be 5800 at the most.

There WILL be another public release, it's called RC1. If you ordered the beta 2 DVD kit you'll get the RC1 DVD kit.

But anyway...I can't wait until this weekend! :D :woot:

What about people that got Vista beta 2 via the public download and activated it?

I guess normally if a build is to be released then it would have been by now...

:laugh: Its only just about midnight in Redmond (on a Friday night/Saturday morning); so there's quite a bit of the "weekend" left before that claim even makes any sense -- they usually spend their Saturdays working on getting the files cached on the 3 locations, and then they "let 'er rip". (When its going to be a "weekend release") So give it some time, lol.

I hope you are right aeden_p. I'm tired of 5456.

If you want to know the truth, I've recently (that is, in the last hour or so) heard from a few people close to Microsoft that they're on their second re-compile, and that while they'd love to get the build to us as quickly as possible, it appears its not going to arrive "this weekend".

To be fair, though, Microsoft never claimed they would be dropping the build this weekend; the only quote is of a Microsoft exec from that news story having said its coming "in the next few days".

Edited by aeden_p

I'm just glad there are youngin' like you guys out there with enough RedBull to stay up, download and run this

stuff. Us old folks just can't screw with beta sofware anymore.

I remember back in my younger days, downloading every beta I could get my hands on to play with.

Not anymore......too tired after work to fool with it.

Thanks for providing a service to the rest of us :yes:

:alien:

Mini-Update: Apparently they're (and already were) farther than a 2nd re-compile; but its still not coming this weekend. I doubt they'll drop anything midweek, and the situation really isn't that "fluid", to be perfectly honest. But rest assured, in due time, we'll be seeing an interim.

Mini-Update: Apparently they're (and already were) farther than a 2nd re-compile; but its still not coming this weekend. I doubt they'll drop anything midweek, and the situation really isn't that "fluid", to be perfectly honest. But rest assured, in due time, we'll be seeing an interim.

of which build? 5472? because Paul Donnelly was using 5472.4 as of yesterday morning. Unless they chose a different build to release...

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Leave Secure Boot off, the Optiplex 7010 isn't getting a firmware update to support the changes...
    • Microsoft confirms Windows 11 26H2 to finally get one of the most requested features by Sayan Sen This past week Microsoft officially confirmed Windows 11 version 26H2 with the latest build, 26300.8697, for testing in the experimental Insider channel. The company also published more details about it mainly directed towards IT admins and system admins. Essentially version 26H2 will be delivered via an enablement package (eKB) over Windows 11 25H2. If you are wondering about some of the upcoming features in the next Windows version, one of them is certainly very interesting as Microsoft has confirmed it is finally bringing one of the most overwhelmingly requested features ever. March Rogers, the Partner Director of Design at Microsoft, recently highlighted some of the Search improvements that the company is testing, and during the interaction with users on X where he posted it, Rogers also confirmed that the company is working on disabling web search results inside Search. This is something which many users find quite annoying as Windows would often serve them links to Bing which it feels could be more helpful rather than bringing up the actual object or app the user may be searching for on their PC. Finally though the company is prioritizing local file search over the web. However the feature could not be disabled for many users as not all new features are immediately rolled out to everyone. Image via phantomofearth (X) Windows enthusiast phantomofearth who likes to dig deep into new builds uncovered the IDs you will need to enable these features. Using the following feature IDs the new Search-related features landing in Windows 11 26H2 can be used. Follow the steps below to enable the new Search experience on Windows 11 build 26300.8697: Download ViveTool from GitHub and unpack the files in a convenient and easy-to-find folder. Press Win + X and select Terminal (Admin). Switch Windows Terminal to the Command Prompt profile with the Ctrl + Shift + 2 shortcut or by clicking the arrow-down button at the top of the window. Navigate to the folder containing the ViveTool files with the CD command. For example, if you have placed ViveTool in C:\Vive, type CD C:\Vive. Type vivetool /enable /id: and press Enter. Restart your computer. If you change your mind and want to restore, repeat the steps above and replace /enable with /disable in the commands on steps 5 and 6. Delightedly and perhaps also expectedly, once you disable web search and other such bloat, the Windows 11 Search is said to get snappier as remarked by another Windows enthusiast Xeno.
    • Makes me think of Family Guy - "Carl Sagan's Cosmos... edited for Rednecks" 🤣 https://www.youtube.com/watch?v=Ljt5iESYA7k&t=2s
  • Recent Achievements

    • Dedicated
      Almohandis earned a badge
      Dedicated
    • Dedicated
      JuvenileDelinquent earned a badge
      Dedicated
    • First Post
      DrWankel earned a badge
      First Post
    • Reacting Well
      DrWankel earned a badge
      Reacting Well
    • Week One Done
      Supreme Spray LV earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      505
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      84
    4. 4
      Steven P.
      76
    5. 5
      Michael Scrip
      76
  • Tell a friend

    Love Neowin? Tell a friend!