Windows 7 Official Public Beta

By atleeit
in The Fast Ring (Insider Previews)

 Share

Recommended Posts

Grand Master

+Ryster Subscriber²

Posted
  • Subscriber²
Posted
Just a quick question. Minimal requirements concerning RAM and CPU?

I found the QnA thread and found my answer, sorry for this post!

Theres nothing official right now, all has been said is that if your system runs Vista then it will run 7. Also on the same system you can expect 7 to be at least as fast (performance wise) as Vista assuming you've got decent drivers.

Grand Master

cpu killer

Posted
Posted
I don't know who creamhackered is lol.

He's a pretty well respected member of the Windows Beta community. He's been around for a while now, that I know of at least since the XP/Longhorn betas, and has (most) always had reliable and accurate information. He knows what he's saying, so coming into a thread and claiming what he says is "probably fake" is not wise.

Veteran

IceBreakerG

Posted
Posted

I see. Good info to know. I'm not the type to scream fake at every single post in a beta thread. It's always funny to go back like a year later and see that all the people that were crying fake were completely wrong :)

Grand Master

tomwarren Veteran

Posted
  • Veteran
Posted

The only thing that could change 7000 from being beta 1 is this MP3 fiasco but as far as I am aware they haven't had time to recompile and instead have done a QFE patch to be pushed out :) 7015 was the latest but that will have changed now as all the MS folk are back to work and compiling hard again.

Grand Master

notuptome2004

Posted
Posted (edited)
The only thing that could change 7000 from being beta 1 is this MP3 fiasco but as far as I am aware they haven't had time to recompile and instead have done a QFE patch to be pushed out :) 7015 was the latest but that will have changed now as all the MS folk are back to work and compiling hard again.

hey craem how ya been , anything new in your world

Edited by notuptome2004
Veteran

Snowl

Posted
Posted
atleeit do you know who creamhackered is?

OFFTOPIC:

Wait... So if creamhackered posted "The newest build is 8049" you would believe him?

Im sorry, but a person CAN be wrong, you know.

ONTOPIC:

I hope it comes out tomorow (AUS) or on the 14th(AUS)

Experienced

atleeit

Posted
  • Author
Posted (edited)
I see. Good info to know. I'm not the type to scream fake at every single post in a beta thread. It's always funny to go back like a year later and see that all the people that were crying fake were completely wrong :)

I Don't see myself screaming either lol :D

And these are Pre-RC1's.

There was 6.1.7003, 6.1.7004, 6.1.7012, 6.1.7013 but i haven't head of 7015.

So if it's v6.1.7015.0.(WHAT DATE) ftes could have access to this.

Edited by atleeit
Mentor

Mannlich

Posted
Posted
OFFTOPIC:

Wait... So if creamhackered posted "The newest build is 8049" you would believe him?

Im sorry, but a person CAN be wrong, you know.

ONTOPIC:

I hope it comes out tomorow (AUS) or on the 14th(AUS)

True, a person can be wrong. However, if you look at the reputation that creamhackered has earned for himself, you would find it unlikely that he would be posting information without knowing what he is talking about. As was earlier mentioned, those of us who were around for the XP betas and Longhorn betas can attest to his credibility. It is always entertaining come beta time to see the users that start throwing around build numbers and guesses about release dates as if they have a clue.

Veteran

Snowl

Posted
Posted
True, a person can be wrong. However, if you look at the reputation that creamhackered has earned for himself, you would find it unlikely that he would be posting information without knowing what he is talking about. As was earlier mentioned, those of us who were around for the XP betas and Longhorn betas can attest to his credibility. It is always entertaining come beta time to see the users that start throwing around build numbers and guesses about release dates as if they have a clue.

Im not saying he is wrong. Im just saying, unless he is an Internal Microsoft worker*, he cannot prove, unless he has the dvd/iso on him, so he COULD be wrong. Also, I said I HOPE, not I know. I guess I could say, Its always entertaining come beta time, some user will come and ridicule other users because they are guessing release times, because they DO want to try the new beta software.

* He lives in London, Uk, according to his location.

Mentor

Mannlich

Posted
Posted
Im not saying he is wrong. Im just saying, unless he is an Internal Microsoft worker*, he cannot prove, unless he has the dvd/iso on him, so he COULD be wrong. Also, I said I HOPE, not I know. I guess I could say, Its always entertaining come beta time, some user will come and ridicule other users because they are guessing release times, because they DO want to try the new beta software.

* He lives in London, Uk, according to his location.

I wasn't referring to you in that quote. I was making a general reference to the fact that come beta time, there are so many people that all of a sudden start throwing out dates and build numbers, that it is hard to keep track of who is credible and who is just blurting out numbers. I want to get my hands on the x64 version of this beta just as bad as anybody else. However, all of the guessing in the world isn't going to do any good. I apologize if you perceived it as an attack on you -- I certainly didn't mean for it to be.

Veteran

Snowl

Posted
Posted
I wasn't referring to you in that quote. I was making a general reference to the fact that come beta time, there are so many people that all of a sudden start throwing out dates and build numbers, that it is hard to keep track of who is credible and who is just blurting out numbers. I want to get my hands on the x64 version of this beta just as bad as anybody else. However, all of the guessing in the world isn't going to do any good. I apologize if you perceived it as an attack on you -- I certainly didn't mean for it to be.

It didnt help that you quoted me :pinch: ...

But I get your point.

Experienced

atleeit

Posted
  • Author
Posted (edited)

Connect works, i'm logged in :) no Windows 7 :p

Also 7015.0.081218-1724 does not seem right.

6.1.7013.0 was built 081220-1600 - So how can Build 7015 be built before 7013 am i making sense?

So Build 7015 is 18th Dec 08

And Build 7013 is 20th Dec 08

See where i'm coming from?

v6.1.7003 was 01/12/08

v6.1.7004 was 03/12/08

v6.1.7012 was 15/12/08

Edited by atleeit
This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Posts

    • Microsoft launches Godot Sample to streamline Xbox PC game development on the engine

      By LoneWolfSL · Posted

      Microsoft launches Godot Sample to streamline Xbox PC game development on the engine by Pulasthi Ariyasinghe Microsoft today announced a new endeavor that aims to make it simpler for Godot developers to get their products into the Xbox PC ecosystem. Dubbed the "XBOX Godot Sample," this is a new public reference for developers using the open-source engine. This is set to serve as an example of how Microsoft GDK, Xbox Services, and PlayFab can be integrated into their projects. The sample is available now on GitHub as a working example. This covers key features in gaming projects that developers may need to release their projects on Xbox PC, with everything from matchmaking and game sign-in to gamepad compatibility with Godot being covered. This release is being called the first step in giving Godot developers the tools to bring their games over to Xbox PC, with more changes to come based on feedback and issue reports. However, the company was clear that this is not related to bringing Godot projects to Xbox consoles. The engine's open development model stops it from accessing console SDKs due to the requirement of NDAs and legal contracts. Here's how it explained this Godot sample project's focus: This is a source-only sample, not a product. It's MIT-licensed at the wrapper layer; the GDK and PlayFab dependencies still require their own installs and license acceptance, consistent with our other XBOX samples. There is no set update cadence for support or maintenance. We’ll watch the repo, monitor issues, and iterate where it makes sense, but this isn't a commercial release. That said, we’re excited to hear your feedback and see any community PRs, as we evolve this together. This is the first step in bringing Godot for XBOX on PC. We plan to evolve it over time based on what the community tells us is most valuable. This sample is built specifically for XBOX on PC. It doesn’t include support for XBOX Series X|S or XBOX One. If you’re already building for XBOX Series X|S or XBOX One, please talk with your XBOX representative. If not, you can get started by signing up here. Game developers can find the XBOX Godot Sample by heading to GitHub over here. Documentation on how to get started with Godot for building an Xbox PC project can be seen here.
    • Browser vendors pen open letter to Microsoft saying "enough is enough"

      By Primey_ · Posted

      The nerve of Google to sign this.
    • Browser vendors pen open letter to Microsoft saying "enough is enough"

      By s0nic69 · Posted

      I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • Browser vendors pen open letter to Microsoft saying "enough is enough"

      By The Norwegian Drone Pilot · Posted

      It is notable that around 70% of web browser users choose Google Chrome. However, it is puzzling why anyone on Windows would opt for Chrome when Microsoft Edge is often superior in many aspects and comes pre-installed. Edge collects less data, uses less RAM, and is more optimized for Windows as a native Microsoft product. While some may point to bloat in Edge, much of it can be removed with simple tools, requiring no more effort than installing Chrome. Meanwhile, Chrome reportedly downloads large amounts of AI data (4 GB) without explicit consent. I'm sure you Chrome users love that, or? Although Microsoft’s aggressive promotion of Edge may be questionable, the browser’s current advantages make it a preferable choice over Chrome today, even if Chrome may have been better in the past.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more

      By David Uzondu · Posted

      JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.

  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later

  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!