All posts by Ed Tittel

Full-time freelance writer, researcher and occasional expert witness, I specialize in Windows operating systems, information security, markup languages, and Web development tools and environments. I blog for numerous Websites, still write (or revise) the occasional book, and write lots of articles, white papers, tech briefs, and so forth.

{WED} Temperamental Dual mSATA SSD Cleaned Up

A few years back, I found myself with some extra mSATA Samsung EVO 250 SSDs on my hands. I purchased two Syba 2.5″ SATA 6G/USB 3.0 to Dual mSATA RAID (SD-ADA40107) adapter cards. I paid about $40 each (they cost $26 now). One of them has been terribly temperamental. Over time its plugged-in SSDs become unreadable. Seems like setting the card down on a conducting surface causes the drives to go bye-bye.  (I don’t have it in a case, as I undoubtedly should.) This happened before on my Surface Pro 3, which sits on a set of (metal) baker’s racks. And today, when I tried to back up my Lenovo X380 Yoga Fast Ring test machine, its drives were once again MIA. Thus, I found myself with a temperamental Dual mSATA SSD cleaned up. Good thing I only keep throwaway data and backups on those drives. Fortunately, I didn’t lose anything I couldn’t recover from.

Temperamental Dual mSATA SSD Cleaned Up.device

I’m guessing that the SSD devices somehow conduct to the rails on the case, and cause the drives to short out if grounded. Sigh.

How Temperamental Dual mSATA SSD Cleaned Up Happened

When I tried to access the devices I got a warning message that they were inaccessible. (I have them set up as JBOD, not RAID, so they show up as Drives E: and F:.) Having seen this before, I attempted repairs using MiniTool Partition Wizard 11. Alas, it couldn’t find anything to recover. So I went into DISKPART and ran a CLEAN operation on each of those drives. Then, I reformatted them as MBR devices using NTFS. They definitely ran faster after the clean-up: Macrium Reflect reports read speeds of 3.6 Gbps and write speeds of 2.6 Gbps for the most recent (and only) backup on the device now. (Of course, this is an artefact of the compression the program uses when accessing the drive: actual throughput isn’t really that fast, either coming or going.)

The funny thing is, I’ve got another one of those cards plugged into a drive caddy where it’s safe from accidental grounding. I’ve never had a problem with that one. So maybe — just maybe — it’s time for me to buy a 2.5″ case (which form factor the card matches exactly). Then, I can  take care of the problem once and for all. But at least I got a refresher on DISKPART out of the deal, and the backups are now running lickety-split. (Elapsed time for the last one was 05:30 for a total of 28 GB of disk space consumed.) That’s the way things go here in Windows-World sometimes, where even backups need occasional backups. Would that I could so easily cure my tendency toward operator error!

Facebooklinkedin
Facebooklinkedin

{WED} MS SaRA + Removing IRST Restores Win10 Stability

Over the past couple of weeks, I’ve been fighting some vicious Windows 10 issues. One of them manifested in the form of over 100 Outlook MoAppCrash errors related to WindowsCommunicationApps that check in with remote email servers. Those came at a rate of at least 5X daily. The other involved regular IAStorDataMgrSvc.exe errors, at the rate of at least one a day. Between the two, as the intro screencap shows, my system’s Reliability Index hit rock bottom 7 days in a row. But between using the Microsoft Support and Recovery Assistant (aka MS SaRA) and removing an unnecessary driver, I’ve been able to return my production PC to more or less normal operation. Hence this blog post’s title: MS SaRA + removing IRST restores Win10 stability.

MS SaRA + Removing IRST Restores Win10 Stability.main

As SaRA’s home screen shows, it’s good for addressing a broad range of Windows problems. It definitely fixed my Outlook errors without too much muss or fuss.
[Click image for full-sized view.]

The Many Powers of SaRA

I hadn’t used SaRA much before (though I did have a copy in my utilities folder). But when I ran it, the software asked me to revisit its Download Center page to grab the latest version. I’m glad I did, because it’s added a lot of new Office and Outlook capabilities in this latest incarnation. And because that’s just what I needed, it was well worth doing. Having now used it on multiple occasions to fix a couple of trivial problems and this latest, more annoying and persistent Outlook issue, I can recommend it to Windows admins, power users, and even ordinary users alike. It should be part of any Windows user’s troubleshooting arsenal, as it is now part of mine (it goes way beyond Windows 10’s built-in Troubleshooters, available through Start → Settings → Update & Security → Troubleshoot). Grab a copy today.

Why Use the Intel IRST Drivers?

The ultimate source of my IAStor related “stopped working” error messages came from this folder:

C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorDataMgrSvc.exe

That’s what clued me in that the Intel Rapid Storage Technology (IRST) software was involved. Although IRST offers some modest performance boosts for SATA disks run independently, its biggest benefits come through its support for software-based RAID (Redudant Arrays of Inexpensive Disks). It turns out that for AHCI users who don’t have RAID disks, IRST is more or less optional. If you really want ALL the details on IRST drivers, versions, and access to nicely-modded alternatives, check out Fernando’s IRST Coverage at Win-RAID.com.

In my case, I decided to uninstall the whole environment because anything that causes errors but provides only modest performance gains is not something I want. Out it went. And, as the rising tide of the Reliability Index shows, taking care of both errors finally has things moving in the right direction. And that’s the way things go sometimes, here in Windows-World. I’m mildly pleased to see the system becoming more stable. Let me see it get back to a perfect 10, and I’ll be somewhat more pleased. Fingers crossed!

Facebooklinkedin
Facebooklinkedin

{WED} Windows Enterprise Desktop Blog Gets New Temporary Home

Just yesterday, I learned that my ongoing blog for TechTarget Windows Enterprise Desktop (WED) is no more. It first appeared on September 29, 2008 as Vista Enterprise Blog (see the banner graphic below for that initial item). Since that first post appeared, I wrote 1,583 items for that blog. My assigned frequency was 12 times a month. Starting on October 2008 through January 2020, gives 135 months. In fact, my actual monthly posting frequency was 11.72 over that period. Given holidays, vacations, and occasional sick days, I believe I met my blogging commitment over the 11 years, 3 months, and 13 days that my blog ran on TechTarget. For now, Windows Enterprise Desktop blog gets new temporary home here at edtittel.com.

Don’t get the wrong idea, though. It’s not just my blog that’s been cancelled. All the other 80-plus blogs at the IT Knowledge Exchange are cancelled, too. TechTarget plans to post no new Q&A or other content to that site, either. It’s the end of an era, and I’m just one of many industry people and players affected. Insider sources tell me the decision emerged from declining statistics, and unsatisfactory SEO results. That’s why I’m neither devestated at the loss, nor inclined to take it personally. Apparently it’s a hard-boiled business decision, pure and simple.

Windows Enterprise Desktop Blog Gets New Temporary Home.banner

I’m bemused to see my tenure extends back to the much-reviled Windows version named Vista. Personally, I never thought it was all that bad. Among many other good things, it brought us Desktop Gadgets, which I still use today.
[Click for full-sized view.]

Windows Enterprise Desktop Blog Gets New Temporary Home Right Here!

I will keep blogging 3 times a week about Windows 10 topics. Right now, I’m still negotiating with TechTarget about obtaining access to my historical blog stream. They own the copyright. Even so, I’m hopeful I can make an archive copy for my readers. While we’re working out those details, however, I’ll post three times a week right here on Windows 10 topics until I get things worked out. So far, my friend and colleague KariTheFinn has graciously offered to host the blog at our jointly-owned Win10.Guru site. But because I already post 3 times a week there on Windows 10 news and topics, I’m concerned that doubling up might reduce my following there. (Yes, there is indeed the possibility of “too much of a good thing.”) I’m also in conversation with a couple of other websites/content developers about staking out a presence somewhere else, so we’ll have to see how things turn out.

Time to Change Your Favorites/Bookmarks

For the next little while, you’ll want to change your bookmarks or favorites from one of the two that worked for this blog’s previous incarnation to the temporary new one. Here’s a list of relevant links:

1. TechTarget: SearchEnterpriseDesktop: Windows Enterprise Desktop (Old, but still has archival content)
2. TechTarget: IT Knowledge Exchange: Windows Enterprise Desktop (Old, but still has archival content)
3. EdTittel.com: Blog: WED posts in my ongoing Blog Stream will start with {WED} ahead of the actual post title. I plan to post there every Mon-Wed-Fri (starting today), until a new home is found or built.

Stay tuned!

A Preview of Coming Attractions

There are several different kinds of items I like to post to WED. First and foremost, I like to document Windows 10 problems, errors and misunderstandings that I experience myself, up close and personal. If I can find a fix or workaround, I’ll include that in the coverage because “problem + solution” beats “problem by itself” without exception. Some mysteries do, alas, remain forever unsolved. Second and less often, I like to share important bits of Windows 10 news and information that should impact or interest readers. Third, I like to share step-by-step instructions or how-to’s for Windows 10 topics that I’ve had to tackle and use on my systems, on the theory that others may find them useful too. Fourth, I’m a little bit of a gadget freak, so when I find a piece of gear that helps me work with Windows 10 more productively in the office or on the road, I’ll share my experiences, describe the gear, and point toward the best prices I can find.

All in all, it’s enough to keep me engaged and interested in publishing bits and pieces three times a week. Ongoing, longtime readership suggests that others feel the same way about these modest efforts. Thus, I hope you’ll shift your bookmarks around (or add a new one) to keep up with these re-housed, but continuing adventures in Windows-World. Thanks for your patronage and support over the past 11+ years. I hope you’ll allow me to keep it going forward.

Facebooklinkedin
Facebooklinkedin

Intro Slides for Data Protection, DRaaS and Disaster Recovery Webinar

On Wednesday, February 12, 2020, I delivered a recorded introduction to an ActualTechMedia.com webinar entitled “Enabling Data Protection, DRaaS, & Disaster Recovery Capabilities.” As is my usual practice, I included hyperlinks to articles and a range of related training and certification programs. Because I was unsure that those slides would be readily available to the audience, I am making them available through this web page. I’ve made this PowerPoint deck available through OneDrive: simply click the link in this sentence, and you’ll be able to download the slide deck immediately.

Here’s what the intro banner looks like on the ActualTechMedia website:

A MegaCast brings six or more leading vendors together to talk about specific tools, platforms, and technologies. For this webinar the following companies participated: Cohesity, druva, Clumio, Datrium, Zerto, Nutanix, and UniTrends.
[Click image for full-sized view.]

Facebooklinkedin
Facebooklinkedin

Mixcder E10 ANC Bluetooth Headphones Are a Real Bargain

From time to time, people contact me to ask me to review their products. That’s how I’m trying out a pair of Mixcder E10 Active Noise Cancelling Bluetooth headphones. So far, they’re a great set of low-to-modestly-priced headphones with excellent product build and sonic characteristics. Here’s what comes with the Mixcder E10 ANC Bluetooth Headphones, from one of their publicity stills:

E10 entire kits

Clockwise from top left: E10 headphones, old-fashioned dual jack airplane audio adapter, genuine leather zip case, dual mail mini-RCA cable, mini-USB to USB-A cable.
[Click image for full-sized view. Source: Mixcder.com.]

Where Does Ed Get Off, Writing About Audio/Headphones?

I’ve been an audiophile since high school. As soon as I got to college and made some money, I built a HeathKit pre-amp. It went with a Dynaco Tube amp to drive a pair of Arena speakers. My first job after undergrad was as an audio engineer at the Library of Congress (LC). I upgraded to a pair of JBL 4331 Studio monitors. I still used the same pre-amp, with a BGW 250-B solid state amplifier (it still drives my right and left front speakers today).

These days, I run an Outlaw Audio 976 pre-amp/video processor. I also use that same BGW amp, plus 3 Rotel 100-watt solid state amps. They drive a 5.2 setup on Phase Technology speakers. Once upon a time, I attended a summer course on audio engineering at the Eastman School of Music (summer of 1974). This came courtesy of Head Engineer Bob Carneal and the LC.

As part of my job at the LC, I mixed up to 8 channels of audio into stereo. This happened on a Langevin mixing board in the LC’s Coolidge Auditorium. During the “cultural season,” we taped chamber music concerts for public radio distribution. That remote mixing board was backstage. Perforce I had to listen in on a set of “cans” (as we called headphones, back in that now-prehistoric time). My ears hosted Sennheiser headphones that cost over US$300. (The Inflation Calculator says that’s worth $1,737.89 in 2020 dollars.) Those concerts could run two hours, or just a bit over. That explains why I’m (painfully) familiar with extended headphone wear.

E10 Build Quality

As you can see from the preceding photo, $65 to $93 buys a fair bit of stuff. (List price on the website is $112.99; the other prices come from swadeal and Amazon, respectively.) The headphones themselves are substantial, and not overly heavy, at 304 grams (10.72 oz). They’re a closed-ear design. Firm memory foam cups are covered in light leather (or a reasonable fascimile thereof). The headrest is built likewise (memory foam underneath, leather wrapping outside). The cups are labeled “R” and “L” inside. This makes it easy to orient them properly when donning them. The materials are solid and the headset looks able to withstand normal wear-and-tear (and then some, perhaps).

E10 Accessories

I’d have liked it better if the ‘phones sported a USB-C port for charging rather than mini-USB. But the E10 is what it is. Charging is quick: the first full charge took about 94 minutes. A second full charge only took 60 minutes. The maker claims 60 hours of battery life with ANC turned off. ANC turned on cuts that in half (a still-respectable 30 hours). So far, I’ve not been inclined to push things. I’ve not exhausted the battery after more than 20 hours of active use (with ANC turned on, mostly).

A mini-RCA cable runs the ‘phones in wired mode. Another reviewer claims this produces slightly better audio quality than Bluetooth. Personally, I couldn’t hear any difference between the two forms of input myself. But at age 67 my ears probably don’t work as well as Jupit3r’s (the other reviewer) do, either. Take it under advisement, knowing that a wired connection is handy in signal-rich environments or when flying. I guess that’s when the mini-RCA to dual airplane jack might come in handy. But I haven’t flown on any planes that featured such jacks in quite some time. (I just got back from Washington, DC last Saturday, January 4: we flew a Boeing 737 with USB-A ports.)

E10 Listening Experience and Headphone Comfort

I’ve read numerous reviews (see links at the end of this story) that praise these ‘phones comfort and fit. I’m sorry to say I don’t agree. Though the sound quality is quite good,  the phones weren’t comfortable for extended wear. I found myself remembering the “headphone headache” I got in the Coolidge Auditorium after wearing the Sennheiser ‘phones. I couldn’t wear the E10 ‘phones for more than 90-120 minutes without taking a break from their firm grip.

That said, that’s my only gripe with the E10s. The sound quality is good enough that I heard some things amidst my recordings that I’d never heard before. (Not even on my mid-range semi-professional audio rig.) The price is especially attractive, given that you can buy the E10s for under US$100. (In fact, as much as $30 less than that from some sellers.) I have a nearly16-year-old son who’s lost one set of earbuds. He’s also worked his way through two different kinds of Bluetooth headphones over the past couple years. I wouldn’t hesitate for a minute to buy him E10s. I’m enjoying them myself, too. I just can’t handle them for more than two hours at a time. YMMV when you put them on for yourself and see how they fit you. They’re definitely worth a listen, in any case.

Other E10 Reviews Worth Reading

Here is a trio of reviews (including the afore-linked one cited earlier in this story) of the E10 headphones. For more info and different perspectives, check one or more of them out!

KnowTechie: Review: Mixcder E10 — Impressive, lag-free noise canceling headphones
Engineering & Technology: Top-of-Mixcder’s-range noise-cancelling wireless headphones for a less-than-a-ton price.
Head-fi.org: Mixcder E10 Review – Active Noise Cancelling Bluetooth V5.0 Headphones

Facebooklinkedin
Facebooklinkedin

SpiceWorld 2019: Native Boot VHDs in Windows 10

Here, as promised, is the slide deck for my presentation at SpiceWorld 2019 this morning, about Native boot VHDs in Windows 10. Click this download link for the PowerPoint file (OneDrive).

SpiceWorld 2019: Native Boot VHDs in Windows 10.title

Native Boot VHDs in Windows 10: Using GPT and Type-2 HyperVisor VHDs (.vhdx)

For GPT, add the “convert GPT” command to the DISKPART script, as follows:

create vdisk file=F:\W10PRO.vhdx maximum=51200 type=expandable
attach vdisk
convert gpt
create part primary
format quick
label=”Windows”
assign letter=W
exit

When creating a VHD file for native boot, always use MBR partitioning! To upgrade Windows on a native boot VHD, you must temporarily run it as a virtual machine. This means attaching that VHD to a VM.

An MBR partitioned VHD is easy to attach to a VM: mark its Windows partition active. OTOH, a GPT partitioned VHD with only a single partition for Windows requires that you manually create system partitions before it’s usable as a bootable VM (MSR and EFI along with the system partition at a minimum, recovery partition if a complete emulation of “normal Windows 10” is desired).

Say you want to use a GPT partitioned VHD for native boot for some reason (and we can’t think of a valid one). In that case, it is best to first create a Generation 2 VM in Hyper-V, then install Windows 10 on it. This takes care of the partitioning automatically, and does so correctly. That VHD can then be added to the boot menu for native boot, or used as a VM.

Facebooklinkedin
Facebooklinkedin

A Twist on Dual SATA Drive Docks

I’ve got a couple of nice dual SATA drive docks here at the office. They’re from a Taiwanese job builder named Inatek, model FD-2002. Right now, you can pick one up for under US$30 on Amazon (see preceding link). I’ve used them with great success for drives of all sizes, up to and including 8 TB (Toshiba X300 Performance: ~US$176). Right now, I’ve got one of them populated with 2 4TB HGST Ultrastar drives (~US$95). Until yesterday, I had the 8 TB Toshiba drive paired with an HGST Ultrastar 3TB drive (~US$40, a truly great deal price/performance wise). Then the twist came into play.

A Twist on Dual SATA Drive Docks.dock

Turns out there’s a limit to how much storage will work in one of these low-cost dual drive docks. I hit that limit yesterday!
[Click image for full-sized view. Image Source: Amazon.]

What’s the Twist on Dual SATA Drive Docks?

Turns out that the bigger the drive’s capacity, the hotter it runs. Putting the 8 TB and 3 TB drives in juxtaposition worked fine, until I started using the 8 TB drive heavily. Then, all of a sudden, the 3TB drive started popping in and out of service. Not good! I’m not sure if it was an issue related to the power draw to the drive dock (more than it could handle seems pretty likely to me). OTOH, it could’ve just gotten too hot to keep working. When I took the 3 TB drive out of the dock, it was uncomfortably warm in my hands. I replaced it with a 2.5″ form-factor SSD drive and that combination has been running without a hiccup for almost 24 hours now.

Let this be a gentle warning, dear readers! If you want to pair up storage devices in low-budget dual drive docks, you may want to limit yourself to no more than 10 TB of total storage. Apparently, I hit some kind of wall when I attempted to make steady, serious use of 11 TB (8 + 3) in such a device yesterday. I’m tempted to try it again with a fan blowing on it, to see if lowering operating temps will permit it to keep working. If not, I’ll be more or less convinced it’s a power supply limitation. We’ll see!

 

Facebooklinkedin
Facebooklinkedin

Interesting Win10 Gadget Conundrum

I can’t help it. I still love Windows Gadgets. They came in — and went out — with Windows 7, supposedly because of security considerations. I’ve never had, nor heard of such issues in the wild. My old friend and security guru, Deb Shinder, also uses Gadgets. She feels the same away about their demise. Helmut Buhler created 8GadgetPack to bring Gadgets to Windows 8. He’s kept up with them, and they work well with Windows 10. (His current version is v29.0, released in May 2019, so it’s pretty up-to-date.) Each time you upgrade Windows, it sees Gadgets and kills them off. So he’s also written a “Restore Gadgets” routine that recognizes this act, and restores the pre-existing Gadget set-up after each OS-based cancellation. Lately, though, I’ve been posed an interesting Win10 Gadget conundrum.

What’s the Condundrum?

The two following screenshots show the puzzler I’ve been dealing with lately. Notice the display at the bottom of the two CPU Meter Gadget windows that follow. It’s a CPU utilization graph, that shows per-core utilization percentages. The graph on the left-hand-side fills up the entire Gadget panel, while the one on the right-hand-side fills up only about two-thirds. After the most recent Nvidia driver update (which applies to the left-hand item) the Gadget on that PC went from a partial graph area (which applies to the right-hand item) to the full graph area. The PC from which the right-hand item comes is a Surface Pro 3 that uses built-in Intel graphics circuitry that’s built into the i7-4650U processor in that machine. The PC on the left is my production desktop, as the i7-6700 CPU should indicate.

Interesting Win10 Gadget Conundrum.both

Careful inspection shows the utliization graph at the left fills the full Gadget frame, while the one on the right fills about two-thirds of the same area. What gives?

Here’s the conundrum: I’m pretty sure that there’s something in the nexus between .NET and the GPU driver that’s causing the CPU utilization display area issue. Installing Nvidia’s latest GeForce driver (Version 431.60, which shows a 7/23/2019 release date (but which I just installed today, 8/5/2019) on my production PC fixed the issue. It still persists on all of my systems running Intel on-chip GPUs.

A Minor Niggle Still in Search of a Fix

This is the kind of mystery that guarantees lifetime (or at least ongoing) employment for Windows wizards, gurus, and mavens. I’ll keep messing around with those Intel drivers until I find one that works like it’s supposed to. This has been going on at least since last February or thereabouts, though, so Intel’s obviously under no pressure to catch up with this minor and niggling little GUI detail. It gives me something to do when I get bored, so I can’t complain. And so it goes, here in Windows-World!

PostScript Added August 6, 2019

OK, so I updated my Lenovo T520’s graphics driver last night, too. It includes both an Intel on-chip GPU (HD 3000) and an Nvidia Quadro NVS4200M independent GPU. I updated the Nvidia device to Version 392.56 later yesterday afternoon. This machine had also been subject to the “reduced display” layout shown above for the Surface Pro 3. But after I remoted into that machine this morning, I immediately noticed that the CPU utilization graph at the bottom of the gadget now filled the entire pane, to wit:

This time I loaded Core Temp so that the “not running” error message didn’t appear. Makes the utilization graph a little easier to see and appreciate. So somehow, updating the Nvidia driver (even though I’m not using it) fixed the problem. As a consequence, I’m rethinking my theory of what’s causing the problem. But on my Intel-only systems, the problem persists. I’ll keep working on it . . .

Facebooklinkedin
Facebooklinkedin

Remembering D-Day and the Greatest Generation

OK, folks. Listen up! Today is the 75th anniversary of D-Day, and the commencement of the invasion at Normandy’s Omaha Beach that would ultimately turn the tides for Allied victory in WWII. General Dwight Eisenhower was informed that casualties could be as high as 75%, but ordered the action regardless. As it turns out, the National D-Day Memorial Foundation determined the number of casualties on the first day of combat at 4,414. Given that 150,000 troops saw action that day, the number could have been much, much higher.

That does not diminish the sacrifice that occurred on June 6, 1944 by one bit. My hat is off to all of those personnel, and to those who were injured or wounded in combat, and to all of their families. My Dad also served in combat in WWII, but in the Pacific theater instead. By the time D-Day rolled around, my Dad was working in the Signal Corps in Manila, in the Philippines, to help restore electrical power to that city. About one month after D-Day, he was seriously burned (and shocked) when a co-worker unintentionally turned on the juice to a 12,000-volt line while my Dad was working on its wiring. He lost most of the skin on his right hand and on the back of his neck, where the current entered (his hand) and exited (his neck). He would be shipped back to the USA, to spend the next four months in recovery and rehab at the famous burn ward at Brooks (then an Army Hospital, now a state-of-the-art Army Medical Center) in San Antonio, TX. One month later, he would meet my Mom, also home from the war for medical treatment, at their mutual hometown of Elizabeth, NJ.

There’s not enough any of us can do or say to recognize and appreciate the sacrifice of all the brave soldiers, men and women, who served our country so faithfully, and so well in this horrible conflict. I’d like to add my thanks and profound appreciation for all of those who served. This goes double for both of my parents, LTC Alfred F. Tittel (USAR, ret, 27 years of active duty) and LT Cecilia K Tittel (nee Kociolek, USAR, honorably discharged in January 1946). Neither of them ever talked very much about their wartime experiences but we could always tell it had touched them deeply, and that they were both honored and grateful to have served their country in time of war and great need.

I’m sitting here at my desk bawling like crazy. As I remember D-Day, this is also a great opportunity to recall and honor my Mom and Dad. Mom passed away on September 11, 2009 and was interred at Arlington National Cemetery in the plot that she will soon share with my Dad. Dad passed away on December 15, 2018 — the same day that Mom was interred at Arlington 9 years before. He’s waiting for his memorial service to join her at Arlington National. Our family is still waiting for Arlington to give us the date for his memorial service, for which Dad requested full military honors, including the caisson and the marching band. The funeral home says it will still be a while yet before we know when that might happen. Whenever it occurs, we’ll be there to honor his passing, and the service that he, my Mom, and all the other soldiers, old and young, also interred there gave this country.

Once again: farewell and thanks to all of them. May you all rest in peace, glory and dignity forever.

–Ed–

The preceding photos are, of course, my Mom and Dad. The photo of Mom was taken in late 1942 or early 1943, just before she was shipped overseas to participate in Operation Torch in Morocco. She would follow the Army through northern Africa (Morocco, Algeria, Tunisia, and Libya), then into Sardinia and Silicy, and onto France before being wounded there in 1944. The photo of my Dad is from the 1990s, in full formal military dress uniform, while attending a gathering of WWII Glider Pilots in Greece, where he was awarded the decoration just under his bowtie for his WWII service.

Facebooklinkedin
Facebooklinkedin

Hey Lenovo! Thanks Loads!!

I got a nice surprise from FedEx last Friday, April 5. An early knock on my door brought a couple of welcome boxes. Courtesy of Jeffrey Witt, Director of Lenovo’s Global Product PR, those boxes housed a couple of 8th Generation i7-based laptops. Mr. Witt graciously acceded to a request I made late in 2018 for a Carbon X1 Extreme, and an X380 of similar vintage. Images and specs will follow, but first, I have another story about some older Lenovo laptops to tell.

A Tale of Two Predecessors

Windows 8 actually has roots back to 2010/2011. By early 2012 Windows 8 was on its way, and technical previews were available. I got hired by Pearson/Que in January to work on a book, Windows 8 in Depth. I also knew Windows 8 was bringing big changes, most notably with the introduction of touch and the tile-based Start Menu. By the end of February, I knew I needed at least one touch-screen unit and one more test machine on which to run Windows 8 Technical Previews. That was the first time I corresponded with Mr. Witt, who was already involved with trade press folks and evals/loaner units. That time around, he helped me get a pretty deep discount on the two machines I bought for my Windows 8 work:

  • X220 Tablet: Sandy Bridge i7-2640M Dual Core CPU with Intel HD Graphics 3000, 500 GB spinner, 4 GB RAM, touchscreen, fingerprint scanner. Today, it has a 256 GB Plextor mSATA SSD, 16 GB RAM, and a SATA 256 GB SSD.
  • T520 Laptop: Sandy Bridge i7-2640M Dual Core CPU with Intel HD Graphics 3000, Nvidia Quadro NVS 4200M, 500 GB spinner, DVD player, 8 GB RAM, fingerprint scanner. Today, it has a 256 Plextor mSATA SSD, 16 GB RAM, OCX Vertex 4 128 GB SATA SSD, Seagate SATA III 1 TB spinner (replaced the DVD player with a SATA drive module).

I still use both of these machines daily. Considering that they’re now over 7 years old, that’s a real testament to their durability and usability. As I check my Windows Enterprise Desktop blog for Techtarget, I see 41 mentions of the T520, and 58 mentions of the X220 Tablet dating from April 2012 through February 2019. I have really *loved* these machines, and taken them from Windows 7 to 8 to 8.1 all the way to the current build for 1809 (Build 17763.404) on the T520, and the current Insider Preview 1903 (Build 18362.30) on the X 220 Tablet. Until the X1 Carbon Extreme showed up last Friday, the T520 had been my primary “road laptop.” It’s gone on every business trip I’ve been on since I bought it, and many of my personal trips as well. (My Surface Pro 3 and my late, lamented Dell Venue Pro 11 7130 also went along on many, if not most, family vacations.)

Say Hello to the New Kids in Town!

OK then, time for some specs on the new machines. But first, I have to gush about the Carbon X1 Extreme. I think it’s faster and more powerful than my production desktop. My son has completely fallen in love with it and uses it for homework every night. This involves a lot of web surfing, and lots of interaction with various Google platforms elements (Docs, Sheets, and so forth, standard in his school district). He still gets 5-6 hours of battery life out of the machine, which means he can pretty much work untethered. He’s also raved to me about its video playback capabilities. I’ll take his word for it: I’ve had no real time to explore these systems in detail yet:

  • X1 Carbon Extreme: Intel 8th Generation i7-8850H (6 cores, 2.6 GHz) with Intel UHD Graphics 630, Nvidia GTX 1050 Ti 4GB, 32 GB RAM,  one each Samsung MSLVBxx NVMe 1 TB and 500 GB SSDs, fingerprint scanner and Windows Hello Face recognition, and more. From what I see on Amazon, this machine retails for around $2,600-2,700. It weighs far less than its predecessor, at a svelte 1.84 kg/4 lbs 0.7 oz.

  • X380 Yoga: Intel 8th Generation i7-8650U CPU (4 cores. 1.9 GHz) with Intel UHD Graphics 620, 16 GB RAM, Samsung MSLVB10 NVMe 1 TB SSD, fingerprint scanner, and more. Checking Amazon again, I find a typical retail price of around $1,500 for this unit. This one weighs in at 1.6 kg/3 lbs (in round numbers: it’s just a hair under 3 lbs, actually).

It’s really far too early for me to do much more than ooh and aah over the latest laptops in my stable. As I have more time and opportunity to work with them, I’ll be writing about them in more depth. So far, the only thing I miss on the X1 Carbon is an RJ-45 port for direct Ethernet plug-in (but I’ve got a USB 3.0 GbE dongle already anyway, so no biggie; Note added April 9: the unit has a built-in I219-LM GbE NIC–and surprisingly, so does the X380–but you have to buy a special cable to get from its compact proprietary port to an RJ-45. Might be worth acquiring, though). I’m planning to acquire some big (256 GB+) SDXC devices for both machines, to further extend their storage. Another big difference with these newer models is soldered-in RAM (so no memory upgrades). But it’s a tradeoff for their enhanced compactness, I know.

I’ll close with a big THANKS to Mr. Witt and his RTP-based team. I really appreciate the opportunity to work with these machines, and hope to accomplish as many great things with them in the years to come as I’ve done with the T520 and the X220 Tablet. Now, if only i had time to really work them out. . .

Facebooklinkedin
Facebooklinkedin