Using advanced recovery options

Caution: This section is intended for MediaMatrix Technical Support staff or users who are under instruction from Technical Support. Using the wrong configuration options could prevent the nControl from functioning.

The recovery process is controlled using settings in an XML file. This file is called switches.xml and is located in the root of the USB stick drive.

By default, the file contains the following code.

<?xml version="1.0" encoding="utf-8"?>
<RecoverySwitches>
 <Control>
 <exit_switch>
 <switch value="1" />
 </exit_switch>
 <put_switch>
 <switch value="1" />
 </put_switch>
 <get_switch>
 <switch value="0" />
 </get_switch>
 <wipe_switch>
 <switch value="0" />
 </wipe_switch>
 </Control>
</RecoverySwitches>

Each of the switches is explained in the table below.

exit_switch

When set to 1, shuts the computer down after the recovery process has finished. Default is 1.

put_switch

When set to 1, restores the system from the .7z image file, located in the MM_Config folder on the USB stick. Default is 1.

get_switch

When set to 1, retrieves the system image from the nControl unit, places it in a .7z file, then copies the file to the MM_Config folder on the USB stick. Default is 0.

wipe_switch

When set to 1, reformats and repartitions the hard disk, wiping the contents from both C: drive and D: drive on an nControl unit.

When set to 0, C: drive will be formatted and the system will be restored on this drive; the contents of D: drive will be left intact. Default is 0.

Note: This switch is for nControl units only. The contents of D: drive on nTouch 180 units are always lost as part of the recovery process.

The switches are set to 1,1,0,0, by default. This will restore the system without wiping the D: drive, then will shut down the nControl unit.

Specifying 0,0,0,0 will simply boot the system and display a command prompt.

See also

Viewing hardware status information

Viewing firmware status information

Rebooting or shutting down the unit

Adding entries to the log manually

Restarting the ControlManager application

Updating the firmware

Recovering the nControl unit if it stops functioning