On the Subject of Tech Support

Have you tried turning it off and on again?

  • Incidentally, one of the modules on the bomb will break down giving an error report on the terminal screen.
  • The affected module can be found by looking for the module with a yellow indicator light. While this light is on, the module will be completely inoperable.
  • Each exception is indicated with an error code, the line and column of the error, and the source file in which the exception occurred.
  • With this information the correct software version, patch file, and patcher launch parameters can be selected.
  • Use the three buttons on the right to navigate through the terminal's menu.
  • A strike is dealt when incorrect information is entered.
  • When too much time is taken, a strike is dealt as well and the interrupted module is automatically rebooted.

Selecting the Software Version

Use the exception's error code and source file to determine the correct software version, using the table below.


Selecting the Correct Patch File

Follow instructions listed below to determine the correct patch file.

  • If the source file's number of vowels is equal to or greater than the number of consonants, or the column index is higher than the line index, select faee.sup.
  • Otherwise, if the source file's first letter is in the last third of the alphabet, select prle.cba.
  • Otherwise, if the less than 99 seconds is still available and the column is higher than 75, select linion.dart.
  • Otherwise, if the error's line and column are both even, select razcle.pxi.
  • Otherwise, if any of the error code's letters are contained in the crashed source file's name, select wane.drf.
  • Otherwise, if this is the fourth or later crash and the cumulative line number of all previous errors is over 450, select gilick.pxd.
  • Otherwise, select shuttle faee.sup.
  • However, if the error's source file is either satcle.bb, or equely.ctl, ignore all rules above and select exed.asc.

Selecting the Correct Launch Parameters

Select the first three characters of the exception's error code, starting after the “0x”, translate these to numerical values (A = 1, B = 2, Z = 26), and sum these. Multiply this number by the exception's line index. Execute the same method for the last three characters of the exception's error code, however, instead multiply this result with the exception's column index. Finally, perform an XOR-operation with the delta between these two numbers, and the value of the sum of the first three and the sum of the last three values multiplied with each other. By subtracting the number of different launch parameters from this number, until it is smaller than that number, the final result is unveiled. Add one to this number and you will have found the index of the correct launch parameters. Use the tables below to determine those launch parameters.

See Appendix: Boolean Operations for XOR-operations reference.

Param IndexParameters
1-n -k -g
2-d -h
3-b -q -k
Param IndexParameters
4-x -m
5-w -t
6-o -v -l
Param IndexParameters
7-t -z
8-f -m -i


Appendix: Boolean Operations

This appendix elaborates the elementary boolean operations that are used in various modules, which are the following: AND, OR, NAND, NOR, and XOR. Each operation compares two binary numbers, resulting in a new one.

Operation Basics

The first step when working with boolean operators is to convert the two provided parameters into binary form. Each 1 in a binary number, or bit, represents a certain value. The last one equals 1, the one before 2, the one before that 4. The values of each preceding number is double the value of the next. Therefore, 127 equals 1111111, 3 equals 11, and 25 equals 11001. When two values have different lengths, add as many zeros in front of that number until they do have the same size. This means that 00001010 and 1010 are the same value.


An AND-operation compares each individual bit in a binary number and outputs a 1 if both bits are a 1 as well. This means that an AND-operation with the values 1010 and 1101 outputs the value 1000, or the decimal value 8.


An OR-operation compares each individual bit and outputs a 1 if either of the two is or both are a 1. This means that an OR-operation with the values 1000 and 0011 outputs the value 1011, or the decimal value 11.


A NAND-operation compares each individual bit and only outputs a 1 if not both of the bits are a 1. This means that a NAND-operation with values 0101 and 0111 outputs the value 1010, or the decimal value 10.


A NOR-operation is the inverse of an OR-operation and outputs a 1 if none of the bits are a 1. This means that a NOR-operation with the values 1100 and 1001 outputs the value 0010, or the decimal value 2.


An XOR-operation is an OR-operation, however, also outputs a 0 if both values are a 1. This means that an XOR-operation with the values 0110 and 1100 outputs the value 1010, or the decimal value 10.