diff options
Diffstat (limited to 'doc/Installing_OSX.html')
| -rw-r--r-- | doc/Installing_OSX.html | 590 |
1 files changed, 295 insertions, 295 deletions
diff --git a/doc/Installing_OSX.html b/doc/Installing_OSX.html index fb01e4a..76aa98a 100644 --- a/doc/Installing_OSX.html +++ b/doc/Installing_OSX.html @@ -1,116 +1,116 @@ -<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html>
- <head>
- <meta http-equiv="Content-Type" content="text/html;
- charset=windows-1252">
- <meta http-equiv="content-type" content="text/html;
- charset=windows-1252">
- <meta name="GENERATOR" content="Mozilla/4.73 [en] (WinNT; I)
- [Netscape]">
- <title>Argyll Installation on Apple OS X</title>
- </head>
- <body>
- <h1> <u>Installing the software on Apple OS X<br>
- </u></h1>
- <br>
- You will need to unpack the downloaded file in such a way that the
- files it contains end up in the location you have chosen to hold its
- contents.<br>
- <br>
- If you want to install it system wide, then you probably want to
- unpack it in the <i>/Applications</i> folder, so that it ends up in
- the <i>/Applications/Argyll_VX.X.X</i> folder.<br>
- Another option is just to install it somewhere under your $HOME
- folder, such as <span style="font-style: italic;">$HOME/</span><i>Argyll_VX.X.X</i>
- or <span style="font-style: italic;">$HOME/</span><i>bin/Argyll_VX.X.X</i>,
- depending on how you like to organize your applications and utility
- programs. ($HOME is the shell symbolic name for your home folder,
- typically /Users/<i>username</i>. Another abbreviation for it is the
- ~ character.)<br>
- <br>
- You can unpack it by control-click on the downloaded file and “Open
- With” BOMArchiveHelper or Archive Utility. Drag the resulting folder
- to where you want it, e.g. into <i>/Applications</i>, <i>$HOME</i>
- or <i>$HOME/bin</i>.<br>
- <br>
- Alternatively you can unpack it on the command line using the
- command <span style="font-weight: bold;">tar -zxf</span> <span
- style="font-weight: bold;">archivename.tgz</span>, which will
- create a folder <span style="font-weight: bold;">Argyll_VX.X.X</span>
- in your current folder, where X.X.X is the version number, and the
- executables will be in <span style="font-weight: bold;">Argyll_VX.X.X/bin</span>
- sub-folder.<br>
- <br>
- Open a Terminal shell. This will be in
- Applications->Utilities->Terminal (Dragging it to the dock is
- a good idea to make it more accessible).<br>
- <br>
- You should configure your $PATH environment variable to give the
- shell access to the executable from your command line environment
- without having to spell out the whole path every time, by editing
- your <span style="font-weight: bold;">.profile</span> file, which
- will be in your $HOME folder. You can open a graphical editor on
- this file by using the open command:<br>
- <br>
- open $HOME/.profile<br>
- <br>
- or alternatively, use some other text editor that you are familiar
- with.<br>
- <br>
- Add a line similar to the following line to your .profile file:<br>
- <br>
- PATH=$PATH:/Applications/Argyll_VX.X.X/bin<br>
- <br>
- where "/Applications/Argyll_VX.X.X/bin" is the path to the folder
- that contains the ArgyllCMS executables.<br>
- Save your changes and exit the editor.<br>
- <br>
- If you want further guidance in setting up and using a command line
- environment, then please consult an appropriate tutorial, e.g. <<a
-href="http://heather.cs.ucdavis.edu/matloff/public_html/UnixAndC/Unix/ShellIntro.pdf">ShellIntro</a>>.<br>
- <br>
- The .tgz file also contains several useful reference files (such as
- scanner chart recognition templates, sample illumination spectrum
- etc.) in the <b>ref</b> sub-folder, as well as all the current
- documentation in a <b>doc</b> sub-folder.<br>
- <br>
- For most devices there is nothing special to do. Plug in and go.
- Some devices may not work without some extra help though:<br>
- <h3><a name="ColorMunki"></a><span style="text-decoration:
- underline;">X-Rite ColorMunki</span></h3>
- Some version of X-Rite's ColorMunki drivers released between 2009
- and 2011 install an X-Rite daemon that runs as root and grabs the
- device, preventing any other programs (such as Argyll) from opening
- them. Latter versions seem to be more cooperative, and don't suffer
- from this problem. There are three ways of working around this
- problem:<br>
- <br>
- 1) Turn off the X-Rite service for the ColorMunki. See <<a
- class="moz-txt-link-freetext"
-href="http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980">http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980</a>>.<br>
- <br>
- 2) Run all Argyll programs that need to access the instrument as
- root. For instance:<br>
- <br>
- sudo spotread<br>
- <br>
- and then you will be asked for the root password.<br>
- While these methods will work, they are inconvenient. <br>
- <br>
- 3) Alter the X-Rite drivers Daeomon so that it runs under your user
- account.<br>
- <br>
- To do this you need to edit the script that controls the X-Rite
- Daemon.<br>
- <br>
- cd ~<br>
- whoami<br>
- cp
- /Library/LaunchDaemons/com.xrite.device.colormunki.plist temp.plist<br>
- open temp.plist<br>
- <br>
- and add one child below the root:<br>
- <br>
+<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en"> +<html> + <head> + <meta http-equiv="Content-Type" content="text/html; + charset=windows-1252"> + <meta http-equiv="content-type" content="text/html; + charset=windows-1252"> + <meta name="GENERATOR" content="Mozilla/4.73 [en] (WinNT; I) + [Netscape]"> + <title>Argyll Installation on Apple OS X</title> + </head> + <body> + <h1> <u>Installing the software on Apple OS X<br> + </u></h1> + <br> + You will need to unpack the downloaded file in such a way that the + files it contains end up in the location you have chosen to hold its + contents.<br> + <br> + If you want to install it system wide, then you probably want to + unpack it in the <i>/Applications</i> folder, so that it ends up in + the <i>/Applications/Argyll_VX.X.X</i> folder.<br> + Another option is just to install it somewhere under your $HOME + folder, such as <span style="font-style: italic;">$HOME/</span><i>Argyll_VX.X.X</i> + or <span style="font-style: italic;">$HOME/</span><i>bin/Argyll_VX.X.X</i>, + depending on how you like to organize your applications and utility + programs. ($HOME is the shell symbolic name for your home folder, + typically /Users/<i>username</i>. Another abbreviation for it is the + ~ character.)<br> + <br> + You can unpack it by control-click on the downloaded file and “Open + With” BOMArchiveHelper or Archive Utility. Drag the resulting folder + to where you want it, e.g. into <i>/Applications</i>, <i>$HOME</i> + or <i>$HOME/bin</i>.<br> + <br> + Alternatively you can unpack it on the command line using the + command <span style="font-weight: bold;">tar -zxf</span> <span + style="font-weight: bold;">archivename.tgz</span>, which will + create a folder <span style="font-weight: bold;">Argyll_VX.X.X</span> + in your current folder, where X.X.X is the version number, and the + executables will be in <span style="font-weight: bold;">Argyll_VX.X.X/bin</span> + sub-folder.<br> + <br> + Open a Terminal shell. This will be in + Applications->Utilities->Terminal (Dragging it to the dock is + a good idea to make it more accessible).<br> + <br> + You should configure your $PATH environment variable to give the + shell access to the executable from your command line environment + without having to spell out the whole path every time, by editing + your <span style="font-weight: bold;">.profile</span> file, which + will be in your $HOME folder. You can open a graphical editor on + this file by using the open command:<br> + <br> + open $HOME/.profile<br> + <br> + or alternatively, use some other text editor that you are familiar + with.<br> + <br> + Add a line similar to the following line to your .profile file:<br> + <br> + PATH=$PATH:/Applications/Argyll_VX.X.X/bin<br> + <br> + where "/Applications/Argyll_VX.X.X/bin" is the path to the folder + that contains the ArgyllCMS executables.<br> + Save your changes and exit the editor.<br> + <br> + If you want further guidance in setting up and using a command line + environment, then please consult an appropriate tutorial, e.g. <<a +href="http://heather.cs.ucdavis.edu/matloff/public_html/UnixAndC/Unix/ShellIntro.pdf">ShellIntro</a>>.<br> + <br> + The .tgz file also contains several useful reference files (such as + scanner chart recognition templates, sample illumination spectrum + etc.) in the <b>ref</b> sub-folder, as well as all the current + documentation in a <b>doc</b> sub-folder.<br> + <br> + For most devices there is nothing special to do. Plug in and go. + Some devices may not work without some extra help though:<br> + <h3><a name="ColorMunki"></a><span style="text-decoration: + underline;">X-Rite ColorMunki</span></h3> + Some version of X-Rite's ColorMunki drivers released between 2009 + and 2011 install an X-Rite daemon that runs as root and grabs the + device, preventing any other programs (such as Argyll) from opening + them. Latter versions seem to be more cooperative, and don't suffer + from this problem. There are three ways of working around this + problem:<br> + <br> + 1) Turn off the X-Rite service for the ColorMunki. See <<a + class="moz-txt-link-freetext" +href="http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980">http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980</a>>.<br> + <br> + 2) Run all Argyll programs that need to access the instrument as + root. For instance:<br> + <br> + sudo spotread<br> + <br> + and then you will be asked for the root password.<br> + While these methods will work, they are inconvenient. <br> + <br> + 3) Alter the X-Rite drivers Daeomon so that it runs under your user + account.<br> + <br> + To do this you need to edit the script that controls the X-Rite + Daemon.<br> + <br> + cd ~<br> + whoami<br> + cp + /Library/LaunchDaemons/com.xrite.device.colormunki.plist temp.plist<br> + open temp.plist<br> + <br> + and add one child below the root:<br> + <br> <span style="text-decoration: underline;">Item Type @@ -121,10 +121,10 @@ Type &nbs -
- Value
- </span><br>
- UserName
+ + Value + </span><br> + UserName string @@ -135,63 +135,63 @@ string &n -
- myusername<br>
- <br>
- where "myusername" is your username shown by whoami, and save the
- file. You then need to copy the modified file back: <br>
- <br>
- sudo cp temp.plist
- /Library/LaunchDaemons/com.xrite.device.colormunki.plist<br>
- <br>
- You will then need to restart the machine for this change to take
- effect, or invoke the following commands:<br>
- <br>
- sudo launchctl unload
- /Library/LaunchDaemons/com.xrite.device.colormunki.plist<br>
- sudo launchctl load
- /Library/LaunchDaemons/com.xrite.device.colormunki.plist<br>
- <br>
- <span style="font-weight: bold;">NOTE</span> that after running
- Argyll tools, you may have to turn the X-Rite service off then on
- again, or disconnect and reconnect the instrument.<br>
- <br>
- <h3><a name="ColorMunki"></a><span style="text-decoration:
- underline;">X-Rite EyeOne Pro</span><br>
- </h3>
- Some version of X-Rite's EyeOne Pro drivers drivers released between
- 2009 and 2011 install an X-Rite daemon that runs as root and grabs
- the device, preventing any other programs (such as Argyll) from
- opening them. Latter versions seem to be more cooperative, and don't
- suffer from this problem. There are three ways of working around
- this problem:<br>
- <br>
- 1) Turn off the X-Rite service for the EyeOne Pro. See <<a
- class="moz-txt-link-freetext"
-href="http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980">http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980</a>>.<br>
- <br>
- 2) Run all Argyll programs that need to access the instrument as
- root. For instance:<br>
- <br>
- sudo spotread<br>
- <br>
- and then you will be asked for the root password.<br>
- While these methods will work, they are inconvenient. <br>
- <br>
- 3) Alter the X-Rite drivers Daemon so that it runs under your user
- account.<br>
- <br>
- To do this you need to edit the script that controls the X-Rite
- Daemon.<br>
- <br>
- cd ~<br>
- whoami<br>
- cp
- /Library/LaunchDaemons/com.xrite.device.i1.plist temp.plist<br>
- open temp.plist<br>
- <br>
- and add one child below the root:<br>
- <br>
+ + myusername<br> + <br> + where "myusername" is your username shown by whoami, and save the + file. You then need to copy the modified file back: <br> + <br> + sudo cp temp.plist + /Library/LaunchDaemons/com.xrite.device.colormunki.plist<br> + <br> + You will then need to restart the machine for this change to take + effect, or invoke the following commands:<br> + <br> + sudo launchctl unload + /Library/LaunchDaemons/com.xrite.device.colormunki.plist<br> + sudo launchctl load + /Library/LaunchDaemons/com.xrite.device.colormunki.plist<br> + <br> + <span style="font-weight: bold;">NOTE</span> that after running + Argyll tools, you may have to turn the X-Rite service off then on + again, or disconnect and reconnect the instrument.<br> + <br> + <h3><a name="ColorMunki"></a><span style="text-decoration: + underline;">X-Rite EyeOne Pro</span><br> + </h3> + Some version of X-Rite's EyeOne Pro drivers drivers released between + 2009 and 2011 install an X-Rite daemon that runs as root and grabs + the device, preventing any other programs (such as Argyll) from + opening them. Latter versions seem to be more cooperative, and don't + suffer from this problem. There are three ways of working around + this problem:<br> + <br> + 1) Turn off the X-Rite service for the EyeOne Pro. See <<a + class="moz-txt-link-freetext" +href="http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980">http://www.xrite.com/product_overview.aspx?ID=1161&Action=support&SupportID=4980</a>>.<br> + <br> + 2) Run all Argyll programs that need to access the instrument as + root. For instance:<br> + <br> + sudo spotread<br> + <br> + and then you will be asked for the root password.<br> + While these methods will work, they are inconvenient. <br> + <br> + 3) Alter the X-Rite drivers Daemon so that it runs under your user + account.<br> + <br> + To do this you need to edit the script that controls the X-Rite + Daemon.<br> + <br> + cd ~<br> + whoami<br> + cp + /Library/LaunchDaemons/com.xrite.device.i1.plist temp.plist<br> + open temp.plist<br> + <br> + and add one child below the root:<br> + <br> <span style="text-decoration: underline;">Item Type @@ -202,10 +202,10 @@ Type &nbs -
- Value
- </span><br>
- UserName
+ + Value + </span><br> + UserName string @@ -216,27 +216,27 @@ string &n -
- myusername<br>
- <br>
- where "myusername" is your username shown by whoami, and save the
- file. You then need to copy the modified file back: <br>
- <br>
- sudo cp temp.plist
- /Library/LaunchDaemons/com.xrite.device.i1.plist<br>
- <br>
- You will then need to restart the machine for this change to take
- effect, or invoke the following commands:<br>
- <br>
- sudo launchctl unload
- /Library/LaunchDaemons/com.xrite.device.i1.plist<br>
- sudo launchctl load
- /Library/LaunchDaemons/com.xrite.device.i1.plist<br>
- <br>
- <span style="font-weight: bold;">NOTE</span> that after running
- Argyll tools, you may have to turn the X-Rite service off then on
- again, or disconnect and reconnect the instrument.<br>
- <br>
+ + myusername<br> + <br> + where "myusername" is your username shown by whoami, and save the + file. You then need to copy the modified file back: <br> + <br> + sudo cp temp.plist + /Library/LaunchDaemons/com.xrite.device.i1.plist<br> + <br> + You will then need to restart the machine for this change to take + effect, or invoke the following commands:<br> + <br> + sudo launchctl unload + /Library/LaunchDaemons/com.xrite.device.i1.plist<br> + sudo launchctl load + /Library/LaunchDaemons/com.xrite.device.i1.plist<br> + <br> + <span style="font-weight: bold;">NOTE</span> that after running + Argyll tools, you may have to turn the X-Rite service off then on + again, or disconnect and reconnect the instrument.<br> + <br> <h3><a name="specbos"></a><span style="text-decoration: underline;">JETI specbos @@ -247,69 +247,69 @@ specbos -
- 1201 and 1211</span> and <u>Klein K10A</u><br>
- </h3>
- <br>
- If you are using the <b>JETI</b> specbos <span style="font-weight:
- bold;">1211</span><span style="font-weight: bold;"> </span>and <b>1201</b>,
- or the <b>Klein K10A</b> then you may need to install the <a
- href="http://www.ftdichip.com/Drivers/VCP.htm">FTDI Virtual COM
- Port Drivers</a> (VCP), if they are not already on your system.<br>
- <br>
- <h3><a name="HCFR"></a><u>HCFR Colorimeter</u></h3>
- The default OS X class drivers will grab this device, preventing
- Argyll from accessing it. To overcome this, you need to install a
- codeless kernel extension if you wish to use the HCFR colorimeter,
- that prevents this from happening. From the command line you need to
- create a folder called Argyll.kext somewhere convenient, and then
- place in it one file called Info.plist, containing the following:<br>
- <br>
- ----------------- cut here ---------------------<br>
- <?xml version="1.0" encoding="UTF-8"?><br>
- <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST
- 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"><br>
- <plist version="1.0"><br>
- <dict><br>
-
- <key>CFBundleDevelopmentRegion</key>
- <string>English</string><br>
-
- <key>CFBundleGetInfoString</key> <string>Libusb
- USB device Shield</string><br>
-
- <key>CFBundleIdentifier</key>
- <string>com.libusb.USB_Shield</string><br>
-
- <key>CFBundleInfoDictionaryVersion</key>
- <string>6.0</string><br>
- <key>CFBundleName</key>
- <string>Libusb USB device Shield</string><br>
-
- <key>CFBundlePackageType</key>
- <string>KEXT</string><br>
- <key>CFBundleSignature</key>
- <string>????</string><br>
- <key>CFBundleVersion</key>
- <string>6.0</string><br>
-
- <key>IOKitPersonalities</key><br>
- <dict><br>
-
- <key>HCFR</key><br>
- <dict><br>
-
- <key>CFBundleIdentifier</key>
- <string>com.apple.driver.AppleUSBComposite</string><br>
-
- <key>IOClass</key>
- <string>AppleUSBComposite</string><br>
-
- <key>IOProviderClass</key>
- <string>IOUSBDevice</string><br>
-
- <key>idVendor</key>
- <integer>1243</integer><br>
+ + 1201 and 1211</span> and <u>Klein K10A</u><br> + </h3> + <br> + If you are using the <b>JETI</b> specbos <span style="font-weight: + bold;">1211</span><span style="font-weight: bold;"> </span>and <b>1201</b>, + or the <b>Klein K10A</b> then you may need to install the <a + href="http://www.ftdichip.com/Drivers/VCP.htm">FTDI Virtual COM + Port Drivers</a> (VCP), if they are not already on your system.<br> + <br> + <h3><a name="HCFR"></a><u>HCFR Colorimeter</u></h3> + The default OS X class drivers will grab this device, preventing + Argyll from accessing it. To overcome this, you need to install a + codeless kernel extension if you wish to use the HCFR colorimeter, + that prevents this from happening. From the command line you need to + create a folder called Argyll.kext somewhere convenient, and then + place in it one file called Info.plist, containing the following:<br> + <br> + ----------------- cut here ---------------------<br> + <?xml version="1.0" encoding="UTF-8"?><br> + <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST + 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"><br> + <plist version="1.0"><br> + <dict><br> + + <key>CFBundleDevelopmentRegion</key> + <string>English</string><br> + + <key>CFBundleGetInfoString</key> <string>Libusb + USB device Shield</string><br> + + <key>CFBundleIdentifier</key> + <string>com.libusb.USB_Shield</string><br> + + <key>CFBundleInfoDictionaryVersion</key> + <string>6.0</string><br> + <key>CFBundleName</key> + <string>Libusb USB device Shield</string><br> + + <key>CFBundlePackageType</key> + <string>KEXT</string><br> + <key>CFBundleSignature</key> + <string>????</string><br> + <key>CFBundleVersion</key> + <string>6.0</string><br> + + <key>IOKitPersonalities</key><br> + <dict><br> + + <key>HCFR</key><br> + <dict><br> + + <key>CFBundleIdentifier</key> + <string>com.apple.driver.AppleUSBComposite</string><br> + + <key>IOClass</key> + <string>AppleUSBComposite</string><br> + + <key>IOProviderClass</key> + <string>IOUSBDevice</string><br> + + <key>idVendor</key> + <integer>1243</integer><br> @@ -319,36 +319,36 @@ specbos -
- <key>idProduct</key>
- <integer>91</integer><br>
-
- </dict><br>
- </dict><br>
-
- <key>OSBundleCompatibleVersion</key>
- <string>1.8</string><br>
- <key>OSBundleLibraries</key><br>
- <dict><br>
-
- <key>com.apple.kernel.iokit</key>
- <string>6.0</string><br>
- </dict><br>
- </dict><br>
- </plist><br>
- ----------------- cut here ---------------------<br>
- <br>
- (You can also copy this from the source installation in
- usb/Argyll.kext)<br>
- <br>
- You then need to install it by using:<br>
- <br>
- sudo cp -R Argyll.kext /System/Library/Extensions<br>
- <br>
- supplying the appropriate root password when prompted.<br>
- Reboot the system to activate the extension.<br>
- <br>
- <p><br>
- </p>
- </body>
-</html>
+ + <key>idProduct</key> + <integer>91</integer><br> + + </dict><br> + </dict><br> + + <key>OSBundleCompatibleVersion</key> + <string>1.8</string><br> + <key>OSBundleLibraries</key><br> + <dict><br> + + <key>com.apple.kernel.iokit</key> + <string>6.0</string><br> + </dict><br> + </dict><br> + </plist><br> + ----------------- cut here ---------------------<br> + <br> + (You can also copy this from the source installation in + usb/Argyll.kext)<br> + <br> + You then need to install it by using:<br> + <br> + sudo cp -R Argyll.kext /System/Library/Extensions<br> + <br> + supplying the appropriate root password when prompted.<br> + Reboot the system to activate the extension.<br> + <br> + <p><br> + </p> + </body> +</html> |