CT LFC Procedure 07mw11

07MW11.
10 SW LFC (GOC3/GOC4)
Last Revised: 10 October 2008
1 Scope
This Load from Cold (LFC) procedure supports GOC3 and GOC4 GRE/Xtream Operator Console
systems using this version of 07MW11.10 or upgrading from versions 06MW03.5 or 06MW29.7. It
also supports upgrading from GOC1 (IRIX) and GOC2 (Linux-Pegasus) Operator Consoles to
GOC3/4.
When loading software, this LFC document must be performed as written in its entirety to be
successful (except for a DARC reload).
 HiSpeed QX/i
 LightSpeed 1.X
 LightSpeed 2.X
 LightSpeed 3.X (4- and 8-slice)
 LightSpeed 4.X (16-slice)
 LightSpeed 5.X Pro16 (80kW & 100kW) - MDAS & GDAS
 LightSpeed 5.X RT (4 slice)
 LightSpeed 5.X (4/8/16 slice) - MDAS& GDAS
 BrightSpeed (4/8/16 slice)
BrightSpeed Select (with glass tube) and LightSpeed 5.X RT (16 slice) systems are not
NOTE:
supported with this software version.
For a description of the procedural flow in this document, see Table 1.
2 Software Deliverables
 5212704 - LightSpeed Xtream Console Operating System
Version - GEMS Linux 6.2.9 OS
 5220445 - LightSpeed Applications Software DVD
Version 07MW11.10
 5212235 - Xtream Serial-Over-LAN Service Software
Supports: DARC/VDARC/IG/VIG Westville or Jarrell hardware, and OS versions: 4.3.16

and 6.2.9
The Xtream Serial-Over-LAN Service Software is used during the LFC if instructed
via a pop-up message box. When unable to connect to the DARC Node via a
telnet session (with the 'service cliservice start' enabled), this CD may be used to
NOTE:
reload the BMC information. 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 (approximately 1-2
minutes).
 HP xw8200 BIOS Floppy Set - 5191796-3

o 5191796 BIOS 2.10 Floppy
o 5191796-2 BIOS 2.10 Configuration Floppy
 HP xw8000 BIOS Floppy: 5138295 BIOS 1.13 Floppy
The Service Pack software may or may not be included with the initial release. Service
NOTE:
Packs are released as required. Always use the latest revision of the Service Pack.
3 Pre-LFC Checks and Information Gathering
NOTICE
Do not load this software on a PET system.
Do not load this software on a CT GOC1 (IRIX, Pegasus) or GOC2 (Linux, Pegasus)
Operator Console. This software requires the presence of a DARC Node
subsystem.
3.1 Required Linux Information Gathering
The following information must be recorded, it is NOT saved on System State:
1. If you choose, you may start the Save System State process (see Table 2) at this time.
2. Verify and record specific system information in Section 1 of the 07MW11.10 GRE/Xtream
Operator Console Information Sheet.
3. With Application Software up, record the [User Prefs] Screen and Film Large Font
Annotation Groups selections. Refer to Section 14 to understand the information that may
need to be gathered.
4. Select Autovoice Volume (Toolchest, upper right corner) and record the Left Value and
Right Value settings. The path to view the all audio settings is as follows:
{ctuser@hostname} audioSetting (PCM2 info is the left and right value as described
above).
5. Record DICOM information as required in Section 3 of the 07MW11.10 GRE/Xtream
Operator Console Information Sheet
6. Open a Unix Shell and type:{ctuser@hostname} installOptions
7. Check the box on the Information Sheet next to each Option currently loaded on the
system.
8. If Exam Split is present, perform the following to determine ves or hes.
a. {ctuser@hostname} su -
b. Password:<password>
If the Password has not been modified by the site and is not known, the
NOTE:
correct course of action is to contact Local GE Service.
c. [root@hostname] ls -l ~ctuser/ves/.hesMode
NOTE: There are no spaces in the phrase ~ctuser/ves/.hesMode.
d. 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.
9. If the results show “No such file or directory,” then VES (Virtual Exam Split) mode is
configured. Record Exam Split Mode (Hard or Virtual). This info will be used during the LFC
Options Installation.
10. If you have the ConnectPro option and use PPS, perform the following (refer to example):
{ctuser@hostname} cd /usr/g/ctuser/resources/pps
{ctuser@hostname} head -12 ppsserver.cfg
Output Example:
PPS_REMOTE_AE_LIST =
# AppTitle,IPAddress,IPPortNo,HostName;
DICOM_TEST_RMT,3.70.204.86,4500,Default;
Record the PPS Information per the following EXAMPLE:
# AppTitle IPAddress IPPortNo HostName

DICOM_TEST_RMT 3.70.204.86 4500 Default
Record the AppTitle
Record the IPAddress
Record the IPPortNo
Record the HostNameRecord
3.2 Additional Console/Gantry/Configuration Information Gathering (not

required)
The information in this section IS SAVED to System State. It is up to the user to decide if the
information gathered in this section is needed. The information may be gathered electronically and
placed onto media (floppy, CD, flash drive).
1. SCSI Tower termination jumper must have been completed. If this has not been completed,
the user may fail the Save/Restore System State process on older SCSI Towers.
2. Visually verify that the SCSI Tower DVD-RAM power is applied.
3. If applicable, verify that the SCSI Tower terminator LED is lit (located at the rear).
4. If a DASM is used on the system, verify that it is disconnected.
5. Verify that the Host Computer DVD-ROM and floppy drives do not have any media on
them.
6. Record additional information in Section 2 of 07MW11.10 GRE/Xtream Operator Console
Information Sheet.
7. If present, verify SDDA (GOC3 only) has its power LED lit.
8. If present, verify ICOM has its power LED lit. (See Illustration 1.)
9. Record the Tube Information in Section 4 of 07MW11.10 GRE/Xtream Operator Console
Information Sheet. When multiple files exist, record information for a minimum of two
years. Select the appropriate software step below.
10. (For 06MW03.X and 06MW29.7 Software) Open the Service icon. Select [Error Logs] and
then [Tube Usage]. Select [Details] and record the following as required for each tube file
applicable to the two-year rule on the Console Information Sheet:
a. Tube serial no.
b. Installed on
c. Last scan on
d. Tube mA (patient and non-patient)
e. Scan Seconds (patient and non-patient)
f. Total Patient Exams
g. Select [Back] for next tube as required.
h. Close the Tube Usage window when information gathering is complete.
11. (For 07MWxx.x Software) Open the Service icon. Select [Error Logs] and then [Tube
Usage]. Select [Details] and record the following as required for each tube file applicable to
the two-year rule on the Console Information Sheet:
a. Tube serial no.
b. Installed on
c. Last scan on
d. Exam Usage Total (patient and non-patient)
e. Click on [Advanced metric] reporting for next tube as required.
f. Tube mA Seconds (patient and non-patient)
g. Scan Seconds (patient and non-patient)
h. Select [Back] for next tube as required.
i. Close the Tube Usage window when information gathering is complete.
12. (For GOC1 (IRIX) and GOC2 (Linux-Pegasus) systems) Dismiss the Common Service
Desktop.
4 Pre-LFC Save System State

The system state backup saves vital calibration and scanner files. Follow the appropriate
procedures throughout this document precisely or valuable information may be lost. This process
takes approximately 10 minutes for GOC3/4, but in some cases it may take up to 30 minutes. This
process is more involved for GOC1 (IRIX) and GOC2 (Linux-Pegasus) upgrades.
Perform one of the following methods to Save System State, depending on current Operator
Console type. A current version of the System State is a requirement for continuing with this LFC
procedure.
4.1 GOC1 IRIX Systems Upgrading to Linux - Save System State Twice
For GOC1 (IRIX) systems, Save System State for Upgrading to Linux, see Table 3.
4.2 GOC2 Systems Upgrading to GOC3/4 - Save System State Twice
For GOC2 (Linux-Pegasus) systems, Save System State, see Table 4
4.3 GOC3/GOC4 - Save System State Once

Follow the procedure described in Table 2. Upon completion, proceed to the LFC installation
procedures in Section 6.
5 GOC1/GOC2 Console Upgrade Only - Install GRE/Xtream

Console
For GOC1/GOC2 Console Upgrade Only - Install GRE/Xtream Console, see Table 5
6 Host Computer LFC

Whenever the Host Computer LFC is performed, the DARC software must be loaded using the
same software set version. Additionally, if the DARC Node is not loaded, ssh (Security Shell) issues
will result in an Unknown Host failure.
Before proceeding you must disconnect the console from the Hospital Network. Failure to
NOTE:
do this may result in the console broadcasting traffic out to the entire Hospital network.
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.
6.1 Host Computer BIOS Requirement
1. Open a Unix Shell and become root:
{ctuser@hostname} su -
2. Password: <password>
If the Password has not been modified by the site and is not known, the correct
NOTE:
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 = 1.13 for xw8000
Version: 786B8 v2.10 = 2.10 for xw8200
4. Ensure that the Host Computer BIOS version is an authorized version as shown above.
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:
o For HP xw8000, see PC BIOS Install& Setup for HP xw8000 Host Console.
REQUIRED: Manually configure all BIOS settings at this time.
o For HP xw8200, see PC BIOS Install& Setup for HP xw8200 Host Console.
REQUIRED: The HP xw8200 has the ability to place the BIOS 2.10 Configuration
Floppy into the Host and configure all BIOS settings without any manual entries.
Load the BIOS 2.10 Configuration Floppy at this time.
6.2 Linux Operating System (OS) Software Load - Host Computer
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.
During the OS load you need to select "ignore" twice when it complains about I/O errors
with a SCSI device. These messages may occur with systems without a DASM:
NOTE:
Input/output error during read on /dev/sd?
Input/output error during write on /dev/sd?
1. Unplug the Hospital Network (HSP) cable from rear Console bulkhead. (See Illustration 2.)
2. Label the cable as HSP and set it aside during LFC.
3. Remove the Operator Console's front cover.
4. If present, ensure that the DARC/IG Troubleshooting Video Cable is not connected to the
Scan or Display Monitors during the software load.
5. Insert the OS DVD into the tray on Host Computer DVD-ROM Drive.
NOTE: The Host Computer must be powered ON to insert the disk.
6. Select one of the following methods to re-power the Operator Console:

a. If Applications are up select the [Shutdown] icon. On the Attention screen
(Illustration 3), select [Restart], then [OK].
b. If Application Software is down, at the Toolchest open a Unix Shell and type:
i. {ctuser@hostname} halt
ii. The Operator Console monitor will display a System halted message
when it is acceptable to power OFF the Operator Console. (See Note.)
(For 06MW03.X Software) Wait 1-2 minutes after the “System

halted” message appears, to allow the VDARC Node to properly
NOTE:
power-down. SW release 06MW29.7 and later has corrected this
issue.
iii. Power OFF the Operator Console at the front panel switch. (See
Illustration 4.)
iv. (For GOC3 Consoles) The Trackball USB-to-PS2 converter must be Part
# 5195935 (provided with FMI 25389). This prevents problems with the OS
load (mouse confusion) on the Host.
v. Wait 30 seconds to allow the disk drive to settle; then power ON the
Operator Console at the front panel switch.
7. As the Host Computer restarts, the booting process messages appear. After the booting
process completes, the boot: prompt appears. (The OS is a bootable media.)
8. At the boot prompt, type the following depending on system type:
(For English Keyboard only) GEHC2
(For International Command only) iGEHC2
If a DASM is connected, select [Ignore] as required for IO errors. If the boot:

prompt does not appear, then either the DVD is unusable or the Console
NOTE: Operating System Media is not installed in the drive. Typing GEHC (or iGEHC)
results in both scan and display being on one monitor and requires a LFC. Typing
any other command not listed in this procedure will result in a LFC.
9. After approximately 20 minutes, the OS is loaded on the Host Computer. A window

appears.
10. Remove the OS DVD from the Host Computer DVD-ROM drive when it ejects and close the
tray.
11. Press <Enter> to reboot.
12. The Host Computer begins to reboot.
Do not insert the Applications Software DVD into the Host Computer until the Host
NOTE: has completed rebooting and the [root@localhost ~] window appears,
displaying the prompt:[root@localhost ~]. (See Illustration 5.)
(For 6.2.9 OS) The bootup screen changes for each OS version. The 6.2.9 OS
Boot-up Screen display (shown below) contains output that may be misunderstood
as a Host hardware or software issue. For example, in the screen below refer to
“PCI: Failed to allocate mem resource #6” and “FATAL: Error
NOTE:
inserting...” errors). These are normal typical messages. Additionally,
whenever the HSP Ethernet cable is disconnected from the Operator Console
bulkhead, Firewall PNF errors may occur. Ignore these errors. Any other errors
should be investigated.
14. After the Host Computer reboots, verify that a window appears on the Display monitor with
the prompt: [root@localhost ~]#.
15. In the root@localhost ~ window, verify 3 Host hard drives and the SCSI Tower MOD and
DVD are present (for a total of 5 items listed for xw8000 and xw8200).
[root@localhost ~]# cat /proc/scsi/scsi
6.3 Application SW Load on the Host Computer
All Applications software will be loaded to the Host Computer during this process.
(For GOC3 Consoles) If a mouse hang occurs after the OS load on the Host, install the
correct Trackball USB to PS2 converter and reset the Host to continue. GOC3 Operator
NOTE:
Consoles must use Part # 5195935 for the Trackball USB to PS2 converter. This converter
is located at the rear of the Host's USB ports.
1. Open the tray on the Host Computer DVD-ROM Drive.
2. Insert the Applications DVD into the DVD-ROM Drive and close the tray.
3. Select the [Run Command] in the Warning box. (See Illustration 6.)
NOTE: If the Warning pop-up box does not appear after two minutes, type the following in
the Welcome box pop-up:
root
install
Type the following in the terminal window with the Application media still installed:
mount /media/cdrom
/media/cdrom/autorun
4. Select the [Load] button in the CT Software Installation window. (See Illustration 7.)
5. System State decision for the Install INFO decision box. (See Illustration 8.)
o If you do not have a valid System State, select [No].
o Insert the System State DVD into the SCSI Tower if you have a valid System State.
Wait until the DVD LED stops blinking, then select [Yes] or [OK] as needed.
Another Install INFO box appears. (See Illustration 9.)
6. If you selected [Yes] , select [ok].
7 Config or Reconfig Setup

1. Select the [System] tab. The System Settings screen appears. (See Illustration 10.)
2. Verify that the:
o Next Patient Exam # is the value restored from System State. Otherwise, set it to 1.
o Proper Time Zone is selected. Failure to set this at this point will result in time jump
issues.
3. Select the [Preferences] tab. The Preferences Settings screen appears. (See
Illustration 11.)
The current illustration for the Preferences tab will not show the additional
NOTE: languages until after Service Pack 2 (or greater) is loaded. At that time the screen
will appear as in Illustration 12.
4. Input the correct:

a. Units for patient weight
b. Language
c. AutoVoice Language
d. Date Format
e. Time Format
f. Preference for Modified in Room Start
Modified in Room Start is normally Off, unless the site is in Japan and/or
NOTE:
the customer has requested that this be turned On.
g. Preference for HIPAA Present
HIPAA Present is normally Off, unless the customer requests HIPPA to be

NOTE:
On.
h. Site preference for Dose Information Display

Dose Information Display is for the site to use in monitoring calculated
NOTE:
Patient Dose.
 [On] (full CTDiw Display)

 [On without Total DLP] (no Dose Length Product Display), or
 [Off] (no CTDIw Display)
i. Preferred kVs
j. Target Noise Index Table
5. Select the [Hardware] tab. The Main Hardware screen appears. (See Illustration 13.)
6. Click on the Hardware Settings (orange button) to access the Select hardware
configuration.screen. (See Illustration 14.)
7. Click on [CT ONLY]. Then, depending on the DAS / Detector rating plate type, click on one
of the following: non-VCT hardware configuration selections.
8. Select [OK] to exit hardware configuration.
9. On the Hardware Settings screen, click on the proper Table Type. (See example screen in
Illustration 15.)
Check the label/rating plate at the front bottom of the Table (Illustration 16),
NOTE:
closest to the Gantry (by the MTCB) and determine the Table Type.
10. Select proper PDU type.

11. Click on the configured (0, 1, or 3) Number of IGs. (See Illustration 15.)
SDAS 4-slice systems, MDAS 4-slice / 8-slice systems cannot upgrade from the 1
single/standard IG Node to the 3 IG Node upgrade option. BrightSpeed 4/8/16
NOTE:
systems may be configured with 0 IG’s, 1 IG, or 3 IG’s depending on the specific
Console type.
12. Select the [Network] tab. The Network Settings screen appears. (See Illustration 17.)
The current illustration for the Network Settings tab will not show the Station Name
NOTE: until after Service Pack 2 (or greater) is loaded. At that time the screen will appear
as in Illustration 18.
13. Gateway Parameters:

. 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.
a. 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.
The Station Name defaults to the Host Name if it is left blank. If entered, it:
 MUST NOT exceed 16 characters.

NOTE:
 MUST only contain the following characters: a through z, A
through Z, 0 through 9, - and _
b. Host Name
The Host Name identifies the hostname and AE Title of the scanner.
 It MUST NOT exceed 16 Characters.

 It MUST only contain the following characters: a through z and 0
through 9
NOTE:
 With the introduction of Service Pack 2 (or greater), A through Z ,
-, and _ characters are allowed.
 MUST have at least one Alpha Character (A - Z or a - z) or a
Special Character (_ or -)
c. IP Address - Site supplied

i. If the supplied hospital IP Address starts with 172.16.0.xx, click on
Advanced Options. Click on the Change DARC Subnet? box, then click on:
169.254.0. Do not input a User defined IP address unless specified by
GE Healthcare Service.
Sites requiring a User Defined IP address will be required to load

the SOL CD during the DARC Node software load process. After
NOTE: the LFC procedure is completed, a reconfig (as root) must be
performed and the DARC Subnet address can be modified.
Additionally, the System State should be saved.
ii.To set the DARC subnet back to default value of 172.16.0.x, deselect the
Change DARC Subnet? box.
d. Net Mask - Site supplied address.
If the hospital backbone IP address is 192.9.220.xx, the Net Mask

NOTE:
must be set to 255.255.255.252.
e. Broadcast Address - Site supplied address

f. Default Gateway - Site supplied address
g. If your customer has AW Direct Connect, click on Enable AW DirectConnect?.
Insert any information as required.
Complete the LFC, configure AW Direct Connect in Section 17.3. (Do not
NOTE:
configure AW Direct Connect now.)
h. 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 have NIS,
ensure that these selections are not checked.
 Domain Name: add your name here (get name from customer’s network
administrator).
 IP Address of Server: add your IP address here (get IP address from
customer’s network administrator).
i. 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.
j. Change DARC Subnet? (under Advanced Options, see the IP Address Gateway
Parameter for specific information. This box is normally not selected.
If the [Accept] tab is selected with the <Num Lock> hard key activated,
NOTE:
load failures may result.
14. Verify that the <Num Lock> hard key on the keyboard is not active. If it is, deselect it to
enable the [Accept] tab in the next step.
Make sure the <Num Lock> button on the keyboard is not active. If it is, deselect it
NOTE: and then select the [Accept] button in the next step. Failure to deactivate the Num
Lock results in load issues.
15. Select the [Accept] tab at the right corner of the User Interface.
CAUTION: FAILURE TO SELECT THE CORRECT 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. THIS ISSUE CAN AFFECT ANY MDAS OR GDAS TYPE SYSTEM
WHEN FLASHED WITH THE WRONG DAS HARDWARE CONFIGURATION FIRMWARE.
16. An Install INFO Acceptance window appears. (See Illustration 19)

17. Select [Yes], if correct.
If the information is not correct, select [No]. Selecting [No] returns you to the
Hardware tab. Select [Hardware Settings] and select the correct hardware
NOTE: configuration from the displayed list. Select the [Accept] tab again, followed by the
[Yes] button on the Install INFO hardware box to accept the new hardware
configuration.
18. A no-action- required pop-up message appears in approximately 1 minute:
Please make sure the CT application media 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.
Do not remove the Applications Software DVD from the Host Computer until
NOTE:
instructed to do so.
19. After the system reboots, an sh window appears. (See Illustration 20.) The Apps software
load begins.
20. After approximately 10-15 minutes, the system prompts for reboot (see Illustration 21.)
Answer [Yes]. The system is going down for reboot NOW.
During the reboot, a message may appear to the effect that the system was not
NOTE: able to determine what the tube type was and to run the TIC tool. This message
should be ignored at this time.
21. After approximately 3 minutes, the CT Software Auto-Start Disabled pop-up box
appears. (See Illustration 22.) Select [OK].
22. Remove the Applications Software DVD from the Host Computer by pressing the button on
the DVD-ROM drive to open the tray.
23. Close the Host drive tray.
24. When the Host Computer has completed its reboot, you may continue.
8 DARC Software Load Process

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.
8.1 DARC Reloads Only- Confirm Host Software
1. Open a Unix Shell and type the following to determine Host Computer software information:
{ctuser@hostname} swhwinfo
07MW11.10<hardware revision info here>
2. {ctuser@hostname} swhwinfo –os for OS version
Release: GEHC/CTT Linux 6.2.9
Built: Wed Jan 3 11:05:37 CST 2007
3. Confirm that the Host OS and Apps results match the OS and Apps software versions to be
loaded for the DARC Node.
8.2 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"
(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.)
o Westville DARC Nodes will contain a WV string (example, SWV25)
o Jarrell DARC Nodes will contain a JR string (example, SE7520JR23)
Westville DARC2 Node (Front)
Jarrell DARC2 Node (Front)

3. If the DARC is Westville, proceed to Section 8.3.
If the DARC is Jarrell, proceed to Section 8.4.
8.3 Westville DARC Nodes Only: DARC BIOS Boot Order Enable Load
Only Westville DARC and DARC2 Nodes require DARC Node BIOS to be enabled and then
restored. Jarrell DARC Nodes DO NOT require a DARC BIOS Boot Order change before or after a
software load (unless the vendor shipped the BIOS with incorrect settings or the DARC has been
previously used and restocked).
This section describes the steps necessary to change the Westville DARC Node BIOS to Enable
the OS/Apps load from the Host Computer. The Westville DARC Node BIOS Boot Order is modified
for Enable before the DARC Node OS load, and must be returned to final operational Restore
settings after the DARC Node load. Failure to return the Westville DARC Node BIOS Boot Order to
the Restore settings after the load process is complete may result in DARC boot issues (DARC
Node fails to boot up) that can occur randomly at any time.
If the DARC OS load fails, a pop-up may appear stating that the DARC BIOS must be
checked. Try reloading the SOL CD. After the BIOS is checked, if the DARC load
NOTE:
continues to fail, determine if the problem is the Ethernet cable, Host NIC, or DARC Node
(look for the LAN LED activity on the DARC).
1. Open a Unix Shell and type the following:

b. Password: <password>
NOTE:
c. [root@hostname]service cliservice start

d. [root@hostname] telnet localhost 623
e. Server:darc
f. Username:<Enter>
g. Password:<Enter>
Login successful
h. dpccli> reset
ok
dpccli> console
A slight delay here is normal. Watch the screen for the [F2] prompt. If the
NOTE: prompt is missed for entering the BIOS, close the Telnet session and
retry.
2. Interrupt the DARC boot process to enter the BIOS Setup mode. When the message
“Press< F2> to enter setup” appears, press [F2].
<F2> must be selected in a timely manner or the process to access F2 will need to
NOTE: be repeated. There will be a short delay before the DARC BIOS setup screen is
displayed.
3. For DARC Node BIOS screen setup instructions for Westville, refer to Change DARC BIOS
Boot Order - Enable Load.
Verify that the initial Boot device Priority for OS load is set as shown below.
IBA 1.1.08 Slot 0338
ATAPI CD-ROM
Hard Drive
IBA 1.1.08 Slot 0339
Removable Devices
For Jarrell DARC Nodes, refer to Change DARC BIOS Boot Order - Restore
NOTE:
Settings, Step 3.
4. After saving the DARC BIOS, the BIOS SETUP UTILITY window should disappear (within
approximately one minute) and the DARC will begin to reboot. If this window does not
disappear within a minute or so, close the window and attempt to load the DARC Node. The
DARC Node may require a reset.
5. If necessary, close the Terminal Window.
8.4 OS / Applications Installation for DARC from Host Computer
No DVD is required during a LFC.. OS will be loaded from the Host Computer (initial OS load)
onto the DARC Node as long as the DARC BIOS Order is configured properly for your DARC Node
hardware type. The Apps will be loaded at this time also. This process takes approximately 30 - 35
minutes.
A DVD may be required for Reloading / Replacement of a DARC Node. The user must perform
the [root@hostname scripts] ./load_darc_subsystem -restart for all DARC Node
replacements or any DARC Node reloads.
1. Open a Unix Shell and type the following:

NOTE:
c. [root@hostname] cd /usr/g/scripts
The user must perform the [root@hostname

scripts] ./load_darc_subsystem -restart for all DARC Node
replacements or any DARC Node reloads that may experience an
unexpected failure. An Attention box may appear instructing the user to
NOTE: insert either the OS DVD or the Apps DVD. It does not matter which media
DVD you insert into the Host Computer; however, the Apps DVD is
preferred if it is known to be good (not a bootable DVD). If the DARC OS
or Application software is corrupt and requires a reload, then a LFC must
be performed.
d. Perform one of the following commands as required:

 For all full LFCs:
[root@hostname scripts] ./load_darc_subsystem
 For DARC Node Reloads, Replacements, or when load failures occur:
[root@hostname scripts] ./load_darc_subsystem -restart
e. An Attention window appears. (See Illustration 23.)

2. Follow the instructions in the Attention window.
3. Then select [OK].
SOL Service (Illustration 24) and DARC BIOS (Illustration 25) error and attention
NOTE:
boxes may appear.
4. The Unix Shell will display output during the 30 minute DARC load. Example output is as
follows:
[root@hostname
[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]#
5. Additionally, an sh window displays the OS and Apps load messages.
The DARC Load should complete in approximately 30 to 35 minutes. It will stop

prematurely ONLY if an error is encountered. An Error Dialog Box should appear
with a brief description of the error. Select [OK] after performing the instructions
displayed on the Monitor.
If failures occur during ./load_darc_subsystem, perform the

NOTE:
./load_darc_subsystem -restart command. If failures occur during
./load_darc_subsystem -restart, perform the ./start_darcOS
command with the OS DVD inserted in the Host Computer. Then, perform the
./start_darc_load command to load the Application software onto the DARC.
If the two previous commands fail and the issue is thought to be software, perform
a full LFC.
A %done status is displayed during the DARC OS load. This is a timed countdown
NOTE:
sequence and does not provide status of the actual load process.
7. When the DARC load has completed, the sh window will close. The Unix Shell provides the
status of the load process.
8.5 Confirm DARC Software Has Loaded / Security Shell
Verify the OS and Application Software has loaded on the DARC.
1. After the DARC is rebooted, open a Unix Shell and type the following:
a. {ctuser@hostname} rsh darc
b. {ctuser@darc} exit
2. If the prompt {ctuser@darc} does not appear, the DARC Node may require a reload or a
hardware failure may be present. Verify the remote shell is successful. If rsh fails, try the
ping darc command and check the Host ifconfig to verify the DARC address and
Running message.
3. Verify the DARC to Host security shell is successful. If the prompt {ctuser@darc} does
not appear, then the LFC process was not followed or a sshd config file has been
corrupted.
a. {ctuser@hostname} ssh darc
b. {ctuser@darc} exit
4. If both the ssh and rsh are successful, continue with next section.
If the rsh is successful, but the ssh command still fails, Application software will not start
properly and the system will eventually halt. Perform the following to correct for port 22
unknown Host issues:
a. Open a Unix Shell and become root:
Password:<password>
b. [root@hostname] config_sshd
c. A message will appear:
[config_sshd] Setting up sshd on oc and darc for root and

ctuser accounts.
Starting sshd: [OK]
Starting sshd: [OK]
8.6 Restore Settings - DARC BIOS Boot Order (Westville ONLY)
This section describes the steps necessary to restore the BIOS boot order on the Westville DARC
Node to its original settings for normal operation. This is a required section for all Westville
DARC Nodes.
(For Jarrell DARC Node) Continue with Section 8.7.
(For Westville DARC Node) The Westville DARC BIOS boot order must be returned to the Restore
Settings (operational mode) to avoid a known Intel PXE boot problem, which can occur randomly
and prevent the DARC Node from booting.
1. Open a Unix Shell (if needed) and type the following:

a. {ctuser@hostname}su -
c. [root@hostname]service cliservice start
d. [root@hostname]telnet localhost 623
e. Server:darc
f. Username:[Enter]
g. Password:[Enter]
Login successful
h. dpccli>reset
ok
dpccli>console
GEHC/CTT Linux 6.2.9
Kernel 2.6.15-2.5 smp...
See you on the darc side of the moon

darc login:
A slight delay here is normal. Watch the screen for the [F2] prompt. If the
NOTE: prompt is missed for entering the BIOS, close the Telnet session and
retry.
If the "reset” and “console" commands fail and the "Active SOL failed"
message is displayed, connect to the DARC per above, but only type the
NOTE: 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].
<F2> must be selected in a timely manner or the process to access F2 will need to
NOTE: be repeated. There will be a short delay before the DARC BIOS setup screen is
displayed.
3. (For Westville DARC Nodes) Verify the final Boot Device Priority is set as shown below.
For detailed Westville BIOS screen setup instructions, perform Change DARC BIOS Boot
Order - Restore Settings .
ATAPI CD-ROM
Hard Drive
IBA 1.1.08 Slot 0339
IBA 1.1.08 Slot 0338
Removable Devices
NOTE: The removable devices might not be present. This is OK.
4. After saving the DARC BIOS, the BIOS SETUP UTILITY window should disappear (within
approximately one minute) and the DARC will begin to reboot. If this window does not
disappear within a minute or so, close the window and attempt to load the DARC Node. The
DARC Node may require a reset.
5. If necessary, close the Terminal Window.
8.7 Initial Setdate
The setdate command provides different output depending on the DARC software state. If
DARC software is present:setdate completed with NO ERRORS. If the DARC is
NOTE:
not ready or no software exists on the DARC: The darc is not responding. darc
will sync time with oc during next darc reboot
1. Wait 2-4 minutes for the DARC Node to complete the reboot process.
2. If necessary, open a Unix Shell and become root:
Password:<password>
NOTE:
3. Using the time from your laptop, type the following to initially setdate:
[root@hostname]# setdate to be prompted through the individual entries. Where:
Note: Type “q” to quit anytime. Enter to proceed:<Enter>
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
Enter the current Year (1980-2030)[2006]:
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...
connect to address 10.0.1.2: Connection refused
trying normal rsh (/usr/bin/rsh)
trying normal rsh (/usr/bin/rsh)
Current OC date : Fri Apr 14 16:14:05 CDT 2006
Current DARC date : Fri Apr 14 16:14:04 CDT 2006
setdate completed with NO ERRORS.
[root@hostname]#
NOTE: The Host/OC time may drift. 24 hours after the initial setdate is performed, the setdate
process will be repeated and these dates will sync up for drift. If messages inform the user
that the DARC is not properly communicating at this time, just ignore them until after the
software load on the DARC.
During the reboot of the console, a message may appear to the effect that the system was
NOTE: not able to determine what the tube type was and to run the TIC tool. This message should
be ignored at this point.
9 Reboot and CT Applications Start Up

A reboot will be required (due to xw8000) to ensure that all loaded files are linked properly. If a
reboot is not performed on certain system configurations, the system will halt after the startup
command is invoked. At this point, the console requires a re-power and subsequent startup
command.
2. Password:<password>
NOTE:
3. [root@hostname] reboot
4. After the system reboots, a pink pop-up Attention Message appears: CT Software
Auto-Start Disabled.
5. Click [OK].
6. Open a Unix Shell to startup the system:
{ctuser@hostname} st
7. A pink pop-up Attention Message appears: Waiting for System Startup….
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
NOTE: 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.
8. Visually verify that each IG Node powers up under DARC control and LAN activity is
present at the front of each IG Node.
9. Watch for IG Node or Recon error messages.
IG NODE NOT RESPONDING: The IG Node(s) may need to be power cycled.

Possibly the DARC Node was unable to actually initialize the IG Node address, or
NOTE: the IG Node did not respond due to a bad Ethernet cable or swapped port
connection. When viewing the DARC Node via a monitor cable, scrolling martian
errors may be the result of an IG Node that did not initialize properly.
10. Select [OK] for FastCal and other message boxes that appear throughout the reboot
process.
After each reboot during the software load process, an Attention Box with the
message “Unrecognized X-Ray Tube'” will be displayed until the tube identity has
NOTE:
been selected (later in this procedure) and “Flash Download” has also been
performed.
11. Review the Error Log and verify that “Selftest completed successfully.”
10 Optional - dvd_search Command

Perform this section whenever a SCSI Tower is replaced or to avoid issues detecting the DVD drive
on the SCSI Tower.
2. Password: <password>
NOTE:
3. [root@hostname] dvd_search
4. The following is an EXAMPLE of what may be displayed:
[dvd_search] SCSI DVD-RAM Drive is found
[dvd_search] DVD-RAM SW-9574S will be used.
Alias device dvd: src2b0t4u0 (sr0) -> (sgc2b0t4u0, sg4)
Alias device mod: sdc2b0t3u0 (sdd) -> (sgc2b0t3u0, sg3)
Unable to match device for line 3 (alias mod1)
[root@hostname ~]#
5. Ignore any “Unable to match device” messages.

6. Close the Unix Shell.
11 Restore System State from DVD (GOC1/GOC2/GOC3/GOC4)

GE Healthcare personnel and customers with Advance Service Limited License
agreements must have the Service Software loaded before performing Restore System
NOTE:
State. If this condition is not met, Restore State will need to be performed again after the
Service Software is loaded.
For GOC1 (IRIX) upgrades to Linux, see Table 6.

For all other consoles, perform the procedure described in Table 7.
12 Install Software Options
NOTICE
For Perfusion and Denta Scan:
These options are not part of VOX Tool, they are individual options.
If you loaded software in a language other than English, please reconfig as root
with Applications software down. Change the language to English and select
Accept. Restart Applications software. Load Perfusion and Denta Scan as
applicable. Failure to load these options in English will cause the options to be
unusable.
NOTE: Customers with the DMPR option may need to build single step protocols.
1. Insert the Options DVD-RAM in the SCSI Tower DVD RAM drive.
If you do not have the Options DVD-RAM, then you can use the eLicense feature.
NOTE: Follow this link to the eLicense Page:
http://egems.gehealthcare.com/elicense/index.jsp
2. With Applications up, select the [Service] icon.

3. Select [Configuration].
4. Select [Install Options]. The Example Software Options screen appears. (See
Illustration 26.)
5. Select [Install]. The Select Mechanism box appears. (See Illustration 27.)
6. Select [Permanent].
7. Insert the Options DVD into the SCSI Tower. The Select Device box appears. (See
Illustration 28.)
8. Select [MEDIA].
9. Select [ok] for DVD insertion.
10. Software options available for installation are displayed on the options screen.
11. Install applicable Options in the order specified per Software Options Installation Order in
Table 8. The order of installation for some Options is critical.
12. Select [Quit] to exit the window when the process is complete.
13. Select [Quit] again to exit Install Options window.
14. A window pops-up displaying: “Application should be shutdown and restarted
for installed/removed options to take effect.”
15. Select [OK].
Options loaded via DVD or CD will NOT be saved to System State.

NOTE:
Options loaded via e-License WILL be saved to System State.
16. Press the button on the DVD-RAM drive on SCSI Tower to eject the option DVD.
17. Close the Service Desktop window in the upper left corner of the screen.
18. If the language was modified via a reconfig for options, re-perform the reconfig process at
this time to re-select the preferred language.
13 Service Software
Service software (Class C and M) applies only to GE Healthcare personnel and customers with an
Advance Service Limited License agreement. Load service software per the instructions on the
media.
1. Open a Unix Shell and type:
The Class C and Class M software version (example xxMWxx.x) must match the
NOTE:
software set loaded. See Section 2, Software Deliverables.
2. {ctuser@hostname} su -
3. Password:<Password>
4. Insert Class C service software into the Host Computer DVD drive tray.
5. Type:[root@hostname]install.classC
6. To close the “sh” window once Class C install is complete, place the cursor in the original
terminal window and press <Ctrl>+<C> or double-click on upper left corner of “sh” window.
7. Remove Class C service software from the Host Computer DVD drive and close tray.
8. (For GE Healthcare personnel only) Install Class M service software (Restore System
State before Class M is required), then perform the Restore System State procedure
(Table 7).
14 Initial load of this software - Retro Recon / Customize Large

Font
This section should only be performed when INITIALLY LOADING this software (not a
reload), because the save was not being performed during the Save System State process
for previous versions of software releases. If the user modified the Screen and Film
Annotation Groups, these will need to be restored manually for the choices listed
(Patient_Name, Patient_ID, or Accession_Number).
NOTE:
The Customize Large Font information will be saved to System State later in this
procedure.
The Reconstruction (not Scan) portion of the system is tested at this point via the Retro
Recon Test (gold rat image is generated). Additionally, this image is required to access
User Prefs.
1. Select [Recon Mgmt] then [Restart Queue] on Scan monitor then [Quit]. The Display
Monitor's FSA Box should show Idle (not Paused or Shutdown).
2. At the Display monitor, select the [Exam Rx] icon.
3. Verify that the toggle switch is selecting [Auto View Layouts].
4. Select [Auto View Layouts]
5. Select the “four-image” viewer box.
6. Select [Retro Recon] on Scan monitor.
7. Locate and select the gold rat Patient ID.
8. Select [Select Series].
9. Select [Confirm].
10. Verify that the image(s) reconstruct and are displayed without artifacts.
11. Verify that the Display monitor’s FSA Box reports successful completion of images.
12. Select the [Image Works] icon. The Image Works Viewer appears. (See Illustration 29.)
13. Select [Viewer].
14. Click on gold rat image.
15. Select [User Prefs] at the bottom of the Display monitor. The User Preferences screen
appears. (See Illustration 30.)
16. Locate (at the top of the screen on the left) Screen box.
17. Select [Customize Large Font]. The Large Font Annotation Groups screen appears. (See
Illustration 31.)
18. Click on the Annotation Group(s) desired.
19. Select [Ok] to save changes. (Perform steps 17- 19 for Film.)
20. Select [Save as default] to apply changes.
15 FLASH Download
The Flash Download takes 5-30 minutes.
Verify the reset switch at the gantry is not flashing and reset the 120 VAC, if necessary.
If there are any issues with the FLASH Download Tool update, open a Unix Shell and try to ping the
following:
(For LightSpeed 1.X/2.X/3.X/4.X)
 ping obcr (Ctrl-C to stop ping)

 ping etc (Ctrl-C to stop ping)
 ping stc (Ctrl-C to stop ping)
(For LightSpeed 5.X)
 ping orp (Ctrl-C to stop ping)

 ping tgp (Ctrl-C to stop ping)
NOTE: Flash Download may take a second time before it is successful.

If an issue exists with Flash Download, retry, then perform SYSTEM RESETS,
SCAN, RUN and verify this passes, and view the log for errors. Cycle 120V gantry
NOTE:
power and repeat Flash Download. Remember to press the Drive Enable Reset
keypad on the front of the gantry after turning the 120V power back on.
1. Select the Service icon, [Utilities], [Install], [Flash Download Tool]. (See Illustration 32.)
2. Select [Update].
NOTE: Ignore any initial errors or TGP “unknown” messaging. This is not a problem.
3. If a pop-up appears requesting the Collimator Serial Number, enter the Collimator Serial
Number and select [Accept].
This pop up may not appear if the Collimator Serial Number was retrieved from the
NOTE:
System State.
4. If a pop-up appears to save the CCB file, select [Yes].

5. Once the Gantry Hardware Flash Downloads successfully, select [Dismiss].
After Flash Download the system will report the following message:
NOTE:
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.
16 GOC1 IRIX Upgrades Only - Edit Gantry Revolutions

Information
For GOC1 IRIX Upgrades Only - Edit Gantry Revolutions Information, see Table 9.
17 Feature Installation
This section describes feature installation.
17.1 HIPAA
Configure HIPAA now if applicable. (Refer to HIPAA Configuration.) When HIPAA configuration is
complete, return to this procedure.
17.2 Product Network Filters (PNF)
When a Save System State is performed, all settings made in the PNF Tool are saved to that
System State.
For general information on Product Network Filters, please see Product Network Filter Theory.
If you or your customer wishes to have Product Network Filters (PNF) configured, then proceed to
Configure Product Network Filters now. When PNF configuration is complete, return to this
procedure.
17.3 AW Direct Connect
If the site requires the configuration of AW Direct Connect, configure AW Direct Connect now.
When configuration is complete, return to this procedure.
18 Connect HSP Cable

Reconnect the Hospital Network (HSP) Ethernet cable at the Operator Console's rear bulkhead.
(See Illustration 2.)
19 Tube Identification Certification

To perform Tube Identification Certification, refer to the steps below.
NOTE: For a visual description of this procedure, refer to the flowchart in Illustration 33.
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.
If a non-GE supplied tube is used, GE cannot assure that the system performance will conform to
specifications.
1. The GE FE shall be called if not on-site for tube ID verification.

2. Visually verify the tube supplier (GE or other).
3. Visually verify if a “Tube ID” board is present (GE only).
4. The GE FE shall install the Class M service key.
5. Select the Service icon.
6. Select [Configuration], then [Tube Install Certification]. The Tube Install Certification
Confirmation screen appears. (See Illustration 34.)
7. Based on tube visual verification results from above, click on the proper tube type.
8. Select [Confirm], [Accept], and [Dismiss].
NOTE: The user will [Restart] the Console from the Service icon later in the LFC.
9. Depending on the process being performed, do one of the following:

o Full LFC: proceed to Flash Download after TIC
Or
o GE FE visiting after the LFC is completed: continue with the following steps
10. Select the Service icon. On the Attention screen, select [Shutdown], then [Restart], and
[OK].
11. The GE FE shall [OK] as required and verify during Apps startup that the pop-up messages
are in accordance with the selections made.
If the tube in your system has a “Tube ID” board, the software automatically selects the
tube identity and sets it to “GE Performix Tube.” There is no action needed. For all other
systems or if the software does not automatically select the tube identity, follow the
procedure shown below.
Verification that a tube is a GE Healthcare tube (called “GE Performix Tube” in the TIC tool)
can be done by checking the tube insert model number (2120785 or 2120785-2), which can
be found on the tube rating plate. (Exception: The “Performix Pro” is a GE OEM tube, but
does not have this tube insert model number.)
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
NOTE:
not available. If double-clicking occurs, close the window and try again. If
issues occur more than once, reboot the system and try again.
NOTE: TIC Notes:
Possible Pop Up messages at start up:
o If the tube selection is GE tube without time limit, no pop up messages

relating to tube identity will occur at Apps startup.
o If the tube selection is GE with time limit, a message with days remaining
for GE FE to verify tube will be shown at Apps startup until the GE FE
removes the time limit with service key. If not verified by the GE FE within
the time limit, the system will default to “All Others.”
o If the tube is set to “All Others,” an unrecognized x-ray tube installed
message will always be shown at Apps startup.
Please refer to Tube Install Certification Tool - Screens for examples of the screens
displayed by the Tube Install Certification Tool.
12. The GE FE shall perform the FLASH Download after TIC and Save System State sections.
20 FLASH Download after TIC

This is a firmware REQUIREMENT to load Tube Identification Certification parameters. A Save
System State is also required; this is performed later within this LFC.
1. Select the Service Icon, [Utilities], [Install], [FLASH Download Tool].

2. Select [Update].
NOTE: Ignore any initial errors or TGP “unknown” messaging. This is not a problem.
3. Once the Gantry Hardware Flash Downloads successfully, select [Dismiss], then close the
window and the Common Service Desktop.
21 Service Pack Load

The initial release of a Service Pack CD may not contain any patches. Service Pack CDs will
include any new patches and all older patches that are still applicable. If a site is required to
uninstall a Service Pack, the previous Service Pack may need to be installed. Therefore, retain the
earlier version of the Service Pack.
Refer to instructions (sometimes inside the jewel case, as a Class A instruction, or FMI) and load
the most current Service Pack at this time.
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:
4. Password:<password>
If the Password has not been modified by the site and is not known, contact Local
NOTE:
GE Service.
5. Perform the following steps to install the Service Pack CD:

a. [root@hostname]#start_udev
b. A message will return: OK
c. Wait 15 seconds after the OK is returned, then type the following install script:
[root@hostname]#patch_install -c
If the Service Pack fails to install, perform

NOTE: [root@hostname]#start_udev. Wait 15 seconds after OK, then retry
the Service Pack.
Any patches on the Service Pack CD will be listed. Before installation of each
patch, the window will wait for user's confirmation as follows:
I will install update Patch Name, is this ok ? [y/n]
d. Input y to install this patch or n to cancel installation of this patch.

e. After installing the Service Pack CD, type patch_status in the Shell window to
determine which patches were installed (if any). The following is an alternate
command to verify the Service Pack load:
[root@hostname]#showprods | grep -i ServicePack
f. Type:[root@hostname]#reboot
A reboot is always required after a patch is installed. Additional processes

NOTE: may be required for installing certain Service Pack media. Refer to the
instructions sent with the Service Pack.
22 Apps Startup
1. Type: {ctuser@hostname}st
2. If a Restart was not performed during the Tube Identification Certification process, the
related tube pop-up messages shall be verified now beginning at Step 10 of Section 19,
“Tube Identification Certification.”
3. When Apps starts up, the Admin screen will appear if “HIPAA Present” was set to ON
during the Application LOAD process. The Admin screen requires the following input:
o Operation: Login
o Username: root
o Password:<password>
NOTE:
o Select [OK].
process.
6. Wait for the system to fully reboot with Applications software fully up before proceeding.
23 Additional Processes Required
The following subsections contain information that may or may not be fixed when Service Pack 2 (or
greater) is loaded. Verify each subsection for your specific host type, and perform adjustments as
required.
23.1 XW8000 and XW8200 Host Computer
23.1.1 Autovoice Settings (Fixed with Service Pack 2)
The Autovoice settings process must be performed for every LFC until Service Pack 2 is loaded. It
is possible that after performing a LFC without Service Pack 2 (or greater), the system may exhibit
two different problems related to Autovoice settings: Low Volume and / or Feedback (squealing or
noise) through the speakers.
23.1.2 Volume Adjustment (Fixed with Service Pack 2)
If Autovoice volume is too low:
1. Select the “Autovoice Volume” (“audioSetting”) tool from the Tool Chest menu to increase
the volume as needed.
2. Click [Save], then [OK]. Changing Autovoice settings may result in feedback issues. If this
occurs, proceed to Section 23.1.3.
23.1.3 Feedback Remediation (Fixed with Service Pack 2)
If Autovoice feedback issues exist, perform the following steps:
1. Open a Unix Shell.

2. Type alsamixer, then <Enter>. The Autovoice Settings screen appears (Illustration 35.
Settings shown may not depict the final settings for your console. Settings vary
NOTE:
from console to console.
3. Press the <right-arrow> key to move the cursor selection to the PCM slider.
4. Press the <up-arrow> key to increase the PCM setting to 100%.
5. If feedback is heard, press the <right-arrow> key to move cursor selection to the Line slider.
6. Press the <down-arrow> key to decrease Line setting until feedback is no longer heard.
NOTE: Do not mute the Line device, as it is needed for Autovoice Record.
7. When you have completed your adjustments, press <Esc> to exit AlsaMixer.
8. If the Line setting was changed, then STOP. You have completed Autovoice setup. If the
Line setting was not changed, select the Autovoice Volume tool from Tool Chest menu and
click [Save], then [OK] to save the PCM settings to file.
If Line setting was changed and then the Autovoice Volume settings saved, the
NOTE: Line value set via AlsaMixer is reset to “61.” (It was overwritten by the “Save.”)
Repeat steps 5 through 7 to adjust Line settings.
23.2 XW8400 Host Computer (Needed when XW8400 is introduced)

23.2.1 Autovoice Settings
After Service Pack 2 is installed, 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, it is
recommended to perform volume adjustment.
23.2.2 Volume Adjustment
1. Select the “Autovoice Volume” (“audioSetting”) tool from the Tool Chest menu to increase
the volume as needed.
2. Next click [Save], then [OK].
23.3 Gantry Tilt Adjustment - Initial Load Only
The 07MW software/firmware was changed on all 7.X and 5.X gantries to catch systems with tilt
speeds grossly out of spec. Since the gantry Home Zero point is reliant upon the Tilt Speed
adjustment, if the Gantry Tilt Speed is too slow or too fast the gantry Zero will be incorrect.
The 5.X and 7.X gantry tilt design has two Zero Home positions, one from the Forward direction and
one from the Backwards tilt direction. The two Home positions are slightly different, but at both
Home locations the gantry display reads 0.0 degrees. The two Home Positions are mainly driven by
the coasting-to-a-stop motion of the gantry. When the Forward and Backward Tilt speeds are set as
close to 1 degree per second as possible, it ensures the two Zero Home positions are the same.
Resolution: The Tilt speed needs to be adjusted to 1 degree / second
The following procedure can be used for 5.X systems. (For additional methods see the Hydraulic
Tilt Motor Speed Adjustment (Illustration 36) in the Systems Service Manual.)
1. Set the Service Switch to Service mode (Illustration 37).

2. Using the gantry controls, tilt the gantry forward and back and the gantry speed will be
displayed on the gantry control (Illustration 38).
24 System Sanity - Scanning & Network Operation

1. Select [Daily Prep] on the Scan monitor.
2. Perform [Tube Warmup].
3. Select [Quit] when tube warm-up is completed.
4. Successfully perform a Scout scan.
5. Successfully perform a Helical scan.
6. Successfully perform an Axial scan.
25 Save System State

To Save System State, follow the procedure described in Table 2.
26 Finalization
All PNF settings were restored from System State. Disabling telnet in PNF is
NOTE:
recommended. Remote telnet is disabled for security reasons; PNF acts as your firewall.
1. Set telnet via Product Network Filters (PNF) per customer request.
2. If the site has DICOM print configured, perform DICOM print to confirm network operation
with the PNF firewall set to ON.
3. If you have archive server configured, perform image archive & retrieve to confirm network
operation with the PNF firewall set to ON.
4. Remove the System State from the SCSI Tower DVD drive.
5. Verify that all software media has been removed from the DVD tray in the Host Computer
and SCSI Tower.
6. Verify that all floppies have been removed from the floppy drive in the Host Computer.
7. Verify all software media has been removed from the DVD tray in the DARC Node.
8. Verify that the DARC/IG Troubleshooting Cable is not connected to Scan or Display
Monitors.
The troubleshooting cable (used for DARC and IG Node) must not be connected
at either end of this cable except when troubleshooting. When connected to a
NOTE: monitor, the DARC/IG Node may take over the monitor, causing customer
confusion. EMC requirements are violated if the troubleshooting cable is
connected to either the DARC or IG Node.
9. Verify that the DARC/IG Troubleshooting Video Cable is not connected to the rear of the
DARC/IG Node.
10. Replace the front and rear Operator Console covers.
11. Remove any phantoms used during System Sanity Scanning.
12. The LFC process is now complete.
27 Drift Setdate
A second setdate is required to calculate a drift adjustment value. Drift varies for each Host
Computer. The usage of the system, internal Host Computer temperature, and the characteristics of
the clock located on the Host motherboard can all affect the time drift. Currently, Engineering
recommends waiting a minimum of 24 hours after the initial setdate. In the event that this 24-hour
interval is not possible, perform setdate now. Understand that setdate may need to be performed
more often at some sites.
The time entered must be based on the same clock source used during the initial setdate.
Open a Unix Shell and become root:
Password:<password>
If the Password has not been modified by the site and is not known, the correct course of
NOTE:
action is to contact Local GE Service.
Utilize the time from your laptop to perform setdate for drift:
[root@hostname]# setdate
Note: Type “q” to quit anytime. Enter to proceed:<Enter>
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>
Enter the current Year (1980-2030)[2007]:
Enter the current Month (1-12)[04]:
Enter the current Day (1-30)[14]:
Enter the current Hour (Military Time) (0-23)[18]:
Enter the current Minute (0-59)[13]:
Enter the current Second (0-59)[00]:
Updating the time on the OC and DARC, Please Wait...
Current OC date : Fri Apr 14 15:18:00 CDT 2006
Could not retrieve the DARC TimeZone.
Please make sure the TimeZones for the OC and DARC are the same.
Setdate completed with NO ERRORS.
[root@hostname]#
28 Restart the System before Customer Turnover
NOTICE
NEVER Use [CTRL - ALT - DELETE] to reboot. This technique will NOT reboot all
console subsystems, and as such is an unacceptable practice.
1. Select the Service icon. On the Attention screen, select [Shutdown], then [Restart], and
[OK].
2. If a Restart was not performed during the Tube Identification Certification process, the
related tube pop-up messages shall be verified now beginning at Step 10 of “Tube
Identification Certification.”
3. When Apps starts up, the Admin screen will appear if “HIPAA Present” was set to ON
during the Application LOAD process. The Admin screen requires the following input:
o Operation: Login
o Username: root
o Password:<password>
NOTE:
o Select [OK].
process.
6. Wait for the system to fully reboot with Applications software fully up before proceeding.
29 Final Save System State

The System State may need to be saved again. Refer to Service Pack instructions. The System
State must be saved after a new LFC and after the Service pack is installed. A Save System State
is also required if additional processes were required because settings were not restored properly
from the previous System State, or if the Service Pack corrections affected saved items. If in doubt,
resave the System State at this time.
30 Smart Step Option (Fixed with Service Pack 2)

When using Smart Step Option, the cradle release button on the Handheld controller does not work
without Service Pack 2 (or greater) loaded. Use the Cradle Release button on the gantry.
31 Appendix: Tables and Graphics

Table 1: LFC Procedural Flow
□ Gather software / hardware information (can be saved to media):

{ctuser@hostname} installOptions
[root@hostname] ls -l ~ctuser/ves/.hesMode
{ctuser@hostname} cd /usr/g/ctuser/resources/pps
{ctuser@hostname} head -12 ppsserver.cfg
□ Save System State: (GOC1 and GOC2 saves a second backup marked original)
□ Host BIOS verification: [root@hostname] dmidecode | grep Ver
□ Load OS and Apps software for the Host: GEHC2 or iGEHC2 System State inserted, if applicable
(No or Yes and ok as needed) Run Command Accept Yes
□ DARC Replacements ONLY, confirm SW/HW: {ctuser@hostname} swhwinfo
{ctuser@hostname} swhwinfo –os
{ctuser@hostname} ipmitool -H darc -P '' fru | grep -i "Board Product"
□ Change DARC BIOS Boot order for Westville ONLY (for Jarrell - set to final BIOS only if issues)
IBA 1.1.08 Slot 0338
ATAPI CD-ROM
Hard Drive
IBA 1.1.08 Slot 0339
Removable Devices (may not be present)
□ Load OS/Apps on DARC (SOL or Boot BIOS / troubleshoot pop-ups may appear)
[root@hostname] cd /usr/g/scripts
LFC: [root@hostname scripts] ./load_darc_subsystem
Reloads: [root@hostname scripts] ./load_darc_subsystem -restart
T/S: [root@hostname scripts] ./start_darcOS
[root@hostname scripts] ./start_darc_load
□ Confirm DARC software has loaded: {ctuser@hostname} ssh darc
{ctuser@darc} exit
□ Westville ONLY, restore DARC BIOS Boot order for operation:
ATAPI CD-ROM
Hard Drive (IDE Hard Drive)
IBA 1.1.08 Slot 0339
IBA 1.1.08 Slot 0338 (Host to DARC port)
Removable Devices (may not be present)
□ Perform initial setdate: [root@hostname]# setdate
□ Reboot and Start Application Software: [root@hostname] reboot
CT Software Auto-Start Disabled (Click [OK]) {ctuser@hostname} st
□ Optional - dvd_search
□ Restore System State (GOC1, GOC2, GOC3, GOC4)
□ Install Options in specific order per Table 8
□ Service Software, if applicable: [root@hostname] install.classC
[root@hostname] install.classM
□ Initial load of this software - Retro Recon / Customize Large Font (Screen and Film)
□ Flash Download
□ Feature Installation (HIPPA, PNF, AW Direct Connect)
□ Connect HSP Ethernet Cable
□ Tube Install Certification
□ Flash Download after TIC
□ Load Service Pack with Apps down, then reboot: [root@hostname]# start_udev
OK, wait 15 seconds, then [root@hostname]# patch_install -c
[root@hostname]# reboot
□ Apps Startup: {ctuser@hostname} st
□ Additional processes required: {ctuser@hostname} audioSetting
{ctuser@hostname} alsamixer Tilt speed needs to be adjusted to 1 degree / second
□ System sanity scanning
□ Save System State
□ Finalization
□ Perform drift setdate (24 hours after initial setdate, if
possible: [root@hostname]# setdate
□ Restart for customer turnover
Shutdown, Restart, OK
□ Inform customer of Smart Step Option workaround (Handheld controller does not work. Use the
Cradle Release button on the gantry.
Table 2: Save System State

Save System State
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.
1. Insert the System State DVD-RAM into the SCSI Tower DVD drive.
2. Wait until the DVD drive is ready (i.e., front panel DVD drive LED is no longer lit).
3. Select: [Service] icon to access the Common Service Desktop (CSD).
4. Select: [Utilities].
5. Select: [System State]. The System State Save/Restore screen appears. See
Illustration 39.)
6. Select [All].
7. Select [Save]. The Save System State box appears. (See Illustration 40.)
8. Select [Yes].
9. Verify that the "Save" of System State was successful. If not, save the System State again.
A message at the end of the Save should state: Save/Restore System State:
Completed Successfully. (See Illustration 41.)
10. When completed, select [Cancel].
11. When completed, select [Dismiss].
12. Close the Service Desktop window at the upper left corner of the screen.
Table 3: GOC1 (IRIX) Systems Upgrading to Linux - Save System State Twice
GOC1 IRIX Systems Upgrading to Linux - Save System State Twice
GOC1 (IRIX) Operator Consoles consist of: Octane with O2 or Octane without O2.
Perform the following steps on the GOC1 IRIX Operator Console before powering down and
installing the Linux based GRE/Xtream Operator Console.
Two “Save System State” MOD procedures must be performed:
 You must save the System State onto your Original System State MOD, label it
appropriately, and keep it in a secure place. The “Original IRIX Conversion
NOTE: Release System State” MOD will be used only if the customer wants to revert
back to the original IRIX-based software.
 You must then save a second System State onto a new MOD. This MOD will be
used for the software LFC.
1. Save System State (twice) to an MOD on the GOC1 IRIX Operator Console before
installing the new Linux based GRE/Xtream Operator Console.
a. Insert the MOD into the SCSI Tower MOD drive.
b. Select: [Service Desktop].
c. If reloading software, select: [Utilities]. If upgrading from earlier version software,
select: [PM].
d. Select: [System State].
e. Select [All] to save all data.
f. Select [Save].
g. 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.
h. When completed select [Dismiss].
i. For the original MOD, label the MOD as “Original IRIX Conversion Release System
State” and set this aside.
j. Repeat Steps a-j, for the second “Save System State”, using a new MOD, and label
with the release version that is found on the Application software label to be loaded.
2. Modify System State MOD as follows:
a. Insert System State MOD into the drive.
b. Open a Unix Shell and type the following:
i. {ctuser@hostname} su –
ii. Password: <password>
iii. [root@hostname] mountMOD
iv. [root@hostname] cd /MOD/service_mod_data/system_state
v. [root@hostname] chmod 666 *bb .epdlog(this changes
permissions on tube usage and edit patient data files)
vi. [root@hostname] rm -f *.stats(this removes runtime stats on
non-HPOWER systems)
vii. [root@hostname] rm -f iipBackupGen2.tar.Z(this removes
IIP “tar ball” files not used by the new IIP)
viii. [root@hostname] rm -f Voxtool.prefs(this removes Voxtool
preferences ⇒ new Voxtool application uses new set of preferences)
ix. [root@hostname] rm -f smartscore.tar.gz(this removes
SmartScore files ⇒ SmartScore (SmartScore may not be supported by this
software)
x. [root@hostname] rm -f vxtlBackup.tar(this removes VoxTool
files ⇒ new Voxtool application uses a new set of files)
xi. Remove VoxtoolPrefs/* and CT_PerfusionPrefs/* files
xii. [root@hostname] rm -f movierx* (this removes Direct 3D
preferences that the customer cannot edit)
xiii. [root@hostname] rm -f *.flm
xiv. [root@hostname] rm -f *.pro
xv. [root@hostname] rm -f *.vrp
xvi. [root@hostname] rm -f *.adv
xvii. [root@hostname] rm -f *.adv.research
xviii. [root@hostname] rm -f *.disp
xix. [root@hostname] rm -f *.disp.research
xx. [root@hostname] cd /
xxi. [root@hostname] unmountMOD
c. Close the Unix Shell.
3. Proceed to next applicable section.
Table 4: GOC2 (Linux-Pegasus) Systems Upgrading to GOC3/4 - Save System State Twice
GOC2 Systems Upgrading to GOC3/4 - Save System State Twice
GOC2 (Linux-Pegasus) Operator Consoles consist of a Pegasus IG Board and a pre-xw8x00 Host
Computer.
Perform the following steps on the GOC2 Operator Console before powering down and installing
the Linux based GRE/Xtream Operator Console.
NOTICE
Two “Save System State” MOD procedures must be performed:
 You must save the System State onto your Original Linux GOC2 System
State DVD, label it “Original Linux GOC2 System State Backup,” and keep
it in a secure place. The original “Save System State” will be used only if
the customer wants to revert back to the original software.
 You must then save the System State onto a new DVD. This DVD will be
used for the software LFC.
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.
Successful completion is indicated by the message, Save/restore system

NOTE:
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 as “Original Linux GOC2 System State Backup.”
10. Repeat Steps 1-8 for the second “Save System State,” using a new DVD, and label with the
release version that is found on the Application software label to be loaded.
11. Close the Service Desktop window in the upper left corner of the screen.
Table 5: GOC1/GOC2 Console Upgrade Only - Install GRE/Xtream Console
GOC1/GOC2 Console Upgrade Only - Install GRE/Xtream Console
This section only applies to GOC1 (IRIX) and GOC2 (Linux-Pegasus) Operator Console upgrades.
1. Power-down the GOC1 or GOC2.
2. Install the new GOC3 or GOC4 Linux based GRE/Xtream Operator Console.
You will be using your existing SCIM / Keyboard, monitors and mouse, unless
NOTE: you received a new SCIM or mouse. You will receive a new trackball that must
be used on the new Operator Console. Your old trackball will no longer work.
3. Install the new SCSI Tower (DVD-ROM drive and MOD drive).
4. Install the new trackball (it is connected at the rear of the Operator Console near the
connections for the keyboard and mouse). The extension cable for the trackball is already
connected to the USB port at the rear of the Host Computer.
5. When you power up the GRE/Xtream Operator Console:
o Verify that the SCSI cable is connected to the SCSI Tower from the Host
Computer.
o Verify that the SCSI Tower power is applied and power LED on front is lit.
o Verify that the SCSI Tower terminator LED is lit (located at the rear for older SCSI
Towers Only).
See the Installation Instructions that came with the new Operator
NOTE:
Console.
Table 6: IRIX GOC1 Upgrades- Restore System State from MOD
GOC1 (IRIX) Upgrades- Restore System State from MOD
This procedure is ONLY for GOC1 (IRIX) upgrade sites with System State Information
NOTE: on a MOD (not a DVD). All other sites should restore System State as instructed in
Section 11.
1. When applications are up, open a Unix Shell from the Service icon -> Utilities tab -> Utilities
folder. Perform the following:
a. Insert the GOC1 IRIX System State MOD into the SCSI Tower MOD drive. The
DVD drive should be empty.
b. {ctuser@hostname} cd /usr/g/bin
c. {ctuser@hostname} sysstategui -MOD -IRX2LNX
d. When the system state GUI comes up, select and restore each item individually, by
selecting the item and then selecting [Restore].
NOTE: Continue until all items are restored.
e. The IRIX to Linux conversion should take around 40 minutes. The command lines
will scroll very quickly during the conversion in the window. When the scrolling
stops, the System State has completed the conversion. When it has completed,
close the window.
3. Remove the MOD from the drive.
Table 7: Restore System State
Restore System State
1. Open a Unix Shell and verify that the SCSI Tower MOD and DVD are
present:{ctuser@hostname} scsistat
3. Insert the previously saved System State DVD-RAM into the SCSI Tower DVD drive.
4. Wait until the DVD drive is ready (i.e., front panel DVD drive LED is no longer lit)
5. Select the [Service] icon to access the CSD (Common Service Desktop).
6. Select: [Utilities].
7. Select: [System State]. The System State Save/Restore screen appears. (See
Illustration 39.
8. Select [All].
9. Select [Restore]. The Restore System State box appears. (See Illustration 42.)
10. Select [Yes].
IP addresses (e.g., DARC Subnet) that were changed during the LFC process
NOTE:
will not be altered when restoring the System State.
11. Verify that the "Restore" of System State was successful. If not, restore the System State
again. A message at the end of the Restore should state:Save/Restore System State
Completed Successfully. (See Illustration 41.)
If Scan Hardware Reset question appears - answer [No]. This reset is performed
NOTE:
during FLASH Download Update.
12. When completed, select [Cancel].

13. Select [No] when the Scan Hardware Reset pop-up appears. This reset is performed during
FLASH Download Update.
14. When completed, select [Dismiss].
Table 8: Software Options Installation Order
LS 1.X, 2.X, 3.X, 4.X, LS 5.X, RT 4-slice, BrightSpeed 4/8/16-slice
1. SmartPrep
2. 3000 Image Series (also called Large Image Series)
3. Helical Tilt
4. Thin Twin Helical (if 4 or 8 slice)
5. Power 440
6. AutomA
7. 6.3 MHU
8. 90KVA
9. Smart Speed (not valid for 1.X)
10. 0.7-Second-Scan (if HiSpeed QX/I system)
11. 8-slice (if 8-slice system)
12. Patient 16-slice (if 16-slice system)
13. Wide View (if 4 or 8 slice system)
14. Direct-3D
15. Direct-MPR (single-step protocols only) or Vari Viewer (site would have only one of these
options)
Direct-MPR requires 4 GB of Host Main memory as shown in hinv; otherwise,

NOTE:
with 2 GB the maximum images is set to 1200.
16. Connect Pro

17. ExamSplit (before installing engineer needs to determine if HES or VES) (requires Connect
Pro)
Hard ExamSplit or Virtual ExamSplit. VES requires PPS (Performed Procedure

NOTE:
Step), which is installed as a part of the Connect Pro install.
18. DentaScan
19. Perfusion 2, Perfusion 3, Perfusion Neuro (site would have only one of these options)
20. SmartStep (not valid for 1.X)
21. Realtime CT Fluoro (only if HP60 based or BrightSpeed)
22. SmartScore Pro
23. Card IQ (Snapshot) (requires SmartScore Pro)
24. EKG Viewer (requires SmartScore Pro)
25. Noise Reduction Filter (c1, cd2, c3) (requires SmartScore Pro)
26. VolumeViewer
27. AdvVesselAnalysis (requires VolumeViewer)
28. CTC Base (requires VolumeViewer)
29. CTC Colonoscopy / CTC Colonoscopy Plus (requires VolumeViewer)
30. CTC Pro (requires VolumeViewer)
31. Card EP (requires VolumeViewer)
32. Card IQ2 (requires VolumeViewer)
33. Card IQ Plus (requires VolumeViewer)
34. Card IQ Pro (requires VolumeViewer)
35. Data Export
36. CopyComposer (also called CD/DVD, Interchange)
37. Advantage 4D
38. AutoBone
LS Pro16 5.X 80 and 100 kW
1. SmartPrep
2. 3000 Image Series (also called Large Image Series)
3. Helical Tilt
4. Thin Twin Helical
5. AutomA
6. HiPower
7. Smart Speed
8. Patient 16-slice (if 16-slice system)
9. 0_4Speed
10. Direct-3D
11. Direct-MPR or Vari Viewer (site would have only one of these options)
Direct-MPR requires 4 GB of Host Main memory as shown in hinv; otherwise,

NOTE:
with 2 GB the maximum images is set to 1200.
12. Connect Pro

13. ExamSplit (before installing engineer needs to determine if HES or VES) (requires Connect
Pro)
Hard ExamSplit or Virtual ExamSplit. VES requires PPS (Performed Procedure

NOTE:
Step), which is installed as a part of the Connect Pro install.
14. DentaScan
15. Perfusion 2, Perfusion 3, Perfusion Neuro (site would have only one of these options)
16. SmartStep or Real Time CT Fluoro
17. SmartScore Pro
18. Card IQ (Snapshot) (requires SmartScore Pro)
19. EKG Viewer (requires SmartScore Pro)
20. Noise Reduction Filter (c1, cd2, c3) (requires SmartScore Pro)
21. VolumeViewer
22. AdvVesselAnalysis (requires VolumeViewer)
23. CTC Base (requires VolumeViewer)
24. CTC Colonoscopy / CTC Plus (requires VolumeViewer)
25. CTC Pro (requires VolumeViewer)
26. Card EP (requires VolumeViewer)
27. Card IQ2 (requires VolumeViewer)
28. Card IQ Plus (requires VolumeViewer)
29. Card IQ Pro (requires VolumeViewer)
30. Data Export
31. CopyComposer (also called CD/DVD, Interchange)
32. Advantage 4D
Table 9: GOC1 (IRIX) Upgrades Only - Edit Gantry Revolutions Information
GOC1 (IRIX) Upgrades Only - Edit Gantry Revolutions Information
If upgrading from a GOC1 (IRIX) Operator Console to a GRE/Xtream Operator Console, then the
gantry revolutions information must be restored.
1. Open a Unix Shell and type the following:{ctuser@hostname} getStats

2. Select menu option (by typing the appropriate number) to Update Gantry Revolutions
Counter Stats.
3. Enter the gantry revolutions counter information captured at the beginning of this LFC.
Illustration 1: ICOM Power LED

Illustration 2: Rear Console Bulkhead
Illustration 3: Attention Screen
Illustration 4: Power Switch

Illustration 5: Display Monitor Prompt Window
Illustration 6: Warning Box
Illustration 7: CT Software Installation Window

Illustration 8: Install INFO Decision Box
Illustration 9: Install INFO Valid System State Box

Illustration 10: System Settings Screen
Illustration 11: Preferences Settings Screen

Illustration 12: Preferences Settings Screen (SP2)
Illustration 13: Main Hardware Screen
Illustration 14: Select Hardware Configuration.Screen
Illustration 15: Example Hardware Settings Screen
Illustration 16: Table Label/Rating Plate
Illustration 17: Network Settings Screen

Illustration 18: Station Name - Network Settings Screen
Illustration 19: Install INFO Acceptance Window
Illustration 20: Apps sh Window
Illustration 21: Reboot Prompt
Illustration 22: CT Software Auto- Start Disabled Box

Illustration 23: DARC Node Attention Window
Illustration 24: SOL Service Error Box
Illustration 25: DARC BIOS Attention Box

Illustration 26: Example Software Options Screen
Illustration 27: Select Mechanism Box

Illustration 28: Select Device Box
Illustration 29: Image Works Viewer
Illustration 30: User Preferences Screen

Illustration 31: Large Font Annotation Groups Screen
Illustration 32: Example Flash Download Screen
Illustration 33: TIC Flowchart

Illustration 34: Tube Install Certification Confirmation Screen
Illustration 35: Autovoice Settings Screen
Illustration 36: Hydraulic Tilt Motor Speed Adjustment

Illustration 37: Service Switch Set to Service Mode
Illustration 38: Gantry Speed Display
Illustration 39: System State Save/Restore Screen

Illustration 40: Save System State Box
Illustration 41: Successful Completion Message

Illustration 42: Restore System State Box

CT LFC Procedure 07mw11

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

CT LFC Procedure 07mw11

Transféré par

Droits d'auteur :

Formats disponibles

07MW11.

For a description of the procedural flow in this document, see Table 1.

Version - GEMS Linux 6.2.9 OS

 5220445 - LightSpeed Applications Software DVD

 5212235 - Xtream Serial-Over-LAN Service Software

Supports: DARC/VDARC/IG/VIG Westville or Jarrell hardware, and OS versions: 4.3.16

 HP xw8200 BIOS Floppy Set - 5191796-3

3 Pre-LFC Checks and Information Gathering

3.1 Required Linux Information Gathering

The following information must be recorded, it is NOT saved on System State:

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

d. Examine the results. If the results are similar to:

then HES (Hard Exam Split) mode is configured.

{ctuser@hostname} head -12 ppsserver.cfg

Record the PPS Information per the following EXAMPLE:

# AppTitle IPAddress IPPortNo HostName

Record the AppTitle

Record the IPAddress

Record the IPPortNo

Record the HostNameRecord

3.2 Additional Console/Gantry/Configuration Information Gathering (not

4 Pre-LFC Save System State

4.2 GOC2 Systems Upgrading to GOC3/4 - Save System State Twice

For GOC2 (Linux-Pegasus) systems, Save System State, see Table 4

4.3 GOC3/GOC4 - Save System State Once

5 GOC1/GOC2 Console Upgrade Only - Install GRE/Xtream

6 Host Computer LFC

6.1 Host Computer BIOS Requirement

1. Open a Unix Shell and become root:

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

[root@hostname] dmidecode | grep Ver

Authorized BIOS versions

Version: JQ.W1.13US = 1.13 for xw8000

Version: 786B8 v2.10 = 2.10 for xw8200

6.2 Linux Operating System (OS) Software Load - Host Computer

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

NOTE: The Host Computer must be powered ON to insert the disk.

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

(For 06MW03.X Software) Wait 1-2 minutes after the “System

(For English Keyboard only) GEHC2

(For International Command only) iGEHC2

If a DASM is connected, select [Ignore] as required for IO errors. If the boot:

9. After approximately 20 minutes, the OS is loaded on the Host Computer. A window

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

6.3 Application SW Load on the Host Computer

1. Open the tray on the Host Computer DVD-ROM Drive.

7 Config or Reconfig Setup

4. Input the correct:

g. Preference for HIPAA Present

HIPAA Present is normally Off, unless the customer requests HIPPA to be

h. Site preference for Dose Information Display

 [On] (full CTDiw Display)

10. Select proper PDU type.

13. Gateway Parameters:

 MUST NOT exceed 16 characters.

 It MUST NOT exceed 16 Characters.

c. IP Address - Site supplied

Sites requiring a User Defined IP address will be required to load

If the hospital backbone IP address is 192.9.220.xx, the Net Mask

e. Broadcast Address - Site supplied address

CAUTION: FAILURE TO SELECT THE CORRECT DAS HARDWARE CONFIGURATION

16. An Install INFO Acceptance window appears. (See Illustration 19)

18. A no-action- required pop-up message appears in approximately 1 minute: