In a nutshell things work as explained in this bulleted list that I lifted directly from the Live ID blog I just cited:
- Associate the most commonly used Windows settings with your user account. Saved settings are available when you sign in to your account on any Windows 8 PC. Your PC will be set up just the way you are used to!
- Easily reacquire your Metro style apps on multiple Windows 8 PCs. The app’s settings and last-used state persist across all your Windows 8 PCs.
- Save sign-in credentials for the different apps and websites you use and easily get back into them without having to enter credentials every time.
- Automatically sign in to apps and services that use Windows Live ID for authentication.
The key phrase that impelled my blog title appears a little later in this post, is in a later paragraph that explains in more detail what kinds of settings are captured and preserved (“… your lock screen picture, desktop background, user tile, browser favorites and history, spell check dictionaries, Explorer settings, mouse settings, and accessibility settings, among many others…”). It says that all of these things “… are now associated with your Windows 8 account and stored in the cloud.” But alas, this capability apparently applies only to Metro style apps because the blog further states: “If you want to roam your settings for desktop apps then you can continue to use the mechanisms available for roaming profiles and client side caching of files available with Active Directory and Windows Server.”
Dang! I see the emergence of a two-tier system here, and a powerful impetus to move users onto Metro style applications. It will be VERY interesting to see how this all plays out, and to see if application developers take the bait and start building Metro style interfaces for most common and popular applications. Only time will tell, but this should be fascinating to watch and learn from.]]>
Side view of the Alienware/Dell M11x notebook PC
I’m going to tweet my activities and progress as I work through the migration process, and then summarize what I record to file Part 2 later this week. But for now, here’s what I see when I poke around on this system:
|AlienWare M11X Hardware Summary (Before)|
|CPU||Intel i7-2617M (1.6 GHz)|
|RAM||2×4 GB DDR3-1333 Samsung|
|Video||Intel 3000 Graphics processor/
Nvidia GeForce GT 540M (2 GB)
|HD||Seagate ST98400423AS 500GB (7200 RPM)|
Hard Disk/OS Summary
|AlienWare M11X Hard Disk/OS Summary (Before)|
|System Drive||40.7 GB Consumed|
|OS||Windows 7 Ultimate x64|
|VSS Space allocated||9.15 GB (2% reserved)|
|Windows folder size||14.9 GB|
|Windows Experience HD||5.7 (Seagate 500GB HD)|
Because I’m going with a nominal 120GB SSD on this machine, I don’t actually have to reduce the drive footprint to get anything to fit. But I’m going through the motions anyway, to report on my findings and get more practice, and also to document the entire migration process along the way. Stay tuned for my next report on this on Wednesday morning.]]>
Microsoft’s UEFI boot sequence diagram from “Building Windows 8″ blog post
The BW8 (Building Windows 8 ) blog struck gold again yesterday (9/22/2011) with a new post entitled “Protecting the pre-OS environment with UEFI,” a discussion of how the Unified Extensible Firmware Interface creates a secure boot environment for PCs modern enough to include this latest-generation collection of “…chipset, hardware, system, firmware, and operating system…” components in their makeup.
I’ve been curious about UEFI for a long time now, having read about it in numerous books, articles, and discussions of PC architecture and BIOS replacement technologies. This blog post goes a long way toward filling in the gaps in my knowledge base, and can probably do the same for you, in explaining what UEFI is, how it works, and how it helps to define a firmware validation process better known as “secure boot.” The big issue is that before the OS loads, older BIOS based systems can be hijacked by malicious boot loader programs that work outside security coverage built into an operating system or antimalware software, simply because this permits malware to take up residence in a system before any of these protective or palliative measures can be brought to bear on the security situation.
The only problem here is that motherboard makers for desktop or notebook PCs have been slow to release UEFI-based systems (MSI demo’ed an X79 motherboard with UEFI at IDF on September 19, 2011; and AMI announced its supportfor the UEFI BIOS at the recent MS BUILD conference on September 15, 2011). I don’t think we’re going to see widespread desktop/notebook support for this technology until 2012, but of course that means Windows 8 will be able to support it–but only on systems new enough to include built-in UEFI. If you ask me this strikes another interesting blow at the notion that “any system that runs Windows 7 can also run Windows 8″ that MS has bruited about from time to time. Given the recent Hyper-V disclosures (which require SLAT support in the processor to run the hypervisor) and now this, it looks like that while older Windows 7 PCs may be able to run Windows 8, they will most assuredly not be able to take advantage of some of its most interesting and advanced features.
To learn more about UEFI, check out the BW8 blog link at the head of this post. You may also want to consult the following resources as well:
“UEFI-Just How Important It Really Is” (Hardwaresecrets.com, 9/21/2011)
“Unified Extensible Firmware Interface” (Wikipedia, references materials dated as recently as 9/20/2011, and includes a great “External Links” section with pointers to other references)
If you have any other space-saving tips for Windows 7 machines, please share them as comments on this blog post. If I get any real doozies, I’ll write them up and give you credit for inspiration, too! Thanks in advance.]]>
Microsoft\’s Virtualization Guy Explains Hyper-V and SLAT
This source is Ben Armstrong’s blog from waaaaaaaaaaaay back in November 2009 entitled “Understanding High-End Video Performance Issues with Hyper-V.” In a very tight nutshell, the upshot of this posting may be summarized as follows:
1. High end graphics cards require frequent and resource-intensive/expensive memory allocations that come from using a PAGE_WRITECOMBINEprotection operation in the hypervisor.
2. This requires the kernel memory manager to flush the translation lookaside buffer and the page cache, which in turn sends an intercept into the hypervisor.
3. Lots of resource intensive hypervisor operations like this turn a (normally) infrequent operation into something frequent enough to hamper or cripple performance. There’s a great diagram in the blog post that shows why a hypervisor falls prey to this limitation, while a virtual machine manager (VMM) like that found in Virtual PC or Virtual Server remains immune to the problem. And interestingly, the faster and more capable the video card in a PC the more likely it is to fall prey to this problem.
One fix mentioned in Armstrong’s blog reads as follows “Get a system with Second Level Address Translation (SLAT).” This lets the hardware handle multiple translation lookaside buffers, on a one-per-VM basis (which is just what’s needed to sidestep the potential performance bottleneck that could otherwise occur). It looks like Microsoft simply opted to avoid potential performance problems from older hardware that might otherwise experience significant delays on the desktop to bypass potential customer complaints. In light of Armstrong’s admonitions to use the SVGA driver, choose a low-end graphics card, or turn off advanced graphics features, I find this decision “interesting” (in the sense of the Chinese curse) but also eminently understandable and defensible. But I still sigh to think of my otherwise very capable quad core Yorkfield processors (QX9650s, in fact) being consigned to the scrap heap of history (or turned into hand-me-downs) because they can’t run Windows 8 Hyper-V.]]>
SIW provides the current details on my notebook graphics situation
At first, I turned up the Verde 280.26 driver (which is what Nvidia still recommends for this chipset on their site) but when I installed it on my machine, Windows 7 presented me with a black screen the next time I rebooted, which immediately told me this graphics driver and my particular configuration weren’t suited to each other. I rebooted again in safe mode using HP’s equivalent of the “press-and-hold F8″ maneuver immediately after BIOS boot complete to get a generic VGA driver that would actually show me something on the screen.
Next, I launched Control Panel, and took advantage of Device Manager’s “Roll Back Driver” button on the Driver tab in the Properties window for the affected device. Luckily for me, this worked like a charm and my system was working again after one more reboot to switch over to the previous driver version.
The Roll Back Driver button can occasionally be a real life-saver
This also got me to thinking about what I would have had to do to get back up and running if there hadn’t been a driver to roll back, or the rollback effort had failed. My quickest fix would be to try the Last Known Good Configuration for the system (another boot option in the F8 menu). Next, I would download a known good working driver to a USB stick, then install that driver in Safe Mode, and try again. I’m pretty sure either one or the other (if not both) of these approaches would restore the unit to proper operation. As it was in my case, I’m pretty sure that none of my meeting colleagues noticed that anything was amiss with my system: it took less than five minutes to set things right.
Eventually I tried the beta 285.27 graphics driver in this machine, and I’m happy to report it’s working just fine. This graphics chipset is something of a wimp, but using MSI Afterburner with the settings turned up as much as I dare, it works OK for me.]]>
[Added 10 AM 9/14/2011] See this Windows 8 Developer Preview Hands-On article from Laptop Magazine for a great overview of the UI, plus new features and functions. A very nice piece of work, but too short on screen caps and illustrations; however, given the speed of its production, I totally understand why this might be the case. Read it to get a pretty good sense of what you’ll find in this Alpha version of the Windows 8 OS.]]>
In attempting to automate the install, the author used a test machine to get the list of necessary files from Driver Details in Device Manager, and also grabbed the related oem*.inf file from the C:\Windows\inf folder to complete the collection of items to attempt an automated and unattended install. Imagine his frustration when this effort produces the following error message:
Windows cannot verify the digital signatures for the drivers required by this device. Error Code 52.
The drivers are in fact signed, and the problem is apparently well-documented all over the Internet for drivers of all kinds. But alas, no easy fix is available, without turning to 3rd party software products to remedy this known Windows defect. I’m sure apexwm isn’t the only Windows admin who would voice his sentiments on this approach “No thanks. I’m not about to start installing a bunch of unknown 3rd party products to try and help with a Windows problem.”
If I were in those shoes, however, I would try to take advantage of Windows’ ability to run post-install scripts after the initial installation process completes (which is how additional common applications such as Office, 7-Zip, FileZilla, and so forth, often occur at the tail end of automated installation processes). It seems to me that if the driver uses an InstallShield .exe file, there should be some way to script or automate its installation as a post-install task.
I do get apexwm’s complaint that Linux/Unix does a much better job of integrating drivers into its kernel directly, and that compilation into the kernel is an option for those few odd drivers that aren’t already included under this umbrella. But I’m a member of the “where there’s a will, there’s also a way” club of Windows-heads and suggest that he needn’t have given up in defeat.]]>
All told I was able to reduce system disk size by at least 5 GB on each system where I tried to use two or more of these techniques. In one case, the savings was over 10 GB where I was able to reduce drivers, compact PSTs, and move the Windows XP VHD to my F: drive. I like it! Got any similar tips to share? Please do, and I’ll write them up if I can put them to work, too.
Here’s a concluding recommendation: try out the free WinDirStat graphical file system display utility. It will show you which files on your drives are the biggest, and point you at the fattest (if not most vulnerable) targets for cleanup. That’s what got me started down the cleanup road I document in the various aforecited blogs.]]>
Headline for Ed Bott’s 9/2/2011 blog
Apparently the appearance of this function in the Building Windows 8 blog earlier this week caused a tempest in a teapot with some readers, who went off on the continued existence of the function in the Windows Explorer of the future (not to mention the Windows 7 present as well). Pet peeves aside, it turns out that “Invert Selection” is a very nice little function, once you understand what it does. Basically, you can pick a list of things you want to keep unchanged in a folder (especially if it’s shorter than the list of things you want to move, delete, or modify), then use “Invert Selection” to de-select those items and select everything else instead.
For example, let’s say you’ve got a folder full of photos that you grabbed from your digital camera. After reviewing 75 snaps, you decide you only want to keep 5. So you pick them, then do ‘Invert Selection,’ then right click any of those entries, and pick “Delete” from the pop-up menu. Presto! All 70 unwanted photos are gone, gone, gone. Easy as pie!
In Windows 7 run Explorer (type
explorer.exe into the Start menu search bar, or click your favorite icon: I usually use the Folder icon that’s pinned to the Task bar at the bottom left of the screen to launch Explorer myself). Then click the Alt key to show the ordinarily hidden “File Edit View Tools Help” menu bar. The Invert Selection item appears at the bottom of the pull-down menu for the Edit entry in this menu bar. And it works like a champ, too.