Recommended Posts

It?s not much of a secret at this point, but CEO Steve Ballmer is expected to announce official availability of the closed Windows 7 Beta 1 release during his Consumer Electronics Show keynote address on January 7. The official (non-Torrented) Beta 1 bits should be available to pre-approved Windows 7 Beta 1 testers later Wednesday night or early on January 8.

Ditto with Windows 7 Server, a k a Windows Server 2008 R2. The private Beta 1 release of that product is scheduled for late January 7/early January 8, I?m hearing.

I?ve gotten a number of questions from readers this year already about the expected public betas of these products. I?ve made some discreet inquiries.

The public (the one and only) beta of Windows 7 client and server could be released simultaneously with the private Beta 1 builds this week, according to some of my sources. What?s the point of a simultaneous public and private beta? The private testers? feedback will get top priority; the public beta will be more of a milestone marker than anything else.

One source of mine said the Windows Server 2008 R2 code definitely will be available to the public this week, but was less sure about client. He said he thought the public beta of Windows 7 client might lag by a week or so.

Update: Nope. It?s going to be sooner, not later. The latest word: The public beta of Win 7 client is due to hit Friday, January 9, according to a source familiar with Microsoft?s plans. The public beta of Win 7 Server is due to hit a day earlier, January 8, the source added.

Microsoft officials declined to comment as to when testers ? public or private ? should expect to get the new Windows 7 client and server builds.

Bottom line: If the tipsters are on their game, anyone who wants to test Windows 7 client and Windows 7 server should be able to do so starting this week?. And if you?re a consumer in the market for a new Windows PC but want the flexibility to upgrade to Windows 7 for free, it sounds like you should wait until July 1, 2009, to make your purchase?.

http://blogs.zdnet.com/microsoft/?p=1792

Update: Nope. It?s going to be sooner, not later. The latest word: The public beta of Win 7 client is due to hit Friday, January 9, according to a source familiar with Microsoft?s plans. The public beta of Win 7 Server is due to hit a day earlier, January 8, the source added.

I heard that MS Netherlands informed the Dutch press in a meeting yesterday that the public beta of Win 7 will be released on January 9.

Fact: On average 64bit run programmes 10% faster than 32bit.

64bit apps also use more memory ;) Did you know that fact too?

Faster because 64bit apps can handle integers 4 words long instead of 2 words in 32bit. They are generally faster when it comes to crunching numbers.

Care to back that up with some sources? I've heard nothing but the contrary (I run 64-bit Vista, btw, so I'm in no way biased against it)

dword

http://msdn.microsoft.com/en-us/library/cc...PROT.10%29.aspx

qword

http://msdn.microsoft.com/en-us/library/2s70e2x4.aspx

If I use a pointer to a memory address in a 64bit OS my pointers will always be 8bytes. Same pointer to memory address in a 32bit OS is only 4 bytes.

Why? Because If I want to address 64bits of memory I need to use pointers that are 64bits long to hold the memory address of the type that its pointing to. So my pointers on the stack now take up two times as much stack seg memory.

it might not seem like much 4bytes here, 4 bytes there, but classes /structs with a lot of pointers and qword members slowly add up in size and that means you will use more memory to store that data.

programming 101.

[tin foil hat]Is there any thought on if these "leaked" copies of win7 found on torrent sites haven't been tempared with and have spyware/root kits on them?[/tin foil hat]

Care to back that up with some sources? I've heard nothing but the contrary (I run 64-bit Vista, btw, so I'm in no way biased against it)

Let me clarify some things about 64-bit.

The x64 (AMD) mode is not an emulation mode like IA64. That is, 32-bit Software run natively in a mode known as "Compatibility" mode of the 64-bit CPU. Therefore, any application as long as its code does not jump back and forth to 64/32 big segments, will run as fast (or as slow) as an 64-bit native one.

What happens with Win32 applications that make system calls or otherwise mess with the kernel? Because the kernel in x64 is only 64-bit (there is no WOW64 for kernel), the code has to jump into x64 and get back to 32-bit segments when they make a system call. Therefore they are slower in theory when running under x64.

The cost, if any, is negligible of course, but in exchange of that you get other features that may or may not increase the speed of the application, that is, SSE/SSE2 instructions by default, a full 4GB of address space of the 32-bit app, PAE by default and some (more developer-wise) stuff.

So an older 32-bit app that wasn't designed to be run under wow64 will probably run slower. The difference is not noticeable even with most developing testing tools and of course it is invisible to the end user. But a 32-bit app that can take care of the extra features under wow64 will probably run faster.

64-bit apps will surely run faster than their 32-bit counterparts under a 32-bit OS because of the nature of programming under x64, including additonal CPU registers, fast calls between procedures and some more. The % difference depends on the application. In notepad might be 0.0001% , in a time critical processing software it might be way over 100% as I 've tested. In addition, they have the entire address space and ram.

Conclusion: x64 at the moment is better than x86 if you have a reason. Most people don't have one currently. But If you have a reason, the x64 is the way to go.

[tin foil hat]Is there any thought on if these "leaked" copies of win7 found on torrent sites haven't been tempared with and have spyware/root kits on them?[/tin foil hat]

I guess that's just a risk some people are willing to take.

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!