Take a look at my recent Reliability Monitor output on my primary production machine. Last year, this thing kept giving me fits until I finally got all the hardware squared away. But what you see here is entirely typical of my experience with this X38-DQ6/QX9650/4GB DDR3-1600 machine for the past six months and more.
The only gotchas I’m currently experiencing occur once a week or so (or twice in quick succession over two-plus weeks, as the previous graph shows). The offending application is Internet Explorer 8, but it only blows up when I meet the following criteria:
- I have multiple tabs open in a single window and/or multiple windows open as well
- I am running Flash in one or more of those windows
- I leave the browser open for some indeterminate amount of time (more than half a hour, less than a day)
- I try to close one or more browser tabs and/or windows
When I do this, the results are annoying rather than catastrophic: IE goes away for a while with a (Not Responding) status in the title bar, but eventually comes back. Somewhere along the way one or more of the tabs or Windows where Flash is running crash, and the runtime shuts them down without affecting my desktop or stability in any other way.
Nevertheless, I have to take a hickey in Reliability Monitor each and every time this happens. Each time it occurs, it costs my reliability index between 1.3 and 1.5 points (when this happened on my machine on 8/20/2010, for example, my index dropped from 9.99 to 8.40; then when it happened again on 8/21/2010, it dropped from 8.56 to 7.22). If I turn Flash off, this problem doesn’t occur. But when I turn Flash off, there’s invariably stuff I can’t see or interact with online to which I need access to do my job. So I have to turn Flash on, and take the occasional hickey when it shows up. I just wish there was a way I could charge Adobe for the loss of reliability on my system that their software is apparently causing.
Anybody got any good suggestions for dealing with this stuff? Yeah, sure, I can work (or maybe I should say “limp”) around it, but that ends up not doing me that much good, either. Is this what they call a “necessary evil?”
In typical fashion, Windows wizard Paul Thurrott once again strikes gold in a recent story from his SuperSite for Windows. Entitled “Use Wireless Hosted Networking to Share an Internet Connection Wirelessly” he explains how to set up and use Internet Connection Sharing in Windows 7 to create a virtual Wi-Fi network on an Internet-connected PC that can be shared with other devices fairly easily. The story explains the steps involved in sharing a Wi-Fi connection through the Network and Sharing center, followed by a sequence of wireless network shell (netsh wlan ...) commands to set up and start a wireless hosted network on the PC with the primary connection.
Even better, he goes on to describe a free utility called Connectify that automates this entire process with its own custom GUI (the command line is all well and good but it’s always easier and less prone to error with a GUI based utility), There is a catch, though, and Connectify can help with that too: this technique does not work with all Wi-Fi interfaces and, in fact, is more likely to work with newer than with older ones (for example my new HP dv6 with its Intel 6200 Centrino interface works fine, but my older Dell D620 with its Intel 3945 ABG does not). Be sure to check out Connectify’s list of compatible/incompatible devices before starting down this road with any particular notebook. It can (and will) save you the effort of trying when the concluded process won’t produce the desired results — namely, a shareable wireless network.
Check out the story, though: it’s definitely worth a read. Road warriors who want to share a Wi-Fi connection with a smartphone or other devices will find it pretty helpful, unless they’ve already purchased a compact, portable Wi-Fi gateway, or their notebook doesn’t sport a compatible Wi-Fi interface.
On August 16, I blogged about a Windows 7 virtual machine technology called ZInstall that lets its users turn an existing Windows XP installation into a virtual machine that runs quite nicely after a target machine gets a clean install of the new OS (remember, you can’t use the “upgrade” option to go directly from Windows XP to Windows 7 using tools from Microsoft). This time out, I’d like to discuss another technology from the makers of Zinstall: it’s called zPOD and it extends Zinstall’s capabilities by permitting users to set up portable virtual machines on removable USB or eSATA drives (the bigger and faster, the better, for capacity and performance reasons, respectively).
I also went to the Zinstall folks with an out-of-the-way request to take the VM created for my small, underpowered Asus Eee 1000HE netbook PC, and let me install it on one of my quad core test machines, so I could see how it might behave in a more salubrious runtime environment. It turns out zPOD was the key to building such a portable VM, and that some pretty serious runtime environment and SID hacking was required to set up a version of the VM from the original Windows.old file on the Asus so it could run from a standalone hard disk environment.
It took a senior tech support staffer by the name of John B., who put the proprietary Zinstall python based installation and management environment through a pretty extreme workout, about two hours to grant my request to build me a standalone version of my old Asus machine running XP so that it would run on another computer. The install work took place on my primary test machine: a PC with an Asus LGA 776 P53 Pro motherboard, an Intel Q9450 processor, and 8 GB of DDR3-1333 RAM. It showed me that the XP VM would indeed work fine on another computer running zPOD, provided that all the SID related login matters were patched along the way.
The XP VM image now resides on a 160 GB Seagate portable 2.5″ drive that’s attached to my wife’s mini-ITX PC with 4 GB of DDR2-800 RAM and a T2350 mobile processor in an MSI industrial motherboard with built-in Intel G35 graphics. That’s not a huge step up from the original Atom N270 with 2 GB of DDR-667 RAM on which the image originally ran, but two real cores, double the memory, and a faster hard disk make the environment tolerably fast and capable. All that’s necessary to use this environment, once installed, is to run a progam named
to launch the runtime environment. On my quad-core system, launch took about 30 seconds; on the T2350 system, it takes nearly a minute, and the zPOD environment consumes just over 2 GB of RAM on the host machine, of which it makes 1,350 MB available (along with a single processor core) to the virtual machine running Windows XP. It’s not going to set any speed records, but it runs reasonably well–appreciably faster, in fact, than the original host environment ran on the Atom N270 processor in its original home without any virtual machine activity in play at all.
zPOD is another $90 product from Zinstall (and volume purchase discounts are available to organizations that might desire them). It’s a great way to retain access to still-working Windows XP environments, and the applications they can deliver, even after migrating to Windows 7. And you can even run the old XP environments virtually on machines other than their original hosts, given the right help from the vendor!
Shameless self-promotion note: Please check out my latest story for Dell’s ITExpertVoice site, which posted publicly last Friday. It’s entitled: “Why Buy Real KVMs, When Virtual KVMs Will Do?” (and lest you think I advocate wholesale abandonment of physical KVMs, this story not only explains how remote access technologies can supplement and to a certain extent supplant KVMs, but also when real, physical KVMs are still necessary to obtain access to key servers and other devices).
According to a story published on SoftPedia on August 16, 2010, Windows 7 has doubled down on Vista, and now owns 17.39% of the desktop operating system marketshare. At the same time, Vista’s share has fallen to 10.78%. By my reckoning that means that the ratio between Windows 7 and Vista is more like 100 copies of the former for every 62 copies of the latter (in round numbers, the actual ratio is 100:61.98) which isn’t as close to 2-to-1 as the headline might lead one to expect.
Nevertheless, it’s another pretty major confirmation of the doomed status of Windows Vista, and yet another affirmation that Windows 7 continues to come on strong, strong, strong. This is not only confirmed by MIcrosoft’s market tracking in-house (which indicated that Windows 7 surpassed Vista in June, 2010) but also by independent company Internet Metrics which reported that Windows 7 is the second most-heavily-used desktop OS as of July, 2010.
Now, if the numbers for enterprise adoptions come in the way Microsoft says (and probably also fervently hopes) they will, indeed there should be over 300 million copies of Windows 7 in circulation by the end of 2010. Zounds!
In a recent ZDNet blog entitled “It’s official: Windows 7 is a hit, and XP is finally in decline” Windowsmeister extraordinaire Ed Bott shares some interesting insights, and one very slick chart, as he explains the analysis that led him to the title for his piece.
The “visitors” in the title for the chart indicates that Bott analyzed the OS that visitors to the ZDnet Website were running, and that these visits provided the data upon which the charts are based. What I find interesting here is that Vista and XP are both in decline over the entire period of record, and that Vista stays consistently below XP by 15 to 20 percent or so. Talk about visual proof that Vista never lived up to its hype: there it is, burnt orange (XP) and maroon red (Vista).
The other interesting item is that the lines for XP and Windows 7 reached the crossover point between April and August of 2010. While this doesn’t reflect the facts as we know them in enterprise organizations, where 70-75 percent of all machines still run XP, it does indicate that for a broader cross-section of the Internet roughly as many people are running Windows 7 as are running XP, if not slightly more. And as time goes by that balance will continue to shift. Should be interesting to watch!
Thanks for another great and useful piece of reporting, Ed. It certainly gives us all lots of interesting points to chew on. Makes me think that by now having (finally) upgraded all of my PCs to Windows 7 (all 10 of ‘em), I may not be as far out on the lunatic fringe as I thought!
I’m writing up a capsule review of a software product called Zinstall, which (among other things) can take the Windows.old files from a machine upgraded from Windows XP to Windows 7 and turn that information into a fully-functional Windows XP SP3 VM with all of the applications and appurtenances ready to run within the host Windows 7 runtime environment. To help prepare my Asus 1000HE netbook for that upgrade, I attempted to delete one and expans another partition on its Seagate Momentus 5400 RPM drive, one of which was home to Windows XP as installed at the factory, the other to a now-expired beta version of Windows 7 Ultimate Edition (Build 7100).
Because I planned to upgrade the XP partition to Windows 7 anyway, and the beta Windows 7 partition wasn’t working any more, I decided to delete the Windows 7 partition I’d created , and merge it back into the original XP partition. I decided that a doubled-up Windows 7/XP runtime might appreciate having the whole drive to work with, so I popped that drive out of the Asus, plugged it into a SATA drive caddy I keep around just to work on drives for such purposes, and fired off Paragon Partition Manager on my primary production PC.
I went into the Advanced partition menu and instructed the software to delete what showed up as the O: partition (the now-defunct Windows 7 partition on the Asus drive), and gave the software permission to reboot the PC into its own runtime to do its thing. Alas, what resulted from this set of instructions was the deletion of the primary system partition for the host computer, rather than the target partition I was sure I’d selected on the 2.5″ notebook drive in my eSATA drive caddy. Dang!
That created the following problem for me: How to restore the image of the C: drive that I’d captured the preceding Friday (part of my normal backup routine). I used a Windows 7 install DVD I’d burned from and MSDN image download to try to run the image restore utility, but encountered a couple of interesting and time-consuming “ignorance problems” along the way. First, I discovered that the Windows 7 Repair Environment (aka WinRE) doesn’t recognize system image files stored on an eSATA drive. Alas, my drive K: (named ExtBackup) is where I keep those files, but I figured out when the Restore utility didn’t present that drive in its selection menu that it couldn’t see it, either. The solution was obvious: copy the image from the external eSATA K: drive to my internal plain SATA D: (Data) drive.
I could have taken my machine apart, pulled the D: drive and gone to another PC and handled the transfer from the K: to D: drive that way. Instead, I elected to install Windows 7 on the PC I was trying to repair, just so I could effect that transfer and perform the install. That’s when I hit my second knowledge gap: I couldn’t get Windows 7 to install on the now-wiped-clean original system drive. I popped it out and reformatted it, reset the partition to Active, and tried again: still no dice. A bit of Internet spelunking helped me understand that I had to re-set the hard drive priority order in the motherboard BIOS to select the target as first in the boot sequence. After that, Windows 7 happily let me target the drive for installation, and even set up a 100 MB repair partition in addition to picking the rest of the drive as the system, boot, and paging file partition.
After that, I was indeed able to run the image restore utility from Windows 7 and put my primary desktop back into action. It still took another hour and a half or so to reapply the updates that I’d first applied last Patch Tuesday, and then to fix all of the security issues (patches to apply, or end of life software to replace) that Secunia PSI found in my application collection. Then, aside from losing a couple of software items I’d purchased and a week’s worth of email I was back to where I’d started. And it only took me 12 hours to get back to where I’d started. Yikes!
Sigh. Now if only I could figure out how in the heck the instructions to delete the old Windows 7 beta partition on my netbook drive in the drive caddy got turned into a command to delete the primary system partition on the host machine… One thing’s for sure: the next time Partition Manager tells me it needs to reboot and take exclusive possession of the C: drive, I’m going to refuse that permission unless I’m really and truly working on that partition and no other. If I have to, I’ll find a different utility that will let me work on other partitions with more of a sense of command and control. I *HATE* when my system gets trashed.
For several months now, I’ve been interacting with the folks at Zinstall about their various products, most notably Zinstall XP7. This tool works with any version of Windows 7 (including Starter, Home Basic, and Home Premium) to migrate an existing, standalone Windows XP runtime environment into a Windows 7 based virtual machine that matches the original version in every respect.
As the proud and sometimes impatient owner of an Asus 1000HE Netbook (which I’ve upgraded to 2 GB of RAM, and in which I use a Samsung SSD instead of the original 5400 RPM hard disk, impatient user that I am) I had an “interesting” XP target machine that I needed to update to the RTM version of Windows 7 anyway. So I prepped my machine for a Windows 7 install, which included some interesting misadventures in switching from the unit’s convention HD to the Samsung SSD, as I relate in a companion blog, and after installing and updating the 1000HE for Windows 7, then bringing all the drivers up to the latest and greatest versions (thanks to my personal fave Web- and subscription-based driver management tool, DriverAgent.com), I tackled Zinstall XP7 next.
The total time for the install was pretty lengthy — longer than installing Windows 7 itself, in fact, but not longer than applying the 45-odd updates to the base image, nor longer than downloading and updating all the drivers — at around 63 minutes give or take a few seconds (see the time log that follows later in this blog for more details). But the program worked like a charm, and delivered on its promise to return my former standalone XP desktop environment in the form of a VM running under Windows 7. But it turns out that the poor little Atom N280 in this machine just isn’t up to the task of running an XP VM inside Windows 7. Everything worked for me, to be sure (aside from a few brief hiccups with display resolution, quickly fixed once I figured out how to regain control over the mouse and my virtual desktop), but it was so painfully slow that I found it intolerable for any kind of real work. That said, it’s incredibly convenient to be able to return to that runtime environment as and when I need to grab files and information from my prior installation to copy or otherwise import them into the new Windows 7 desktop environment.
Here’s the timetable for my install activities, which also explain the various stages of the Zinstall XP7 installation and conversion process. Here’s a screenshot of the pre-final program display, that names all of the steps in the process.
The list of steps and my timetable ran as follows (times are in mm:ss format):
1. Initializing 15:23
2. Analyzing Source <C:\> 09:30
3. Preparing Source <C:\> 00:05
4. Copying Source <C:\> 04:35
5. Applying hard disk layout 00:02
6. Adjusting old Windows 01:28
7. Configuring Zinstall machine 03:55
8. Fine tuning Zinstall machine 26:05
9. Embedding Zinstall machine 02:05
There were some times during the fine-tuning stage when I despaired of successful completion, because the progress bar for this sub-task seemed to hang at the 95% point nearly forever, but the program did eventually complete successfully and deliver me a copy of my previous XP runtime environment inside a working (but painfully slow, on this underpowered netbook) virtual machine. It was also easy to switch back and forth between the Windows 7 desktop and the XP desktop by using the notification area icons that Zinstall provides both for XP and Windows 7 for that purpose.
When I loaded Zinstall and had it convert my XP environment to a VM, I elected the “convert in place option.” Zinstall can also migrate the XP image from one machine to another across the network, or from one drive (the old system drive, presumably) to another (the new system drive) on the same machine. Everything I saw about the program, as constrained as my netbook was for memory and CPU resources shows me that the program is well-built, very stable, and quite capable. In fact, things should go much, much faster on more powerful hardware, and it’s a real testament to the program’s capabilities that it worked without a hitch on a machine with 1 GB less memory than the recommended configuration for such an in-place install, and on such a puny processor as well. At $89 this program is an excellent value for the money (SMBs and enterprises facing volume migrations should look to the company’s volume purchase offerings, which add a migration server with centralized automated control into the mix).
I had the great pleasure of speaking with Alec Milton, Managing Director of Product Marketing for Oasys Limited last Friday, to talk about the company’s excellent Mail Manager product. Before I tell you a little about the software — which is unbelievably cool and capable — let me tell you a little about the company. It’s the kind of story guaranteed to warm at least my nerdish heart, if not yours as well. As a product, Mail Manager is the result of an internal development project to organize and manage email messages for a world-class large-scale engineering company (the ARUP group, to be precise) gone so very, very well that it has actually given birth to a subsidiary company to sell technology developed to help manage the message and file traffic routinely associated with engineering projects (which not only involve text communications, but huge volumes of supporting files for engineering plans, CAD drawings, complex workflows and schedules, and yada yada yada, along with serious retention and accountability requirements to assume liability and be ready to deal with potential litigation as and whenever it may happen, as it sometimes does).
I’m learning the program and plan to write a lengthy review in 4-6 weeks after I can say something meaninful about its capabilities and benefits based on personal experience. But in a very small nutshell, what Mr. Milton showed me about Mail Manager tells me that its capabilities are pretty darn amazing:
1. It sidesteps all of the standard PST vs. Exchange based message store issues by maintaining its own XML-based message store, which is compact, highly searchable, and supports user tagging and association mechanisms uniquely suited to project-oriented information storage and retrieval.
2. It works equally well for small, SOHO class business where anywhere from one to a handful of people must collaborate and organize documents along with email to keep communications, work product, timesheets, and reports together on a per-project basis, and for ginormous project-oriented mega-engineering outfits like the company what built it — namely, the ARUP Group (for which Alec showed me a message store with thousands of projects and a complex semantic Web uniting project messages, documents, and other elements together so that fast searches and easy access are available on a truly global scale). The biggest users operate the software for a community of about 50,000 users, so I’d have to say that scalability is pretty much proven.
3. From a day-to-day “get things done” perspective, Mr. Milton’s half-hour demo showed me that Mail Manager makes it easy for people to file information as and when they need to, and then to find it later on when they must refer to their stored information for all kinds of reasons. The product even allows offline work, so that pending filing or retrieval activities can be queued up until an Internet connection once again becomes available, without hampering local work or effort in the meantime. The use of a well-indexed, highly searchable centralized and distributed repository also means that duplicate messages and files need not be stored, and that organizations can save on storage and network traffic. The coolest thing I saw was an ad-hoc organization of different kinds of data called “Collections” that is best understood by the Windows-7-savvy as “Libraries for a message store” where items from all over the place (literally) can be composed and organized inside a single logical and hierarchical framework.
I’ve worked with Exchange-based Outlook and SharePoint applications, and with extensive, extended Lotus Notes environments at many and various points in my checkered career. I can’t wait to see how Mail Manager stacks up against these other mega-messaging alternatives as I get to know the product better. Count on me to keep you informed about what’s going on, and to tell you more about what I observe and learn about Mail Manager along the way. In the meantime, to learn more about Mail Manager on your own, check out the Oasys Mail Manager product page at your leisure.
First, a clarification, EOS stands for “End Of Support” and refers to the official cut-off dates for support from Microsoft for these various operating systems. Next, kudos to Ed Bott for totally nailing this topic in his Microsoft Report for ZDNet Monday, entitled “How long will Microsoft support XP, Vista, and Windows 7?”
What makes things interesting here is that MS has extended the normal life of XP in response, one imagines, to the crashing failure of Vista to enlist much market uptake, especially on the corporate side of the street. Ed also explains in his report that “The official date of retirement for support is the second Tuesday in the first month of the quarter following that anniversary [5 years from the General Availability or GA date for general public support, plus another 5 years of "extended support" for business users] …” Microsoft refers to general public support as “mainstream support” and that’s how you’ll see it named in the screencap that follows later in this blog.
Here’s how this works out, for the calendrically challenged:
- The GA date for Windows 7 fell on October 22, 2009. Add five years to get 10/22/2014, after which the next quarter starts on 1/1/2015, and in which the second Tuesday falls on 1/13/2015. That’s when mainstream support ends for Windows 7, so extended support ends 5 years later on 1/13/2020.
- The GA date for Windows Vista fell on January 30, 2007. Add five years to get 1/30/2012, after which the next quarter starts on 4/1/2012, and in which the second Tuesday falls on 4/10/2012. That’s when mainstream support ends for Windows Vista, so extended support ends five years after that, on 4/10/2017.
- The preceding calculations don’t apply to Windows XP because MS has extended its life well beyond those dates already. This is where the Microsoft Product Lifecyle Search page comes into play, into which I plugged Windows XP Professional (as the most likely business/enterprise XP version in use) to produce these results, which peg the end date for extended support at 4/8/2014, with mainstream support already having expired on 4/14/2009.
OK, so now you know. What are you going to do about it? It will be interesting to see how availability of Windows 8 in 2012, before extended support ends for Windows XP, will play out for Windows 7 sales into the enterprise. I personally think this is going to be less of an issue than some believe. That’s because the impending exhaustion of IPv4 addresses and the concomitant wholesale migration to IPv6, plus less-than-stellar support for IPv6 in Windows XP, is going to make Windows 7 a whole lot more attractive and compelling than a lot of enterprises may find it at the moment.
Poking through the Windows blog this weekend, I stumbled across an August 5 posting by Michael Kopcsak entitled “A behind-the-scenes look at designing the new Hotmail: part two.” Part 1 of this series ain’t bad, but Part Two gets into some useful nitty-gritty details. There’s some great suff on message filtering and cleaning up inbox (or folder) clutter using button controls, and a great explanation as to how the filtering mechanisms were designed (and work) to be simple, straightforward, and easy to access.
You’ll also find some peachy explanations of Hotmail navigation and UI behavior, including search, IM controls, and message threading tools. You’ll get an improved understanding of how message history works, and how overall threaded conversations fit and work together inside the Hotmail interface. You’ll get some geat survey results on how the Hotmail default view was designed, and what kinds of user input over time helped to drive design decisions (and a good explanation of why you can organize emails by conversations but why that wasn’t chosen as the default view).
It may not signify much for those who use a different email package (Windows Live Mail, Outlook, Gmail, or whathaveyou) but for those in the Hotmail embrace, it’s really great stuff!