...

1. Stop and close the following VIs.
   1. Cryo Control Panel (CCP_Main.vi) — Click the "Stop All Subsys" button and then , click the "Stop This Panel" button.
   2. BOS+EOS Handler — Follow the detailed procedure written below.
2. Shut down the OS.
3. Ask the SpinQuest network admin to shut down the following SpinQuest servers.
   1. e1039scrun — Use SSH and the "poweroff" command
   2. e906-gat1, e1039gat1 — Use SSH and "poweroff"
   3. e906-db1 — Use SSH and "poweroff"
   4. SeaQuestDsk0 (/data2) — Long-press the hardware power button until the power goes off

Turning On

1. 1. , and then close the front-panel window.
   2. Spill Counter (Spill_Counter_Main.vi) — Click the "STOP" button, and then close the front-panel window.
   3. Close the LabVIEW startup window.
2. Shut down the OS.

Turning On

1. Confirm with the NM4 network admin that the NM4 servers are up and running.
2. Make sure that the following Sea/SpinQuest servers are up and running.  If not, contact the network admin or boot them up if allowed.
   
   1. SeaQuestDsk0, e906-db1 — Wait until SeaQuestDsk0 becomes up.
   2. e906-gat1, e1039gat1
   3. e1039scrun
3. Make sure that the slow-control rack and the magnet rack are up and running.
4. Boot up the OS.
5. Login as "e1039daq".  Only the UVA members know the password.
6. Click "SX Virtual Link" in the taskbar to open it.  It connects to all remote USB devices automatically.
7. Start the following VIs.
   1. BOS+EOS Handler — Follow the detailed procedure written belowSpill Counter — Double-click "Spill_Counter_Main.vi" on the desktop and click the VI "Run" icon.
   2. Cryo Control Panel — Double-click "CCP_Main.vi" on the desktop and click the VI "Run" icon.

...

All virtual USB devices are usually disconnected.  You have to connect/disconnect each device before/after you use it via "SX Virtual Link".  You can click the icon in the taskbar to bring up the user interface like this. 

...

The "uva-spin" GitHub repository ( https://github.com/uva-spin ) is cloned at "github" on desktop.  Our default software to manipulate the repository is "Git Bash" in "Git for Windows" ( https://gitforwindows.org/ ).

...

Environmental Variables for EPICS

...

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.

...

• Network path = "192.168.24.160:/mnt/seaquestdsk0" — Found in "e1039gat1:/etc/fstab"
  
• UID = 500 (e1039daq) and GID = 10391 (e1039sc) — Found by "ls -n /data2/e1039_data/slowcontrol_data"

...

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

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

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

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

...

• Open "command prompt" from the search box.
• 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!
• Screenshots: Command prompt. and Z: folder.

...

Misc Settings

The following settings were made, as instructed in another page.

• Git repository
• NFS mount
• Disabling automatic Windows update

...

Create "nfsmount.bat" with the following contents:

...

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

There are several ways of disabling the automatic Windows updates on Windows 10 Pro.  Let's use "Group Policy" on the target computer.  It was disabled by the following procedure on 2021-10-25.

1. Search for "gpedit.msc" (using the task-bar search box) and execute it.
2. Go to "Computer Configuration" -> "Administrative Templates" -> "Windows Components" -> "Windows Update".
3. Double click "Configure Automatic Updates" policy setting and select "Enabled".
4. Choose "2" ("Notify for download and notify for install") under "Configure automatic updating" section.
5. Click "Apply", followed by "OK".

Reference:  https://answers.microsoft.com/en-us/windows/forum/all/how-permanently-disable-windows-10-pro-64-updates/18727670-db05-4267-80fb-cf2622eee8c1

...

Change in Target Computer Setup

...