Update Project Steps

Registry Key

Create and/or set a registry key on the JNIOR with a value. The RegKey cell must contain the exact text and capitalization needed for the Registry key. The RegValue cell must contain an acceptable value for the Registry key. The RebootRequired cell can be set to false or true to indicate if a reboot is required as a result of this step. A Reboot Step must also be included in the Project to trigger a reboot after this step is executed. The user can edit the Name cell for
display purposes in the Step list window on the left.

Update Registry

Grabs an .ini file from you PC and uploads it to the selected JNIOR. This will update the registry with the one saved as the .ini file.

Delete File

Delete a file on the JNIOR. The user must enter the file name in the RemoteFile cell and any folder name where the file is stored (besides the root directory) in the RemoteFolder cell. The user can edit the Name cell for display purposes in the Step list window on the left.

Make Remote Directory

Create a new folder (directory) on the JNIOR for storing an application or other file. The user must enter the folder name and any path in the RemoteFolder cell. The user can edit the Name cell for display purposes in the Step list window on the left.

Reboot

Reboot the JNIOR during the execution of the project. A reboot must occur to update the JNIOR OS, or stop and start an application or for some Registry setting changes to take effect. If any of the steps require a reboot, then a Reboot step must be included in the project to respond to the reboot flag set by one of the other steps. The user can also set the ClearSystemMemory to true to clear the RAM memory on reboot. This deletes all the logs and some other temporary files, but does not delete anything in the flash memory (same as a reboot –a command). The user can also set the MustReboot option to true to force a reboot regardless of the previous steps. The user can edit the Name cell for display purposes in the Step list window on the left.

Load Applications

Can be used to load any application. You do NOT need to have a version or version location registry key (location) defined. If a version number is available, the Load Application Step will check it and compare the version numbers. You can also use the Generic File Transfer Step to transfer an application besides a standard INTEG application.

Transfer

There are several types of file transfer functions available. There is a generic File Transfer Step and two specific steps for use with the Cinema.JNIOR application.

• File Transfer – Allows the user to transfer a file to the JNIOR. The location of the file on the PC must be selected via the LocalFile cell and the location for the file on the JNIOR must be entered in the RemoteFile cell. The file can be transferred to a specific folder on the JNIOR by entering the complete path in the RemoteFolder cell.
  NOTE: The folder on the JNIOR must exist or must be created with a Make Remote Folder Step prior to this step. The user can rename the file and the Support Tool will change the name of the file before it is transferred to the JNIOR. A file on the JNIOR with the same name will be removed before transferring the new file (RemoveFirst). The user can edit the Name cell for display purposes in the Step list window on the left.
• Cinema Macro File – Allows the user to transfer a Macro file used by Cinema.JNIOR. This step is different than a Generic File Transfer because it will first check the JNIOR to see if a macro file exists with the same name or a different name. In either case, it will delete the macro file so that only one macro file exists on the JNIOR. The location of the file on the PC must be selected via the LocalFile cell. The name for the file on the JNIOR must be entered in the RemoteFile cell and must be macro_xxx.csv (where xxx can be anything) to be recognized by the
  Cinema.JNIOR program. The file can only be transferred to the root directory. The user can edit the Name cell for display purposes in the Step list window on the left.
• Cinema Device File – Allows the user to transfer a Devices file used by Cinema.JNIOR. This step is different than a Generic File Transfer because it will first check the JNIOR to see if a devices file exists with the same name or a different name. In either case, it will delete the devices file so that only one devices file exists on the JNIOR. The location of the file on the PC must be selected via the LocalFile cell. The name for the file on the JNIOR must be entered in the RemoteFile cell and must be devices_xxx.csv (where xxx can be anything) to be recognized by the Cinema.JNIOR program. The file can only be transferred to the root directory.

Clean Up

Allows you to delete one or more files on the JNIOR. When the user clicks in the Remote Files cell, a window will pop-up allowing the user to enter the file names and/or folder/filenames of the files to be deleted. The user can edit the Name cell for display purposes in the Step list window on the left. 

Preserve/Restore Files

These steps should be used together. The preserve will save certain files from you JNIOR to keep and then the Restore will reset the JNIOR then load the files saved back onto that JNIOR.

Telnet Command

Allows you send a telnet command through the command line, allowsing for example a “reboot” command to reboot the JNIOR or a “ps” command that will show you which process on the JNIOR are running.

Transfer Zip

Allows you to send the contents of a zip file to a JNIOR.

Update Series 4 OS

Allows the user to transfer a upd update file to the JNIOR operating system. This file is provided by INTEG, as needed. When the user clicks in the Local File cell, clicking on the icon with three dots will allow the user to navigate to the location of this file. The Support Tool will pull this file from the remote location and put it in a local folder. The JNIOR OS version is automatically detected and displayed in the Version cell. The Option to reboot the JNIOR is set as true by default. This causes the JNIOR to reboot immediately after the file is transferred. The user could set this to false and utilize the Reboot Step later in the project. The user can edit the Name cell for display purposes in the Step list window on the left.

Update Series 3 OS

Allows the user to transfer a jr310.upd file to update the JNIOR operating system. This file is provided by INTEG, as needed. When the user clicks in the Local File cell, clicking on the icon with three dots will allow the user to navigate to the location of this file. The Support Tool will pull this file from the remote location and put it in a local folder. The JNIOR OS version is automatically detected and displayed in the Version cell. The Option to reboot the JNIOR is set as true by default. This causes the JNIOR to reboot immediately after the file is transferred. The user could set this to false and utilize the Reboot Step later in the project. The user can edit the Name cell for display purposes in the Step list window on the left.