Installation Guide: OS X
From UVLayout Docs
Revision as of 07:38, 23 June 2016 (edit) Headus (Talk | contribs) (→El Capitan vs USB Dongles) ← Previous diff |
Revision as of 07:43, 23 June 2016 (edit) (undo) Headus (Talk | contribs) (→El Capitan vs USB Dongles) Next diff → |
||
Line 42: | Line 42: | ||
case anyone else encounters the same problem: | case anyone else encounters the same problem: | ||
- | # Reboot and press CMD + R to go into Recovery Mode. | + | # Reboot and hold Command + R to go into Recovery Mode. |
# Go to Terminal under Utilities. | # Go to Terminal under Utilities. | ||
# Type in '''csrutil disable'''. A comment will be displayed that your csrutil has been disabled. | # Type in '''csrutil disable'''. A comment will be displayed that your csrutil has been disabled. | ||
- | # Reboot normally | + | # Reboot normally. |
Revision as of 07:43, 23 June 2016
|
This page describes how to install or upgrade UVLayout onto OS X systems. Currently only Intel powered Macs running OS X Leopard (10.5) or newer are supported.
UVLayout runs under the X11 environment, but X11 is no longer bundled with the OS X operating system. You can however get a compatible version of X11/XQuartz from ...
We recommend before you install UVLayout that you run X11/XQuartz first, to make sure that it is working OK, and enable the "Focus Follows Mouse" preference (see image right). This only affects applications run through the X11 environment, which is most likely only going to be UVLayout, so don't worry about any adverse effects. To install UVLayout, open the supplied UVLayout.dmg disk image file and follow the instructions in the Read-Me.txt file. If this is the first time you have installed UVLayout, you will need to activate it by cut'n'pasting your license key into the keys file. Instructions on that are here. Known Problems
El Capitan vs USB DonglesIn our own testing, we had no problems with OS X El Capitan recognizing a UVLayout Pro version USB Dongle, but one of our users reported that their dongle wasn't being detected. It turned out that SIP was causing their issues, so they disabled it. Here are those instructions in case anyone else encounters the same problem:
|