A deep dive into Windows 7 (build 6801)

A deep dive into Windows 7 (build 6801)

Summary: Microsoft took the wraps off Windows 7 for the first time at the Professional Developers Conference in Los Angeles three weeks ago. Since returning from PDC, I’ve been installing and using Windows 7 on a variety of hardware platforms (eight distinct desktop and portable systems so far). My immediate goal is to learn as much as possible so I can begin writing my next book. The deeper I dive into Windows 7, the more I discover, including subtle changes and tweaks that aren’t obvious in a first look. In this post and its accompanying image gallery, I’ll share some of those details with you.

SHARE:

Special Report: Windows 7

Microsoft took the wraps off Windows 7 for the first time at the Professional Developers Conference in Los Angeles three weeks ago. That public unveiling and the widespread availability of a pre-beta release of the Windows 7 code (build 6801) inspired a slew of first looks (including mine). But after that initial flurry of activity, most of the interest quickly subsided.

Since returning from PDC, I’ve been installing and using Windows 7 on a variety of hardware platforms (eight distinct desktop and portable systems so far). My immediate goal is to learn as much as possible so I can begin writing Windows 7 Inside Out. And there’s plenty to learn. The deeper I dive into Windows 7, the more I discover, including subtle changes and tweaks that aren’t obvious in a first look. In this post and its accompanying image gallery, I’ll share some of those details with you.


 Image Gallery: I look carefully at the new and redesigned features in the pre-beta release of Windows 7.  Image Gallery: Evolution of the Windows interface Image Gallery: Easier access to the preview pane 

As I work with the new OS, I’m finding myself paying much more attention to small details. In fact, Windows 7 is the first Windows release I’ve ever used that looks like it was designed and not just bolted together from projects built in parallel by disconnected development teams. In the two-plus years since Windows Vista was released, critics have noted its many user interface inconsistencies – Long Zheng even put together the Aero Taskforce web site to highlight the most egregious examples. Many of those flaws have been fixed in Windows 7. In many cases, you have to compare the two systems side by side to notice the difference. I’ve highlighted many of those examples here.

The first wave of Windows 7 coverage included plenty of praise for its stability and polish. That’s true, but it’s also an incomplete picture. The more I work with this early release of Windows 7, the more I see the little glitches, the unfinished pieces, and the bugs. Despite its impressive stability and polish relative to other Windows projects at similar stages of development, this is truly a pre-beta release. Given that this build was locked down three months ago, those little flaws don’t bother me too much.

The purpose of this post is not to review Windows 7. It’s way too early for that. Rather, my objective is to call attention to the changes and design decisions that have gone into the product so far and to highlight features and changes you might not have noticed in the flurry of initial coverage. I’ve done no performance testing, and have no plans to do any, at least with this build. Any publication that would devote more than a paragraph to benchmarking an early build like this one is guilty of journalistic malpractice, in my opinion.

For this deep dive, I’ve taken a closer look at five areas of Windows 7, all of which are significantly changed in this release.

Use the links above to jump to any topic you find interesting, or click below to continue reading.

Next page: Death of the drive letter? -->

<-- Continued from Page 1

Windows Explorer

If you look at the fossil record of Windows Explorer, you’ll see an evolution from its humble File Manager roots to something akin to an all-purpose browser capable of handling a variety of data types. In XP, the Folders List to the left of the Explorer data pane is optimized for drilling through storage hierarchies that start with drive letters. Vista muddied the waters slightly with a navigation pane that can show shortcuts to favorite folders, a tree-style Folders list, or both.

Windows 7 tries to bury tree-style navigation even more deeply by highlighting libraries as the predominant element in the navigation pane.

win7dd_small_page_2.jpg
For a closer look at all the changes in Windows 7, see the image gallery that accompanies this post.
Libraries are collections of physical locations that appear as a single virtual folder in the navigation pane. Windows 7 includes a handful of predefined libraries for documents, downloads, music, pictures, and videos. You can edit these libraries or add custom libraries to serve the needs of a project. So, for example, I might create a ZDNet library that aggregates content from my Windows Live Writer Drafts folder, a directory full of screen shots from a SharePoint server, and the local Public Documents folder where other network users can open and save files.

Libraries are an especially useful way to narrow searches to locations that contain related types of files. Other subtle improvements to the built-in search tools include shortcuts at the bottom of the search box where you can filter a search. And my favorite change of all: a button that toggles the preview pane with a single click.

If your number-one gripe about Vista’s Explorer was the absence of an Up button, you will be able to continue complaining. It shows no sign of making a reappearance, ever.

Next page: Another stab at simpler networking -->

<-- Continued from Page 2

Networking

The Network and Sharing Center that debuted in Windows Vista was Microsoft’s attempt to make network setup and configuration easier by consolidating everything into a single starting point. To call the critical reaction “mixed” is to be charitable. So the Windows 7 designers have revisited the original concept, with an eye to keeping the basic organization but streamlining it still further.

Gone are the long lists of settings under the Sharing and Discovery heading. They’ve been replaced with four links to common tasks. In addition, the previously cluttered task pane on the left now contains only two links, which offer one-click access to adapter settings and advanced sharing details.

win7dd_small_page_3.jpg
For a closer look at all the changes in Windows 7, see the image gallery that accompanies this post.
At least one major networking task has been yanked completely out of the Network and Sharing Center. The new interface for connecting to wireless networks borrows from the Mac OS X approach, with a tray icon that glows to indicate the presence of wireless networks. Clicking that icon in turn pops up a list of available networks, where you can connect using a security key, a device password, or a web-based interface (for public hotspots and the like).

The other major change in networking is an innovation called the homegroup, which allows you to set up password-protecting sharing on a home network without having to hassle with user accounts. The details involve a hidden user account and a HomeUsers security group, all managed via a simple console. It will be interesting to see whether this latest incarnation in the keep-it-simple school of networking succeeds with its target audience of non-techies.

Next page: Improved performance monitors -->

<-- Continued from Page 3

Performance

One of my favorite Windows Vista additions is Resource Monitor, a slick utility that was the centerpiece of my ”Top troubleshooting tools” feature earlier this year.

In Windows 7, Resource Monitor is at least an order of magnitude more valuable. It still offers an overview of performance with real-time measurements of CPU, memory, disk, and network usage. But those displays are now customizable, and you can drill down into any resource area to find a wealth of detail about how well your system is performing.

win7dd_small_page_4.jpg
For a closer look at all the changes in Windows 7, see the image gallery that accompanies this post.
Using the Windows 7 Resource Monitor, you can get a quick summary of memory usage and see details about RAM usage on a per-process basis, without having to flip between different displays. If you’re concerned about network traffic, you can click the network tab to see in-depth information about current network activity, complete with details about open connections and ports.

One annoying performance glitch in Windows Vista is its insistence on indexing new and changed files as soon as you start or resume from sleep. That leads to the perception that the OS is thrashing the disk and affecting overall performance. In this build of Windows 7, the indexer is more considerate, automatically pausing its operations for two full minutes after you resume from sleep. That gives other processes unrestricted access to CPU and disk resources, presumably making the system feel snappier at startup.

If you’ve been waiting for the scale on the Windows Experience Index to finally reflect the performance of new quad-core CPUs and high-end GPUs, you can stop waiting. The scale, which topped out at 5.9 in Vista, now goes to 7.9 (but not yet to 11).

And finally, in the “you asked for it” department, Disk Defragmenter now includes progress indicators that let you see at a glance how a defragmentation operation is going.

Next page: Troubleshooting tools -->

<-- Continued from Page 4

Troubleshooting and hardware

Some of the most subtle changes in Windows 7 are pure political correctness. Several dialog boxes that affect search settings, for example, used to warn that choosing a particular option “might be slow.” Now they use a more neutral phrase: “this might take several minutes.” Another popular Vista utility, the Reliability Monitor, also gets a redesign that de-emphasizes the 1-to-10 rating on the System Stability Index.

So, does that mean that Windows troubles are going to be swept under the rug by the language police? Not if the extensive collection of troubleshooters is any indication. In XP and Vista, troubleshooting gets plenty of attention in the Help and Support section. In Windows 7, Control Panel includes a lengthy collection of troubleshooters for most common hardware, software, and network-related problems

win7dd_small_page_5.jpg
For a closer look at all the changes in Windows 7, see the image gallery that accompanies this post.
If you’re worried that these troubleshooters are just the latest incarnation of wizards, join the crowd. In my limited testing so far, these troubleshooters seem to do their job with a minimum of fuss and in several cases go beyond the mere basics. The default setting is “just do it” mode, although you can use advanced options to see each setting in advance and view a report listing all changes made after completing the troubleshooter.

The most high-profile change for tracking down maintenance and troubleshooting issues is the new Windows Solution Center, which looks like the Vista-era Security Center but consolidates a slew of other functions into the panel, including access to backup functions, problem reports, and System Restore. The whole thing still feels overly busy and unfinished. In fact, a recent post on the Engineering Windows 7 blog suggests that this feature is about to undergo some radical changes, including a new name, Action Center. Regardless of the name, the real challenge is getting non-technical users to actually find the new control panel and then use it.

An impressive amount of design work has also gone into device support, starting with a new Devices and Printers dialog box that offers a simplified view of the devices you’re most likely to want to configure, including printers, cameras, scanners, and multi-function devices.

One feature I was especially happy to discover is an obscure setting under the Power Options dialog box. By toggling a switch here, you can disable “wake timers,” which are those annoying scheduled tasks and activities that wake your computer up when you’d just as soon it remain asleep.

  • Next page: A kinder, gentler UAC? --><-- Continued from Page 5

    Security, backup, and recovery

    You can talk all you want about security features in Windows 7, but at the first break in the conversation, the one question on everyone’s lips will be, “Have they fixed User Account Control?” Those annoying UAC prompts have been a source of consternation for Windows Vista users, who seem them as pointless nagging.

    In Windows 7, Microsoft has tweaked UAC enough that the annoyance factor will drop down to acceptable levels for most people. So what’s changed?

    win7dd_small_page_6.jpg
    For a closer look at all the changes in Windows 7, see the image gallery that accompanies this post.
    The options dialog box for the UAC feature now has four settings instead of just two. Those intermediate settings are the default for standard and administrative users in Windows 7.

    For starters, the Secure Desktop option, which dims the desktop and switches to a different security context when a UAC prompt appears, is off by default. In addition, a new setting allows any user with an Administrator account to run signed Windows binaries without having to click through a UAC consent dialog box.

    The flip side of security is backup and recovery. Vista introduced some much-improved backup solutions but earned brickbats for their implementation. In Windows 7, the entire backup experience is streamlined, to make it easier to set up automated backups and view their progress. In addition, three big backup complaints are finally addressed:

    • You can now include or exclude specific folders from file backups.
    • You can define any network location as a destination for an image-based backup, a la OS X’s Time Machine.
    • You can create a System Recovery disk from the Backup and Restore Center so that you don’t need to rummage around for your original installation media to restore a complete backup.

    The one outstanding question for Backup is whether Microsoft will make image-based backups available for home editions of Windows 7. Currently, that option is available only with the Business and Ultimate editions of Windows Vista. It would be a welcome change to see these features available to every Windows user.

  • Topics: Operating Systems, Data Management, Microsoft, Networking, Software, Windows

    Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

    Talkback

    162 comments
    Log in or register to join the discussion
    • Sad, but Snipping Tool is still the same

      In classic MS fashion, the snipping tool is not able to capture the borders of all aero themed windows neatly, for e.g. the Firefox "About" dialog box. Sadly this has not changed even in Windows 7 alpha. I hope they fix this.
      iravgupta
      • Works for me

        Try as I might I can't replicate what you describe. Firefox "About" dialog box appears identical on screen and in snipping tool image.

        OS: Vista x64
        Chipset: Intel 965GM+ICH8M
        Graphics: GMA 3100
        Screen res: 1600x1200

        Harry
        hjacobson
    • Not to look nasty

      but i learn close to nothing i didn't know about
      Windows 7 build 6801 from your article.
      Things that would interest me,but which are not in
      this article,are:
      *The minimum hardware on which Windows 7 build 6801
      run well
      *How Windows 7 build 6801 scale from netbook to Quadri
      Core CPU, in terms of load support and in terms of
      services shutdown or active
      *What impact in terms of security have the different
      levels of UAC,even though i don't plan to use anything
      other the most restrictive level.
      timiteh
      • Re: Not to look nasty

        It's pretty pointless asking for hardware requirements on pre-beta software.
        TV John
        • Perhaps

          However it is only to have an idea of how serious is
          about the reductions of the ressource requirements and
          the improvements of scalability of the new Windows.
          If the pre-beta Windows behaves quite well regarding
          these 2 aspects, it would be quite a good sign.
          If not than one could question how serious Microsoft
          is about those 2 aspects.
          timiteh
          • What I understand

            From what I understand, it'll have hardware specifications
            similar to that of Windows Vista but it will perform better on
            the same hardware from what I have heard. There are a
            number of 'under the hood' changes but it still won't
            convince me to buy it until they fix up the inconsistent mess
            that is the Windows UI and the poor quality of the bundled
            applications such as Internet Explorer, Mediaplayer etc. etc.
            Kaiwai
            • I agree ...

              ... I think that the overall spec will remain the same, but that the user experience on lower-spec hardware will be better. Certainly this is what I'm seeing so far.
              Adrian Kingsley-Hughes
            • Not sure about your point as...

              ...W7 will run better than Vista on lower powered hardware - and bear in mind 'low powered' in 2009 will effectively be a single core 1.6GHz Atom.

              As for the UI, that's an acquired taste as are the applications which can easily be replaced by the numerous third party alternatives available.
              Sleeper Service
            • Has nothing to do with that

              It has to do with consistency - and all the third party
              hackware in the world isn't going to change the fact that
              Microsoft has no HIG, they refuse to establish a set of
              standards for their internal development, each different
              application uses a different widget kit.

              Notepad uses a different widget kit to the calculator, the
              calculator uses a different set to another application. There
              is no consistency in either the look and feel or the HIG. It
              has all the refinement of an opensource desktop running
              applications which rely on various different widget kits and
              each doing its own thing when it comes to HIG rules.
              Kaiwai
            • someones discovered a new

              abbreviation
              mrjoctave@...
            • Eh?

              http://msdn.microsoft.com/en-us/library/aa511258.aspx
              Sleeper Service
      • If you'd read the first page

        you would have known that not only does the article NOT do performance testing, Ed considers in unethical/unprofessional to test for that on such an early build

        I for one am completely uninterested in performance tests at this point. When they get to the RC stage, it becomes semi-relevant. When it goes RTM, which is generally MONTHS before you and I can buy it, it becomes very important.

        Right now, benchmarks tell you very little. If it's faster, than Vista, it may be relevant, but there's several months to go and it could get slower.

        Obviously the converse is true as well.
        notsofast
        • Should i have formulated my post differently ?

          I did read the first page and i don't see why people
          has some troubles to clearly understand what i said in
          my post.
          I clearly said that i wish to know what is the minimum
          hardware on which Windows 7 build 6801,[b]note the
          mention of the specific version which is different to
          the mention of only Windows 7[/b],run well and how
          this version scales on different hardware from a
          netbook to a high end PC.
          My wish is to know what efforts Microsoft have already
          done in these domains up to version 6801.
          And i know that the performances of such an alpha
          build would probably give little indication for the
          performances of the RC or RTM build.
          Generally when i write an application,even the last
          pre beta build can have some significant difference
          compared to the final build i nterms of both
          performance and U.I.
          timiteh
          • I plan to cover in a follow-up post

            I have now installed this build on six different systems (soon to be seven), all at very different performance levels, and will report on the experience shortly.
            Ed Bott
            • Thanks Ed.

              I am seriously interested by how the current pre-beta
              Windows 7 behave on netbook.
              I don't think that there will be a significant
              difference performances wise between the build 6801
              and the first public beta release espected for the
              beginning of the next year (or hopefully for december
              of this year).
              Thus it would be interesting to know how well the
              current build behave on a netbook as i intend to try
              the beta release on my future Asus Eee PC 1000H.A test
              of the behavior of the current build could give some
              idea of what to expect on the Asus.
              timiteh
            • No netbook here yet, unfortunately

              I have several other hardware platforms to choose from but no netbooks at the moment, so i probably won't have that in my next post.
              Ed Bott
    • RE: A deep dive into Windows 7 (build 6801)

      Well, judging from all the reviews I have read, it seems undisputed that Windows 7 will have a considerably smaller footprint than Vista. Which seems to make Windows 7 a viable option even for Netbooks.

      Apart from that, TV John is right: is IS pointless to ask for hardware requirements for a pre-beta version.
      cgdams
    • Too early for a Deep Dive?

      As this is Alpha code, perhaps some of it will change with the first BETA and then again in the RC. Maybe it's too early to be saying, "This is what Windows 7 will be like."
      jpr75_z
      • What I have heard

        What I have heard is that the pre-beta is 'api complete' and
        what will happen in the beta will simply be the UI being given
        attention (and other parts that don't affect compatibility). I
        guess they've learned from Vista that you need to nail down
        the API so that developers have sufficient time to test their
        software against a stable target.
        Kaiwai
      • I disagree

        I think that M$ should at least let the community know what their goals are for hardware requirements of the various versions. If they are aiming to make Windows 7 available for netbooks, that might have an affect on people purchasing or waiting to purchase netbooks. The same with other computers. If you are purchasing a new computer and are dithering about what size RAM to go for then an idea of what Windows 7 would require could make the difference on what you choose. I am sure M$ has set goals for the developers to aim for. If they set goals that people will not put up with, then better to get it on the table now rather than later when you might run into the whole "Vista capable" mess again where it is flagged as being suitable for Vista but you find that it is only suitable if you will accept performance that is slower than Windows ME.

        The other point is that if M$ finds people are not going to accept the goals M$ has set then M$ might revisit those goals and make them more acceptable to the user community and also lower the requirements.
        rhomp2002@...