Recommended Posts

Haha and so it starts, i remember when the first Win 98 beta was leaked back in the day.

yeah people went crazy back then trying to get a copy.. "Come on man just loan me the floppies"

[Off Topic] It would be awesome if you were really Hammond.. I just started watching Top Gear about 2 months ago on satellite and now I DVR it and my wife and kids watch every episode with me. (yes Hammond is their fav).. although I still love Jeremy.

well not this time around but the last time i saved, i dunno.. $400? Beta testers of Vista got a copy for free but i didn't care about that part. I like to see what's next... to me a stable OS is boring. Same thing everyday.. no matter how many skins you put on it there's nothing new to learn about it. I've been using Vista for a few years already and even that's getting a tad boring :)

Beta, well surely it might crash often but you go and dig and figure out why it's crashing and then you learn things that you can apply in other situations where it's similar or same.

well not this time around but the last time i saved, i dunno.. $400? Beta testers of Vista got a copy for free but i didn't care about that part. I like to see what's next... to me a stable OS is boring. Same thing everyday.. no matter how many skins you put on it there's nothing new to learn about it. I've been using Vista for a few years already and even that's getting a tad boring :)

Beta, well surely it might crash often but you go and dig and figure out why it's crashing and then you learn things that you can apply in other situations where it's similar or same.

That's exactly the way I am :)

I stuck with Windows ME until XP was leaked. Devils0wn? Something like that.

Was sticking with ME taking things too far? I don't know, it was a constant battle but a great way to cut your teeth.

Build is pointless since it locks out by June 10th even though it references early May. A second level of WPA kicks in and enforces that the system is not activated after that date.

The task scheduler engine is kinda buggy.

Tiburon

Edited by Tiburon

This being from back in Dec 07, I'm interested in where MS is at right now. I'm guessing they're probably up into the 67xx builds if not higher. The wait for PDC is a killer in this regard. *sigh*

Nor was it implied, but the guy asked whats the point of the leak?

You said to test bugs... I said Microsoft are really gonna appreciate that feedback arent they?

That was happened to Vista. Hundred thousands of testers helped to make it very stable and secure. Why old build? Because MS needs to test out something important from this build. Something important that also exist in other newer builds, but they don't want to show the current state of development and new features. They just need a lot of feedback for something, they don't even want to tell, where this M1 build is enough for testing that unnamed feature. That's why they allowed M1 build to go away.

That was happened to Vista. Hundred thousands of testers helped to make it very stable and secure. Why old build? Because MS needs to test out something important from this build. Something important that also exist in other newer builds, but they don't want to show the current state of development and new features. They just need a lot of feedback for something, they don't even want to tell, where this M1 build is enough for testing that unnamed feature. That's why they allowed M1 build to go away.

Microsoft doesn't sanction build leaks.

Why is it when they release new "Alpha/Beta" releases of upcoming Windows OS's, they Always change the ScreenSaver, it's like the first thing they are thinking about. I would be worrying about making the build more useable/stable/fixing the 400 Security Updates/ etc... But no, they always have to go and change everything that says 2000/XP/Vista to the brand new name right out of the gates.

IMO, I think these changes to the UI should be done at the very end of the development stages, Anyone else agree? It's kind of like the Demo they had the other day with the touch interface and the "I can't really talk about it" taskbar. I would worry more on fixing the kernel and patching everything so it works correctly before I start changing the taskbar or playing with touch sensors. Let's see I can touch the screen all I want but if Windows isn't stable what good is it?

Just my couple of cents (sense)

Why is it when they release new "Alpha/Beta" releases of upcoming Windows OS's, they Always change the ScreenSaver, it's like the first thing they are thinking about. I would be worrying about making the build more useable/stable/fixing the 400 Security Updates/ etc... But no, they always have to go and change everything that says 2000/XP/Vista to the brand new name right out of the gates.

IMO, I think these changes to the UI should be done at the very end of the development stages, Anyone else agree? It's kind of like the Demo they had the other day with the touch interface and the "I can't really talk about it" taskbar. I would worry more on fixing the kernel and patching everything so it works correctly before I start changing the taskbar or playing with touch sensors. Let's see I can touch the screen all I want but if Windows isn't stable what good is it?

Just my couple of cents (sense)

You do realize there is more than one person working on Windows, right? There are multiple teams, one for the kernel, one for the shell, and so on. The guy working on the taskbar probably wouldn't be very well suited for working on the kernel, but that doesn't mean he should sit around doing nothing until that part is finished.

You do realize there is more than one person working on Windows, right? There are multiple teams, one for the kernel, one for the shell, and so on. The guy working on the taskbar probably wouldn't be very well suited for working on the kernel, but that doesn't mean he should sit around doing nothing until that part is finished.

I think it just seems silly to have these included in such an early build. Maybe they should focus on fixing Vista somewhat, then work on all the fixes and core elements for Windows 7. Add the crazy UI in builds that are a little later in the development or use them for internal testing, I don't think changing the Screen Saver is really necessary right now No...

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

    • No registered users viewing this page.
  • Posts

    • Because Chrome is doing it. And no one said anyone had to update immediately. That's silly. They could update every day for all I care as long as it's fast, and the next time the browser restarts, you're good. And the basic point is not to tee it up for bigger updates. As it is right now, all the windows I had open reopen anyway except inprivate.
    • Why? Does anybody actually want this? The constant need to close all browser sessions and wait for a new version to install, just so that there’s a integrated coupon manager feels like a waste of everyone’s time
    • I remember when Louis used to just do interesting Mac/iPhone repairs, now he's boring and just launches "crusades" every week
    • A shame it don't allow people to bypass the MS account, I will stick to using Rufus.
    • Microsoft about to radically change how often your Edge browser updates by Paul Hill Microsoft has just announced that starting with Edge 152, it will be moving to a two-week release cycle for faster, smaller updates. This faster release cadence will begin on August 27. This change comes just several months after Microsoft switched Visual Studio Code to weekly updates. The company said that the Extended Stable releases will remain on an eight-week cycle and that no admin changes are needed to experience the faster release cycle on the Stable channel. The new two-week release cycle will enable the faster delivery of security updates and platform improvements, all while reducing the size and complexity of individual updates. Microsoft claims that organizations will benefit from this change as it offers predictable validation cycles. For organizations that prefer a “more deliberate pace”, the Extended Stable channel remains an option. This change will affect Edge Stable releases on Windows, macOS, Linux, and mobile. The Extended Stable channel will continue to be updated every eight weeks, or every fourth Stable release, for example: versions 152, 156, 160, and 164. The Extended Stable could be a good option for organizations that don’t want the latest updates twice a month and don’t want as much hassle constantly updating browsers. In the case of Visual Studio Code, many of the updates being pushed by Microsoft are AI-related. As we all know, Microsoft Edge has a lot of AI features, so we could see Microsoft pushing more AI, thanks to the faster cycles. On the flip side, quicker releases could mean faster security updates, which is beneficial in a world where AI systems are hunting for software exploits. What do you think? Let us know in the comments. For more updates on Edge, be sure to follow Neowin's coverage. In May alone, we reported on Edge offering in-browser pop-ups to assist users with website compatibility issues, that Edge was losing Copilot Mode, and that Microsoft had fixed a plain-text password bug in Edge. Source: Microsoft 365 Admin Center
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      514
    2. 2
      PsYcHoKiLLa
      185
    3. 3
      +Edouard
      159
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!