View source for Patching 3T

== Introduction ==
This page explains what a scanner patch does, how you can check the currently active patch, and how you should install or remove the active patch. Note that it is <u>your own</u> responsibility to make sure the correct patch is running.
<br><br>

'''What is a patch?'''

When the standard functionality of the scanner is insufficient to run the desired protocols, the system can be 'patched' to include this functionality. By default, no patch is installed. If you install a different patch, make sure to remove it after your scan session. On release 5, patches are automatically uninstalled when the system is started under the restricted MRUser account. Patches can only be installed and selected during startup under the gyrotest account.

== Checking which patch is active ==

Before scanning, it is always wise to check which patch is active. Having the wrong patch installed does not necessarily raise a conflict on the scanner so you might only find out when your data does not look the way they are supposed to. You can check the active patch by bringing up the MR Boot Configuration Manager by using the windows key for example.

[[File:philips_boot_menu.jpg]]
<br><br>

== Starting or switching a patch  ==

Make sure that the CheckPatchReady utility is running in the background. The CheckPatchReady utility is automatically started when logging in as gyrotest user, but if the window was accidentally closed, it can be restarted from the start menu (''Start->All Programs->Startup''). Only select a new patch when the following message is displayed: <pre>READY TO (DE)SELECT PATCH, LOGOUT OR START GUI</pre>

[[File:ready_to_patch.jpg]]

Then, within the MR Boot Configuration Manager, there is an option to select a patch. A list of patch folder names as located in E:\research\patches will appear and the required patch folder can be selected. 

[[File:select-patch-dialog.jpg]]

After selecting the patch, the system will need approximately 4 minutes to reconfigure the system. The CheckPatchReady utility will monitor this configuration process and display a message when it is OK to start the application GUI. Do '''not''' start the GUI before the following message is displayed: <pre>READY TO LOGOUT OR START GUI</pre>

[[File:Ready_message.jpg]]

Upon starting the application software all required processes will be started using the selected patch. A warning will be prompted before activating the selected patch.

[[File:patch-start-warn.jpg]]

== Deselect a patch  ==

An active patch can be deactivated by a logout of the windows desktop. However, the patch removal itself will postponed until the next login. So, to prevent unexpected delays for the next user, it is required to login again immediately. Keep in mind to take account for the additional time required to (de)activate a patch when you book a scan slot. Do not select an empty folder to remove a patch because that will have negative side effects, like additional delays on the next login. Note that is not required to logout and deactivate a patch first when a new patch has to be activated.

== Installing new patches ==

Installation of new patches should only be performed by certified MR technicians. Make sure that the new patch is compiled for the current software release. Available patches are located in E:\research\patch. Use Windows Explorer to copy a patch folder to this location and make sure to give the folder a proper name. Preferably including the release version for which is was compiled: MRE_FFE_rev3__5.1.8_SWID31. However, if the folder name is too long it won't be displayed in the MR Boot Configuration Manager. Do not put a patch inside a subfolder. Never remove  or change patch files of an active patch.

[[File:browse-patch-folder.jpg]]

== Advanced users only  ==
For advanced users only, there still is the option to install a patch in the 'old' method, however '''never''' use this method if you do not know what you are doing.
To do this, rename the "''Patch''"-symlink folder on the g-drive to "''Patch_backup''", create a new folder named "''patch''", copy your patch in the ''G:\patch'' folder, run ''permproc stopall'', wait until all processes have stopped, run ''permproc startall'', use ''logd'' to see if all processes were started, then start the scanner '''without''' using the "''select patch''" button. 
After scanning, use ''permproc stopall'', delete the "patch" directory, rename "''Patch_backup''" to "''Patch''" (not the capital P) and use ''permproc startall'' to start all processes.