I think all the existing answers are on the basis of creating a new Linux VM.

And if I understand you correctly, you already have a bare metal Linux install that you want to run whilst Linux is up.

This is the best search result I could find: https://forums.virtualbox.org/viewtopic.php?t=93437

It sounds like Virtualbox will indeed create a pseudo vhdx that points to a real partition, but windows is going to give you permissions drama.

The above link is out of date though, so its best viewed as info rather than guide.

Good luck.

A lockdown browser?

If you need to use windows because of a software issue, not a hardware issue, you’re probably best off running windows in a VM.
That way your linux install is making the WPA3 connection, and as far as the Windows install is concerned, it’s on a wired lan.
This has the added benefit of not having to reboot, you just always start linux and turn the windows VM on and off as required.

I agree, that’s why I said “and able”

You can interoperate with googles RCS.
If you are willing and able to enter a partnership like Samsung, you can do it fully (including encryption support etc).

Google are determined to not make it easy, and I agree with you, it appears to be yet another messaging land grab.

Trying to put myself in their headspace for a moment, one justification for making it hard is to stop thousands of apps coming out declaring “full RCS support!” through the APIs, then screwing the pooch (through poor security or deliberate back doors or or or).
Right now Google are desperately attempting to make RCS happen, after almost a decade of trying and failing to make various carriers play ball.
They do not want any bad press about how feature poor/insecure/slow/buggy it is right now.

Only Google can make an RCS app

Yes and no.
You don’t need to make your own OS, but you do need to implement support for the RCS protocol within your app, rather than piggyback on Googles APIs.

I don’t like it, but there’s no legal requirement for google to provide those APIs, like they did with SMS etc.

Windows XP is basically firmware at this point, and has been for over a decade.

Lots of proprietary hardware that works perfectly, will not work on newer versions of Windows due to lack of drivers.

I see it constantly in factory situations with scales, scanners and robot controllers, it would only be worse for million dollar x-ray machines.

I don’t think it’s strictly compliant, although they claim to have based it’s syntax on Korn shell, which is the strictest definition of POSIX shells.

You can do pretty much everything in powershell that you can do in something like bash BUT, it will be done slightly differently, so trying to make a script cross compatible is pointless (you might as well just write it natively in powershell etc).

Powershell isn’t inherently bad, unlike bash for instance which just allows piping out text output, Powershell can pass around true .net objects.
But if what you’re looking for is cross OS compatability, you’re pushing shit uphill.

99.9% of the time, I open powershell and just ssh into a “real” linux box.

FOSS is enshitification-hardened, not proof.

VLC remains awesome because the guy (maybe Jean-Baptiste Kempf?) that controls the project has refused to be bought, has in fact refused HUGE sums of money.

The original author of any project has to right to sell it with the corresponding licence changes at any time.
There’s some legal grey area on something like Linux or VLC which have MANY MANY developer hands in the pie, and existing users could certainly fork off the existing releases, but VLC could pivot tomorrow to a for profit company and make future releases of the official VLC a paid product, if they choose too.