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

    • (macOS) Screen zoom was broken for me in beta 1 and it's now working properly in beta 2. In terms of performance and UI design/consistency, these betas are already much better than Tahoe.
    • Less powerful than a PS5 at twice the price! I wonder if they use that for marketing? Totally DoA.
    • Astra 0.6.1 Beta by Razvan Serea Astra is an audiophile music player designed for local music libraries, supporting MP3, FLAC, WAV, AAC, OGG, M4A, OPUS, WMA, AIFF, and more via FFmpeg. It offers gapless playback with pre-buffering, multichannel audio remapping, and Dolby Atmos decoding, ensuring albums play seamlessly while maintaining high-fidelity sound. Astra features real-time DSP visualizers powered by a native C++ engine, including an oscilloscope, spectrum analyzer, and vectorscope. A fully parametric 10-band EQ with live frequency response, built-in presets, and AutoEQ headphone calibration import lets you precisely shape your sound. Playback controls include shuffle, repeat, and drag-and-drop queue management, while the library automatically extracts metadata, album artwork, and supports global search, favorites, and recently played tracking. Additional features include output device selection, delay calibration, customizable themes, fullscreen and mini-player modes, Discord Rich Presence, optional Last.fm scrobbling, and an opt-in local API for integrations. Astra delivers a complete, high-quality desktop audio experience with no telemetry, accounts, or streaming. Astra 0.6.1 Beta changelog: Lyrics Initial XLRC support via @boof2015/xlrc 0.2.0 (#131) XLRC sidecar scanning, manual import, and renderer support Word timing, furigana, translations, voice labels, and translation-priority controls for XLRC Fullscreen lyrics overhaul with additional layout polish Manual lyrics editor with LRC, XLRC, and plain-text modes Drag-and-drop lyrics import plus sync offset controls Clickable synced lyrics for seeking, with popout and transport lyrics updates (#138) Fixed lyrics info sidebar scrolling (#138) Added a workaround for LRCLIB instability Metadata & Library Metadata editor rebuilt as a side panel Virtual DB metadata overrides and optional direct file tag writing Bulk metadata editing for title, artist, album, album artist, genre, year, track/disc numbers, and artwork Undo/redo support for virtual metadata edits Clear overrides action and default save-mode preference Artist page grid view added, with later design and sizing refinements Improved Jump to Playing with smart source, queue, album, artist, and library track targets Fixed smart source jump behavior Playlists Fixed VLC-style M3U import failures (#127) Added playlist export to M3U/M3U8 (#118) Improved imported playlist path resolution and missing-entry preservation Shuffle added to playlist pages (#121) Remove tracks directly from playlist views (#128) Fixed create-playlist-from-track modal closing when clicking inside it (#137) Multi-select quality-of-life fixes Right-click context menus no longer clear multiselections UI & Navigation Fixed UI scaling regressions in sidebar and home surfaces (#122, #123) Fixed transport bar regression (#126) Fixed horizontal scrolling on Home and Library rails Fixed artist grid sizing while searching Updated playlist action buttons and related layout polish Additional fullscreen lyrics visual adjustments Visualization Scopes and visualizers now respect UI scaling settings (#155) Added shared canvas sizing logic for correct DPR/backing-store behavior Canvas sizing tests added for visualizer scaling regressions Discord RPC Discord Rich Presence activity structure refactored Compact status can prioritize title or artist Profile info line can show file info or album Title and artist links can target YouTube Music, Last.fm, or be disabled Optional small Astra badge for cover-art presence Configurable “clear when paused” timing Added Discord activity tests Scrobbling Fixed custom Last.fm2 API profiles being accidentally blocked Expanded scrobbler profile protocol handling coverage Stability & Tests Added/expanded tests for XLRC parsing, lyrics presentation, metadata editor state, playlist import/export path handling, artist grid layout, horizontal scrolling, canvas sizing, and Discord RPC activity building Download: Astra 0.6.1 Beta | 138.0 MB (Open Source) View: Astra Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • How does it compare to the "SeeStar S30 Pro" and the "Vespera PRO 2"?
  • Recent Achievements

    • Week One Done
      Almohandis earned a badge
      Week One Done
    • Rookie
      dorf went up a rank
      Rookie
    • First Post
      mike_rumble earned a badge
      First Post
    • Dedicated
      tuben earned a badge
      Dedicated
    • Week One Done
      mnsgroup earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      501
    2. 2
      +Edouard
      209
    3. 3
      PsYcHoKiLLa
      100
    4. 4
      Michael Scrip
      85
    5. 5
      neufuse
      69
  • Tell a friend

    Love Neowin? Tell a friend!