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

    • I bought one of these last year. I really hope I won't have to deal with this crap. My drive is in good condition at the moment.
    • Umm, read my answer again! If you have something to add or contribute, feel free. Otherwise my point was that you apparently dont want faster updates... so you want slower updates by process of elimination. If you have something to contribute, meaningful answers are better.
    • These features described above are good, but far from what developers will like the most. The main feature that developers will care and love the most it's called "Bring Your Own Models". It gives us the ability to connect to LOCAL AI models running on Ollama. The feature it's located on GitHub Copilot tab -> On the model picker where you can select "manage models" instead of paid models and then it will show you the "Bring your own models" window where you can now select Ollama and the endpoint of your local server. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      516
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      82
    5. 5
      ATLien_0
      81
  • Tell a friend

    Love Neowin? Tell a friend!