OK, so it doesn’t take a rocket scientist to understand that MS has to do something to boost Surface Pro battery life, not only to establish parity with other emerging Windows 8 tablets, but also to help level the playing field with ARM-based Apple and Android tablets, too. That’s what makes this morning’s iTechPost story “Microsoft Surface Pro 2: Top features Intel’s new Haswell processor brings to the table” particularly interesting.
A peek inside the Surface Pro from the 2/13/2013 LifeOnMyMobile story “Take a Look at the Microsoft Surface Pro from the Inside” (photos from the iFixIt teardown).
Here are some of the items from that story, prompted no doubt by some opening Haswell shots in what should become a fusillade at Computex in Taipei this week:
- The Verge gets attribution for the claim that “…the Haswell processor is expected to boost battery life by an extra three hours.” That takes the normal range from 4-5 hours and extends it to 7-8 hours, nearly enough for a day’s worth of untethered computing. That’s certainly getting closer to what most professional users want — including me.
- Haswell chips are smaller than their predecessors which iTechPost says “…could mean we’ll be seeing an array of even thinner tablets,” while also observing that thinner probably also means smaller batteries, invoking a by-now classic engineering trade-off.
- Increased processing power should bring more oomph to Haswell graphics, and faster boot times for Haswell-based tablets.
What I’m really curious about is if MS will take the plunge into a removable battery, so users can elect to purchase extras and carry them around to extend battery life beyond whatever limits the combination of form factor, battery size, and power consumption the new Haswell-based units will afford. I’d also love to get some reliable information on when the next generation of Surface Pro units is likely to ship, so I can start saving my pennies and planning to buy one. Some publications, such as TechThirsty, speculate that the next-gen Surface Pro release may be tied to the upcoming Windows 8.1 release. If so, that means it may be available around the end of October 2013. On the other hand, TechRadar speculates that the Surface 2 could be released as early as June at Microsoft’s Build Developer Conference. TechRadar’s story also presents some interesting snippets form a Reddit AMA (Ask Me Anything) session that includes disclosures that the next Surface Pro will support an interface to accommodate an external battery link up (via the current “accessory spine” jack used to accommodate a snap-on keyboard at present), and some suggestion that the next edition will be better at accommodating external screens at various (and different) display resolutions.
Very interesting. I’m not at all sure that my “wish list” from November, 2012, will be satisfied in one go from MS with the Surface Pro 2. Nevertheless, it sounds like the next version should tick off a few checkmarks in some categories, and make significant progress in others. I’m hopeful that as we learn more about what’s coming, we’ll also like what emerges even more than what’s shaping up from the current crop of rumors, speculations, and educated guesses.
Well, well, well. It’s been forever since the worm turned and AMD got a leg up on Intel–almost seven years, in fact, since the introduction of Intel’s Core family of processors whipped the daylights out of AMD and gave them the undisputed processor crown they’ve worn exclusively ever since then. But according to recent reports (see for example this PCWorld story from Michael Brown “AMD reveals next-gen mobile CPUs, claims unprecedented graphics performance“) that balance might soon tip the other way — at least, where mobile processors are concerned. That being the only remaining growth vector in the non-server PC market, especially for tablets and ultrabooks, that’s no small thing.
This caption from the AMD product announcement PPT deck states an interesting value proposition.
The new processors coming later this year are currently code-named “Temash,” “Kabini,” and “Richland,” and the claim is that these new architectures combine x86 compatible CPUs with the latest generation of AMD Radeon processors to offer serious graphics oomph along with extended battery life — a combination that represents an important sweet spot for touchscreen devices, particularly tablets. The Temash models for example, are numbered A4-1200 (2 cores, 3.9W TDP), A4-1250 (2 cores, 8W TDP), and A6-1450 (4 cores, 8W TDP) and correspond respectively to AMD Radeon HD 8180, HD 8210, and HD8250 GPUs. Kabini CPUs comes in both A and B series, with two 4-core A-series models (A6-5200 @ 25W TDP and HD8400 GPU, AB-5000 @15W TDP and HD8330 GPs), and three 2-core B-series models (E2-3000 @15W TDP and HD8280 GPU, E1-2500 @15W TDP and HD8240 GPU, E1-2100 @ 9W TDP with HD 8210 GPU). Richland CPUs come in 7 models, 3 A-Series at 35W TDPs, and 4-Aseries with low voltage (25 and 19W) and ultra-low voltage (17W) TDPs. Corresponding GPU models run from HD8650G at the top end (384 cores, 720 MHz) all the way down to HD8310G (128 cores, 554 MHz) at the bottom of the ULV end.
According to the PCWorld story, even though AMD itself hasn’t announced any design wins based on these new CPUs just yet, MSI has already indicated a refresh of its gaming notebooks will include AMD’s AMD10-5750M mobile Richland CPUs. The conclusion of the story also makes an important point that Intel is sure to chew on incessantly, as it plans its upcoming Haswell roll-outs “If AMD can usher in an era of very inexpensive, but highly capable tablets and notebooks, the company will have a success on its hands.” Could it be that the killer Windows 8 tablet deal will come from an unexpected quarter, and not only help to restore AMD’s flagging fortunes, but Microsoft’s as well? Only time (and lots of competitive benchmarks) will tell. In the meantime, keep your fingers crossed: increased competition in this market can only be good for the consumers of such technology!
Over at PC World, Mark Hachman reports on a terrific bit of Windows 8.1 (Microsoft’s now-official name for the next upcoming Windows desktop release, preview due out on later this month) code analysis work. It’s by Justin Angel and is entitled “Pre-beta Windows 8.1 WinRT Developer APIs,” an innocuous sounding name that hides a treasure trove of useful information and suggestive hints about what lies ahead in Windows-land.
Wow! The new, more frequent point release approach to Windows makes for a lot more change and update to keep track of…
Angel explains his forensic approach as follows: Because Windows 8.1 image files include WinMD files that describe embedded Windows 8.1 APIs, tools can extract those WinMD files and compare them to their plain vanilla Windows 8 counterparts. Angel used a tool called Reflection to tease out the differences between the two versions. Here’s how he describes his methodology verbatim:
- Download the latest Windows 8.1 “leaked” image. This article was based on an image named “9385.0.FBL_PARTNER_OUT17.130415-2049_X86FRE_CLIENT_EN-US-PL-PL-RU-RU.ISO”.
- Create a bootable USB drive from the ISO file and Install it on a nearby machine.
- Win8.1’s WinMD files can be found under the following directory: C:\Windows\System32\WinMetadata
- Using Microsoft’s Framework Design Studio it’s then possible to compare the WinMD files from a WIndows 8.1 “leaked” image and Windows 8 RTM.
Following this approach, Angel was able to extract all kinds of information: it’s summarized in a 28-item “Table of Contents” in his article, and includes a whole raft of interesting revelations. To begin with he discovers support for the two major Bluetooth protocols in 8.1 — namely RfComm and GATT (the latter is key to supporting the latest generation of ultra-low energy BT devices). Some of the API calls indicate this could incorporate such devices as heart rate monitors, thermometers, glucose detectors, pedometers, proximity sensors, and more. Next up: barcode scanners and magnetic card readers, indicating a drive toward cash register apps for point of sale use. Likewise, there’s increased support for smart cards and pin code authorization techniques. Other highly interesting elements also include VPN support for Modern UI/Metro apps, supplementation of printer support already in Windows 8 with equivalent scanner support, ability to recognize and access arbitrary USB devices, PDF rendering services for apps, multiple screen handling for apps (PC screen only, duplicate, extend, and second screen only, just like on full-blown Windows 8), interesting new resolution scaling support for displays and support for resolutions up to 4K ultraHD displays, text-to-speech services for apps, and a whole bunch more.
If you’re curious, the original article is definitely worth reading. Sounds like there’ll be interesting additions to RT for Windows 8.1, and it’s inevitable that some or all of these new capabilities will also appear in the full-blown 8.1 version as well. Veeeeeeeeeeeery interesting!
Call them “Windows Store apps,” “Modern UI apps,” or even “Metro apps,” the latest monthly report from Soluto reveals that these apps don’t figure much into how actual users employ their Windows 8 PCs day-in and day-out. The company’s sample drew from 10,848 Windows 8 machines, and included over 313 thousand Metro app launches among a population of 9,634 different Metro apps. The results are a bit surprising, and may in fact be somewhat daunting for Microsoft for all kinds of reasons. Here’s an overview of what this report lays out:
The presence of touch and the use of tablets profoundly affect frequency of Metro app usage, but all usage levels are pretty low.
- The average Windows 8 user launched just 1.52 Metro apps on a daily basis. As you’d expect that number varies from a high of 2.71 daily launches for tablet users to a low of 1.41 daily launches for desktop users. Laptop users average 1.51, and touch laptop users 2.22.
A significant sector of the user population launches Metro apps less than once a day; again, tablet and touch figure in to some degree.
- Among desktop and laptop users who lack touch screens, 60% of them launch a Metro app less than once a day. Even tablet users don’t use Metro apps daily — in fact, 44% of them also launch a Metro app less than once a day.
- There’s also a very interesting list of the Top 20 Metro apps by frequency of use in the Soluto report, which shows that images, PDFs, and entertainment figure heavily into the apps that Windows 8 users actually access (the “Windows Communications Apps” or WCA is a portmanteau that includes Mail, People, Messaging, and Calendar, and it comes in on top). The most interesting observation here is that even in the top 20, only the top 3 (WCA, Windows Photos, and Microsoft Reader) are accessed once a week or more; the remaining 17 items are all accessed 0.71 times per week or less.
- Soluto also provides a measure of what they call “the most engaging apps” — by which they mean how often individuals who use a certain Metro app return back to it each week. By this measure, Yahoo! Mail comes out on top (with 26.91 average uses per week), followed by Social Jogger (Cyberlink: 25.98) and Social Networks (Cyberlink: 21.19). For number 4, Lync MX, the frequency drops to 4.4, WCA is number 3 at 3.21, and the remaining 10 items all fall at 2.13 times per week or less (item 15, iStunt2 registers at 1.43 times per week). Interestingly, items 2 and 3 are Acer apps for social networking, including Facebook and Twitter access.
To me, the overwhelming impact of this study is that Windows 8 isn’t being used very much at all in the way that Microsoft would like us to use it — namely, running Tile-based applications through the Modern UI interface. No wonder Windows 8 RT has tanked so badly: that’s pretty much the only interaction paradigm that this particular Windows 8 version supports. This also helps me to understand why Microsoft is back-pedaling in the upcoming “Blue” release with the return of the Start button and the ability to boot straight to the desktop. Microsoft collects Windows 8 telemetry, too, and their results can’t be all that different from Soluto’s. What is different, and useful, is that Soluto is sharing this information with the world. What will be more interesting to watch is to see if Modern UI app usage trends up over time…
As I mentioned in my last blog post, I’ve been setting up and breaking in a new touch-screen convertible tablet/ultrabook Dell PC recently. Last Thursday and Friday, in fact, I found myself in a seemingly insoluble dilemma that began to assume Kafka-esque proportions as I noodled through far too many attempts to fix my problem before I finally came up with a workable solution. The cause of the problem was laughable, and surely a result of my less-than-perfect eyesight, because when I set up my initial login, I tied it to my Microsoft Live account — which starts with the string “etittel”– but because the 1980×1020 resolution on the XPS12 turns out truly tiny letters in the input box (and subsequent displays) I didn’t figure out until much, much too late that I’d misspelled that string by adding an extra “t” in the middle, making it “etitttel” instead of “etittel!” It wasn’t until I turned on remote access and started working with the UI on a 27″ screen (with 1980×1200 resolution) that I could actually see that I was the author of my own misery.
The initial symptom was that Microsoft kept asking me to verify the account through its associated email address, and I kept seeing no email to verify (because my email address, of course has only two “t”s in the middle, not three). When at last I figured out my error, I then found myself flailing about to try to get rid of the erroneous login account, and to replace it with the proper one. It took repeated trials before I realized that I had to follow a routine that’s familiar to any programmer who wants to replace one programming variable with another without losing the variable’s contents:
1. First, I had to create a second account with the properly-spelled Microsoft Live email address.
2. I then had to verify that account with Microsoft (completely dead simple, once there was an email inbox to receive the confirmation message)
3. I had to set the privileges for the new account to Administrator equivalent, and completely log out of the bogus three-t account
4. Only then could I successfully delete the account with its hilariously misspelled name
I bought this little widget to speed big downloads, but it helped me switch from a misspelled Windows Live login to its properly-spelled counterpart.
And along the way, I learned something very interesting about Windows 8’s startup behavior. Apparently, it only loads wireless network drivers after a successful login. And because the initial login for the correct account name needed to be verified for the first login to complete, I couldn’t make it work until I attached my StarTech USB3-to-GbE network interface to the new machine. It verified just fine through a wired Ethernet connection, after stubbornly refusing to do so wireless through half a dozen tries (even if I had a working wireless connection going through a parallel and simultaneous login through the other account). It really is always something, when it comes to Windows!
I’m working with some staff at Dell, and with a loaner XPS12 convertible tablet/ultrabook running Windows 8, to explore ways to boost the usability and productivity gains (both personal and professional) that access to such nice gear can deliver.
The XPS12 is compact, and the screen flips inside the outer bezel to switch between ultrabook and tablet mode.
Just recently, having taken possession of the machine about two weeks ago, I’ve been slowly but surely getting the machine’s drivers and OS updated, adding my usual software toolkit, and exploring more and better ways to work with this system. In today’s blog, I’d like to report on some of my experiences so far, including:
(a) Driver-related issues and discoveries
(b) A laundry list of software elements I’ve found it necessary or useful to add to the system
(c) What’s been involved in getting backup working, and creating recovery media
Driver Issues and Discoveries
While I have been able to access drivers pretty handily through the Dell support pages, what I really want from them is a driver scanner to examine what’s on my system and then to tell me what I need to download and install (even better would be an automated facility that would march through the download list and install all of them for me). In theory, that’s what the Dell Support Driver & Downloads page is supposed to deliver. But although I could get it to tell me what I might need by way of driver files both quickly and easily, the Dell Driver Analyze Utility didn’t tell me what was up-to-date and what wasn’t on my machine.
So, I turned next to my old stalwart maintenance tool, eSupport’s DriverAgent driver scanning tool. It initially reported that 15 drivers were out of date, at least half of which were related to the Intel Chipset drivers. As somewhat of an old hand at this game, I downloaded the 220.127.116.114 chipset utility, and extracted its contents to a folder on my 64 GB Mushkin USB3 flash drive (UFD), which proved itself amazingly speedy at handling read/write activities (it’s faster than a conventional external hard disk, in a reversal of the performance ranking when attaching via USB2 instead). I went into Device Manager and manually updated the various Intel devices that DriverAgent labeled as out of date, which knocked off 8 of the offending entries in the list. I had to use the Intel Driver Update utility to find and grab the latest Centrino wireless and PROSet drivers, and upon continuing difficulty in finding the latest AHCI SATA driver for the unit’s SSD, turned to the most recent Intel RST driver (18.104.22.1686 with a 3/18/13 release date) to finally clear that up. I also had to update the audio drivers, the driver for my USB3 Ethernet adapter (which saved my butt on one very interesting issue I’ll elaborate on later), and the Intel Dynamic Platform and Thermal Framework.
Total time invested in picking up where Microsoft Update left off to get things as up-to-date as I could make them (I wound up with two drivers still out of date: one for something I’ll never use, and another for a motherboard resource related to the Intel Thermal Framework) was between three and four hours, which is pretty representative of my usual post-install (or post-unboxing) experience on a Windows 8 laptop (I’ve been through this exercise on perhaps a dozen different such installs at this point).
The New Software Laundry List
In bringing the XPS12 up to what I consider production-ready status, here’s what I’ve installed on that machine so far, above and beyond what it included upon its arrival:
- Piriform’s CCleaner (free version), which I use to clean up dross on the system’s drives and for light-duty registry sweeping
- Google Chrome, which I often prefer to IE, especially when digging into HTML or CSS markup on Web pages, as I must often do
- Windows DriverStore Explorer [RAPR], a free (codeplex) utility that lets you examine and prune older entries from the Windows Driver Store — never a bad idea after updating lots of sometimes-large drivers on a Windows PC
- Image Resizer Powertoy, a (free) codeplex shell extension to Windows Explorer that lets you resize images in PNG, JPG, or GIF format from a right-click inside Explorer.
- RecImg Manager, which puts a Modern UI face on the terrific built-in recimg command line utility used to create a custom Windows image (.wim) file for the Refresh your PC utility that’s new to Windows 8 [Note: you can’t target a UFD for a recovery image using this utility because Windows won’t let you; if you try, you’ll get a mysterious and not terribly informative error message that only indicates that the backup failed but doesn’t tell you this is why.]
- SIW Pro (a free version is also available), Gabe Topala’s superb system profiling tool for Windows PCs
- Start8, which is the best of the various “Start button replacement programs” available for Windows 8 (and at $5, cheap enough to buy for all your machines)
- WinDirStat, a (free) sourceforge project that provides a comprehensive view of what’s on your disk drives (very handy for keeping track of scarce and valuable SSD storage space)
- 7-Zip, my favorite — and free — compression/decompression tool, which is also peachy at unpacking drivers from many .exe or .msi driver installer files that don’t update my drivers properly, but which do contain drivers installable through Device Manager (if only you can get at them, which this tool does nicely more often than not)
As I look at my other production machines, I see a few more items in my near-term “to-add list” for software on this machine, including MS Office 2013 (which helps me make my living), FileZilla (still my favorite FTP utility), Secunia PSI (a terrific security status checker for the OS and applications), Notepad++ (an outstanding programmer’s file editor), Revo Uninstaller (even the freeware version beats the built-in Programs and Features utility in Control Panel hands down), and Unlocker (a handy-dandy file unlocking tool when you want to delete a file and Windows won’t let you do it).
Making Backup and Recovery Work Like They Should
I found myself entangled in some issues on the XPS12 related to backup and recovery that puzzled me a bit. I like to use the Windows 7 File Recovery utility in Control Panel, which still runs much like the old ntbackup.exe that goes all the way back to Windows NT 3.5 or thereabouts, because it makes an eminently usable image backup that’s peachy for restoring entire drives (often my preferred method of recovery anyway). Unfortunately, the tool kept failing about 35% of the way into the system drive with error codes 0x81000033 and 0x81000017. A little research showed me that one of three things could be at fault, and by process of elimination, I determined that Dell’s default installation of McAfee Security was the culprit. Upon uninstalling that program, I’ve had no difficulties backing up or restoring since using the built-in Windows utility.
I also like to use RecImg Manager (from Slimware Utilities) to create image backups in the form of .WIM files for my systems, because this then lets me use Windows 8’s “Refresh Your PC” repair tool to restore an image that has all the up-to-date drivers, patches, and apps I want on my machine, instead of rolling all the way back to a factory-fresh image and having to rebuild from there. I’ve done that on this machine not only because it’s a good idea to do so, but also because I took a “before” snapshot to which I’ll want to roll back if I ever want to try a different approach to bringing my system back up to snuff.
More to Come…
This is just the beginning of my continuing adventures with this machine, and with figuring out how to make more and better use of a lightweight convertible tablet PC running Windows 8. I have at least one more interesting adventure to related based on recent experience — which I’ll cover in another blog — and will also be reporting on some upcoming developments at Dell to improve their support and value-add offerings for these PCs. Stay tuned!
For the past year, I’ve had the pleasure of knowing that my son’s 3rd grade class had the use of two extra laptops I had laying around unused for daily use in surfing the web, taking reading tests, visiting math and science resources online, and more. This prompted a story I wrote for EdTech Magazine that bears more or less the same title as this blog does (expect to see it showing up online sometime in July or August, I’d guess).
EDTech Focus on K-12 provides information, news, and resources of interest to K-12 teachers, school administrators, and interested parents.
The ultimate points of the story rest on two assertions:
1. Most classrooms have only one or two PCs at their disposal, and anywhere from 15 to 30 kids to share them.
2. More computers at kids’ disposal means more opportunities for learning and study.
I’d urge families and small businesses with surplus PCs to loan to schools to consider doing just that to help classrooms out with additional computing resources. Computers for classroom use don’t need to be new, powerful, or support lots of storage. Nearly all the applications that are used run through a Web interface, so it’s not out of line to view such machines more as a kind of thin client rather than as a full-fledged standalone computer. There is one essential element for such use however — namely, wireless networking. Nearly all school campuses now support guest networks running on 802.11g or 802.11n, so any loaner PC must be able to access such wireless networks (this won’t be an issue for most laptops, which routinely come equipped with wireless; but it may require purchase of a $15-20 USB wireless interface for desktops that typically lack wireless connections built-in).
Prepping a machine for classroom use requires system clean-up, and I’d recommend replacing hard disks to avoid the possibility that any data that ever resided on those drives might be sniffed out thanks to ever-more sophisticated data recovery tools for deleted files that once resided upon them. You’ll find the complete details required to do the prep work in my upcoming EDTech K-12 article, where you’ll also learn that those who loan their equipment should also be prepared to donate some time for the upkeep (and occasional tech support) of those machines throughout the school year. But it’s definitely worth it, to help our students make the most of their schooling.
The upcoming release of Windows 8, formerly known as Windows Blue, is now (drum roll, please) called Windows 8.1.
Windows 8.1 will be delivered as a free update to Windows 8 and Windows RT and it will be accessible from the Windows Start Screen through the App store, said Tami Reller, Microsoft’s Windows division Chief Financial Officer said during the J.P. Morgan Global Technology, Media, & Telecom Conference in Boston today. Enterprise customers will have the option of how often and when they deliver the Windows 8.1 update to their end users, she explained.
Microsoft, which has already delivered 739 updates, will preview Windows 8.1 at the Microsoft Build Conference on June 26 in San Francisco, Reller said.
Customers who want to purchase a Windows 8 device today can upgrade their devices for free when the software is available, she said.
Companies have been slow to adopt Windows 8 so far. Although many businesses wait for the first update of an OS before doing an upgrade, Windows 8.1 probably won’t make a huge impact on enterprise plans. The Windows 8 learning curve and additional cost for touch screen devices makes it a hard proposition to upgrade all users to the new operating system at this time.
Reller noted two thirds of enterprise desktops today deploy Windows 7. Microsoft recommends that enterprises continue on the Windows 7 deployment path, evaluate the Windows 8 tablets and other new device types coming out, and look at the line of business applications, she said.
Asked about the next version of Surface and what future products would look like, Reller smoothly deflected the question to talk about the generalities of touch-based convertibles and detachable products. Reller also reiterated support for Windows 8-based 7- and 8-inch tablets without spilling the beans on what those devices might actually include.
With Microsoft executives dribbling out Windows news at every conference, I’ll be interested to hear what’s next on the agenda.
Lately, there’s been lots of interpretation and speculation swirling about the general topic of Windows “Blue” (aka Windows 8.1, scheduled for release to the world sometime before the end of 2013). The best take on this emerging phenomenon so far comes from ZDnet, in Mary Jo Foley’s occasionally brilliant and always interest All About Microsoft blog. Entitled “With Windows Blue, Microsoft may (finally) do the right thing,” it talks about what’s driving Microsoft’s recently discovered intentions — thanks to leaks and analyses of Windows “Blue” builds of late — to provide what MJF calls “an optional Start Button” and “boot-to-desktop capability.”
In light of MJF’s discussions and disclosures, the co-mingling of Windows 7 and 8 visual elements actually makes a perverse kind of sense.
In addition to these widely reported updates planned for Blue, MJF also calls on unidentified “tipsters” to report some additional UI tweaks potentially in the offing:
- changes to the Charms designed to make them more mouse-friendly
- changes to the Start screen specifically aimed at desktop users (presumably, only with mouse and keyboard at their disposal)
- new tutorials and context-sensitive help information to help newbies make better sense of Blue than they’ve apparently been able to make of the current Windows 8 release
Her take is that this might just be enough to move experienced users off of Windows 7 and into Windows 8, including her own production gear, given the reduction in learning curve and ease of use such changes would entail. I’ve already learned on my own 5 Windows 8 systems that by installing either Start8 or Classic Shell you can bypass most of the “UI friction” experienced users grouse about, and in so doing, have observed that Windows 8 is modestly faster, more compact, and quite stable in everyday test and production use.
My favorite part of this occurs when she quotes former Windows division president Steven Sinofsky’s “damned if we do; damned if we don’t” blog post (the actual title is “disrupt or die“) wherein he quite rightly observes that MS has no choice but to push the envelope on touch and tablet features in Windows versions from here on out. If they don’t do, somebody else will — and they’ lose market share; and if they do do it (or perhaps it’s appropriate to say “when they do it” at this point, what with Windows 8 out for 7 months-plus now), they’re going to disgruntle users who don’t want to deal with change, or who don’t like their changes or design ethos. There’s actually some of all of those things in what’s been happening with Windows 8 and its market reception and analysis since the consumer preview starting circulating in February 2012, and it doesn’t appear to have any end in sight.
The key point here is that Microsoft had to do something, and that is what they did. With the next version (“Blue”) they can make some corrections, but it’s not going to change either Microsoft’s or the technology world’s migration path from static, non-touch, deskbound devices to mobile, touch, hand-held and portable ones. Please check out the original article, and ponder its conclusion: “I believe Microsoft can stay its Metro-centric, touch-centric course with Windows Blue, while still making some changes that will make the OS more usable and comfortable for a bigger pool of users. While it would have been great if Windows 8 debuted this way last October, I say better late than never.” Amen and indeed, I say in reply. Good work, MJF!
Just saw a very interesting bit of “build detective work,” by Rafael Rivera over at the Within Windows blog. It’s entitled “Windows 8.1, PowerShell 4.0, and new cmdlets.” For those not already in the know, cmdlets are PowerShell scripts, usually designed to lift the burden of repetitive maintenance, configuration, and management tasks for Windows admins. Rivera takes the time to list out all of the new cmdlets he finds in the recently-leaked Build 9374 of Windows 8.1 aka “Windows Blue.” This makes for very interesting reading, so I’m going to reproduce them in tabular format here, and then comment on what I see afterwards.
|Windows 8.1 “Blue” Cmdlets By Category|
|VPN Configuration||Windows Defender||Start Screen|
|Get-KioskLockdown||Add-NetNatExternalAddress||Trusted Platform Module (TPM)|
|Set-StorageTier||Systems Mgmt Bus (SMB)||Start-PCSVDevice|
Here’s some more information and speculation on the categories and their applets, from left to right and top to bottom in order of appearance:
- VPN Configuration: a great many more cmdlets for managing Virtual Private Network connections, triggers, routes, and DNS make an appearance
- Windows Defender: make it possible to automate management of Windows Defender across an entire Windows network
- Start Screen: provide the ability to customize the Windows 8 Start screen
- DISM has been at odds with PowerShell syntax in the past; these cmdlets hide the differences inside standard structure and syntax
- Kiosk: enables setting up Windows 8 to run a single application (for a museum, store, or special-purpose kiosk PC)
- NAT management: enable automated handling for Network Address Translation elements in the Windows Routing and Remote Access (RRAS) infrastructure found in Windows Server
- Trusted Platform Module (TPM): provides access to important TPM info without having to work through a TPM API or access the TPM Management Console
- TCP/IP: a “net compartment” is new terminology, so we’ll have to wait and see what this means/is for
- Windows Management Instrumentation (WMI): manages information in WMI schemas and instances
- Systems Management: provides access to the new Physical Computer System View (PCSV) information to be found in next-generation Windows systems in the enterprise
- Storage: management for storage roles in Windows Server “Blue”, interacts with Storage Pools on both clients and servers
- Volume: miscellaneous volume management utilities
- SMB: something inside which to wrap the Systems Management Bus APIs from Microsoft
- Printer: these items reference NFC (“near field communications”) so Rivera speculates — and I agree — that this is an intimation of support for NFC printers, possibly for asset management or tracking
In his story Rivera includes a screen capture from the Registry Editor that clearly shows a new PowerShell 4.0 version reported in Windows 8.1 “Blue,” indicating another version change is pending. It will be interesting to see what new language changes and features this brings to the table. I’m going to contact some of my PowerShell buddies and see if they can give me a preview of coming attractions. More information on that as and when it comes my way!