It is astonishing that so little has changed in almost 30 years. Despite visual differences, menus and windowing in general is almost exactly the same.
Web based Windows XP desktop recreation, built with React
131–140 of 156 posts
Re: Web based Windows XP desktop recreation, built with React
#132Run it at full screen and can't back to the browser view. All function keys are captured. Nice. Now add Excel or Word to it. Running it at full screen would be a nice "I'm working hard" wallpaper for the people peeping over your shoulder.
Re: Web based Windows XP desktop recreation, built with React
#133Earlier quoted context omitted.
I can somewhat understand having to compile for XP (it's been 20 years but... legacy, I get it). However compiling on XP must be hell. Do you mind me asking what you do that requires this?
Aerospace. A specific instrument requires that its code is compiled with a gcc version from the nineties . It has been working since then and introducing a new compiler would change the binary generated, thus nullifying all the accumulated flight hours. And why windows XP? Well, the gcc binary is 16 bit...
Re: Web based Windows XP desktop recreation, built with React
#134Re: Web based Windows XP desktop recreation, built with React
#135Re: Web based Windows XP desktop recreation, built with React
#136Re: Web based Windows XP desktop recreation, built with React
#137Earlier quoted context omitted.
I can somewhat understand having to compile for XP (it's been 20 years but... legacy, I get it). However compiling on XP must be hell. Do you mind me asking what you do that requires this?
Aerospace. A specific instrument requires that its code is compiled with a gcc version from the nineties . It has been working since then and introducing a new compiler would change the binary generated, thus nullifying all the accumulated flight hours. And why windows XP? Well, the gcc binary is 16 bit...
Surely making a code change and recompiling would also change the binary?
Re: Web based Windows XP desktop recreation, built with React
#138I am very disappointed in the lack of response from Explorer > Help > Is this copy of Windows legal?
In a moment of serendipity, I was just finishing up a tiny project prompted by a moment of nostalgia: installing a Windows XP system under VirtualBox and getting the internet working on it. I always had fond memories of Win2k and WinXP and I wanted to know if my feelings today would match what I remembered, or if I was just seeing the past through rose-coloured glasses. I couldn't get IE to co-operate with modern bro…
Windows 10 will ask you questions about many privacy/diagnostics/tracking-related options during setup. Here’s a YouTube video of someone picking the wrong answers for all the questions: https://www.youtube.com/watch?v=TvgL2NI22Ks
Re: Web based Windows XP desktop recreation, built with React
#139Earlier quoted context omitted.
Aerospace. A specific instrument requires that its code is compiled with a gcc version from the nineties . It has been working since then and introducing a new compiler would change the binary generated, thus nullifying all the accumulated flight hours. And why windows XP? Well, the gcc binary is 16 bit...
Doesn't Windows 10 have a 32-bit version as well?
Re: Web based Windows XP desktop recreation, built with React
#140Earlier quoted context omitted.
My goto test: Does it crash my virtual machine? Some of the most basic websites trigger a serious (and still unresolved after years...) bug where the rendering stutters to a halt until virt-manager and all my VM windows crash. Just basic landing pages with weird animated backgrounds, etc. Nothing rich. This app? It works almost flawlessly with little jank and doesn't even stress my browser. And it has a much richer U…
Huh. What VM configuration and guest OSes are you using? Exactly what is crashing? I presume qemu itself, but can't tell if you're describing BSOD type events. Can you reproduce the crashes using qemu-system-x86_64 directly?
I can reproduce the crashes by going to a number of websites. I always assumed it had something to do with OpenGL but lately it's happening on websites that I doubt are running any accelerated content. So it could be the browser's hardware acceleration.
But essentially it takes down virt-manager/virt-viewer and I have to launch another instance. The machine itself is fine but it becomes a race to close the tab before the window crashes again.
It's been a while since I tried debugging but I'm pretty sure that it happens whether or not hw acceleration is enabled in Firefox and it also doesn't matter whether the libvirt XML configuration enables OpenGL or not.
By directly, do you mean just running the virtual machine through the cli or actually setting all my configuration flags in the qemu-system-x86_64 command?