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

    • BleachBit 6.0.1 Beta by Razvan Serea When your computer is getting full, BleachBit quickly frees disk space. When your information is only your business, BleachBit guards your privacy. With BleachBit you can free cache, delete cookies, clear Internet history, shred temporary files, delete logs, and discard junk you didn't know was there. Designed for Linux and Windows systems, it wipes clean thousands of applications including Firefox, Microsoft Edge, Google Chrome, Opera, Safari, and more. Beyond simply deleting files, BleachBit includes advanced features such as shredding files to prevent recovery, wiping free disk space to hide traces of files deleted by other applications, and vacuuming Firefox to make it faster. Better than free, BleachBit is open source. BleachBit has many useful features: Delete your private files so completely that "even God can't read them" according to South Carolina Representative Trey Gowdy. Simple operation: read the descriptions, check the boxes you want, click preview, and click delete. Multi-platform: Linux and Windows Free of charge and no money trail Free to share, learn, and modify (open source) No adware, spyware, malware, browser toolbars, or "value-added software" Translated to 64 languages besides American English Shred files to hide their contents and prevent data recovery Shred any file (such as a spreadsheet on your desktop) Overwrite free disk space to hide previously deleted files Portable app for Windows: run without installation Command line interface for scripting and automation CleanerML allows anyone to write a new cleaner using XML Automatically import and update winapp2.ini cleaner files (a separate download) giving Windows users access to 2500+ additional cleaners Frequent software updates with new features Going beyond standard deletion of files, BleachBit has several advanced cleaners: Clear the memory and swap on Linux Delete broken shortcuts on Linux Delete the Firefox URL history without deleting the whole file—with optional shredding Delete Linux localizations: delete languages you don't use. More powerful than localepurge and available on more Linux distributions. Clean APT for Debian, Ubuntu, Kubuntu, Xubuntu, and Linux Mint Find widely-scattered junk such as Thumbs.db and .DS_Store files. Execute yum clean for CentOS, Fedora, and Red Hat to remove cached package data Delete Windows registry keys—often where MRU (most recently used) lists are stored Delete the OpenOffice.org recent documents list without deleting the whole Common.xcu file Overwrite free disk space to hide previously files Vacuum Firefox, Google Chrome, Liferea, Thunderbird, and Yum databases: shrink files without removing data to save space and improve speed Surgically remove private information from .ini and JSON configuration files and SQLite3 databases without deleting the whole file Overwrite data in SQLite3 before deleting it to prevent recovery (optional) BleachBit 6.0.1 Beta release notes: BleachBit 6.0.1 beta is now available for testing. This maintenance-focused release includes bug fixes, updated translations, and a range of safe enhancements. This release fixes a Windows security issue that could allow arbitrary file deletion during privileged cleaning (reported by Zeze with TeamT5). It also adds new cleaners (including a DNS cache cleaner, Claude Code, and Visual Studio Code forks), support for multiple Chrome and Edge profiles, new deep scan options for developer directories like node_modules and venv, and safer, faster file shredding. All Platforms Added cleaners for Claude Code, DNS cache, and many Visual Studio Code forks. Added support for multiple Chrome and Edge profiles. Chrome can now clean downloaded AI models. Deep Scan can optionally remove venv, __pycache__, node_modules, and .angular directories. Deep Scan is faster by skipping directories on the keep list. File shredding is safer, faster, and leaves fewer recoverable traces. Improved handling of cookies, symlinks, Unicode filenames, external processes, and configuration files. Improved Expert Mode warnings and long warning dialogs. Fixed crashes related to cleaner detection, invalid Unicode, and malformed cleaner data. Clipboard is now cleared automatically after shredding files via paste operations. Linux Added AppImage support. Added cleaners for Visual Studio Code, Codeium, Librewolf (.deb), Transmission (Flatpak), and Profanity. Improved Linux trash detection, including Snap-installed applications and mounted drives. Fixed Wayland root CLI issues and several Snap-related problems. Improved package dependencies, AppStream metadata, and desktop file handling. Fixed startup crashes when Python Requests is unavailable. Windows Fixed a security vulnerability that could allow arbitrary file deletion when cleaning with elevated privileges. Added %WindowsSystem% variable support. Improved clipboard clearing using native Windows APIs. Improved installer experience on unsupported Windows versions. Reduced installer size and improved application robustness. Fixed Unicode handling, filename anonymization, Git revision reporting, and splash screen stability. [full release notes] Download: BleachBit 6.0 | Portable | ~20.0 MB (Open Source) View: BleachBit Home page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • DriversCloud 12.1.6 by Razvan Serea With DriversCloud (formerly My-Config.com), you can explore your computer easily, safely and free. The application quickly scans your PC and identifies the hardware and software components. DriversCloud then establishes a list of the different drivers compatible with your OS and hardware. Download the drivers needed for the proper functioning of your computer. To detect your drivers, DriversCloud also displays a detailed summary of your hardware and software configuration, analyzes your BSOD, monitors in real-time your PC voltages and temperatures and lets you share your configuration online. Once the hardware components have been detected, you will be able to obtain with just a few clicks the latest drivers corresponding to the identified hardware. You can record your configuration on the site for free, and can get the corresponding URL to post the configuration to technical forums, e-mail and social networks. You can also download the detection result (the configuration) as a PDF file. To protect the user's privacy and data confidentiality, a 4-level confidentiality system was created that filters the XML marks and gives control to the user. The default level can be modified in the preferences. Using the maximum level will prevent the user from publishing his configuration and generating a corresponding PDF file. In non-connected mode, each XML configuration is stored on the server for one day (for practical reasons). However, you are given the opportunity to manually delete it. Created in 2004, and continually improved, My-Config.com has established itself on the web as a free service to PC users running Windows and Linux operating systems. The service is designed to work with the most common Internet browsers (Edge, Firefox, Chrome, Safari). Download: DriversCloud 64-bit | 20.0 MB (Freeware) Download: DriversCloud 32-bit | 18.9 MB Link: DriversCloud Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      agatameier earned a badge
      Week One Done
    • One Month Later
      agatameier earned a badge
      One Month Later
    • Week One Done
      ssd21345 earned a badge
      Week One Done
    • Contributor
      MarkHughes4096 went up a rank
      Contributor
    • Dedicated
      jordanspringer earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      516
    2. 2
      +Edouard
      189
    3. 3
      PsYcHoKiLLa
      148
    4. 4
      ATLien_0
      96
    5. 5
      Steven P.
      76
  • Tell a friend

    Love Neowin? Tell a friend!