• Topic ID: id_18717816
  • Version: 1.0
  • Date: Sep 20, 2018 2:03:39 PM

LFC Procedure (13BW29.5) for LCGOC/GOC4 Console

1 Scope

This LFC (Load from Cold) procedure supports the following systems:

  • BrightSpeed Elite with GOC4 Operator Console

  • BrightSpeed Edge with LCGOC Operator Console

  • BrightSpeed Excel with LCGOC Operator Console

This LFC (Load from Cold) procedure supports the following software revisions:

note:

Class C/M install CD are not shipped with system.

note:

The Xtream Serial-Over-Lan Service Software is not used during the LFC unless instructed via a pop-up message box "SOL Service - ...run the Serial Over LAN Service CD...". This CD is loaded directly into the DARC Node. Then press the reset (or cycle power) at the front panel of the DARC Node as required. This CD will auto-eject when the SOL load process is complete.

note:

The Xtream Serial-Over-Lan CD is not used for AIO / TIO / NIO16 Console.

2 Hardware-Related Prerequisites

2.1 Ensure Both SDDA Drives Are Functioning

Open Unix Shell and type the following:

  1. {ctuser@hostname} rsh  darc

  2. [ctuser@darc] cat /proc/scsi/scsi

    note:

    Output should look similar to the following. Look for two drives. If there are NOT two drives, troubleshoot.

    Attached devices:

    Host: scsi0 Channel: 00 Id: 00 Lun: 00

         Vendor: SEAGATE Model: ST336753LW Rev: 0006

         Type: Direct-Access ANSI SCSI revision: 03

    Host: scsi0 Channel: 00 Id: 01 Lun: 00

         Vendor: SEAGATE Model: ST336753LW Rev: 0006

         Type: Direct-Access ANSI SCSI revision: 03

  3. Close the Unix Shell.

2.2 SCSI Tower Drive Verification

Perform this recommended procedure to check DVD or MOD functionality prior to performing a LFC.

  1. Verify the SCSI Tower DVD-RAM power is applied.

  2. Verify the SCSI Tower terminator LED is lit (located at the rear).

  3. Verify the Host Computer DVD-ROM drive does not have a disk in it.

  4. Open a Unix Shell and verify the SCSI Tower components are present (two examples are shown below, but may not match your SCSI Tower configuration):

    {ctuser@hostname} scsistat

    Example #1:

    Device 0 00 Direct-Access SEAGATE ST336753LW FW Rev: HPS2 OS 36 GB

    Device 1 01 Direct-Access SEAGATE ST373453LW FW Rev: HPS2 73 GB Image

    Device 1 02 Direct-Access SEAGATE ST373453LW FW Rev: HPS2 73 GB Image

    Device 2 03 Optical Device SONY SMO-F551-SD FW Rev: 1.04 SCSI Tower Sony MOD

    Device 2 04 CD-ROM MATSHITA DVD-RAM LF-D521 FW Rev: A109 SCSI Tower DVD-RAM

    Example #2:

    Device 0 00 Direct-Access SEAGATE ST336753LW FW Rev: HPS3

    Device 1 01 Direct-Access SEAGATE ST373453LW FW Rev: HPS3

    Device 1 02 Direct-Access SEAGATE ST373453LW FW Rev: HPS3

    Device 2 03 Optical Device SONY SMO-F551-SD FW Rev: 1.03 SCSI Tower Sony MOD

    Device 2 04 CD-ROM HITACHI DVD-RAM GF-2050 FW Rev: E372 SCSI Tower Hitachi DVD-RAM

    Device 4 00 CD-ROM HL-DT-ST DVD-ROM GDR8163B FW Rev: 0B15

  5. DVD Drive Verification:

    1. Create a temporary testing file:

      {ctuser@hostname} su  -

      Password: #bigguy

      {root@hostname} dd  if=/dev/urandom  of=/tmp/foo  bs=1024  count=50k

      51200+0 records in

      51200+0 records out

    2. Ensure the temporary testing file was created:

      {root@hostname} ls  -al  /tmp/foo

      -rw-r--r-- 1 root root 52428800 May 10 11:55 /tmp/foo

      (”52428800” represents the file size.)

    3. Calculate the checksum for the local temporary file.

      note:

      These numbers will change every time you generate a new file.

      {root@hostname} sum  /tmp/foo

      44519   51200

      note:

      1st # = checksum (FE should write this down to use for comparison later)

      2nd # = size of file checksum'd

      Checksum    File Size in kilobytes

      --------    ----------------------

      44519                51200

    4. Insert DVD-RAM into SCSI Tower.

      Data on inserted DVD will be destroyed.

    5. Create a filesystem on the DVD by typing the following:

      {root@hostname} mkfsDVD

      ----------------------------------------------------------

      *** CAUTION ***

      A filesystem already exists on this DVD.

      This utility will create a new file system on the DVD. In turn it will wipe clean any existing files and data. Make sure you have the correct DVD media in the correct DVD drive.

      Do you wish to proceed? [n] y

      Making file system. This will take approximately 3-5 minutes

      -----------------------------------------------------

    6. Mount the DVD:

      {root@hostname} mountDVD

      Mounting DVD

    7. Copy the file to the target device:

      {root@hostname} cp  /tmp/foo  /DVD  &&  sync

    8. Unmount the drive & eject the DVD to ensure the system's cache is flushed. This is required to calculate the checksum properly.

      1. {root@hostname} unmountDVD

        DVD is now unmounted.

      2. Eject the DVD

      3. Reinsert the DVD

      4. Remount the target device, using mountDVD.

    9. Generate checksum on file in DVD drive:

      {root@hostname} sum  /DVD/foo

      45731 51200

    10. Verify (compare) the file's checksum calculated by the host console matches the checksum calculated by the drive.

    11. {root@hostname} unmountDVD

      DVD is now unmounted.

    12. Eject the DVD

2.3 Information Capture

2.3.1 Common Information Capture

  1. Record Autovoice Volume control settings (ALT-F3 by Toolchest, upper right corner).

  2. Write down all of the system INFO information on the reconfig screens, including the network information (use the appropriate information sheet, found in Console Information Sheets ).

  3. Verify and record specific system hardware configuration.

    1. Open a shell and type the following:

      {ctuser@hostname} cat  /usr/g/config/INFO

    2. Record screen information in Console Information Sheets.

      For an example output, see Example Config/INFO Output.

  4. If the console has Connect Pro installed, write down the information when you run installhisris so it can be entered on the new console when installing the Connect Pro option.

  5. Close the Service Desktop window in the upper left corner of the screen.

2.3.2 Information Capture for Option Installation

If your system does NOT have “Exam Split” option, skip this section.

Perform these steps before powering down your current Operator Console:

  1. Open a Unix Shell and type the following:

    1. {ctuser@hostname} su  –

    2. Password: #bigguy

    3. [root@hostname] ls  –l  ~ctuser/ves/.hesMode

      note:

      There are no spaces in the phrase ~ctuser/ves/.hesMode

  2. Examine the results.

    • If the results are similar to:

      -rw-r--r-- 1 ctuser users 0 Apr 3 12:43

      /usr/g/ctuser/ves/.hesMode

      Then HES (Hard Exam Split) mode is configured.

    • If the results show ‘No such file or directory’, then VES (Virtual Exam Split) mode is configured.

  3. Record Exam Split Mode (Hard or Virtual). This info will be used during the LFC Options Installation.

  4. Close the Unix Shell

2.3.3 Save JEDI Runtime Parameters

Save the Jedi Runtime parameters, refer to Software-> HV Subsystem Utilities Jedi Generator Tool for how to save them.

3 Procedure

  • caution
  • Potential for Loss of Patient Data.
  • This procedure will overwrite existing data.
  • Before performing this procedure, ensure that the Archive and Network Queues are empty of patient data. If they are not, DO NOT proceed until it can be verified that all patient data has been archived.
Notice Image
  • notice
  • After each reboot during the software install process, an 'Unrecognized X-Ray Tube' message will be displayed (as shown in Tube Install Certification Tool - Screens), until the tube identity has been selected and 'Flash Download' has also been performed. The same “unrecognized x-ray tube” message will also be displayed on the CSD Homepage, until the ID and flash download are done.

3.1 Save System State

Notice Image
  • notice
  • Do NOT switch screens or run other programs while saving System State. Otherwise the GUI may “hang” while trying to close, and the System State will need to be saved again.
note:

Jedi Runtime parameters should be saved to state DVD before starting the LFC.

note:

New tasks are included in this SW release These task will generate data that needs to be saved to the system state DVD. Follow the save and restore procedures throughout this document precisely or valuable information may be lost.

Notice Image
  • notice
  • Two “Save System State” DVD procedures must be performed:
note:

The original “Save System State” will be used only if the customer wants to revert back to the original SW.

Perform these steps before powering down your Console:

  1. Insert the DVD-RAM into the SCSI Tower DVD drive.

  2. Select Service Desktop.

  3. If reloading software, select: UTILITIES. If upgrading from earlier version software, select: PM.

  4. Select System State.

    note:

    System State Save may be under Utilities or PM.

  5. Select ALL to save all data.

  6. Select SAVE.

  7. If applicable, select OK when the following message appears: System State Media Status: Please insert a DVD or MOD into the drive and press Save again.

    note:

    Successful completion is indicated by the message, Save/restore system state: completed successfully.

  8. When completed select DISMISS.

    IMPORTANT: Do NOT select DISMISS more than once. Doing so will result in the GUI becoming hung, and the System State will be unusable. Should this occur, Save System State again.

  9. For the original DVD, label the DVD as “Linux System State Backup”.

  10. Repeat Step 1-8, for the second “Save System State”, using a new DVD and label with the same SW release that is found on the Application DVD label.

  11. Close the Service Desktop window in the upper left corner of the screen.

  12. Sites performing the next sub-section should not remove the DVD-RAM from the SCSI Tower DVD-RAM drive.

3.2 Host Computer LFC

Use the procedures in this section to perform a LFC.

3.2.1 Host Computer BIOS Requirement

  1. Open a Unix Shell and become root:

    {ctuser@ hostname }   su  -

  2. Password: #bigguy

    note:

    If the Password has not been modified by the site and is not known, the correct course of action is to contact Local GE Service.

  3. To determine the Host Computer BIOS version, type the following:

    {root@ hostname }   dmidecode  |  grep  Ver

    Authorized BIOS versions

       Version: JQ.W1.13US v1.13 for xw8000

       Version: 786B8 v2.10 for xw8200

       Version: 786D5 v2.24 for xw8400

  4. Ensure that the Host Computer BIOS version is shown above. If correct, skip the following step. If not correct, perform step 5.

  5. If the Host BIOS version is not correct or if you suspect incorrect Host BIOS settings (changes specified by GE from default), follow the instructions for your specific Host type:

3.2.2 OS Installation on Host Computer

note:

Takes 20 minutes approximately to complete OS installation.

note:

System State SAVE must be performed before shutting down apps (Application Software).

note:

During the OS load you need to select "ignore" twice when it complains about I/O errors with a SCSI device. These messages will occur with systems without a DASM:

Input/output error during read on /dev/sd?

Input/output error during write on /dev/sd?

  1. Remove the Operator Console's front cover.

  2. Remove the Hospital Backbone Ethernet cable from the Console Bulkhead Assembly, located at the rear of the Operator Console.

  3. Insert the OS disk into the DVD-ROM drive on the Host Computer. See the following illustration.

  4. Select one of the following methods to re-power the Operator Console:

    1. If Applications are up:

      1. Select the Shut Down button.

      2. Select Restart then OK to restart the system.

    2. If Application Software is down, at the toolchest open a Unix Shell and type:

      1. {ctuser@hostname} sync

      2. {ctuser@hostname} sync

      3. {ctuser@hostname} halt

      4. The Operator Console monitor will display a System halted message when it is acceptable to power OFF the Operator Console.

      5. Power OFF the Operator Console at the front panel switch.

      6. Wait 30 seconds to allow the disk drive to settle; then power ON the Operator Console at the front panel switch.

  5. As the computer restarts, the booting process messages appear. After the booting process completes, the boot: prompt appears.

  6. At the boot prompt, type the following depending on system type:

    GEHC2 Enter

    note:

    The Console Operating System load takes approximately 20 minutes. If the boot: prompt does not appear, then either the DVD-ROM is bad or the Console Operating System DVD is not installed in the drive.

    Typing GEHC will result in both scan and display being on one monitor and require a LFC.

  7. After the OS is loaded, a red button appears and displays Reboot.

  8. Remove the OS disk, when it ejects.

  9. Press ENTER to reboot.

  10. The Host Computer reboots.

    note:

    Do not insert the Application disk into the Host Computer until the system reboots and the [root@localhost] window appears, displaying the [root@localhost root]# prompt.

3.2.3 Application SW Load on the Host Computer, “Applications” DVD-ROM

There is a single Application DVD used for both the Host Computer and the DARC. All applications software will be loaded to the Host Computer during this process.

note:

Takes 40~50 minutes approximately to complete Application installation

Notice Image
  • notice
  • FAILURE TO INSTALL THE CORRECT APPLICATION SOFTWARE AND SELECT THE CORRECT SYSTEM DAS HARDWARE CONFIGURATION WILL RESULT IN SYSTEM DOWNTIME AND DCB CIRCUIT BOARD REPLACEMENT. (THIS FAILURE WILL OCCUR AFTER THE FLASH DOWNLOAD PROCEDURE FLASHES THE FIRMWARE.)
  1. After the Host Computer reboots, verify that the window appears with the [root@localhost root]# prompt.

  2. In the root@localhost Window, verify the SCSI Tower MOD and DVD are present after the OS load:

    [root@localhost root]# cat  /proc/scsi/scsi

  3. Insert the Application DVD into the DVD-ROM drive on the Host Computer. See the illustration below.

  4. After approximately 15 seconds a pop-up box appears:

    note:

    If the pop-up box Warning does not appear after two minutes, type the following and wait approximately one minute for the pop-up box to appear.

    mount  /media/cdrom Enter

    /media/cdrom/autorun Enter

  5. Select Run Command to run / media / cdrom/ autorun..

  6. After approximately 15 seconds, an Installation Utility window appears. (See illustration, below.)

  7. Select Load. A prompt message appears asking if you wish to load the INFO file from the System State DVD.

    • If you do NOT have a System State or the System State is unusable, select No.

    • If you have a System State DVD, select Yes.

  8. A prompt window appears asking if you wish to load INFO file from DVD or USB media. Select DVD or USB where you save system state.

  9. A prompt window appears as follows. Ensure the System State DVD is in the DVD drive in the tower (on top of the console) or USB disk is in the USB port. then select ok.

    An “unMount media” pop-up may appear. No action is required.

  10. Select the System tab.

    See example System Settings screen, below.

  11. Verify that the Next Patient Exam # on the System Settings screen is the value restored from Save System State. Otherwise, set to 1.

  12. Verify that the proper Time Zone is selected

    Select/enter information as required for your system configuration.

  13. Select the Preferences tab.

    See the illustration below, for an example Preference Settings screen.

  14. Select the units for patient weight.

  15. Select Language: (English or other).

    note:

    To select additional 6 languages: Danish, Swedish, Finnish, Norwegian, Dutch or Euro Portuguese, please select English during LFC. After complete all LFC procedures, perform language selection again to preferred language.

  16. Select Preferred FastCal KV - select the kV to be calibrated during FastCal. These kVs should include all kVs that the site uses for patient scanning.

  17. Select Target Noise Index Table.

    (Default is Table 2.)

  18. Verify proper Date Format is selected.

  19. Verify proper Time Format is selected.

  20. Select AutoVoice Language.

  21. Verify Modified in Room Start is set to Off. Sites in Japan must be set to On.

  22. Set HIPAA Present to OFF unless the customer requests HIPAA to be ON.

  23. Select the site-preferred Dose Record option for the site. Default is ON. The dose information is saved in a DICOM structured report. The DICOM standard defines a new DICOM X-RAY Radiation SR SOP class, which the other systems must support. The Dose SR feature saves an exam’s dose information in this format.

    ON = Saves the dose information in a DICOM Enhanced SR SOP Class.

    OFF = Turns off the option.

    FULL = Saves the dose information in a DICOM X-Ray Radiation Dose SR SOP Class.

  24. Set Flip and Rotate to OFF as default. Configures the preference for allowing the Flip and Rotate feature to be turned on in the User Interface on the (Left) SCAN monitor. This preference allows the customer to apply custom orientation changes based on Exam Type and reconstructions methods on the DICOM images that will be transferred to PACS and related systems.

  25. Select the Hardware tab. The Main Hardware screen appears.

  26. Click on the Hardware Settings (orange button) to access the Select hardware configuration screen. Below illustration only an example, please select appropriate system on site, refer to Table 3

    note:

    FAILURE TO INSTALL THE CORRECT APPLICATION SOFTWARE AND SELECT THE CORRECT SYSTEM DAS HARDWARE CONFIGURATION WILL RESULT IN SYSTEM DOWNTIME AND DCB CIRCUIT BOARD REPLACEMENT. (THIS FAILURE WILL OCCUR AFTER THE FLASH DOWNLOAD PROCEDURE FLASHES THE FIRMWARE.)

    Click on the CT ONLY. then Select your System types HW Parameters, and select OK.

  27. On the Hardware Settings screen, select Tube Type, DAS Type, Table Type and Console Type. The screen will appear as below:

  28. Select the Network tab.

    See example Network Settings screen, below.

  29. Configure Network Settings:

    1. Suite Name - The Suite Name must utilize uppercase letters. It must start with a letter, followed by 3 alphanumeric characters. The total must be four characters long. It is suggested that you choose CT01 for the first scanner (CT02....), unless a different Suite Name is required.

    2. Station Name - The Station Name identifies the text that is stored in the DICOM attribute “Station Name” (DICOM TAG 0008,1010) in all CT images created. Some PACS systems may use the Station Name attribute or system tracking for identification of the scanner where the CT images were generated. Typically, the Host Name and Station Name are the same.

      note:

      The Station Name defaults to the Host Name if it is left blank. If entered it:

      • MUST NOT exceed 16 characters

      • MUST only contain the following characters: a through z, A through Z, 0 through 9, - and _

      • MUST have at least one Alpha Character (A-Z or a-z) or Special Character (_ or -)

    3. Host Name

      note:

      The Host Name identifies the hostname and AE Title of the scanner. It:

      • MUST NOT exceed 16 Characters.

      • MUST only contain the following characters: a through z and 0 through 9

      • MUST have at least one Alpha Character (A-Z or a-z) or Special Character (_ or -)

    4. IP Address - Site supplied address.

      The following procedure should be performed if your customer Ethernet hospital backbone begins with 172.16.0.xx, OR if the scanner will connect to a device with an IP address of 172.16.0.xx.

      1. If hospital backbone starts with 172.16.0.xx and this is a first time install, change the DARC subnet by checking the Change DARC subnet box, and fill in the following value: 169.254.0. Continue and complete the software load on the HOST and DARC.

      2. If the hospital backbone starts with 172.16.0.xx, and the DARC subnet was already changed, verify that the Change DARC subnet box is checked and a subnet is already filled. Continue and complete the software load on the HOST and DARC.

      3. If the DARC subnet was already changed and needs to be set to the 172.16.0 subnet, deselect the Change DARC subnet box. Continue and complete the load on HOST and DARC.

    5. IP Address - Site supplied address.

      1. If hospital backbone starts with 10.0.1.xx and this is the first time install, change the IG subnet by checking the Change DARC subnet box, and fill in the following value: 169.254.0. Continue and complete the software load on the Host computer.

      2. If hospital backbone starts with 10.0.1.xx, and the IG subnet was already changed, verify that Change DARC subnet box is checked and a subnet is already filled. Continue and complete the software load on the Host computer.

      3. If the IG subnet was already changed and needs to be set to the 10.0.1 subnet, deselect the Change DARC subnet box. Continue and complete the software load on the Host computer.

    6. Net Mask - Site supplied address.

      note:

      If the hospital backbone IP address is 192.9.220.xx, then the Net Mask must be set to 255.255.255.252.

    7. Broadcast Address - Site supplied address.

    8. Default Gateway - Site supplied address.

      note:

      Make sure the NUM LOCK button on the keyboard is not active. If it is, deselect it to enable the ACCEPT button in the next step. Failure to deactivate the NUM LOCK results in load issues.

    9. If your customer has AW Direct Connect, then select Enable AW Direct Connect?. Complete the LFC, making certain to configure this feature in AW Direct Connect. (Do not configure AW Direct Connect now.)

    10. If there is an Internal Option - Internal Subnet setting displayed and checked, then un-check it. (This option might not appear on your system.)

    11. Verify with customer’s network administrator if they have NIS. If they do, ensure the Advanced Options and Use NIS? boxes are checked. If they don’t, ensure these selections are not checked.

      1. Domain Name: add your name here (get name from customer’s network administrator).

      2. Enter the IP Address of Internal Server: add your IP address here (get IP address from customer’s network administrator).

    12. If your customer wants to synchronize the system time to their NTP server, then select Enable Network Time Protocol, and enter the Primary Server IP address.

    13. At Enable TCP Segmentation Offload?, the default selection is On. In some situation, TCP Segmentation Offload can't work normally. Please select No at this time.

  30. Select the ACCEPT button at the right corner of the User Interface.

  31. An Install INFO pop-up box is displayed.

    See the following illustration, for a typical Install INFO message (the Install INFO message is different for each system configuration, example as below).

    note:

    In Hardware setting screen, if select console type as GOC3_GOC4_LCGOC, above Install INFO message screen shown as GOC3 on Console Type.

  32. Select yes, if correct, and wait for system to reboot.

    note:

    If the information is not correct, select the NO button. This returns you to the Hardware screen. Select the Hardware Parameters Selection button and select the correct system configuration from the displayed list. Select the Accept button again, followed by the YES button on the Install INFO pop-up to accept the new hardware configuration.

  33. The following pop-up message appears:

    Please make sure the CT Application SW is in the drive - the system will be rebooted.

    No action is required for this pop-up. The system will automatically reboot after approximately 10 seconds if the OK button is not selected.

    note:

    Do not remove the Apps DVD from the Host Computer until instructed to do so.

  34. As the system reboots, the following shell Installation screen appears and the application software starts loading.

  35. After the system reboot automatically, the pink pop-up box appears, stating CT Software Auto-Start Disabled. In this box, select OK.

    note:

    Follow the next procedure, Do NOT type “startup” at this time

  36. Press the button on the DVD-RAM drive to remove the Apps DVD from the Host Computer.

3.2.4 Confirm Host PC Software

Confirm the Host Computer Software type. The software section of the version output should match example shown.

  1. Open a Unix Shell and type the following to see software and hardware Config information:

    {ctuser@hostname} cd  /usr/g/bin

    {ctuser@hostname} swhwinfo

  2. Confirm that the swhwinfo results match the software revision shown on the Applications Disk.

    • If the revisions match, continue with this procedure.

    • If the revisions do NOT match, reload the software (Host Computer LFC).

  3. Type: cat  /GEHC*

    Release: GEHC/CTT Linux 6.3.11

  4. Confirm that the cat result matches the Operating System version shown on the OS disk.

  5. Close the Unix Shell.

3.3 DARC Software Load Process

note:

This section describes the DARC Software Load Process. This section of the LFC is also used for DARC reload and replacement. In the reload case, if any Service Packs have been released for this version of software, refer to included instructions and load the Service Pack after the DARC software load if necessary.

3.3.1 Check DARC Node Type

  1. Log into the DARC and determine hardware type (Westville = WV or Jarrell = JR):

    {ctuser@ hostname }   ipmitool -H darc -P '' fru | grep -i "Board Product" (P means upper case)

    (Example) Board Product : SE7520JR23

    Board Product : Intel(R) Management Module - Professional Edition

  2. To determine DARC Node type, view the first line at the top of the response. (See examples below.)

    • Westville DARC Nodes will contain a WV string (example, SWV25)

    • Jarrell DARC Nodes will contain a JR string (example, SE7520JR23)

      Westville DARC2 Node (Front)

      Jarrell DARC2 Node (Front)

3.3.2 Change DARC BIOS Boot Order Settings - Enable OS Load on DARC from PC

note:

(For Westville DARC Nodes) require DARC BIOS changed by follow Change DARC BIOS Boot Order Settings - Enable OS Load on DARC from PC before a software load then restored to original settings after LFC.

(For Jarrell DARC Nodes) need confirm DARC BIOS setting same as step 12 on section 3.3.2 before a software load. If BIOS setting do not same as step 12, following Change DARC BIOS Boot Order Settings - Enable OS Load on DARC from PC to complete BIOS setting. DO NOT returned to original settings after LFC.

This section describes the steps necessary to change the DARC Node BIOS to enable the OS load onto DARC Node from the Host Computer.

note:

Be patient. Telnet response may be slow.

  1. Open a Unix Shell and type the following:

    1. {ctuser@hostname} su  -

    2. Password: #bigguy

    3. [root@hostname] service  cliservice  start

    4. [root@hostname} telnet  localhost  623

    5. At Server Prompt type: darc

    6. username Enter

    7. password Enter

      Login successful

    8. dpccli> reset

      ok

      dpccli> console

      note:

      A slight delay here is normal. Be patient.

  2. Interrupt the DARC boot process to enter the BIOS Setup mode. When the message “Press <F2> to enter setup” appears, press F2.

    note:

    F2 may have to be pressed many times before BIOS setting screen can be seen. There will be a short delay before the DARC BIOS setup screen is displayed.

  3. Select Boot Menu, using arrow keys.

  4. Select Boot Device Priority Menu, using arrow keys, then press Enter.

  5. Select 1st Boot Device, using arrow keys, then press Enter.

  6. A small window will appear with the options available. Using the down-arrow key, scroll down to highlight IBA 1.1.08 Slot 0338 (for a Westville DARC) or IBA GE Slot 0320v (for a Jarrell DARC), then press Enter.

  7. Using the down-arrow key, scroll down to highlight the 2nd Boot Device entry. Press Enter.

  8. A small window will appear with the options available. Using the down-arrow key, scroll down to highlight the ATAPI CD-ROM entry (for a Westville DARC) or PS -slimtype COMBO entry (for a Jarrell DARC). Press Enter.

  9. Using the down-arrow key, scroll down to highlight the 3rd Boot Device entry. Press Enter.

  10. A small window will appear with the options available. Using the down-arrow key, scroll down to highlight the Hard Drive entry (for a Westville DARC) or PM-ST94813A entry (for a Jarrell DARC). Press Enter.

  11. (For Westville)

    Verify the Boot device Priority is set to:

    IBA 1.1.08 Slot 0338

    ATAPI CD-ROM

    Hard Drive

    IBA 1.1.08 Slot 0339

    Removable Devices

    note:

    The removable devices might not be present. This is OK.

  12. (For Jarrell)

    Verify the Boot device Priority is set to:

    IBA GE slot 0320v

    PS -Optiarc CDROMDVD

    PM -ST940815A

    IBA GE slot 0321v

    EFI Boot Manager

    note:

    Above shown information only the example, the name should be related to the actual hardware using in DARC

  13. Press Esc to exit back to Boot menu.

  14. Save DARC BIOS settings:

    1. From Boot menu, arrow to (move to) Exit menu.

    2. Highlight Save Changes and Exit, and press Enter

    3. Highlight [OK], and press Enter, to “Save configuration changes and exit setup.”

      Wait one minute. If the pop up window still appeared, you can close the terminal window directly.

    note: (For Westville)

    After saving the DARC BIOS, the DARC BIOS Setup Utility will disappear (within one minute) and the DARC will begin to Reboot. If the BIOS SETUP UTILITY window does not disappear within a minute, perform the steps within this section again.

    note: (For Jarrell)

    After saving the DARC BIOS, the DARC BIOS Setup Utility will NOT disappear and the DARC will begin to Reboot. Open another shell:

    • {ctuser@hostname} su  -

    • Password: #bigguy

    • [root@hostname] rsh  darc

    • [root@localhost root]

      (If the prompt is displayed exactly as shown, then the login was successful and the DARC was up.)

    • [root@localhost root] exit

  15. Close the Terminal Window.

3.3.3 OS and Applications Installation on DARC from Host Computer

OS will be loaded onto the DARC Node from the Host Computer as long as the DARC BIOS Boot Order is configured for Enable Load.

For details on Serial Over LAN CD Usage, refer to VDARC/DARC Node OS Load Troubleshooting.

note:

The DARC OS was created during the initial Host Applications Software Installation.

  1. Open a Unix Shell and type the following:

    1. {ctuser@hostname} su  -

    2. Password: #bigguy

    3. [root@hostname] cd  /usr/g/scripts

    4. [root@hostname]   ./load_darc_subsystem

    An Attention window appears. See the illustration below.

    note:

    DO NOT follow the instructions in the Attention window. Insert the OS in the Host, Apps DVD does NOT work.

  2. Select OK.

  3. The Unix Shell will display output during the DARC load (approximately 33 minutes). Example output is as follows:

    [root@hostname scripts]# ./load_darc_subsystem

    [load_darc_subsystem] [Start time] Loading the darc subsystem(OS + Apps) takes 30 minutes

    [load_darc_subsystem] [Start time] Loading the darc OS

    [load_darc_subsystem] [Time] Loading the darc OS is complete

    [load_darc_subsystem] [Time] Loading the darc apps

    [load_darc_subsystem] [End time] Loading the darc is complete

    [load_darc_subsystem] [End time] Load started: (Date)   (Start time)

    [load_darc_subsystem] [End time] Load ended: (Date)   (End time)

    [load_darc_subsystem] [End time] Finished loading darc subsystem.

    [root@ hostname]#

  4. A sh window displays the OS load messages and Apps load messages.

    note:

    The DARC OS Load will stop prematurely ONLY if an error is encountered (refer to VDARC/DARC Node OS Load Troubleshooting). An Error Dialog Box will appear with a brief description of the error. Select OK after reading the instructions displayed on the Monitor. Refer to DARC OS Load Pop-Up Boxes for additional information on these error pop-up windows. Also, if any problems arise, verify the correct software disk is installed and verify BIOS Setup Utility Boot Order is correct.

    note:

    A %done status is displayed during the DARC OS load. This is only a timed countdown sequence and does not provide status of the actual load process.

  5. When the DARC load has completed, the sh window will close. DVD drive on host computer automatically ejected. Remove the OS DVD from the DVD drive.

3.3.4 Confirm DARC Software Has Loaded

Verify the OS and Application Software has loaded on the DARC.

  1. Open a Unix Shell and type the following:

    1. {ctuser@hostname} ping darc

    2. [Ctrl C] to stop ping

    3. {ctuser@hostname} rsh darc

    4. [ctuser@darc]

  2. If ping is successful but the prompt [ctuser@darc] does not appear, then the OS is loaded but the DARC Apps load process was not successful.

  3. Verify the OS and Application Software has loaded correctly.

    1. [ctuser@darc] cd  /usr/g/bin

    2. [ctuser@darc bin] ./swhwinfo

    3. [ctuser@darc bin] cat  /GEHC*

  4. Confirm that the swhwinfo results match the software revision shown on the Applications disk.

    • If the revisions match, continue with this procedure.

    • If the revisions do NOT match, reload the software (Host Computer LFC).

  5. Verify that cat results match the Operating System version and Software Build Date.

    Release: GEHC/CTT Linux 6.3.11

  6. Close the Unix Shell.

3.3.5 Return DARC BIOS to Original Settings

(For Jarrell DARC Node) Continue with Set Time and Date

(For Westville DARC Node) The Westville DARC BIOS must be returned to the Restore Settings (operational mode) to avoid a known Intel PXE boot problem, which can occur ramdomly and prevent the DARC Node from booting.

This section describes the steps necessary to restore the BIOS on the Westville DARC Node to its original settings for normal operation. This is a required section for all Westville DARC Nodes.

note:

Be patient. Telnet response may be slow.

  1. Open a Unix Shell and type the following:

    1. {ctuser@hostname} su  -

    2. Password: #bigguy

    3. [root@hostname] service  cliservice  start

    4. [root@hostname] telnet  localhost  623

    5. server: darc

    6. username Enter

    7. password Enter

      Login successful

    8. dpccli>   reset

      ok

      dpccli>   console

      GEHC/CTT Linux 6.3.11

      Kernel 2.6.15-2.5 smp...

      See you on the darc side of the moon

      darc login:

    note:

    A slight delay here is normal. Be patient.

    note:

    If the "reset” and “console" commands fail and the "Active SOL failed" message is displayed, connect to the DARC via SOL, and then type the command "console". With the SOL session connected to the DARC Console, press the "reset" switch (not the power switch) on the front of the DARC and proceed with the instructions below.

  2. Interrupt the DARC boot process to enter the BIOS Setup mode. When the message “Press <F2> to enter setup” appears, press F2.

    note:

    F2 may have to be pressed many times before BIOS setting screen can be seen.

    There will be a short delay before the DARC BIOS setup screen is displayed.

  3. Select Boot Menu, using arrow keys.

  4. Select Boot Device Priority Menu, using arrow keys, then press Enter

  5. Select 1st Boot Device, using arrow keys, and press Enter.

  6. Continue setting Boot Device Priority.

  7. Verify the Boot device Priority is set to:

         ATAPI CD-ROM

         Hard Drive

         IBA 1.1.08 Slot 0339

         IBA 1.1.08 Slot 0338

  8. Press Esc to exit back to Boot menu.

  9. Save BIOS settings:

    1. From Boot menu, arrow to (move to) Exit menu.

    2. Highlight Save Changes and Exit, and press Enter.

    3. Highlight OK, and press Enter, to “Save configuration changes and exit setup.”

      Wait one minute.

    note:

    After saving the DARC BIOS, the DARC BIOS Setup Utility will disappear (within one minute) and the DARC will begin to Reboot. If the BIOS SETUP UTILITY window does not disappear within a minute, perform the steps within this section again.

    • {ctuser@hostname} su  -

    • Password: #bigguy

    • [root@hostname] rsh  darc

    • [root@localhost root]

      (If the prompt is displayed exactly as shown, then the login was successful and the DARC was up.)

    • [root@localhost root] exit

  10. When the darc login: prompt appears, close the Terminal Window.

3.4 Set Time and Date

You must set the date and time on the Host Computer with Application Software down.

  1. Open a Unix Shell and log in as root:

    1. {ctuser@hostname} su  -

    2. Password: #bigguy

  2. Set date and time. Type the following:

    {root@ hostname }#   setdate   Enter, to be prompted through the individual entries. Where:

    Note: Type “q” to quit anytime. Enter to proceed:

    Note: TO BE ACCURATE, this tool will prompt you to enter the “Second”. Watch your clock or PC carefully to enter the proper value, and hit [Enter] at the right second to set the accurate time. Enter to proceed:

    Enter the current Year (1980-2030) [2010]:

    Enter the current Month (1-12) [04]:

    Enter the current Day (1-30) [14]:

    Enter the current Hour (Military Time) (0-23) [18]: 15

    Enter the current Minute (0-59) [13]: 18

    Enter the current Second (0-59) [00]: 10

    Updating the time on the OC and DARC, Please Wait...

    PING darc (172.16.0.2) 56(84) bytes of data.

  3. Upon completing either of the above commands, the user will receive one of the two following responses:

    1. If the DARC Node has been replaced and has no software, the following response will appear:

      --- darc ping statistics ---

      1 packets transmitted, 0 received, 100% packet loss, time 0ms

      The darc is not responding. darc will sync time with oc during next darc reboot

      Current OC date : Fri Apr 14 15:18:00 CDT 2010

      Could not retrieve the SBC TImeZone.

      Please make sure the TimeZones for the OC and SBC are the same.

      [root@hostname]#

    2. If the DARC Node is being reloaded and had software, the following response will appear:

      --- darc ping statistics ---

      1 packets transmitted, 1 received, 0% packet loss, time 0ms

      rtt min/avg/max/mdev = 0.139/0.139/0.139/0.000 ms, pipe 2

      connect to address 10.0.1.2: Connection refused

      connect to address 10.0.1.2: Connection refused

      trying normal rsh (/usr/bin/rsh)

      connect to address 10.0.1.2: Connection refused

      connect to address 10.0.1.2: Connection refused

      trying normal rsh (/usr/bin/rsh)

      Current OC date : Fri Apr 14 16:14:05 CDT 2010

      Current DARC date : Fri Apr 14 16:14:04 CDT 2010

      setdate completed with NO ERRORS.

      [root@hostname]#

  4. Type:

    [root@ hostname ]#   shutdown  -y  -g0   << this is a “zero”, not an “oh”

  5. Wait for DARC to power off & the login prompt on monitor then Turn OFF the Operator Console power at the front switch.

  6. Wait for about 10 seconds, Power On Operator Console.

  7. A pink pop window appears with message that Application cannot auto start.

  8. Select OK.

3.5 Startup application software

  1. Open a Unix Shell and type the {ctuser@hostname}st

  2. Application will be started up automatically.

  3. A pink pop-up Attention Message appears: OC initializing. Please wait….

    note:

    If a message concerning incorrect DAS configuration is encountered, review the Error Log for the Card List issue. Select from the following two methods to alleviate this issue: Flash Download Update or Power OFF the Axial Drive and HVDC at the Gantry service panel - turn OFF DAS Power for 1 minute - turn DAS Power back ON - turn Axial Drive and HVDC at the Gantry service panel back ON - Flash Download Update - verify error message has disappeared. If error message reappears then troubleshoot the DAS/DCB.

  4. Select OK for other pink message boxes that appear throughout the reboot process.

    After each reboot during the software load process, an 'Unrecognized X-Ray Tube' message will be displayed (as shown below) until the tube identity has been selected (later in this procedure) and 'Flash Download' has also been performed.

  5. If any Recon Selftest Failures are encountered, review the error log. Make certain to note the errors for troubleshooting after the LFC.

3.6 Load Other Service Software

(For GE Heathcare Employees or Licensed Customers Only) If applicable, load Class C Service Software now.

(For GE Healthcare Employees Only) If applicable, load Class M Service Software now.

3.6.1 Service Pack Load

note:

Before install any Service Pack or Patch, please confirm that the Service pack/patch version matches the Application Software version.

note:

If Service Pack questions arise, contact Local GE Service.

  1. Open a Unix Shell.

  2. If Application software is up, perform{ctuser@hostname}cleanMon.

  3. In the Unix Shell, become root:

    {ctuser@ hostname }   su  -

    Password: #bigguy

  4. Check which Service Pack is installed, type {root@hostname}#swhwinfo.

  5. Insert the Service Pack CD into DVD drive in the host.

    note:

    Service Pack CD will include any new service pack and all previous released service packs that are still applicable. Load all of the Service Packs included in the latest Service Pack CD in sequence.

  6. Perform the following steps to install the Service Pack CD:

    1. Type the following install script:

      [root@ hostname ]# patch_install -c

      Any Service Packs on the Service Pack CD will be listed. Before installation of each pack, the window will wait for user's confirmation as follows:

      I will install update Patch Name , is this ok ? [y/n]

    2. Input y to install this patch or n to cancel installation of this patch.

    3. After installing the Service Pack CD, type patch_status (Class M service key inserted is required to use this command) in the Shell window to determine which Service Pack patches were installed (if any). The following is an alternate command to verify the Service Pack load:

      [root@ hostname ]# showprods | grep  -i ServicePack

    4. Type:[root@hostname]#reboot

      note:

      A reboot is always required after a pack is installed. Additional processes may be required for installing certain Service Pack media. Refer to the instructions sent with the Service Pack.

3.7 Install Software Options

Notice Image
  • notice
  • For Perfusion and Denta Scan: If you loaded software in a language other than English, please reconfig, changing the language to English, to load these two options. Otherwise, the LFC procedure may fail.
Notice Image
  • notice
  • Options must be loaded before Protocols.
note:

If performing a Load From Cold (LFC) for the first time and Software Option Licenses plus site-specific configuration has not been saved to System State, Software Options will need to be loaded manually.

  • Follow the procedures in this section to install the options manually.

    OR

  • Software Options licenses will be loaded during Restore System State. Proceed to next section.

  1. Insert the Options DVD in the SCSI Tower DVD-RAM drive.

  2. With the Applications up, select the SERVICE DESKTOP.

  3. Select CONFIGURATION.

  4. Select INSTALL OPTIONS. A blank Software Options screen appears:

  5. Select INSTALL. A Select Mechanism window opens (see illustration, below). Select the mechanism through which you want to install Option Keys.

  6. Select Permanent. A Select Device window opens (see illustration, below). Select the mechanism through which you want to install the Permanent Option Keys.

  7. Select the MEDIA button and insert the Options DVD or MOD. Available options appear on the Software Options screen.

  8. Perform the following Option installations, if applicable:

    note:

    The order of installation is critical.

    1. VolumeViewer

    2. CardIQ2

    3. CardEP

    4. Connect pro (enable pps)

    5. Exam Split (VES)

  9. Pick remaining options one at a time from the Available Options list and select INSTALL to update each selection and place it on the Installed Options List.

  10. When the process is complete, select Quit then Quit to close the window.

3.8 Restore System State

note:

Restart Application to Restore System State

  1. Open a Unix Shell and verify the SCSI Tower MOD and DVD are present:

    {ctuser@ hostname }   scsistat

  2. Close the Unix Shell.

  3. Insert the Save System State DVD into DVD-RAM SCSI Tower drive.

  4. Select the SERVICE icon.

  5. Select: UTILITIES

  6. Select: SYSTEM STATE

  7. Select ALL

  8. Select RESTORE

  9. Verify the overall system state content has restored correctly (look for message “Save/Restore System State Completed Successfully”), then select CANCEL.

  10. When completed, select DISMISS or close the window.

    note:

    If Scan Hardware Reset question appears - answer [NO]. This reset is performed during FLASH Download Update.

  11. Select Quit when Dose Check Configuration screen pop up.

3.9 FLASH Download

note:

The Flash Download takes anywhere from 5-30 minutes, depending on which subsystems require updates.

  1. Before running the Flash Download Tool, verify the reset switch at the gantry is not flashing and reset the 120 VAC, if necessary. Also, try to ping the following (press Ctrl-C and close the shell when finished pinging), to see if there are any issues:

    • ping  orp

    • ping  stc

        - OR -

      ping  tgp

      If below information appear, it mean the ping is successful:

      64 bytes from TGP (192.9.220.2): icmp_seq=1 ttl=64 time=0.638 ms

      64 bytes from TGP (192.9.220.2): icmp_seq=2 ttl=64 time=0.588 ms

      64 bytes from TGP (192.9.220.2): icmp_seq=3 ttl=64 time=0.595 ms

      64 bytes from TGP (192.9.220.2): icmp_seq=4 ttl=64 time=0.876 ms

      If below information appear, it mean the ping is failed:

      bj12_oc (192.9.220.1) icmp_seq=1 Destination Host Unreachable

      bj12_oc (192.9.220.1) icmp_seq=4 Destination Host Unreachable

      bj12_oc (192.9.220.1) icmp_seq=5 Destination Host Unreachable

  2. Select the SERVICE DESKTOP.

  3. Select in sequence: UTILITIES > FLASH DOWNLOAD.

  4. Select UPDATE. Ignore any initial errors.

  5. When the pop-up shown below appears, enter the Collimator Serial Number, and select Accept.

    note:

    This pop up may not appear if the Collimator Serial Number was retrieved from the System State. If the pop up does not appear, go to step 7.

  6. When the pop-up shown below appears, select Yes, to save the CCB file.

  7. When then Flash Download process is complete, select DISMISS or close the window.

    note:

    After Flash Download the system will report the following message:

    The entire Generator database has been reset. You may now restore JEDI runtime parameters. Filament calibration is required before scanning patients.

    If you are reloading software, this message may not appear. If you get this message, you must perform a Filament Calibration, because the JEDI database was reset.

3.10 Restore JEDI Runtime Parameters

Restore the Jedi Runtime parameters, refer to Software-> HV Subsystem UtilitiesJEDI Generator Tool for how to restore them.

3.11 Feature Installation

3.11.1 Product Network Filters (PNF)

For general information on Product Network Filters, please see Product Network Filter Theory.

If your customer has special network requirements, then proceed toConfigure Product Network Filters now. When PNF configuration is complete, return to this procedure.

note:

If network problems arise after configuring PNF:

  1. Turn OFF PNF.

    • If the problem still exists with PNF off, then troubleshoot the network.

    • If networking issues no longer exist, then call the OLC Connectivity Team to resolve the issue.

  2. Once the PNF setup problem is fixed, turn PNF back ON.

3.11.2 AW Direct Connect

If the site requires the configuration of AW Direct Connect, then configure it now (see AW Direct Connect). When configuration is complete, return to this procedure.

3.12 Tube Identification

Notice Image
  • notice
  • (For Scanners with GE Tubes) If the software is installed by a non-GE person or the GE field engineer does not have a service key, a GE Field Engineer is required On-Site within 30 days, to perform the verification portion of this procedure. This verification cannot be done by non-GE employees. If a GE Service employee is not currently on site, please contact your GE Healthcare representative to arrange a visit. This section is absolutely critical to perform. Failure to do so will result in nuisance pop-ups to the customer and tube performance may decrease.

follow the procedure shown in the Flowchart below.

Verification that a tube is a GE Healthcare tube (called “GE Tube” in the TIC tool) can be done by visually checking the Manufacturer Name, which can be found on the tube rating plate.

  • If you are installing a GE brand tube, please confirm tube brand by checking tube rating plate, then select [GE Performix Tube] or [GE MAXIRay Tube].

  • If rating plate does not identify the tube as a GE brand tube, click [ALL OTHERS]

note:

Some Advanced features may be disabled and pop-up warnings will be activated

note:

Do not double-click the Tube Certification Tool. This will cause more than one tool window to be displayed; one with message ‘service key information not available’. If this happens, close the window and try again. If this happens more than once, reboot system and try again.

Figure 1. Selection of Tube Identity

Flowchart Note:

Possible pop-up messages at start-up:

  • If the tube selection is GE tube without time limit, no pop-up messages relating to tube identity on boot up.

  • If the tube selection is GE with time limit, a message with days remaining for GE FE to verify tube will be shown on boot up until GE FE removes the time limit with service key. If not verified by GE FE within the time limit, the system will default to 'All Others'.

  • If the tube is set to 'All Others', unrecognized x-ray tube installed message will always be shown at boot up.

Please refer to Tube Install Certification Tool - Screens for examples of the screens displayed by the Tube Install Certification Tool.

3.13 Restart the System

3.13.1 Reconfig and Restart the System

Notice Image
  • notice
  • NEVER Use CTRL - ALT - DELETE to reboot the host computer. This technique will NOT reboot all console subsystems, and as such is an unacceptable practice.

To restart the system:

  1. Replace the Hospital Backbone Ethernet cable to the Console Bulkhead Assembly (located at the rear of the Operator Console).

  2. Shutdown Application, then Open a Unix Shell:

    1. {ctuser@hostname}su -

    2. Password: #bigguy

    3. Type reconfig

    4. Select config and confirm the all configuration is correct

    5. Click Accept

    6. Select Yes to Reboot system, Startup Application.

3.13.2 If HIPAA Present set to ON - Admin Screen

When the system comes up the following screen will be displayed if HIPAA Present was set to On during the LOAD process. Verify the admin screen below has the following 'Select user':

  • Select user: root

  • Password: #bigguy

3.14 Additional Processes Required

For XW8400 Host Computer (GOC4 with xw8400)

  1. Autovoice Settings

    If the Autovoice setting is equal to 85 (i.e. factory default setting), then do not perform volume adjustment. If the Autovoice setting is higher or lower than 85, then it is recommended to perform volume adjustment.

  2. Volume Adjustment

    1. Select the “Autovoice Volume” (“audioSetting”) tool from the Tool Chest menu to increase the volume as needed.

    2. Click Save, then OK.

3.15 System Sanity - Scanning & Network Operation

note:

Load any applicable software FMIs (software patches) prior to performing system sanity scans.

  1. Successfully perform a Scout scan.

  2. Successfully perform a Helical scan.

  3. Successfully perform an Axial scan.

  4. If have DICOM print configured, perform DICOM print to confirm network operation (Product Network Filter (PNF) setup).

  5. If have archive server configured, perform image archive & retrieve to confirm network operation (PNF setup).

Software Load Process is now complete.

3.16 Retro Recon Test

The Reconstruction (not Scan) portion of the system can be tested at this point.

When Application Software is up, perform the following:

  1. Select Recon Management, and select Restart Queue if not in the Idle Mode.

  2. Select RETRO RECON on the left Monitor.

  3. Select the rat gold series.

  4. Select SELECT SERIES.

  5. Select CONFIRM.

  6. Verify the image(s) reconstruct and are displayed.

  7. Remove Rat Gold generated images via Image Works.

  8. Select QUIT.

3.17 Recon Self-Test

note:

only applicable with the Service security key

  1. Select the Service Icon.

  2. Select Diagnostics.

  3. Select Image Generation

  4. Select Recon Data Path.

  5. Verify it is set to 1 and ALL.

  6. Select Run.

  7. Verify Recon Data Path tests pass.

  8. Select Dismiss or close the GUI.

3.18 Finalization

  1. Perform FastCal as required.

  2. Remove the System State DVD-RAM from the SCSI Tower.

  3. Replace the front and rear Operator Console covers.

  4. Save System State:

    • Insert the Save System State DVD into the Peripheral Tower DVD-RAM drive.

    • Select SERVICE DESKTOP.

    • If reloading software, select UTILITIES

    • Select SYSTEM STATE

    • Select ALL to select all the cals, characterization, etc.

    • Select SAVE

    • If applicable, select OK when the following message appears: System State Media Status: Please insert a DVD or MOD into the drive and press Save again.

    • When completed select DISMISS.

    • Save all reformat / recon protocols.

    • Close the Service Desktop window in the upper left corner of the screen.

    • Sites performing the next sub-section should not remove the DVD from the Peripheral Tower DVD-RAM drive.