summaryrefslogtreecommitdiffstats
path: root/Documentation/user-manual.txt
diff options
context:
space:
mode:
authorGravatar Dirk Hohndel <dirk@hohndel.org>2013-02-18 11:25:37 -0800
committerGravatar Dirk Hohndel <dirk@hohndel.org>2013-02-18 11:25:37 -0800
commit8362a22f9f4fb2c5d57ac906c2e39fe97245326d (patch)
treea88204e56f6519d0ba3a2cce5c64c64cfa593d48 /Documentation/user-manual.txt
parentf52486e4e163aec29c263a2e37cb1239084e1e2f (diff)
downloadsubsurface-8362a22f9f4fb2c5d57ac906c2e39fe97245326d.tar.gz
Documentation: minor rewrite of the Mac Driver appendix
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Diffstat (limited to 'Documentation/user-manual.txt')
-rw-r--r--Documentation/user-manual.txt16
1 files changed, 8 insertions, 8 deletions
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index dd8a380bf..e5b8470ab 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -786,27 +786,27 @@ Zeagle:::
Appendix B: Mac OSX Driver Installation
---------------------------------------
-Working out which driver to use for a Mac requires for a particular dive computer can
+Working out which driver to use for a Mac when using a particular dive computer can
require some experimentation. The libdivecomputer website provides a useful point from
which to start: http://www.divesoftware.org/libdc/drivers.html. It lists a number of
sites for manufacturers of the serial to USB chips which provide the necessary conversions.
Here you have two alternatives. Either you try each of the major drivers in turn until
you find the right one, or you follow some further steps to try and identify the right
-driver up front. To determine the required driver up front, first attach the USB to device
-connector cable. Next open a terminal window and run the command:
+driver up front. To determine the required driver up front, first attach the USB download
+cable for your dive computer. Next open a terminal window and run the command:
system_profiler SPUSBDataType > usb.txt
-you should end up with a file (usb.txt in this example) which contains the VID/PID information
+You should end up with a file (usb.txt in this example) which contains the VID/PID information
which can then be used with the URL above to narrow the field. Just open the text file and
compare the information with the table in the drivers section of the web page. This should
-point you to the relevant driver manufacturer. Typically, one then needs to navigate to the
+point you to the relevant driver manufacturer. Typically, you then need to navigate to the
relevant sub page for "drivers" and then the one for "VCP drivers." VCP stands for Virtual
Com Port. You want VCP rather than D2XX drivers, for example. Make sure to download the correct
version for your particular version of OS X.
-These can be downloaded to the Mac and installed in the usual way. Details on how to
+Downloaded that driver to your Mac and install it in the usual way. Details on how to
install on OS X 10.8 differ from earlier versions due to the new security functions.
Put simply, unless the driver has been digitally signed in an approved way OS X will
block the installation. You can either make some changes to your system security settings
@@ -824,7 +824,7 @@ goes like this:
You can find a high-level explanation of the new security features from apple here:
https://www.apple.com/osx/what-is/security.html.
-Until you have the correct driver installed, subsurface will not connect to your dive
-computer. If you try one VCP driver and it still doesn't work, try the next manufacturer
+Until you have the correct driver installed, subsurface will not be able to connect to your
+dive computer. If you try one VCP driver and it still doesn't work, try the next manufacturer
until it does. If you run out of drivers and still can't get things working perhaps
it is time to contact us via the subsurface mail lists.