Technical Publication

GE Medical Systems
Technical
Publication
Direction 2284291-100
Revision 08
GE Medical Systems
CT/I LFC Procedures for Versions 4.4,
4.5, 6.1, 6.2 and 6.3
Copyrighted © by GE Medical Systems, 2001, 2004

Page Left Intentionally Blank
2
Direction 2284291-100, Rev 08 CT/I LFC Procedures for Versions 4.4, 4.5, 6.1, 6.2 and 6.3
Important Precautions
LANGUAGE
WARNING This Service Manual is available in English only.
If a customer’s service provider requires a language other than English, it
is the customer’s responsibility to provide translation services.
Do not attempt to service the equipment unless this service manual has
been consulted and is understood.
Failure to heed this Warning may result in injury to the service provider,
operator or patient from electric shock, mechanical or other hazards.
AVERTISSEMENT Ce Manuel de maintenance n’est disponible qu’en anglais.
Si le technicien du client a besoin de ce manuel dans une autre langue que
l’anglais, c’est au client qu’il incombe de le faire traduire.
Ne pas tenter d’intervention sur les équipements tant que le manuel
Service n’a pas été consulté et compris.
Le non-respect de cet avertissement peut entraîner chez le technicien,
l’opérateur ou le patient des blessures dues à des dangers électriques,
mécaniques ou autres.
WARNUNG Dieses Kundendienst-Handbuch existiert nur in englischer Sprache.
Falls ein fremder Kundendienst eine andere Sprache benötigt, ist es
Aufgabe des Kunden für eine entsprechende Übersetzung zu sorgen.
Versuchen Sie nicht, das Gerät zu reparieren, bevor dieses Kundendienst-
Handbuch zu Rate gezogen und verstanden wurde.
Wird diese Warnung nicht beachtet, so kann es zu Verletzungen des
Kundendiensttechnikers, des Bedieners oder des Patienten durch
elektrische Schläge, mechanische oder sonstige Gefahren kommen.
AVISO Este Manual de Servicio sólo existe en inglés.
Si algún proveedor de servicios ajeno a GEMS solicita un idioma que no
sea el inglés, es responsabilidad del cliente ofrecer un servicio de
traducción.
No se deberá dar servicio técnico al equipo, sin haber consultado y
comprendido este manual de servicio.
La no observancia del presente aviso puede dar lugar a que el proveedor
de servicios, el operador o el paciente sufran lesiones provocadas por
causas eléctricas, mecánicas o de otra naturaleza.
3
Direction 2284291-100, Rev 08 CT/I LFC Procedures for Versions 4.4, 4.5, 6., 6.2 and 6.3
LANGUAGE
ATENÇÃO Este Manual de Assistência Técnica só se encontra disponível em Inglês.
Se qualquer outro serviço de assistência técnica, quE não a GEMS,
solicitar estes manuais noutro idioma, é da responsabilidade do cliente
fornecer os serviços de tradução.
Não tente reparar o equipamento sem ter consultado e compreendido este
Manual de Assistência Técnica.
O não cumprimento deste aviso pode por em perigo a segurança do
técnico, operador ou paciente devido a‘ choques elétricos, mecânicos ou
outros.
AVVERTENZA Il presente manuale di manutenzione è disponibile soltanto in inglese.
Se un addetto alla manutenzione esterno alla GEMS richiede il manuale in
una lingua diversa, il cliente è tenuto a provvedere direttamente alla
traduzione.
Si proceda alla manutenzione dell’apparecchiatura solo dopo aver
consultato il presente manuale ed averne compreso il contenuto.
Non tenere conto della presente avvertenza potrebbe far compiere
operazioni da cui derivino lesioni all’addetto alla manutenzione,
all’utilizzatore ed al paziente per folgorazione elettrica, per urti meccanici
od altri rischi.
4
DAMAGE IN TRANSPORTATION
All packages should be closely examined at time of delivery. If damage is apparent write “Damage In
Shipment” on ALL copies of the freight or express bill BEFORE delivery is accepted or “signed for” by a
GE representative or hospital receiving agent. Whether noted or concealed, damage MUST be reported to
the carrier immediately upon discovery, or in any event, within 14 days after receipt, and the contents and
containers held for inspection by the carrier. A transportation company will not pay a claim for damage if
an inspection is not requested within this 14-day period.
Call Traffic and Transportation, Milwaukee, WI (414) 785 5052 or 8*323 5052 immediately after damage is
found. At this time be ready to supply name of carrier, delivery date, consignee name, freight or express
bill number, item damaged and extent of damage. Complete instructions regarding claim procedure are
found in Section S of the Policy And Procedures Bulletins. 14 July 1993
CERTIFIED ELECTRICAL CONTRACTOR STATEMENT
All electrical installation, that’s preliminary to positioning of the equipment at the site or in preparation for
the equipment, shall be performed by licensed electrical contractors. In addition, licensed electrical
contractors shall perform all electrical feeds into the power distribution unit. Other connections between
pieces of electrical equipment, calibrations and testing shall be performed by qualified ge medical
personnel. The products involved (and the accompanying electrical installations) are highly sophisticated,
and special engineering competence is required. In performing all electrical work on these products, ge
will use its own specially trained field engineers. All of GE's electrical work on these products will comply
with the requirements of the applicable electrical codes.
The purchaser of GE equipment shall only utilize qualified personnel (i.e., GE’s field engineers, personnel
of third-party service companies with equivalent training, or licensed electricians) to perform electrical
servicing on the equipment.
IMPORTANT...X-RAY PROTECTION
X-ray equipment if not properly used may cause injury. Accordingly, the instructions herein contained
should be thoroughly read and understood by everyone who will use the equipment before you attempt to
place this equipment in operation. The General Electric Company, Medical Systems Group, will be glad to
assist and cooperate in placing this equipment in use.
Although this apparatus incorporates a high degree of protection against x-radiation other than the useful
beam, no practical design of equipment can provide complete protection. Nor can any practical design
compel the operator to take adequate precautions to prevent the possibility of any persons carelessly
exposing themselves or others to radiation.
It is important that anyone having anything to do with x-radiation be properly trained. They must also be
fully acquainted with the recommendations of the National Council on Radiation Protection and
Measurements. As published in NCRP Reports available from NCRP Publications, 7910 Woodmont
Avenue, Room 1016, Bethesda, Maryland 20814, and of the International Commission on Radiation
Protection.
The equipment is sold with the understanding that the General Electric Company, Medical Systems
Group, its agents, and representatives have no responsibility for injury or damage, which may result from
improper use of the equipment. Various protective materials and devices are available. It is urged that
such materials or devices be used.
OMISSIONS & ERRORS

Customers, please contact your GE Sales or Service representatives. GE personnel, please use the
GEMS CQA Process to report all omissions, errors, and defects in this publication.
5
Legal Notes
COPYRIGHTS
All Material Copyrighted(c) 2001, 2004 by the General Electric Company, All rights reserved.
REVISON HISTORY
Revision Date Reason for change

0 10/12/00 Initial Release
1 11/08/00 Updates to 4.4 procedure
2 04/27/01 Updated to included Indigo 384mb memory configuration
3 08/08/01 Document now includes SW release 6.2 LFC and Patch installation.
4 09/19/01 LFC option for 6.2 removed. Instructions for loading 6.2 patch according
to SW dependencies added.
5 10/16/01 LFC procedure updated to include 6.3 and patches. Added 4.5 patch
procedure
6 09/16/04 PQR 13013577 - Updated instructions on page 27, step 7.
7 09/24/04 PQR 13013714 - Updated instructions on page 37, step 11.
8 07/11/08 PQR 13120277 (13120279, 13121764, 13131803, 13144968)

Chapter 3, Section 2.7, updated step 7, added admin 13 menu selection.
Chapter 3, Section 2.7, updated step 7a, b, to include disk drive
partioning.
Chapter 3, Section 2.7, updated step 7e, to include an additional exit
command.
6
Table of Contents
Important Precautions ................................................................................................ 3
Legal Notes .................................................................................................................. 6
Table of Contents ........................................................................................................ 7
Chapter 1 ` Turbo LFC Procedure (Rel. 4.4) .............................................................. 9

Section 1 Introduction .......................................................................................................................................... 10
1.1 Appendix List: .......................................................................................................................................... 10
1.2 Software Load From Cold (LFC) Overview .............................................................................................. 10
Section 2 Load From Cold Procedure ................................................................................................................. 11
2.1 Install Software Contained On The Two CD-ROMs. ................................................................................ 11
2.2 Save System State Data and BMD Database (if applicable) ................................................................... 13
2.3 Record Information In Case Your System State MOD Is Lost/Damaged................................................. 19
2.4 Shutdown the System .............................................................................................................................. 24
2.5 Boot Standalone IRIX Disk Partitioning Utility.......................................................................................... 24
2.6 If You Have A Keyboard Other Than A US-English Keyboard................................................................. 25
2.7 Install System Software (Irix OS) ............................................................................................................. 25
2.8 Install CT/i Software On The OC ............................................................................................................. 28
2.9 Install CT/i Software On The SBC ........................................................................................................... 39
2.10 Setup time on the SBC and the OC ......................................................................................................... 40
2.11 Configure Touch ...................................................................................................................................... 40
2.12 Start up CT applications .......................................................................................................................... 41
2.13 Restore System State.............................................................................................................................. 41
2.14 Initialize Characterization......................................................................................................................... 43
2.15 Initiailize SBC and Verify Collimator Characterization ............................................................................. 43
2.16 Add Software Options .............................................................................................................................. 44
2.17 Convert the DICOM Camera Host File to the New Format ...................................................................... 47
2.18 Install Cameras........................................................................................................................................ 47
2.19 Install BMD (only if BMD Option is installed in section 2.17) ................................................................... 47
2.20 Convert the Network Host File to the New Format (For FIRST-TIME Upgrade to 4.4 ONLY) ................ 47
2.21 SW Gantry Revolutions Counter Verification/Initialization ...................................................................... 48
2.22 Shutdown the System & Restart Applications.......................................................................................... 49
2.23 Restore BMD Database (only if BMD Option is installed to the system).................................................. 49
2.24 Verify System Operation .......................................................................................................................... 50
2.25 “SW Gantry Rev Count “ option in HealthPage: (For FIRST-TIME upgrade to 4.4 ONLY) ................... 52
Appendix A Procedures for Creating Default Partitions:.......................................................................................... 55
Appendix B Procedures for Installing ConnectPro................................................................................................... 59
Appendix C Procedures for installing Dentascan filming option .............................................................................. 61
Appendix D Procedures for Installing Add-on Packages ......................................................................................... 63
Appendix E Changing the System Timezone .......................................................................................................... 65
Appendix F Installing Laser and DICOM Cameras .................................................................................................. 67
Appendix G Installation of Network Printer .............................................................................................................. 76
Chapter 2 SW Version 4.5 Patch Procedure ........................................................... 77

Section 1 Installation of the 4.5 Patch ................................................................................................................. 77
Section 2 De-installation of 4.5 SW Patch........................................................................................................... 78
7
Chapter 3 ` Turbo LFC Procedure (Releases 6.1 & 6.3) ......................................... 79

Section 1 Introduction .......................................................................................................................................... 80
1.1 Appendix List: .......................................................................................................................................... 80
1.2 Software Load From Cold (LFC) Overview .............................................................................................. 80
Section 2 Load From Cold Procedure ................................................................................................................. 81
2.1 Before You Begin..................................................................................................................................... 81
2.2 Save System State Data and BMD Database (if applicable) ................................................................... 83
2.3 Record Information In Case Your System State MOD is Lost/Damaged................................................. 87
2.4 Shutdown the System .............................................................................................................................. 92
2.5 Boot Standalone IRIX Disk Partitioning Utility.......................................................................................... 92
2.6 If you have a keyboard other than a US-English Keyboard. .................................................................... 92
2.7 Install System Software (Irix OS) ............................................................................................................. 93
2.8 Install CT/i Software On The OC ............................................................................................................. 96
2.9 Install CT/i Software On The SBC ......................................................................................................... 105
2.10 Setup time on the SBC and the OC ....................................................................................................... 106
2.11 Configure Touch .................................................................................................................................... 106
2.12 Start up CT applications ........................................................................................................................ 107
2.13 Restore System State............................................................................................................................ 107
2.14 Initialize Characterization....................................................................................................................... 109
2.15 Initialize SBC and Verify Collimator Characterization ............................................................................ 109
2.16 Security Patch (Version 6.3 SW Only)................................................................................................... 110
2.17 Add Software Options ............................................................................................................................ 112
2.18 DICOM camera Host File Conversion.................................................................................................... 115
2.19 Install Cameras...................................................................................................................................... 115
2.20 Install BMD ............................................................................................................................................ 115
2.21 Network Host File Conversion (For FIRST-TIME Upgrade from 5.x to 6.x ONLY) ............. 115
2.22 SW Gantry Revolutions Counter Verification & Initialization.................................................................. 116
2.23 Shutdown the System & Restart Applications........................................................................................ 117
2.24 Restore BMD Database (only if BMD Option is installed to the system)................................................ 118
2.25 Verify System Operation ........................................................................................................................ 118
2.26 “SW Gantry Rev Count “in Health Page: ............................................................................................... 121
Appendix A Creating Default Partitions ................................................................................................................. 123
Appendix B Installing ConnectPro ......................................................................................................................... 127
Appendix C Installing Dentascan filming Option.................................................................................................... 129
Appendix D Installing Add-on Packages................................................................................................................ 131
Appendix E Changing the System Timezone ........................................................................................................ 133
Appendix F: Installing Laser and DICOM cameras................................................................................................ 135
Appendix G Installation of a Network Printer ......................................................................................................... 143
Chapter 4 SW Version 6.2 Patch Procedures ....................................................... 145

Section 1 Before you Begin ............................................................................................................................... 145
1.1 Software Dependencies......................................................................................................................... 145
1.2 CTi 6.2 SW Load Scenarios .................................................................................................................. 146
Section 2 Installation of the 6.2 Patch (from CD-ROM) ..................................................................................... 146
Section 3 De-installation of 6.2 SW Patch......................................................................................................... 147
8
Chapter 1 `
Turbo LFC Procedure (Rel. 4.4)
PROCEDURE:
Archive Patient • Ensure all patient images are archived
Images
Load From Cold • Save System State Data

Procedure
• Record Key System Information
• Shutdown the System
• Boot Standalone IRIX Disk Partitioning Utility
• Install System Software OS on Operator Console
• Install System Software on the SBC
• Install CT/I Software on the OC and SBC
• Set Date and Time on the OC and SBC
• Start up CT Applications
• Restore System State
• Add Software Options
System • Save System State

Checkout
9
Section 1
Introduction
This document describes the procedure to load software version 4.4 on a HiSpeed
Advantage CT/i Indigo System from CD-ROM media. Please note the following
conventions:
• In this document, commands to be typed in by the user and output from the
computer system is shown in bold, Courier New font, for example: login
• distinctions between the various modes of load (IRIX versions, network vs local
loads) and important messages are shown in bold print, for example: Save
• Entry characters of one, lower-case-L, zero, & upper-case-O appear different (listed
respectively), for example: 1, l, 0, O
• The ”Enter” key (otherwise known as the ”Return” key) is indicated by <Enter>
1.1 Appendix List:

Appendix A : Procedures for creating default partitions
Appendix B : Procedures for installing ConnectPro
Appendix C : Procedures for installing DentaScan filming option
Appendix D : Procedures for installing add-on packages
Appendix E : Changing the System Timezone
Appendix F : Installing Laser and DICOM cameras
Appendix G : Installation of Network Printer
1.2 Software Load From Cold (LFC) Overview

HiSpeed Advantage CT/i Load From Cold (LFC) involves preparing the system disks,
installing and configuring the system software, on both the OC and SBC computers.
Notice: Make sure that all Images have been reconstructed and archived before performing
this procedure. This procedure will re-initialize all system data disk, erasing all images
and scan data.
10
Section 2
Load From Cold Procedure
2.1 Install Software Contained On The Two CD-ROMs.

• IRIX 6.2 OS CD-ROM
• HiSpeed CT/i Application Software(Base) CD-ROM
CDROM DRIVE VERIFICATION:

Since the CDROM Drive is seldom used except for loading system software, it's
advisable to perform a quick test on the ability of the CDROM drive. Read some data
from a CD before you begin the LFC procedure. Inserting and mount one of the OS
CDROM disks, and performing a checksum (read check) on the files in one of the
directories. If any errors occur while the system is reading this CDROM, you must stop
to investigate and correct the CD problem (for example the SCSI Bus, CDROM Drive
problems, etc.).
1. Open a UNIX shell.

2. Type:
tail -f /usr/adm/SYSLOG <ENTER>
3. Open a second UNIX shell.
4. Insert the IRIX 6.2 OS CD-ROM (2282439-2) into the CDROM Drive and type:
mountCD /mnt <ENTER>
cd /mnt/dist <ENTER>
sum * > /tmp/CDROMtest <ENTER> (~5 minutes to display prompt)
5. While the system is reading the CDROM and is calculating checksums, monitor the
SYSLOG, in UNIX shell window. Look for any error messages that may occur. Errors
related to SCSI or CDROM problems (timeouts, read errors, SCSI Bus resets, etc.).
6. If checks are successful (no errors produced), type the following command to verify
the checksum:
sum /tmp/CDROMtest <ENTER>
7. Verify that the resultant display for the command in step 6 is:
30761 10 /tmp/CDROMtest
11
8. If you encounter any CDROM or SCSI related errors during this check, stop and
troubleshoot/ repair the problem before attempting to perform the FMI.
9. Terminate the ’tail’ command by typing ^C in the first UNIX shell window where the
’tail’ command is running.
10. Unmount the CDROM by typing the following commands in the second UNIX shell
window:
cd / <ENTER>
unmountCD <ENTER>
VERIFY CDROM Firmware Revision on Toshiba XM6201TA Drives
11. Open a UNIX Shell

12. Type scsistat <ENTER>
13. Check the last column of the output line for the CDROM drive.
14. If the CDROM firmware revision is 1037 and the system has a Toshiba
XM6201TA installed, it is likely that the system will not load 4.4 software. The
drive should be replaced prior to attempting the 4.4 LFC.
For example :
ctuser@engbay24}[1] scsistat
Device 0 1 Disk SGI IBM DDRS-34560W FW Rev: S96A
Device 1 3 Optical Maxoptix T5-2600 FW Rev: A6.5
Device 1 4 Comm CenData ST-1400A FW Rev: V5.7
Device 1 6 CD-ROM TOSHIBA CD-ROM XM-6201TA FW Rev: 1030
The firmware revision is 1030.
12
2.2 Save System State Data and BMD Database (if applicable)
2.2.1 Find KV Board Installed Before You Do A Save System State:

To ensure that you know what KVBoard is installed in your system (This information will
be needed later in Sec 2.8 – 7 (g) ), follow the procedure listed below:
1. Bring the system up and start the applications.

2. Open a Unix shell.
3. Login to the SBC side (Type: rlogin sbc).
4. Become root (Type: su root).
5. Type: nbsClient obcr

You should now see the following prompt:
[NBS, OBCR]: [NBS, OBCR]:
6. Type: y <Enter>.
7. Some hardware information will come up - look for the line " =====| KV Board
Revision: "
The KVBoard information will be displayed. Record al of the information as it is
required later. __________________________
8. Exit nbsClient by using CTRL C. Proceed with system state save, and then with
reconfig/LFW/LFC.
9. Type CTRL D or type EXIT to return to the OC.
13
2.2.2 Save System State Data

Before beginning the software install, you will want to, save the system configuration
information, characterization, calibration, protocols, etc.
1. Bring the system up if it is not already up.

2. Click on the Service desktop.
3. Click on PM.
4. Highlight System State.
5. Click on the ”Start ...” button.

6. Click on ”All” (which will highlight Cals, Characterization, Reconfig Info, etc).
7. Click on Save.
8. A dialog box titled ’Save System State’ will pop up with the following message:
Select YES when the MOD is ready.
Select NO to exit without Saving.
Click on YES.
(The save will take a few minutes)
Review the output for errors or missing files; the scroll bar on the right works only
when the tool isn’t busy performing some task -- it takes a little while.
If you see any missing files or failures, then refer to the notice below.
Proceed to step 9 when the message window shows that Save system state was
completed and MOD released. The system will prompt with the following message in
the System State Message Log window:
Calibration Database: COMPLETE
Releasing MOD...
MOD Release completed with success.
Save/Restore System State: Completed successfully.
9. Click on Dismiss.
NOTE: SAVE/RESTORE SYSTEM STATE ERRORS
If System State reported no problems, then you may skip to the section, which records
collimator characterization values (page 8).
Save/Restore System State reports status on each file specification listed in the
/usr/g/config/SysState.cfg file. The status may be:
• Save (or Restore) of {filename} succeeded
• Save (or Restore) of {filename} skipped. File not found
• FAILED
A status of ”FAILED”, indicates potential problems, ”skipped” means the file not found
was not required. Please review the following for each file you see an error reported.
14
--------------------------------------------------------------------
If the site does not have InSite, you may see the following:
...
Save(or Restore)of insiteINFO skipped. File not found
Save(or Restore)of sclink.cfg skipped. File not found
Save(or Restore)of bg_schedule_data skipped. File not found
Save(or Restore)of intrusive_schedule_data skipped.File not found
Save (or Restore) of timeslot_data skipped. File not found
...
Save/Restore System State: Completed Successfully
For a site without InSite these will be seen and this should not be regarded as a
problem. A site with InSite should not get these errors; else you will need to reload
InSite or re-enter the ProDiags schedule later.
In case of a restore system state, the system may report
Chmod of sclink.cfg failed.
This is because during restore, the file is not found (Save skips the file if InSite is not
installed on the system).
Some files simply may not exist on the system. If certain tools were never run then
certain files may never get created. You may view /usr/g/config/SysState.cfg
and look for a req field. req=Y means the file in question is required. You may also
wish to check the system and MOD to verify whether is was actually missing or if there
were permission or owner problems with the file.
2.2.3 Handy commands:

mountMOD (mount the MOD on the /MOD dir)
ls -l /MOD/servicep_mod_data/system_state (or /MOD/serv*/sys*)
find /MOD -name ’*abc*’ -print (locates any file with ’abc’ in it)
cd; unmountMOD (must cd out of MOD dirs to unmount it)
more /usr/g/config/SysState.cfg (view the locations of System State files)
su - (password) man 1 chmod chown (access man pages as root)
rsh sbc (access the SBC)
--------------------------------------------------------------------
15
Notice: For the 4.4 upgrade, you must record the current collimator’s characterization
values so you can properly re-enter these values toward the end of the load. Values
are not automatically restored. They must be entered manually toward the end of the
load. 4.4 software is compatible with and provides support for the new G5 collimator. In
the Service Desktop, select Replacement Procedures -> Collimator Change ->
Mechanical Characterization -> Collimator Data, and record the values (i.e.: Closed,
1mm, 3mm, 5mm, 7mm, 10mm and CRC). These values are used for creating the new
collimator characterization file in Section 2.14. (Values can also be found in System
Integration -> Characterization -> Collimator, if the service key is not available.)
Collimator Data
Closed:
1mm:
3mm:
5mm:
7mm:
10mm:
CRC:
16
Notice: For the 4.4 upgrade, in ImageWorks, select an image, click Viewer -> User Prefs.
Select modality CT and record the values of Title, w/width and w/level for all entries.
These values are used for restoring the user preferences file in Section 2.14.
NOTE: If there are no images in the database, the user can create a SMPTE image by
selecting Troubleshoot -> Display Processing -> Install SMPTE image in the Service
Desktop.
User Preferences
Title: w/width: w/level:
2.2.4 For the [3.x] or [4.x] to [4.4] upgrade
Save Reformat Protocols

Insert or keep the proper system state save/restore MOD to the MOD drive.
1. mountMOD
2. cd /MOD
3. Check if the directory service_mod_data/system_state exists. If not:
mkdir service_mod_data/system_state
4. Check whether some reformat protocols are saved in the system, by typing:
ls –l /usr/g/ctuser/Prefs/VoxtoolPrefs/*
5. If some protocols are present then proceed further:
cp /usr/g/ctuser/Prefs/VoxtoolPrefs/*.flm /MOD/service_mod_data/system_state/
This will save all the reformat protocols available in the system onto the MOD.
Make sure you have copied all protocols to the MOD by typing the command:
6. CD /MOD/service_mod_data/system_state
7. ls -l
8. cd (this is to ensure that the next command is not run from /MOD)
9. unmountMOD
NOTE: The above ‘save’ method enables the Reformat protocols to be restored via the
normal ‘restore system state’ procedure after the applications have been installed.
17
Save ConnectPro Information

1. If you have the ConnectPro option, run ‘installhisris.’
2. Record the four data which will be required in Appendix B when you reinstall the
ConnectPro option.
3. Then ‘CANCEL.’
2.2.5 Backup BMD Database (only if BMD option is installed to the system)
1. Insert a MOD to the MOD drive for saving BMD database.
2. Switch to the ImageWorks Desktop, click on the ’BMD’ button on the browser.
3. Click on the ’Backup and Restore’ button on the BMD toolbar.
4. Click on the ’Backup to Archive Disk’ on the BMD Database Archive toolbar.
5. Click on the ’OK’ button to proceed with the backup.
NOTE: If the current MOD in the drive is un-initialized, click on ’OK’ button to make a file
system on the MOD.
6. To exit, click on the ’Quit’ button on the BMD Database Archive toolbar, and then
click on the ’Quit’ button on the BMD toolbar.
2.2.6 Record Computer Memory Configuration

Open a shell tool and check the hardware environment. Note the amount of main
memory installed in the system (192MB, 256MB, 384MB). You will need this
information later.
At the prompt in the shell, type hinv
The output will look similar to this - note the amount of memory installed.
{ctuser@somesystem} [1] hinv
Iris Audio Processor: version A2 revision 1.1.0
1 200 MHZ IP22 Processor
FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
CPU: MIPS R4400 Processor Chip Revision: 6.0
On–board serial ports: 2
On–board bi–directional parallel port
Data cache size: 16 Kbytes
Instruction cache size: 16 Kbytes
Secondary unified instruction/data cache size: 2 Mbytes on Processor 0
Main memory size: 384 Mbytes

EISA bus: adapter 0
18
Integral Ethernet: et0, IO0

Integral Ethernet: ec0, version 1
Integral SCSI controller 1: Version WD33C93B, revision D
CDROM: unit 6 on SCSI controller 1
Optical disk: unit 5 on SCSI controller 1
Optical disk: unit 3 on SCSI controller 1
Disk drive: unit 1 on SCSI controller 1
Integral SCSI controller 0: Version WD33C93B, revision D
Graphics board: Solid Impact
Graphics board: High Impact
NOTE: If you have a configuration of 384MB of main memory, you must have the memory patch
CD 2295259 to complete the software load. If you do not have this CD at this time, do
not proceed.
2.3 Record Information In Case Your System State MOD Is Lost/Damaged

This information is all saved on the System State MOD, but to be safe it should also be
recorded somewhere on your site in case the State MOD is lost or damaged. This step
is optional, especially if you have already recorded this information somewhere else.
1. Record the most important Reconfig INFO for the scanner.

The following procedure will gather all this info for you from the INFO file.
(a) Open or go to an Unix shell on the OC.
(b) View the INFO file created by reconfig; type:
more /usr/g/config/INFO <Enter>
(c) For each of the fields below look at the ”more file output” to find the associated
”setenv” value and record the value in the table provided.
NOTE: IP Addresses and Net/Broadcast Masks have the format www.xxx.yyy.zzz
19
NOTE: When recording the NEXT_PATIENT_EXAM_NUMBER, confirm that this number is

the most current value by looking at the lsat exam scanned from the Browser. If the
Browser shows a value higher than the INFO file, use the value from the browser.
System Configuration
Field Name: ”setenv” Name: Field Value:
System Service ID SERVICE_ID
Settings:
Hospital Name HOSPITAL_NAME
Exam Number NEXT_PATIENT_EXAM_NUMBER
DAS Type DASTYPE
PDU Type PDUTYPE
Network Gateway Host Name GATEWAY_HOSTNAME
Settings:
Gateway IP Address GATEWAY_IP
Gateway Net Mask GATEWAY_NETMASK
Gateway Broadcast Mask GATEWAY_BROADCAST
Suite Name SUITEID
Record the Networking Static Routing information (only if Static Routing is used)
If you know that this site uses Static Routing, record the data requested in this
procedure, because it is not automatically saved and restored during a Load–From–
Cold.
Otherwise, if you are not sure, perform the following steps to determine if Static Routing
is being used at this site:
(a) Open a UNIX shell.
(b) Type: chkconfig | grep routed [Enter]
(c) Look for the line that contains the following:
routed on/off <– Note that the route daemon will be either on or off.
Record the setting.
(d) Examine the following file to see if Static Routes are set up, and if they are, record
the following information from the following file:
Type: more /etc/config/static–route.options [Enter]
At the end of this file, there will be entries similar to the following if Static Routes are set
up:
$ROUTE$QUIET add default 3.7.53.3
or $ROUTE$QUIET add 192.168.1.1 192.0.2.5
or $ROUTE$QUIET add –net 10 192.0.2.3
20
NOTE: Ignore all lines that start with ”#” (comment lines), but record any Static Route
entries in the following table:
Static Route Information
$ROUTE$QUIET entry
$ROUTE$QUIET entry
$ROUTE$QUIET entry
$ROUTE$QUIET entry
Route daemon setting (routed on/off) ON / OFF
2. Record the Networking Application (Image transfer) Configuration.

On the ImageWorks Desktop, in the Browser under Network, for each host
configured for networking do the following and record the information in the table
provided:
(a) Click on Select Remote Host.
(b) Click on the Hostname.
(c) Click on Update.
(d) Write the information in the table provided.
(e) Click on Cancel to exit Select Remote Host.
If you find this process tedious, you can look at file

/usr/g/ctuser/Prefs/SdCRHosts on the system to get this information. The 1
in the file means Advantage Net, the 2 means DICOM. The pound sign in the file is
a separator and means nothing.
21
Networking Application (Image Transfer) Configuration

Host name Network Network Port AE Title
address protocol number
Archive Node* Send Images* Query/Retrieve* Custom Comments*

Search*
* Some systems may not have these categories
3. Record the Camera Application Configuration.

If you are currently on a Sonata system:
(a) Click on the Service Desktop button.
(b) Click on the Utilities tab
(c) Click on Install Camera.
(d) Write the information in the tables provided.
(e) For a Laser Camera configuration click on Cancel to exit.
(f) For a DICOM print configuration click on Accept to continue with the Image
Quality and Network Timeout parameters.
If you find this tedious, for Laser cameras you can look at the file
/usr/g/ctuser/app-defaults/devices/camera.dev on the system. To get
22
this information for DICOM print cameras, you can look at the files
/usr/g/ctuser/Prefs/SdCPHosts and
/usr/g/ctuser/app-defaults/print/dprint.cfg .
If you are not on a Sonata system, look at the file
/usr/g/ctuser/app-defaults/devices/camera.dev on the system to get

the information for Laser cameras.
Laser Camera Configuration
Camera Type:
DASM Type:
Film Type:
Options:
Valid Film Formats:
Default Film Formats:
DICOM Camera Configuration

Camera Type:
IP Address:
Host Name:
AE Title:
TCP/IP Listen Port:
Comments (optional):
Destination:
Orientation:
Medium Type:
Magnification:
Valid Film Formats:
23
DICOM Camera Advanced Configuration

Smoothing Type:
Configuration:
Minimum Density:
Maximum Density:
Border Density:
Empty Density:
Association Timeout:
Session:
N-Create:
N-Set:
N-Get:
N-Delete:
N-Action:
NOTICE: Make sure that all Images have been reconstructed and archived before performing
this procedure. This procedure will re-initialize all system data disk, erasing all
images and scan data.
2.4 Shutdown the System

Click on the (square red) Shutdown button (shown below). Press OK to shutdown
Applications. This will take down both CT/i Applications and UNIX and put you at the
boot prompt.
2.5 Boot Standalone IRIX Disk Partitioning Utility

1. Insert the IRIX 6.2 All Indigo Impact CD into the CD-ROM drive.
2. A message should be on the screen that says ”ok to power off the system now”.
The next step requires two selections in quick succession (you may only have three
seconds between selections); please read carefully before proceeding:
You will first be selecting ”Restart”, to bring up the system. A message may appear
about running power up diagnostics. Then a window will come up about starting up
the system. There will be a small button in the right hand corner: ”Stop for
Maintenance”. You will use the mouse to quickly press this button.
You should now select Restart and Stop for Maintenance.
24
3. A screen will pop up with several icons:

• Start System
• Install System Software
• Run Diagnostics
• Recover System
• Enter Command Monitor
• Select Keyboard Layout
2.6 If You Have A Keyboard Other Than A US-English Keyboard

1. Use the mouse and click on Select Keyboard Layout
2. Select the appropriate keyboard type. Supported keyboards are:
• English - US (default)
• German - DE
• Swedish - SE
• French - FR
3. Select Apply to reconfigure.
2.7 Install System Software (Irix OS)

NOTE: You need to follow the procedures for creating default partitions in Appendix A IF
AND ONLY IF you have a new disk, have just formatted or the disk is corrupted.
Otherwise go to step 1.
1. Click on Install System Software.
NOTE: Make sure that the IRIX 6.2 All Indigo Impact CD is in the CDROM drive.
Ensure the CDROM drive is not busy before proceeding to step(2).
2. Click on Local CD ROM.

3. Click on Install to proceed installation.
A Message will appear:
Insert the installation CD-ROM now
4. Click on Continue.
Message appears:
Obtaining installation tools
Another message appears:

Copying installation tools to disk
25
Screen goes blank

Message:
Creating miniroot devices, please wait ...
You will see a menu with 4 selections:

1. Run the installation startup script now.
2. Ignore the startup script.
3. Show the contents of the startup script.
4. Help/Show the introductory "README" statement again.
NOTE: If message "Unable to continue; press <Enter> to return to the menu" appears on
the screen, do the following:
a) Eject the CD from the CDROM drive, and re-insert the CD into the drive.
b) Click on the ’Return’ button to continue.
c) Click on the ’Stop for Maintenance’ button.
d) Proceed to step (3) in section 2.5
5. Select Ignore the startup script by entering:

Enter a Choice [1]: 2 <Enter>
You will see the install menu appear as follows:
Default distribution to install from: /CDROM/dist
For help on inst commands, type "help overview".
Inst Main Menu
1. from [source] Specify location of ...
2. list [keywords] [names] Display information ...
3. go Perform software ...
4. install [keywords] [names] Select subsystems ...
5. remove [keywords] [names] Select subsystems ...
6. keep [keywords] [names] Do not install or ...
7. step [keywords] [names] Interactive mode ...
8. conflicts [choice ...] List or resolve ...
9. help [topic] Get help in general ...
10. view ... Go to the view ...
11. admin ... Go to the Admin ...
12. quit Terminate software ...
6. Select admin
inst> admin <Enter>
You will see the admin appear as follows:
1. set [preferences] List all ...
2. date [args] Display or ...
3. files [names] List files ...
4. space List disk ...
5. recalculate Recalculate ...
6. sh [cmd] Escape to ...
7. shroot [cmd] Escape to ...
8. mount [fsname] [dir] Show mounted ...
9. umount [fsname] Unmount a ...
26
10. mkfs [blockdevice] Make a new ...

11. sethostname Set name of ...
12. sethostipaddr Set host ipaddr ...
13. savefilename Save selection ...
14. loadfilename Load selection ...
15. config [changed] List all or ...
16. hardware List machine ...
17. update keep file Add N(ew) .....
18. return Go to ...
Admin>
7. At the Admin> prompt, type:
sh <Enter>
sed s/3569/3157/g /CDROM/scripts/ct_autodisk > /bin/ct_autodisk <Enter>
chmod +x /bin/ct_autodisk <Enter>
/bin/ct_autodisk <Enter>
exit <Enter>
Message appears:
Starting automatic disk partition script
...
Ensuring the unnecessary partitions are unmounted
Wait about 1 minute.
8. Admin> load /CDROM/scripts/list.full <Enter>
A menu with 4 different selections will be displayed:
1. Run the installation startup script now
2. Ignore the startup script
3. Show the contents of the startup script
4. Help/Show the introductory "README" statement again
9. Select Ignore the start up script by entering:
Enter a choice [1]: 2 <Enter>
Wait about 1 minute.
10. Select return.
Admin> return <Enter>
11. Select go.
inst> go <Enter>
Pre-Installation check
Messages Installing/removing software will show percentage complete.
Wait about 10-15 minutes. Until the following message appers:
Installations and removals were successful.
If you are planning to install from a different CD, enter the CD in the drive and type:
from
12. After the load is complete, eject the CD-ROM from the drive.
NOTE: If loading is to be done from network then skip step 13 because if object server is off
then configuring the Network will give errors in IRIX 6.2
13. inst> shroot echo off > /etc/config/objectserver <Enter>

chrooting to /root
14. inst> shroot echo semmns =128 >> /var/sysgen/stune <Enter>
27
NOTE: The Syntax of this command is critical - make sure there is a "space" before the "="
and no "space" after the "=".
15. inst> quit <Enter>
Building dynamic ELF inventory file for rqs(1) processing..
Invoking rqs(1) on necessary dynamic ELF objects ...
Wait about 5 minutes.
Automatically reconfiguring the operating system

NOTE: If you did not do so earlier, eject the CD-ROM from the drive now.
16. Ready to restart the system? [y]es, [n]o, [sh]ell, [h]elp

Respond to the prompt: y <Enter>
System is starting
Iris internet address is the default.
Starting up system in standalone mode.
2.8 Install CT/i Software On The OC

NOTE: At this time, the systems state disk should be inserted in the drive - do not remove it
until it has been restored.
1. A large window will appear, Double click on ROOT

2. Open a ”Unix Shell” window by using the ”Desktop” pull down menu.
3. Insert the applications CDROM. Wait until the CDROM is not busy.
Type: install.ct <Enter>
NOTE: If you are using TEAC CD-ROM drive, when you execute the commands (e.g.:
install.ct) for the first time, it may pop up error message saying unknown CD-ROM
type TEAC may not function correctly. When you see this error message, execute
the command again. It will function properly.
If message ”/mnt/install - no such file or directory”

appears, do the followings:
a) Type: umount /mnt <Enter>
b) Eject the CDROM media from the CDROM drive
c) Re-insert the CDROM media into the CDROM drive
d) Proceed to step (2) in this section
28
The following window will appear:
Load Config
4. In the HiSpeed CT/i Install Utility window click on Load.

5. A pop up message will query if you wish to load the INFO file from the System State
MOD; if you have a System State MOD, select ”Yes”. Another pop-up message will
appear. Place the System State MOD in the drive and select OK.
In the following steps, you will now go through each of the Reconfig screens and
verify the information. You may make updates as needed. If you did not have a
System State MOD, you will need to enter the appropriate information (refer to the
data you recorded in section 2.3).
29
6. System Settings Screen:
(a) Change Hospital Name to the site’s preferred name.

(b) Enter the Service ID issued by the service organization. The
GENNET_ServiceID default must be replaced by a valid service ID.
(c) Select the Timezone for this site, and record it below.
Region / Time Zone
Notice: If the timezone of your location is not in the selection menu, select one of the
universal times. In this case, automatic changes for daylight-saving time will not
take effect.
(d) Verify/change Next Patient Exam # (it should be 1 larger than the ”last exam
number” recorded earlier).
(e) Select Preferences to proceed to the next screen.
Notice: The Next MOD#, & Next Diagnostic Exam # are currently not implemented.
30
7. Preferences Setup Screen:
NOTE: Options Doctor’s Title and Units for patient weight are not currently implemented.
(a) Select English the Language for installation
NOTE: English must be used for installation due to a tools problem if installed in another
language. The other language will be set up later in this procedure.
For the 4.4 upgrade, as the INFO file is being read from MOD, it has the old
language value and no language is being selected on the screen. Make sure you
have selected English on the screen.
(b) Select Preferred FastCal KV - select the kVs to be calibrated during FastCal.
NOTE: These kVs should include all kVs which the site uses for patient scanning.
Deselecting All Preferred FastCal KVs is the same as selecting ALL the Preferred
FastCal KVs.
(c) Select the desired Date Format and Time Format.

(d) Select the Default Archive Device.
31
NOTE: The selection sets up the device for autostore and selects the default archive media
on the browser.
(e) Select the desired Dose Information Display. Choose either On (full CTDIw
display), On but without display of the total DLP, or Off (no CTDIw display).
(f) Turn on or off the Streak Artifact Reduction as desired.
(g) Select Hardware to proceed to the next screen.
8. Hardware Settings Screen:
(a) Select the DAS Type for this system.
NOTE: New systems have an HP DAS. Upgraded systems may have either HP DAS or
Rev G4 EDAS.
(b) Select the Tube Type for the system.

(c) Select the PDU Type for the system.
NOTE: If the PDU Type of the system is not in the PDU Type selection, select HSA (46-
296220G1) / (46-327106G1).
(d) Select the desired Collimator/Filter Type.
32
NOTE: The G4 and G5 Collimators/Filters support the Smart Beam Option. If you check the
G1,G2,G3 box, Smart Beam will be disabled by the Scan user interface.
(e) If you have a Network Image Printer, select it. Next enter it’s Name and IP
Address.
NOTE: A ”PRINT SERVER” IS NOT SUPPORTED (ie: a computer with a printer attached);
a Network Image Printer (which is supported) is a printer directly attached to the
network.
(f) Camera Setup.
NOTE: Cameras will be installed later in the load through the Utilities menu in the Service
Desktop.
(g) KVBoard Selection
If you have found out the kVBoard Type from sec 2.2.1, select that generation of
kVBoard type.
If you don’t know the kVBoard type, open the gantry and check the type printed
on the installed kVBoard.
(h) Select Network to proceed to the next screen.
33
9. Network Settings Screen
OC SBC
Networking Notes are on the next page.

Refer to the data you recorded in section 2.3 to verify these entries.
(a) Host Name identifies the name of this scanner. This name must be unique for
the site, and will appear in unix prompts and in a few other places. If you set up
a network connection to the site, the OC computer will appear on the site’s
network as <Host Name>.
(b) Suite Name must start with a letter, followed by 3 alphanumeric characters (ie: it
MUST be 4 characters long). The name of the Bit-3 OC interface will be <Suite
Name>_OC0 and the Bit-3 SBC interface will be <Suite Name>_SBC0.
34
If the CT/i scanner is not connected to a ”Site Subnet”, then;

• Verify all other fields are set to the defaults listed in the diagram above, and
fields Host Name and Suite Name are set to ct01 and CT01 respectively; if
you change the Gateway IP Address and have InSite, you must notify the
OnLine Center.
• You should now skip to the step titled *** READY TO INITIATE
INSTALLATION *** on the next page.
Networking Notes:
The CT/i scanner’s OC computer and SBC computer form the scanner’s
subnet. The Bit3 VME to VME connection is the wire connecting the
computers in the subnet. Due to the nature of the VME to VME direct
connection, no other computers can be added to the scanner’s subnet.
The ethernet connection on the OC can connect the scanner’s subnet to
the site’s subnet via a standard Ethernet TCP/IP connection. If the OC’s
Ethernet connection is used, then this Ethernet port is said to be the gateway
connecting the scanner’s subnet to the site’s subnet.
If the system you are installing is replacing a Genesis-based HLA or HSA
scanner, you can reuse the networking information from the old scanner as
follows:
HLA/HSA Suite Id ---> CT/i Suite Name

HLA/HSA Suite Id ---> CT/i Host Name
HLA/HSA 2nd Ethernet Gateway IP Address ->CT/i Gateway IP Addr.
HLA/HSA 2nd Ethernet Gateway Netmask --->CT/i Gateway Netmask
(c) The OC and SBC IP Address & Net Mask should always be set to the defaults
listed in the diagram on the previous page.
NOTE: Due to a limitation of the Bit-3 Networking software, the Netmask for the OC and
SBC subnet is always 255.255.255.0.
(d) Advanced Options
The Advanced networking options provide support for NIS.
Do not turn on NIS unless requested by the site’s network administrator.
Selecting the Use NIS? option allows the scanner to use the site’s NIS (a.k.a.
Yellow Pages) database. The Domain Name must be provided by the site’s
network administrator.
When you turn on NIS, you should enter the domain name and router ip address
without fail. Error message will pop up, when you select NIS on and leave these
2 fields blank.
NOTE: For the first time upgrade to 4.4, the domain name & ip address will not be
present in INFO file. So, the operator has to fill it, if turned on.
35
Network Settings Screen when NIS is turned “on”
*** READY TO INITIATE INSTALLATION ***

10. Disable the route daemon.
Open a “Unix Shell” OC window from the Toolchest and become root by
Typing: su - root <Enter> (then enter the root password).
At the operating system prompt type: chkconfig routed off <Enter>
Exit the root session by typing: exit <Enter>
11. Enable a static default route (Only if applicable)
Do not do this step unless confirmed by the site’s network administrator. The
default router IP address must be provided by the site’s network administrator.
36
Open a “Unix Shell” OC window from the Toolchest and become root by typing:
su root <Enter> (then enter the root password).
At the operating system prompt type:
echo '$ROUTE $QUIET add default <IP address of the default
router>' >> /etc/config/static-route.options
For example: echo '$ROUTE $QUIET add default 3.7.52.252' >>
/etc/config/static-route.options
12. Select Accept to utilize the configuration and continue installation.
13. The system will load the CT/i software, OS patches, kernel changes and configure
the system.
This will take between 35 and 60 minutes.
While the load is going on, the results will be displayed in a shell window (which
closes when the load is complete). All the window output is logged to a file named
”/var/adm/install.log.YYYYMMDDWWWHHMMSS” (where
YYYYMMDDWWWHHMMSS is the Date/Time that the process was started).
14. The system will then prompt you to reboot
Click on YES.
15. The system will automatically login in as ctuser after the reboot.
Select OK on the ”AutoStart Disabled” popup message.
NOTE: If the system does not reboot after 10 minutes, cycle power and continue with the
procedure at step 15.
16. Installing the Memory Patch for 384MB of Main Memory

If your system is configured with 384 MB of main memory (as recorded in step
2.2.5), a memory patch must be installed to support this configuration. To install the
memory patch, follow the steps below. If you do not have a memory configuration of
384MB, proceed to step 19 and do not complete the memory patch installation steps
below.
typing: su - <Enter> (then enter the root password).
Insert the IRIX Memory Patch CD, Part number 2295259, into the CD Drive
(a) Mount the CD
type: mountCD /CDROM
type: cd /CDROM
(b) Execute the Installation Script

type: install_memory_patch
37
(c) Verify that no errors show on the screen, and that the install succesful message is
printed on the screen. A successfull load should print a message similar to the
below:
install_memory_patch[50]: test: argument expected
Loading IRIX 6.2 PatchSG0003484 ...
Reading installation history .. 100% Done.
Reading distribution .. 100% Done.
Checking dependencies .. 100% Done.
Pre-installation check .. 100% Done.
Installing/removing software .. 0%
Installing new versions of selected patchSG0003484.eoe_sw
subsystems
Installing/removing software .. 100% Done.
Running exit-commands .. 100% Done.
Installations and removals were successful.
You must reboot your system to complete the installation.
Loading of IRIX 6.2 PatchSG0003484 is complete.
(d) Unmount the CDROM

type: cd /
type: unmountCD
(e) Remove the CDROM from the drive
(f) Verifying Successful Patch Load
Verify that the patch exists by opening a UNIX Shell.
Once the shell is open, type: showprods | grep 003484
A successful load of the patch will return the following:
I patchSG0003484 03/05/2001 Patch SG0003484: Audio/Serial

Option tlbmiss
invalid kptbl entry panic fix for IRIX 6.2
I patchSG0003484.eoe_sw 03/05/2001 IRIX Execution Environment
Software
I patchSG0003484.eoe_sw.unix 03/05/2001 IRIX Execution
Environment
17. Reboot the system
NOTE: If the system does not reboot after 10 minutes, cycle power and continue with the
procedure at step 18.
19. Insert the Applications CD 2282440-3 into the CDROM drive.

20. Open a unix shell from the toolchest. and login as root
Type: ls –al /usr/g/informix/data*
If there are any files of length 0 with the name form ‘dbfile*’
38
Type: Install2Disk
Again Type: ls –al /usr/g/informix/data* ( or !ls )
If there are any files of length 0 with the name form ‘dbfile*’, restart the complete
LFC or contact the OLC
NOTE: The following is to prepare the OC for network booting the SBC
Type:
loadSBC <Enter>
<Enter> again after messages
NOTE: If the CD-ROM is TEAC and the command fails, repeat the commands This will take
about 5 minutes.
2.9 Install CT/i Software On The SBC

1. Connect to SBC over the serial line using cu. In a shell window on the OC type:
cu sbc <Enter> (If you do not get a prompt, press ”Enter” a couple times.)
NOTE: If this doesn’t work, try sending a break signal ~%b (ie: tilde percent b).
2. If there is not a MC68040> prompt, login as root and type: halt <Enter>
3. At the MC68040> prompt Type: b vd() <Enter>
The system will then boot over the network. After about 2 minutes you should get a
login prompt.
4. Login as root. (No password is required): root <Enter>
5. Type: ctloadSBC <Enter>
The following menu appears:

Choose your option for auto partition & label...
1 - Label ’sd0 and sd2’ - then continue loading system
2 - Label ’sd0’ only - then continue loading system
3 - Do not relabel disk, just continue loading system
4 - Exit to user shell
At the menu enter: 1 <Enter>
The SBC loads all of its software, configures itself and finally reboots.
This can take up to 50-60 minutes.
NOTE: During software load, if error message ”UX:dd: ERROR: Cannot open
/CDROM/sbc_files/hlfc/xx: No such file or directory” appears on the screen, do the
following:
a) Wait for the boot prompt: ”Boot: ”

b) Sending a break signal by typing: ~%b (ie: tilde percent b)
c) Eject the CD from the CDROM drive and re-insert it into the drive
d) Proceed to step (3) in this section
39
6. Remove the CD from the drive.

7. To Exit the cu session type: ~. <Enter>
i.e.: to exit the cu session press the following keys : <tilde><dot> <Enter>
2.10 Setup time on the SBC and the OC

*** YOU MUST DO THIS ***
NOTE: Setting the timezone correctly on the SBC is important to the OC; if not correct, the plot
function in Smart Prep may not work.
1. Open a ”Unix Shell” OC window from toolchest, become root: su root <Enter>
(then enter the root password)
2. Type: setdate and input the appropriate values
Verify the dates and times on the OC and the SBC are the same.
NOTE: If the dates or times are not the same, re-try step (1) to (2) in this section, and re-
verify the dates and times. If the dates or times are still not the same, proceed to
Appendix E for changing the timezone to one of the universal times. In this case
automatic changes for daylight-saving time will not take effect.
3. To Exit the root session on the OC window, type: exit <Enter>. Then type: exit
<Enter> again to close this window.
2.11 Configure Touch

The following steps will setup the display for touch. If you do not have a touch
monitor skip to the next section - Start up CT applications.
1. In a ”Unix Shell” window, become root: su root <Enter>

2. Type: cd /usr/g/xtouch <Enter>
3. Type: ./setup <Enter>
4. The ”Serial Device Name” field should contain: /dev/ttya2

5. Click on software calibrate
NOTE: In the next two steps, be sure to carefully touch the indicated corners of the monitor.
If you do not, you will later find the cursor does not correctly land at a touched
location on the monitor -- you will then need to re-run this touch procedure.
6. Touch on lower left corner.

7. Touch on upper right corner.
40
8. Click on save settings.
NOTE: This setup program will dump core if you are not running it as root; if this occurs,
simply re-execute the procedure.
9. Click on exit
Notice: ’xtouch’ will not take effect until the next time ctuser logs in or system reboot.
10. Logout root session by typing: exit <Enter>
11. Close the unix shell window by typing: exit <Enter>
2.12 Start up CT applications

Start up system by opening a unix shell window and type ’startup’.
Notice: An error message will be displayed in the message window that says: ”Failed to
initialized with current tube usage file. Will not record tube usage.” Please ignore
this error message because the system state has not been restored.
2.13 Restore System State

The following procedure restores Characterization Data, Calibration Data, Protocols,
etc., from your System State MOD. If you don’t have a System State MOD, skip this
section.
NOTE: Image Works should not be displaying any images when you restore System State (to
ensure preferences are restored correctly). If you were in Images Works earlier, you
should go back and exit to the Browser.
1. Insert Save System State MOD in to MOD drive.

2. Click the button for the Service desktop.
Notice: If the Service Key is installed, the user has to press the (1), (2), (3) keys in order to
proceed.
3. Press the PM option from the list.

5. Press the Start button.
6. Click on All, which will highlight the cals, characterization, etc.
7. Press Restore (it will deselect ”Reconfig Info”).

8. A dialog box titled ’Restore System State’ will pop up with the following message:
Select YES when the MOD is ready
Select NO to exit without restoring.
Click on YES.
41
The restore takes a few minutes.

Review the output for errors or missing files. The scroll bar on the right works only
If you see any errors, review the ”Notice” in section 2.2 and the one
immediately following step 9 below.
Proceed to step 9 when the System State Message Log window shows displays the
following messages:
Releasing MOD ...
MOD release completed with success.
9. Once the restore is complete, respond Yes to the ”Reset Hardware?” prompt; this
takes a couple minutes; (note that the System State Reset Box may be partially
covered by the System State Message Log). When complete, select Dismiss.
NOTE: If the prompt does not appear then select the following:
a) System Resets
b) Scan
c) Run
d) Upon completion, Exit via the File pulldown.
10. Remove the System State MOD
42
Notice: RESTORE SYSTEM STATE ERRORS AND WORKAROUND
=> For the 4.4 upgrade, files collimator_g4.char, collimator_g5.char and

AdvantageUserPrefs did not exist on the System State. Therefore, the tool will
report errors during the restore on 4.4.
To create the collimator characterization file, in Service Desktop, select

Replacement Procedures -> Collimator Change -> Mechanical Characterization ->
Collimator Data, and replace the default numbers by the numbers recorded in
Section 2.2. (Values can also be entered in System Integration > Characterization >
Collimator if the service key is not available.) Then select ’Update Table’, ’Continue’
and finally ’Hardware Reset’ for reading the new characterization file. Exit
Mechanical Characterization tool.
=> To create the user preferences file, in ImageWorks, select an image, click Viewer
-> User Prefs. Select modality CT and replace the default titles and values by the
titles and values recorded in Section 2.2. Then select ’Set as default’ and exit the
tool.
NOTE: If there are no images in the database, the user can create a SMPTE image by
selecting TroubleShoot -> Display Processing -> Install SMPTE image in the Service
Desktop.
2.14 Initialize Characterization

Initializing the system characterization is needed each time the software is loaded.
In Service Desktop, select System Integration -> Characterization, then click Start.
When the Characterization window appears the initialization is complete. Select File
from the menu bar and then select Exit.
2.15 Initiailize SBC and Verify Collimator Characterization

Notice: IMPORTANT: Do this before rebooting to ensure proper SBC initialization (timer files).
Rebooting the SBC after the first applications startup but before proper SBC initialization
can result in corrupt SBC timer files which may fill the SBC disk partition.
1. Run Tube Warmup (this step initializes the timer files).

2. Verify collimator characterization and calibration by scanning at appropriate kVs and
apertures.
43
2.16 Add Software Options

Software Options must be loaded every time the OC software is reloaded.
1. In Service Desktop, select Utilities -> Install Options, then click Start.
An Options Window appears:
2. Click on the “Install” button.
3. Click on the “Permanent” button.
44
4. Click on the “MOD” button
5. Insert the Options MOD into the drive
Notice: This selection must be run once for each option MOD you are loading. For example,
if you have two options MODs you must run this selection twice.
6. Click on OK.
45
Example screen showing the options on sample MOD and options installed on
sample system:
7. Select the options to be installed (ex: click & drag down to highlight all the available
options, then release).
NOTE: 1) If there is a scroll bar present, you may have to complete the installation in two
steps.
2) CTPerfusion and Turbo Recon are not CT/I / INDIGO options
8. Click on the Install button.

A box may appear while the options are loading
When the option is displayed in the ”Installed Options” list, then installation of that
option is complete. Note that some options take a fraction of a second to install,
while options like 3D may take a half a minute (due to the fact that they are installing
software).
NOTE: If you install ConnectPro as an option, you need to follow the procedures in
Appendix B.
9. After all the options are installed, select Quit twice, then OK.
NOTE: Do NOT reboot at this time, but continue as directed, and when you have completed
installing all options, proceed to section 2.18.
46
10. Remove the MOD & write protect the side with options. (Note: The initial install
requires the MOD to NOT be write protected; subsequent installs can be done with
the MOD write protected).
11. If you have another option MOD to load, go back to step 2.
NOTE: If you have installed Dentascan and the camera is setup, you need to follow the
procedures in Appendix C for installing Dentascan filming option.
2.17 Convert the DICOM Camera Host File to the New Format
NOTE: For FIRST-TIME Upgrade to 4.4 ONLY
This has to be done after restoring camera preferences (or system state).
1. In the Service Desktop, select Utlities -> Shell and open a unix shell.
2. Type: updateCameraConfig
2.18 Install Cameras

Camera installation is required in the following cases:
• Loading a new system.
• Loading a system with Sonata software for the first time.
• When a system state MOD is unavailable, unreadable or does not contain camera
preference information.
• If changes need to be made to existing camera configurations.
To install cameras, proceed to Appendix F: Installing Laser and DICOM Cameras.
2.19 Install BMD (only if BMD Option is installed in section 2.17)

Please proceed to the BMD documentation for BMD software installation.
2.20 Convert the Network Host File to the New Format (For FIRST-TIME
Upgrade to 4.4 ONLY)
Notice: If the user is unsure whether the Network Host File has the old Format, type:
cat ~ctuser/Prefs/SdCRHosts
An example of the OLD format is as follows:
3.7.52.160 aw31pc0 # 2 4006 No Comment
An example of the NEW format is as follows:
3.7.52.160 aw12pc0 # 2 4006 aw12pc0 No Comment 0 1 1 0
47
Notice the alphanumeric field “aw12pc0” and numeric fields “0 1 1 0” are added in the
new format of the Network Host File.
Please proceed onto steps (1) to (3) ONLY IF the system has the OLD format of
the Network Host File.
1. Open a “Unix Shell” OC window in Service Desktop, select Utlities -> Shell.
2. Type: su – (then enter the root password).
3. Type: configRemoteHostFile
NOTE: Applications must be shutdown and restarted for the New format SdCRHosts file to
be used by the Application.
2.21 SW Gantry Revolutions Counter Verification/Initialization

Shut down the application. In Service Desktop select Utilities & click on Shutdown
Application.
Since SW Gantry Revolutions Counter is a new feature introduced in release 4.4 during
“First Time upgrade Only “ do the following steps in Section A ,otherwise proceed
onto steps in Section B ( during the subsequent loads ).
SECTION A:
1. On a unix shell Type: rsh sbc rm /usr/g/service/log/GantryRev.stats.
2. Record the number of gantry revolutions counts information from “Odometer” in the
gantry
3. Open a Unix Shell on OC & type: rsh sbc,
Type : putStats
When prompted enter the “note down number” in step(1)
4. Type: getStats 6 | more,
Verify the “no. of gantry revolution counts” (in the top line) info from the o/p to be
same as that from step (2).
Come out of sbc by typing : exit.
5. Proceed to “shutdown the system and restart the applications” section.
SECTION B:
1. Note down the no. of gantry revolutions counts information from “Odometer” in
gantry.
2. Open a unix shell and type: rsh sbc getStats 6 and verify that the gantry
revolutions counts info in step(2) to be same as that of step (1) .
If both the readings are same then proceed to “shutdown the system & restart the
applications”. Otherwise record the difference between (1) and (2) readings (
odometer counts - software counts )
48
3. Type: rsh sbc
4. Type: putStats
5. When prompted enter the difference noted down if any in step(2).

6. Proceed to “shutdown the system & restart the applications.”
2.22 Shutdown the System & Restart Applications

1. Open a Unix Shell
2. Login as root ( By doing 'su - root' and subsequently entering Password)
Note: To become root, you should use ‘su –‘ and not simply ‘su’. Otherwise, you will not
have proper permissions.
If you need to change languages:
3. Run reconfig.
4. In the ‘Preference Settings’ Screen select the Language to display on the scanner
system.
5. Select Accept.
6. When the Reboot popup appears – select YES.

7. After the system starts up and you can access a UNIX shell, do reconfig on SBC:
• become root again
• rsh sbc
• reconfig
8. After the SBC reboots and the shell reverts to the OC type: st <Enter> to bring up
the applications.
Otherwise:
9. Run ‘reboot’.
10. After the system starts up and you can access a UNIX shell type: st <Enter> to
bring up the applications.
NOTE: If the system does not reboot after 10 minutes, cycle power and continue.
2.23 Restore BMD Database (only if BMD Option is installed to the system)
1. Insert the MOD with BMD database to the MOD drive.
49
4. Click on the ’Restore from Archive Disk’ on the BMD Database Archive toolbar.
5. Click on the ’OK’ button to proceed the restore
2.24 Verify System Operation

These are suggestions for things to try to make sure the system is operating properly
after upgrading or reloading the software.
1. SBC Timerfiles.
(a) In a Unix shell, rlogin to SBC. Change directories to: cd
/usr/g/service/log. List the SBC timer files: ls -l *timers*
Note: In the above command string, the the ”-l” is <dash>
<lower-case L>.
you should see the following files listed:

dataacq.timers.log
fwmgr.timers.log
scanmgr.timers.log
scif.timers.log
(b) Verify timer file integrity by running the following commands:
Note: In the following command strings, the the ”-l” is <dash>

<lower-case L>, and the separator ”|” before ”head” is the ”pipe” symbol.
• timerReport -l dataacq.timers.log | head

timerReport -l fwmgr.timers.log | head
timerReport -l scanmgr.timers.log | head
timerReport -l scif.timers.log | head
• This is an example output report of a good timer file.
Report Generation Date: Wed Aug 13, 19100 10:29:27
ZeusRP System Timers Report
-------------------------------
From: Tue Aug 12, 1997 16:42:58
Through: Wed Aug 13, 1997 14:43:57
Hospital: Green Bay Packer Memorial Hospital
Suite Id: RP11
• This is an example output report of a bad timer file:
validateLogHdr(): unexpected magic number (djka;tiouapoietu) found in
scanmgr.timers.log. Expected (TIL).
File [scanmgr.timers.log] is not a Timers Log ... file not processed
50
(c) If any of the timer files are bad, then remove the bad timerfile. (Note you must be
root to remove the dataacq timers file).
Example: rm scnmgr.timers.log.
After removing the corrupt timer file, to generate a ”good” timer file, reboot the
system and rerun section 2.15
2. ExamRx Desktop:
(a) Start the system and make sure you are on the ExamRx desktop.
(b) Verify that the date and time shown in the system status area is correct.
(c) Perform Tube Warmup and Fastcal.
(d) Set ExamRx Display up to Autoview using your favorite Autoview layout
(e) Verify Touch (if installed); make sure the cursor moves to the exact location
touched. Touch new patient and make sure the next screen appears.
(f) Scan your favorite image quality phantoms to ensure the system is making good
images. Make more than one image in a series so you can play with the images
below.
(g) Verify that the date and time shown on the images and in the browser are
correct.
(h) If your system has a Touch monitor installed, touch a few things on the Scan
Prescription screen to verify that touch is working and aligned correctly.
(i) If you have the SmartBeam option installed, set at least one scan to use Large
SFOV and verify that the text on the Scan User Interface says Large%. If you
don’t have SmartBeam installed the SFOV button will just say Large. Make sure
this group scans normally and check the image quality.
(j) Watch to make sure the images autoview.
(k) Use List/Select to bring an image up in an ExamRx free viewport.
(l) Try each of the Window/Level Preset keys to make sure they are set correctly.
(m) Set the window level via the mouse.
(n) Set the window level via the trackball.
(o) Use the Trackball to Page through the images.
(p) Film at least 1 sheet of film and verify the image quality.
(q) If the site has a Network Image Printer, verify the print quality.
3. ImageWorks Desktop:
(a) Go to the Image Works Desktop.
(b) Select Network and make sure all of the Remote hosts were restored when you
restored the system state. If they were not restored, use the information you
saved earlier to configure for networking.
(c) If you have any Genesis based systems configured for networking, and they are
up and running, select one of the remote systems and Query to see if you can
see those systems. (If the Hospital and the user on a remote system grants you
permission, try pushing images to the remote system.) Use both genesis and
non-genesis images if available.
51
(d) If you can see those systems, try pulling one or more exams onto this system.
(e) If it is alright with your site, try pushing images to and all Genesis and DICOM
systems that you have in your network configuration.
(f) Use Archive to restore one or more of the most recent Exams performed by the
site.
(g) Select an interesting Exam in the Browser and click on CT Viewer to see the
images.
(h) Try each of the Window/Level Presets to make sure they are set correctly.
(i) Set the window level via the mouse.
(j) Try a reformat of an interesting series.
(k) If you have the 3D option, try doing a 3D rendering of an interesting series.
(l) Print at least one film and check the image quality.
(m) Remove one or more of the Exams you pulled onto the system.
4. Service Desktop:
(a) Go to the Service Desktop.
(b) Click on Utilities to see the list of Utility Applications.
(c) Click on Verify Security and Start to see if the system can see your security
key.
(d) Click on Verify Options and Start to see if the right options are configured.
(e) Click on Scan Analysis and Start to see if you can see the scan files you made
earlier.
(f) Click on System Resets, perform a Scan Hardware Reset, and verify that it
completes normally.
(g) When the Scan Hardware Reset is complete, click on Cleanup to exit all the
Service applications.
5. Sherlock
(a) Place the Sherlock CDROM in the CDROM drive.
(b) Select Sherlock to see it.
(c) Go through a few screens to make sure you can use Sherlock.
2.25 “SW Gantry Rev Count “ option in HealthPage: (For FIRST-TIME

upgrade to 4.4 ONLY)
1. Open a unix shell & make sure that system state MOD is mounted by typing
mountMOD
2. Type: RevCountOptionAdd
3. Through Service Desktop -> PM -> System Health Page -> Configure -> Edit
Report
4. Verify the “SW Gantry Rev Count “ option in the GUI by scrolling through the
list.
52
5. Type: unmountMOD
6. Type: exit
53
54
Appendix A
Procedures for Creating Default Partitions:
Run this procedure IF AND ONLY IF if a hard drive has been replaced or reformatted.
1. Select Enter Command Monitor icon. A boot monitor screen will pop up.Start
standalone disk partitioning utility.
NOTE: Make sure that the O/S CDROM (‘Pa’ for IRIX 6.5) is in the drive, and that the
CDROM drive is NOT busy before you proceed.
For IRIX 6.2, at the >> prompt type the following:

boot -f dksc(1,6,8)sashARCS dksc(1,6,7)stand/fx.ARCS - -x <Enter>
For IRIX 6.5, at the >> prompt type the following:
boot -f dksc(1,6,8)sash64 dksc(1,6,7)stand/fx.64 <Enter>
NOTE: If the boot is not successful, retry the command again.
2. Type the following responses to the indicated prompts:

(a) Do you require extended mode with all options available(no) ? yes
(b) fx: ”device-name” = (dksc) <Enter>

(c) For IRIX 6.2:
fx: ctrl # = (0) .... 1 <Enter> (ie: one)
For IRIX 6.5:
fx: ctrl # = (0) ...... <Enter>
(d) fx: drive # = (1) .............. <Enter>

Message appears: SGI drive type = <Disk Model No.>
--- please choose one (? for help, .. to quit this menu) ---
[exi]t [d]ebug/ [l]abel/
[b]adblock/ [exe]rcise/ [r]epartition/
(e) fx> r <Enter>
[ro]otdrive [o]ptiondrive [e]xpert
[u]srrootdrive [re]size
(f) Select [ro]otdrive.
fx/repartition> ro <Enter>
55
fx/repartition/rootdrive: type of data partition = (xfs) ... <Enter>

(h) Continue? ........ y <Enter>
(i) Go up a menu .. <Enter> (ie: two periods)

(j) Select [l]abel l <Enter> (ie: lower-case-L)
(k) Select [sy]nc sy <Enter>
(l) Go up a menu .. <Enter> (ie: two periods)

(m) Select [exi]t exi <Enter>
The screen will go blank and return to the system menu; (ie: the screen with the
list of icons).
3. Select ”Install System Software.
Note: Make sure the CDROM drive is NOT busy before proceeding to step (4).
4. Click on Local CD Rom.

5. Click on Install.
A message will appear: Insert the installation CD Rom now.
Note: You already have the IRIX 6.2/6.5 Pa CD in the drive from section 2.5, step (1).
Message appears: Obtaining installation tools.
Another message appears: Copy installation tools to disk.
Screen goes blank.
Message: Creating miniroot devices, please wait ...
Note: If creation of the miniroot devices fails with a message such as ”Filesystem is too
large for device”, do the following steps:
a) At the ”Hit Enter to go to a C shell” prompt, press <Enter>
b) For IRIX 6.2:
At the # prompt, type: mkfs /dev/dsk/dks1d1s0 <Enter>
For IRIX 6.5:
c) Proceed with step (7) below
Notice: Depending on the type of hard drive, the system may set the drive up initially with a
default filesystem and blocksize. If so, the following prompts may not appear and
steps 7-10 should be skipped. Later, during the load, the system will reset the drive
to the correct filesystem type and blocksize.
7. Make new file system on <Disk Device> [yes/no/sh/help]: yes <Enter>
56
NOTE: For IRIX 6.2, <Disk Device> should be /dev/dsk/dks1d1s0. For IRIX 6.5, <Disk
Device> should be /dev/dsk/dks0d1s0.
8. Are you sure? [y/n] (n): ...................................... y <Enter>
9. For IRIX 6.2:

Do you want an EFS or an XFS filesystem? [efs/xfs]: ................ xfs <Enter>
For IRIX 6.5:
Skip to step 10.
10. Block size of filesystem 512 or 4096 bytes? ....................... 512 <Enter>
11. Go to step (5) in Section 2.7 for continuing system software installation.
57
58
Appendix B
Procedures for Installing ConnectPro
The following window will appear:
Notice: For more information about the ConnectPro configuration, click ’Help’ button in the
window.
1. Enter the HIS Server IP Address.
NOTE: HIS Server IP Address identifies the Internet Address for the worklist information
server.
2. Enter the HIS Server AE Title.
NOTE: HIS Server AE Title is the name of the software that will provide the worklist data.
3. Enter the HIS Server AE Port.
NOTE: HIS Server AE Port is the well known, DICOM defined, port number for the AE Title.
4. Enter the CT Server AE Title.
59
NOTE: CT Server AE Title is used by Schedule Patient to query the Hospital Information System for
Procedure Steps scheduled for [This System].
5. Click ’Accept’ button in the window.

6. Goto step 6 of Section 2.17 for continuing installation.
60
Appendix C
Procedures for installing Dentascan filming
option
1. Open UNIX shell from the toolchest.
2. Type: cd ~ctuser/install <Enter>
3. Type: installcamera.denta <Enter>
4. If there is more than one printer on the system a list of printers is displayed.
Otherwise go to step (6).
Message appears: Enter index of the camera selected and press <Enter>:
5. Enter the index number for the camera: N <Enter>
6. Message appears: Sending a film to the camera.

…
Enter the distance Dist 1 in (mm):
Notice: To determine the value of Dist 1 or Dist 2, measure the distance between the two
vertical lines on the film(s) printed, and enter the value(s) in MILLIMETERS (mm).
7. Enter the measurement of Dist 1: XXX.X <Enter>
8. If Zoom is supported by the type of Camera, the message will appear:

Enter the measurement of Dist 2: YYY.Y <Enter>
9. Message appears: DentaScan filming option installed.
10. Type: exit in the UNIX shell.
11. Go to Section 2.18 for continuing installation.
61
62
Appendix D
Procedures for Installing Add-on Packages
1. Open UNIX shell, become root: su root <Enter>
(then enter the root passwd)
2. Type: installpkg
A software packages window appears:
3. Insert the Software Packages Media into the CD-ROM/MOD drive.

4. Click on the media you are using for installation.
Example screen showing the packages available on sample Packages Media:
63
5. Select the packages to be installed (e.g.: click & drag down to highlight all the
available options, then release).
A box appears while the software packages are loading.
7. After all the packages are installed, select Quit, then OK.
8. Follow the instructions in the release notes for continuing installation.
64
Appendix E
Changing the System Timezone
1. If applications is running, shutdown applications by selecting Utilities -> Shutdown
Applications on the Service Desktop.
2. Open the console window, by double clicking on the console window icon in the
toolbox.
3. On the console window, login as root, type: cd /usr/g/scripts
4. Then type: ./reconfig
5. Select ’Config’ on the Installation title screen

6. On the System Configuration screen, select the Timezone for this site, and record it
below:
Region / Time Zone
7. [Accept] the reconfig

8. Click ’Yes’ to reboot the system.
9. Open a ”Unix Shell” OC window from toolchest, connect to SBC over the serial line:
cu sbc
10. Login as root (then type the root password)
11. On SBC window, type: reconfig
The SBC reconfigs the software and finally reboots
12. Proceed to section 2.10 to setup time on both SBC and OC.
65
66
Appendix F
Installing Laser and DICOM Cameras
Notice: 1) Empty all filming queues before modifying camera parameters.
2) The DASM must be connected to the system and turned on at system startup to
correctly setup the Laser Camera.
For installing new cameras after a load from cold, follow the procedure below.
1. Click on the Service desktop button.

2. On the Desktop Toolbar select Utilities -> Install Camera.
3. The GUI that comes up will show a list of the cameras installed. (figure F-1)
Figure F-1 : Printer configuration GUI:
4. To add a new camera, click the “Add” button.

The dialog window for the camera type (DASM/DICOM) comes up (figure F-2).
67
Figure F-2 : Dialog box for camera type:
If no DASM has been detected during the OC boot, the “DASM” button will be disabled.
(F-3).
Figure F-3:
If the DASM is present and it has not been detected, reboot the OC and start the
camera configuration tool again.
5. To add a new laser camera, click “DASM” in the camera type dialog box.
This brings up a list of camera models. Select the appropriate model from the list
and click “Select”.
Select the camera model from the camera models list the camera model dialog
window (figure F-4).
68
Figure F-4 : Camera model dialog:
69
DASM Interface, will be detected automatically as either Analog or Digital.
Two Options are available with a Laser camera, Slides and Zoom. Set this option only
if the camera being installed supports slides and zoom. Setting the option allows it to be
enabled or disabled at the application level.
Camera manufacturers provide two Magnification type options for cameras. The
Smooth resolution blurs the image, while the Sharp resolution makes the image
”pixelly.” The default is smooth.
Finally, select the Film Formats to use by selecting “On” from the pull-down menu for
the appropriate formats. Valid film formats are determined by the camera manufacturer
(for example IMATION does not support 4x6, 2x4 or 1x2; Agfa does not support 2x4).
Also note that the DICOM print convention is to designate film formats by column x row
(e.g. 12 on 1 film is 3x4).
When finished setting the parameters, click on Done, then proceed to step 5.
70
6. To install a DICOM camera, click on “Add” and click “Dicom” in the dialog box that
appears.
This brings up a list of camera models. (figure F-6). Select the appropriate model
from the list and click “Select”.
This will pre-set all of the other parameters with the exception of the Network
Parameters. It is a good idea to verify the pre-set information as camera models do
change over time.
Notice: Selection of a different camera model will also clear the Image Quality parameters
as these are camera manufacturer dependent.
71
Set up the Network Parameters:

Device Name - A unique name to identify the camera.
Host Name - DICOM Print Server host name as defined by the network.
IP Address - DICOM Print Server IP Address as defined by the network.
AE Title - DICOM Print Server Application Entity Title as defined by the server.
TCP/IP Listen Port - DICOM Print Server TCP/IP Listen Port as defined by the
server.
Comments - (Optional) Comments to be used by the DICOM Print Server.
72
The Destination parameter selects the final location for film output, either Magazine or
Processor.
Orientation selects the film orientation; currently only the Portrait option is supported.
Medium Type selects the type of film to be used, currently only Blue Film or Clear Film
options are supported.
The Magnification Type parameter selects the algorithm used interpolate pixels to
provide the necessary film resolution. This parameter should be set in conjunction with
the camera manufacturer to make the best possible image. The settings are:
None - No interpolation. This option is not supported by all camera vendors
Replicate - Adjacent pixels are interpolated which results in images described as
”pixelly.” This algorithm is not usually preferred
Bilinear - A first order interpolation of pixels is used which results in images
described as blurred. This algorithm is not usually preferred
Cubic - A third order interpolation is used with a large number of possible
formulations. Camera manufacturers define parameters called smoothing type to
set coefficients used in the algorithm. The implementation of these coefficients is
camera manufacturer dependent.
Finally, select the Film Formats to use by selecting “On” from the pull-down menu for
the appropriate formats. Valid film formats are determined by the camera manufacturer
(for example IMATION does not support 4x6, 2x4 or 1x2; Agfa does not support 2x4).
Also note that the DICOM print convention is to designate film formats by column x row
(e.g. 12 on 1 film is 3x4).
After the camera has been configured, click Advanced. This will create the camera
device file and bring up the Advanced Parameters screen.
73
The advanced camera parameters control the image quality of the films and the network
timeouts. For more information on the proper settings for these parameters, please see
the DICOM Print Device Conformance Statement or the camera manufacturer
representative.
Smoothing Type - This parameter is used when the magnification type is CUBIC
and it represents the coefficient for the image resolution algorithm. This parameter
is camera manufacturer dependent (for example, IMATION uses numbers 1-15;
Agfa uses numbers 0, 100-299).
Configuration - This parameter is camera manufacturer dependent and is typically
used to specify the image contrast (for example, IMATION uses LUT=0,7; Agfa sets
PRECEPTION_LUT=140; Kodak has CS300\CN-3\PD2.3).
Notice: The Configuration field may be up to 1024 characters long. The field will scroll
automatically as characters are typed. To review the Configuration field if the entire
length does not appear on screen, click and hold down the left mouse button while
the cursor is in the field, and drag the mouse towards the right (or left as required).
Minimum and Maximum Density - These are used to set the brightness of the
images on the film. The range of values is 0-4095, although the valid range for a
specific camera is manufacturer dependent (for example, IMATION has a maximum
density level of 320).
74
Empty Image Density - This parameter sets the density for empty film viewports.
Typically BLACK is used but WHITE is also an option. The Minimum and Maximum
Density values are used as the representation.
Border Density - This sets the density for the border used around the film
viewports. Typically BLACK is used but WHITE is also an option. The Minimum and
Maximum Density values are used as the representation.
Click on Done, when finished setting up the Advanced Parameters.
75
Appendix G
Installation of Network Printer
1. Open a Unix Shell.
2. Login as root ( By doing 'su - root' and subsequently entering Password).
NOTE: To become root, you should use ‘su –‘ and not simply ‘su’. Otherwise, you will not
have proper permissions to install network printer.
3. Ping printer's ip address' (This is done to check if the printer is available on the
Network).
4. If ping fails, do not proceed. The printer will not be installed.
5. Run reconfig.
When you do reconfig, in Hardware Settings Screen,
(a) Select Network Image Printer.
(b) Enter the Name and IP Address of the Network Image Printer.
NOTE: A “PRINT SERVER” is NOT SUPPORTED ( ie: a computer with a printer attached).
Network Image Printer ( which is supported) is a printer directly attached to the
network.
6. Then, continue the reconfig. After completing reconfig on OC, do reconfig on SBC.
76
Chapter 2
SW Version 4.5 Patch Procedure
Section 1
Installation of the 4.5 Patch
1. Bring CT Applications s down: Service -> Utilities -> Application Shutdown

2. Become root by typing: su - within a shell window
3. Insert the 4.5 CD-ROM
4. Type the following at the system prompt:
mountCD /mnt
/mnt/install4.5patch
5. After the patch has finished loading, type: unmountCD and remove the CD-ROM.
6. Perform the following checks, to verify the patch has been loaded correctly.
a. Using the showprods command, type the following:
showprods | grep Rhapsode_patch_45
b. Verify that following text is displayed

I Rhapsode_patch_45 06/01/2001 Rhapsode Patch 4.5.3 ver 1
I Rhapsode_patch_45.img 06/01/2001 Patch files on the Operator Console
I Rhapsode_patch_45.img.fixes 06/01/2001 Quality fixes for CT/i ver 4.4.19.1
I Rhapsode_patch_45.img.sdc_patch 06/01/2001 IOS fixes for CT/i 4.4.19.1
c. Using the showprods command, type the following:

Showprods | grep patchGESG0004050
d. Verify that following text is displayed

I patchGESG0004050 06/01/2001 Security patch
I patchGESG0004050.sw 06/01/2001 Software
I patchGESG0004050.sw.base 06/01/2001 Base Software
7. Restart applications.
77
Section 2
De-installation of 4.5 SW Patch
1. Bring CT Applications s down using the Service Desktop

Service -> Utilities -> Application Shutdown
2. Become root by typing: su – (within a shell window)
3. Within a shell window as root, type: /usr/g/scripts/uninstall4.5patch
78
Chapter 3 `
Turbo LFC Procedure (Releases 6.1 & 6.3)
PROCEDURE:
Archive Patient • Ensure all patient images are archived
Images
• Save System State Data

Load From Cold
• Record Key System Information
Procedure
• Shutdown the System
• Boot Standalone IRIX Disk Partitioning Utility
• Install System Software OS on Operator Console
• Install System Software on the SBC
• Install CT/I Software on the OC and SBC
• Set Date and Time on the OC and SBC
• Start up CT Applications
• Restore System State
• Install Security Patch (Version 6.3 only)
• Add Software Options
System
Checkout • Save System State
79
Section 1
Introduction
This document describes the procedure to load software Versions 6.1 and 6.3 on a
HiSpeed Advantage Turbo System from CD-ROM media.
The following typographical conventions are used in this document:
• Commands typed in by the user and output from the computer system is shown in
bold, Courier New font, for example: login
• Distinctions between the various modes of load (IRIX versions, network vs. local
loads) and important messages are shown in bold print, for example: Save
• Entry characters of one, lower-case-L, zero, & upper-case-O appear different (listed
respectively), for example: 1, l, 0, O
• The ”Enter” key (otherwise known as the ”Return” key) is indicated by <Enter>
1.1 Appendix List:

Appendix A
Procedures for Creating Default Partitions:
Appendix B
Procedures for Installing ConnectPro
Appendix C
Procedures for installing Dentascan filming option
Appendix D
Procedures for Installing Add-on Packages
Appendix E
Appendix F
Appendix G
Installation of Network Printer
1.2 Software Load From Cold (LFC) Overview

The procedure involves preparing system disks, installing and configuring the system
software on both the OC and SBC computers.
Notice: Make sure that all Images have been reconstructed and archived before performing this
procedure. This procedure will re-initialize all system data disk, and erase all images
and scan data.
80
Section 2
Load From Cold Procedure
2.1 Before You Begin
2.1.1 Collect the Necessary CD-ROM Media

You should have the following CD-ROMs to load Software.
• IRIX 6.5.4M UPDATE CD-ROM
• IRIX 6.5 Pa CD-ROM
• IRIX 6.5 Pb CD-ROM
• HiSpeed CT/i Application Software (Base) CD-ROM
• Security Patch CD-ROM (Version 6.3 only)
2.1.2 Verify CD-ROM Drive Compatibility

If the CD-ROM’s firmware revision is 1037 and the drive is a Toshiba XM6201TA model,
software will not load. The drive should be replaced prior to attempting the LFC.
To check the firmware revision of the drive, perform the following check.
1. Open a UNIX Shell
2. Type: scsistat <ENTER>
3. Inspect the last column within the row that lists the CD-ROM.
Device 0 1 Disk SGI IBM DDRS-34560W FW Rev: S96A
Device 1 3 Optical Maxoptix T5-2600 FW Rev: A6.5
Device 1 4 Comm CenData ST-1400A FW Rev: V5.7
Device 1 6 CD-ROM TOSHIBA CD-ROM XM-6201TA FW Rev: 1030
The firmware revision is 1030.
2.1.3 Verify CD-ROM Drive Operation

It's recommended that you test the CD-ROM drive before you begin the LFC procedure.
You are ask that you insert and mount one (1) of the OS CDROM disks and perform a
checksum (read check) of the files in one of the directories.
If any errors should occur while reading the CDROM, it must be fixed before proceeding.
1. Open a UNIX shell.

2. Type:
tail -f /usr/adm/SYSLOG <ENTER>
3. Open a second UNIX shell.
81
4. Insert the IRIX 6.5 Pa CD-ROM (2276660) into the CDROM Drive and type:
mountCD /mnt <ENTER>
cd /mnt/dist <ENTER>
sum * > /tmp/CDROMtest <ENTER> (~5 minutes to display prompt)
5. While the system is reading the CDROM and calculating checksums, you need to
monitor the SYSLOG. Look in the first UNIX shell window for any error messages
that may occur that are related to SCSI or CDROM problems (timeouts, read errors,
SCSI Bus resets, etc.).
6. If checks are successful (no errors produced), type the following command to verify
the checksum:
sum /tmp/CDROMtest <ENTER>
7. Verify that the resultant display for the command in step 6 is:
26501 5 /tmp/CDROMtest
8. If you encounter any CDROM or SCSI related errors during this check, stop and
troubleshoot/ repair the problem before attempting to perform the FMI.
9. Terminate the ’tail’ command by typing ^C in the first UNIX shell window where
the ’tail’ command is running.
10. Un-mount the CDROM by typing the following commands in the second UNIX shell
window:
cd / <ENTER>
unmountCD <ENTER>
2.1.4 Record the Version of kVBoard Currently Installed
NOTE: This must be done before you Save System state
To ensure that you know what KVBoard is installed in your system, follow the procedure
listed below. This information will be needed later in Sec 2.8 – 7 (g).
1. Bring the system up and start the applications.

2. Open a Unix shell.
3. Login to the SBC side (Type: rlogin sbc)
4. Become root (Type: su root)
5. Type: nbsClient obcr
You should now see the following prompt:
[NBS, OBCR]: [NBS, OBCR]:
6. Type: y <Enter>
7. Some hardware information will come up - look for the line " =====| KV Board
Revision: "
The KVBoard information will be displayed.
8. Note it down, exit the program, proceed with system state save, and then with
reconfig/LFW/LFC.
82
9. Type: ~. ( tilda dot ) to quit.
2.2 Save System State Data and BMD Database (if applicable)
2.2.1 Save System State Data

Before beginning the software install, you will want to, save the system configuration
information, characterization, calibration, protocols, etc.
NOTE: If you are upgrading from a pre-release of Smartview software, prior to saving the
system state edit the dprint.cfg and dprint.cfg.def files (if they exist). These files are
found in the /usr/g/ctuser/app-defaults/print directory.
Remove the line: bi_implem_uid = “1.2.840.113619.6.2”
Change the line: in_abort_tio To read: in_abort_tio = 10
1. Bring the system up if it is not already up.

2. Click on the Service desktop.
3. Click on PM.
5. Click on the ”Start ...” button.
6. Click on ”All” (which will highlight Cals, Characterization, Reconfig Info, etc).
7. Click on Save.
8. A dialog box titled ’Save System State’ will pop up with the following message
Select NO to exit without Saving.
Click on YES.
(The save will take a few minutes)
Review the output for errors or missing files; the scroll bar on the right works only
If you see any missing files or failures, then refer to the notice below.
Proceed to step 9 when the message window shows that Save system state was
completed and MOD released. The system will prompt with the following message in
the System State Message Log window:
Calibration Database: COMPLETE
Releasing MOD...
MOD Release completed with success.
9. Click on Dismiss.
83
NOTE: SAVE/RESTORE SYSTEM STATE ERRORS

If System State reported no problems, then you may skip to section 2.3.
Save/Restore System State reports status on each file specification listed in the
/usr/g/config/SysState.cfg file. The status may be:
• Save (or Restore) of {filename} succeeded
• Save (or Restore) of {filename} skipped. File not found
• FAILED
A status of ”FAILED”, indicates potential problems, ”skipped” means the file not
found was not required. Please review the following for each file you see an error
reported.
--------------------------------------------------------------------
If the site does not have InSite, you may see the following:
Save (or Restore) of insiteINFO skipped. File not found

Save (or Restore) of sclink.cfg skipped. File not found
Save (or Restore) of bg_schedule_data skipped. File not found
Save (or Restore) of intrusive_schedule_data skipped. File not found
Save (or Restore) of timeslot_data skipped. File not found
...
Save/Restore System State : Completed Successfully
For a site without InSite these will be seen and this should not be regarded as a
problem. A site with InSite should not get these errors; else you will need to reload
InSite or re-enter the ProDiags schedule later.
In case of a restore system state, the system may report
Chmod of sclink.cfg failed.
This is because during restore, the file is not found (Save skips the file if InSite is not
installed on the system).
Some files simply may not exist on the system. If certain tools were never run then
certain files may never get created. You may view
/usr/g/config/SysState.cfg and look for a req field. req=Y means the file in
question is required. You may also wish to check the system and MOD to verify
whether is was actually missing or if there were permission or owner problems with
the file.
2.2.2 Handy commands:

mountMOD (mount the MOD on the /MOD dir)
ls -l /MOD/service_mod_data/system_state(or /MOD/serv*/sys*)
find /MOD -name ’*abc*’ -print (locates any file with ’abc’ in it)
cd; unmountMOD (must cd out of MOD dirs to unmount it)
more /usr/g/config/SysState.cfg(view the locations of System State files)
su - (password) man 1 chmod chown (access man pages as root)
rsh sbc (access the SBC)
--------------------------------------------------------------------
84
NOTE: For the 5.3 to 6.1 upgrades, you must record the current collimator’s
characterization values so you can properly re-enter these values toward the
end of the load. Values are not automatically restored. They must be
entered manually toward the end of the load. Version 6.1 software is
compatible with and provides support for the G5 collimators. In the Service
Desktop, select Replacement Procedures -> Collimator Change ->
Mechanical Characterization -> Collimator Data, and record the values (i.e.:
Closed, 1mm, 3mm, 5mm, 7mm, 10mm and CRC). These values are used
for creating the new collimator characterization file in Section 2.14 (Values
can also be found in System Integration -> Characterization -> Collimator, if
the service key is not available.)
Collimator Data
Closed:
1mm:
3mm:
5mm:
7mm:
10mm:
CRC:
NOTE: For the 5.3 to 6.1 upgrade, in ImageWorks, select an image, click Viewer ->
User Prefs. Select modality CT and record the values of Title, w/width and
w/level for all entries. These values are used for restoring the user
preferences file in Section 2.14. If there are no images in the database, the
user can create a SMPTE image by selecting TroubleShoot -> Display
Processing -> Install SMPTE image in the Service Desktop.
User Preferences
Title: w/width: w/level:
85
2.2.3 For a [5.3] to [6.1] Upgrade
SAVE REFORMAT PROTOCOLS

Insert or keep the proper system state save/restore MOD to the MOD drive.
1. mountMOD
2. cd /MOD
3. Check if the directory service_mod_data/system_state exists. If not:

mkdir service_mod_data/system_state
4. Check whether some reformat protocols are saved in the system, by typing
ls –l /usr/g/ctuser/Prefs/VoxtoolPrefs/*
5. If some protocols are present then proceed further:
cp /usr/g/ctuser/Prefs/VoxtoolPrefs/*.flm /MOD/service_mod_data/system_state/
This will save all the reformat protocols available in the system onto the MOD
Make sure you have copied all protocols to the MOD by typing the command:
6. ls -l /MOD/service_mod_data/system_state/*
7. cd (this is to ensure that the next command is not run from /MOD)
8. unmountMOD
NOTE: The above ‘save’ method enables the Reformat protocols to be restored via the
normal ‘restore system state’ procedure after the applications have been installed.
SAVE CONNECTPRO INFORMATION
1. If you have the ConnectPro option, run ‘installhisris’

2. Record the four data, which will be required in Appendix B when you reinstall the
ConnectPro option.
3. Then ‘CANCEL’
2.2.4 Backup BMD Database (only if BMD option is installed to the system)
1. Insert a MOD to the MOD drive for saving BMD database.

4. Click on the ’Backup to Archive Disk’ on the BMD Database Archive toolbar.
5. Click on the ’OK’ button to proceed the backup
86
NOTE: If the current MOD in the drive is uninitialized, click on ’OK’ button to make a file
system on the MOD.
2.3 Record Information In Case Your System State MOD is Lost/Damaged

This information is all saved on the System State MOD, but to be safe it should also be
recorded somewhere on your site in case the State MOD is lost or damaged. This step
is optional, especially if you have already recorded this information somewhere else.
1. Record the most important Reconfig INFO for the scanner.

The following procedure will gather all this info for you from the INFO file.
(a) open or go to a unix shell on the OC
(b) View the INFO file created by reconfig; type:
more /usr/g/config/INFO <Enter>
(c) For each of the fields below look at the ”more file output” to find the associated
”setenv” value and record the value in the table provided.
NOTE: IP Addresses and Net/Broadcast Masks have the format www.xxx.yyy.zzz

When recording the NEXT_PATIENT_EXAM_NUMBER, confirm that this number is
the most current value by looking at the lsat exam scanned from the Browser. If the
Browser shows a value higher than the INFO file, use the value from the browser.
System Configuration
Field Name: ”setenv” Name: Field Value:
System Service ID SERVICE_ID
Settings:
Hospital Name HOSPITAL_NAME
Exam Number NEXT_PATIENT_EXAM_NUMBER

DAS Type DASTYPE
PDU Type PDUTYPE
Network Gateway Host Name GATEWAY_HOSTNAME
Settings:
Gateway IP Address GATEWAY_IP
Gateway Net Mask GATEWAY_NETMASK
Gateway Broadcast Mask GATEWAY_BROADCAST
Suite Name SUITEID
87
Record the Networking Static Routing information (only if Static Routing is used)
If you know that this site uses Static Routing, record the data requested in this
procedure, because it is not automatically saved and restored during a Load–From–
Cold.
Otherwise, if you are not sure, perform the following steps to determine if Static Routing
is being used at this site:
(a) Open a UNIX shell.
(b) Type: chkconfig | grep routed [Enter]
(c) Look for the line that contains the following:
routed on/off <– Note that the route daemon will be either on or off.
Record the setting.
(d) Examine the following file to see if Static Routes are set up, and if they are, record
the following information from the following file:
Type: more /etc/config/static–route.options [Enter]
At the end of this file, there will be entries similar to the following if Static Routes are
set up:
$ROUTE$QUIET add default 3.7.53.3
or $ROUTE$QUIET add 192.168.1.1 192.0.2.5
or $ROUTE$QUIET add –net 10 192.0.2.3
NOTE: Ignore all lines that start with ”#” (comment lines), but record any Static Route
entries in the following table:
Static Route Information
$ROUTE$QUIET entry
$ROUTE$QUIET entry
$ROUTE$QUIET entry
$ROUTE$QUIET entry
Route daemon setting (routed on/off) ON / OFF
88
2. Record the Networking Application (Image transfer) Configuration

On the ImageWorks Desktop, in the Browser under Network, for each host
configured for networking do the following and record the information in the table
provided:
(a) Click on Select Remote Host
(b) Click on the Hostname
(c) Click on Update
(d) Write the information in the table provided
(e) Click on Cancel to exit Select Remote Host
If you find this process tedious, you can look at file

/usr/g/ctuser/Prefs/SdCRHosts on the system to get this information. The 1
in the file means Advantage Net, the 2 means DICOM. The pound sign in the file is
a separator and means nothing.
Networking Application (Image Transfer) Configuration

Host Network Network Port AE Title
name address protocol number
Archive Send Query/Retrieve* Custom Comments*

Node* Images* Search*
* Some systems may not have these categories.
89
3. Record the Camera Application Configuration

If you are currently on a Smartview system:
(a) Click on the Service Desktop button
(b) Click on Utilities
(c) Click on Install Camera
(d) Write the information in the tables provided
(e) For a Laser Camera configuration click on Cancel to exit
(f) For a DICOM print configuration click on Accept to continue with the Image
Quality and Network Timeout parameters
If you find this tedious, for Laser cameras you can look at the file
/usr/g/ctuser/app-defaults/devices/camera.dev on the system to get
this information, or for DICOM print cameras you can look at the files
/usr/g/ctuser/Prefs/SdCPHosts and
/usr/g/ctuser/app-defaults/print/dprint.cfg for this information.
If you are not on a Smartview system, look at the file /usr/g/ctuser/app-
defaults/devices/camera.dev on the system to get the information for Laser
cameras.
Laser Camera Configuration
Camera Type:
DASM Type:
Film Type:
Options:
Valid Film Formats:
90
DICOM Camera Configuration

Camera Type:
IP Address:
Host Name:
AE Title:
TCP/IP Listen Port:
Comments (optional):
Destination:
Orientation:
Medium Type:
Magnification:
Valid Film Formats:
DICOM Camera Advanced Configuration

Smoothing Type:
Configuration:
Minimum Density:
Maximum Density:
Border Density:
Empty Density:
Association Timeout:
Session:
N-Create:
N-Set:
N-Get:
N-Delete:
N-Action:
Notice: Make sure that all Images have been reconstructed and archived before performing
this procedure. This procedure will re-initialize all system data disk, erasing all
images and scan data.
91
2.4 Shutdown the System

Click on the (square red) Shutdown button (shown below). Press OK to shutdown
Applications. This will take down both CT/i Applications and UNIX and put you at the
boot prompt.
2.5 Boot Standalone IRIX Disk Partitioning Utility

1. Insert the IRIX 6.5 Pa CD into the drive.
2. A message should be on the screen that says ”ok to power off the system now”.
The next step requires two selections in quick succession (you may only have three
seconds between selections); please read carefully before proceeding:
You will first be selecting ”Restart”, to bring up the system. A message may appear
about running power up diagnostics. Then a window will come up about starting up
the system. There will be a small button in the right hand corner: ”Stop for
Maintenance”. You will use the mouse to quickly press this button.
You should now select Restart and Stop for Maintenance.
3. A screen will pop up with several icons:
• Start System
• Install System Software
• Run Diagnostics
• Recover System
• Enter Command Monitor
• Select Keyboard Layout
2.6 If you have a keyboard other than a US-English Keyboard.

1. Use the mouse and click on Select Keyboard Layout.
2. Select the appropriate keyboard type. Supported keyboards are:
• English - US (default)
• German - DE
• Swedish - SE
• French - FR
3. Select Apply to reconfigure.
92
2.7 Install System Software (Irix OS)

NOTE: You need to follow the procedures for creating default partitions in Appendix A. IF AND
ONLY IF you have a new disk, just formatted it or the disk is corrupted. Otherwise, go to
step 1.
1. Click on Install System Software.
NOTE: Make sure that the IRIX 6.5 Pa CD is in the CDROM drive, and the CDROM drive is
not busy before proceeding to step(2).
2. Click on Local CD-ROM.

3. Click on Install to proceed installation
A Message will appear:
Insert the installation CD-ROM now
Message appears:
Obtaining installation tools
Another message appears:

Copying installation tools to disk
Screen goes blank.

Message:
Creating miniroot devices, please wait ...
93
NOTE: If message ”Unable to continue; press <Enter> to return to the menu” appears on
d) Proceed to step (3) in section 2.5.
If message ”make new file system on /dev/dsk/dks0d1s0[yes/no/sh/help"

a) Type: yes <Enter>
b) Are you sure ?[y/n](n) Type: yes <Enter
c) Blocksize Of filesystem 512 or 4096 bytes ?” Type: 512 <Enter>
If message ”Unable to mount partition /dev/dsk/dks0d1s0”; Press <Enter> to go to

csh and, do the following:
a) Press <Enter>, in the shell, type: mkfs /dev/dsk/dks0d1s0
b) Type: exit, and proceed to the next step
5. You will see the install menu appear as follows:

For help on inst commands, type ”help overview”.
Inst Main Menu
1. from [source] Specify location of .
2. open [source] Specify additional ..
3. close [source] Close distributions
4. list [keywords] [names] Display information .
11. help [topic] Get help in general .
inst>
6. Replace the IRIX 6.5 Pa CDROM in the drive with the IRIX6.5 4M Update CDROM.
Ensure the CDROM drive is not busy before proceeding to the next step.
NOTE: Make sure that the IRIX 6.5.4M Update CD (Disk #4M) is in the CDROM drive.
7. From Inst menu enter the shell environment:

Type: 13 <Enter>
Type: sh <Enter>
Ignore the message: “Can’t open /etc/sys_id”
94
(a) Type: mount /CDROM <Enter>

Type sed 's/4926/5000/' /CDROM/scripts/install.cti > /bin/install.cti <Enter>
(b) Type: chmod +x /bin/install.cti <Enter>
Type /bin/install.cti <Enter>
Messages appear. Several pages. For example:
Starting automatic disk partition script.
Ensuring the unnecessary partitions are unmounted.
Copying Miniroot Image to the new partition location.
It may take a few minutes
Copying contents of UPDATE CDROM to working directory...
[After approx. 5-10 minutes, you will see the message: ]
Eject the UPDATE Disk

Please insert the First OS Disk(Pa), then press <enter>
(c) Replace the IRIX 6.5.4M UPDATE CDROM in the drive with the IRIX6.5 Pa
CDROM and press <enter>.
Message appears:
Copying packages from the first OS Disk(Pa) to working
directory...
[ After approx. 5-10 minutes, you will see the message: ]
Eject the First OS Disk
Please insert the Second OS Disk(Pb), then press <enter>
(d) Replace the IRIX 6.5 Pa CDROM in the drive with the IRIX6.5 Pb CDROM
and press <enter>
Message appears:
Copying packages from the Second OS Disk(Pb) to working
directory...
The packages form the last OS disk will be copied and the
installation process will continue. This process will
take approximately 30-40 minutes and no user input is
required.
After the OS installation is complete the user will be
instructed to type in the following commands to complete
the IRIX OS(OC) install.
*********** Done installing the OC System **********
(e) When installation is complete:

Type:'exit' to exit back into the original Inst session
Type: 'exit' again, to exit back into the original Inst session.
Type:'quit' at the Inst> prompt, restart the system.
Type:'yes ' when you are prompted to restart the system...
(f) Remove the IRIX 6.5 Pb CDROM from the drive.
95
The system will go blank and restart the OC Operating system and automatically
log you into the system as the root user.
2.8 Install CT/i Software On The OC

1. Open a ”Unix Shell” window by using the ”Desktop” pull down menu.
2. Insert the applications CDROM. Wait until the CDROM is not busy.
Type: install.ct <Enter>
Note: If you are using TEAC CD-ROM drive, when you execute the commands ( eg:
install.ct) for the first time, it may FAIL and pop up error message saying CD-ROM
type may not function correctly. This is normal. Just execute the command again.It
will function properly.
If message ”/mnt/install - no such file or directory” appears, do the
following:
a) Type: umount /mnt <Enter>
b) Eject the CDROM media from the CDROM drive.
c) Re-insert the CDROM media into the CDROM drive.
d) Proceed to step (2) in this section.
The following window will appear.
Load Config
3. In the HiSpeed CT/i Install Utility window click on Load.

4. A pop up message will query if you wish to load the INFO file from the System State
MOD. If you have a System State MOD, select ”Yes”. Another pop-up message will
appear and you should place the System State MOD in the drive and select OK.
96
In the following steps, you will now go through each of the Reconfig screens and
verify the information. You may make updates as needed. If you did not have a
System State MOD, you will need to enter the appropriate information (refer to the
data you recorded in section 2.3).
5. System Settings Screen:
(a) Change Hospital Name to the site’s preferred name.

(b) Enter the Service ID issued by the service organization. The
GENNET_ServiceID default must be replaced by a valid service ID.
(c) Select the Timezone for this site, and record it below.
Region / Time Zone
NOTE: If the time zone of your location is not in the selection menu, select one of the
universal times. In this case, automatic changes for daylight-saving time will not
take effect.
(d) Verify/change Next Patient Exam # (it should be 1 larger than the ”last exam
number” recorded earlier).
97
(e) Select Preferences to proceed to the next screen.
Notice: The Next MOD#, & Next Diagnostic Exam # are currently not implemented.
6. Preferences Setup Screen.
NOTE: Options Doctor’s Title and Units for patient weight are not currently
implemented.
(a) Select English as the Language for installation.
NOTE: English must be used for installation due to a tools problem if installed in another
language. The other language will be set up later in this procedure.
For the 5.3 to 6.1 upgrades, as the INFO file is being read from MOD, it has the
old language value and no language is being selected on the screen. Make sure
you have selected English on the screen.
98
NOTE: If message ”Unable to continue; press <Enter> to return to the menu” appears on
d) Proceed to step (3) in section 2.5.
If message ”make new file system on /dev/dsk/dks0d1s0[yes/no/sh/help"

a) Type: yes <Enter>
b) Are you sure ?[y/n](n) Type: yes <Enter
c) Blocksize Of filesystem 512 or 4096 bytes ?” Type: 512 <Enter>
If message ”Unable to mount partition /dev/dsk/dks0d1s0”; Press <Enter> to go to

csh and, do the following:
a) Press <Enter>, in the shell, type: mkfs /dev/dsk/dks0d1s0
b) Type: exit, and proceed to the next step
5. You will see the install menu appear as follows:

For help on inst commands, type ”help overview”.
Inst Main Menu
1. from [source] Specify location of .
2. open [source] Specify additional ..
3. close [source] Close distributions
4. list [keywords] [names] Display information .
11. help [topic] Get help in general .
inst>
6. Replace the IRIX 6.5 Pa CDROM in the drive with the IRIX6.5 4M Update CDROM.
Ensure the CDROM drive is not busy before proceeding to the next step.
NOTE: Make sure that the IRIX 6.5.4M Update CD is in the CDROM drive.
7. From Inst menu enter the shell environment:
Type: 13 <Enter
Type: sh <Enter>
Ignore the message: “Can’t open /etc/sys_id”
94
(a) Select the DAS Type for this system.
NOTE: New systems have an HP DAS. Upgraded systems may have either HP DAS or
Rev G4 EDAS.
(b) Select the Tube Type for the system.

(c) Select the PDU Type for the system.
NOTE: If the PDU Type of the system is not in the PDU Type selection, select HSA
(46F-296220G1) / (46-327106G1).
(d) Select the desired Collimator/Filter Type.
NOTE: The G4 and G5 Collimators/Filters support the Smart Beam Option. If you
check the G1,G2,G3 box, Smart Beam will be disabled by the Scan user
interface.
(e) If you have a Network Image Printer, select it. Next enter it’s Name and IP
Address.
NOTE: A ”PRINT SERVER” IS NOT SUPPORTED (ie: a computer with a printer

attached); a Network Image Printer (which is supported) is a printer directly
attached to the network.
(f) Camera Setup.
NOTE: Cameras will be installed later in the load through the Utilities menu in the
Service Desktop.
(g) KVBoard Selection.

If you have found out the kVBoard Type from sec 2.2.1, select that generation of
kVBoard type.
If you don’t know the kVBoard type, open the gantry and check the type printed
on the installed kVBoard.
(h) Select Network to proceed to the next screen.
100
8. Network Settings Screen:
OC SBC
Networking Notes are on the next page.

Refer to the data you recorded in section 2.3 to verify these entries.
(a) Host Name identifies the name of this scanner. This name must be unique for
the site, and will appear in UNIX prompts and in a few other places. If you set up
a network connection to the site, the OC computer will appear on the site’s
network as <Host Name>.
(b) Suite Name must start with a letter followed by 3 alphanumeric characters (ie: it
MUST be 4 characters long). The name of the Bit-3 OC interface will be <Suite
Name>_OC0 and the Bit-3 SBC interface will be <Suite Name>_SBC0.
101
If the CT/i scanner is not connected to a ”Site Subnet”, then:

• Verify all other fields are set to the defaults listed in the diagram above. The fields of
Host Name and Suite Name are set to ct01 and CT01 respectively; if you change the
Gateway IP Address and have InSite, you must notify the OnLine Center.
• You should now skip to the step titled ***READY TO INITIATE INSTALLATION*** on
the next page.
Networking Notes:
The CT/i scanner’s OC computer and SBC computer form the scanner’s subnet. The
Bit3 VME to VME connection is the wire connecting the computers in the subnet. Due
to the nature of the VME to VME direct connection, no other computers can be added to
the scanner’s subnet.
The Ethernet connection on the OC can connect the scanner’s subnet to the site’s
subnet via a standard Ethernet TCP/IP connection. If the OC’s Ethernet connection is
used, then this Ethernet port is said to be the gateway connecting the scanner’s subnet
to the site’s subnet.
If the system you are installing is replacing a Genesis-based HLA or HSA scanner, you
can reuse the networking information from the old scanner as follows:
HLA/HSA Suite Id ---> CT/i Suite Name
HLA/HSA Suite Id ---> CT/i Host Name
HLA/HSA 2nd Ethernet Gateway IP Address ->CT/i Gateway IP Addr.
HLA/HSA 2nd Ethernet Gateway Netmask --->CT/i Gateway Netmask
(c) The OC and SBC IP Address & Net Mask should always be set to the defaults
listed in the diagram on the previous page.
NOTE: Due to a limitation of the Bit-3 Networking software, the Netmask for the OC and
SBC subnet is always 255.255.255.0.
(d) Advanced Options
The Advanced networking options provide support for NIS.
Do not turn on NIS unless requested by the site’s network administrator. Selecting
the Use NIS? option allows the scanner to use the site’s NIS (a.k.a. Yellow Pages)
database. The Domain Name must be provided by the site’s network administrator.
When you turn on NIS, you should enter the domain name and router ip address
without fail. Error message will pop up, when you select NIS on and leave these 2
fields blank.
102
Network Settings Screen when NIS is turned “on”
***READY TO INITIATE INSTALLATION***
9. Disable the route daemon.

typing: su root <Enter> (then enter the root password).
At the operating system prompt type: chkconfig routed off <Enter>
10. Enable a static default route (Only if applicable).
Do not do this step unless confirmed by the site’s network administrator. The
default router IP address must be provided by the site’s network administrator.
11. Open a “Unix Shell” OC window from the Toolchest and become root by typing:
su root <Enter> (then enter the root password).
12. At the operating system prompt type:

echo '$ROUTE $QUIET add default <IP address of the default
router>' >> /etc/config/static-route.options
For example: echo '$ROUTE \$QUIET add default 3.7.52.252' >>
/etc/config/static-route.options
103
13. Exit the root session by typing: exit <Enter>

14. Select Accept to utilize the configuration and continue installation.
15. The system will load the CT/i software, OS patches, kernel changes and configure
the system.
This will take about 25 minutes.
While the load is going on, the results will be displayed in a shell window (which
closes when the load is complete). All the window output is logged to a file named
”/var/adm/install.log.YYYYMMDDWWWHHMMSS” (where
YYYYMMDDWWWHHMMSS is the Date/Time that the process was started).
16. The system will then prompt you to reboot.
Click on YES.
18. Open a unix shell from the tool chest.
NOTE: This is to prepare the OC for network booting the SBC.
19. Login as root and type:

loadSBC <Enter>
<Enter> again after messages.
NOTE: If the CD-ROM is TEAC and the command fails, repeat the commands
This will take about 5 minutes.
104
2.9 Install CT/i Software On The SBC

1. Connect to SBC over the serial line using cu. In a shell window on the OC type:
cu sbc <Enter>
(If you do not get a prompt, press ”Enter” a couple times.)
NOTE: If this doesn’t work, try sending a break signal ~%b (ie: tilde percent b).
2. If there is not a MC68040> prompt,
3. Login as root and type: halt <Enter>
4. At the MC68040> prompt Type: b vd() <Enter>

The system will then boot over the network. After about 2 minutes you should get a
login prompt.
5. Login as root. (No password is required): root <Enter>
6. Type: ctloadSBC <Enter>

The following menu appears:
Choose your option for auto partition & label...
1 - Label ’sd0 and sd2’ - then continue loading system
2 - Label ’sd0’ only - then continue loading system
3 - Do not relabel disk, just continue loading system
4 - Exit to user shell
At the menu enter: 1 <Enter>
The SBC loads all of its software, configures itself and finally reboots.
This takes about 20 - 30 minutes.
NOTE: During software load, if error message ”UX:dd: ERROR: Cannot open
/CDROM/sbc_files/hlfc/xx: No such file or directory” appears on
a) Wait for the boot prompt: ”Boot: ”
b) Sending a break signal by typing: ~%b (ie: tilde percent b).
c) Eject the CD from the CDROM drive and re-insert it into the drive.
d) Proceed to step (3) in this section.
7. Login as root (and enter the root password): root <Enter>
8. Type: updateSBC <Enter>

The following mesages appear:
Updating exports and fstab files
Mounting /data
Done!
9. Type: exit <Enter>
105
10. Remove the CD from the drive.

11. To Exit the cu session type: ~. <Enter>
i.e.: to exit the cu session press the following keys : <tilde><dot> <Enter>
2.10 Setup time on the SBC and the OC

*** YOU MUST DO THIS ***
NOTE: Setting the Timezone correctly on the SBC is important to the OC; if not correct, the
plot function in Smart Prep may not work.
1. Open a ”Unix Shell” OC window from toolchest, become root: su root <Enter>
2. Type: setdate mmddhhmmyy
Where, mm is the month (01-12), dd is the day (01-31), hh is the hour (00-23), mm
is the minute (00-59), and yy is the year (96-99, 2000-2030)
Verify the dates and times on the OC and the SBC are the same.
NOTE: If the dates or times are not the same, re-try step (1) to (2) in this section, and re-
verify the dates and times. If the dates or times are still not the same, proceed to
Appendix E for changing the timezone to one of the universal times. In this case
automatic changes for daylight-saving time will not take effect.
3. To Exit the root session on the OC window, type: exit <Enter>.

Then type: exit <Enter> again to close this window.
2.11 Configure Touch

The following steps will setup the display for touch. If you do not have a touch monitor
skip to the next section - Start up CT applications.
1. In a ”Unix Shell” window, become root:su root <Enter>
2. (then enter the root password)
3. Type: cd /usr/g/xtouch <Enter>
4. Type: ./setup <Enter>
5. The ”Serial Device Name” field should contain: /dev/ttya2
6. Click on software calibrate.
NOTE: In the next two steps, be sure to carefully touch the indicated corners of the monitor.
If you do not, you will later find the cursor does not correctly land at a touched
location on the monitor -- you will then need to re-run this touch procedure.
7. Touch on lower left corner.

8. Touch on upper right corner
9. Click on save settings.
106
NOTE: This setup program will dump core if you are not running it as root; if this occurs,
simply re-execute the procedure.
10. Click on exit.
NOTE: ’xtouch’ will not take effect until the next time ctuser logs in or system reboot.
11. Logout root session by typing: exit <Enter>
12. Close the unix shell window by typing: exit <Enter>
2.12 Start up CT applications

Start up system by opening a unix shell window and type ’startup’
NOTE: An error message will be displayed in the message window that says: ”Failed to
initialized with current tube usage file. Will not record tube
usage.” Please ignore this error message because the system state has not been
restored.
2.13 Restore System State

The following procedure restores Characterization Data, Calibration Data, Protocols,
etc., from your System State MOD. If you don’t have a System State MOD, skip this
section.
NOTE: Image Works should not be displaying any images when you restore System State (to
ensure preferences are restored correctly). If you were in Images Works earlier, you
should go back and exit to the Browser.
1. Insert Save System State MOD in to MOD drive

2. Click the button for the Service desktop
3. If the Service Key is installed, the user has to press the (1), (2), (3) keys in order to
proceed.
4. Press the PM option from the list
5. Highlight System State

6. Press the Start button
7. Click on All, which will highlight the cals, characterization, etc.
8. Press Restore (it will deselect ”Reconfig Info”);

9. A dialog box titled ’Restore System State’ will pop up with the following
message
Select NO to exit without restoring.
107
Click on YES.
The restore takes a few minutes.
Review the output for errors or missing files. The scroll bar on the right works only
If you see any errors, review the ”Notice” in section 2.2 and the one
immediately following step 9 below.
Proceed to step 10 when the System State Message Log window shows displays the
following messages:
Releasing MOD ...
MOD release completed with success.
10. Once the restore is complete, respond Yes to the ”Reset Hardware?” prompt; this
takes a couple minutes; (note that the System State Reset Box may be partially
covered by the System State Message Log). When complete, select Dismiss.
NOTE: If the prompt does not appear then select the following:
a) System Resets.
b) Scan.
c) Run.
d) Upon completion, Exit via the File pull down.
11. Remove the System State MOD
NOTE: RESTORE SYSTEM STATE ERRORS AND WORKAROUND
=> For the 3.5 to 6.x upgrade, files collimator_g4.char, collimator_g5.char and
AdvantageUserPrefs did not exist on the System State. Therefore, the tool will
report errors during the restore on 6.x.
=> To create the collimator characterization file, in Service Desktop, select

Replacement Procedures -> Collimator Change -> Mechanical Characterization ->
Collimator Data, and replace the default numbers by the numbers recorded in
Section 2.2. (Values can also be entered in System Integration > Characterization >
Collimator if the service key is not available.) Then select ’Update Table’, ’Continue’
and finally ’Hardware Reset’ for reading the new characterization file. Exit
Mechanical Characterization tool.
=> To create the user preferences file, in ImageWorks, select an image, click Viewer
-> User Prefs. Select modality CT and replace the default titles and values by the
titles and values recorded in Section 2.2. Then select ’Set as default’ and exit the
tool.
If there are no images in the database, the user can create a SMPTE image by
selecting TroubleShoot -> Display Processing -> Install SMPTE image in the Service
Desktop.
108
2.14 Initialize Characterization

Initializing the system characterization is needed each time the software is loaded.
In Service Desktop, select System Integration -> Characterization, then click Start.
When the Characterization window appears the initialization is complete. Select File
from the menu bar and then select Exit.
2.15 Initialize SBC and Verify Collimator Characterization

NOTE: IMPORTANT: Do this before rebooting to ensure proper SBC initialization (timer files).
Rebooting the SBC after the first applications startup but before proper SBC initialization
can result in corrupt SBC timer files, which may fill the SBC disk partition.
1. Run Tube Warm-up (this step initializes the timer files).

2. Verify collimator characterization and calibration by scanning at appropriate kVs and
apertures.
109
2.16 Security Patch (Version 6.3 SW Only)

This section applies to Version 6.3 software only. Skip this and go onto the next if using
version 6.1 or earlier.
2.16.1 Installing the Security Patch

The security patch is only required when Version 6.3 software is installed. Skip this
section is not installing version 6.3 software. The procedure for installing the patch is as
follows.
1. Bring SW applications down by going into the Service Desktop and selecting the
Utilities tab, and then Application Shutdown
2. In a shell become root by typing: su –
3. Enter the root password

4. Insert the Security Patch CD
5. Type: mountCD /CDROM
6. Type: /CDROM/install_securityOctane_patch
7. Verify the installation completed successfully by typing the following within a Unix
shell:
showprods | grep 0004060
8. Inspect the screen output. You should see the following:

I patchSG0004060 04/30/2001 Patch SG0004060: Security Fix for telnetd (does not
require a reboot)
I patchSG0004060.eoe_sw 04/30/2001 IRIX Execution Environment Software
I patchSG0004060.eoe_sw.base 04/30/2001 IRIX Base Execution Environment
9. If the patch installed correctly, Type: unmountCD
10. Now restart CT applications
110
2.16.2 Removing the Security Patch

Normally, the Security patch never needs to be removed. If it dose, the following
procedure will allow you to remove it.
1. Bring SW applications down by going into the Service Desktop and choosing the
Utilities tab and then Application Shutdown
2. In a shell become root by typing: su –
3. Enter the root password and insert the Security Patch CD.
4. Type: mountCD /CDROM
5. Type: /CDROM/uninstall_securityOctane_patch
6. Restart CT Applications.
111
2.17 Add Software Options

Software Options must be loaded every time the OC software is reloaded.
1. In Service Desktop, select Utilities -> Install Options, then click Start.
An Options Window appears:
112
2. Click on the “Install” button.
3. Click on the “Permanent” button.
4. Click on the “MOD” button.
5. Insert the Options MOD into the drive.
Notice: This selection must be run once for each option MOD you are loading. For example,
if you have two (2) options MODs, you must run this selection twice.
113
6. Click on OK.
Example of a screen showing the options on sample MOD and options installed on
sample system:
7. Select the options to be installed (ex: click & drag down to highlight all the available
options, then release).
NOTE: If there is a scroll bar present, you may have to complete the installation in two
steps.

A box may appear while the options are loading.
When the option is displayed in the ”Installed Options” list, then installation of that
option is complete. Note that some options take a fraction of a second to install,
while options like 3D may take a half a minute (due to the fact that they are installing
software).
NOTE: If you install ConnectPro as an option, you need to follow the procedures in
Appendix B
Procedures for Installing ConnectPro.
9. After all the options are installed, select Quit twice, then OK.
NOTE: Do NOT reboot at this time, but continue as directed, and when you have completed
installing all options, proceed to section 2.18.
114
10. Remove the MOD & write protect the side with options. (Note: The initial install
requires the MOD to NOT be write protected; subsequent installs can be done with
the MOD write protected).
11. If you have another option MOD to load, go back to step 1.
NOTE: If you have installed Dentascan and the camera is setup, you need to follow the
procedures in Appendix C for installing Dentascan filming option.
2.18 DICOM camera Host File Conversion

NOTE: For FIRST-TIME upgrade to 6.x ONLY
This has to be done after restoring camera preferences (or system state).
1. In the Service Desktop, select Utlities -> Shell and open a unix shell.
2. Type: updateCameraConfig
2.19 Install Cameras

Camera installation is required in the following cases:
• Loading a new system.
• Loading a system with Smartview software for the first time.
• When a system state MOD is unavailable, unreadable or does not contain camera
preference information.
• If changes need to be made to existing camera configurations.
To install cameras, proceed to Appendix F
2.20 Install BMD

NOTE: Only if BMD Option is installed in section 2.17
Please proceed to the BMD documentation for BMD software installation.
2.21 Network Host File Conversion (FIRST-TIME Upgrades from 5.x to 6.x ONLY)
NOTE: If the user is unsure whether the Network Host File has the old Format, type:
cat ~ctuser/Prefs/SdCRHosts
An example of the OLD format is as follows:
3.7.52.160 aw31pc0 # 2 4006 No Comment
An example of the NEW format is as follows:

3.7.52.160 aw12pc0 # 2 4006 aw12pc0 No Comment 0 1 1 0
115
Notice the alphanumeric field “aw12pc0” and numeric fields “0 1 1 0” are added in
the new format of the Network Host File. Please proceed onto steps (1) to (3) ONLY IF
the system has the OLD format of the Network Host File.
1. Open a “Unix Shell” OC window in Service Desktop, select Utlities -> Shell
2. Type: su – (then enter the root password).
3. Type: configRemoteHostFile
NOTE: Applications must be shutdown and restarted for the New format SdCRHosts file to
be used by the Application.
2.22 SW Gantry Revolutions Counter Verification & Initialization

Shut down the application. In Service Desktop select Utilities & click on Shutdown
Application. Since SW Gantry Revolutions Counter is a new feature introduced in
release 6.1 during “First Time upgrade Only “ do the following steps in Section A
,otherwise proceed onto steps in Section B ( during the subsequent loads )
SECTION A :
1. In a unix shell, type: rsh sbc rm /usr/g/service/log/GantryRev.stats

2. Note down the no. of gantry revolutions counts information from “Odometer” in the
gantry.
3. Open a Unix Shell on OC & type: rsh sbc
4. Type : putStats
5. When prompted enter the “note down number” in step(1).
6. Type: getStats 6 | more
7. Verify the “no. of gantry revolution counts” (in the top line) info from the o/p to be
same as that from step (2).
8. Come out of SBC by typing : exit
9. Proceed to “shut down the system and restart the applications” section.
116
SECTION B:
1. Note down the no. of gantry revolutions counts information from “Odometer” in
gantry.
2. Open a unix shell and type: rsh sbc getStats 6
Verify that the gantry revolutions counts info in step(2) to be same as that of step
(1) . If both the readings are same then proceed to “shutdown the system & restart
the applications”. Otherwise record the difference between (1) and (2) readings
(odometer counts - software counts ).
3. Type: rsh sbc
4. Type: putStats
5. When prompted enter the difference noted down if any in step(2)
6. Proceed to “shutdown the system & restart the applications”
2.23 Shutdown the System & Restart Applications

2. Login as root ( By doing 'su - root' and subsequently entering Password).
have proper permissions.
If you need to change languages:
3. Run reconfig.
4. In the ‘Preference Settings’ Screen select the Language to display on the scanner
system.
5. Select Accept.
6. When the Reboot popup appears – select YES.
7. After the system starts up and you can access a UNIX shell, do reconfig on SBC:
• become root again
• rsh sbc
• reconfig
8. After the SBC reboots and the shell reverts to the OC type: st <Enter> to bring up
the applications.
Otherwise:
9. Run ‘reboot’.
10. After the system starts up and you can access a UNIX shell type: st <Enter> to
bring up the applications.
117
2.24 Restore BMD Database (only if BMD Option is installed to the system)
1. Insert the MOD with BMD database to the MOD drive.
4. Click on the ’Restore from Archive Disk’ on the BMD Database Archive toolbar.
5. Click on the ’OK’ button to proceed the restore
2.25 Verify System Operation

These are suggestions for things to try to make sure the system is operating properly
after upgrading or reloading the software.
1. SBC Timerfiles.
(a) In a Unix shell, rlogin to SBC.
Change directories to: cd /usr/g/service/log.
List the SBC timer files: ls -l *timers*
NOTE: In the above command string, the the ”-l” is <dash><lower-case L>.
you should see the following files listed:

dataacq.timers.log
fwmgr.timers.log
scanmgr.timers.log
scif.timers.log
(b) Verify timer file integrity by running the following commands
NOTE: In the following command strings, the the ”-l” is <dash><lower-case L>, and the
separator ”|” before ”head” is the ”pipe” symbol.
• timerReport -l dataacq.timers.log | head

timerReport -l fwmgr.timers.log | head
timerReport -l scanmgr.timers.log | head
timerReport -l scif.timers.log | head
• This is an example output report of a good timer file.
Report Generation Date: Wed Aug 13, 1997 10:29:27
ZeusRP System Timers Report
-------------------------------
From: Tue Aug 12, 1997 16:42:58

Through: Wed Aug 13, 1997 14:43:57
Hospital: Green Bay Packer Memorial Hospital
118
Suite Id: RP11

• This is an example output report of a bad timer file.
validateLogHdr(): unexpected magic number (djka;tiouapoietu)
found in scanmgr.timers.log. Expected (TIL)
File [scanmgr.timers.log] is not a Timers Log ... file not
processed
c) If any of the timer files are bad, then remove the bad timerfile. (Note you must be
root to remove the dataacq timers file).
Example: rm scnmgr.timers.log.
After removing the corrupt timer file, to generate a ”good” timer file, reboot the
system and rerun section 2.15.
2. ExamRx Desktop:
(a) Start the system and make sure you are on the ExamRx desktop.
(b) Verify that the date and time shown in the system status area is correct.
(c) Perform Tube Warmup and Fastcal.
(d) Set ExamRx Display up to Autoview using your favorite Autoview layout
(e) Verify Touch (if installed); make sure the cursor moves to the exact location
touched. Touch new patient and make sure the next screen appears.
(f) Scan your favorite image quality phantoms to ensure the system is making good
images. Make more than one image in a series so you can play with the images
below.
(g) Verify that the date and time shown on the images and in the browser are
correct.
(h) If your system has a Touch monitor installed, touch a few things on the Scan
Prescription screen to verify that touch is working and aligned correctly.
(i) If you have the SmartBeam option installed, set at least one scan to use Large
SFOV and verify that the text on the Scan User Interface says Large%. If you
don’t have SmartBeam installed the SFOV button will just say Large. Make sure
this group scans normally and check the image quality.
(j) Watch to make sure the images autoview.
(k) Use List/Select to bring an image up in an ExamRx free viewport.
(l) Try each of the Window/Level Preset keys to make sure they are set correctly.
(m) Set the window level via the mouse.
(n) Set the window level via the trackball.
(o) Use the Trackball to Page through the images.
(p) Film at least 1 sheet of film and verify the image quality.
(q) If the site has a Network Image Printer, verify the print quality.
119
3. ImageWorks Desktop:
(a) Go to the Image Works Desktop.
(b) Select Network and make sure all of the Remote hosts were restored when you
restored the system state. If they were not restored, use the information you
saved earlier to configure for networking.
(c) If you have any Genesis based systems configured for networking, and they are
up and running, select one of the remote systems and Query to see if you can
see those systems. (If the Hospital and the user on a remote system grants you
permission, try pushing images to the remote system.) Use both genesis and
non-genesis images if available.
(d) If you can see those systems, try pulling one or more exams onto this system.
(e) If it is alright with your site, try pushing images to and all Genesis and DICOM
systems that you have in your network configuration.
(f) Use Archive to restore one or more of the most recent Exams performed by the
site.
(g) Select an interesting Exam in the Browser and click on CT Viewer to see the
images.
(h) Try each of the Window/Level Presets to make sure they are set correctly.
(i) Set the window level via the mouse.
(j) Try a reformat of an interesting series.
(k) If you have the 3D option, try doing a 3D rendering of an interesting series.
(l) Print at least one film and check the image quality.
(m) Remove one or more of the Exams you pulled onto the system.
4. Service Desktop:
(a) Go to the Service Desktop.
(b) Click on Utilities to see the list of Utility Applications.
(c) Click on Verify Security and Start to see if the system can see your security
key.
(d) Click on Verify Options and Start to see if the right options are configured.
(e) Click on Scan Analysis and Start to see if you can see the scan files you made
earlier.
(f) Click on System Resets, perform a Scan Hardware Reset, and verify that it
completes normally.
(g) When the Scan Hardware Reset is complete, click on Cleanup to exit all the
Service applications.
5. Sherlock:
(a) Place the Sherlock CDROM in the CDROM drive.
(b) Select Sherlock to see it.
(c) Go through a few screens to make sure you can use Sherlock.
120
2.26 “SW Gantry Rev Count “in Health Page:

NOTE: For FIRST-TIME upgrades to 6.1 ONLY
1. Open a unix shell & make sure that system state MOD is mounted by typing
mountMOD
2. Type: RevCountOptionAdd
3. Through the Service Desktop -> PM -> System Health Page -> Configure -> Edit
Report.
4. Verify the “SW Gantry Rev Count “ option in the GUI by scrolling through the list.
5. Type: unmountMOD
6. Type: exit
SOFTWARE LOAD IS COMPLETE.
121
122
Appendix A
Creating Default Partitions
Run this procedure IF AND ONLY IF if a hard drive has been replaced or reformatted.
1. Select Enter Command Monitor icon. A boot monitor screen will pop up. Start
standalone disk partitioning utility.
NOTE: Make sure that the O/S CDROM (‘Pa’ for IRIX 6.5) is in the drive, and that the
CDROM drive is NOT busy before you proceed.
For IRIX 6.2

At the >> prompt type the following:
boot -f dksc(1,6,8)sashARCS dksc(1,6,7)stand/fx.ARCS - -x <Enter>
For IRIX 6.5

At the >> prompt type the following:
boot -f dksc(1,6,8)sash64 dksc(1,6,7)stand/fx.64 <Enter>
NOTE: If the boot is not successful, retry the command again.
2. Type the following responses to the indicated prompts:

(a) Do you require extended mode with all options available(no) ? yes
(b) fx: ”device-name” = (dksc) <Enter>
(c) Enter the following based on OS type,
For IRIX 6.2
fx: ctrl # = (0) .... 1 <Enter> (ie: the number one)
For IRIX 6.5:
fx: ctrl # = (0) ...... <Enter>
(d) fx: drive # = (1) <Enter>

The following message appears:
SGI drive type = <Disk Model No.>
[exi]t [d]ebug/ [l]abel/
[b]adblock/ [exe]rcise/ [r]epartition/
(e) fx> r <Enter>

[ro]otdrive [o]ptiondrive [e]xpert
[u]srrootdrive [re]size
123
(f) Select [ro]otdrive.

fx/repartition> ro <Enter>
(g) fx/repartition/rootdrive: type of data partition = (xfs) ... <Enter>
(h) Continue? ........ y <Enter>
(i) Go up a menu .. <Enter> (ie: two periods)
(j) Select [l]abel l <Enter> (ie: lower-case-L)
(k) Select [sy]nc sy <Enter>
(l) Go up a menu .. <Enter> (ie: two periods)
(m) Select [exi]t exi <Enter>
The screen will go blank and return to the system menu; (ie: the screen with the
list of icons).
3. Select ”Install System Software.
Note: Make sure the CDROM drive is NOT busy before proceeding to step (4).
4. Click on Local CD Rom.

5. Click on Install.
A message will appear: Insert the installation CD Rom now.
Note: You already have the IRIX 6.2/6.5 Pa CD in the drive from section 2.5, step (1).
Message appears: Obtaining installation tools.
Another message appears: Copy installation tools to disk.
Screen goes blank.
Message: Creating miniroot devices, please wait ...
Note: If creation of the miniroot devices fails with a message such as ”Filesystem is too
large for device”, do the following steps:
a) At the ”Hit Enter to go to a C shell” prompt, press <Enter>
b) For IRIX 6.2:
For IRIX 6.5:
c) Proceed with step (7) below
NOTE: Depending on the type of hard drive, the system may set the drive up initially with a
default filesystem and blocksize. If so, the following prompts may not appear and
steps 7-10 should be skipped. Later, during the load, the system will reset the drive
to the correct filesystem type and blocksize.
7. Make new file system on <Disk Device> [yes/no/sh/help]: .. yes <Enter>
124
NOTE: For IRIX 6.2, <Disk Device> should be /dev/dsk/dks1d1s0. For IRIX 6.5, <Disk
Device> should be /dev/dsk/dks0d1s0.
8. Are you sure? [y/n] (n): y <Enter>
9. For IRIX 6.2:

Do you want an EFS or an XFS filesystem? [efs/xfs]: xfs <Enter>
For IRIX 6.5:
Skip to step 10.
10. Block size of filesystem 512 or 4096 bytes? 512 <Enter>
11. Go to step (5) in Section 2.7 for continuing system software installation.
125
126
Appendix B
Installing ConnectPro
The following window appears:
Notice: For more information about the ConnectPro configuration, click ’Help’ button in the
window.
1. Enter the HIS Server IP Address.
NOTE: HIS Server IP Address identifies the Internet Address for the worklist information
server.
2. Enter the HIS Server AE Title.
NOTE: HIS Server AE Title is the name of the software that will provide the worklist data.
3. Enter the HIS Server AE Port.
NOTE: HIS Server AE Port is the well known, DICOM defined, port number for the AE Title.
4. Enter the CT Server AE Title.
127
NOTE: CT Server AE Title is used by Schedule Patient to query the Hospital Information
System for Procedure Steps scheduled for [This System].
5. Click ’Accept’ button in the window.

6. Go to step 6 of Section 2.17 for continuing installation.
128
Appendix C
Installing Dentascan filming Option
1. Open UNIX shell from the toolchest.
2. Type: cd ~ctuser/install <Enter>
3. Type: installcamera.denta <Enter>
4. If there is more than one printer on the system a list of printers is displayed.
Otherwise go to step (6).
Message appears: Enter index of the camera selected and press <Enter>:
5. Enter the index number for the camera: N <Enter>
6. Message appears:
Sending a film to the camera.
…
Notice: To determine the value of Dist 1 or Dist 2, measure the distance between the two
vertical lines on the film(s) printed, and enter the value(s) in MILLIMETERS (mm).
7. Enter the measurement of Dist 1: XXX.X <Enter>
8. If Zoom is supported by the type of Camera, the message will appear:

Enter the measurement of Dist 2: YYY.Y <Enter>
9. Message appears: DentaScan filming option installed.
10. Type: exit in the UNIX shell.
11. Go to Section 2.18 for continuing installation.
129
130
Appendix D
Installing Add-on Packages
1. Open UNIX shell, become root: su root <Enter>
(then enter the root passwd)
2. Type: installpkg (A software packages window appears)
3. Insert the Software Packages Media into the CD-ROM/MOD drive.

4. Click on the media you are using for installation.
Example screen showing the packages available on sample Packages Media:
131
5. Select the packages to be installed (e.g.: click & drag down to highlight all the
available options, then release).
A box appears while the software packages are loading.
7. After all the packages are installed, select Quit, then OK.
8. Follow the instructions in the release notes for continuing installation.
132
Appendix E
1. If applications is running, shutdown applications by selecting Utilities -> Shutdown
Applications on the Service Desktop.
2. Open the console window, by double-clicking on the console window icon in the
toolbox.
3. On the console window, login as root, type: cd /usr/g/scripts
4. Then type: ./reconfig
5. Select ’Config’ on the Installation title screen

6. On the System Configuration screen, select the Time zone for this site, and record it
below:
Region / Time Zone
7. [Accept] the reconfig

8. Click ’Yes’ to reboot the system.
9. Open a ”Unix Shell” OC window from tool chest, connect to SBC over the serial line:
cu sbc
10. Login as root (then type the root password)
11. On SBC window, type: reconfig
The SBC reconfigs the software and finally reboots
12. Proceed to section 2.10 to setup time on both SBC and OC.
133
134
Appendix F:
Installing Laser and DICOM cameras
Notice: Empty all filming queues before modifying camera parameters. The DASM must be
connected to the system and turned on at system startup to correctly setup the Laser
Camera.
For installing new cameras after a load from cold, follow the procedure below.
1. Click on the Service desktop button.

2. On the Desktop Toolbar select Utilities -> Install Camera.
3. The GUI that comes up will show a list of the cameras installed. (figure F-1)
Figure F-1 - Printer configuration GUI:
4. To add a new camera, click the “Add” button.

The dialog window for the camera type (DASM/DICOM) comes up (figure F-2).
135
Figure F-2 : Dialog box for camera type:
If no DASM has been detected during the OC boot, the “DASM” button will be
disabled. (F-3).
Figure F-3:
If the DASM is present and it has not been detected, reboot the OC and start the
camera configuration tool again.
5. To add a new laser camera, click “DASM” in the camera type dialog box.
This brings up a list of camera models. Select the appropriate model from the list
and click “Select”.
Select the camera model from the camera models list the camera model dialog
window (figure F-4).
136
Figure F-4 : Camera model dialog:
137
DASM Interface, will be detected automatically as either Analog or Digital.

Two Options are available with a Laser camera, Slides and Zoom. Set this option
only if the camera being installed supports slides and zoom. Setting the option
allows it to be enabled or disabled at the application level.
Camera manufacturers provide two Magnification type options for cameras. The
Smooth resolution blurs the image, while the Sharp resolution makes the image
”pixelly.” The default is smooth.
Finally, select the Film Formats to use by selecting “On” from the pull-down menu
for the appropriate formats. Valid film formats are determined by the camera
manufacturer (for example IMATION does not support 4x6, 2x4 or 1x2; Agfa does
not support 2x4). Also note that the DICOM print convention is to designate film
formats by column x row (e.g. 12 on 1 film is 3x4).
When finished setting the parameters, click on Done, then proceed to step 5.
6. To install a DICOM camera, click on “Add” and click “Dicom” in the dialog box that
appears.
This brings up a list of camera models. (figure F-6). Select the appropriate model
from the list and click “Select”.
This will pre-set all of the other parameters with the exception of the Network
Parameters. It is a good idea to verify the pre-set information as camera models do
change over time.
138
Notice: Selection of a different camera model will also clear the Image Quality parameters
as these are camera manufacturer dependent.
Set up the Network Parameters:

Device Name - A unique name to identify the camera.
Host Name - DICOM Print Server host name as defined by the network.
IP Address - DICOM Print Server IP Address as defined by the network.
AE Title - DICOM Print Server Application Entity Title as defined by the server.
TCP/IP Listen Port - DICOM Print Server TCP/IP Listen Port as defined by the
server.
Comments - (Optional) Comments to be used by the DICOM Print Server.
139
The Destination parameter selects the final location for film output, either Magazine
or Processor.
Orientation selects the film orientation; currently only the Portrait option is
supported.
Medium Type selects the type of film to be used, currently only Blue Film or Clear
Film options are supported.
The Magnification Type parameter selects the algorithm used interpolate pixels to
provide the necessary film resolution. This parameter should be set in conjunction
with the camera manufacturer to make the best possible image. The settings are:
None - No interpolation. This option is not supported by all camera vendors
Replicate - Adjacent pixels are interpolated which results in images described as
”pixelly.” This algorithm is not usually preferred
Bilinear - A first order interpolation of pixels is used which results in images
described as blurred. This algorithm is not usually preferred
Cubic - A third order interpolation is used with a large number of possible
formulations. Camera manufacturers define parameters called smoothing type
to set coefficients used in the algorithm. The implementation of these
coefficients is camera manufacturer dependent.
Finally, select the Film Formats to use by selecting “On” from the pull-down menu
for the appropriate formats. Valid film formats are determined by the camera
manufacturer (for example IMATION does not support 4x6, 2x4 or 1x2; Agfa does
not support 2x4). Also note that the DICOM print convention is to designate film
formats by column x row (e.g. 12 on 1 film is 3x4).
After the camera has been configured, click Advanced. This will create the camera
device file and bring up the Advanced Parameters screen.
140
The advanced camera parameters control the image quality of the films and the
network timeouts. For more information on the proper settings for these
parameters, please see the DICOM Print Device Conformance Statement or the
camera manufacturer representative.
Smoothing Type - This parameter is used when the magnification type is
CUBIC and it represents the coefficient for the image resolution algorithm. This
parameter is camera manufacturer dependent (for example, IMATION uses
numbers 1-15; Agfa uses numbers 0, 100-299).
Configuration - This parameter is camera manufacturer dependent and is
typically used to specify the image contrast (for example, IMATION uses
LUT=0,7; Agfa sets PRECEPTION_LUT=140; Kodak has CS300\CN-3\PD2.3).
Notice: The Configuration field may be up to 1024 characters long. The field will scroll
automatically as characters are typed. To review the Configuration field if the
entire length does not appear on screen, click and hold down the left mouse
button while the cursor is in the field, and drag the mouse towards the right (or
left as required).
141
Minimum and Maximum Density - These are used to set the brightness of the
images on the film. The range of values is 0-4095, although the valid range for a
specific camera is manufacturer dependent (for example, IMATION has a
maximum density level of 320).
Empty Image Density - This parameter sets the density for empty film
viewports. Typically BLACK is used but WHITE is also an option. The Minimum
and Maximum Density values are used as the representation.
Border Density - This sets the density for the border used around the film
viewports. Typically BLACK is used but WHITE is also an option. The Minimum
and Maximum Density values are used as the representation.
Click on Done, when finished setting up the Advanced Parameters.
142
Appendix G
Installation of a Network Printer
2. Login as root (By doing 'su - root' and subsequently entering Password).
have proper permissions to install network printer.
3. Ping the printer's IP address (This is done to check if the printer is available on the
Network).
4. If ping fails, do not proceed. The printer will not be installed.
5. Run reconfig.
When you do reconfig, in Hardware Settings Screen,
(a) Select Network Image Printer.
(b) Enter the Name and IP Address of the Network Image Printer.
NOTE: A “PRINT SERVER” is NOT SUPPORTED ( ie: a computer with a printer

attached). Network Image Printer ( which is supported) is a printer directly
attached to the network.
6. Then, continue the reconfig. After completing reconfig on OC, do reconfig on SBC.
143
144
Chapter 4
SW Version 6.2 Patch Procedures
Section 1 Before you Begin
1.1 Software Dependencies
NOTE CTi 6.2 SW patch must always be installed last. Remote connectivity Service software
should never be installed over the patch.
Software (SW) must be installed in the proper order, for the CT system to operate
correctly. The SW patch for 6.2 must be installed properly to create the proper SW
dependencies. If installed incorrectly, Remote Connectivity Service SW may fail to
function properly. Figure 1 shows the SW dependencies for installation of the 6.2
SW.
SW Dependencies
1 2 3
Patch
LFC w/o Service SW LFC w/Service SW
(Typical)
6.1 OS, CT APPS and
Service SW 6.1 OS SW 6.1 OS SW
(if applicable)
6.1 CT Application 6.1 CT Application

6.2 SW Patch
SW SW
6.1 Remote
6.2 SW Patch Connectivity Service
SW
6.2 SW Patch
Figure 1 - CTi 6.2 SW Patch Dependencies and Scenarios
To determine the SW procedure that's correct for you, determine the scenario that
best describes your situation.
145
1.2 CTi 6.2 SW Load Scenarios

Typical (see column 1 in Figure 1)
If your CTi system has 6.1 SW installed or 6.1 SW plus 6.1 Service SW installed,
follow the procedure described in Section 2 that follows.
NOTE To install 6.1 Service SW later, you must do the following:

1) De-install 6.2 SW patch (see Section 3)
2) Install Remote Connectivity Service SW
3) Install 6.2 SW patch (see Section 2).
Load from Cold (LFC) (see columns 2 & 3 in Figure 1)
If your CTi system has no CT SW installed, do the following:

1. Install 6.1 SW, as described in Chapter 3 `
Turbo LFC Procedure (Releases 6.1 & 6.3)"
2. Install 6.1 Service Software
3. Install 6.2 SW, as described in Section 2 that follows.
Section 2
Installation of the 6.2 Patch (from CD-ROM)
3. Insert the 6.2 patch CD-ROM
4. Type the following at the system prompt:
mountCD /mnt
/mnt/install6.2patch
You will see the following output:

"********************"
" Loading 6.2patch"
"********************"
5. After the patch has finished loading, type: unmountCD and remove the CD-ROM.
6. Perform two quick checks to verify the patch has been loaded correctly. Use the
showprods command as follows.
a) Type showprods | grep Rhapsode_patch_62
146
b) Verify that following text is displayed

I Rhapsode_patch_62 06/01/2001 Rhapsode Patch 6.2.2 ver 1
I Rhapsode_patch_62.img 06/01/2001 Patch files on the Operator Console
I Rhapsode_patch_62.img.Tilt 06/01/2001 Prescibed Tilt for CT/i ver 6.1.19.1
I Rhapsode_patch_62.img.fixes 06/01/2001 Quality fixes for CT/i ver 6.1.19.1
I Rhapsode_patch_62.img.sdc_patch 06/01/2001 IOS fixes for CT/i 6.1.19.1
c) Next, type showprods | grep patchSG0004060
b) Verify that following text is displayed

I patchSG0004060 06/01/2001 Patch SG0004060: Security Fix for telnetd
(does not require a reboot)
I patchSG0004060.eoe_sw 06/01/2001 IRIX Execution Environment Software
I patchSG0004060.eoe_sw.base 06/01/2001 IRIX Base Execution Environment
7. If the above information is listed, you have successfully installed the 6.2 patch. If not,
re-install the patch.
Section 3
De-installation of 6.2 SW Patch

10. Within the shell window, type /usr/g/scripts/uninstall6.2patch
147
148
GE Medical Systems
P.O. BOX 414
MILWAUKEE WISCONSIN 53201-0414 U.S.A.

Technical Publication

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

Technical Publication

Transféré par

Droits d'auteur :

Formats disponibles

GE Medical Systems

Copyrighted © by GE Medical Systems, 2001, 2004

CERTIFIED ELECTRICAL CONTRACTOR STATEMENT

OMISSIONS & ERRORS

Revision Date Reason for change

1 11/08/00 Updates to 4.4 procedure

2 04/27/01 Updated to included Indigo 384mb memory configuration

6 09/16/04 PQR 13013577 - Updated instructions on page 27, step 7.

7 09/24/04 PQR 13013714 - Updated instructions on page 37, step 11.

8 07/11/08 PQR 13120277 (13120279, 13121764, 13131803, 13144968)

Legal Notes .................................................................................................................. 6

Table of Contents ........................................................................................................ 7

Chapter 1 ` Turbo LFC Procedure (Rel. 4.4) .............................................................. 9

Chapter 2 SW Version 4.5 Patch Procedure ........................................................... 77

Chapter 3 ` Turbo LFC Procedure (Releases 6.1 & 6.3) ......................................... 79

Chapter 4 SW Version 6.2 Patch Procedures ....................................................... 145

Load From Cold • Save System State Data

System • Save System State

1.1 Appendix List:

1.2 Software Load From Cold (LFC) Overview

2.1 Install Software Contained On The Two CD-ROMs.

CDROM DRIVE VERIFICATION:

1. Open a UNIX shell.

VERIFY CDROM Firmware Revision on Toshiba XM6201TA Drives

11. Open a UNIX Shell

2.2.1 Find KV Board Installed Before You Do A Save System State:

1. Bring the system up and start the applications.

4. Become root (Type: su root).

5. Type: nbsClient obcr

2.2.2 Save System State Data

1. Bring the system up if it is not already up.

4. Highlight System State.

5. Click on the ”Start ...” button.

2.2.3 Handy commands:

2.2.4 For the [3.x] or [4.x] to [4.4] upgrade

Save Reformat Protocols

Save ConnectPro Information

2.2.6 Record Computer Memory Configuration

Main memory size: 384 Mbytes

Integral Ethernet: et0, IO0

2.3 Record Information In Case Your System State MOD Is Lost/Damaged

1. Record the most important Reconfig INFO for the scanner.

NOTE: IP Addresses and Net/Broadcast Masks have the format www.xxx.yyy.zzz

NOTE: When recording the NEXT_PATIENT_EXAM_NUMBER, confirm that this number is

2. Record the Networking Application (Image transfer) Configuration.

If you find this process tedious, you can look at file

Networking Application (Image Transfer) Configuration

Archive Node* Send Images* Query/Retrieve* Custom Comments*

* Some systems may not have these categories

3. Record the Camera Application Configuration.

If you are not on a Sonata system, look at the file

/usr/g/ctuser/app-defaults/devices/camera.dev on the system to get

Default Film Formats:

DICOM Camera Configuration

Default Film Formats:

DICOM Camera Advanced Configuration

2.4 Shutdown the System

2.5 Boot Standalone IRIX Disk Partitioning Utility

3. A screen will pop up with several icons:

2.6 If You Have A Keyboard Other Than A US-English Keyboard

2.7 Install System Software (Irix OS)

1. Click on Install System Software.

2. Click on Local CD ROM.

* READY TO INITIATE INSTALLATION *