Windows 7 product editions

This content is 15 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Microsoft has announced the product line-up for Windows 7 and those who were looking for something a little simpler than the SKUs we saw for Windows Vista will be sadly disappointed. As with Vista there are several versions planned for Windows 7; however, unlike with Vista, each is a superset of the preceding version (i.e. the features in each version of Windows 7 build upon the one before it so that, as customers move up as version, they gain additional features and lose none).

Microsoft’s recommendations are:

  • For price-sensitive customers with small notebook PCs (e.g. netbooks), some OEMs will offer Windows 7 Starter Edition.
  • For customers in emerging markets, Windows 7 Home Basic will be available.
  • For consumers, Microsoft recommends Windows 7 Home Premium for most customers and Windows 7 Professional for customers who want additional features and functionality useful for small business activities. There will also be an Ultimate Edition of Windows 7.
  • For businesses, Microsoft recommends Windows 7 Professional for most customers and Windows 7 Enterprise for medium-to-large business and enterprise customers that choose to license Windows through Software Assurance.

Whilst I can see why this approach has been taken and I think that making each version build upon the previous one is a a sensible decision, in my opinion this is still too many versions (why do we need Ultimate or Enterprise – surely those features can be rolled into Home Premium and Professional as Microsoft has stated that it intends to focus on these as the primary editions of Windows 7?). Interestingly there is no mention of a version of Windows 7 labled N, K or KN as there was for previous versions of Windows in order to comply with legal rulings in Europe and Korea. The announcement also makes no mention of the differences between 32- and 64-bit editions amd whilst I expect to see x64 versions of the high-end SKUs, I’ll be surprised if the low-end versions are available for anything other than a 32-bit architecture.

In terms of available functionality, the line-up is as follows:

Version Key features
Windows 7 Starter Edition
  • Broad application and device compatibility with up to 3 concurrent applications.
  • Safe, reliable, and supported.
  • Ability to join a Home Group.
  • Improved taskbar and JumpLists.
Windows 7 Home Basic Edition Windows 7 Starter Edition features plus:

  • Unlimited applications.
  • Live Thumbnail Previews & enhanced visual experience.
  • Advanced networking support (ad-hoc wireless networks and internet connection sharing).
  • Mobility Center.

Windows 7 Home Basic Edition will only be available in emerging markets.

Windows 7 Home Premium Edition Windows 7 Home Basic Edition features plus:

  • Aero glass and advanced windows navigation.
  • Easy networking & sharing across all PCs and devices.
  • Improved media format support, enhancements to Windows Media Center and media streaming, including Play To.
  • Multi-touch and improved handwriting recognition.
Windows 7 Professional Edition Windows 7 Home Premium Edition features plus:

  • Ability to join a managed network (domain join).
  • Protect data with advanced network backup and encrypting file system.
  • Print to the right printer at home or work with location aware printing.
Windows 7 Enterprise and Ultimate Editions Windows 7 Professional Edition features plus:

  • BitLocker data protection for internal and external drives.
  • DirectAccess for seamless connectivity to the corporate network (requires Windows Server 2008 R2).
  • Prevent unauthorised software from running with AppLocker.

Windows 7 Enterprise Edition will only be available through Microsoft Volume Licensing.

Windows 7 Ultimate Edition will include multi-language packs.

Did SpinRite actually save my data?

This content is 15 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

This morning, I shut down the notebook PC that I use for work and set off to meet a colleague. Upon returning, I tried to boot the system but nothing happened. Technically, something happened – but not what I expected – basically Windows would not boot and sometimes it reached the startup screen, sometimes it didn’t. Once or twice I’m sure I saw the once-familiar blue screen of death flash up for a fraction of a second before the PC reset itself. I tried a normal startup as well as last known good configuration, before finally I gave up and tried to recover the system using the Windows Server 2008 DVD but this couldn’t locate an installed copy of Windows to recover. What it would let me do though was get to a command prompt, where attempting to access drive C: returned:

The request could not be performed because of an I/O device error.

That didn’t sound good but I managed to run diskpart.exe and list disk told me that disk 0 was online. Moving on to try list partition told me that the two partitions I expected to see were there but it was list volume that really helped shine a light on the problem – the DVD drive and WinRE volumes showed as healthy but drive C: was reported as being a 110GB Healthy partition of type raw (i.e. not NTFS). At this point, I began to panic. Something had happened to the NTFS and that could mean lost data. I have a reasonably recent backup but the last couple of weeks at work have been mayhem and there was some stuff that I know I don’t have a second copy of.

I could call my company’s IT support number but it normally takes at least a day for a callback; I’d have to take the laptop to a “local” office (a 100 mile round trip); if a system won’t boot, the standard approach is to spend a very limited amount of time trying to fix it (probably none at all for people like me who run a non-standard operating system) before simply wiping the system and installing a new corporate build. That means going back to Windows XP and Office 2003 (which is painful when you are used to Windows Vista/Server 2008/7 and Office 2007), the loss of an activated copy of Windows Server 2008 Enterprise Edition (which is not exactly inexpensive) and also losing my data (the standard build has separate system and data partitions and my build does not… although now I’m starting to reconsider that choice).

I’m pretty sure that the root of this problem is a failing hard disk (after all, it is a “Western Dodgital“) but, without the tools to prove it, I’ve got a snowball’s chance in hell of getting a new one) and, to cut a long story short, when it comes to supporting my non-standard build, I’m on my own (at least unless I can prove that the hardware is faulty).

One of the podcasts that I listen to is “Security Now” and the hosts (Steve Gibson and Leo Laporte) spend far to much time plugging Steve’s SpinRite product. I’ve often wondered if it was any good but was not prepared to spend $89 for speculative purposes – this afternoon I decided that it was time to give it a try.

After paying up, downloading the software, extracting the ISO and creating a bootable CD, I ran SpinRite and performed what is referred to as a “level 2” scan. For the first 20 minutes, SpinRite ran through my disk finding nothing untoward but at the 50% mark it switched into “DynaStat” mode and started trying to identify lost data on one particular sector, slowly narrowing down the unrecoverable bits of the sector. Just this one sector took almost 5 hours and around 2000 samples but all of a sudden SpinRite took off again and finished up the rest of the drive in another 20 minutes. Even though the sector was marked as unrecoverable, a technical support conversation by e-mail confirms that this relates to the data, not the sector. With some trepidation, I restarted the computer, waited with baited breath and have never been so glad to see Windows start checking its disk(s). After a short while, chkdsk was complete and I was presented with a logon screen.

There’s nothing in the Windows event logs to indicate why my system failed to boot so many times this afternoon so it’s difficult to say what the problem was and whether it really was SpinRite that fixed it (although SpinRite did report the SMART data for the drive and there were a number of seek errors, backing up my theory that the hard disk is on its way out). What’s important though is that, as I write this post, Windows Server 2008 is 63% of its way through a backup and all seems to be well. I’m not quite ready to wholeheartedly endorse SpinRite – it does almost sound too good to be true – but, on the face of it, it seems to have recovered enough data on my disk to let Windows boot and for me to gain access to my system. That’s worth my $89 – although somehow I don’t see me getting that particular item through on my expenses…

Mounting ISO images in Windows 7

This content is 15 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

The Windows 7 beta includes the ability to burn CDs/DVDs from ISO images but it doesn’t seem to be able to mount them as volumes. As this beta is supposed to be feature complete, I don’t think it’s very likely that we’ll see this functionality added in future builds (even though rival operating systems can already do it…) but there are some third party alternatives available.

Last week, I (finally) got around to upgrading my netbook from Windows 7 milestone 3 (build 6801) to the beta (build 7000) and, as I didn’t have access to a DVD drive, I used Slysoft Virtual CloneDrive to mount the ISO as a drive, after which I could select the Windows 7 setup.exe from the autorun menu. It did exactly what I needed it to and that, rather lengthy, upgrade process didn’t seem to hiccup at all. From a quick trawl of the ‘net, there is at least one alternative out there (which I haven’t tried) – PowerISO – although this is a chargeable product and Virtual CloneDrive is freeware.

I got burned by [Google] FeedBurner

This content is 15 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

On Friday night I wrote a post which optimistically suggested that I’d successfully migrated this site’s RSS feeds from FeedBurner to the new Google FeedBurner platform. Unfortunately many people won’t have seen that post (at least not until after I spent a good chunk of my weekend enlisting the support of known subscribers to try and work out why the primary URL given out for this site’s RSS feed wasn’t working: Thanks go to Bill Minton, Alistair Doran, Garry Martin and Aaron Parker) – it all turned out to be because FeedBurner’s instructions for users of their MyBrand service have a vital step missing…

I’ve made the point before that free online services are not necessarily an ideal solution but nevertheless, many of us rely on them and hopefully my experiences will help out others who are going through the (soon to be forced) migration from the (old) FeedBurner platform to (new) Google FeedBurner.

If it ain’t broke, why fix it?

Some time ago, Google bought FeedBurner. That’s not all bad – I’m sure the guys who started FeedBurner were pretty stoked, and for us customers (who, after all, were largely using free services), things got better as premium services like MyBrand (more on that in a moment) were made free.

It was inevitable that at some point the service would be absorbed into Google’s infrastructure and if I hadn’t moved voluntarily in my own timescales (i.e. over a period when I was off work and potentially had some time to deal with any resulting issues), account migration would have been forced upon me at the end of this month.

What’s all the fuss about?

I may not have the largest blog in the world but I’ve worked hard for several years to get this blog to where it is now. With that in mind, I approached this migration with some trepedation but the Transferring FeedBurner Accounts to Google Accounts FAQ made it all sound pretty straightforward, including this text:

“Will I lose all my subscribers in this process?
You should not lose any readers of your feed during this transition process. All URLs will redirect your readers to feeds hosted by Google.


I use MyBrand, the service that allows me to map a domain I own to my feed. Do I need to change anything?
Yes. After transferring your account, you will be sent an email with instructions on how to change MyBrand. You can also get these instructions on the MyAccount page after the transfer.

You will be required to change your DNS CNAME to the Google hosted domain service, the same service that handles custom domains for Google applications like Blogger and Google Apps for Your Domain.

Please note that the CNAME will no longer be the same domain as the domain that serves feeds, but the service level and functionality will be identical.”

That all sounded straightfoward enough, so I followed the migration steps on FeedBurner’s website until I saw a message that indicated successful completion. The follow-up e-mail included this text:

“Important! If you use MyBrand, FeedBurner’s custom-domain service, you need to make a very important change to ensure your feeds remain available to subscribers using your custom domain(s).

To make this change in your Google account, follow the instructions listed in your account’s new MyBrand page:”

I followed the instructions (i.e. made the changes to my DNS zone) but, 48 hours later (and after confirming that the name was resolving correctly) I was still receiving HTTP 404 (Not Found) errors when I used the URL (i.e. the one that uses the FeedBurner MyBrand service to redirect subscribers to the real location.

The missing step

Double-checking my account settings and the DNS record I had edited, I decided to deactivate the MyBrand service and reactivate it. Some time later (I’m not sure exactly how long afterwards, but not long) the 404s were gone and I was able to check with some of my subscribers that their feeds were updated with posts from after the migration. Whilst I waited for this confirmation, another FeedBurner user confirmed that this had worked for him too but it would be good if the instructions included this step…

Why is this Google’s problem?

To be fair to FeedBurner/Google, buried in a post on the FeedBurner Status Blog is this text:

“4-DEC 2008: Have you recently moved your feeds to a Google account? Seeing a ‘404’ error when trying to view your feeds, and you use our MyBrand service? Try the following workaround to fix the problem:

  1. Sign in to
  2. Visit My Account > MyBrand.
  3. Click the remove link next to your current MyBrand domain(s), and then click Save.
  4. Re-enter the domain(s) you removed in the previous step and then click Save.
  5. Try to view the feed(s) that were showing 404 errors before. They should now display your content.”

It should be noted though that these instructions don’t work (there is no remove option in the new interface)… and there is nothing more recent in the blog about this.

Meanwhile, the MyBrand page in the FeedBurner account settings is typically Googlite in its tone, basically telling us that we’re welcome to use the service but if it breaks we’re on our own.

FeedBurner provides no technical support for MyBrand; you must configure DNS settings correctly with your domain/web hosting provider’s help. More technical detail and discussion of the requirements for using this service are available in this Help topic.

It can take up to 24 hours for a new CNAME entry to take effect. If your new feed address isn’t working, have a nice day and check back tomorrow.”

Thanks a bunch Google. My DNS is fine… but your migration process is broken and it seems that you don’t provide any method to report the problem.

Several other people have written about this problem (including one particularly useful post on the whole migration process) so it’s certainly not an isolated case but Google responses are nowhere to be seen on this two-week old post on the FeedBurner Help Group (providing a service without formal support is one thing but monitoring your own help forums is a basic courtesy).


Ironically, the FeedBurner MyBrand service (which let’s me host a FeedBurner Feed under my domain name) that caused this a problem but, because I use this service, many of the subscribers to this blog are using a URL that is under one of my domains (so, ultimately, under my control). This problem may have cost me a good chunk of my weekend but at least I got it fixed and if I hadn’t been able to work out what was happening then I would have reverted to serving the feed directly from WordPress (with the consequential hit on bandwidth and loss of analytics). Imagine if I had a popular blog with a large number of subscribers that wasn’t hosted on my own domain name and the service went belly-up…