Recommended Posts

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.

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.

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 :)

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.

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
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)

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
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.

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.

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.

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.

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.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • 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.
    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. I'm sure you will come with the argument of bloat in Microsoft Edge. Sure, but most of that can be fixed with a simple tool (there are many good ones out there for this). Yes, that require a couple of clicks in the same way as it requires several clicks to install 'Google Chrome'. And I'm sure you really love the 4 GB of AI-slop data 'Google Chrome' is downloading for Chrome without you agreeing to it. Fun right? Sure, the way Microsoft is pushing 'Microsoft Edge' on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • 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.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
  • 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
  • Tell a friend

    Love Neowin? Tell a friend!