Recommended Posts

Good evening!

there are many sources saying that build 7061 of windows 7 is now released and out "in the wild" but no one has tested it yet. Is it true ? this build is an RC- Escrow of the OS. WTH is an RC-Escrow ? :o

sources :http://news.softpedia.com/news/Windows-7-B...09-106822.shtml

WTH is an RC-Escrow ? :o

"An escrow build, according to Microsoft sources, means code development is ceased as developers and beta testers hunt for recall class bugs. The escrow code is considered the release to manufacturing code."

-- Taken from here: Article about Windows 2000 RC :)

I'm not saying that 7061 is an escrow build or the RC, just answering your question.

Bad?

Something must be wrong with your system..., the OS appears to be very stable and complete, except for some minor issues that are still being worked out.

I agree with you Build 7057 is by far the best build of Windows 7 I have used so far!!! :)

Build 7057 fixes almost all the bugs I have found in early builds!

I agree with you Build 7057 is by far the best build of Windows 7 I have used so far!!! :)

Build 7057 fixes almost all the bugs I have found in early builds!

Judging from the comments in the forums, it seem that more people have had problems with 57 than the earlier builds.

Judging from the comments in the forums, it seem that more people have had problems with 57 than the earlier builds.

Putting opinion and hyperbole aside you've hit the nail squarely on the head. The evidence in the forum speaks for itself.

For everyone else the fact is that whether or not you've encountered issues with 7057 they exist in abundance. For those that find 7057 to be wonderful or the best build so far it simply means you haven't encountered the bugs yet or use your PC in ways that are less likely to reveal them.

Sorry, but I get annoyed when people (like xendrome) suggest that those encountering issues must have some problem with their installations. If a number of people are reporting the same bugs (as they are with this build) then the evidence would suggest otherwise.

7057 shows the general direction MS are taking and I think it's a good one but they still have to squash some serious bugs and not get carried away with trimming the cake before it's fully baked.

Sorry, but I get annoyed when people (like xendrome) suggest that those encountering issues must have some problem with their installations. If a number of people are reporting the same bugs (as they are with this build) then the evidence would suggest otherwise.

Sorry, but I get annoyed when people (like wiggly1uk2000) use branch builds then wonder whey they're buggy. It's not a release build, that's what happens!

Sorry, but I get annoyed when people (like wiggly1uk2000) use branch builds then wonder whey they're buggy. It's not a release build, that's what happens!

Actually I accept the bugs with good grace (and I would even for an official public build), report them here for the benefit of others and then move on. Are we just supposed to say every build is wonderful when it's not? If there's a bug why on earth would anybody NOT mention it here in the Windows 7 beta forum??? :blink:

Personally I've no complaints about 7057 and I think the general direction of Windows 7 is very positive but I reserve the right to post about any bugs I find regardless of whether or not it's an official public build. Neowin have not as far as I know limited the Windows 7 forum to build 7000. Even people close to MS have posted here regarding other builds.

I'm not so excited considering how bad 7057 was.

Concur....7057 was faster, but seems to freeze alot.

I did a deep/full format first. And, my system is reasonably current; phenom II x4- 810, with 4 gigs of ram.

Plus, 7048 ran like a dream....zero issues that weren't merely me being unable to figure something out. Zero freezes...

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!