Before I cover what Mr. Nielsen has to say about Windows 8, let me explain a little about who Jakob Nielsen is. A former Sun Distinguished Engineer (back in the days when that really meant something), Nielsen is also the author of numerous influential and widely-read books on Web design and Web usability, most notably: Designing Web Usability: The Practice of Simplicity. I’ve read this 1999 book at least four times — the last time in 2011, while revising my HTML For Dummies into its 13th edition overall, and every time I read it, I get more and more useful or indispensable information out of its contents.
According to Reisinger, “Nielsen says that the new Windows 8 users interface ‘smothers usability with big colorful tiles while hiding needed features.'” To come to this summation, Nielsen assembled one dozen experienced PC users to take Windows 8 for test spins, both on conventional desktops and on the new Microsoft Surface PCs (Windows 8 RT models, those being the only kind publicly available at this time). Users noticed a dual-nature to the Windows 8 OS, where the tablet- and touch-focused Start screen and Windows Store UI contrasted greatly with a traditional PC-oriented desktop interface. One problem for users, according to Nielsen, is that differing design concepts require users to “remember where to go for which features.” Another problem is that the dual focus creates an “inconsistent user experience.” Net result: reduced usability overall. Inside the Windows Store UI, Nielsen found its lack of multiple window support to be “one of the worst aspects of Windows 8 for power users.”
As other power users and experts have also concluded, Reisinger’s story also states that “…Nielsen believes that Microsoft has focused on tablets with Windows 8 to the detriment of PCs.” Furthermore, Nielsen is quoted as saying that Windows 8 is “weak on tablets” but that it is “terrible for PCs,” where “on a regular PC, Windows 8 is Mr. Hyde: a monster that terrorizes poor office workers and strangles their productivity.”
Ouch! In closing, however, Nielsen holds out some hope for the future saying that “Windows 7 is a good product and … Windows 8 is a misguided one.” His plans probably echo that of many other readers, especially those using Windows in the enterprise: “I’ll stay with Win7 the next few years and hope for better times with Windows 9. One great thing about Microsoft is that they do have a history of correcting their mistakes.” Let’s hope further that Mr. Nielsen is correct!
Over at Forbes, David K. Johnson has just released a very interesting article entitled “Seven Reasons Windows 8 Adoption in the Enterprise Is at Risk.” The story poses some potentially noteworthy observations to suggest that, for at least the next year, widespread Windows 8 adoptions in the enterprise are unlikely at best:
1. Most IT shops are still in the midst of their Windows XP to 7 migration: True enough, and with a 3 to 5 year life cycle for most desktops, enterprises will want to work their way through that cycle before starting another one.
2. Windows 8 makes strides in security and manageability, but Windows 7 is good enough for most: True again, with UEFI and secure boot, an improved BitLocker, and even Dynamic Access control as tempting inducements to move to Windows 8, none of these makes a killer argument that waiting is a mistake. At present, perceived value of the upgrade comes nowhere close to matching time and effort involved in making wholesale desktop migration work.
3. The New Windows interface is a major change that carries added support risk for I&O. Certainly, the new UI paradigm has been the focus of so much ranting and raving that there’s no need to question or belabor this point.
4. Confusion between Windows RT and Windows 8. With the ARM-only RT out there alongside the x86 full-blown Windows 8 version, RT poses a potential trap for buyers, especially those who — like most enterprise workers — expect access to a desktop for legacy and conventional applications in addition to Windows Store apps. This could blow up for those not careful enough to distinguish Windows RT from Windows 8.
5. Limited availability of apps in the Windows App Store. Johnson cites the numbers game that so many analysts have discussed: an almost 30-to-1 ratio for Apple Store vs. Microsoft Store apps (only 4K for RT, in fact) with over 700K apps for Android (70-to-1 vis-a-vis the MS Store). Until MS achieves critical mass — on which point Johnson cites Frank Gillett to observe this could take a year or longer — there isn’t enough “stuff” available for the Windows Store UI to spur adoption and deployment.
6. Comparatively high Windows 8 resource requirements for tablets. The cost and features requirements for Windows 8 tablets that can run full-blown applications comes at a serious cost, weight, and resource disadvantage as compared to iOS or Android alternatives. A medium-range iPad is available for just over $600, and Android tablets run from $400 to 800; a reasonable x86-based Surface tablet is hard to buy for under $1,000, and it’s easy to spend $1,300 to $1,500 for a fully tricked-out model.
7. Fragmented OEM hardware ecosystem. Too many choices, where many OEMs also pander to consumer desires to get “just good enough” capability at the lowest possible price. Without strong enterprise demand, there’s no inducement for OEMs to start building truly “business-class” tablets and convertibles with an emphasis on reliability and durability. This will probably change over time, but Davidson is right to opine that it’s much likely to happen later, rather than sooner.
All in all, I think Johnson does an excellent job of summing up the key arguments. Certainly what’s scariest for lots of enterprises is the paradigm shift in the UI, and the attendant learning curve for users (and support staff) that has to be climbed to make investments in the new OS worthwhile. But with most enterprises lagging 18-36 months behind public release to complete wholesale migration, I think the only potential error in his story is the one year timeframe he imposes on himself. I think he’s right, and likely to stay that way for some time longer than that — another six to 24 months, if the typical time-table for enterprise adoptions for the last four or five major Windows versions (NT, 2000, XP, and Windows 7 — add in Vista if you like, but it never got much traction) also holds true for Windows 8. So far, I see no reasons why it shouldn’t.
I’ve been working with Windows 8 for nearly one year now, and am slowly but surely moving into the mindset needed for the new OS’s take on desktop and tablet computing. I’ve been lucky enough to work with a Lenovo X220 Tablet with Windows 8 since last March (or just over 8 months now) and have learned alot about what makes for a positive tablet computing experience, thanks as much to my ownership of an iPad 2 as to my interaction with Windows 8 in a tablet (or touchscreen notebook) PC setting. I’ve also been reading lots of reviews of new Windows 8 tablet offerings including the MS Surface PC, the Kupa Ultranote, and most recently the Lenovo Yoga 13 convertible “ultrabook” unit.
In working daily with the Lenovo X220 Tablet, and playing with the MS Surface and the Samsung ATIV at the Microsoft Store, plus a brief groping session yesterday with my friend’s brand-new Yoga 13, I’ve formulated a “wish list” for features that I wish were commonplace for all Windows 8 tablets, with ratings for these various units for each such feature.
|Ed’s Wish List for Windows 8 Tablet PCs|
|Feature||X220 Tablet||MS Surface||Yoga 13||Samsung ATIV 700T|
|Lightweight||Not really (4.2 lbs)||Yes (1.5 lbs RT; Win8Pro TBD)||Close (3.4 lbs)||Yes (1.89 lbs)|
|Easy keyboarding||Yes||Yes (with cover)||Yes||Yes (add-on unit)|
|Enough power||Yes||RT model lacking; Win8Pro probably||Yes||Yes|
|Usable desktop||Yes||Only for Win 8 Pro models||Yes||Yes|
|Usable touch||Almost (2 tp)||Yes (10 tp for all models)||Yes (10 tp)||Yes (10 tp)|
The tp in the usable touch row stands for “touchpoints,” as in the number of simultaneous touches the display can sense at any given moment. The minimum Win8 requirement is 5, and all of the new tablets meet or exceed this requirement. My biggest concern is for weight, which really translates into usability in the hand. Even my iPad 2 at 1.625 pounds gets too heavy after a while (which, incidentally, helps explain the potential appeal of the iPad mini and other 7″ tablets), and all of these units are no lighter than that and both of the Lenovo models are significantly heavier (as I guess convertibles must be). The Lenovo keyboards are legendary and quite usable, even on the smaller layouts for these two units; the MS Surface Touch Cover is pretty minimal but surprisingly usable where the Type Cover is a good keyboard in keeping with other MS keyboard offerings; the Samsung keyboard isn’t bad, but its layout takes some getting used to. When it comes to computing horsepower, the bigger Lenovo units offer a great deal more capability (mobile but not ultra-low voltage i5 and i7 models are available), where the slim design of the true MS Surface and Samsung ATIV tablets require lighter-weight CPUs to keep weight and battery requirements manageable. Business users still have to be able to switch between the Modern style (formerly Metro) UI and the desktop to run business applications, so it’s really not yet an option to eschew the desktop entirely. This is the area where the Lenovo units jump ahead of their more svelte but perforce also more limited MS and Samsung counterparts. All the modern units do touch quite well (and even the X220 Tablet is usable, if not as quick or capable as the other tablets in the preceding table) but this is less important when running conventional business apps.
By going through this exercise, my appreciation for the value of a slim but powerful tablet has jumped noticeably. I’m not sure the technology is completely there yet, but the industry is definitely making some great strides. By the time many businesses are really ready to take Windows 8 seriously — which is to say sometime in the next 18-36 months) it’s entirely possible that technology will rise to meet their needs. If a 1.5 pound unit with an attachable and usable keyboard can match today’s Lenovo units for computing horsepower, moving these units should be a slam-dunk proposition!
If you’ve been reading this blog for any length of time, you already know that Lenovo has been updating its PC and notebook drivers and software for Windows 8, surely but steadily, since the March-April timeframe of this year. Just recently, I downloaded their latest version of the ThinkVantage Power Manager software (version 3.00.0006) which represented itself on the download page as ready for Windows 7 and Vista but made no mention of Windows 8. Having had pretty good luck getting 7 stuff to work with 8, I decided to give it a try anyway. It installed without errors or warnings, but lacks any reporting on or coverage of the battery installed in that machine (see photo).
Imagine my surprise when I later downloaded and installed the Lenovo Solution Center for Windows 8… (LSC) and it produced the following screen on the X220 Tablet:
This was very interesting, because the battery appeared to be working just fine but simply invisible to the Power Manager (and by extension, to LSC as well). I could see and access it using the built-in Power Options item in Control Panel, and a quick download and test of my favorite third-party battery manager — namely, Battery Bar (and its even better commercial sibling, Battery Bar Pro) — showed that the battery was indeed present, and seemed to be doing its job well enough. I’m not wild about the battery life for the X220 Tablet’s stock battery — the 63Wh 42T4879 model only delivers about 2-3 hours of life under normal usage — so I decided to call support, share this information with them, and see what would happen.
It took me about half an hour to get on the phone with a support technician after initial dial-in. I explained the situation to her as clearly and concisely as I could, and she said that she would research the matter and someone would call me back “soon.” That was on Friday morning (November 9). This morning, the UPS guy rang my doorbell and presented me with a box containing –surprise! — a replacement battery for the X220 Tablet. I can only assume the company decided to replace the battery because of the LSC diagnostic (bogus, IMO) about which I reported to them. Lenovo may end up eating costs for a lot of X220 Tablet batteries, if all those who own these machines and upgrade to Windows 8 do as I have done, and call in to report the LSC status and wind up with a free replacement. The cheapest price I can find for that part number is $42, not to mention costs involved in shipping and handling a replacement unit via UPS Next Day Air (I’m guessing this cost Lenovo at least $60, perhaps more).
But wow! What a way to “update status” on a request for help with immediate delivery of a replacement. You cannot at all fault Lenovo (or IBM Support, which handled my phone call for Lenovo) for slow, faulty, or non-responsive customer service. Without a doubt, this is the very best warranty replacement service I have ever received from any vendor of computing gear, in all the years I’ve been in the industry. Amazing!
Next Tuesday, November 13, will be the first Patch Tuesday since the official Windows 8 release occurred on October 26. Thus, it’s entirely fitting that Windows 8 will receive its first-ever “Critical” updates on that day. I puzzled over an article from Lance Whitney at CNET a few minutes ago because it was entitled “Windows 8, RT to get first critical security patches next Tuesday,” until it finally dawned on me that he wasn’t saying “first security patches” in general, but rather “first security patches with a Critical designation.” Because MS explains this as a “vulnerability whose exploitation could allow code execution without user interaction,” this is pretty serious stuff indeed.
Here’s a preview of coming attractions from the MS Security Bulletin for November 2012 (advance edition):
Of the three items that apply to Windows 8 with critical designations (Bulletins 2, 4, and 5) all are labeled with remote code execution, and at least two of them will require a restart (1 and 5) and 4 may also require a restart as well. It should be interesting to see exactly what these bulletins cover, and how well Windows 8 slips into the regular Patch Tuesday cycle going forward. So far, we’ve seen two Windows Updates for the Flash Player, an important GA cumulative update (KB2756872), protected content playback (KB2768703), and logo images in All Apps view (KB2751352). But other than the usual Flash folderol there’s been nothing designed to fend off potential system takeovers. Maybe next Tuesday will change things?
In reading a recent (11/6/2012) posting from Paul Thurrott entitled “Taking Surface to Work” I stumbled across an incredibly interesting and tantalizing set of suggestions about what an upcoming planned revision to Microsoft’s Intune cloud-based PC and device management service could mean for enterprises interesting in centralized management and security for PCs and a variety of mobile devices, including Windows 8 RT and Windows 8 Phone devices. Let me begin with an extended quote from his blog post:
Surface comes with the same desktop-based Remote Desktop Connection (RDC) you know and love from Windows 7 and Windows 8, and it works the same way, allowing you to access remote PCs and servers through RDP. (There’s a Metro version too, if you’re all in on the new stuff.) It’s also compatible with RemoteApp, meaning that you can stream individual apps from servers to the Windows RT desktop, just as you do with normal Windows versions. So that’s all good.
For now, Surface can be managed only using Exchange ActiveSync (EAS). That is, it can’t connect to a domain and be managed with Group Policy. EAS is actually pretty good: You can configure PIN and password policies, do remote wipe, and so on. But if you’re familiar with the granularity of Group Policy, you know you can do a lot more to lock down true Windows clients. And although Windows RT (and thus Surface) can’t partake in that, change is coming.
Soon, Microsoft will ship a revision to its Windows Intune cloud-based PC and device management service. And although the firm hasn’t talked too much about this update, it will include Microsoft’s implementation of the Open Management Interface (OMI), which, put simply, offers more granular management capabilities than does EAS. This will make Surface (and all RT devices) far more manageable than other mobile devices based on Android or iOS. (Yes, Windows Phone 8 will use this management infrastructure, too.) [Italic emphasis mine]
I can’t say much about OMI yet, but I’ll note that it makes a ton of sense to use a cloud-based service to manage devices that are never going to be connecting to your on-premises infrastructure anyway. It makes so much sense that my understanding is that this capability will never, in fact, be added to System Center. Instead, I believe that System Center licensees will get — free or inexpensively — the right to use Intune for this purpose, too.
What this means is that MS understands full well that enterprises simply won’t use RT unless it can be managed rationally–which is to say centrally, using standard existing tools and platforms, with a rich and varied enough set of controls to ensure proper security, data and loss protection, and ways to mitigate potential loss or theft of IP and confidential information. The new revision to Intune is supposed to deliver just that, and should make Surface much easier for enterprises to set up, deploy, manage, and control — all of which should also make Surface much easier for such organizations to adopt and accommodate.
This is the first strong evidence I’ve seen that Microsoft is taking the long view in making Windows 8 an attractive option for enterprise class organizations and their users. They know that most of these kinds of adopters will wait a year or two before adopting the platform anyway. It looks like MS is doing due diligence to make sure that when enterprises are ready to start entertaining the idea of migrating to Windows 8, they will find it attractive. Thus, the mobile device options that Windows 8 offers will not only be appealing to their user communities, but also fit nicely into a vision of device and security management that, according to ITIL and other business process methodologies, represents the “right way” to deploy and manage technology within a modern organization. Veeeeeeeeeeeery interesting!
OK, so now I’ve been through it, too. On my brand-new Dell XPS-13, I’ve exercised the $14.99 upgrade to Windows 8 (followed by a $40 Upgrade to Windows 8 Pro) to catch the machine’s OS up Microsoft’s latest and greatest offering. I followed up the Dell “Windows 8 Upgrade Offer,” charged it to my credit card, then downloaded the upgrade. Along the way, I encountered two very interesting Windows 8 Store app-style screens:
Unlike the pre-release version, Windows 8 offers more upgrade options than with previous versions (which ostensibly required clean re-installs to move from one version to the next, but which could be “tricked” into upgrading). I especially like the option of creating a bootable UFD (USB Flash Drive) because it can be re-used more than once after it’s created (though you must use a different key for each install, and the $15 upgrade process — including collecting the all-important install key — MUST be run on the intended target machine). The $40 upgrade is a little more forgiving: you can pay for up to 5 keys on a single machine, then use them with the UFD for other machines where you want to go through the upgrade motions.
FWIW, I elected to forgo the “upgrade right away” option on my XPS-13 because I had some Intel driver issues to fix that required uninstalling Wi-Fi, along with a few other odds and ends, before I could apply the upgrade. Since Wi-Fi is the only networking option built into the XPS-13 — as an ultrabook, it lacks an RJ-45 port for wired Ethernet — I elected to burn a USB drive with a bootable OS image, and then install later, after I cleaned up my drivers and installed and used my wired StarTech USB 3.0 GbE interface for networking instead. All of this worked reasonably well, and the whole process took just under an hour to complete. But I did also have to spend some time cleaning up drivers before I could lurch ahead into the outright OS install process.
Another word of warning: make sure you have ready access to your Windows 8 key, because when you run the Installer, it asks for the key BEFORE it runs the compatibility check. Because of this ordering — which made me a little nostalgic for the days of standalone compatibility checkers — I had to print my key from the XPS-13 running Windows 7 before booting into the install UFD, to re-run the compatibility check to create my “to do” list of things to clean up before running the installer again. In fact, the compatibility check comes about 5 steps into the installation process, which makes it tedious to have to repeat it more than once, so be prepared to print or otherwise capture your own to-do list the first time you run the Updater, and you may save some extra time that way. But the Installer does give you the option of uninstalling offending items directly, as shown in the screen cap, and picks up where it left off after a reboot so all goes pretty well along the way. I chose that option for the XPS-13 and it worked spiffily, but added 10-12 minutes to the overall install time. My advice is to do a clean reinstall, unless you have compelling reasons to keep elements of your current Windows 7 installation around.
Once the install completed, I ran DriverUpdate to see what needed to be found and re-installed to make the machine’s drivers current. Curiously, it was mostly Intel stuff that needed to be brought back up to snuff. Took about 2 hours to get everything as squared away as I could (DriverAgent says the system needs a new version of WiDi, but I can’t get the recommended program to find any WiDi adapters; looks like I have to take it into the living room with my new Samsung SmartTV).
Here’s what I get from the Windows Experience survey in Windows 8 on this machine:
Between my MSDN license (which gets me 5 licenses each for Windows 8 and Windows 8 Pro, plus one Windows 8 Enterprise license) and the 5 licenses I can buy through the $40 upgrade program, plus the one el-cheapo I qualify for on my Dell XPS-13, I think I’m taken care of as far as Windows 8 licenses go. But life will be harder for those pirates who seek to exploit low-cost TechNet and MSDN licenses, and I hope the low prices on legit upgrades will spur users to purchase them on the open market rather than on the grey-to-black market, instead. As upgrades go, this one didn’t kill me and isn’t terribly different from the Vista-to-7 or XP-to-7 experience.
TIFKAM is, of course, my slightly-tongue-in-cheek acronym for “The Interface Formerly Known As Metro.” After some hoopla and waffling in the wake of Microsoft’s decision to kill the “Metro” name for its tile-oriented user interface, the Windows 8 UI has gone through a whole slew of names since then. To the best of my ability, that series of names runs something like this:
2. Modern UI-style
3. Windows 8-style
4. Windows 8 style UI
5. Windows 8 Store
6. Windows Store
A recent CNet story report that the new official nomenclature is “…simply Windows Store apps.” As numerous observers have noted, this is not exactly a thrilling or even terribly descriptive brand name. And according to Mary Jo Foley of ZDnet, Microsoft is following suit to change what had formerly been known as “the Metro design language and style” to “the Microsoft Design Language” instead.
OK, so now we know what to call it, according to MS official nomenclature. But I read a lot of Windows 8 coverage, and many experts — including Ed Bott, Paul Thurrott, and Fred Langa — continue to use the word “Metro” to describe the Windows 8 interface, even though they all routinely acknowledge that this term is no longer officially blessed. I’m curious to see if Microsoft can actually move the world along to adopt its own terminology or if the original term will continue to stick, where non-MSofties use “Metro” as their preferred name, and simply acknowledge (once, at the beginning of any discussion) what the current name of the moment might happen to be, and stick to the original moniker.
What’s in a name for the Windows UI? Beats me, but this flopping about and constant change is both irritating and interesting at the same time!
Today, I’m doing a recap and shout-out to Tony Bradley’s excellent PCWorld blog entitled “10 Essential Ingredients of a Killer Windows 8 Business PC.”
Instead of the Sony Vaio with which he kicks off his blog, I show a publicity still of the new Lenovo Yoga 13″ convertible laptop/tablet, which is garnering accolades as one of the best combo platforms for Windows 8, with strong chops both as a tablet and as a conventional laptop. Bradley cites an interesting iYogi survey in his blog that “…38 percent of the respondents currently using iPads for business are exploring Windows 8 tablet options…” and “…one-third of small businesses are considering switching to Windows 8…” Both of these numbers are somewhat higher than I would expect (I’d love to know how they selected the population of 175 small business customers they interviewed).
The ten characteristics that Bradley enumerates in his blog are as follows:
1. Touch support: if not an outright touch screen (not terribly practical for conventional desktop or laptop PCs), then a multi-touch touchpad is essential for Win 8.
2. Horsepower: Win 8 works well on existing Win 7 PCs and laptops, and doesn’t make strenuous budget demands for new PCs, either.
3. Storage: 500 GB or more of local storage, plus access to SkyDrive, means that Win 8 users don’t have major storage woes.
4. Battery: The focus on mobility for Win 8 means it’s an excellent power miser, and makes the idea of “a day’s work on a single charge” more realistic (if still a bit too optimistic) than ever before.
5. Portability: Nothing beats a tablet for light weight and small form factor, though the size and weight of the platform is best determined by the kind of workload users must manage.
6. Connections: Choose your ports wisely and well, and recognize that tablets come with precious few of them. Pick USB 3.0 whenever possible to exploit its higher throughput.
7. Networking: If you need mobile networking, look for devices with 3G or 4G WWAN support. Consider waiting for 802.11 ac wireless, if high network bandwidth is important to you.
8. Durability: Be sure your tablet or notebook can take a beating to improve the rates of survival for business travel or you might be sorry. Another great argument for SSD storage comes from its ability to withstand shocks and trauma without damage to data and programs.
9. Security: Win 8 offers improved support for UEFI, TPM, biometric scanners, and more to up the overall security for this new OS.
10.Flexibility:Win8 lets users combine tablet and laptop functionality to give buyers (and users) more options on how to work while on the move. Overall, this is a good thing for business users.
Overall, I’m in agreement with Bradley’s analysis, and believe that Win8 will enjoy some business uptake and success. But I think it’s going to take time, and it will be something of a difficult slog for MS to convince business users to give up on Windows 7 in the wake of recent migrations and the whole Vista debacle.
I’m sending off my 2010 MacBook Air to Virginia, so my high-school age niece can use it regularly for schoolwork (I never really found as much call for it was I thought I would, once I finished tech editing Chris Minnick’s WebKit For Dummies late last year). That left me with a USB drive that I’d been using for Time Machine backups that I wanted to repurpose for backing up my Lenovo Windows 7 and 8 notebook PCs (an X220 Tablet running Windows 8 Pro, and a T520 notebook running Windows 7 Professional). But when I tried to reformat the drive to make the switch to Windows, I learned two interesting things:
1. Mac OS X lays down a 200 MB EFI partition at the head of its disks, even USB-attached drives.
2. The built-in Windows Disk Management tool
diskmgmt.msc won’t delete or format over EFI partitions.
Obviously, I needed a different tool for this job, and I found it in Paragon Software’s Hard Disk Manager 12 Suite. Using this toolset, I was immediately able to grab and delete the offending EFI partition, after which I reformatted the entire drive (nominal 750 GB, 698 GB reported in Windows Explorer) without any further difficulty. I’ve already backed up both Lenovo machines, and sucked up nearly 80 GB of space on this drive, a Samsung SpinPoint HD753LJ hard disk.
This little adventure reminded me that where there’s a will there’s a way to get things done in Windows, but also that exercising such will must sometimes involve tools outside what Microsoft uses to stock its basic OS toolbox. For dealing with disk issues of all kinds — including OS migration, partition management and resizing, and repair — I’ve found the Paragon Software tools to be straightforward to use, entirely reliable, and reasonably affordable. Be sure to check them out at the Paragon Software site online; free trials (some with functionality limited to virtual mode operation only) are available for most of its products. Good stuff!
I realized that I was guilty of GUI thinking in jumping out of the Windows corral to tackle this problem, so these contortions are at least partly of my own making. Of course, I could have turned to the command line instead, where the
diskpart utility could have done away with the offending EFI partition pretty quickly (along with the rest of that drive’s existing disk structure). All I had to do was use the
diskpart command, then issue the following sequence of instructions:
DISKPART> list disk
DISKPART> select disk y
In this command sequence, y stands for the drive number for the target drive, so the target drive need not even be mounted as a Windows file system volume to perform this task (a good thing, since any Mac OS drive won’t mount by default in Windows). The concluding
exit command is required to exit the
diskpart utility, after which you can close the command window.