Preston Gralla writes a great blog for Computerworld entitled “Seeing through Windows.” That title can, of course, be interpreted in more than one way — and so very often can his blogs — and those are just some of the things I like about his work. In an 8/28/2012 posting entitled “Samsung Weighs in on Windows 8: Users need the Start button,” Gralla describes three Samsung desktops (all-in-ones, actually) planned for Windows 8, all of which include an optional Start button.
Quoting from an AP report entitled “Samsung previews its 3 Windows 8 desktop computers,” he pulls a fascinating quote that reads as follows:
“In an effort to minimize the potential frustration caused by Windows 8′s new look, Samsung built its own optional start button that can be used to pull up a menu of applications.”
Interestingly, it looks like PC vendors will have a chance to remedy one of the biggest user and pundit complaints about Windows 8 — namely that it lacks the old familiar Start button found in every Windows version since 95, and missing in 8 in favor of the Modern (“Metro”) UI screen instead. I wonder how this capability will differ from Stardock’s free Start8 functionality: this tool puts the old familiar Start button back on the toolbar, but doesn’t offer a set of pull-down menu for all installed non-Metro programs. Instead it throws up the Windows 8 Start screen in a more contained format. It will be interesting to see what Samsung — and possibly also, other vendors — offer up to compensate or correct for this all-too-common Windows 8 complaint.
As is so often the case, after I upgraded from Windows 8 RP to RTM, I had a few drivers to clean up on each of my test machines (right now, they include a Lenovo X220 Tablet and a home-built desktop with an Asus P8Z68-V Pro Gen3 mobo, i7-2600K CPU, 32 GB RAM, and so on). On the RP version, DriverAgent gave me a clean bill of health for each OS before I started the upgrade process to Windows 8 Pro RTM, and left me with three drivers in need of update on the Lenovo notebook and four drivers on the home-built desktop machine.
In both environments, Bluetooth proved the most challenging element to find and fix. I was unable to install the recommended Fujitsu driver on the X220 without first unpacking the contents of the recommended ZIP file, then using Device Manager to forcibly update the drivers using the old, familiar “Update my driver” and “Browse my computer for driver software” menu progression for the affected device on that machine. The same approach didn’t succeed on my Asus homebrew box, because I ran into software compatibility problems simply trying to run the self-installing executable that DriverAgent said I needed for that machine. I used the technique of clicking the left-hand icon on the device line in the DriverAgent scan to see what else was available to me, as show in this screen capture:
With the second software/driver combination I was able to install a working Bluetooth environment on my desktop PC, and jump the driver currency hurdle in DriverAgent for that machine, as this scan display header attests:
On to the next tangle…
With drivers now finally subdued, I used Secunia Personal Software Inspector (PSI) to check software status on the two Win 8 Pro RTM machines. A quick Chrome and Adobe component (Flash, Shockwave, and Air) quickly got the Lenovo X220 Tablet whipped into shape, but I have to chase another chimera with Adobe Flash on the desktop machine. PSI tells me I need a new 64-bit version of the ActiveX Flash Player (it sees that version 11.3.372.94 is installed). But when I try to perform the auto-update, by accessing get.adobe.com/flashplayer, I get this very interesting error message from the site instead of an auto-update:
But when I try to install the standalone installer for Flash version 11.4.402.265 I get an Adobe error message that reads as follows: “Your Microsoft Internet Explorer browser includes the latest version of the Adobe Flash Player built-in. Windows Update will inform you when new versions of the Flash Player are available.” It also provides this explanatory screen:
On the one hand, we clearly see a new version is available, on the other Adobe won’t let me install it, and MS isn’t pushing the latest version through Windows update yet. Even running the Flash uninstall utility, I wasn’t able to force IE 10 to drop the old version and prepare the ground for the new one. I’ll just have to wait and see what happens with this, and live with the older Flash Player version in the meantime, I guess…
As this snippet from Peter Bright’s Ars Technica story from yesterday illustrates, Microsoft’s replacing the corporate logo it’s used for the past 25 years.
I’m not the only one who’s noticed its resemblance to the Windows 7 logo, albeit in “non-wavy,” unshaded rectilinear form. Many other pundits and observers have noted the similarity of colors in the four logo blocks above to the Win7 flag’s layout and position.
It’s very interesting that as the Windows 8 logo adopts a monochrome blue color scheme and a rectilinear layout, the Microsoft logo picks up the rectilinear motif, but drops its “perspective view,” at the same time preserving the four-color theme from Windows 7.
What’s it all mean? I wish I could say for sure, but it does seem to suggest continuity with the Windows brand, while shaking up the established order for something new and different.
Here’s my first report on experiences with Windows 8 Pro RTM, in the wake of two successful upgrade installs: one on my Lenovo X220 Tablet, the other on my i7-2700K.
First things first: Mr. Denny’s tip on modifying the
cversion.ini file in the
.../sources directory in the unpacked ISO files is a gem. I was indeed able to use a modified ISO-based image for Windows 8 Pro to perform an upgrade install on my Windows 8 Release Preview install, and preserve my already-installed applications and tools, as well as settings and preferences while installing the latest and final version of the OS on my Lenovo X220 Tablet and my i7-2600K desktop PC. As you might expect, the installation takes a while longer (over half an hour) when you have various installed elements to port over from an old OS to a new one. I grabbed the Windows 8 Pro ISO from MSDN on Tuesday, and then used the Windows 7 USB DVD Download tool to convert that ISO to a writable install image on an 8 GB UFD (I tried a 4 GB UFD, and the copy process failed to complete properly, so you’ll want to go 8GB or larger). A quick edit to the aforementioned file, and everything worked as I expected it to.
The post-install aftermath came with a couple of unexpected and interesting side effects. I figured the Windows 8 RP drivers would port to Windows 8 RTM without a hiccup, but I figured wrong. For one thing, I had issues across the board with Bluetooth. Before the installer would let me proceed with the Windows 8 Pro install on my desktop, which includes an Asus P8Z68-V Pro Gen3 motherboard with built-in Qualcom Atheros BT circuitry, it required me to uninstall the Asus BT GO! Bluetooth software, citing incompatibility issues with that software. And so far, I’ve been unable to find a replacement BT software suite to run with this motherboard, either. That said, the built-in Windows Bluetooth utilities — namely Add Bluetooth Device, Change Bluetooth Settings, View Devices and Printers, and Set up a connection or network — all work properly with the default driver that Windows 8 Pro RTM installed on that machine. Likewise, I’ve been unable to install and use what DriverAgent insists is the latest and greatest Bluetooth driver on either machine, so there’s something wonky going on with BT that I’m still puzzling my way through.
On the Lenovo X220 Tablet, four drivers needed updating after I upgraded from Windows 8 RP to RTM:
- Intel HD Graphics 3000: I was able to grab and use a Fujitsu driver (they seem to be doing a very good job of keeping up with Windows 8 drivers, and I’ve learned to trust them as a source for solid, stable Windows 8 driver software). But my Windows Experience Index value for this graphics circuitry dropped from 5.1 in Windows 8 RP to 4.6 in Windows 8 Pro RTM.
- Intel 82579LM GbE Network Connection: another Fujitsu driver to the rescue here, thanks very much.
- Intel Display Driver Audio: still one more Fujitsu driver, and thanks again.
- Bluetooth: haven’t yet been able to crack this nut, even using the Fujitsu driver. Instead of a successful install, I get the following error message window, even if I use the Program Compatibility Troubleshooter and try it with various XP, Vista, and Windows 7 settings as well:
I imagine I’m just going to have to wait to get these matters resolved, as Asus and Lenovo (and probably also, the Bluetooth technology vendors such as Qualcom Atheros, Broadcom, and so forth) get their heads around the underlying issues and start to issue newer drivers and software tools for their Bluetooth devices.
Some other observations based on my two days’ of experience with the new OS include:
- Boot-up and shutdown are noticeably faster on both machines as compared to the RP version
- The Aero-free desktop is pretty clean, and easy to work with
- Switching between Windows 8 GUI (the UI formerly known as Metro) and the desktop is easier than before, thanks to easier access to the Start screen by “cornering the cursor” (moving it into the nearest corner on your screen)
- Desktop Gadgets are indeed gone, gone, gone (searching for “Gadget” through the Start screen turns up 0 Apps, 0 Settings, and 0 related Files).
- Gabe Topala’s Siw-x64.exe (the temporary version he produced for Windows 8 beta users) quits working in the RTM version. So far, no news on a replacement 64-bit commercial version for Windows 8 x64 RTM and final versions, either.
- All of my applications still appear to be working: I haven’t made an exhaustive survey of everything yet, but every program I’ve tried has continued to work without issues (except for the Bluetooth stuff the installer asked me to uninstall before I continued on with Windows 8 Pro installation, but since it’s not installed anymore, I can’t exactly try it out — and it won’t install on Windows 8 Pro, either).
My final comment on where things stand is “So far, so good.” I’ll continue to follow up as more things present that appear worthy of reporting and discussion.
Thanks to SQL Server blogger Mr. Denny right here on ITKE, I have a great trick to share with readers who want to upgrade their Windows 8 Release Preview installs to the latest RTM version now available through MSDN, TechNet, and other sources. This blog post of his is entitled “Upgrading Windows RP to RTM” and covers the complete set of actions required to achieve this eminently laudable goal, step-by-step. Apparently, the whole exercise hinges on the contents of a file named
cversion.ini that resides in the
<drv>:\sources\ directory (where <drv> is the drive letter for the UFD onto which you’ve unpacked the Windows 8 RTM install ISO image). I’m guessing that the number that appears in this file usually matches up to whatever release number attaches to the version of Windows installed on your PC. For Windows 8 Release Preview that’s 8508.0. But by changing the number to 7100.0 (a number that corresponds to a version of Windows 7 , though my Windows 7 with SP 1 installed shows up as 7601 when I run the
winver command) you can fool the installer into performing an upgrade install to bring your version up to the RTM version without demur.
Fantastic! Having been out on vacation this past week with family, I plan to try this out later today, as soon as I finish downloading the latest Windows 8 RTM ISO from MDSN.
[Note: Copy added 12:14 PM CST Tuesday 8/21/2012]I’m installing the new OS right now. Without editing the cversion.ini file on the install UFD, I couldn’t access the upgrade option on my Lenovo X220 Tablet. But after editing the UFD as Mr. Denny suggested, the upgrade install is steaming along on that machine quite happily right now. When it finished, I’ll do the same for my home-built i7-2700K desktop and see how that works. Tomorrow, I’ll blog about my upgrade experiences. Stay tuned!
The ongoing Metro flap continues. Yesterday, Mary Jo Foley posted a story entitled “Microsoft: Don’t call it Metro. Call it ‘Windows 8.’” She suggests that the whole dust-up is intended to resolve a naming dispute with a German retailer (and Microsoft partner) named Metro AG. So, from now on anyplace you’ve seen Metro, you’ll now see Windows 8 popping up. Thus anything once called “Metro-Style application” (which sometimes appears without the hyphen) is to be called “Windows 8 application.” Likewise for “Metro Design;” it’s now “Windows 8 design.” She also points to a new promo page from Lenovo for its Windows 8 Thinkpad Tablet 2 that makes use of the new terminology in a bullet that refers to “Desktop and Windows 8 Apps.”
There’s still some apparent confusion within the MS ranks, though: earlier this week the Windows 8 app developer blog featured an entry entitled “Building your own Windows Runtime components to deliver great Metro style apps.” It will probably take a while for this new official word to percolate all the way through the organization and for the necessary string substitutions to take effect globally. Foley also speculates that the same rules will affect Windows Phone as well, itself due for a version 8 of its own software.
Others have speculated that terms such as “Modern UI Style” might possibly replace Metro (Tom Warren, The Verge). Apparently, MS used Modern in connection with the new interface as far back as January 2011, as documented in this article from Paul Thurrot. Who knows? In this rough-and-tumble world of Windows, anything is possible! That said, you can be sure MS won’t call it “Old-fashioned,” “Frustration,” or “No More Start Menu!”
There’s been enough hoopla and unhappiness about the Windows 8 tile-oriented user interface known until now as Metro, that MS has apparently decided to kill the name and call this GUI something else entirely. Too bad I haven’t yet laid hands on the RTM code for Windows 8, because I’d love to find out if the M-word shows up in that version of the OS. On August 2, Mary Jo Foley of ZDNet reported that “…I’ve been hearing from a number of my contacts that Microsoft is trying to slow, if not halt, internal and external use of the term ‘Metro.’” She also produced this marvelous quote from a Microsoft spokesperson about Metro: “We have used Metro style as a code name during the product development cycle across many of our product lines. As we get closer to launch and transition from industry dialog to a broad consumer dialog we will use our commercial names.” Very interesting, and even more interesting is the follow-up work that Ed Bott documents in his recent article entitled “Cleaning Up Microsoft’s Metro Mess.”
Ed performs some fascinating text analysis on the MS corpus, to produce the following information on Metro mentions therein:
- Steve Ballmer mentioned Metro as “our featured attraction” in his 2012 CES keynote address, and then went on to mention the name 27 times in that presentation.
- Microsoft has been encouraging developers to build Metro style apps since 2011, until the end of last week (August 3).
- Microsoft even posed a Windows Metro Style App Challenge to students enrolled in accredited college-level programs.
- He provides a link to a page in the Windows Dev Center entitled “White papers for Metro Style apps” that includes over a dozen entries, plus links to other materials.
- He points to language in the App Developer Agreement that makes repeated references to Metro Style Apps as such, and also points to sessions for MS’s Public Sector Developer Weblog for sessions at a Tampa, FL, DevCamp Public Sector Series, 7 of which use the word “Metro” in their titles.
Though other market followers have already intoned the inflection point between Windows XP and Windows 7 — namely, the point at which the old (XP) finally dips below the new (Win7) — tracking firm NetMarketShare has not yet seen its sampling of millions of PC users indicate that Windows 7 has surpassed Windows XP in overall share. That said, they do report that the numbers are getting closer all the time, as witnessed in the last years’ trend lines for XP (in blue) and Windows 7 (in green).
It looks like the inflection point could occur sometime during this month (August, 2012). That’s ironic because it’s occurring almost three years after Windows 7 launch in October, 2009, and only three months before the General Availability date for Windows 8, which was released to manufacturing on Wednesday, August first. The RTM version of Windows 8 will be made available to entitled users through subscriptions or service contracts starting with TechNet and MSDN users on August 15, and various other groups shortly thereafter. This all reminds me of the grim need to avoid gaps in the royal succession inherent in the French epigram: “Le Roi est mort, vive le Roi!” (The [old] king is dead. Long live the [new] king!)
I find myself wondering if the success and uptake for Windows 7 (which is now also running on half or more of enterprise and business desktops globally at long last) doesn’t make it less likely that the Windows 8 trend line will be close to crossing over the Windows 7 trend line three years from today. Windows XP’s long run — it’ll be eleven years old the day before Windows 8 becomes generally available on October 26 — may just presage a longer-than-expected run for Windows 7, too, given how reluctant business users have become to relinquish Windows versions that appear to be stable and reliable. My gut feel is that Windows 8 is in for a longer occupation of the crown prince’s chair than Windows 7 had, and that this poor prince may never actually take the throne, given others sure to queue up (Windows 9 and 10) behind him may get a better reception in the marketplace than Windows 8 has enjoyed so far.
At 11:00 AM Central, 9:00 AM Pacific, Microsoft pushed “Releasing Windows 8 — August 1, 2012” out to the Building Windows 8 blog. It wasn’t so much a set of rumors (see below), as it was a set of educated guesses, apparently. Also, as of today, “… the [Windows] Store is open for business, and we’ll rapidly expland to over 200 markets around the world.” Though the next stop is touted as GA on October 26, no word yet on when the RTM will be made available to corporate users, and to the legions of TechNet and MSDN subscribers. I guess we’ll have to save that for another day!
[Note added 8/2/2012] Peter Bright at Ars Technic reports this morning that MSDN and TechNet subscribers will gain access to Windows 8 RTM on August 15th. See his story about the RTM release to manufacturing for more information.
OK, the rumors are flying thick and fast that MS has already signed off on the RTM release, and that it will make its way to OEMs really, really soon: meaning today. I’m watching the MS site for news –especially the Building Windows 8 blog (often the place where release news receives its first official Microsoft mention) — but so far, there’s nothing official. That said, you can find rumors, guesses, and other forms of speculation all over the place that August 1, 2012, is THE DAY for Windows 8 RTM to leave Redmond and make its way into OEM’s no-doubt eager hands. Check out this Google News search to see over 50 stories on this subject, including this doozy from the BGR site in India entitled “Windows 8 RTM leaked, offers more customization options,” itself based on information posted to the Win8China site on July 31.
Windows 8 tracking site Windows8Beta.com also posted a story early today entitled “Windows 8 RTM Already Signed Off?” They quote a report from the WinUnleaked.info Windows 8 build list to the effect that a release numbered
9200.16384.win8_rtm.120725-1247 is in all likelihood the Windows 8 RTM release that will go to OEMs sometime today. With tongue planted firmly in cheek to acknowledge its “license terms,” I reproduce the builds list graphic as the lead-in to today’s blog posting. I’ll keep check the official MS outlets, and post again later whenever real word comes.
I had to chuckle this afternoon when I read Ed Bott’s latest Operating Systems piece. It’s entitled “How to skip Windows 8 and continue using Windows 7.” In it he makes the very essential observation that MS doesn’t retire its old OSes as soon as new ones come out. He also tells an amusing story about his experiences in a Kentucky coffee shop to make this point: “If you don’t want to upgrade, just don’t upgrade.” Then he points out that the end-of-support-date for Windows 7 SP1 is January 14, 2020 (that’s 7 years and 5 months from now). He also observes that retailers will be able to sell a boxed version of Windows 7 until October 25, 2013 (or longer) and that OEMs can sell systems with Windows 7 pre-installed until a year after that (October 25, 2014, and also perhaps longer). And finally, he points out that Windows licenses usually confer downgrade rights, so that you are within your rights to replace Windows 8 Pro with a copy of Windows 7 Professional, should you so choose. Bottom line: Windows 7 isn’t going to disappear when Windows 8 ships, and plenty of buyers will happily continue to buy and use systems with the older OS installed.
I’m still waiting to understand more good reasons to upgrade to Windows 8, and continue to believe that “later, rather than sooner” will be the timing for many business users who don’t have compelling needs to put tablets or other touch devices into their employees’ hands. By the same token, I’ll be very curious to see if a new generation of touch-enabled mobile devices springs up to replace the durable Psion and other touch- and pen-based devices that some meter-readers, the UPS guy, and countless other mobile workers carry with them on their daily rounds of data acquisition, service or package delivery, and so forth and so on. Maybe the embedded systems buyers will actually lead the charge to the new OS, simply because it speaks to value propositions that they already know and love?
On the other hand, I’ve found many things about Windows 8 to be worth an upgrade — at least as far as I’m concerned:
1. I’ve been using touch long enough now that it’s starting to feel natural and unforced. In fact, I find myself reaching out to touch screens now that lack touch capability, just because I’m used to interacting with my systems in that way.
2. I’ve also learned to appreciate Windows 8′s improved Task Manager and its nice touches to the Windows Explorer interface (especially more and better data about ongoing file copies, the Quick Access Toolbar, better right-click menus, and context-sensitive tool tabs).
3. The ability to synch my notebook and desktop using the login to the same Windows Live ID is great — as long as you set files up so that they’re easy to share across platforms. I expect this will become a widely-used feature for users who bounce between or among multiple Windows platforms. So far, I don’t see it reaching far enough to create a clamor for Windows 8 smartphones, but I could always be wrong (or somebody will write a killer app that brings Android and iOS devices under this umbrella).
4. A sleeker, speedier Windows: Faster boot-up and shutdown, faster app loading and execution, manageable memory footprint, incredibly SSD-friendly. There’s probably more to say here, but I haven’t found or learned it yet. I can’t wait until Mark Russinovich and his colleagues get around to another update to their Windows Internals book, so I can improve my understanding of the inner workings of this new OS (but alas, it probably won’t be out for at least another 18 months, if history is any guide).
I think for a lot of consumer- and enthusiast-grade users, these factors and more will propel a certain level of Windows 8 adoption when it hits the streets in October 2012. Whether that’s enough to justify Microsoft’s hopes and analysts expectations’ that Windows 8 sales will help Microsoft’s earnings trend upward is still an uncertain guess, as far as I’m concerned. All I can say on this subject is “We’ll see…”