You have told us the machine, so this page skips straight to the licence and then to installing it on 32-bit linux. Not your machine?
MCPRO is written by William L. Jorgensen and licensed by Cemcomco LLC. It is free to use under the non-profit licence, but it is not public-domain software: installing it means accepting a licence. The form below records that acceptance and then starts your download.
For 64-bit Intel/AMD systems. The programs are 32-bit, so the 32-bit runtime is needed first: sudo apt install libc6-i386 lib32z1 lib32stdc++6 csh. This is the newest MCPRO there is — May 2020.
Untested by us. If you run it, please tell us how it went — we will say so here.
Manuals: MCPRO 2.3. The newest manual written is for 3.2 and ships inside the Linux download as MCPROman320.pdf — there is no 3.3 manual.
Copyright © William L. Jorgensen, all rights reserved. Questions about licensing, including multi-department and site licences, go to our contact page.
The MCPRO executables are 32-bit i386 binaries, so a 64-bit system needs the 32-bit compatibility runtime. Without it you get No such file or directory for a file that is plainly there — the missing piece is the 32-bit loader, not MCPRO. The driver scripts are written in csh.
sudo apt install libc6-i386 lib32z1 lib32stdc++6 csh
MCPRO shares BOSS's fixed-width path handling, so keep both the install and your working directories short.
cd ~
tar xzf mcpro1020.tar.gz
Add this to your shell profile so it persists. The scripts find everything through it.
setenv MCPROdir ~/mcpro # csh/tcsh
export MCPROdir=~/mcpro # bash/zsh
mcpro/README explains which executable to use: mMCPRO is the normal one, and aMCPRO reads ligand alpha values with 800 codes at the end of the Z-matrix. The manuals are in mcpro/MCPROman/ — MCPROman320.pdf is the newest, written for 3.2. Test jobs, including the protein–ligand FEP examples, are in mcpro/testjobs/.
ls $MCPROdir/testjobs
Worth knowing before you start: we have not run either MCPRO build ourselves, so these steps come from the bundled readme rather than from a run of our own. MCPRO shares BOSS's habit of printing success after a step has failed — check that the files you expected are actually there and not zero bytes. If you get it working, tell us and we will say so here.