End of Support for Personal Capture
August 30th, 2019: The download links for PCAP will be removed from the platform. This is also the end of support date for these applications in Europe, Middle East, and Africa (EMEA). While the applications will likely continue to work for the rest of the year, there will be no support available. Clients in the EMEA region should plan a full transition to Universal Capture before this time. Clients in other regions can continue to use existing PCAP installations but will no longer have the ability to download it.
January 15th, 2020: This date marks both the end of life and the end of support for these applications globally. As of this date, PCAP will cease to work with the Echo360 platform due to enhancements in the capture pipeline that will only work with Universal Capture. It is of utmost importance that all Echo360 clients complete their transition to Universal Capture by this time.
Command line installation of Personal Capture Windows is nearly identical to Command Line Installation of Classroom Capture. Refer to those instructions if using a command line to install PCAP Windows.
Personal Capture (PCAP) for Mac allows for command line installation (or unattended) of the software via command line execution on the target computer.
The command line install process is nearly identical to the standard installation process except that you will use a configuration file to identify the installation directory (rather than entering or confirming the location via a wizard), and of course, you will initiate the installation via a command line.
PCAP for Mac is supported on Mac OS X 10.10 through 10. 12.
You cannot use these command line instructions to install PCAP on Mac OS 10.12 Sierra. You must use the UI installer instead. See Install Personal Capture for Mac for instructions.
Finally, you do not have to remove the previous version of PCAP to install a newer version. However, users can launch future upgrades by clicking the "upgrade" message that appears in the bottom status bar of the PCAP application window.
- Create a configuration file to use for all of the installations.
- Ensure that all target Macs are running at least Mac OS 10.10.
- Download the installer to each target machine.
- Run the installation command.
The configuration file for command line installation of PCAP Mac requires only a single parameter that identifies the installation directory for the application.
For example, using the typical default installation directory identified in the installation wizard, the configuration file would read:
Create a text file containing this parameter and save it in a location accessible to the installer.
The instructions on this page assume the name of the file is config.txt, and that the file has been saved to the target computer's desktop.
You may include other parameters if you want to initiate debug logging during installation, however, this is not required.
The installation procedure provided below assumes the following:
- The installation file was downloaded and you know the directory into which it was saved.
- The directories identified in the configuration file can be created on the target Mac.
- You know and can include the fully qualified path to the configuration file.
To install PCAP Mac via command line:
- Open the Terminal.
- Navigate to the directory where the installation executable was saved. By default, this is:
- Enter the following commands to adjust the permissions needed for this procedure:
chmod +x Echo360\ Personal\ Capture && chmod +x osx-intel && chmod +x installbuilder*
- Run the installation using the configuration file parameters. Be sure to use the fully qualified path to the configuration file.
The example command shown below assumes the configuration file is saved on the Academic Staff member's desktop on the target computer. Replace ~/Desktop/ with the appropriate directory/path.
./installbuilder.sh --mode unattended --optionfile ~/Desktop/config.txt
- The installer GUI is launched; click OK on any notification messages you may receive.
- When the installer is finished, close the Terminal window.
If you have problems with the installation, you can turn on a higher level of error messaging by adjusting the "debuglevel" option in the configuration file and specifying the location of the debug results. The most "verbose" debug level is level 4, and should provide you with sufficient information.
An example configuration file for additional debug logging:
The example above assumes the debug file name being created is "debug.txt" and that it is being saved on the Academic Staff member's desktop on the target computer. Replace "debug.txt" with the appropriate filename and ~/Desktop/ with the appropriate directory/path.