26 Jan
2012
26 Jan
'12
1:34 p.m.
On Thu, Jan 26, 2012 at 7:27 AM, Paul Emsley
Another option might be that it is somehow picking up an old coot - and the communication dependences are not in place - however, I thought the Phenix gui guards against this possibility.
Not really - the rules are: 1. If the path to coot is defined in Preferences, it uses that; 2. Otherwise, if "coot" is a valid command in the shell's search path, use that; 3. Finally, look for various common places where Coot might be expected (this is usually only necessary on Mac) for a "coot" executable. I may have some idea what is breaking here; will check again in a few hours (first I need coffee). Peter: what is the terminal output when you click the Coot icon? -Nat