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

    • This Samsung T7 external SSD deal lasts less than a day by Sayan Sen Recently we had covered some nice deals of internal NVMe SSDs which include the 4TB TeamGroup G50 for only $400, the WD_BLACK SN7100 2TB for just $243, as well as the Samsung 990 PRO 1TB for $370. If however you require an external SSD for portability and quick data transfers and have a budget of less than $200 the Samsung T7 1TB model is currently on a limited time deal at just $190, it's lowest price in nearly three months. The deal ends today so you better hurry if you need one (purchase link below). The T7 weighs in at just 72 grams meaning it should be fairly easy to carry around helping in the portability department. Via its USB 3.2 Gen 2 interface the T7 promises sequential read speeds of up to 1050 MB/s and writes of 1000 MB/s. It is also fairly robust with a drop protection of up to 2 meters, though bear in mind that this is not waterproof. For that you will have to choose the rugged T7 Shield. The technical specifications of the Samsung T7 1TB are given in the table below: Specification Value Model Code (1TB) MU-PC1T0T / MU-PC1T0H Interface USB 3.2 Gen 2 (10 Gbps) Dimensions (W × H × D) 85 × 57 × 8 mm Weight 72 g Sequential Read Speed Up to 1,050 MB/s Sequential Write Speed Up to 1,000 MB/s Drop Resistance Up to 2 m (6.6 ft) Encryption AES 256-bit hardware encryption Operating Temperature 0°C to 60°C Non-Operating Temperature -40°C to 85°C Humidity 5% to 95% (non-condensing) Shock Resistance 1,500 G, duration 0.5 ms, 3-axis (non-operating) Vibration Resistance 20–2,000 Hz, 20 G (non-operating) Get it at the link below: Samsung T7 Portable SSD, 1TB External Solid State Drive, MU-PC1T0T/AM, Gray: $189.98 (Sold and Shipped by Amazon US) Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
    • I just wish they would put more love into Virtual Desktops. There is just so much more they could do.
    • Sounds like you just skimmed over the review, I answer all those questions in it. Although I admit I did not test if DTS works over the headphones, when I get some time I will test this. My personal use case is more speaker-driven (I cover this in the review too).
    • It actually does the same exact thing as yours, 7.1 virtual surround over headphones. From the product page: "Experience sound that surrounds you with 7.1 virtual surround, delivering a wider, more immersive soundstage for movies, games, and music." So both of them are two channel, with 7.1 virtual surround that only work in Headphones mode.
  • 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
      183
    3. 3
      PsYcHoKiLLa
      84
    4. 4
      Michael Scrip
      78
    5. 5
      Steven P.
      76
  • Tell a friend

    Love Neowin? Tell a friend!