A'ight, so it seems that using a VNC server under Linux has proven difficult, so I'll spin up a W7 VM (I'm not too confortable with the command line, well to a certain degree), and use Tightvnc...
Fingers crossed that this won't turn into a Druaga1-esque moment (for the uninitiated, druaga1 is a YouTuber who does videos about computers, Macs beige box PCs among other stuff, and his videos often end up in hilarious mishaps, such as one time where he tried to install Linux on a Power Macintosh G5).
In the meantime, I'll probably try to secure a Mac Pro 1,1 (don't need a powerhouse for this experiment), this should be easier to set up than my épave d'ordinateur (=a PC that barely works) that works half of the time.
I sure didn't expect this challenge to be greater than I was expecting it to be.
Fingers crossed that this won't turn into a Druaga1-esque moment (for the uninitiated, druaga1 is a YouTuber who does videos about computers, Macs beige box PCs among other stuff, and his videos often end up in hilarious mishaps, such as one time where he tried to install Linux on a Power Macintosh G5).
In the meantime, I'll probably try to secure a Mac Pro 1,1 (don't need a powerhouse for this experiment), this should be easier to set up than my épave d'ordinateur (=a PC that barely works) that works half of the time.
I sure didn't expect this challenge to be greater than I was expecting it to be.
it's just a bit scuffed up), I won't be able to update much (and besides most of the work I do require Windows, there's no other way around this I'm afraid), so I'm still on the process of finding a suitable machine for VNC, my two "low power" Intels are out (they only have WiFi and VNC over wifi is unusable) and my HP Pavilion rig is too unstable for VNC (even trying to set a VM proven to be impossible without having a inevitable crash).