Donux Just found a solution. In fact, shockingly, it made NoMachine usable on a laptop where Windows 10 is typically unusable. Working in Windows 10 1809 on ThinkPad T480 (8th gen Intel i5, UHD Graphics 620):
The Solution
Install an Ubuntu MATE 24.04 VirtualBox VM within Windows 10 1809
- (since it's within a VM, this seems to bypass the typical GPU driver issues that newer Ubuntu versions have, which is why I simply use 24.04 instead of an older version)
Disable 2D acceleration in the VM graphics settings
Disable the fullscreen bottom toolbar in VirtualBox UI settings (to ensure the VM runs 100% fullscreen)
Disable the software compositing window manager in Ubuntu MATE's "Window" settings
FWIW, I left MATE's text rendering on subpixel, I actually found it the most comfortable of the options
Turn off Ubuntu automatic updates for good measure
Use the VM in fullscreen.
Install NoMachine within the Ubuntu MATE VM and use it there.
(set up similar NoMachine settings, of course — BTW also keep ditherig.exe running on the Windows side to ensure stuff stays reduced to 6bit if your laptop isn't true 8bit)
Immediate and 100% noticeable difference. SO much less strain.
This is because the non-accelerated Linux VM itself is what makes it super comfortable, so all other Linux apps like Firefox run with way less strain too. Your screen will remain like this until you exit fullscreen and return to Windows 10, which will cause the usual strain to return.
Bonus: you also get less slippery trackpad scrolling within the Linux NoMachine client 😉
Wait, what???
For some totally unknown reason, whenever my VirtualBox VM of Ubuntu MATE 24.04 is running fullscreen, the strain that I experience in Windows (and by extension, the Windows version of NoMachine on this laptop) pretty much vanishes. Everything looks flat and solid color backgrounds look so much more relaxing while the Linux VM is fullscreen.
In fact, the fullscreen VM is more comfortable to me than running Linux natively (which in that case, was only marginally more comfortable than Windows 10 on my T480)
Of course, this is super weird and it doesn't seem like this would work at first because Windows 10 is technically still the thing running behind this all, but the VM consistently stops strain for me every single time.
While running Windows, even with ditherig.exe, I usually need to wear "everything becomes pure deep shades of red" monochrome color filter glasses in order to use this laptop (which surprisingly get the job done! As long as I'm wearing the glasses and essentially viewing this laptop without color, I can use this laptop for many hours. But when I'm not using the glasses, Windows 10 on the T480 becomes unusable after only 10 minutes, and it doesn't matter if Intel graphics drivers are enabled, disabled, or downgraded, I get the same strain. It's even worse on 22H2 which is why I'm on 1809.)
BUT… whenever the Linux VM is fullscreen it's seriously a night and day difference. I immediately feel like I don't need the glasses anymore. I can use this laptop very comfortably in full color as long as the VM remains in fullscreen(!!) — even if Intel drivers remain enabled in Windows (however, Intel drivers were downgraded to earliest possible version, if that matters.)
I'm writing this post on "NoMachine inside VirtualBox inside Windows" without any strain. BTW, NoMachine still runs perfectly fine at full speed within the VM.
And yes, the strain returns for me immediately after hiding the VM and switching back to Windows.
Trying to figure out why
It's not because of the Windows UI design or text rendering, because I put a PNG screenshot of Windows within the VM and suddenly I could view that single "freeze-frame" of Windows without strain. I have a more detailed theory that I will make a thread about later, but what I'm generally thinking is that it's related to a specific type of strain-inducing illusion-like color/contrast enhancement method (in fact, not temporal and unrelated to dithering) that I'm becoming pretty confident is used by Windows 10 and 11 — that somehow VirtualBox is able to bypass.
What led to this theory is that I've noticed that solid black vertical lines look different on the fullscreen VM vs. on usual Windows. On the VM, the lines actually look like deep black ink to me. On Windows, there is a very faint hint of color fringing (that is there regardless of ClearType on or off — it's not related to ClearType and affects more than just text).
I've consistently repeated this same exact experience switching between Windows and the fullscreen Linux VM every day for 2 weeks now. This is why I am finally posting this — I know this is not placebo.