Compatibility
An application made for another system.
Many of them run on Cyclop OS, through a translation layer. Here is how to install it, what to expect, and when to stop trying.
First, look for the real thing
Cyclop Store holds about 4,850 applications, and for most needs one of them runs natively. Native is faster, it updates with the system, and it does not break with the next version of anything.
Double-click a downloaded executable and Cyclop OS speaks up before it runs: it says the file is not one it recognises, and when it knows an application that does the same job it offers to install that one instead. You can always carry on at your own risk, and it says that too.
Install the compatibility layer
- Open the applications menu and look for Windows App Support
- Open it. It opens the software page that installs it
- Install it. It brings the translation layer and the tools around it
It is part of the paid editions (Education, Pro, Gaming and Enterprise). On Community the package is not in the repository, so it cannot be installed.
Run the application
Once the layer is installed, an executable you open runs through it. For a simple application, nothing else is needed.
An application with several components is better installed in a container of its own, which is what the tools installed alongside the layer are for. A broken installation then stays in its own corner instead of spoiling everything else.
Games go another way
Steam carries its own compatibility layer, and the Gaming edition adds an application that checks a title before you buy it: whether it is known to run, and whether its anti-cheat allows it. The second question is what decides most cases, and it is the one people find out too late.
What to expect, honestly
Plenty of applications run as they are. Some run with quirks. Some do not run at all, and no amount of configuration changes that: an application whose anti-cheat refuses this system will refuse it tomorrow as well.
The order that costs the least time is: a native application, then the web version, then the compatibility layer. In that order.
If it does not work
- Nothing happens on a double-click: the layer is not installed, or the file is not marked as executable.
- It installs and then will not start: try it in a container of its own rather than in the shared one.
- A game refuses over anti-cheat: that is the publisher’s decision, not a setting on your machine. Check a title before buying it.