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

    • The laptop in the bedroom is an Acer with i7-10510U CPU. Acer's website states they will not be upgrading it so I had little choice other than disable secure boot. I know next to nothing on these matters so hopefully it will be fine.
    • GitHub removes manual model selection from Copilot free and student plans by Karthik Mudaliar GitHub is removing the ability to manually select an AI model from its Copilot Free and Student plans, making its automatic routing system the default and only way to choose a model. This means users on these tiers will no longer be able to deliberately select a particular OpenAI, Anthropic, Google, or Microsoft model for a task. In its announcement, GitHub said Copilot Auto will dynamically choose what it considers the best model for each request. Free and Student accounts will retain access to models from multiple families, although the available selection will continue to depend on the restrictions attached to each plan. GitHub did not identify a fixed pool of models that Auto will always use, and its documentation warns that model availability can change over time. GitHub describes Auto as more than a random fallback system. On supported surfaces, its task-optimization technology evaluates the complexity of a request alongside real-time information about model health and availability. Straightforward prompts can be routed to faster and less expensive models, while more demanding coding tasks may be sent to higher-cost reasoning models. The company says this approach should reduce rate limiting, latency, and failed requests. Auto generally selects one model along natural prompt-caching boundaries rather than repeatedly switching models during a session, as GitHub found that mid-session changes increased costs without producing sufficient improvements in output quality. Users can still check which model generated a response. In Copilot Chat, the information appears when hovering over an answer, while Copilot CLI and the Copilot cloud agent display the selected model alongside their output. Auto is available in Copilot Chat, Copilot CLI, and the cloud agent, with the exact implementation and release status varying between supported development environments. The latest restriction follows several months of adjustments to Copilot’s individual plans. GitHub temporarily halted new Pro, Pro+, and Student subscriptions in April as it sought to manage demand and service reliability. It later introduced token-based billing and began gradually reopening individual-plan registrations on June 17. Alongside the picker change, GitHub is retiring the “Preview” label from Microsoft-developed models. It argues that the label is no longer necessary because Auto handles model routing and models are continuously updated behind the scenes.
    • Look up 'inflation' kid. Ask an AI for the numbers between both games.
    • Google reportedly set to lose two key Gemini and DeepMind researchers to Anthropic by Karthik Mudaliar Google is reportedly preparing to lose two more prominent artificial intelligence researchers, with Gemini contributors Jonas Adler and Alexander Pritzel planning to join rival AI developer Anthropic. According to a report from Bloomberg, both researchers are viewed internally as important contributors to Google’s flagship Gemini model family. Adler worked on Google’s AI coding efforts, while Pritzel was involved in the process used to train AI systems. Neither company has publicly confirmed the moves. The report also does not say when the researchers will formally leave Google or what positions they will hold at Anthropic. Training a large AI model requires decisions covering its architecture, data preparation, distributed computing infrastructure, and post-training methods that shape how the finished system behaves. Researchers with experience operating at the scale of Gemini are consequently difficult to replace quickly. Both Adler and Pritzel have previously contributed to Google DeepMind’s scientific research as well. They are listed among the authors of the company’s work on expanding AlphaFold protein-structure predictions across entire proteomes, alongside AlphaFold researchers including John Jumper. The reported departures arrive shortly after another important change within Google’s Gemini organization. Gemini co-lead Noam Shazeer is leaving Google for OpenAI, after returning to the search company in 2024 through its deal with Character.AI. Shazeer is particularly well known as one of the authors of the Transformer paper, whose architecture became the foundation for most modern large language models. Anthropic, meanwhile, has been recruiting recognizable figures from other leading laboratories. OpenAI co-founder and former Tesla AI director Andrej Karpathy joined Anthropic’s pre-training team in May. His move, followed by the reported recruitment of several Google researchers, suggests Anthropic is strengthening the research teams responsible for the core capabilities of future Claude models rather than concentrating solely on product and enterprise sales. The competition is complicated by the companies’ extensive commercial relationships. Anthropic competes directly with Google’s Gemini models, but it also relies on Google as an infrastructure partner. In April, Anthropic announced an expanded agreement with Google and Broadcom covering multiple gigawatts of next-generation Tensor Processing Unit capacity. TPUs are Google-designed accelerators used to train and run large AI models. via Bloomberg
    • This article makes my head hurt. Lots of confusing words
  • Recent Achievements

    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
    • One Year In
      Tom Schmidt earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      462
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      124
    4. 4
      Michael Scrip
      79
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!