Skip to main content

Windows 7 – Looks good so far

I bit the bullet and installed the new beta. Here’s my first day impressions, written using Live Writer on Windows 7.

It’s an easy install. After freeing up and formatting a 20GB partition, I downloaded a 2.5GB ISO, burned it, mounted it and ran setup. A handful of questions and a couple reboots and it was up and running. It was fast, easy and painless compared to the typical new computer first time setup.

No crapware needed. I have a functional computer with no add-on or third party drivers. I gave up on Linux as a desktop years ago simply because of the hassle of managing hardware compatibility, and my experience with Vista indicates that removing non-essential vendor provided crud helps performance and memory utilization. Win 7’s initial impression is that a GB of memory will be adequate provided that I don’t have to load up with 3rd party drivers and utilities, and so far I don’t, so I should be OK with 1GB of RAM.

It’s fast. I dual boot Vista on this computer (a cheap 1.6Ghz T2060 dual core notebook with 1GB RAM) and there is no comparison between the two. Either it’s faster or it’s got me fooled into thinking it’s faster. Either way, Win 7 wins. Vista on the same hardware is like a two year old on the potty. A simple thing, like opening a Vista control panel app, seems like it’s a big production, with lots of effort and whining. “I donwaannaaa poop” “You can do it, just try it” “I caaann’t poooop” “Sure you can, squeeze harder” “waaaa……I caaann’t”. Eventually a turd the size of a dime comes out. “Yea! Good Job"!”. And the Vista control panel app finally opens. You feel like you need to thank it & give it a cookie for being so good.

Bluetooth A2DP works, but I haven’t been able to pair with my phone. Tethering is a must-have, and ideally I wouldn’t have to add a 3rd party BT stack to get it.

The user interface is cleaned up. It’s still got some non-intuitiveness in places, but it’s a step up from Vista. I’ve gotten a lot farther with this UI in the first day than I did with either Vista or OSx. I’m used to Vista, so it’s an easy transfer, but some of it is because it’s more intuitive.

The Resource Monitor is a step up from Vista and now includes netstat equivalent functionality, including TCP socket & ports per process.


It’s got a nifty and simple memory usage graph. You can see that after a fresh install, I’ve got about half a gig used.


The Resource Monitor also includes a process explorer that shows open files handles and DLL’s.


Microsoft finally is providing what I think is the minimal functionality for that type of tool. Mapping a process to file handles and network sockets is essential for troubleshooting.

And – check this out - it’s got a real shell:


(OK – I had to add the Unix subsystem to get it, but it’s there and it works)

So far – it’s a win.


  1. Thanks for posting a review, Michael. I've been wondering what I'd do with my desktops after XP became unobtainable. From the repots I've read, 7 seems like a viable alternative.

    Keep us updated as you notice things. I'm looking forward to checking it out.

  2. Maybe it's just because I've got a 3yr old and the memories are fresh. In any case, I'll never think about performance the same again! ;)


Post a Comment

Popular posts from this blog

Cargo Cult System Administration

“imitate the superficial exterior of a process or system without having any understanding of the underlying substance” --Wikipedia During and after WWII, some native south pacific islanders erroneously associated the presence of war related technology with the delivery of highly desirable cargo. When the war ended and the cargo stopped showing up, they built crude facsimiles of runways, control towers, and airplanes in the belief that the presence of war technology caused the delivery of desirable cargo. From our point of view, it looks pretty amusing to see people build fake airplanes, runways and control towers  and wait for cargo to fall from the sky.The question is, how amusing are we?We have cargo cult science[1], cargo cult management[2], cargo cult programming[3], how about cargo cult system management?Here’s some common system administration failures that might be ‘cargo cult’:Failing to understand the difference between necessary and sufficient. A daily backup is necessary, b…

Ad-Hoc Versus Structured System Management

Structured system management is a concept that covers the fundamentals of building, securing, deploying, monitoring, logging, alerting, and documenting networks, servers and applications. Structured system management implies that you have those fundamentals in place, you execute them consistently, and you know all cases where you are inconsistent. The converse of structured system management is what I call ad hoc system management, where every system has it own plan, undocumented and inconsistent, and you don't know how inconsistent they are, because you've never looked.

In previous posts (here and here) I implied that structured system management was an integral part of improving system availability. Having inherited several platforms that had, at best, ad hoc system management, and having moved the platforms to something resembling structured system management, I've concluded that implementing basic structure around system management will be the best and fastest path to…

The Cloud – Provider Failure Modes

In The Cloud - Outsourcing Moved up the Stack[1] I compared the outsourcing that we do routinely (wide area networks) with the outsourcing of the higher layers of the application stack (processor, memory, storage). Conceptually they are similar:
In both cases you’ve entrusted your bits to someone else, you’ve shared physical and logical resources with others, you’ve disassociated physical devices (circuits or servers) from logical devices (virtual circuits, virtual severs), and in exchange for what is hopefully better, faster, cheaper service, you give up visibility, manageability and control to a provider. There are differences though. In the case of networking, your cloud provider is only entrusted with your bits for the time it takes for those bits to cross the providers network, and the loss of a few bits is not catastrophic. For providers of higher layer services, the bits are entrusted to the provider for the life of the bits, and the loss of a few bits is a major problem. The…