Our Impressions

Immediately upon trying to install Vista, it's obvious Microsoft has been making some long-awaited changes for the installation procedure. The last of the console view for the installer is gone, and it has been replaced by an entirely graphical process. This includes the recovery console, and while it's still not a walk in the park, it isn't so intimidating any more. More importantly though, Vista is now USB-aware, so the days of the floppy disk are now truly limited, as drivers can be loaded off of USB devices such as flash drives. We can't state enough just how happy this makes us. The installation procedure is otherwise nearly the same as XP: it asks a few fewer questions, and doesn't spend the entire time boasting about its features (though that may change at release), so installation overall is not exceedingly different from XP.

Microsoft has also included a basic memory testing utility as both a recovery and advanced startup option. This can either be taken in a positive light or negative light, depending on whether you're happy that you may no longer need external utilities like MemTest86, or troubled that bad memory is now so common that Microsoft is bothering to include a memory testing utility. The utility seems sound enough; on the surface it seems a workable replacement for MemTest86, but as we don't have any bad DIMMs at the moment to test with it, an actual capability test will need to wait. At least until we break something.

Once installed, our fresh copy of Vista Ultimate Edition x86 ate up 10GB of hard drive space, and in the out-of-the-box configuration was using approximately 512MB of RAM. Running Vista x64 while trying to get real work done can push memory usage up to the capacity of physical memory in configurations we tested (though we never tested with more than 2GB). The actual RAM usage should drop a good deal once Vista is in shipping condition, as many debugging features are still in the code for this beta of Vista. XP 64-bit edition was eating a similar amount of memory when it was in beta, and dropped by over 100MB for its final release, so we'd expect something similar with Vista.

In order to get a good feel for Vista for writing this, we "dogfooded" (Microsoft's new term for beta testing) this for a week, and our reactions are overall mixed. As we previously mentioned, some of the UI changes that have replaced the traditional menus are just very hard to get used to. It's not so much that these changes represent a significant shift in how Windows operates, but rather it's that a lot of things have been moved, combined into buttons, etc. For most of these layout changes, there's little that directly improves Windows or its productivity for most users; people will adapt over time, and these changes essentially make more or less sense depending on how much you like the current XP interface.

We've managed to adapt to these changes for the most part, but it's the kind of paradigm shift not everyone will be ready for, and since the old menu structure is still available that's okay. At the end of the day most users will end up using Windows Vista the exact same way they ended up using XP. The real productivity features powered by Aero potentially have the most impact for changing how users work, such as giving up Alt+Tabbing for Flip3D, but as we mentioned earlier that's not going to happen with the current incarnation of Flip3D: it's not effective enough to replace Alt+Tabbing, let alone the improved Alt+Tabbing of Vista.

To Microsoft's credit, there were to places where we did end up changing our habits a bit thanks to Vista. The first is with the inclusion of a much smarter searching system that can use the search index to instantly pull up results and mix in partial results (very similar to Tiger's Spotlight feature), searching isn't nearly as painful as it is with XP. Given the current implementation of this quick search and indexing service however, there's still some work to be done. By default only the start menu and a user's home directory are indexed, so searching from anywhere else loses the instant results and becomes a normal search. It's also flat-out buggy at this point; quick searching from our home folder for a specific image didn't work, but it did inside of the pictures folder of our home folder.

IE7+ has also picked up a major overhaul, both in terms of new features (sandbox mode, anti-phishing filters, etc.) and its interface. The main thing here is that IE finally has tabbed browsing, and in fact this is one of the few things at this point that really shines compared to Safari/Firefox. For IE's tabs, a new view has been added to help manage tabs by showing a scaled down version of all open tabs at once, effectively creating an Exposé for tabs. It's hard to put in words, but it's similar to looking at a folder full of pictures using the thumbnail view. This is a very useful feature that we're glad to see in IE and it undoubtedly makes it easier to use than any other tabbed browser.

The implementation of Gadgets (aka widgets) also gets a nod, even though Microsoft is very late to this particular party. If you're looking for something innovative in the field of widgets here, you're going to be disappointed, but there's little to be said about these kinds of utilities that hasn't already been said. Users accustomed to Tiger's widgets will be happy to know that these widgets are active all the time and do not have the refresh delay that Tiger's do, at the cost of memory and CPU usage.

Performance Improvements More Impressions and Test Setup
Comments Locked

75 Comments

View All Comments

  • rqle - Friday, June 16, 2006 - link

    dont really need bad memory module, overclock the memory just a tad bit to give errors while keeping the cpu clock constant or known stable clock.
  • JarredWalton - Friday, June 16, 2006 - link

    That still only works if the memory fails. Plenty of DIMMs can handle moderate overclocks. Anyway, it's not a huge deal I don't think - something that can sometimes prove useful if you're experiencing instabilities and think the RAM is the cause, but even then I've had DIMMs fail MemTest86 when it turned out the be a motherboard issue... or simply bad timings in the BIOS.
  • PrinceGaz - Saturday, June 17, 2006 - link

    Erm, no. Just overclock and/or use tighter-timings on a known good module beyond the point at which it is 100% stable. It might still seem okay in general usage but Memtest86 will spot problems with it. Now see if Vista's memory tester also spots problems with it. Pretty straightforward to test.
  • xFlankerx - Friday, June 16, 2006 - link

    I love how I was browsing the website, and I just refresh the page, and there's a brand new article there...simply amazing.
  • xFlankerx - Friday, June 16, 2006 - link

    Masterful piece of work though. Excellent Job.

Log in

Don't have an account? Sign up now