Category Archives: AI

Mismatch Mars Surface Laptop Ultra

I’m chuckling — and the whole situation genuinely appalls me. If you want to spring for the top-of-the-line Surface Laptop Ultra, you can ONLY get it with a 1 TB SSD. IMO, this mismatch mars Surface Laptop Ultra offerings. Surely those who want 128 GB of RAM and the 20-Core Grace RTX CPU also want more solid-state disk storage? So, what was MS thinking?

The Ferrari with a 10-Gallon Tank

Think of it like equipping a Ferrari with a 10-gallon gas tank — that’s exactly what Microsoft did by pairing 128 GB of RAM and a 20-core CPU with a mere 1 TB of SSD. ASUS and HP already offer 2 TB configurations (and the ASUS ProArt P16 throws in a second M.2 slot for good measure). Dell, Lenovo, and HP haven’t yet revealed their planned configurations, but I’d find it shocking if any of them failed to offer at least 2 TB SSDs.

Wow! The whole thing stuns me. Maybe MS simply couldn’t source bigger drives. Nevertheless, configuration data confirms that models up to 4 TB from multiple vendors will likely run on top-end RTX Spark machines, to wit:

Drive Capacity Interface Notes
Samsung 9100 Pro Up to 4 TB PCIe Gen 5 Top tier, excellent thermal profile
WD Black SN850X Up to 4 TB PCIe Gen 4 Gen 4 will work but won’t hit Gen 5 speeds
Crucial T705 Up to 4 TB PCIe Gen 5 Strong value option
Seagate FireCuda 540 Up to 4 TB PCIe Gen 5 Competitive sequential speeds

Buy2Replace!

In fact, Copilot recommends that anyone buying the MS top-end model for US$5,899 MSRP should immediately upgrade to a 4 TB SSD from the table above. I now lean toward models that come with 2 M.2 slots — they push the storage ceiling even further.

After all, if you’re going “all the way,” you don’t want the vendor holding you back from wretched excess. But here in Windows-World, what you want and what you get often fail to coincide. So it goes!

Facebooklinkedin
Facebooklinkedin

Can Googlebook Occupy a Real Niche in the Computing Landscape?

Today, September 21, Google fired off its Googlebook platform. Five tier-one OEMs (namely, ASUS, Acer, Dell, HP and Lenovo) are all launching “premium” laptops into this newly defined space. Thus, asking “Can Googlebooks occupy a real niche” is a serious question. On the one hand the computing landscape is already carved into deeply entrenched players. On the other, that carving leaves gaps, and Google is betting it has found one it can occupy, and prosper from.

Who Already Occupies the Landscape?

Each major platform has staked out its territory clearly. Windows dominates business, enterprise, and line-of-business applications. It owns Active Directory, Microsoft 365, and decades of legacy software compatibility. That’s an enormous moat to cross.

Apple Silicon Macs own creative professionals and developers. Xcode, Final Cut Pro, and Logic Pro anchor a loyal, high-spending ecosystem. ChromeOS owns the education budget tier, shipping hundreds of millions of units into classrooms globally. Linux serves the hardcore developer and sysadmin community (and runs on 75+% of global Web and enterprise servers) with precision and flexibility.

Each of these niches is deeply entrenched. Therefore, the question is serious: does Googlebook find a gap, or does it create a new one? Those are very different challenges, and only one of them is easy.

Can Googlebook Occupy a Real Niche Amidst 3B Android Carriers?

This is Google’s best proposition. There are roughly 3 billion active Android devices globally. Most of their users have never found a laptop that felt native to this ecosystem. That’s a genuinely underserved market, and Google knows it.

Googlebook OS merges Android’s app stack with ChromeOS foundations. It adds phone-to-laptop handoff via “Continue On” and “Cast My Apps.” These features mirror Apple Handoff and iPhone Mirroring directly. In short, Google is attacking Apple’s continuity story head-on.

PCMag’s Brian Westover is cautiously optimistic. He called Googlebook “Google’s biggest hardware gamble to date,” but added that he is “betting on Google to reinvent the laptop again” (PCMag). He also noted: “This is probably the worst version of the Googlebook, it only gets better from here” (PCMag). The Android continuity story is real. Even so, it has to work, and not just in demos.

What Do Experts Say? Pros and Cons

Not everyone is convinced. Oflight’s enterprise analysis is frank: “Real-world software compatibility and platform stability will only be provable after the fall 2026 launch. Early adoption carries meaningful validation risk” (Oflight). That’s an outright caution for would-be enterprise buyers.

Consider further that Google’s hardware track record is mixed. The Pixelbook line is dead. Stadia is gone. Pixel Slate never took off. Enterprise buyers have long memories, and Google’s history of platform abandonment is a nagging concern.

On the upside, Oflight also notes that Googlebook inherits Chromebook’s low IT management overhead. It runs on the same Google Admin Console. For schools and SMBs already using Google Workspace, the upgrade path is smooth and familiar (Oflight).

PCWorld’s Ben Patterson frames the AI divide well. He describes it as “NVIDIA RTX Spark, which delivers local AI, versus Google Gemini Spark, which bets on the cloud” (PCWorld). Googlebook bets the cloud. RTX Spark bets local compute. Both bets make sense, but both can’t win (though both can lose).

NVIDA RTX Spark Arrives Oct 7

Mark October 7, 2026 on your calendar. That’s when NVIDIA’s RTX Spark platform hits. RTX Spark is a serious high-end play: up to 128 GB unified memory, 6,144 Blackwell CUDA cores, and 1 petaflop of FP4 AI performance. Pricing runs $2,000 to $3,500 and up.

RTX Spark doesn’t compete with Googlebook directly. However, it does apply real pressure at the top of Googlebook’s $899-to-$1,299 range. A buyer at $1,299 could pause. For $700 more, RTX Spark delivers local AI processing with full Windows app compatibility. That’s a considerable counter-offer.

Gzmato’s TCO analysis finds only 5 to 10 percent of buyers truly need that kind of comuting power (Gzmato). But that buyer group includes developers, researchers, and AI pros. Those are the very users Googlebook is trying to recruit. PCWorld’s Patterson captured it cleanly: “2026 is shaping up to be [NVIDIA] Spark versus [Gemini] Spark, and only time will tell” (PCWorld).

Rating Googlebook’s Odds of Success

Where does this leave Googlebook? The following table scores some key factors. Note further that strength alone does not guarantee a niche. Execution, timing, and staying power all matter. Google must prove it will not abandon this platform the way it abandoned others.

Factor Assessment
Android ecosystem leverage Strong: 3B+ active devices and a vast Play Store
OS credibility at launch Unproven: validation risk is real
AI feature differentiation Solid, but cloud-dependent vs. RTX Spark’s local story
Price positioning Competitive vs. MacBook; exposed vs. RTX Spark
OEM commitment Genuine: 5 tier-1 partners is no soft launch
Google’s staying power The biggest wildcard, given previous history

The niche is real but not yet earned. Android users without a native laptop have nowhere good to go right now. That is a genuine market. And it’s way larger than any hardware niche Google has targeted before. Alas, the computing landscape does not reward goodwill: It rewards execution.

Googlebook ships today, October 4. RTX Spark ships October 7. The next six months of reviews, compatibility reports, and developer adoption will answer the question analysts can’t answer today. Can Googlebook occupy a real niche in the computing landscape, or will it become another chapter in Google’s long list of hardware near-misses? Lots of people will be watching closely, including yours truly. I’ll also be wondering if this could pose a real challenge to Windows-World, given my own focus and interests. We’ll see!

Facebooklinkedin
Facebooklinkedin

Using Copilot on Intelligent Terminal

OK then, I just got my first chance to give Copilot in the “new” Intelligent Terminal app a shot. You’d think it would be easy, but there are a few hurdles to get over before Copilot will do its thing inside Windows Terminal, intelligent or otherwise. Indeed, using Copilot on Intelligent Terminal requires a GitHub Copilot account of some kind (Free, Pro, Pro+ or Max) before you can run queries inside the app. Otherwise, you’ll see something like this instead:

As you can see, no GitHub Copilot status means you can ask Copilot stuff inside WinTerm, but you can’t get anything except a “not authorized” error message in return.

Using Copilot on Intelligent Terminal
Takes Time & Effort

Ironically enough, I used Copilot outside of WinTerm to tell me how to get it working inside Intelligent Terminal. Turns out I had to set up a GitHub account, sign up for GitHub Copilot Free, then wait for registration to “take” so my login attempt would then be authorized.

Copilot told me it it would take 15 minutes to an hour for the sign-up process to result in a working session. As you can see in the lead-in graphic, when I put a query to Copilot inside Intelligent Terminal this morning, it worked. Having set the account up mid-afternoon yesterday, that was the expected outcome. But it still came as a welcome and pleasant surprise.

Now, To Learn How This REALLY Works…

As I understand it, GitHub Copilot Free limits users to 50 chat messages per month. Here are its other limits, again courtesy of Copilot itself:

  • Unlimited inline code completions (the lightweight autocomplete model)
  • Access to the GitHub.com Copilot Chat UI
  • Access to Terminal Chat (same 50‑message pool)
  • No access to premium models
  • No agent‑mode operations
  • No AI credits of any kind

Obviously I need to spend some time messing around with the tool, and get it working on scripting tasks for me. That seems to be the best way to put it work within the limited confines of the Free plan in which I’m currently enrolled.

At least, I got Copilot working inside Intelligent Terminal. Here in Windows-World, you have to take your victories, however minor, as you earn them. Stay tuned! I’ll be chiming in on this tool and related topics as I start making my way up the learning curve…

Facebooklinkedin
Facebooklinkedin

Testing Catches Copilot Errors

I’m happy to admit that Copilot makes many of my Windows adventures easier to undertake. It certainly helps a great deal with PowerShell scripting stuff. But just this morning I was reminded that it’s always smart to question — and verify — everything Copilot tells me. In testing a USB4 NVMe enclosure just now, I asked it which of the ThinkPad X12 Detachable Gen 1 left-side USB-C ports is faster, remembering that one is 10Gbps (UASP) and the other 40Gbps (TB4). It replies “the lower port,” so I run CrystalDiskMark on both to check its answer. Once again, I confirm that testing catches Copilot errors. Let me explain.

How Testing Catches Copilot Errors

Simply put, checking what Copilot tells you will either confirm that it’s correct, or show that it’s wrong. As you can see in the lead-in graphic, which places the upper USB-C port left, and the lower one at right, large reads are MUCH faster on the left. That means the upper port MUST be the TB4 one because UASP/10Gbps can’t deliver more than 1,000 – 1,200 MB/s for either reading or writing.

When I showed Copilot the CDM results, it responded as follows:

I had it backwards — apologies for the bad call. The source I pulled from apparently described the ports in board-schematic order rather than physical top-to-bottom position as you see them on the tablet. Your bench test is the definitive answer.

And if you’re seeing typical UASP numbers (~1,000 MB/s sequential) from the lower port right now, that confirms it’s the USB 3.2 Gen 2 controller — exactly what you’d expect at 10 Gbps with protocol overhead.

At least, it doesn’t fight with me when I knock it over the head with contrary results. And when it writes scripts, the PowerShell mostly either works or it doesn’t. In the latter case, Copilot may fumble around for a while but it eventually gets things right.

Trust, But Verify

It’s not unreasonable to believe much, or perhaps even most, of what Copilot tells you. But if you don’t check its work, you’re setting yourself up for trouble. It’s good at finding stuff and presenting theories and explanations. It’s by no means infallible, as I have just shown. Take that into account, when you start leaning on it for help…

Facebooklinkedin
Facebooklinkedin

Copilot Amazon Differ on TB5 NVMe Availability

I’m prepping for an AskWoody  story about RAID 1 setups on Windows 11. It had me popping open my half-dozen or so NVMe enclosures yesterday to see what I had at my disposal. Among my inventory, I found two identical NVMes (ideal for a RAID 1 test). I also found a Crucial T705 1TB PCIe x5 drive, which isn’t suited for any of my enclosures. It really needs Thunderbolt 5 or USB4 v2.0 to exceed the 40 Gbps speed limit that TB4/USB4 imposes. Imagine my surprise when Copilot said no such enclosures were available, while Amazon showed me at least half-a-dozen products for sale right now. Hence my claim that Copilot, Amazon differ on TB5 NVMe availability.

If Copilot Amazon Differ on TB5 NVMe Availability, Try Evidence

I work with Copilot near daily, especially on understanding and fixing Windows problems, issues and misconfigurations. Warnings about AI hallucinations are always worth remembering with Copilot. Why? Because it has repeatedly shown itself to be wrong or — as in this case — misinformed.  I reproduce Copilot’s response to my correction in which I provide the simple Amazon search that showed me 6-plus TB5 capable NVMe enclosures for sale at US$190 and up.

One big problem I see with AI information is that it includes no shades of grey. If Copilot and other AI interfaces could include confidence levels or probability of correctness, that might help. But no: Copilot, Google AI, Grok and so forth put forward their information as gospel truth. There’s a huge gap between Copilot’s initial flat statement that no TB5 NVMe enclosures are available, and its later correction to “TB5 NVMe enclosures exist, but most are early‑generation products whose real‑world performance is currently limited by host support and certification status.” Big difference!

As Always, Proceed with AI Cautiously

I don’t use or act on AI provided info unless and until I can confirm it through at least one (preferably, two or more) reliable public sources. This little “No it’s not; Well, yes it is…kinda/sorta” encounter demonstrates pretty well why that’s so. Indeed, for testing purposes I plan to buy one of the very enclosures Copilot told me yesterday didn’t exist. Today, it’s a different story!

Isn’t that just the way things go here in Windows-World sometimes? But at least, I’m going to be able to see if TB5/PCIe x5 Gen5 technology lives up to its billing when the Acasis enclosure shows up. If things work as reported, I’ll have an external USB drive that’s as fast as the internal drive on my production desktop.

Facebooklinkedin
Facebooklinkedin

Copilot: Driver’s Education

If you read yesterday’s blog, you already know that I spent most of the weekend with my Flo6 desktop in UEFI, booting, or at the command line in WinRE/WinPE. On the other PC next to my desk chair, I keep a Lenovo P16 Gen1 Thinkpad. I was running Copilot on that PC, looking for insight into making Secure Boot work on the Flo6. Simply put, you can’t ask for help in Windows when that OS isn’t running. During that process I ended up in class for Copilot: driver’s education became quite a concern as I had difficulty scrolling down to read longish replies to my prompts and queries.

What Copilot Driver’s Education Is About

Turns out my scrolling attempts were misguided. I didn’t really understand how the touchpad on the P16 works. As you can see in the prompt window I’m using in this post for a lead-in graphic, the P16 touchpad is  more oriented to gestures than to driving screen controls.

While I was working over the weekend, I simply popped in a wired mouse — complete with scroll wheel — and used that to speed scrolling while interrogating Copilot on the P16. After I had time to dig in a bit deeper, I learned that a two-finger gesture works for scrolling that touchpad quite nicely (two-finger sweep up to scroll down, down to scroll up — shades of Doc in the movie Cars).

Hah! I’ve been using Copilot since it first showed up over two years ago (June 2023) and didn’t know that this till this weekend. Probably because I still mostly drive with a mouse and not a touchpad. Now I know. Here in Windows-World, it’s the little things that sometimes make a big difference…

Facebooklinkedin
Facebooklinkedin

Secure Boot Pursuit Undone

We’ve been (and still are, I kid you not) snowed in here in Central Texas. With Winter Storm Fern bearing down on us, we started hunkering down here last Friday (1/23). On Saturday we had rain, sleet and snow, and woke up to snowy sights Sunday. Figuring I had time on my hands, I decided to see if I could get Secure Boot working on my Asrock B550 Ryzen 7 5800X Flo6 production desktop. Alas, after much wrestling with hardware and software, I saw my Secure Boot pursuit undone early, early this morning. Let me explain…

Why Is My Secure Boot Pursuit Undone?

Through all kinds of contortions (see list below) I couldn’t get the PC to boot with Secure Boot enabled. Let me enumerate some of them so you can appreciate what I tried and failed to get done this weekend:

  • 2 repair  installs of my current running OS
  • 1 “dirty install” (do not format partitions, but run installer which moves old OS into Windows.old and creates a new one: IDKYDT)
  • At least 2 each dism /restorehealth, sfc /scannow & chkdsk
  • Remove boot/sys drive from its M.2 slot to wipe NVMe config data from UEFI (have to remove GPU to access slot, sigh)
  • Swapped out old, soon-to-be obsolete 1070 Ti for 3070 Ti GPU.
  • spent over 30 hours fiddling with UEFI and Windows configs

After the “dirty install” I realized I’d hosed the primary MSA login on my main work machine. Not acceptable!! This morning, I built a new Macrium Reflect X Rescue disk, extracted the drivers from the Flo6, and restored my most recent backup (Friday afternoon, after I’d reorganized the boot/sys drive partitions).

Back in Business, Back to Work!

I learned a bunch about boot configuration data and related commands. I’m definitely completely up on booting the Flo6 into WinRE, Windows installer media, and the Macrium Rescue Disk. I’m much better acquainted with the Asrock UEFI than I’ve ever been before.

I also learned that my old MS Comfort Curve 4000 keyboard can’t (or won’t) send Fn key data to UEFI. Working on the ThinkPad P16 Gen 1 I soon figured out scrolling Copilot output was MUCH easier with an external mouse with scroll wheel than using the touchpad. Who knew?

And finally, I learned that Copilot will lead you all over the place trying to solve problems, heedless of time involved and consequence entailed. Sure, AI will tell you pretty much anything about Windows you want to know, but I wasn’t happy with the circuitous routes it took me on, and the circles it spun me through. Then it occurred to me: the words mendacious, malicious, utopia, and paradise all include AI, as do the phrases folie a deux and waste of time. Here in snowed-in Windows-World this weekend, I saw all those things play out. It was oddly engaging, but I’m glad it’s over.

Facebooklinkedin
Facebooklinkedin

Catching Up Can Be Hard to Do

I’ll admit it. I’m lazy. When I hooked up the Lenovo ThinkCentre Neo 50q Tiny PC a couple of weeks ago, I cheated. How? By hooking up the power, networking, video, keyboard, mouse and camera that had previously been driving the ThinkStation P3 Ultra Gen 2 mini-PC. Yesterday, I had some free time so I unhooked the former and reconnected to the latter. Given the hiatus a storm of updates followed (as expected). When I checked Reliability Monitor (ReliMon) this morning, I found a couple of unexpected errors for the Lenovo TSSIOMonitor (aka Super IO Monitor). When I asked Copilot for help reading those tea leaves, its response: “Catching up can be hard, especially after a prolonged idle period.”

Why Catching Up Can Be Hard

As I look at ReliMon for yesterday afternoon, I see a steady stream of updates and installs that start at 3:38PM and run through 4:09PM (60 in all). According to Copilot, TSSIOMonitor.exe is a Lenovo executable that’s constantly monitoring hardware. Its job is to throw errors when things don’t look or work correctly.

One potential cause of the error is when sensor data is invalid. Another is when driver data doesn’t match what the monitor expects. That’s precisely what happens when chipset drivers update, ACPI tables get rebuilt, embedded controllers reinitialize, and Super I/O registers may be unstable. Basically, the monitor was  using stale data to analyze a fresh situation, and erroring because of inevitable mismatches. Good to know.

Copilot Offers Insight, But I Must Assess Same

I’m getting used to asking Copilot to opine on system stuff when I need help understanding what’s going on. It certainly has more access to deep Windows arcana that I do, but I do notice occasional hiccups and hallucinations as it recites specific details. Indeed it sometimes goes off on tangents that don’t relate to my specific situation, but do play into the general circumstances and experiences around it.

This time, Copilot’s explanation makes good sense. And it helps me understand why such errors might occur when they did. It’s even comforting for it to tell me what I already knew: that a one-off or two-off error while a bunch of updates are underway isn’t terribly concerning. But we both agree that if it kept on happening (TSSIOmonitor.exe has been quiet ever since updates finished) there would be cause for concern, and possible action.

What Ronald Reagan said about nuclear arms monitoring apparently also provides to ingesting information from Copilot: “Trust, but verify.” Words to live by, here in a brave new AI-informed Windows-World.

Facebooklinkedin
Facebooklinkedin

Notification Reveals RDP Recall Gotcha

Here at Chez Tittel, there are 9 PCs in my office (6 laptops, 3 desktops). I tend to remote into 8 of those 9, working from my primary desktop. It’s running an Asrock B550 Extreme 4 with AMD Ryzen 7 5800X CPU, 128GB RAM, and an NVIDIA 3070Ti GPU. When I remoted into the ASUS Zenbook A14 this morning, a seemingly innocuous notification popped up in the RDP window, lower right. That notification reveals RDP Recall Gotcha that reads “Recall: Sign-in with Windows Hello to resume, no snapshots are being saved.”

When Notification Reveals RDP Recall Gotcha , Then What?

I followed the notification’s instruction: Walked up to the laptop, and let the camera log me in locally via facial recognition. When I fired up the RDP session again, there was no such notification showing. So, I checked Windows Hello status, and it shows that facial recognition is enabled and working for my phiz.

Then I checked Recall settings. It shows two interesting facets to what is apparently a real and present RDP gotcha:

1. For RDP to work, it’s necessary to turn off “Require Windows Hello login” in Sign-in Settings (aka “enhanced sign-in security”). For Recall to work this must be enabled.

2. Lack of enhanced sign-in security apparently makes the RDP session behave as if Windows Hello is neither enabled nor defined on this system.

Can you say “Catch-22?” Looks like if you want to use Recall on a Copilot+ PC, you can only do so through a local login. At least for me, it doesn’t work through RDP. Good to know! Though I can’t say I like this much, it is important to understand the limitations of Recall for users who might wish to take advantage of its capabilities.

Looks like Recall requires local operation. My conclusion: To use Recall (and I presume other AI features) go local, or go home. It’s always something, here in Windows-World.

 

 

Facebooklinkedin
Facebooklinkedin

Copilot sez: Enough, or Too Much

I’ve been excessively busy for the past few days, working on a legal matter. Along the way, I’ve learned a few things about Copilot’s limits. Turns out this tool is extraordinarily adept at running down references and finding sources that document specific quotes. But it’s also inclined to get stuck sometimes if my queries assume too much about what it already knows. That is, echoing William Blake’s Proverbs of Heaven and Hell Copilot sez: Enough, or Too Much?  Thereupon it becomes unresponsive. Yesterday, I had to reboot a machine to bring Copilot back to life. Even ending the task and restarting the app didn’t help. Weird!

When Copilot sez: Enough, or Too Much,
Do This…

So I had to ask Copilot “Why do you choke or become nonresponsive sometimes?” It had 5 answers, at least 3 of which corresponded to yesterday’s circumstances:

1. Overloaded or ambiguous input: Messages (prompts, I would say) are too long, too vague or contain multiple conflicting instructions.

2, Tool or system glitches: Copilot avers it relies on a whole box of tools (it names “search, image generation, memory, etc.”). Should one fail to respond, Copilot has to wait, and may stall while waiting.

3. Safety or Policy Filters: By design, Copilot won’t respond to prompts that violate its safety and policy rules. Good thing, and I hope they’re sufficiently broad and devious enough to foil hackers.

4. Missing Context or References: It’s too easy to assume Copilot remembers and understands what you’ve been asking it recently. TLDR version: not always. Be specific.

5. Complex Reasoning Bottlenecks: Technical, multi-layered tasks require Copilot to find, assemble and structure lots of information. Takes time, enough so that it might seem like forever.

I’m pretty sure yesterday’s hangup was a mix of items 2, 4 and 5. I try very hard not to overload my prompts, and what I work on shouldn’t trigger failsafes — of any kind. But hey, here in Windows-World, hang-up and delays are all part of the daily routine. Yours too, I guess?

Facebooklinkedin
Facebooklinkedin