CAT-Tools/DéjàVu X/Does DVX run on Mac or Linux too?
Mac OS X
[edit | edit source]No DejaVu version runs natively under Mac OS X. You have to use either a virtual machine solution or an API layer. These are known - so far:
- Parallels (http://www.parallels.com/), virtual machine, known to work with Windows + DVX installed, good Mac integration. DejaVu Dongle works.
- CrossOver Office (http://www.codeweavers.com/), API layer, runs, has some issues to be solved before working as it should. Dongle doesn't work yet. Please see http://www.codeweavers.com/compatibility/browse/name?app_id=205 Feel free to contribute!
Linux
[edit | edit source]No DejaVu version runs natively under Linux. You have to use either a virtual machine solution or an API layer. These are known - so far:
- CrossOver Office (http://www.codeweavers.com/), API layer, has some issues to be solved before working as it should. Dongle doesn't work yet. Please see http://www.codeweavers.com/compatibility/browse/name?app_id=205 Feel free to contribute!
Unix
[edit | edit source]So far, nobody seems to have tested running DejaVu on any Unix system, but with CrossOver available for both Mac OS X, Linux and Solaris, and Mac OS X being built on BSD, it might work (e. g. with Parallels). Possibly even via thin client, which may however run into dongle issues.
Notes on technology
[edit | edit source]- Virtual machine: You install Windows into a virtual machine, which is software that behaves to Windows as if it were PC hardware. Any other software you want to run is installed "as usual" in that Windows system. The current development goes towards making the operating systems aware of being run in a virtual machine, which might enhance performance and get rid of some hardware access problems, like e. g. dongle handling.
- API layer: Presents the software you want to run with the interface towards the operating system it was made for and expects, in this case Windows. The other side of the interface is in this case connected to Linux, Mac OS X, Solaris UNIX etc., rather than leading to Windows. This approach rids you of having to use Windows altogether, and of introducing an additional layer for the virtual machine. Unfortunately, it instead introduces problems for software that wants direct hardware access, most notably for the dongle - so far.