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

    • What I like about Paint is using it almost exclusively for cropping and resizing images I get elsewhere--it's quick, easy and cheap... I keep it glued to my taskbar, in fact. Also, the clipping tool comes in handy, as well (hit print scrn on the keyboard and it activates immediately.)
    • I still remember it fondly today. It was so cool to work in 64-color Half Bright mode and 4.096-color HAM mode (interlaced) when x86 was still in 4-color CGA or 16-color EGA low res. C= never realized what it had until it was far too late--the failure of C= was the failure of its top management. The C= Amiga was 20 years ahead of its time, I always thought. It didn't hurt that in only 512k of chip memory, the Amiga could preemptively multitask when Apple was still doing gray scale graphics on tiny screens and along with everyone else was doing cooperative multitasking (running more than one app at a time in resident memory, but you could only run one of them at a time--had to manually switch between them.) I had a ball with AREXX scripting running between programs that had AREXX ports so that when you sent other applications data and instructions, those running applications could process the same in real time to output! Memories...
    • I'm not sure about that, but it at least "does" a version of 7.1 that this brand new card doesn't....
    • Floorp 12.15.2 by Razvan Serea Floorp is a cutting-edge web browser that combines the trusted foundation of Mozilla's Firefox with a unique Japanese perspective, offering users an exceptional online experience. This open-source browser prioritizes privacy, customization, and security. Floorp is transparent, with no user tracking or data sharing, and it's completely open source. With a strict no-tracking policy and full transparency, your personal information remains private. As an open-source project, Floorp not only shares its source code but also its build environment, inviting users to contribute and build their unique versions. The regular updates, based on Firefox ESR, ensure that you always have the latest features and security enhancements. Floorp key features: Strong Tracking Protection: Floorp offers robust tracking protection, safeguarding users from malicious tracking and fingerprinting on the web. Flexible Layout: Customize Floorp's layout to your heart's content, including moving the tab bar, hiding the title bar, and more for a personalized browsing experience. Switchable Design: Choose from five distinct designs for the Floorp interface, and even switch between OS-specific designs for a unique look Regular Updates: Based on Firefox ESR, Floorp receives updates every four weeks, ensuring up-to-date security even before Firefox's releases. No User Tracking: Floorp prioritizes user privacy by abstaining from collecting personal information, tracking users, or selling user data, with no affiliations with advertising companies. Completely Open Source: The full source code for Floorp is open to the public, allowing transparency and enabling anyone to explore and build their own version. Dual Sidebar: Floorp features a versatile built-in sidebar for webpanels and browsing tools, making it perfect for multitasking and quick access to bookmarks, history, and websites. Flexible Toolbar & Tab Bar: Customize your browser with Tree Style Tabs, vertical tabs, and bookmark bar modifications, catering to both beginners and experts in customization. User-Centric Web Experience: Floorp prioritizes user privacy and collaboratively blocks harmful trackers. Floorp 12.15.2 changelog: fix: reset tab drag state on dragend to prevent position offset (#2488) by @Ryosuke-Asano in #2497 fix(workspaces): hide split view wrapper when all tabs are hidden by @Ryosuke-Asano in #2495 fix(split-view): prevent stuck pointer-events:none after drag on web content by @Ryosuke-Asano in #2492 feat(design): add Gecko 152 CSS variable aliases and Lepton compatibility layer by @Ryosuke-Asano in #2494 fix(workspaces): exitOnLastTabClose no longer quits Floorp when closing the last tab by @Ryosuke-Asano in #2498 Download: Floorp 64-bit | 95.0 MB (Open Source) Links: Floorp Website | Github Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • I can barely recall getting web results from a file search... I must've turned it off long ago. 26H2 is Insider's Preview build 26300.8697, which I am running, atm. It is not available for people running the standard commercial builds of Windows--only for the beta test Insider's group. But anyway, as mentioned in the thread, this feature has been around for a long time...
  • 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
      507
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      84
    4. 4
      Michael Scrip
      78
    5. 5
      Steven P.
      76
  • Tell a friend

    Love Neowin? Tell a friend!