Rev 3 DFW 2.8 Installation Manual English

ENGLISH
DIGORA® for Windows 2.8
Installation, configuration and

administration manual
Number 204207 (A4) ver. 3 (2011-04)
Number 204231 (A5) ver. 3 (2011-04)

DIGORA® for Windows
DIGORA® for Windows 2.8

Dental Imaging Software
Software installation, configuration and
administration manual
Medical Device Directive

93/42/EEC
DIGORA for Windows 2.8

Installation and configuration manual
Number 204207 (A4) ver 3 (2011-04)
Number 204231 (A5) ver. 3 (2011-04)
Original approved English language version
Manufactured by SOREDEX
Nahkelantie 160, Tuusula
P.O. BOX 148
FI-04301 Tuusula,
Finland
Tel. +358 (0)10 270 2000
Fax. + 358 9 701 5261
Installation and configuration manual 204207 iii

Windows is a registered trademark of Microsoft Corporation.
DIGORA is a registered trademark of SOREDEX.
SOREDEX endeavours to produce product documentation that is accurate

and up to date. However, our policy of continual product development may
result in changes to products that are not reflected in the product documenta-
tion. Therefore, this document should not be regarded as an infallible guide
to current product specifications. SOREDEX maintains the right to make
changes and alterations without prior notice.
iv Installation and configuration manual 204207

Contents
1. Introduction........................................................................................................ 1
1.1 About this manual .......................................................................................... 1
1.2 Computer Specifications ............................................................................... 2
2. Single User Installation ..................................................................................... 4
2.1 Before installing DIGORA for Windows ......................................................... 4
2.2 Previous versions of DIGORA for Windows .................................................. 4
2.3 Installing DIGORA for Windows .................................................................... 5
2.4 Licensing DIGORA for Windows ..................................................................11
2.5 Image storage options ..................................................................................11
3. Network Installation ........................................................................................ 12
3.1 Introduction ................................................................................................ 12
Network overview ..................................................................................... 12
Previous versions of DIGORA for Windows.............................................. 13
Before installing DfW Network version ..................................................... 13
Installation Overview................................................................................. 14
3.2 Installing the database (Solid 4.2) in the Server ......................................... 15
3.3 Starting and stopping Solid ......................................................................... 19
Starting and stopping Solid as a service (default): ................................... 19
Starting and stopping Solid manually: ...................................................... 20
3.4 Modifying the default Solid 4.2 configuration .............................................. 20
Editing the solid.ini file .............................................................................. 21
Changing the database listening (port) number........................................ 22
Database size ........................................................................................... 24
Changing the backup directory ................................................................. 26
Scheduling database backup.................................................................... 26
3.5 Installing DfW client in the workstation PCs ................................................ 27
3.6 Connecting DfW client to the database ....................................................... 32
Database Identification section ................................................................. 33
Application Server section ........................................................................ 33
Connection Parameters section................................................................ 33
3.7 Image storage options ................................................................................. 34
Installation and configuration manual 204207 v

4. Converting Databases..................................................................................... 36
4.1 About converting DfW databases ................................................................ 36
The SOLConvertD Database Conversion Utility ....................................... 36
4.2 Converting DfW 2.0/2.1 databases to database version 2.5 ....................... 37
Prerequisites for the database conversion: .............................................. 37
For network versions: ........................................................................... 37
For Single User versions: ..................................................................... 39
For Network and Single User versions ................................................. 39
Starting the conversion process ............................................................... 40
4.3 Converting DfW 2.5 (R0) network databases .............................................. 44
Prerequisites for the database conversion: .............................................. 44
Starting the conversion process ............................................................... 47
5. Licensing DIGORA for Windows .................................................................... 51
5.1 Registering the software ............................................................................. 51
5.2 Entering your license in DIGORA for Windows ........................................... 52
Entering license information received by email ........................................ 52
Entering license information received by fax or postal mail ..................... 54
5.3 Viewing your license information ................................................................. 55
6. DIGORA FMX PCI interface board P4602 ...................................................... 56
6.1 PCs running Windows XP ........................................................................... 56
Installing the PCI board ............................................................................ 56
Installing the driver ................................................................................... 56
vi Installation and configuration manual 204207

A1. Administration ................................................................................................. 1

A1.1 Introduction ................................................................................................. 1
A1.2 Installation ................................................................................................... 1
A2. Using DIGORA Admin..................................................................................... 2
A2.1 Starting DIGORA Admin ............................................................................. 2
A2.2 User Interface ............................................................................................. 2
A2.3. Opening a Database .................................................................................. 3
A3. Image Media .................................................................................................... 4
A3.1. Supported Media Types ............................................................................. 5
A3.2. Image Archiving Scenarios ........................................................................ 6
A3.3. Edit Media Types ....................................................................................... 8
A3.3.1 Adding New Media Type Record ..................................................... 9
A3.3.2. Modifying Media Type Record ...................................................... 10
A3.3.3. Deleting a Media Type Record ......................................................11
A3.4. Media Manager ........................................................................................ 12
A3.4.1. Adding New Image Media Record ................................................ 17
A3.4.2. Modifying Image Media Record.................................................... 18
A3.4.3. Deleting Image Media Record ...................................................... 19
A3.5. Create Media Files ................................................................................... 20
A3.5.1 Select Image Media Page ............................................................. 21
A3.5.2. Enter Calculate storage capacity ................................................. 22
A3.5.3. Enter Temporary Folder................................................................ 24
A3.5.4. Parameter Checking..................................................................... 25
A3.5.5. Create Image media ..................................................................... 26
A3.6. Restore Media Files ................................................................................. 27
A3.7. Set Current Folder ................................................................................... 28
A4. Database Parameters ................................................................................... 30
A4.1. Import Parameters ................................................................................... 33
A4.2. Export Parameters ................................................................................... 34
A5. Disk Space Controller Data .......................................................................... 35
A5.1. Adding New Disk Space Item .................................................................. 39
A5.2. Modifying Disk Space Item ...................................................................... 41
A5.3. Deleting Disk Space Item ........................................................................ 42
A6. Log Files ........................................................................................................ 43
Installation and configuration manual 204207 vii

viii Installation and configuration manual 204207

DIGORA® for Windows 1. Introduction
1. Introduction
1.1 About this manual
This manual describes how to install and configure
DIGORA for Windows (DfW) 2.8 dental imaging
software.
Two versions of the software are available:

- Single user version and
- Network or multi user version

This manual describes how to install both versions.
Installation and configuration manual 204207 1

1. Introduction DIGORA® for Windows
1.2 Computer Specifications

The computer specifications listed below are the
minimum requirements for normal clinical use. If the
computer will be used for administrative tasks, copy-
ing patients from one database to another database
or database conversion, more memory and disk
space will be required.
NOTE: Please refer to the digital device installation

manual for additional device-specific requirements.
Single User PC
Operating system - Windows 7, 32 or 64-bit, Professional, Ultimate or
Enterprise.
- Windows Vista SP2, 32 or 64 bit, Business, Ultimate or
Enterprise (SP2)
- Windows XP Professional, 32-bit (SP3)
PC Pentium 4 CPU 2.0 GHz, CD/DVD-ROM
RAM 1 GB or more (Windows XP)
2 GB or more (Windows Vista, Windows 7)
Hard disk 100 GB (or more)
Monitor (minimum) 17” XGA, 1024 x 768, True Color
19” SXGA, 1280x1024, True Color (recommended)
Network interface 10/100/1000 Ethernet
Network protocol TCP/IP
Backup Tape drive (SCSI) or other external backup device
Other Optional CD/DVD-R drive for archive purposes.
DIGORA FMX and CRANEX D require one PCI slot for
the interface card.
CRANEX D with serial number B81642 and below
requires two RS-232 serial ports (first RS-232 port must
be built into the motherboard).
2 Installation and configuration manual 204207

DIGORA® for Windows 1. Introduction
Workstation PC
Operating system - Windows 7, 32 or 64-bit, Professional, Ultimate or
Enterprise.
- Windows Vista SP2, 32 or 64 bit, Business, Ultimate or
Enterprise (SP2)
- Windows XP Professional, 32-bit (SP3)
PC Pentium 4 CPU 2.0 GHz, CD/DVD-ROM
RAM 1 GB or more (Windows XP)
2 GB or more (Windows Vista, Windows 7)
Hard disk 25 MB for client software (data is stored on server)
Monitor (minimum) 17” XGA, 1024x768, True Color
19” SXGA, 1280x1024, True Color (recommended)
(Second network adapter required for CRANEX Excel D
and CRANEX BaseX D)
Backup See server requirements
Other Optional CD/DVD-R drive for archive purposes.
DIGORA FMX and CRANEX D require one PCI slot for
the interface card.
CRANEX D with serial number B81642 and below
requires two RS-232 serial ports (first RS-232 port must
be built into the motherboard).
Server PC
Operating system - Windows Server 2008 R2, 64-bit (client use requires
installation of Desktop Experience)
- Windows Server 2008, 32 or 64-bit (SP2) (client use
requires installation of Desktop Experience)
- Windows Server 2003, 32-bit (SP2)
- Windows 2000 Server, 32-bit (SP4)
PC Pentium 4 CPU or better, CD/DVD-ROM
RAM 1 GB or more (32-bit)
2 GB or more (64-bit)
Hard disk 100 GB (or more)
Monitor (minimum) No special requirements
Backup Tape drive (SCSI) or other external backup device
Other UPS (Uninterruptible Power Supply)

2. Single User Installation DIGORA® for Windows
2. Single User Installation

2.1 Before installing DIGORA for Windows
Please refer to the minimum PC requirements de-
scribed in section 1.2, Single-User PC.
If you are installing a digital device with an Ether-

net connection to the PC, ensure that the digital
device(s) are installed and connected to either the
network interface in the PC (stand-alone single-user
installation) or the network hub or switch (network
installation).
If you are installing a digital device which is supplied

with a PCI interface card, the card and driver must
be installed first, before starting DIGORA for Win-
dows installation. Drivers for the DIGORA FMX PCI
interface are included on the DIGORA for Windows
CD. For other digital devices the drivers will be sup-
plied on CD with the digital device. Please refer to
the digital device installation manual for information
on installing the PCI interface and driver.
IMPORTANT!
Installation requires administrator privileges on the
computer. You must be able to log into the computer
using an administrator user account. If you do not
have access to an administrator user account, you
will not be able to install the software. Normal, daily
use of the software can be done with normal user
accounts.
2.2 Previous versions of DIGORA for Windows

If a previous version of DIGORA for Windows is
installed in the PC uninstall before installing the new
version.
Do not remove or uninstall DfW 1.xx versions until

after database conversion has been performed.
Databases created with previous versions of DfW,

are NOT compatible with databases created with
DfW 2.5 R1 and above (hereafter referred to as
database version 2.5).

DIGORA® for Windows 2. Single User Installation
Previous databases must be converted to database

version 2.5 databases. For information on database
conversion see section 5 Converting Databases.
2.3 Installing DIGORA for Windows

1. Close all open programs.
2. Insert the DIGORA for Windows Single-User CD

into the CD-ROM drive.
3. The InstallShield Wizard will start automatically.

If it does not appear, you may need to start the
installation program manually. To do this, browse
the CD and double-click setup.exe.
4. Select the desired language.
Click the Next button.

5. The Welcome window will appear.
Click the Next button to continue.
6. The License Agreement window will appear.
Click the Yes button to accept the license agree-

ment and continue the installation.

7. By default DfW will be installed in C:\Program

Files\Soredex\DfW 2.8. If you wish to install
DfW in a different location, click the Browse...
button and select a new destination.
8. The next window will allow you select the digital

devices that you wish to use with DfW. Select
the devices that you want to install by placing a
check in the box next to the device.

Do not select devices which are not present.

Devices can be added or removed at any time
by clicking the add/remove button of DfW in the
Windows Control Panel, Add/Remove Programs
applet. Select Modify, then Next and you will be
able to add or remove devices.
NOTE:
If you selected DIGORA PCT or SCANORA
D, an additional window will allow you to select
which device to install.
Click the appropriate button to select the re-

quired device.
Click the Next button to continue

NOTE:
If you selected CRANEX D, an additional win-
dow will allow you to select Serial connec-
tion type. For CRANEX D units, serial number
B81642 and earlier select Serial connection
and for units with serial number B91643 and
later select Fiber connection.

quired connection.

9. The next window will show the installation path

and devices to be installed.
Click the Next button and the DfW software will

be installed into the PC.
10. When the installation is complete click the Fin-

ish button to end the installation. Wait for addi-
tional components to be installed. This may take
several minutes depending on the speed of the
PC
11. After all components have been installed restart

the PC.

2.4 Licensing DIGORA for Windows

DfW must be licensed for normal use. Without a li-
cense, DfW runs in Demo mode and is limited to
a maximum of 50 patients in each database. To
license DfW, you must fill out the license form pro-
vided with the software and send it to SOREDEX.
For information how to license the software see sec-
tion 6. Licensing DfW.
2.5 Image storage options

In DfW, images can be stored in two different ways:
a. Inside the database as binary large objects
(BLOBs). This is the default setting.
b. Outside the database as bitmap files in a sepa-

rate folder(s).
The database used in the Single-User version is lim-
ited to 2GB maximum size. Therefore if the images
are stored inside the database, the maximum size
can be reached within a short time. In most cases it
is strongly recommended to store the images out-
side the database in a folder.
NOTE:
The file system of the computer will become slow-
er when the number of files in the image folder
reaches about 10,000. It is important, therefore, to
monitor image folder(s) and create new ones when
needed on a regular basis.
For information on how to create image folders, see

section A3. Image Media.

3. Network Installation DIGORA® for Windows
3. Network Installation
3.1 Introduction
Network overview
The network is made up of PCs that are used as
workstations (Workstation PCs) and a PC that is
used as a database server (Server PC).
The DfW client is installed in each Workstation PC

in the network.
The database engine is installed in the Server PC.

All images from the digital devices will be stored in
the database on the Server PC.
An optional Disk Space Monitor service can also be
installed in the Server PC. The Disk Space Monitor
can monitor the available disk space on the server’s
hard disks.
SOREDEX strongly recommends that the DfW cli-

ent is NOT installed in the Server PC.

DIGORA® for Windows 3. Network Installation
Previous versions of DIGORA for Windows

If a previous version of DIGORA for Windows is
installed in the PC, uninstall it before installing the
new version.
Do not remove or uninstall DfW 1.xx versions until

after database conversion has been performed.
Databases created with DfW 2.5 R0 versions and

below are NOT compatible with DfW 2.8 databases.
Incompatible databases must be converted to da-

tabase version 2.5 before use with DfW 2.8. For
information on database conversion see section 5
Converting Databases.
Before installing DfW Network version

Please refer to the minimum PC requirements de-
scribed in section 1.2, for both Workstation PC and
Server PC.
If you are installing a digital device with an Ether-

net connection to the PC, ensure that the digital
device(s) are installed and connected to either the
network interface in the PC (stand-alone single-user
installation) or the network hub or switch (network
installation).
If you are installing a digital device which is supplied

with a PCI interface card, the card and driver must
be installed first, before starting DIGORA for Win-
dows 2.8 installation. Drivers for the DIGORA FMX
PCI interface and CRANEX D PCI interface are
included on the DIGORA for Windows 2.8 CD. For
other digital devices the drivers will be supplied on
CD with the digital device. Please refer to the digital
device installation manual for information on install-
ing drivers.

IMPORTANT!
Installation requires administrator privileges on the
computer. You must be able to log into the computer
using an administrator user account. If you do not
have access to an administrator user account, you
will not be able to install the software. Daily use
of the software can be done with normal user ac-
counts.
Installation Overview
Installing DfW in a network environment is carried
out as follows:
i. Install the DfW database (SOLID Server) in the
Server PC.
ii. Modify the SOLID Server parameters (optional).
iii. Install the DfW 2.8 client in each Workstation PC

in the network.
iv. If you are upgrading DfW 2.0 or 2.1 to DfW 2.8,

convert the 2.0 or 2.1 database to database ver-
sion 2.5.
NOTE:
If you need to upgrade older 1.x versions of
DfW, please contact SOREDEX Customer Sup-
port for instructions.

3.2 Installing the database (Solid 4.2) in the Server

IMPORTANT!
Observe the following if you are upgrading a previ-
ous version of DfW 2.0 or 2.1 to DfW 2.8:
- The DfW 2.8 database MUST be installed to a
different location than a DfW 2.0 or 2.1 data-
base.
- The 2.8 database MUST have a DIFFERENT

listening number than the 2.0 or 2.1 database.
For information on how to do this see section
3.4 Modifying the default SOLID.INI file - Chang-
ing the database listening number.
- DfW 2.0 or 2.1 databases MUST be converted

to a DfW 2.8 database after DfW 2.8 has been
completely installed.
For information on how to do this see section 5
Converting Databases.
IMPORTANT!
If you are upgrading a previous version of DfW,
close all DfW clients and stop the database en-
gine before starting to install of DfW 2.8.
2. Insert the DfW 2.8 Network CD into the CD-

ROM drive of the server PC.
3. Browse the CD and open the folder Solid7User\

DISK1 or Solid20User\DISK1 and then double
click SETUP.EXE. The Welcome window will
appear.

4. The Choose Destination Location window will

appear.
By default the DfW database (Solid 4.2) will be
installed in C:\Solid\ (Destination Folder) but if
you wish to install it in a different location click
the Browse... button and select a new destina-
tion folder.
IMPORTANT!
If you are upgrading a previous version of
DfW the DfW 2.8 database MUST be installed
to a different folder than the previous ver-
sion database.

5. The next window allows you to select the com-

ponents to be installed. An optional Disk Space
Monitor component named DfWSrv can be used
to monitor the free disk space on the server. If
you do not wish to use the DfWSrv component,
remove the check mark from the box.
The database will be installed to the location

specified and with the selected options.
6. The next window allows you to select how the

database (Solid 4.2) will be started:

Start Solid Server Automatically (during

bootup): Solid will be installed as a Windows
Service and will start automatically each time
the server PC is booted.
Manual launch of Solid server: Solid Server

must be started manually from the desktop icon
or Windows Start menu each time the server PC
is booted.
Click Next to continue after making your selec-

tion.
7. When the installation is complete, the following

window will appear. Click the Finish button to fin-
ish the database installation.
8. If you selected manual launch of Solid server,

you must double-click the desktop icon to start it
now.
NOTE:
If you selected Start Solid Server Automatically,
Solid Server will be started at the end of the
installation automatically.

3.3 Starting and stopping Solid

Starting and stopping Solid is done in different ways
depending on if it was installed to run automatically
as a service or if it was installed to be run manually.
The default installation will install Solid to run as a
service.
There are also some differences in the way the user

interacts with Solid depending on the startup meth-
od. These are explained below.
Starting and stopping Solid as a service (default):
Starting and stopping Solid as a service is done

using the Services applet in Administrative Tools in
the Control Panel. Click the Start menu, then Set-
tings, then Control Panel, then Administrative Tools.
Double-click the Services icon to open the applet.
Starting Solid
1. Locate SOLID Server 4.2 in the service list
and double-click it.
2. Click the Start button. Solid will start and the
status will change to Started.
Stopping Solid
1. Locate SOLID Server 4.2 in the service list
and double-click it.
2. Click the Stop button. Solid will stop and the
status will change to Stopped.
IMPORTANT:
Before stopping Solid, make sure that ALL DfW
clients are closed. When running Solid as a service,
Solid will not warn you if you try to stop it while us-
ers are still connected. Stopping Solid while users
are connected to the database may result in loss
of data.
NOTE:
The Solid service is started automatically each time
the server is booted. When Solid is running as a
service, there is no user interaction or user interface
for the service except in the Services applet.

Starting and stopping Solid manually:
Starting and stopping Solid manually
Starting Solid
1. Double click the Solid icon on the Windows
desktop; or
2. Click the Start menu, then Programs, then Solid,
Stopping Solid
1. Right-click the Solid button on the Windows
taskbar.
2. Select Close from the popup menu. Solid will

stop and disappear from the taskbar.
IMPORTANT:
Before stopping Solid, make sure that ALL DfW cli-
ents are closed. When running Solid manually, Solid
will warn you if you attempt to close it while users
are still connected to the database. Stopping Solid
while users are connected to the database may
result in loss of data.
NOTE:
Solid must be started manually each time the server
is booted, or it can be added to the Windows startup
folder so that is started when a user logs on. Please
refer to the Windows documentation for information
how to add shortcuts to the startup folder.
3.4 Modifying the default Solid 4.2 configuration

In most cases the default configuration of Solid does
not need to be modified. The default settings are:
• Database initial size up to 10 GB (gigabytes)
• Database listening (port) number is 1315
• Cache size used by Solid is 64 MB (megabytes)
• Online backup is made at 01:00 each day

The default configuration of Solid must be modified

if:
i. The database listening number needs to be
changed. (For example, if you are upgrading a
previous version of DfW to DfW 2.8, the data-
base MUST have a DIFFERENT listening num-
ber).
ii. The NetBIOS protocol will be used (not recom-

mended).
iii. The size of the database will exceed the 10 GB

initial size. (for example, database conversion)
iv. A different location for the backup folder is re-

quired.
v. The backup time needs to be changed.
NOTE:
This document does not include instructions on how
to add or change network protocols in the Windows
environment. Refer to the Microsoft® Windows docu-
mentation for more information.
NOTE:
If you make modifications to the solid.ini file you
must stop and re-start Solid for the changes to be in
use.
Editing the solid.ini file

1. Open Windows Explorer, locate the folder where
the database is installed and double click the
solid.ini file. The file will be opened in Notepad.
Below you will find the most important sections

of the solid.ini file which may need modified
based on your needs.

NOTE:
The solid.ini file is self-commented. All lines
starting with the semi-colon character (;) are
comments and will be ignored. Only lines with-
out the semi-colon character are used by Solid
for setting the configuration options. Please note
that the solid.ini samples shown in this manual
may not display properly due to text wrapping.
NOTE:
The solid.ini file is divided into sections to help
organize the configuration settings. Each section
is named within square brackets, for example:
[Com]
Changing the database listening (port) number

[Com]
;*** NETWORK NAME ***

;Listen=<protocol> <name or port>
;
; Solid listens to the network using certain
protocols and listening
; names or port numbers. Client processes must
use a matching network
; name, when connecting to a server.
; The default listening names vary depending on
platform.
; Select, edit and uncomment a suitable listen-
ing setting from below:
Listen=tcpip 1315 ; Generic

;Listen=tcpip 1315, nmpipe SOLID ; Windows
;Listen=tcpip 1315, shmem SOLID ; Windows
;Listen=tcpip 1315, upipe SOLID ; Unix
;Listen=tcpip 1315, decnet SOLID ; OpenVMS
;Listen=spx SOLID ; NetWare
The Listen parameter (in bold text) specifies

the listening protocol and port number. The valid
parameters for protocol are:
• tcpip - TCP/IP protocol
• netbios - NetBIOS protocol

An example to use TCP/IP protocol and number

1317:
[Com]
Listen=tcpip 1317
An example to use NetBIOS protocol and number

1313:
[Com]
Listen=netbios 1313
After editing the solid.ini file, save the file and then
stop and re-start Solid.
NOTE:
The number used with TCP/IP is the same as the
port number and must be available (not in use). A
list of the reserved port numbers can be found in:
C:\Windows\system32\drivers\etc\services
NOTE: The NetBIOS protocol is supported but is

not recommended. It is inherently less reliable than
TCP/IP. TCP/IP is the default and recommended
protocol.

Database size
Database installation automatically creates a da-
tabase that can will expand up to 10 GB. Further
expansion is done by adding additional File Specifi-
cations (FileSpecs) to the solid.ini file.
Below is the default configuration which creates 10
FileSpecs of 1 GB each (10 GB total):
[IndexFile]
;*** DATABASE FILES ***
FileSpec_1=C:\Solid\solid.db 1000m ;filepath &
maximum size in bytes
FileSpec_2=C:\Solid\solid.2 1000m
If the database is expected to expand beyond 10

GB, additional FileSpecs can be added. Additional
FileSpecs can be added at any time.
IMPORTANT:
If a previous version DfW database exists which
will be converted to a DfW 2.8 database, the DfW
2.8 database must be configured with adequate
FileSpecs so that it is large enough to store the con-
verted data and also have enough space for future
storage needs.
1. Open the solid.ini file in Notepad.
2. Create one or more new FileSpec entries below

the last one. (refer to bold text in example be-
low)

[IndexFile]
;*** DATABASE FILES ***
FileSpec_1=C:\Solid\solid.db 1000m ;filepath & maxi-
mum size in bytes
...
...
2. Close the solid.ini file and save the changes.

The changes will be active after stopping Solid
and restarting it.
The number at the end of each FileSpec line is the

maximum file size. The maximum size that is pos-
sible per FileSpec is 2 GB. You may use abbrevia-
tions k for kilobyte and m for megabyte after the
number.
Note that the FileSpec number must be incre-

mented by 1 for each new FileSpec and that the file
name must be unique (e.g. solid.5, solid.6, etc.). It
is highly recommended to use the full path name in
the FileSpec.
IMPORTANT:
Do not create FileSpecs to allow the size of the da-
tabase to exceed the amount of free disk space.
NOTE:
File Specifications can be located on any hard disk
in the server, they do not need to be in the same
folder or hard disk. Be sure to specify the full path
name including drive letter and folder name. Solid
will not create folders for you.
WARNING:
Do not place FileSpecs on remote drives or on
other computers that are accessed over the net-
work. All FileSpecs must be located on one or more
local hard drives in the server PC. Failure to do this
may result in lost data and images.

Changing the backup directory

The BackupDirectory line defines the folder in which
Solid stores backups of the databases.
;*** BACKUP LOCATION ***
BackupDirectory=C:\Solid\backup
;BackupDirectory=<default_backup_path>
1. If you wish to change the default backup direc-

tory to a different location, first create the new
folder and then modify the BackupDirectory line
in solid.ini. Note that Solid will not create fold-
ers automatically.

and restarting it.
IMPORTANT!
The Solid database backup only creates a backup
copy of the database to the specified folder. It is im-
portant to backup this copy to tape or other remov-
able media on a daily basis.
IMPORTANT:
It is the user’s responsibility to verify that the backup
is fully functional. The user must also verify that
there is enough free disk space in the new backup
location to contain copies of the database (all
FileSpecs and log files).
Scheduling database backup

The default backup time is 01:00 (1:00 AM).
[SRV]
;Backup done each night at 01:00
At=01:00 backup
The time format is 24 hour format.

1. To change database backup time edit the exist-
ing time.

and restarting it.

IMPORTANT:
Be sure to schedule the Solid backup so it will fin-
ish it’s process before the backup to tape or other
removable media is scheduled to run. If the Solid
backup process has not finished when the tape or
other removable media backup starts, the database
may not get backed up to removable media.
3.5 Installing DfW client in the workstation PCs

The DfW client can be installed in every workstation
PC in the network.
NOTE:
The number of workstations to which you may install
the DfW client is unlimited. The maximum number of
clients simultaneously connected to the Solid data-
base is either 7 or 20 users depending on the ver-
sion purchased.
NOTE:
If you are using a supported 3rd party database like
Microsoft SQL Server, then the maximum number
of simultaneous users will be determined by the
number client access licenses (CAL’s) you have
purchased from Microsoft.
2. Insert the DfW 2.8 Network CD into the CD-

ROM drive of the workstation PC.
3. Browse the CD and open the folder

DfW2.8Client and then double click setup.exe.
The language selection window will appear.
Select the desired language.

Click the Next button.
4. The Welcome window will appear, click the Next

button to continue.
5. The License Agreement window will appear.

Click the Yes button to accept the license agree-
ment and continue the installation.
6. By default DfW will be installed in C:\Program

Files\Soredex\DfW 2.8. If you wish to install DfW
in a different location, click the Browse... button
and select a new destination.

7. The next window will allow you select the digital

devices that you wish to use with DfW. Select
the devices that you want to install by placing a
check in the box next to the device.
Do not select devices which are not present. De-

vices can be added or removed at any time by
clicking the add/remove button of DfW 2.8 in the
Windows Control Panel, Add/Remove Programs
applet. Select Modify, then Next and you will be
able to add or remove devices.

NOTE:
If DIGORA PCT or SCANORA D was selected,
another window will allow you to select which
device to install.
Click the appropriate button to select the proper

device. Click the Next button to continue.
NOTE:
If you selected CRANEX D, an additional win-
dow will allow you to select Serial connec-
tion type. For CRANEX D units, serial number
B81642 and earlier select Serial connection
and for units with serial number B91643 and
later select Fiber connection.

quired connection.

8. The next window will show the installation path

and devices to be installed.
Click the Next button to continue. The DfW soft-

ware will be installed into the PC.
9. When the installation is complete click the Fin-

ish button to end the installation. Wait for addi-
tional components to be installed. This may take
several minutes depending on the speed of the
PC.
10. After all components have been installed restart

the PC.

3.6 Connecting DfW client to the database

The connection to the database must be configured
for each workstation PC where DfW has been in-
stalled.
Before continuing, please be sure that the database

(Solid) is running in the server PC.
1. Click the Start button in Windows, select Pro-

grams, DfW 2.8 and then click DfW 2.8.
An error message (6000) will appear because
the database connection has not been config-
ured. Click OK and the Insert Database window
will open.

Database Identification section

2. In the Name field enter a name for the data-
base, for example Database 1.
3. In the Number field enter the listening number

of the database. The default number is 1315.
IMPORTANT NOTE:
If the default listening number was changed dur-
ing database installation by editing the Solid.ini
file, enter that number instead of 1315.
Application Server section

4. If you wish to use the Disk Space Monitor (see
section 4. Disk Space Monitor), enter the IP
address of the server PC in the Server Name
field.
If you do not wish to use the Disk Space Monitor
put a check mark in the Do not use DIGORA
Server Component box.
Connection Parameters section

5. In the Server OS field select Windows NT.
6. In the Protocol field select the network protocol

used to communicate with the database in the
server PC. This must be the same network pro-
tocol used by Solid. (default: TCP/IP)
7. If you are using the TCP/IP protocol, enter the

IP address of the server PC in the Host Address
box.
8. Click the OK button to accept the settings and

connect to the database.
The above procedure must be carried out with ALL

workstation PCs in the network where DIGORA for
Windows is installed.

IMPORTANT:
When DIGORA for Windows is first installed, it oper-
ates in Demo mode. In demo mode the software is
fully functional but you cannot store more than 50
patients in the database.
You must register your copy of DIGORA for Win-

dows and receive an installation license for each
workstation. After the license has been installed,
DIGORA for Windows will operate in normal mode
and the number of patients you can store in the
database is unlimited.
For information on how to register and license
DIGORA for Windows, see section 6. Licensing
DIGORA for Windows.
NOTE:
The database connection information is stored for
each Windows user account. If multiple user ac-
counts are used the database connection informa-
tion must be entered using each user account.
IMPORTANT NOTE:
If you are using multiple databases the database
entry names MUST written in exactly the same way
in all PCs and Windows user accounts.
3.7 Image storage options

Images can be stored in two different ways:
a. as binary large objects (BLOBs) inside the data-
base.
b. as bitmap files in a separate folder(s) outside

the database.
It is important to decide carefully where images
should be stored. Storage space can be used up
very quickly especially if large images are being
stored.

If images are stored inside the database additional

disk space is needed. The database engine (Solid)
makes a regular backup of the database. The back-
up copy of the database is the same size as the
database, so a 6GB database also requires 6GB for
the backup for a total of 12GB.
If images are stored in a folder(s) outside the da-

tabase, only text data and small thumbnail images
are stored in the database. This means that the size
of the database does not grow as fast as if all the
images are stored inside the database.Less disk
space is needed for the backup as only the text data
and thumbnail images are backed up.
IMPORTANT:
Unless disk space is very limited, it is highly recom-
mended that images are stored in the database.
This is the most secure and safe method.
NOTE:
The Windows file system will become much slower
if the number files inside a folder reaches about
10,000. It is important, therefore, to monitor image
folder(s) and create new ones either when needed
on a regular basis.
For information on how to create image folders, see

sections 8.4 and 8.7 Administration.

4. Converting Databases DIGORA® for Windows
4. Converting Databases
4.1 About converting DfW databases
Databases created with DfW versions 2.5 R0 and
earlier are not compatible with DfW 2.8 and must
be converted to database version 2.5 (used by DfW
2.8) with the SOLConvertD Database Conversion
Utility supplied with DfW 2.8.
IMPORTANT:
DfW 1.x databases cannot be converted DIRECTLY
to database version 2.5. A DfW 1.x database must
first be converted to a DfW 2.1 database and then
the 2.1 database is converted to database version
2.5.
Converting 1.x databases to 2.1 databases is de-
scribed in Appendix A at the back of this manual.
IMPORTANT NOTE FOR PREVIOUS VERSIONS

OF DFW 2.5 R0 NETWORK:
DfW 2.5 R1 and later network versions (including
DfW 2.8) use a different version of the Solid data-
base engine than the previous DfW network ver-
sions. If you are upgrading a DfW 2.5 R0 (or earlier)
version to DfW 2.8, the DfW 2.5 R0 data must be
copied from the Solid 2.2 database to a new Solid
4.2 database using the database converter. Refer to
the section 5.3 for instructions.
The SOLConvertD Database Conversion Utility

The SOLConvert Database Conversion Utility is
used to:
- Convert DfW 2.0 and 2.1 databases to database
version 2.5 databases.
- Convert (compact) database version 2.5 data-

bases so that they can be copied or moved.

DIGORA® for Windows 4. Converting Databases
4.2 Converting DfW 2.0/2.1 databases to database

version 2.5
SOLConvertD copies images and data from a DfW
2.0/2.1 (hereafter DfW 2.x) database (source) to a
new database version 2.5 database (target) used
by DfW 2.8. After conversion, the 2.x source data-
base remains on the hard disk and can be deleted
when it is no longer needed. It is recommended to
make a backup copy of the source database for
long-term archive purposes before deleting it.
If data is stored in the DfW 2.x database but the

images are stored outside the database in folder(s),
SOLConverD will copy the data in the DfW 2.x da-
tabase to database version 2.5 database but leave
the images in their original location outside the
database.
NOTE:
Solid database files used by DfW are binary com-
patible across operating systems, but the log files
are not. For example, you can copy the database
file(s) from Novell NetWare to Windows NT and run
them in Solid on Windows NT. Please note that the
Solid version must be the same. Solid 2.2 database
files are not compatible with Solid 4.2.
Prerequisites for the database conversion:

For network versions:
- Both DfW 2.x (source) and DfW 2.8 (target) da-

tabases must be running.
- All DfW clients in workstation PCs are closed.
- If source and target databases are network

versions, both must have a unique database
listening number. By default, DfW 2.x versions
use 1313 and DfW 2.8 uses 1315. Changes are
not needed unless the default numbers were
changed. For information on modifying the lis-
tening number, refer to section 3.4.

- Enough free disk space is available. A MINI-

MUM of 3.5X the size of the existing database is
required for conversion and immediately follow-
ing the conversion. After conversion is finished
and the first Solid backup is run, a minimum of
1.5X is needed.
- By default, DfW 2.8 allocates 10 GB size for

the database. If the source database is larger
than 10 GB, then additional FileSpecs must
be added to the target database’s Solid.ini
file and Solid re-started before using the
database converter. If the source database is
larger than 10 GB and enough FileSpecs are
not added to the Solid.ini file prior to starting the
conversion process, the conversion will not com-
plete successfully. Refer to section 3.4 for infor-
mation on how to increase the database size.
NOTE:
If images are stored in a folder in the source da-
tabase, this space is not included in the free disk
space needed. Only the size of the database is
used in the free disk space calculation.
IMPORTANT:
Depending on the size of the source database, the
conversion process could take many hours. If the
source database backup (Solid) is scheduled to oc-
cur during the conversion process, it should be disa-
bled in the Solid.ini file (and Solid re-started) before
starting the conversion. If the backup is allowed to
run during conversion, it will cause the conversion
to take much longer and addition disk space will be
needed.

For Single User versions:
- DfW must be closed.

required for conversion.
NOTE:
For Network and Single User versions
- Do not open DfW during the conversion proc-

ess.
- Do not run any CPU intensive applications on

the PC where you are running the database
converter until after conversion is finished.
- Additional RAM above the minimum DfW re-

quirements may be needed in the PC where the
converter is run especially with large network
databases. In some cases 1 GB of RAM may be
needed.
- In the PC used for the conversion process,

make sure the Windows pagefile size is con-
figured for at least 2.5X the amount of RAM
installed in the PC. In a typical PC with 512 MB
or RAM, the pagefile size should be 1280 MB.
The minimum and maximum size of the pagefile
should be the same. If you are unsure about
setting the pagefile size, refer to the Microsoft
Windows documentation for information regard-
ing setting the pagefile size or consult your
computer administrator.

Starting the conversion process

1. Start the conversion utility SOLConvertD by
locating the file using Windows Explorer. The
conversion utility is located in the folder where
DfW 2.8 is installed. By default this is:
C:\Program Files\Soredex\DfW2.8\
Double-click the file SOLConvertD to start it.

The DfW2.5 Database Converter Utility window
will appear.
2. Select the DfW 2.0-2.5 Database Converter tab.

3. In the Source Database section click the Select

button.
The Select Database window will appear.
4. Click the database that you want to convert (the

source database) to select it. Click the OK but-
ton.
5. In the Target Database section, select the new

DfW 2.8 database in the same way that you
selected the source database.
6. Click the Analyse button.

The database converter will check the source

database for possible errors that could cause
the conversion to fail. If errors are reported you
have the option to ignore any errors and convert
the database anyway. If you choose to ignore
the errors, click the Yes, I take full responsibil-
ity check box in the The Source Database Er-
ror Recovery Options section. Additional check
boxes will become available. Click either or both
of the additional check boxes as required.
WARNING:
If these options are selected patient data and/or
images may be lost during conversion.
7. Click the Convert button to start conversion.

8. The Progress window will appear. It shows the

status of the conversion.
When conversion is complete, a message will

appear indicating if the conversion was success-
ful. Click the OK button.
9. A Close button will appear in the progress win-

dow. Click the Close button.
10. Close the database converter by clicking the OK

button at the bottom of the window.

4.3 Converting DfW 2.5 (R0) network databases

The database converter SOLConvertD is also used
to convert (copy) a previous DfW 2.5 R0 database
to a new database version 2.5 database.
SOLConvertD copies images and data from a DfW

2.5 R0 database (source) to a new database ver-
sion 2.5 database (target). After conversion, the
DfW 2.5 R0 source database remains on the hard
disk and can be deleted when it is no longer need-
ed. It is recommended to make a backup copy of
the source database for long-term archive pur-
poses before deleting it.
If data is stored in the DfW 2.5 database but the

images are stored outside the database in folder(s),
SOLConverD will copy the data in the DfW 2.5
database to the database version 2.5 database but
leave the images in their original location outside
the database.
NOTE:
Solid database files used by DfW are binary com-
patible across operating systems, but the log files
are not. For example, you can copy the database
file(s) from Novell NetWare to Windows NT and run
them in Solid on Windows NT. Please note that the
Solid version must be the same. Solid 2.2 database
files are not compatible with Solid 4.2.
Prerequisites for the database conversion:

- Both DfW 2.5 R0 (source) and the database ver-
sion 2.5 (DfW 2.8) (target) databases must be
running.
- All DfW clients in workstation PCs are closed.
- Both databases must have a unique database

listening number. By default, DfW 2.5 R0 ver-
sions use 1313 and database version 2.5 uses
1315. Changes are not needed unless the de-
fault numbers were changed. For information on
modifying the listening number, refer to section
3.4.


required for conversion and immediately follow-
ing the conversion. After conversion is finished
and the first Solid backup is run, a minimum of
1.5X is needed.
- By default, DfW 2.8 databases allocate 10 GB

for the database. If the source database is
larger than 10 GB, additional FileSpecs must
be added to the target database’s Solid.ini
file and Solid re-started before using the
database converter. If the source database is
larger than 4 GB and enough FileSpecs are not
added to the Solid.ini file prior to starting the
conversion process, the conversion will not com-
plete successfully. Refer to section 3.4 for infor-
mation on how to increase the database size.
- Do not open DfW during the conversion proc-

ess.
- Do not run any CPU intensive applications on

the PC where you are running the database
converter until after conversion is finished.
- Additional RAM above the minimum DfW re-

quirements may be needed in the PC where the
converter is run especially with large network
databases. In some cases 1 GB of RAM may be
needed.
- In the PC used for the conversion process,

make sure the Windows pagefile size is con-
figured for at least 2.5X the amount of RAM
installed in the PC. In a typical PC with 512 MB
or RAM, the pagefile size should be 1280 MB.
The minimum and maximum size of the pagefile
should be the same. If you are unsure about
setting the pagefile size, refer to the Microsoft
Windows documentation for information regard-
ing setting the pagefile size or consult your
computer administrator.

NOTE:
IMPORTANT:
Depending on the size of the source database, the
conversion process could take many hours. If the
source database backup (Solid) is scheduled to oc-
cur during the conversion process, it should be disa-
bled in the Solid.ini file (and Solid re-started) before
starting the conversion. If the backup is allowed to
run during conversion, it will cause the conversion
to take much longer and addition disk space will be
needed.

Starting the conversion process

1. Start the conversion utility SOLConvertD by
locating the file using Windows Explorer. The
conversion utility is located in the folder where
DfW 2.8 is installed. By default this is:
C:\Program Files\Soredex\DfW2.8\
Double-click the file SOLConvertD to start it.

The DfW2.5 Database Converter Utility window
will appear.
2. Select the DfW 2.5-2.5 Database Converter tab.

3. In the Source Database section click the Select

button.
The Select Database window will appear.
4. Click the database that you want to convert (the

source database) to select it. Click the OK but-
ton.
5. In the Target Database section, select the new

DfW 2.8 database in the same way that you
selected the source database.

6. Click the Analyse button.

The database converter will check the source
database for possible errors that could cause
the conversion to fail. If errors are reported you
have the option to ignore any errors and convert
the database anyway. If you choose to ignore
the errors, click the Yes, I take full responsibil-
ity check box in the The Source Database Er-
ror Recovery Options section. Additional check
boxes will become available. Click either or both
of the additional check boxes as required.
WARNING:
If these options are selected patient data and/or
images may be lost during conversion.

7. Click the Convert button to start conversion
8. The Progress window will appear. It shows the

status of the conversion.
When conversion is complete, a message will

appear indicating if the conversion was success-
ful. Click the OK button.
9. A Close button will appear in the progress win-

dow. Click the Close button.
10. Close the database converter by clicking the OK

button at the bottom of the window.

DIGORA® for Windows 5. Licensing DfW
5. Licensing DIGORA for Windows

For normal usage, DIGORA for Windows software
must be licensed. When DfW is installed, it operates
in DEMO mode. In DEMO mode, the database is
limited to a maximum of 50 patients.
To receive your license, you must complete the

registration form and send it to SOREDEX. SORE-
DEX will then process your registration and send
you a license key to unlock DfW and remove the 50
patient limit.
After receiving your license key, you must install it in

DfW to unlock the software.
5.1 Registering the software

1. Open Windows Explorer and browse to the
folder where DfW 2.8 is installed, by default this
is: C:\Program Files\Soredex\DfW2.8.
2. Locate and double-click the file Licform.htm to

open the license form in your web browser.
3. Enter your information on the form. Please note

that all items in RED are mandatory. SORE-
DEX will not process incomplete registration
forms.
4. If the PC where you opened the license form

is connected to the internet, just click the Send
button at the bottom of the form. The form will
be sent electronically to SOREDEX. If the PC
has no internet access, you have two options.
a. Complete the form, save it, and then send

it as an attachment via email from another PC
which has an internet connection. To save the
form once you have completed it, select Save
as... from the File menu in Internet Explorer.
b. Complete the form, print it and then fax or

send it by postal mail to SOREDEX.
IMPORTANT:
SOREDEX will not process hand-written regis-
tration forms.

5. Licensing DfW DIGORA® for Windows
5.2 Entering your license in DIGORA for Windows

You will receive your license information from
SOREDEX, either by e-mail, fax or postal mail.
Please note that your license will be sent to you by
email if you have provided an email address.
You will enter the license in one of two ways de-

pending on how you received it:
- email as an attachment
- fax or postal mail
IMPORTANT:
Keep a copy of your license information in a safe
place in case you need to re-install DfW 2.8 in the
future.
IMPORTANT:
The license key information is stored in the Win-
dows registry. You must be logged in with Admin-
istrator rights when you enter your license infor-
mation. If you are not logged in with Administrator
rights, your license key will not be saved. For
information how to log in with Administrator rights,
refer to the documentation supplied with your PC or
contact your computer administrator.
NOTE:
In DfW network versions, the license key must be
installed in each PC where DfW is installed.
Entering license information received by email

1. The license file will be sent as an email attach-
ment. Save the attachment to your PC and then
copy it to the DfW 2.8 folder. By default this is:
C:\Program Files\Soredex\DfW2.8

2. Open DfW 2.8.
3. From the File menu select License and then

New...
The License window will open.
Click License file...
4. The Open window will appear. Select the license

file you copied in step 1 from the DfW 2.8 folder.
Click Open.
5. The license information will appear in the Li-

cense window. Click OK to save the license
information.
IMPORTANT:
Do not change or edit the Licensed to: or Li-
cense string: fields or the license will not be
accepted.

5. Licensing DfW DIGORA® for Windows
6. Repeat the licensing procedure with all the PCs

if you have a network version of DfW.
Entering license information received by fax or postal

mail
1. Open DfW 2.8.
2. From the File menu select License and then

New...
The License window will open.
3. Enter the Licensed to and License string in-

formation provided on the license you received.
Make sure that this information is typed in ex-
actly the same way as it appears on the license
including letter case and punctuation marks.
IMPORTANT:
Do not change or edit the Licensed to: or Li-
cense string: fields or the license will not be
accepted.
Click OK to save the license information.
3. Repeat the licensing procedure with all the PCs

if you have a network version of DfW.

5.3 Viewing your license information

1. If want to view the license information, click the
File menu, select License and click Info... .
The License Info window will appear.

6. Installing the Interface Board DIGORA® for Windows
6. DIGORA FMX PCI interface board P4602

6.1 PCs running Windows XP
Installing the PCI board
1. Turn the PC off and disconnect it from the main
power supply.
2. Remove the cover from PC. Refer to the PC

user’s manual.
3. Remove the cover from an empty PCI expan-

sion slot.
4. Insert the interface board into the expansion

slot. Make sure that it is fully inserted into the
PCI slot. Secure the board in position with the
screw from the expansion slot cover.
5. Replace the PC cover.
Installing the driver

1. Turn on PC.
2. During start up Windows will automatically

detect new hardware, and the New Hardware
Found dialog box will appear.
3. Insert the DIGORA for Windows software CD.
4. In the New Hardware found dialog box, browse

to the Drivers\pci_FMX folder on the CD and
then click OK. Follow the on screen instructions.
5. Windows will install the appropriate drivers.
6. Install DfW.

DIGORA® for Windows A. Administration
A1. Administration
A1.1 Introduction
DIGORA Admin is used to modify data that is com-
mon for all users. Usually that kind of data is critical
when considering the overall system performance
and functionality. So when using DIGORA Admin,
good understanding of system architecture is abso-
lutely required.
NOTE:
When any administrative task is performed, DfW
program(s) must be closed.
A1.2 Installation
DIGORA Admin is always installed along with DI-
GORA for Windows single user version.
When installing DIGORA for Windows network ver-

sion, DIGORA Admin is installed to one or more
client workstations. When installing client software,
the installation application asks if DIGORA Admin
will also be installed. DIGORA Admin should be
installed to workstations used by administration
personnel only.
Installation and configuration manual 204207 A-1

A. Adminstration DIGORA® for Windows
A2. Using DIGORA Admin

A2.1 Starting DIGORA Admin
DIGORA Admin is started by clicking taskbar’s Start
button, selecting menu ‘Programs – DfW 2.8’, and
clicking menu item ‘DIGORA Admin’.
DIGORA Admin opens a connection to the default

database during the startup process, so after DIGO-
RA Admin has been started it is immediately ready
to use.
A2.2 User Interface
DIGORA Admin User Interface
A-2 Installation and configuration manual 204207

The DIGORA Admin user interface consists of three

parts:
1. Database controls, name of the current data-
base, and button for opening another database.
2. Pages for different types of tasks. The function-

ality has been divided the following way:
- Modifying image media data (see Section B3)
- Modifying other parameters common for all
users (see Section B4)
- Modifying disk space controller data (see Sec-
tion B5)
In addition, there is page for viewing log files.

For more information, see Section B6.
3. Close button to close the application.
A2.3. Opening a Database

You may open another database by doing the fol-
lowing:
1. Click main window’s Open button. The following
window is opened:
Select Database Window

2. Select the database you wish to open.
3. Click the OK button. The selected database will

be opened and its name will be shown in the
DIGORA Admin main window. From now on,
all the actions are performed the newly opened
database.
For more information on the other functions of the
Select Database window, see the clinical part of the
DIGORA for Windows user manual Section 4.2.
A3. Image Media

DIGORA for Windows supports two methods for
saving images:
1. Saving images directly in the database. With
this option, image bitmaps are saved in the
database as BLOBs (Binary Large OBject), and
database engine takes care of all image saving/
restoring functionality. Since image bitmaps will
take considerable hard disk space, da-
tabase files will became large.
2. Saving images so that the image bitmap will be

saved in a separate file. With this option, image
attributes and a reference to the image file are
saved in the database. The database engine will
take care of saving/restoring image attributes,
and DIGORA for Windows client application will
take care of reading image bitmaps. Since im-
age bitmaps are saved outside of the database,
database files will be much smaller.

When adding new images, DIGORA for Windows

will by default use the former option, i.e. image bit-
maps are saved directly in the database. It is possi-
ble to configure DIGORA for Windows so, that latter
option is used. For more information, see Sections
3.1 Supported Media Types, 3.4 Media Manager,
and 3.7 Set Current Folder.
In addition of giving alternatives when saving im-

ages, Image Media functionality offers solution for
another important issue: Image Archiving. DIGORA
for Windows supports practically any kind of archiv-
ing media. For more information on image archiving
functionality, see Sections 3.2 Image Archiving
Scenarios, 3.3 Edit Media Types, 3.4 Media Man-
ager, and 3.5 Create Media Files.
A3.1. Supported Media Types

Media types supported by DIGORA for Windows fall
into two categories. Only one media type belongs
to the first category: folder media type. DIGORA
for Windows supports folder media type automati-
cally, i.e. support for it has been built in DIGORA for
Windows. The purpose of folder media is to offer a
location for images when they are saved outside of
the database (for more information, see Section 3.7
Set Current Folder).
All the rest of the media types, other than the folder
media type, belong to the archival media category.
As the name implies, archival media are used for
image archiving. By default, DIGORA for Windows
supports one archival media type: CD-ROM. More
archival media types may be added with Edit Media
Types function. For more information, see Section
3.3 Edit Media Types.

In the following, the characteristics of both catego-

ries are compared:
Folder Media Archival Media

_______________________________________________________________
Purpose Location for images Archiving images
when they are saved
outside of database
________________________________________________________________
Storage medium Hard disk CD-ROM,
DVD-ROM,
Magneto-Optical, etc…
_______________________________________________________________
Size Variable size Fixed size
_______________________________________________________________
Writeability Must always be Usually read-only,
writeable may be writeable
_______________________________________________________________
Removability Not removable May be removable
A3.2. Image Archiving Scenarios

The image archiving system supported by DIGORA
for Windows is highly scalable. To give some idea
of the possible alternatives, low-end and high-end
solutions are described in the following.
Low-End Solution
A low-end system consists of a standalone PC,
equipped with CD-Writer and CD-ROM drive, and
DIGORA for Windows single user software installed.
Images are archived relatively seldom. All images
that are going to be archived during the systems
lifetime will fit on a few CD-ROM discs.
When using this kind of system, the user must
change the CD-ROM disc in CD-ROM drive when
needed. Typically, this happens when such an im-
age is opened in DIGORA for Windows, whose im-
age data has been archived to some other disc than
is currently in the CD-ROM drive.

High-End Solution
A high-end system consists of multiple comput-
ers connected with a network, server computer
equipped with CD-ROM storage system, one com-
puter equipped with CD-Writer, and DIGORA for
Windows network software installed. Images are
archived relatively often.
Administrative personnel will take care of creating

new CD-ROM discs. Always when a new CD-ROM
is created, it is placed permanently in the CD-ROM
storage system. When using this kind of system, all
images are available all the time.
Note that mixing both models is supported. In some

situations, it is even recommended. Specially, if DI-
GORA for Windows single user system is used and
there is need for more than a few CD-ROM disks,
then using some CD-ROM storage system is highly
recommended.
Note also, that even in the scenarios above where

CD-ROM media type was used as an example, to-
day other storage systems with much higher capac-
ity are available.

A3.3. Edit Media Types

The Edit Media Types function is used to maintain
the system’s archival media type information. When
clicking Edit Media Types button, DIGORA Admin
first reminds of the database backup, and then
opens the following window:
Edit Media Types Window
In the media type list, all supported archival media

types are shown. The following media type informa-
tion is displayed:
1. Name
Media type name.
2. Warning Size
Used when creating media files (see Section 3.5
Create Media Files). If total size of image bit-
maps added to image media exceeds this level,
then a warning message is displayed to the
user. Warning size should be slightly less than
the media’s full capacity.

3. Error Size
Used when creating media files (see Section 3.5
Create Media Files) to control that not too many
images are moved to the same media. If total
size of image bitmaps added to image media
exceeds this level, then an error message is dis-
played to the user and execution is terminated.
Error size should be the same as the media’s
full capacity.
In the right part of the window, there are buttons for

closing the window, adding new media types, and
modifying and deleting existing media types.
A3.3.1 Adding New Media Type Record

You may add a new media type record by doing the
following:
1. Press the Add… button. The following window

is opened:
Add Media Type Window
2. Enter the Name, Warning Size and Error Size

parameters, and press OK. The new media type
record will be added to the database.

A3.3.2. Modifying Media Type Record

You may modify media type parameters by doing
the following:
1. Select the media type record to be modified in

the media type list.
2. Press the Modify… button. The following win-

dow is opened:
Modify Media Type Window
3. Modify the media type name, and press OK. The

modified name will be saved in the database.
Note that you cannot modify Warning Size and Error

Size parameters.
A - 10 Installation and configuration manual 204207

A3.3.3. Deleting a Media Type Record

You may delete a media type record by doing the
following:
1. Select the media type record to be deleted in the
media type list.
2. Press the Delete… button. The following confir-

mation is asked:
Confirm Delete Media Type Record
3. Press Yes. The media type record will be de-

leted.
Note that you cannot delete a media type record if

any media record of that corresponding media type
exists in the database. This means that the corre-
sponding image media record, which includes the
media type to be deleted, must be deleted first. How
to delete an image media record is explained in sec-
tion 3.4.3 Deleting an Image Media Record.
Installation and configuration manual 204207 A - 11

A3.4. Media Manager

Media Manager is used to maintain the system’s
image media information. Initially, after installation of
DIGORA for Windows, no image media information
exists in the database.
New image media records may be added and ex-

isting image media records may be modified with
Image Media Manager. When clicking the Media
Manager button, DIGORA Admin first reminds you
of the database backup, and then opens the follow-
ing window:
Image Media Manager Window
In the image media list, all image media records

which have been added to the database are shown.
The following image media information is displayed:

1. Folder Name
Name of the folder associated with the image
media. When DIGORA for Windows needs to
access image data, it reads it from this folder.
See the following paragraph ‘Folder Name For-
mat’ below for more information on the recom-
menced folder name format.
2. Volume Label
Volume label of the image media. Volume label
is used in low-end systems only, in high-end
systems the volume label should be left empty.
See paragraph ‘What happens if image data is
not found’ for more information of the meaning
of this parameter.
3. Type
Image media type. Two image media types are
predefined, CD-ROM and folder.
4. Size
Total size of image files moved so far to the im-
age media.
Folder Name Format

In Windows, there are two alternatives for giving
path names:
1. Local name consisting of drive letter, colon,
backslash, and subfolder names separated with
backslashes. If the name refers to root folder,
then name consists only of drive letter, colon
and backslash. Example 1: C:\Windows\System.
Example 2 (root folder): C:\
2. Universal Naming Convention name (UNC

name). UNC names are computer independent,
i.e. in local area network the same resource is
identified the same way in all computers.

UNC name consists of two backslashes, compu-

ter name and shared resource name separated
with backslash, and subfolder names separated
with backslashes.
Example: \\DfW Server\CD Rack\2000 Jan. In

the example ‘DfW Server’ is computer name,
‘CD Rack’ is the name of shared resource, and
‘2000 Jan’ is a subfolder name.
When entering a folder name for an image media in

DIGORA Admin, the rule is straightforward:
1. In single user version, local names should be

used.
2. In network version, UNC names MUST be used.
What happens if image data is not found

When opening an image in DIGORA for Windows,
and image data cannot be read, then one of the fol-
lowing messages is shown:

Messages shown if image data cannot be read
The first two messages are shown in low-end sys-

tems (for more information, see Section 3.2 Image
Archiving Scenarios). The first message is shown
if there is a disk in the media drive, but it is not the
correct one. User is asked to change the disk.
The second message is usually shown if there is no

disk in the media drive at all. User is asked to insert
the correct disk into the drive.
Note that in both cases some action is asked from

the user. The user needs to physically be located
near the computer, and all the image media disks
should be immediately available.
Third message is shown in high-end systems. It is

more severe than the first two messages, since it
means that for some reason image data could not
be read from image storage system. (As stated in
Section 3.2 Image Archiving Scenarios, image
data should always be available in high-end sys-
tems).
Note that no immediate action is asked from the

user. The reason for that is the following: The prob-
lem is in image storage system, and maintaining it
belongs to administrative personnel. Ordinary users
are not required to maintain it, and probably those
kinds of maintenance tasks are even prohibited
from them.

So the question now is the following: How does

DIGORA for Windows know what kind of message
should be shown, i.e. is the system low-end system
or high-end system. The answer is the volume label
parameter.
If a volume label parameter has been given for the

image media, then DIGORA for Windows assumes
the system is a low-end system, and the user will
change image media disks when needed.
If a volume label has not been given, then DIGORA

for Windows assumes the system is a high-end sys-
tem. If any problems occur when opening an image,
then it is a task of administrative personnel to fix the
problem.
To put it another way once more:
1. In low-end systems, always give a volume label

for image media.
2. In high-end systems, leave the volume label

parameter empty.
Special case of Folder media type

If folder media type has been selected for image
media record, then volume label parameter can-
not be given. The reason for that is obvious: Folder
media are used to save image bitmaps to the hard
disk, and the nature of folder media is permanent.
From DIGORA for Windows point of view, they re-
semble very much a high-end archival media, so a
volume label is not needed.
Note anyway, when using the folder name param-

eter, the same rules apply for folder media type than
for any other media type (see paragraph ‘Folder
Name Format’).

A3.4.1. Adding New Image Media Record

You may add a new media record by doing the fol-
lowing:
1. Press the Add… button. The following window is
opened:
Add Image Media Window

2. Enter the folder name parameter. For more in-
formation on the proper format, see Section 3.4
Media Manager, paragraph ‘Folder Name For-
mat’.
3. For low-end systems, enter the volume label

parameter. For more information on the volume
label parameter, see Section 3.4 Media Man-
ager, paragraph ‘What happens if image data is
not found’.
4. Select the media type.
5. Press OK. The new image media record will be

added to the database.

A3.4.2. Modifying Image Media Record

You may modify image media parameters by doing
the following:
1. Select the image media record to be modified in
the Image Media Manager list.
2. Press the Modify… button. The following win-

dow is opened:
Modify Image Media Window
3. Modify the folder name and/or volume label, and

press OK. The modified data will be saved in the
database.
Note that you will seldom need to modify image

media records. Take special care when modify-
ing image media records, since with incorrect
parameter values, the system will become unus-
able as image data can no longer be found.

A3.4.3. Deleting Image Media Record

You may delete an image media record by doing the
following:
1. Select the image media record to be deleted in
the media list.
Press the Delete… button. The following confir-

mation is asked:
Confirm Delete Image Media Record
2. Press Yes. The image media record will be de-

leted.
Note that you cannot delete an image media record

if any images have been moved to the correspond-
ing media.

A3.5. Create Media Files

The create Media Files function is used to move
image bitmap data from the database to the image
media.
All media types are supported. Functionality differs

slightly between folder media type and other archi-
val media types. With archival media, it is assumed
that the media is read-only, so image files are not
moved directly to media folder. Instead, they are
moved first to a temporary folder, from which they
are then moved to media folder with some other util-
ity software. Usually that kind of tool comes along
with the storage system hardware. An example
would be CD burning software for CD-R drives
When moving images to folder type media, it is as-

sumed that the media folder is writeable, and image
files are moved directly to the media folder. A tem-
porary folder is not used at all.
The user interface of Create Media Files function is

wizard-like. In the following, the functionality of each
wizard page is described more closely.

A3.5.1 Select Image Media Page

When clicking the Create Media Files button, DIGO-
RA Admin first reminds of the database backup, and
then opens the following window:
Select Image Media Page
Select the image media to which the image bitmaps

will be moved, and press the Next button.
Note that at this point you may modify the image

media data the same way as with Media Manager,
i.e. you may add, modify and delete image media
records. For more information, see Sections 3.4.1
Adding New Media Record, 3.4.2 Modifying Me-
dia Record, and 3.4.3 Deleting Media Record.

A3.5.2. Enter Calculate storage capacity

This feature allows you to determine how many im-
ages can be stored on the particular storage media
that you wish to use.
To use this feature:
1. Open the “Enter Image Search Criteria” (for
more information see section B3.5 Create Media
Files).
Select beginning date (Begin time) and end date

(End time) for the time period in which the im-
ages you wish to archive are located.
2. Key in the maximum data size of your storage

media, in MB, and click the “Calculate” button.

3. If all the images can be stored on the storage

media the end time that you previously keyed
in will appear in the “Calculate End Time” win-
dow. If there is not enough space, the date up to
which images can be stored will appear.
If you wish to archive the images click the “Ac-
cept” button.
4. The “Enter Image Search Criteria” window

will reappear. Click “Next” and the “Parameter
Checking” window will appear giving information
on the storage medium. Click “Next” to continue.

A3.5.3. Enter Temporary Folder

The last thing the user must do is to select a tempo-
rary folder for the image files. Below is an example
of that.
Enter Temporary Folder Page
A temporary folder may be selected from the folder

tree. The selected folder must be empty.
There is also another method to specify a temporary

folder name. First, a folder is selected from the fold-
er tree. Then a subfolder name is entered in the edit
box in the upper part of the window. DIGORA Admin
will then create a new subfolder with the specified
name, and use that folder as a temporary folder.

Note that a temporary folder is used only for archival

media types, i.e. for folder media it not used at all.
In the latter case, DIGORA Admin will move image
files directly to the media folder.
A3.5.4. Parameter Checking
Parameter Checking Page
When all parameters have been given, DIGORA Ad-

min will show all the given parameters. In addition,
exhaustive parameter checking is done. If every-
thing is OK, then creation of image media files may
be started by clicking the Next button.

A3.5.5. Create Image media
Create Image media Page
DIGORA Admin will show the progress of creat-

ing the image media files. Creation occurs in three
phases:
Phase 1:
Image media files are created.
Phase 2:
Media files are verified, i.e. it is checked that images
were not corrupted during creation, and they are ac-
ceptable for DIGORA for Windows.
Phase 3:
Database is updated. This means two things:
a) Reference information is updated so that DIGO-
RA for Windows is able to associate the image
with proper image media, and

b) Image bitmaps are deleted from the database.
After image media files have successfully been

created, then further actions depend on the media
type:
- With archival media, the image files must be

moved to the proper location (CD-ROM disk etc.),
usually with some utility software, i.e. CD burning
software.
- With folder media, DIGORA Admin copied im-
ages directly to the proper location, and no further
actions are required.
A3.6. Restore Media Files

The Restore Media Files is the opposite function
of the Create Media Files function. It may be used
to move image bitmaps from image media back
to the database. When clicking the Restore Media
Files button, DIGORA Admin first reminds you of
the database backup, and then opens the following
window:
Select Image Media Window

To restore image files back to the database, first

select the image media to be restored, and then
click OK button. That is all that needs to be done.
DIGORA Admin will restore all image media files
back to the database, and show the progress of the
restoration process.
A3.7. Set Current Folder

In DIGORA for Windows, when new images are
scanned and added to the database, the image
bitmap data is saved either in the database, or to a
separate file on the hard disk. By default, the former
alternative is used. The Set Current Folder func-
tion may be used to change the default location
for image bitmaps. When clicking the Set Current
Folder button, DIGORA Admin first reminds you of
the database backup, and then opens the following
window:
Select Location for Image Bitmaps Window
To set a folder as the default location for image bit-

maps, do the following:
1. In the upper part of the window, click the Folder

option.
2. From the image media list, select the proper im-

age media.
3. Press OK. From now on, all new image bitmaps

are saved to the folder of the selected image
media.

To set the database as the default location for im-

age bitmaps, do the following:
1. In the upper part of the window, click the Data-

base option.
2. Press OK. From now on, all new image bitmaps

are saved to the database.
Note that in the image media list only those image

media records whose type is folder are shown. If no
folder type media records have yet been added to
the database, DIGORA Admin shows the following
message:
No Image Media Records Message
In that case, you must first add at least one folder

type media record with Media Manager. For more
information, see Section 3.4.1 Adding New Media
Record.

A4. Database Parameters

The Database Parameters page is used to modify
miscellaneous database parameters. One thing is
common for these parameters: as the name implies
they are saved in the database. This means two
things:
1. Parameters are common for all database users,

i.e. when changing a parameter value, it has
an effect for all users. So special care must be
taken when changing parameter values. This
issue is meaningful (obviously) in DIGORA for
Windows network version only.
2. If running multiple databases, and some spe-

cific parameter value needs to be taken into use
system-wide, then the parameter value must be
changed in all databases.
If there is a need to update multiple parameters

uniformly among multiple databases, the latter thing
could lead to a difficult to maintain situation. To ad-
dress this issue, there are functions to export and
import database parameters between databases.
For more information, see Sections 4.1 Import
Parameters and 4.2 Export Parameters in this
section.

Database Parameters Page

The Database Parameters page consists of the fol-
lowing elements:
1. Image Media Volume Label.
If ‘Generate default name’ is checked, then a

default name is generated for the volume label
of the image media, when new image media
record is added (see Section 3.4.1 Adding New
Media Record).

Below the format string is given. The format string

consists of any alphanumeric characters, and of the
following specific formatting codes which are re-
placed with the corresponding data:
%Y Year with century
%y Year without century
%m Month as decimal number
%d Day of month
%i Serial number, one -based, incre-
mented if multiple image media records are added
during the same day
2. Patient IDs.
If ‘No duplicate patient IDs’ button is checked,

then all new patients added to the database
must have unique IDs. If a new patient with an
ID owned already by some other patient, is at-
tempted to be added, DIGORA for Windows will
show the following message:
Patient with given ID exists already in the database -message
3. Image Compression.
If the ‘Compress Images’ button is checked,

then all images added to the database will be
compressed. Compressed images will
take significantly less hard disk space. The com-
pression algorithm used by DIGORA for Win-
dows is ‘lossy’, meaning that some information
is lost when the image is compressed.
4. Import / Export Parameters.

For more information, see the next two Sections.

A4.1. Import Parameters

The Import Parameters function is used to import
database parameters from a text file. To import pa-
rameters, do the following:
1. Click Import Parameters… button. The following

window is opened:
Import Database Parameter File Window
2. Select the parameter file from the file list.
3. Press Open button to save the parameters.
Note that in addition to parameters described in

Section 4 Database Parameters, image media type
information is read from the parameter file and
saved in the database.

A4.2. Export Parameters

The Export Parameters function is used to save
database parameters to a file. Do the following:
1. Click Export Parameters… button. The following
window is opened:
Export Database Parameter File Window
2. Select a suitable path or folder and enter the file

name. By default, DIGORA Admin names the
parameter file according to the database name.
In most cases, that is a good default value.
3. Press the Save button to save the parameter

file.
Note that in addition to parameters described in

Section 4 Database Parameters, image media type
information is written into the parameter file.

A5. Disk Space Controller Data

The Disk Space Controller function is used to moni-
tor the available hard disk space. Disk space is
always checked when new images are added to the
database.
NOTE:
If the Disk Space Controller is installed to Windows
Server 2003, the user accounts must be in the
DCOM user group, otherwise a system error may
occur.
In the following there is an example of a typical con-

figuration:
Disk Space Controller Page

User interface consists of following elements:
1. Switch (checkbox) used to activate disk space

checking functionality. By default, disk space
checking is disabled.
2. Warning level value, expressed in megabytes.

When a new image is to be added to the data-
base, and there is less hard disk space available
than the warning level value, the following mes-
sage is displayed to the user:
Hard disk space running out message
In this case, the image is added to the database.

Usually this kind of warning means that some action
needs to be undertaken soon to increase the avail-
able hard disk space.
3. Error level value, expressed in megabytes.

When a new image is to be added to the data-
base, and there is less hard disk space available
than the error level value, the following message
is displayed to the user:
Hard disk full message

Immediate action should be undertaken to increase

the available hard disk space.
4. List of items to be checked. See the next para-
graph for more information on such items.
Disk Space Controller Items

Disk Space Controller is able to check two kinds of
items:
1. File items
2. Folder items
File items are (appropriately) files on the hard disk.
Always, when a new file item is added, the maxi-
mum size attribute is given for it. For file items, the
Disk Space Controller evaluates two things:
a) Remaining space within the file, i.e. maximum
size minus the current file size, and
b) Free disk space available on the drive where

the file is located. Final free disk space value
evaluated for a file item is the smaller of those
two values.
Example: maximum file size value is 1000MB, cur-
rent size of the file is 700MB, and there is 500MB
hard disk space available. The first value evaluated
is the space available within the file, i.e. 1000MB –
700MB = 300MB. That value is compared with the
available disk space, 500MB. The final value evalu-
ated for the file item is the smaller of those values,
i.e. 300MB.
Folder items are (appropriately) folders on the hard

disk. For folder items, Disk Space Controller evalu-
ates one thing only: Free disk space available on
the drive where the folder is located.

How the total free disk space is evaluated

When evaluating the total free disk space, the Disk
Space Controller evaluates all items, and the total
free disk space value that is evaluated, is smallest
of them.
Example: two items have been added to item list.

1. File item with the same characteristics as that
in the example above, i.e. maximum size is
1000MB, current size is 700MB, and free disk
space 500MB.
2 Folder item, free disk space on the drive where

the folder is located is 2000MB.
The value evaluated for the first item is 300MB
(see example above), and for the second folder
item the evaluated value is simply the free disk
space, 2000MB. The smallest of these two values is
300MB, which is the total free disk space evaluated
by the Disk Space Controller. That value is then
compared against the warning level and error level
values.
Item Chains
An item chain is a quite rarely used feature used
to control the disk space for items, which are by
nature ‘equal’. When adding a new disk space item
(see Section 5.1 Adding New Disk Space Item) and
the item is added as a sub-item for the selected
item, then an item chain will be constructed. When
evaluating an item chain, the Disk Space Control-
ler evaluates the values of each item, and the final
value evaluated for the item chain is the largest of
all evaluated values.
Example: The database engine is able to split da-

tabase files in multiple parts, or files. Two file items
have been chained:

1. D:\Data\DB_File, current size is 995MB
2. E:\Data\DB_File, current size is 200MB

The maximum size for both items is 1000MB. The
available free disk space on both drives is 2000MB.
The value evaluated for the first item is: min

(1000MB – 995MB, 2000MB) = 5MB
The value evaluated for second item is: min

(1000MB – 200MB, 2000MB) = 800MB
The final value evaluated for the item chain is the

largest of the item values, i.e. 800MB
Note: In order to use item chains in the situation

described in the example above, one must be abso-
lutely sure, that items are ‘equal’, i.e. the database
engine is equally capable to use remaining free
space in both database files.
A5.1. Adding New Disk Space Item

New disk space items may be added by clicking
Add Item button. Either of the following will happen:
1. If some item has been selected in the item list,
then user is given an option to add the item as
a sub item for the selected item. The following
window is opened:
Disk Space Item Window

If the user selects the ‘New root item’ option, then

the item will be added as a root item. When to-
tal free disk space is evaluated, the item is taken
into account as described in Section 5 Disk Space
Controller Data, paragraph ‘How the total free disk
space is evaluated’.
If the user selects the ‘Sub item of the selected item’

option, then the item will be added as a sub item,
and an item chain will be created. When evaluating
free disk space, the item is taken into account as
described in Section 5 Disk Space Controller Data,
paragraph ‘Item Chains’.
2. If no item has been selected in the item list,
then the item is always added as a root item.
When evaluating total free disk space, the item
is taken into account as described in Section 5
Disk Space Controller Data, paragraph ‘How the
total free disk space is evaluated’.
Next, the following window is opened to enter the

disk space item data:
Add New Item Window
Do the following:
1. Select the item type, folder or file.

2. Enter the path name. For folder items, enter

name of the folder. For file items, enter name of
the file. Note that the path name is always given
relative to the application server machine, and
NOT relative to the client machine where DIGO-
RA Admin is run. For more information of
application server concept, see DIGORA for
Windows Installation Manual.
3. For file items, enter the maximum size of the file.
4. Press OK. The new item will be added to the

item list.
A5.2. Modifying Disk Space Item

To modify a disk space item, do the following:
1. Select the item to be modified in the item list.
2. Click the Modify Item… button. The following

window is opened.
Modify Item Window
3. Modify the path name and/or max. size value.
4. Click the OK button.
Note that you cannot change the item type with the
Modify Item function.

A5.3. Deleting Disk Space Item

To delete a disk space item, do the following:
1. Select the item to be deleted in the item list.
2. Click the Delete Item… button. The following

confirmation is asked:
Confirm Delete Item
3. Click the Yes button. The selected item will be

deleted.

A6. Log Files

Log files are text files generated when executing
different tasks in DIGORA Admin and in DIGORA for
Windows. The purpose of log files is to view detailed
error information, in case any errors occur. DIGORA
Admin’s Log Files page is used to view log files.
Log Files Page
To open a log file for viewing, click the Log Files but-
ton.

Open Log File Window
To open a log file, select it from the list, and press

the Open button. A log viewer window is opened:
Error Log Viewer Window
In the list, all logged records are shown. You may

sort the records according to any data item, by click-
ing the corresponding column header. To switch the
sort order, click column header twice.

You may select the columns to be shown by clicking

the Select Columns… button. The following window
is opened:
Select Columns Window
By default, all columns are visible. You may hide a

column by removing the check mark for that column.

Rev 3 DFW 2.8 Installation Manual English

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Rev 3 DFW 2.8 Installation Manual English

Uploaded by

Copyright:

Available Formats

ENGLISH

DIGORA® for Windows 2.8

Installation, configuration and

Number 204231 (A5) ver. 3 (2011-04)

DIGORA® for Windows 2.8

Medical Device Directive

DIGORA for Windows 2.8

Number 204207 (A4) ver 3 (2011-04)

Number 204231 (A5) ver. 3 (2011-04)

Original approved English language version

Installation and configuration manual 204207 iii

Windows is a registered trademark of Microsoft Corporation.

DIGORA is a registered trademark of SOREDEX.

SOREDEX endeavours to produce product documentation that is accurate

iv Installation and configuration manual 204207

Installation and configuration manual 204207 v

vi Installation and configuration manual 204207

A1. Administration ................................................................................................. 1

Installation and configuration manual 204207 vii

viii Installation and configuration manual 204207

Two versions of the software are available:

- Network or multi user version

Installation and configuration manual 204207 1

1.2 Computer Specifications

NOTE: Please refer to the digital device installation

2 Installation and configuration manual 204207

Installation and configuration manual 204207 3

2. Single User Installation

If you are installing a digital device with an Ether-

If you are installing a digital device which is supplied

2.2 Previous versions of DIGORA for Windows

Do not remove or uninstall DfW 1.xx versions until

Databases created with previous versions of DfW,

4 Installation and configuration manual 204207

Previous databases must be converted to database

2.3 Installing DIGORA for Windows

2. Insert the DIGORA for Windows Single-User CD

3. The InstallShield Wizard will start automatically.

4. Select the desired language.

Click the Next button.

Installation and configuration manual 204207 5

5. The Welcome window will appear.

Click the Next button to continue.

6. The License Agreement window will appear.

Click the Yes button to accept the license agree-

6 Installation and configuration manual 204207

7. By default DfW will be installed in C:\Program

Click the Next button to continue.

8. The next window will allow you select the digital

Installation and configuration manual 204207 7

Do not select devices which are not present.

Click the Next button to continue.

Click the appropriate button to select the re-

Click the Next button to continue

8 Installation and configuration manual 204207

Click the appropriate button to select the re-

Click the Next button to continue.

Installation and configuration manual 204207 9

9. The next window will show the installation path

Click the Next button and the DfW software will

10. When the installation is complete click the Fin-

11. After all components have been installed restart

10 Installation and configuration manual 204207

;* NETWORK NAME *