51–60 of 188 posts
This system works by launching an official Windows image in Docker and then making an RDP connection to it. There are a couple of others too now like WinBoat What all of them avoid mentioning is that the images were intended by Microsoft for test and development purposes on Windows and the license clearly states you need a valid Windows license to use them: https://hub.docker.com/r/microsoft/windows#license I wonder…
https://get.activated.win wouldn't be online if microsoft cared.
Earlier quoted context omitted.
Last time i checked a Windows 10 and 11 license does not permit running Windows in a virtualized environment. That could have changed by now.
Last time I checked I did not agree to be bombarded with ads and have all my data tracked after paying 100+ for a piece of software...
(Friendly reminder that legality, once again, ≠ morality. Victimless crimes can be illegal, and Enron fucking shit up and filing bankruptcy can be legal.)
Earlier quoted context omitted.
I'm using MS Office for Work in the browser. But I just live with the shortcomings specifically in PowerPoint where I can't do connectors for example.
She only uses that laptop for MS Office. She did actually use the browser version for a few months, but even that is a significant downgrade compared to native apps. MS Office and most popular multiplayer games are the 2 biggest hurdles for Linux adoption at the moment.
I see it's time for the bimonthly reinvention of VirtualBox and VMWare's seamless modes from a few faceless techies on GitHub and designed for people who can't be bothered to use WINE or VirtualBox.
Thing thing uses RDP for communication which was designed for remotely administering servers over low speed networks.
VirtualBox in contrast integrates at the driver level, and allows you to share the underlying GPU buffers, giving you a native experience that works for things like games or heavy apps. It integrates the Linux filesystem on a driver level as well.
I see it's time for the bimonthly reinvention of VirtualBox and VMWare's seamless modes from a few faceless techies on GitHub and designed for people who can't be bothered to use WINE or VirtualBox.
Except these seamless modes have been broken for many years. Also using a containerized Windows means one doesn't have to fiddle with the insane Windows 11 setup process and TPM issues.
I see it's time for the bimonthly reinvention of VirtualBox and VMWare's seamless modes from a few faceless techies on GitHub and designed for people who can't be bothered to use WINE or VirtualBox.
As someone who is looking to go Linux, do most windows apps work now through Wine or VirtualBox ? I know Valve did a lot of work for games. It’s been 4 years since I even took a good look at it.
So essentially the WSL in reverse? I'm kind of surprised you can "run Windows" in a Docker container at all. Isn't the fundamental restriction of Docker that all containers share the same (linux) kernel? Is there a way for docker to inject a "translation layer" somehow that makes it look like an NT kernel for the Windows processes?
I see it's time for the bimonthly reinvention of VirtualBox and VMWare's seamless modes from a few faceless techies on GitHub and designed for people who can't be bothered to use WINE or VirtualBox.
And unfortunately it has become the norm in open-source to push out shiny-looking projects with pretty logos and UX but shoddy underlying technology and deceptive/overstated claims (looking at you Tauri). Thing thing uses RDP for communication which was designed for remotely administering servers over low speed networks. VirtualBox in contrast integrates at the driver level, and allows you to share the underlying GPU…
Hard things become easy when for example it becomes feasible to connect to RDP instead of mucking about at the driver level.
It will be more reliable but less performant.
This system works by launching an official Windows image in Docker and then making an RDP connection to it. There are a couple of others too now like WinBoat What all of them avoid mentioning is that the images were intended by Microsoft for test and development purposes on Windows and the license clearly states you need a valid Windows license to use them: https://hub.docker.com/r/microsoft/windows#license I wonder…
I don't get it. Is it a VM in a container? Skimming https://hub.docker.com/r/microsoft/windows I would have interpreted that as a native Windows container, which I vaguely recall being a thing, but that would require an NT host, not Linux.