...

1. Search for "env" in the search box.
2. Bring up "Edit the system environment variables".
3. Click the "Environment Variables..." button.
4. Add or modify the EPICS variables; EPICS_BASE, EPICS_CA_ADDR_HOST and EPICS_HOST_ARCH.  Example.
5. Reboot.

NFS Mount

The target computer mounts the E906/E1039 network disk (i.e. "/data2") to record slow-control data.  The disk is automatically mounted when the main user logs in.  It was configured on 2021-11-21 by the following procedure.

1. Collect the information on the network disk.
   1. Network path = "192.168.24.160:/mnt/seaquestdsk0" — Found in "e1039gat1:/etc/fstab"
      
   2. UID = 500 (e1039daq) and GID = 10391 (e1039sc) — Found by "ls -n /data2/e1039_data/slowcontrol_data"
2. Search for "turn windows features on or off" on the task-bar search box, and click it.
3. Enable "Services for NFS".
4. Enable the write permission.

   1. Open "regedit" from the task-bar search box.

   2. Expand HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> ClientForNFS -> CurrentVersion -> Default.

   3. Create a new DWORD value (via right-click menu), with name = "AnonymousUid" and value = "500".

   4. Create a new DWORD value (via right-click menu), with name = "AnonymousGid" and value = "10391".

5. Reboot the OS.
6. Mount the network disk manually for test.
   1. Open "command prompt" from the search box.
   2. Execute this command: "mount -o anon -o nolock -o fileaccess=775 \\192.168.24.160\mnt\seaquestdsk0 Z:".  Note that "-o anon,nolock,fileaccess=775" does not work!
7. Set up an automated mount via startup
   1. "Start Menu" → "Run" → Enter "shell:startup".

   2. Create "nfsmount.bat" with the following contents:

      mount -o anon -o nolock -o fileaccess=775 \\192.168.24.160\mnt\seaquestdsk0 Z:

      
      

   3. Reference: https://dop-amine.com/posts/persistent-nfs-windows/

Notes:

• The mount option "-o nolock" was necessary to avoid an error when creating a file: "0x80070021: The process cannot access the file because another process has locked a portion of the file."
• "UID = GID = 65534" didn't work since the write permission of "/data2/e1039_data/slowcontrol_data" is not granted.
• It is a bit anxious that any user on the target computer can (re)move any network files by mistake, where such mistake can happen more easily on graphical interface.  A precaution is wanted.
• The registry can be edited via the command prompt.  Have a try next time:
  
  • New-ItemProperty HKLM:\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default -Name AnonymousUID -Value 500 -PropertyType "DWord"
  • New-ItemProperty HKLM:\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default -Name AnonymousGID -Value 10391 -PropertyType "DWord"
  • Reference: https://blog.edie.io/2018/06/16/mounting-nfs-shares-in-windows-using-identity-mapping/
• Reference: https://docs.datafabric.hpe.com/61/AdministratorGuide/MountingNFSonWindowsClient.html

Disabling Automatic Windows Update

...