Changes

=== WSL2 ===

=== WSL2 ===

I got CCP4 7.1 including coot-0.9.5 to work on Ubuntu 20.04 LTS running under WSL2, with https://mobaxterm.mobatek.net/ MobaXterm as the Xserver (but not with Xming or VcXsrc). My ~/.bashrc has the line (which the CCP4 installation created):

I got CCP4 7.1 including coot-0.9.5 to work on Ubuntu 20.04 LTS running under WSL2, with [https://mobaxterm.mobatek.net/ MobaXterm] as the Xserver (but not with Xming or VcXsrc, at least not reproducibly). My ~/.bashrc has the line (which the CCP4 installation created):

  source /opt/xtal/ccp4-7.1/bin/ccp4.setup-sh  

  source /opt/xtal/ccp4-7.1/bin/ccp4.setup-sh  

and I created a file (replace MYUSERNAME with your Windows username) in the Windows filesystem:

and I created a file in the Windows filesystem (replace MYUSERNAME with your Windows username):

  cd /mnt/c/Users/MYUSERNAME/

  cd /mnt/c/Users/MYUSERNAME/

  echo "[wsl2]" > .wslconfig

  echo "[wsl2]" > .wslconfig

  echo "kernelCommandLine = vsyscall=emulate" >> .wslconfig

  echo "kernelCommandLine = vsyscall=emulate" >> .wslconfig

to make the shelx* programs happy (see https://github.com/microsoft/WSL/issues/4694 ), and "vsyscall=emulate" appear in /proc/cmdline. After creating the file, WSL2 must be restarted with "wsl.exe --shutdown" (or the machine booted).

to make the shelx* programs happy (see https://github.com/microsoft/WSL/issues/4694 ), and to make "vsyscall=emulate" appear in /proc/cmdline. After creating the file, WSL2 must be restarted with "wsl.exe --shutdown" (or the machine booted).

A few libraries also needed installation (tcsh is needed by CCP4, the others are mostly graphics libraries):

A few libraries also needed installation (tcsh is needed by CCP4, the others are mostly graphics libraries):