WINDOWS SYSTEMS

 

For Windows systems, you must run the provided .bat (batch) files as an administrator. No other setup or permissions are required.

Use the Right-Click Menu
To run the batch file as an administrator, use the context menu.

1)   Right-click the .bat file.

2)   Click Run as administrator from the menu.

3)   Click Yes on the User Account Control (UAC) if prompted to do so.

 

 

MACINTOSH SYSTEMS

 

For Macintosh systems, you may receive an "unknown developer" error when attempting to run the provided command files. There is a single script named Set-Command-File-Permissions.command that you can run to set the correct permissions for the other command files in the folder.

Before running Set-Command-File-Permissions.command, you must set its own permissions manually. Please follow the steps below to set the permissions on this file. Then, just run the file one time and the other scripts will be ready to go.

Use the Terminal to Set Permissions

A) Remove the Quarantine Flag

Completely remove the hidden "quarantine" flag that macOS attaches to downloaded files.      

1)   In Terminal, type the following command followed by a space (not a return):

xattr -d com.apple.quarantine

2)   Drag and drop the .command file from Finder directly into the Terminal window to automatically paste its exact file path.

3)   Press Enter. 

B) Make the File Executable

Next make sure the file is executable.

1)   In Terminal, type the following command followed by a space (not a return):

chmod +x

2)   Drag and drop the .command file from Finder directly into the Terminal window to automatically paste its exact file path.

 

3)   Press Enter.

C)  Ensure macOS Line Endings

If you see an immediate error similar to “/bin/bash^M: bad interpreter: No such file or directory logout”, then the file does not have macOS line endings. Do the following to correct this:

1)   In Terminal, type the following command followed by a space (not a return):

sed -i '' $'s/\r$//'

2)   Drag and drop the .command file from Finder directly into the Terminal window to automatically paste its exact file path.

3)   Press Enter.

 

 

Your .command file Set-Command-File-Permissions.command is now ready to run. Run this command file one time. If no errors, the other test scripts are now ready to run as well.

If you encounter any specific error codes or permission denied messages while attempting these steps, please contact tech support.