Recommended Posts

if you ask me it's feak.....

if you zoom in on the picture where the text say;

windows vista beta 2

evaluation copy. Build 5308.winmain_idx01.060126-1800

the background of the text is crappy.....

That is because of jpeg compression artifacts. Same thing has happened around the icons.

I wished they kept Luna as a theme :(

I don't see how hard it is to have it in there.

Classic, Luna and Aero *default*, thats how it should be :)

Thanks for the screenshot, guess all we know is a newish build #.. hehe

^ What's wrong with having a Pentium 3 600mhz? I still got that! (it's sitting somewhere in my grandma's room though) =P lol

Back to topic...all it shows is a new Network (Center) icon and a new Volume icon in the systray....

Even those aren't new. *sigh*

Even those aren't new. *sigh*

We wont see final icons till RC build, and probably it won't look as it looks now. But, for sure many of the icons through the development will be part of shell32.dll. I guess they are playing with the things and final decision about many things isn't made yet. The programming is like an art. MS Developers pretty much finished the code for shell (theme). Now they can skin Windows Vista into anything they want, it is nothing what would take more then a month.

if you ask me it's feak.....

if you zoom in on the picture where the text say;

windows vista beta 2

evaluation copy. Build 5308.winmain_idx01.060126-1800

the background of the text is crappy.....

HAHAHAHHAHA

Looks like someone hasn't saved a jpeg / gif in his/her life.

HAHAHA

All I will say is that while this specific compile isn't the February CTP, but it is an early build of the CTP. It will bare the build number 5308 and will be from the idx01 branch. The build itself installs much faster than any previously release builds, and Thurrot is correct about the Sidebar being in the build. The build is feature complete, although it is not UI complete... meaning the April CTP (aka Beta 2/RC0 equivalent... although the April CTP will not be milestone quality) will contain most of the final UI touches and bits.

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

    • No registered users viewing this page.
  • Posts

    • Microsoft's fast coding model MAI-Code-1-Flash comes to Copilot Business and Enterprise by Karthik Mudaliar Microsoft’s recently announced MAI-Code-1-Flash model is now generally available to GitHub Copilot Business and Copilot Enterprise customers. With this support, organizations can have more centralized policy controls and billing while finally being able to use Microsoft’s lightweight, first-party coding model. According to GitHub’s announcement, Business and Enterprise plan administrators must enable the MAI-Code-1-Flash policy in Copilot settings before developers can access the model. Microsoft says that MAI-Code-1-Flash is for fast, iterative coding work rather than the most demanding architectural or debugging tasks. GitHub’s official model comparison page says that the model is great for "general-purpose coding and writing," while it excels at fast, accurate code completions and explanations Microsoft introduced MAI-Code-1-Flash on June 2 as part of a broader collection of internally developed MAI models. GitHub subsequently expanded support to Copilot CLI, the Copilot cloud agent, GitHub.com chat, GitHub Mobile, Visual Studio, JetBrains IDEs, Eclipse, and Xcode, but said support for managed Business and Enterprise customers was still on the way. In Microsoft’s own benchmark testing, MAI-Code-1-Flash scored 51.2% on SWE-Bench Pro, compared with 35.2% for Anthropic’s Claude Haiku 4.5. Microsoft also claimed that the model used up to 60% fewer tokens on SWE-Bench Verified. Do note that these are vendor-run results rather than independent measurements. The model is billed at provider list pricing under GitHub’s usage-based system. GitHub currently lists MAI-Code-1-Flash at $0.75 per million input tokens, $0.075 per million cached input tokens, and $4.50 per million output tokens. For organizations, the main incentive to use MAI-Code-1-Flash is likely to be efficiency rather than maximum capability. A smaller model that responds quickly and limits unnecessary output is quite useful for repetitive agent tasks at scale, especially after GitHub Copilot’s move toward usage-based billing. The "Flash" model is recommended for fast work and not necessarily for huge repositories with loads of context. It's better if teams compare their output with other larger models, especially if they're working on security-sensitive changes and complex, multi-file work.
    • yes AND no the "original" or plain/normal Optiplex 7010 won't be getting any more new firmware updates BUT the Optiplex SFF/SFF Plus {small form factor}, Micro/Micro Plus & Tower/Tower Plus 7010 editions DO get new updates such as this new one   and here are similar guides from the Dell web site for Dell systems: https://www.dell.com/support/kbdoc/en-us/000390990/secure-boot-transition-faq https://www.dell.com/support/kbdoc/en-us/000347876/microsoft-2011-secure-boot-certificate-expiration
    • AT&T has been spying on US citizens with the NSA for decades.. they just know how to keep it more under wraps.. the evil level is still there.
  • Recent Achievements

    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      462
    2. 2
      +Edouard
      213
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      72
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!