February 11, 2013 4:52 PM
Posted by: Ed Tittel
A quick peek at the latest desktop operating system market share pie graph from NetMarketShare.com shows that Windows continues to dominate, with a least a 86 percent overall share. In that mix, Windows 7 rules at 44.48%, XP follows next at a still-high 39.51%, and Windows 8 trails far behind at 2.26% (less than Mac OS X 10.8 at 2.44%, and just over one third of the aggregate OS X share of 6.4% for versions 10.8, 10.7, and 10.6 combined).
Windows still rules the pie on the desktop, but how long can it stay on top?
But there’s another figure on the NetMarketShare page, that tells a changing story that bodes ill for the desktop — and Microsoft — in the long term. It shows the composition of overall share by device type, and distinguishes desktop devices from mobile and tablet devices. Right now, that breakdown looks like 87.8% for desktop and 11.8% for mobile and tablet devices (presumably with the remaining 0.4% allocated elsewhere or lost to rounding error). But on the corresponding mobile share graph, Microsoft barely registers at 1.15% for all versions of Windows Phone, and iOS at 60.56% and Android at 24.51% rule this roost.
The emerging long-term trend, of course, is that the ratio of desktops to mobile devices is going to keep tilting ever more strongly in favor of mobile devices, as billions of new smartphones and tablets get purchased and start tapping into the Internet, particularly outside First World countries where computer ownership is more or less given in most families. In the Second and Third Worlds, however, high costs and lack of infrastructure, training for, and exposure to conventional PCs combine with an inexhaustible appetite for mobile devices to suggest that sometime in the next decade — perhaps sooner — the ratio will change to put mobile devices in the majority, and those devices will achieve absolute ascendancy as the workloads that demand PCs today can also be accommodated on mobile devices in the future.
When that happens (and most experts are convinced this switchover is just a matter of time) what happens to Microsoft? Good question! Obviously, the company itself is concerned, as its remaking of the Windows 8 desktop as a tablet-oriented OS shows, and as the company’s renewed and intensified focus on Windows Phone OSes also attests. Will it be enough to keep the colossus of Redmond relevant to the emerging 21st century mobile computing landscape? Another good question. I can tell that they’re trying hard to stage a big comeback, but also that success so far eludes their grasp. This should be an interesting technology tango to watch, as Apple and Android seek to eat Microsoft’s lunch. I have to see this as a consumer win, but also hope that today’s highly fragmented mobile landscape finds a bit more order amidst the prevailing chaos as we work our way deeper into this decade, and beyond. This blog may need a new title sometime sooner, if it doesn’t become completely irrelevant before then!
February 8, 2013 4:23 PM
Posted by: Ed Tittel
With documented exploits for both Mac OS and Windows reported in the field, Adobe released another Flash version last night, moving up from version 11.5.502.146 to 11.5.502.149 in the process (see both numbers in my Flash Player Settings Manager window, after updating IE with the ActiveX version, but before installing the Plug-in Version for Netscape-compatible browsers):
The latest version counters malware vulnerabilities in both Mac OS X and Windows versions.
The previous version (11.5.502.146) carries a release date of 1/8/2013 in the Flash Player Archives on the Adobe Website. Dan Goodin of Ars Technica has an excellent story entitled “Adobe issues emergency Flash update for attacks on Windows, Mac users,” that indicates updates are also available for Android and Linux platforms, too. Apparently, the thinking is that the vulnerability is severe enough to warrant hurry-up effort from malefactors to bring it up on those other runtime environments, because the ability to compromise Safari and Firefox on the Mac has also played into foisting booby-trapped Word documents with malicious Flash content on the PC is believed likely to show up in various other forms there as well. These vulnerabilities are classified as CVE-2013-0634 (Mac) and CVE-2013-0633 (Windows).
Here’s the skinny on the latest versions for all platforms, straight from Goodin’s article:
Thursday’s fix brings the latest version of Flash for Windows and OS X to v. 11.5.502.149. The latest Linux version is v. 188.8.131.522, and the most current Android versions are 184.108.40.206 for Android 4 and above and 220.127.116.11 for Android 3 and earlier. Updates are available here. Flash in Google Chrome and in Microsoft Internet Explorer 10 is automatically updated.
In this context, it’s worth pointing out that Google is invariably speedy in posting updates to Flash for Chrome ( my Plugins page currently shows version 18.104.22.168, and Adobe claims that’s the most recent version thanks to its find-version-flash-player page. OTOH, Microsoft pushes Flash updates for the Windows Store UI version of Windows 8 through Windows Update, and a version was posted to that service at 3:15 yesterday afternoon. The corresponding Adobe Security bulletin addresses the same CVE numbers mentioned earlier in this blog post, so it looks for once as if MS has pushed out an “emergency” Flash update in a timely manner. I’m stunned, but also pleased…
February 6, 2013 4:19 PM
Posted by: Ed Tittel
The real-PC version of Microsoft’s Surface tablet, the Surface Pro, becomes publicly available this Friday, February 9. So far, I’ve seen stories on the new tablet from Paul Thurrott (SuperSite for Windows), Ed Bott (The Bott Report, ZDNet), David Pogue (NYT), Jon Phillips (PCWorld), and countless others (run this Google News search to see dozens of serious, reputable reviews and commentary, amidst thousands of blogs, opinion pieces, news reports and more).
The Surface Pro supports a Wacom digitizer pen, which many reviewers liked (Source: CNET).
So far, here’s the emerging consensus:
1. Battery life is indeed a problem, as it was expected to be, with 4-6 hours of battery life available for varying usage scenarios.
2. Overall functionality and capability (aside from how long the battery holds its juice) are uniformly positive, but that positivity varies from lukewarm to medium, and seldom jumps into rabid enthusiasm.
3. The 1920×1080 true HD display gets uniformly good ratings for sharpness, clarity, and readability, and beats 1366×768 displays hands-down.
3. As a tablet, the Surface Pro gets ho-hum ratings from the experts; as an ultrabook, it does somewhat better, especially with the Type cover. It’s never positioned as a world-beater by anybody, though.
4. These days a 64 GB SDXC memory card — which the Surface Pro will gladly accommodate — costs anywhere from roughly $40 for a slow model, to upwards of $150 for a pretty fast one (over $200 for the fastest models). This provides an easy way to stretch the 89-plus GB of free storage space available on the Surface Pro’s 128 GB SSD. 128 GB SDXC cards should become available later this year, but will also be costly.
In general the experts are pretty broadly split on their decisions regarding the Surface Pro, with about half saying “So-so, not the greatest, not my cup of tea,” and the other half opining that for those looking for maximum portability with real Windows PC oomph it’s the best choice among the other offerings of its kind available from Acer, Samsung, Sony, and others. In revisiting about a dozen of those reviews, I note that the reviewer’s final opinion often rests on how strongly wedded they are to Windows computing in general, versus a more catholic or platform-agnostic view of the overall mobile computing space.
Ed Bott Sez It Best
IMO, Ed Bott summed up the unique position that the Surface Pro occupies in the PC marketplace today in his review for ZDNet entitled “Is the brilliant, quirky, flawed Surface Pro right for you?” Here’s what he has to say at the very tail end of his 3-page story, quoted verbatim:
…this is a great product for anyone who’s already committed to a Microsoft-centric work environment. It isn’t likely to inspire many iPad owners to switch, unless those Apple tablets are in the hands of someone who has been eagerly awaiting an excuse to execute the iTunes ecosystem.
I don’t expect Surface Pro to be a breakout hit for Microsoft. Too many people will have good reasons to say no, at least for now. But it does represent a solid, interesting, adventurous alternative for anyone who wants to spend some quality time today exploring Microsoft’s vision of the future.
To me, this makes the upcoming super-ultra-low voltage Haswell processors due out from Intel later this year even more interesting — and important for the future survival of the Surface Pro models, and perhaps also for the future of PC and notebook computing as we understand it today. If the new chips mean that Microsoft (and other hardware designers) can trim the extra 0.5″ that currently separates the RT from the Pro model (and others of those ilks) and boost battery life to the 8-10 hour range, by golly, we might just have something. If that doesn’t happen, though, the real question will become: Is there enough there to make buying into this hardware vision worth doing for business and more serious personal users. Methinks not. Methinks further that the emergence of the Chromebook phenomenon is likely to play hob with this entire set of market dynamics.
February 5, 2013 3:36 PM
Posted by: Bridget Botelho
Dell has officially gone private.
The company has been in a transformation phase for some time as cloud computing, tablets, and mobile devices have eaten into its PC and server business. Industry watchers say that going private could help the company compete in new markets.
Here, in its entirety, is CEO Michael Dell’s email to company’s employees on what this move means for the business as a whole:
Today, we announced a definitive agreement for me and global technology investment firm Silver Lake to acquire Dell and take it private.
This transaction is an exciting new chapter for Dell, our team and our customers. We can immediately deliver value to stockholders, while continuing to execute our long-term growth strategy and focus on helping customers achieve their goals.
Together, we have built an incredible business that generates nearly $60 billion in annual revenue. We deliver enormous customer value through end-to-end solutions that are scalable, secure and easy to manage, and Enterprise Solutions and Services now account for 50 percent of our gross margins.
Dell’s transformation is well underway, but we recognize it will still take more time, investment and patience. I believe that we are better served with partners who will provide long-term support to help Dell innovate and accelerate the company’s transformation strategy. We’ll have the flexibility to continue organic and inorganic investment, and grow our business for the long term.
I am particularly pleased to be in partnership with Silver Lake, a world-class investment firm with an outstanding reputation and significant experience in the technology sector. They know all the technology business models, understand the value chain and have an extremely strong global network of contacts. I am also glad that Microsoft is part of the transaction, further building on a nearly 30-year relationship.
I am honored to continue serving as chairman and CEO, and I look forward to working with all of you, including our current senior leadership team, to accelerate our efforts. There is much more we can accomplish together. I am committed to this journey and I am grateful for your dedication and support. Please, stay focused on delivering results for our customers and our company.
There is still considerable work to be done, and undoubtedly both challenges and triumphs lie ahead, but as always, we are making the right decisions to position Dell, our team and our customers for long-term success.
February 4, 2013 5:30 PM
Posted by: Ed Tittel
Don’t ask me why — because I can’t answer that question — I chose to use one of my Centron 128 GB USB drives to build a recovery and repair boot-up disk this weekend. I used the Recovery Drive option on one of my Windows 8 machines. Here’s the crux of the matter: the disk partition for the repair medium gets formatted using FAT32, which limits the size of the resulting drive to 32 GB. Here’s a snapshot of the resulting drive from the Disk Management plug-in for the Windows Management Console (diskmgmt.msc):
An atypical USB flash drive problem: more real estate than a utility can use.
Of course this isn’t a problem for USB flash drives of 32 GB or smaller, so probably the most important take-away for readers of this blog post is: don’t use UFD’s larger than 32 GB to build a Windows 8 Recovery Disk. If you do, you’ll find yourself in the same situation I found myself in after setting this up — namely, with a whole bunch of unallocated space on the resulting drive that remains inaccessible to that recovery disk itself.
The gotcha comes into play in that, unless you dig deep into the command-line diskpart.exe utility, you can’t clean up the drive that’s been set up using the built-in Windows 8 tool. Thus, for example, you can’t delete the bootable partition from what appears as the I: drive in the preceding screen capture. Even if you change its format from FAT32 to NTFS, diskmgmt still won’t let you extend or delete the resulting partition, either. The first time I cleaned things up, I turned to Paragon’s Hard Disk Manager to do the job, and instructed it to wipe the drive, then to create a single 119 GB partition (that’s the actual size of the drive, as reported in File Explorer and other native Windows utilities, as confirmed in the Disk Management screenshot above). But that took too long for my impatient self (the wipe drive is very thorough, to meet MilSpec data wiping standards, and took several hours to complete). The second time I found myself in this spot was when I created the screenshot that appears earlier in this post, after which I turned to diskpart for the ensuing clean-up. I started with the “list disk” command to ensure that I wanted to work on Disk 5 as shown above, then typed “select disk 5″ to turn the utility’s focus to that drive, then finally “clean” to wipe out all of its existing disk format info. At that point, using diskmgmt. msc I was able to define a new simple volume, and format the drive to NTFS, and name it Centon128.
Three quick commands in diskpart.exe, and you’re done, done, done.
February 1, 2013 3:50 PM
Posted by: Ed Tittel
As an inveterate tinkerer, and somebody who’s always finding reasons to troubleshoot Windows systems, I’m always on the lookout for good tips, tweaks, tricks, and repairs. This morning I found a good one over on TechSpot, by Julio Franco entitled “Windows 8 Boot Issues? Try Fixing the Master Boot Record (MBR) or Boot Configuration Data (BCD).” I actually experienced the very issue he documents in that story — boot problems when adding a second SSD to a system, though mine stemmed from the installer’s practice of leaving a separate boot/recovery partition intact on the original boot drive, so that when I removed the original SSD from that system, the new system drive actually lacked a boot partition — about two weeks ago, and went through the very automatic repair scenario he describes at the first of the various fixes he describes therein.
Here’s a snap of the “Advanced Options” screen that Windows 8 presents when you elect to troubleshoot a Windows 8 installation during the boot-up process:
What you want is Automatic Repair from these options to access boot repair facilities.
For more info on how to provoke this menu, and use its options and selections, see Kent Chen’s excellent story at Windows 7 Hacker entitled “Microsoft Layouts Windows 8 Boot Options,” itself based on a Building Windows 8 blog from May, 2012, that digs deeply into Windows 8 boot options and behavior. Good stuff, all the way around!
What I like best about Franco’s TechSpot article is that it marches you through the various options for boot repair quickly, with brief but helpful instructions on how to use each one effectively. He starts with automated repair, then digs into basic command line tools to achieve the same end. After that, he explains how to use BDCedit if necessary, and then points to the executable for the startup repair tool (StartRep.exe) as a last-ditch method when all else fails. And of course, if none of this works, it’s time to reformat (or replace) the boot drive, and then to restore your latest image backup!
January 30, 2013 3:58 PM
Posted by: Ed Tittel
This morning, I was poking around on the Windows 8 Forums site, and found a nifty tutorial on the improved check disk (chkdsk) utility that’s been built into Windows pretty much since Day 1 of its nearly three decades of life. Alas, there is an error in that tutorial that caused me a bit of stumbling around until I finally had the intelligence to call on the utility’s own built in help file (shown in the following screenshot, along with my attempt to use this new feature which garbage collects unneeded security descriptor data on the target drive):
Upon looking at the file I recognized that the security descriptor switch in the tutorial appears as “sdccleanup” when it should instead be “/sdcleanup”; likewise, “offlinescanandfix” should be “/offlinescanandfix” as well. But with these minor gaffes corrected, I was able to explore the new capabilities and see how they worked. I can’t say that the changes are laden with drama, but they do offer some nice new capabilities, including the security descriptor cleanup (which will recover increasingly more space on drives as files are added then deleted over time) and the spot fix capability, which performs limited repairs without requiring a system reboot (except when they are required on the system/boot volume, which will have to be performed immediately following the next reboot).
Good stuff: check it out!
January 28, 2013 6:24 PM
Posted by: Ed Tittel
At midnight, Wednesday, January 31, the Microsoft budget upgrade offer for Windows 8 expires. I just jumped up to the Windows 8 Upgrade Offer page, and learned that those promo codes Microsoft has been sending me via e-mail (thanks to my various Windows Live accounts) bring the price down from an already-awesome $39.99 to an even more stellar $14.99, if entered into the promo code field during the “pay for it before you get a key” phase of the ordering process.
Act fast, because the “deal” is off starting on February 2 (this Thursday).
If you don’t want to install the OS any time soon, you can quit the process as soon as you’ve paid for your new license and you get a key for a Windows 8 install. You can always grab the ISO file from other sources later on: as long as your key is good you can wait until you’re ready to install, well after the January 31 deadline comes and goes. In my case, I’ve already built a couple of bootable UFDs with x64 Windows 8 Pro install images — one for UEFI machines, the other for machines with conventional BIOSes. I’ve used them before for numerous Win8 installs, and I’ll use them again with my bargain basement keys.
And again: if you do have a promotional code for Windows 8, it takes the already low $39.99 cost down to an irresistible $14.99. But you must grab your key before midnight Wednesday to take advantage of this pricing. Don’t delay: do it now!!!
January 25, 2013 10:37 PM
Posted by: Ed Tittel
In the past three or four months, I’ve messed around with various takes on installing Windows – especially Windows 8 — on PCs sporting the Unified Extensible Firmware Interface, in lieu of the more traditional BIOS firmware used to raise PCs from a cold dead start to normal operation since time immemorial. Along the way, I’ve encountered lots of speculation, rumor, and word of mouth information on this fascinating topic. This morning, I finally came across a detailed reference in the TechNet Library that I wanted to share with all of my readers.
What you see to the left is a snippet from that element of the TechNet Library entitled “Phase 4: Image Deployment,” specifically the entry that’s highlighted in black: “Installing Windows to an EFI-Based Computer.” It explains that you must run Windows set-up, which may or may not take advantage of a special answer file to perform all kinds of interesting and intricate disk partitioning and formatting as part of the initial set-up process.
There’s an equally interesting article elsewhere in TechNet entitled “Sample: Configure UEFI/GPT-Based Hard Drive Partitions by Using Windows Setup” (and a variant that uses Windows PE and DiskPart instead). These items include step-by-step answer file entries (for the first of these two options) or ready-to-run script files (for the second) to handle the details of disk layout, partition assignment and sizing, and so forth and so on.
So far, this is the first and best detailed set of instructions and information on working with UEFI that I’ve found. It’s already helped me to make sense of the kinds of default disk layouts that Setup creates on its on when you perform a UEFI-based install, and I now understand how to increase the size of some of the non-Windows disk partitions that have occasionally given me trouble in the past (particularly the Windows RE tools, MSR, and Recovery Image partitions that Setup creates on its own).
What I still long to do, however, is to boot my UEFI PCs into the EFI shell immediately following start-up and learn how to work on my systems inside that pre-Windows boot run-time environment. I’ve read the Intel books (Beyond BIOS… and Harnessing the UEFI Shell) but I’ve yet to get to the command line and do anything with it after booting into EFI. Because I’m dying of interest and curiosity, I’m hoping some reader can recommend how I can built a boot USB or CD-ROM that will actually put me into a working run-time environment after booting into EFI.
Otherwise, these resources make me feel much more comfortable working with EFI-based installs, image captures, and deployments. Though I haven’t yet reached UEFI nirvana, that makes me feel a whole lot better about this stuff. Hopefully, other readers will benefit from access to these resources as well.