I believe 3.0 finally moved to Python 3. Resynthesizer was also totally rewritten for 3.0, but I don’t think it’s in Python anymore (?).

Lucky for me, I upgraded both my desktop and laptop to 2TB SSDs before they decreed that the peasants can’t have SSDs or RAM anymore.

I get the complaints of lackluster writing in SNW S3, but also, you haven’t seen truly bad media until you’ve watched either Twisters or Beetlejuice, Beetlejuice, which makes Discovery season 2 seem downright straightforward and well-written by comparison.

It’s not the best consolation, but it could go much worse. Also, I feel like if I had a choice, I’d take being strapped to a chair and forced to watch SNW season 3 looped 2.5 times over the same for TNG season 1.

Unless it does something egregious, I’ll probably push myself through it no matter what for the sake of completionism.

Speaking of which, I need to do that for Disco’s last couple seasons before I start the show.

I read it through my library, which keeps a good stock of Trek comic volumes. I think I now also have a PDF of it from a Humble Bundle.

You forgot somebody, and he’s very mad:

My biggest worry is what they do with the Klingons in the 31st century; they’re probably going to talk about how war-torn and poor Qo’Nos is or have the planet have gotten blow up or something dumb like that.

I’d love to have it so that either Qo’Nos surprisingly has had its crap together and managed to avoid brutal civil wars post-burn, with the result being in defiance of all expectations, it was one of the better planets to get stuck on after the Burn.

This guy is low-key the Gowron of the Orions. I kind of hope he shows up again in one of the two later seasons.

Post system specs here just to be safe. If it’s an older machine, there could be various hardware failures. “Monitors” makes it sound like a desktop, but you should clarify just to be safe, and perhaps indicate if has PCIe slots or is more of a mini PC.

Also, what do you mean by “monitors going dark”? Are the backlights on, or are they absolutely dark?

It’s probably not Secure Boot. I mean, worth a test, but it sounds like the issue occurs in the middle of a running session, which is not consistent with the issues sometimes presented by Secure Boot.

Honorary mention: IDW Picard’s Academy was a fun enough read.

It’s solidly okay. I wish it were in brush form like Photoshop was, and I wish it were better-optimized; it’s written in Python and a bit slow. I think Photoshop GPU accelerates this.

Still, usable for a lot of things.

To be fair, I think there are more reasons to pay for Netflix than there are reasons to pay for Paramount+ that don’t rhyme with “Schmar Schmeck”.

And honestly, I’m looking to just switch to a Blu Ray/DVD collection; with Lower Decks and Prodigy over, I might as well just have their series BluRays. Maybe I’ll come back for SNW seasons (and maybe SFA if worth it) so the show can get some ratings or whatever.

As to avoid giving Paramount geezers cash, I’ll probably try to buy used from local businesses.

For DS9 and VOY, though, I’ll probably just buy DVDs for plausible deniability and then torrent one of the many upscales. There’s supposedly a nifty project where someone’s using a Domesday duplicator to rip DS9 and VOY seasons’ laser discs with Domesday duplicator because the DVD transfers of those seasons are so horrible.

I usually use my device’s native boot menu these days; booting through GRUB usually triggers the Bitlocker screen.

Sounds like a freak accident rather than the fault of the VM.

I literally use a GPU for passthrough on my Windows 10 (and macOS) VM; PCIe is a much more complex protocol and much easier to F up than USB.

I’ve used my iPhone many times through Windows and been fine, as well as whole USB keyboards and mice (just simple ones); I think I might have even updated an iOS device once, though I can’t remember if I actually did. I’ve also used an iPod Nano 7th through an 11 LTSC VM before.

I could see some things being a little finicky, but simply managing a Zune with a VM probably causes no issues. It’s probably been eons since it got a firmware upgrade anyway.

That’s just a VM running atop Docker container; convenient, perhaps, but a little misleading to users who don’t understand how Docker works and might think it’s better performance-wise than a VM.

I’d love to see those on him in one of the scenes in Star Trek: Klingon where he angrily shakes you…

Dual boot isn’t that bad if you just use separate drives; the issue is only with Windows and Linux on one drive.

It’s not possible on all devices, but my laptop has dual NVMe slots, and I used to boot Linux off an SATA SSD and Windows off an NVMe on my desktop before getting rid of Windows and moving my Linux install to the NVMe drive. Never had a problem.

The only hiccup you’ll probably run into is exorbitant storage prices, although you can probably opt for less storage (256GB or 512GB), you can still get well below $100 and have it be perfectly fine.

It might be possible, depending on if the screen is connected to the dGPU or iGPU (I’d guess iGPU). I wouldn’t know because I did my setup on a desktop with two dGPUs. I would think it’s possible, but you might need an external monitor (?). I don’t know how Optimus laptops are wired.

Where I started for GPU passthrough, which got me ~90% of the way there, is https://github.com/bryansteiner/gpu-passthrough-tutorial . Gives you the shell scripts, XML, etcetera needed to do it; I had to modify some bits (some of which you can see in issues), but this is my preferred tutorial. Basically, try it, get really frustrated, take a break for a while, get back to it and keep tinkering with it (check permissions, logs, PCIe driver binds, etcetera), and eventually, you’ll figure it out.

https://github.com/mysteryx93/GPU-Passthrough-with-Optimus-Manager-Guide is linked in one of the issues and specifically concerns your kind of laptop.

I might be able to send over some of my XML to get you started, but I don’t know how helpful that will actually be over the tutorial, as our systems are completely different, and the AMD GPU I use has different bugs/quirks when doing this than Nvidia ones. The truth of the matter on why there’s not really a single-click, easy way to do GPU passthrough is because each system is unique, from the motherboard PCIe implementation to bugs in GPU firmware. That doesn’t mean you shouldn’t try, but it takes a bit of ingenuity.

To be fair, I’ve heard Wii U isn’t particularly pleasant running Linux either. I’ve never run Linux on my homebrewed Wii U, but someone in my Linux Users Group brought theirs in once.