ProBase/C

1.3

User manual
Questions and suggestions

Do you have ...

... any questions or suggestions regarding ... any technical questions or problems?
this manual?

Please note the order number or the date Please refer to the WINCOR NIXDORF
of issue of this manual and refer it to: Customer Care GmbH.

address: E-mail: [email protected]

WINCOR NIXDORF International GmbH
Handbuchredaktion R&D PDB 73
33094 Paderborn
Germany

August 2017
ProBase/C

1.3

User manual

Edition August 2017

Copyright © Information and trademarks

© WINCOR NIXDORF International GmbH 2017

All rights, including rights of translation and

rights of reproduction by reprinting,
copying or similar methods, even of parts,
are reserved.
Any violations give rise to a claim for
damages.

All rights, including rights created by patent

grants or registration of a utility model or
design, are reserved. Delivery subject to
availability; right of technical modifications
reserved.

All names of hardware and software

products mentioned in this manual are
trade names and/or trademarks of their
respective manufacturers.

August 2017
 Contents

ProBase/C ........................................................................................................................1
Documentation ..................................................................................................................1
System requirements .........................................................................................................2
Supported devices .............................................................................................................3

Product characteristics ...................................................................................................7

Product components ..........................................................................................................8
Product services ................................................................................................................9
Device function .............................................................................................................9
Optical Security Interface..............................................................................................9
System maintenance ..................................................................................................12
Software loading .........................................................................................................13
Integration points .............................................................................................................14
Customizing ................................................................................................................14
Installation ..................................................................................................................14
System start................................................................................................................14
Problem report with WNReport ...................................................................................16
Supported operating systems ..........................................................................................18
Security issues ................................................................................................................19
Hardening ...................................................................................................................19
Privileges and permissions in Windows ......................................................................19
System services .........................................................................................................20
Trusted Platform Module ............................................................................................20
Port Numbers .............................................................................................................21

Configuration basics .....................................................................................................23

Windows registry .............................................................................................................23
ProBase......................................................................................................................23
Environment variables ................................................................................................23
Automatic configuration ...................................................................................................24
HW_CONF .................................................................................................................24
Customizing .....................................................................................................................25
PROBASE.CUS..........................................................................................................25

ProBase Setup ...............................................................................................................27

General ............................................................................................................................27
Command line parameters ..............................................................................................28
Setup Type .................................................................................................................28
ProBase Destination Folder ........................................................................................28
Custom Control Folder................................................................................................28
Additional Options ......................................................................................................30
Custom Control Center - Dialog .......................................................................................31
First installation...........................................................................................................31
Maintenance ...............................................................................................................33
Finish dialog ...............................................................................................................34
Setup information .......................................................................................................35

Abbreviations.................................................................................................................37

Notes ..............................................................................................................................39

August 2017
August 2017
ProBase/C
ProBase is the SW platform for banking self-service systems from Wincor Nixdorf.

ProBase/C is characterized by the following features:

 Programmability
Supporting the CEN-standardized XFS programming interface, the system can be
freely programmed at system component / device level.
 System maintenance
Supported by an internal diagnostic kernel, ProBase/C has integrated service and
operating functions for the maintenance personnel.
 Software loading
ProBase with its ProSetup component offers a consistent process for basic installation
of the system PC. This includes: Hard disk partitioning, installation of the operating
system and of the operating system drivers, installation and configuration of the
ProBase components.

Documentation
The ProBase data medium contains various documents in PDF format. According to the
product structure, you will find the documents in subdirectories:

/DATA/DOC/
CSCW32/
CSCW32/SYS_MESS
DIAGSERV
PRODEVICE
Note: ProSetup, the software which controls the basic setup of the system PC, is
provided on an additional data medium which is also delivered with ProBase. The
corresponding documentation can be found on this data medium.

August 2017 1
System requirements
Not considering the application layer, which may contribute significant additional resource
demands, ProBase recommends the following lower limits for resources running
ProBase/C:

ProBase/C and Windows 10:

 EPC 5G or better
 Main memory: Minimum 2GB
 Hard disk: at least 50 GB
 Bootable DVD drive for initial installation *

ProBase/C and Windows 7:

 Processor: Pentium IV 2000 MHz

 Main memory: Minimum 1GB
 Hard disk: at least 50 GB
 Bootable DVD drive for initial installation *

Note: A personalized PC with Trusted Platform Module is required when using a Cineo
Cash System based on RM3 technology or a CHD V2CU with secure channel
communication.
* For systems without bootable CD-ROM drives, the ProSetup documentation describes
an alternative initial installation procedure.

2 August 2017
ProBase/C Supported devices

Supported devices
Document printer

Windows 7 Windows 10

TH97G
NP01
NP05
TP01/TP11 TP01/TP11
TP05/TP15 TP05/TP15
TP09/TP19 TP09/TP19
TP20 TP20
TP22 TP22
TH23 TH23

Journal printer

Windows 7 Windows 10

ND98
ND9D
ND98/D
TH30
NP06 NP06
TP06 TP06

Receipt printer

Windows 7 Windows 10

ND9A
ND9C
ND9E
TP07, TP07-2 TP07, TP07-2
TP07A, TP07-2A TP07A, TP07-2A
TP07C
TP13 TP13
TP24 TP24
TP25 TP25
TP27 TP27
TP28 TP28
NP07, NP07A NP07, NP07A
TH21
TH22

Passbook printer

Windows 7 Windows 10

PMxx PMxx
PUxx PUxx

August 2017 3
Printing cassette

Windows 7 Windows 10

TH60

Scanner

Windows 7 Windows 10

TOSCA 3 TOSCA 3
CM3000 (only USB) CM3000 (only USB)
RS89X RS89X
Bollettini check module Bollettini check module

ID card unit

Windows 7 Windows 10

MM, CIM86 additiv MM, CIM86 additiv

ID18
V2XF, V2XU V2XU
V2CU V2CU
ICM 300, ICM 300-2, ICM 330, ICM 330-2 ICM 330, ICM 330-2
ID24
MCT3K5
ICT3S5 ICT3S5

VPK2 (contactless) VPK2 (contactless)

PIN device

Windows 7 Windows 10

EPP V4, EPP V4+

EPP V5 EPP V5
EPP V6 EPP V6
EPP J6.1 EPP J6.1
EPP V7 EPP V7
PINpads
SEL softkeys SEL softkeys
ProPrint softkeys

4 August 2017
ProBase/C Supported devices

Sensor and indicator unit

Windows 7 Windows 10

SEL III
ProPrint x000 SEL
SEV4 SEV4
SEV5 SEV5
SE-CDL SE-CDL
MLC32 MLC32
proximity sensor (WATCHPORT/D) proximity sensor (WATCHPORT/D)
Headphone audio jack Headphone audio jack
Askim 1, Askim 2D, Askim 2DD Askim 2D, Askim 2DD
UPS (connected to special electronics) UPS (connected to special electronics)
Customer Connection Box (1 + 2) Customer Connection Box (1 + 2)
SDS

Text terminal unit

Windows 7 Windows 10

OP03 (V.24 operator panel)

OP04 (USB) OP04 (USB)
LC display ProPrint 1000
OP05 (usable either via OP03/OP04 emulation or
directly via Windows calls)
OP06 (usable either directly via Windows calls or OP06 (usable either directly via Windows calls or
Windows with OP03/OP04 emulation) Windows with OP03/OP04 emulation)
BA80 (for ProCash 285 rearload) BA80 (for ProCash 285 rearload)

Cash dispenser

Windows 7 Windows 10

CMD-V4 CMD-V4
CRSxe (ProCash 3100xe)
RM2
CMOxH Coin Dispenser CMOxH Coin Dispenser
CM2-O-8H Coin Dispenser CM2-O-8H Coin Dispenser
RM3 RM3
CMD-V5 CMD-V5

Cash-in module

Windows 7 Windows 10

CRSxe (ProCash 3100xe)

RM2 with Line-XLA or Line-XLB BIM
Coin Deposit Module CINA3xA4x Coin Deposit Module CINA3xA4x
Coin Deposit Module CM3 S/D Coin Deposit Module CM3 S/D
Coin Recycler (iCash 15e) Coin Recycler (iCash 15e)
CCDM CashIn with Line-XSA or Line-XSB BIM CCDM CashIn with Line-XSA or Line-XSB BIM
CCDMv2 CCDMv2
JCM WBA/UBA JCM WBA/UBA
RM3 (incl. Move BIM) RM3 (incl. Move BIM)

August 2017 5
Depository device

Windows 7 Windows 10

Envelope Depository with V.24 interface (firmware

DEPUST00.FRM and DEPUPC00.FRM)
Envelope Depository with V.24 and USB interfaces Envelope Depository with V.24 and USB interfaces
(firmware DEPUUS00.FRM and DEUUSB01.FRM) (firmware DEPUUS00.FRM and DEUUSB01.FRM)
Envelope Depository with V.24 and USB interface Envelope Depository with V.24 and USB interface
(firmware DEPUSB00.FRM) (firmware DEPUSB00.FRM)
EDU 281 EDU 281

Camera device

Windows 7 Windows 10

MAKU II MAKU II
CINEO USB cameras CINEO USB cameras
(card reader, facia camera, portrait) (card reader, facia camera, portrait)
Niscaya camera system Niscaya camera system

Barcode reader

Windows 7 Windows 10

1D: MS-804, MS-954

1D/2D: MS-4407
1D/2D: IS49020 (USB) 1D/2D: IS49020 (USB)
2D: ED40 (USB) 2D: ED40 (USB)

6 August 2017
Product characteristics
ProBase is the SW platform for banking self-service systems from Wincor Nixdorf. This
platform is used to provide SW components required for the operation of the system. The
following chapter gives an overview of ProBase; it is intended for persons whose
business is the integration in real-life application environments.

The ProBase platform is available in two product versions:

 ProBase/C Cash
 ProBase/C Info

ProBase/C is characterized by the following features:

 Programmability
Through the support of the CEN-standardized XFS programming interface, the system
can be freely programmed at system component / device level.
 System maintenance
Supported by an internal diagnostic kernel, ProBase has integrated service and
operating functions for the maintenance personnel.
 Initial installation
ProBase in combination with ProSetup offers a consistent process for basic setup of
the system PC. This includes: Hard disk formatting and partitioning, installation of the
operating system and of the operating system drivers, installation and configuration of
the ProBase components.

August 2017 7
Product components
ProBase/C provides the platform components required for the operation of self-service
equipment. These components are briefly introduced in the following:

 RTS
Run-Time System
- Basis device drivers and low-level software layers
- Service Provider implementations according to XFS
- Optical Security Interface (OSI) with services for cameras
- Trace and logging system
- Private JRE
- Hardware related device firmware files

 DAS
Diagnostics & Serviceability Platform with basic services for diagnostics,
troubleshooting support, operations analysis and system information.
 T/SOP
Graphical user interface of D&S Platform. Typically called via the application SOP.

 SDK
Software Development Kit
Contains all files for application development according to the XFS standard and tools.

 ProBase Setup
ProBase Setup supports the complete installation and configuration of ProBase/C
either GUI based or via command line, attended as well as unattended.

 ProSetup (on second CD)

Consistent software loading process from the setting up of the hard disk, through the
installation of the operating system, to the installation and configuration of the
ProBase components.

The ProBase/C product package includes further literature on the individual components.

8 August 2017
Product characteristics Product services

Product services
The previous chapter listed up the ProBase components and give a short outline of them.
Another approach to ProBase is via the services offered by ProBase. These can basically
be assigned to the following categories:

 Device function
 Maintenance
 Software loading

Device function

ProBase is to be regarded as an integration platform making the functionality of the

system hardware available in the form of a programming interface. Business case
mapping, transaction flow control and host communication are reserved to the
applications based on ProBase.

With regard to the programming interfaces offered, ProBase/C relies on the open
standard XFS. XFS stands for "eXtensions for Financial Services".

The first version of the XFS interface (WOSA/XFS) was defined in 1993, with the
participation of all major ATM manufacturers, with the aim of defining an international
standard for integrating special banking peripherals in Windows. In 1998, the specification
of the interface was assigned to the CEN.

Optical Security Interface

Beginning with ProCash 8xxx series, all Wincor Nixdorf ATMs can be equipped with high
resolution digital cameras that are connected directly to the ATM PC via USB. To operate
these cameras, ProBase contains the Optical Security Interface (OSI) that takes images,
adjusts the camera exposure and timing and provides the taken images via TCP/IP. This
makes these cameras compatible with standard IP-based CCTV cameras.

August 2017 9
Internal cameras
ProBase/C camera infrastructure consists of up to three, high resolution, digital cameras
with special functionality regarding the monitored area and or person, namely:

1. Portrait camera to take pictures of the terminal user (1),

2. Fascia camera in indoor (2a) and outdoor systems (2b) to observe the fascia,
especially the exit slot (shutter) of the cash module,
3. Card reader camera (3). Due to exclusive use by OSG, it is currently not supported by
OSI.

OSI subsystem
All these cameras will be connected to the terminal PC via USB. The images can be
either transferred as BMPs, a single JPEG or as a motion JPEG stream. They are
integrated into the OSI subsystem which is integral part of ProBase/C itself. OSI provides
the following public interfaces:

1. IP camera interface for mostly external video surveillance systems

2. Direct show interface to support usually the WebCam functionality (for e.g.
ProView)
3. XFS interface for banking application
In addition to the provision of public interfaces, OSI is used internally also for further
camera use cases like eye detection in drive-up systems in order to adjust the display tilt.

At system start OSI searches for all cameras in all available camera models (currently:
UVC and other) in the ATM system. At run time OSI manages the camera connection,
knows the concrete position within the system and is familiar with the required image
processing (rotation, cutting, etc.).

XFS support
From XFS point of view there are two different options how the USB cameras are used.
Depending on the selected customizing parameters they lead to the configuration of two
different XFS service providers where each one is reserved for a certain use case as
described in the following sub chapters:

10 August 2017
Product characteristics Product services

Direct use of USB cameras via XFS

Since ProBase/C 1.2, the XFS support of the USB cameras has been released. That
means, that an XFS application is able to control these cameras in order to take various
pictures whenever the use case it requires. The XFS names for the cameras are different
from the terminology used by OSI. The following mapping shows the relations:

1. Room (WFS_CAM_ROOM) and Person (WFS_CAM_PERSON) camera corresponds

to the portrait camera.
2. Exit slot camera (WFS_CAM_EXITSLOT) corresponds to the fascia camera.

Please note:

 For more detailed information about the OSI subsystem and its functionality including
installation and configuration see the document OSI_DOCUMENTATION.PDF.
 XFS related details can be looked up in the XFS documents for CAM device class.

Collaboration with external camera systems via XFS

ProBase/C supports also external camera systems (i.e. MAKU or other PBM compatible
systems), which are connected via serial interface (RS232) in order to trigger pictures. An
additional IP connection provides the access to the USB in the system via OSI. Thus, the
external camera system is able to address and steer these cameras.
Based on the picture below, depending of the concrete configuration of the external
system the banking application is able to control via XFS the following set of cameras:

 internal cameras (1, 2a, 2b) as well as

 external cameras (4, 5, 6),

in order to take and store pictures depending on the current transaction use case.

IP
external camera system
RS232

Please note, that the same XFS driver can be used for external camera systems where
the cameras are analogue. This is the camera concept mainly used in the ProCash xxxx
series.

August 2017 11
System maintenance

In addition to the freely programmable device functions, ProBase contains services which
directly support the group of persons involved in the maintenance and support of the
system (engineers, banking staff, ATM replenishment companies, administrators) in their
roles and tasks. These functions are provided mainly by the D&S Platform and T/SOP
components.

The D&S platform provides information and services for error identification, isolation and
correction as well as test- and runtime functions for the hardware components assembled
in the ATMs. These functions and diagnostic information can be used to examine the
runtime behavior or error conditions, in order to translate the findings into suitable
maintenance and repair activities. Statistics, analytic services to trace error codes back to
error causes, or the analysis of an error condition are further typical examples of the
services provided by the D&S Platform.

The T/SOP (technical SOP) supports users with varying technical knowledge regarding
the technical handling of Wincor Nixdorf systems. It is based mainly on the Diagnostic
and Serviceability Platform and allocates the graphical user interface to the functions and
data provided by the D&S platform.
Due to potential hardware damage not all functions of D&S and T/SOP are freely
available; their usage requires the use of a personalized CrypTA USB stick.

The services of the T/SOP are optimized to be displayed on a SVGA- or VGA-compatible

display medium such as the front screen or an operator panel, referred to as OP05/OP06.

12 August 2017
Product characteristics Product services

Software loading

With the installation components provided by ProBase (ProSetup and ProBase

Installation), a self-service machine can be fully loaded with the required platform
software. The software loading process is roughly as follows:

 Booting the system with ProSetup

 Formatting and setting up the hard disk
 Installation of the operating system
 Installation of drivers
 Installation and configuration of the ProBase components

If the operating system including the drivers has already been set up, the ProBase com-
ponents can be installed directly.

Before the actual installation takes place it is recommended to take some preparatory
steps. First the HW_CONF.INI file that is suitable for the hardware used should be held
ready. It is located on the data medium that comes with every self-service system
shipped by Wincor Nixdorf. In addition, the customizing can be prepared for the ProBase
configuration before the actual installation process starts. All these steps are described in
detail in the installation chapter.

With appropriate ProSetup customizing it is possible to integrate an application

installation in the software loading process.

August 2017 13
Integration points
ProBase is considered an integration platform; it therefore has various integration points
that are to be taken into account in an application and system integration process. The
following are the main points of contact with ProBase that are to be considered within the
framework of an integration process.

Customizing

Customizing is the adaptation of ProBase to the customers' individual needs. With

ProBase this takes place mainly during the installation process. The key element is the
Customizing file, which is taken into account by the ProBase setup and leads to various
installation procedures and configurations. If customizing is required, the file must be
prepared in an adapted form for the installation process. ProBase includes a default file
as the basis for the modification.

Installation

Although the ProBase data media as delivered are in principle the basis for software
loading on the system, under certain circumstances the generation of individual
installation CDs can simplify the installation process. In particular the number of data
media needed for the installation can be minimized.

System start

Another point of contact with ProBase during system integration is the system start. All
components involved in the system start - platform components, add-on und secondary
components - are to be aligned with one another. The main ProBase components in-
volved in a system start are outlined below. For details please refer to the relevant
component documentation.

CscWInit
CscWInit is the root of the platform startup. The startup point is defined by the integrator
by his placement of the synchronous call of CscWInit into the startup script of the
application.

CscWInit itself starts the ProBase services.

Startup of ProBase
The ProBase startup conducts various initializations - both pure SW initializations and
initializations of complete devices. Please note that under certain circumstances the
device initializations may take some time (for instance due to firmware load).

The ProBase startup is initiated by the program CscWRun.exe, while the shutdown is
performed by CscWStop.exe. As, however, CscWRun and, therefore, ProBase are
automatically launched by CscWInit, the use of CscWRun and CscWStop is restricted to
recovery situations at most.

By default, the XFS software layer is also started automatically in the course of the
ProBase startup.

14 August 2017
Product characteristics Integration points

For compatibility reasons with previous versions of ProBase there is a customizing option
which leads to a startup configuration where the XFS layer is not started automatically. In
that case, the call of <XFSROOT>\bin\ProDeviceStart becomes necessary as before.

Start of T/SOP
The T/SOP can be controlled in different ways:

It can be with the command file <CSCROOT>\diagserv\bin\tsopstart and terminated with

<CSCROOT>\diagserv\bin\tsopstop. In addition, it is possible to start the T/SOP via the
XFS VDM. Especially for use in labs, it may be convenient to start the T/SOP by means
of the related entry in the ProBase start menu, and terminated through its user interface.
As a matter of fact T/SOP never starts automatically.

The Diagnostics&Serviceability Platform required by T/SOP is both started and stopped

together with ProBase during system startup. If D&S is stopped, a running T/SOP is also
stopped.

To get up-to-date status information for all devices, it is necessary that all devices are
started by an application.

August 2017 15
Problem report with WNReport

Should problems occur with ProBase, please contact your local office or contact address.
Prepare a problem report with the following information:

- Describe the problem.

- Indicate the time and the frequency of its occurrence.

- How can the problem be reproduced?

- Did the problem occur after a particular event or a change (e.g. hardware, firmware or
software update)?

- Describe the system environment (ProBase version, operating system, application,

system).

- Is this an isolated problem or can it be observed on several systems?

Please use WNreport.exe on the system on which the problem occurs/occurred.

i This program collects bits of system information that is helpful for further analytic
purposes. Add the created file to the problem report.

The system report contains the exported files of the TLS (trace- and error-log) and the
eventlog (application, security, system). Furthermore various registry settings, list of
module identifications and directory lists are included. The report is completed by copies
of certain files (e. g. log and configuration files).

The size of the resulting ZIP file may be reduced by collecting the voluminous files (flight
record traces, JDD and D&S logs) within a specified time interval. Furthermore it is
possible to collect only the flight record traces with or without the JDD/D&S logs by
specifying a profile.

At the start of the collection process the working directory (%CSCROOT%\WNreport) and
all directories and files below are deleted.

The collected information/files are compressed and stored in corresponding

subdirectories of the resulting file "%CSCROOT%\WNreport\WNreport.zip". Using the
options reducing the size (-i, -p) the current date and time is inserted into the name of the
ZIP file in the format "WNreport_yyyymmdd-hhmmss.zip".

Command
WNREPORT.EXE [-s] [-o] [-l:<level] [-c:<path>] [-i[:<interval>]] [-p:<profile>]

The following command line options are supported:

-s silent mode; no console output of collecting activities is generated

-o console output of collecting progress (in percent)

-l:<level> collecting information up to and including <level>; the default level is 10

- execution with level > 10 may need several minutes
- for compatibility reason the default level is used when specifying level 1

-c:<path> copy resulting report file to the directory specified by the fully qualified
pathname

16 August 2017
Product characteristics Integration points

If the pathname contains spaces, add quotation marks around the

pathname. For example:

WNREPORT.EXE -c:"C:\Program Files\ProBase\logs"

-i[:<interval>] collecting flight record traces and JDD/D&S logs within <interval>:
- no interval specified the last 3 days
- 0, ..., 100 the last n days
- dd.mm.yyyy-dd.mm.yyyy from start to end date

Examples:

WNREPORT.EXE -i
WNREPORT.EXE -i:10
WNREPORT.EXE -i:01.01.2012-31.01.2012

-p:<profile> collecting according to the <profile>:

1 - only flight record traces
2 - only flight record traces and JDD/D&S logs

Error level

The program reports the following error levels:

0 no error

1 another instance of the program is already active

2 syntax error at command line

3 configuration of CSCROOT is missing (environment variable, registry)

4 error on compressing the report file

5 error on copying the report file

Report level (see option -l:<level>)

The scope of the data being collected is defined by registry settings. Each individual
command is represented by a registry parameter and assigned to a level
that supplements the name, separated by a comma:
<parameter name>,<level>=<command> (e. g. “Environment,5=set
> %WNREPFILE%”)

The usage of the levels is cumulative, thus a higher level includes all information
collected by a lower level. Calling WNREPORT.EXE without the level
option executes all commands with a level less than or equal the default
level (10). This default collection is a precondition for a meaningful error
analysis.

The assignments made in the default configuration can be modified project specific when
required. It must be ensured that the default collection contains all the
information of the default configuration. That is, even the modified levels
must be within the range 2 to 10 (level 1 is reserved).

August 2017 17
Supported operating systems
Windows 7 Professional, 32 Bit, Service Pack 1, with UAC switched off.

Windows 10 IoT Enterprise 2016 LTSB, 64bit, with UAC switched off.

Note of 64bit systems: ProBase/C is installed as 32bit software and is therefore subject of
redirection procedures (in registry and file system) due to the WOW64. For 32bit
applications, all redirections are transparent and therefore compatible.

18 August 2017
Product characteristics Security issues

Security issues
The following chapter outlines the security-relevant issues to be taken into account with
ProBase.

Hardening

ProBase is an open platform and provides no means for system hardening. To harden the
system, to prevent unauthorized access to the system and to ensure the integrity and
confidentially of security relevant and sensitive components of ProBase it is strongly
recommended to use Wincor Nixdorf Terminal Security Suite.

Privileges and permissions in Windows

The first thing to point out is that the ProBase setup program can only be executed in the
security context of an administrator.

The normal operating phase following the installation can of course also run in the
security context of an administrator. However, this is not an absolute necessity from the
ProBase point of view, but a security profile described below will do.

The security profile of a standard user, i.e. of a member of the “Users” group, serves as
the basis for the required privileges and permissions.

Beyond the user’s standard privileges, the following privileges are required for the user
that runs ProBase and the service user that runs any ProBase service (usually the
system user):
 Write access to the %CSCROOT% directories and subdirectories
 Full access to the registry branches
HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\CSC-W32
HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\DeviceInfo
HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\FilexFlash
HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ProBase
HKEY_LOCAL_MACHINE\SOFTWARE\Cryptera
HKEY_LOCAL_MACHINE\SOFTWARE\XFS
HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ProDevice/SSP
HKEY_USERS\.Default\XFS

August 2017 19
System services

Depending on the system and its devices, there may be ProBase processes that run as
Windows service in the LocalSystem account. In general, the services are configured to
start automatically so that their startup need no further attention. Only in the rare case
that a system service is to be started with the ProBase startup, the user need the
permission to start that service. This applies to the spooler if a legacy statement printer is
to be driven.

For granting the necessary permission we recommend the use of the subinacl tool from a
Windows resource kit. An administrator can use this tool to grant a particular user the
permission to start and stop a given service.

The required calls are:

subinacl /service spooler /grant=<user name>=F

In this context, <user name> is a placeholder for a particular user.

Trusted Platform Module

The communication with the RM3 and CMD-V5 cash device and the card reader device
V2CU1 is secured by cryptographic means.
To initialize this secure channel a personalized TPM module is mandatory 2on the PC
side. The necessary TPM driver stack is provided by ProBase. To prevent any
unintentional side effects please uninstall all other TPM software products prior to the
installation of ProBase. This includes the Infineon Professional Package.

For usage under Windows 10 the following registry values must be removed for proper
function:

HKLM\Software\Microsoft\TPM\BlockedCommands\List - delete 13 and 90

HKLM\Software\Wow6432Node\Microsoft\TPM\BlockedCommands\List - delete 13 and 90

For using the keys inside the TPM by the ProBase Platform, the TPM's software
configuration must be restored in advance to the device operation. This is performed by a
'restore' task that is initiated by default in the ProBase installation process and can be
manually called via T/SOP. Alternatively it is possible to configure an automated process
that is performing the 'restore' task at each system start (if necessary) plus an automatic
base key exchange for the RM3 technology based cash module, see configuration key
"BkeMode". The base key exchange with CHD is performed automatically.

It is important that the keys in the TPM are not tampered with, as they are created during
hardware production. Clearing the TPM in the BIOS will result in the loss of the correct
key. In that case the PC has to be exchanged by the service.

1 In contrast to the cash devices, regarding CHD no software upgrade kit will be

supported.

2 except for CMD-V5 retrofits

20 August 2017
Product characteristics Security issues

Port Numbers

Below, a selection of all "Port numbers" used in ProBase:

Diagnostics&Serviceability
- Port 4443 (tied to Localhost)
Used for communication between D&S and T/SOP (SSL secured http). This port is
bound to the network interface, on which D&S listens for incoming T/SOP
connections. In order to change the port definition, the following changes must be
performed:
1. Change key dsTsopListeningPort in file config.properties.
2. Change key tsopDsServerPort in file config.properties,
All keys must have the same value.

- Port 5050
This port is set up within the CrypTA library. It is bound to the external network
interface address (not reconfigurable). See the CrypTA documentation for changing
the port definition.

- Port 9090 (tied to Localhost)

This port is used by JMX server provided by D&S. The bounded network interface
depends on the setting of the configuration key dsJmxListeningAddress in the
configuration file config.properties. The port is bound to the local network interface
127.0.0.1 only, when dsJmxListeningAddress is set to 127.0.0.1. Otherwise the port is
always bound to the external network interface. In order to change the port definition,
the following changes must be performed:
1. Change key dsJmxListeningPort in file config.properties
All keys must have the same value. A change of this port has also impacts on other
applications using the JMX interface.

- Port 31424 (tied to Localhost)

Used for heartbeat requests between tstopstart.exe and T/SOP/D&S. This port is only
opened, when T/SOP is active. After a shutdown of T/SOP, this port is closed, too.
The port is bounded to the local network interface 127.0.0.1 (not reconfigurable). In
order to change the port definition, the following changes must be performed:
1. Change key tsopHeartbeatPort in file config.properties.
All keys must have the same value.

- Port 37917 (tied to Localhost)

This port is used for WnDSCon. It is bound to the local network interface 127.0.0.1
(not reconfigurable). In order to change the port definition, the registry key must be
modified:
HKLM\SOFTWARE\Wincor Nixdorf\CSC-W32\CurrentVersion\WNDSCON\PORT

-- Port 54321 (tied to Localhost) in the J/DD as an interface to the D&S.

August 2017 21
 Remote Support
With ProBase 1.3/00 a remote support feature (winrs.exe) has been introduced which can
also be started via T/SOP.
To enable winrs.exe to access the internet by default port 443 needs to be unlocked in
the local windows firewall.
Otherwise this feature cannot be used or a popup comes up when starting winrs.exe.

CSC-W32
- Port 22224 (default)
Internal communication port used in drivers for CINA3xA4x and CM3x coin deposit
modules

- Port 5757
Internal communication port used between CMD-V4 Device Handler and Thor board
software

Optical Security Interface

(These ports are default values and can be configured by the customer)
- Port 8001
This port provides a video overview and further status information (possibly OSG
alarm handling).

- Port 8002
This port provides a video stream of the portrait camera.

- Port 8003
This port provides a video stream of the pinpad camera.

- Port 8004
This port provides a local video stream of the portrait camera for ProView Video
Surveillance (deactivated by default).

- Port 8005
This port provides a local video stream of the pinpad camera for ProView Video
Surveillance (deactivated by default).

XFS
Used from ProBase 1.2/00 "Transport-System Sockets". Default PortNumber 50000 ff
See also the appropriate customizing parameter
(prodevice.spec30.TP_SOCKETS.PORTNUMBERBASE).

22 August 2017
Configuration basics
This chapter covers some of the basics of configuring ProBase/C. The ProBase/C setup
program leads to a ready-to-run system. Necessary are:

- the hardware configuration file (HW_CONF.INI) that describes the hardware system

- the customzing file (PROBASE.CUS) that describe the parameters customized for the
customer and/or the application

Windows registry

ProBase

The settings are stored in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ProBase\CurrentVersion

Name Description
Build Build version
Product Product name
Java-Home Reference to the JRE
JavaRuntimeLib Reference to the Runtime library of the JRE
XfsRoot Path to ProBase root directory

Environment variables

Variable Description

PROBASE_JAVAHOME Reference to the JRE

PROBASE_JAVARUNTIMELIB Runtime library of the JRE

CSCROOT Reference to ProBase root directory

XFSROOT Reference to ProBase root directory

August 2017 23
Automatic configuration
SETUP offers the automatic configuration of your system. That means all ProBase
depending registry entries, configuration files and so on are set automatically during the
setup procedure.
It is recommend to use this kind of installation, otherwise the system may not work as
expected and the system installation and configuration must be done manually.
To do the automatic configuration the hardware information file and optionally a
customizing file is used.

HW_CONF

HW_CONF.INI

This file is normally located on the so-called hardware disk shipped with the system. The
file contains all hardware information necessary to configure the ProBase software auto-
matically.

It is of critical importance that you use a file that contains exactly the hardware
i information of the system you want to install. If the hardware of the system has
been changed, the HW_CONF.INI also has to be changed.

The HW_CONF.INI must be located in %CustomControlFolder%/CONF during the

installation.

24 August 2017
Configuration basics Customizing

Customizing
If the default installation does not meet your needs then you have to customize the
installation. Central point for customizing is the file PROBASE.CUS.

PROBASE.CUS

The PROBASE.CUS file offers the possibility to adjust the ProBase settings to the
customer's and/or application's needs. The central customizing file is located on the
ProBase DVD in the directory DATA\RTC\INSTALL\CUSTOM. This file is used by default.

Before starting the setup procedure, copy the customizing file PROBASE.CUS
! from the ProBase DVD. Change only the values for the parameters which differ
from the default values. Make sure the file is available for processing the setup.

The changed PROBASE.CUS must be located in %CustomControlFolder%/CONF

during the installation.

In the following you find some information on customizing parameters in general and on
some basic parameters in details.
Lines, prefixed with "#" are not interpreted (comment lines).

ProBase settings

 Parameters, prefixed with 'xfsw32' are provided for special adjustments between
CSC-W32 and ProDevice settings.

Example:

xfsw32.CSC-W.CCDM_DEF_IMAGE_TYPE=BMP

This parameter overrules the settings made with

! cscw32.CSC-W.CCDM_DEF_IMAGE_TYPE=<value>

ProDevice settings
The parameters prefixed 'prodevice.' are the parameters for the ProDevice configuration.
The parameters in the following table are of special importance as they affect basic
installation and configuration settings.

Parameter Value Description

30 Installation of XFS Spec 3.0

prodevice.xfsmanager YES Installation of XFS Manager (default)

NO

prodevice.XfsSupportOfUsbCamera NO (Default)
YES

Example:

prodevice.spec.default = 30
prodevice.XfsSupportOfUsbCamera = YES

August 2017 25
 XFS Spec 3.0 settings
The settings for XFS Spec 3.0 are represented by the identifier "prodevice.spec30." in file
PROBASE.CUS. A sample configuration for ProDevice Spec 3.0 is available in
commented-out form in file PROBASE.CUS.

The detailed description of the customizing parameters for ProDevice is available in file
PROBASE.CUD, where all parameters are described with their syntax and the permitted
value range.

The description of the ProDevice Spec 3.XX registry parameters is to be found in the
ProDevice documentation in directory DATA\DOC\PRODEVICE on the ProBase/C CD.

CSC-W32 settings
The parameters are described in chapter "CUSTOM.CUS" of manual "Generation and
Tools" (DATA\DOC\CSCW32\generation_tools.pdf) of the CSC-W32 documentation.

26 August 2017
ProBase Setup
General
The ProBase Setup realized the custom installation and configuration of software
ProBase.

! For the ProBase installation you must log on with local administrator rights!

Always the SETUP.EXE program must be started to install the ProBase software. The
program is delivered with the Product DVD.

During a first installation, SETUP.EXE is started from the "data medium".

“Data medium” can be in this context any data medium (DVD, directory on the local hard
drive, USB stick, etc.). However, the setup can only be executed (during first installation)
without errors if the directory structure outlined below exists.

SETUP.EXE

+---DAS
+---RTC
+---SDK

For all subsequent MAINTENANCE installations SETUP.EXE can also be stared from
any directory. Recommendation: called from %ProBaseDestinationFolder%\INSTALL

It is not possible to install ProBase 1.3 over an older ProBase version.

i For more information see chapter “Maintenance, PRO_DEL”.

August 2017 27
Command line parameters
Setup Type

/ST=<[RTC], [RTC#DAS], [RTC#SDK], [RTC#DAS#SDK] >

This parameter defines the (S)etup (T)ype, or the components to be installed

Default: /ST=RTC#DAS

Only valid during "Fist installation" and ignored at "Maintenance" installation.

RTC RuntimeTime Components CUSTOMER

W32 layer, XFS layer, Firmware, private Java Runtime
RTC will always complete installed.

SDK Software Development Kit DEVELOPER

RTC and test tools, development modules (Lib´s, Includes etc.),
no Documentation.

DAS Diagnostic And Serviceability platform

Contains the complete diagnostic and service platform including T/SOP.

DAS will always be installed.

i
A de-selection is only possible if DAS is not required for the system
according to HW_CONF.INI.

ProBase Destination Folder

/PF=<Probase destination Folder>

Optionally, specifies the destination folder.

Default Windows 7(32bit): /PF=C:\Program Files\Probase

Default Windows 10(64bit): /PF=C:\Program Files (x86)\Probase

Only valid during "First installation" and ignored at "Maintenance" installation.

Windows 10: "C:\Program Files" is not allowed as a destination !

Custom Control Folder

/CF=<Custom control Folder>

This directory contains a maximum of 4 different subdirectories whose different contents
offer the possibility to customize and update ProBase software. The directory is freely
selectable but not the names of the subdirectories.
Without "/CF" only the ProBase components are installed. Custom options “/CO”
parameter are also ignored.

28 August 2017
ProBase Setup Command line parameters

Subfolders
CONF HW_CONF.IINI and optionally a modified PROBASE.CUS
PACK Packages (PRJ, HI)
PRJ = upgrade package (PRJ_<xxx>.z)
HI = HotInfo package (HI_<xxxx>.z)
VCUF File(s) that will be installed "version controlled"
VUUF File(s) that will be installed "version un-controlled"

/CO=<[A] [C] [P] [V] [U]>

This Custom Options are available when you specify the /CF parameter.

[A]utomatic configuration
Configuration according HW_CONF.INI located at %CustomControlFolder%/CONF.

[C]ustomizing
Based on your own "PROBASE.CUS" located at %CustomControlFolder%/CONF.

[P]ackages
Installs valid packages (e.g. PRJ_<xxx>.z , HI_<xxxx>.z) located at
%CustomControlFolder%/PACK.

Upgrade packages (e.g. PRJ_nnn.Z) contain upgrades for a certain ProBase/C build and
system. Update packages (e.g. HI_xxxx.z) contains HotInfo file(s) for a certain ProBase/C
build.

When packages les are placed in %CustomControlFolder%/PACK, setup checks whether

these packages are released for the build setup is going to install.
If a package doesn’t meet this condition, the package will not be used.

A package (e.g. PRJ_<xxx>.z respectively HI_<xxxx>.z) that has already been installed
and is still located in %CustomControlFolder%/PACK will not be installed again.

The installed packages are listed in the following registry key:

HKLM\SOFTWARE\Wincor Nixdorf\PROBASE\CurrentVersion\Components.

[V]ersion controlled
Installs single files (version checked) located at %CustomControlFolder%/VCUF.

Version [U]ncontrolled
Installs single files (version unchecked) located at %CustomControlFolder%/VUUF.

Only selected options are performed.

Examples
/CO=A automatic configuration based on HW_CONF
/CO=AC automatic configuration based on HW_CONF and customizing
/CO=C customizing (only useful in combination with A)
/CO=P version controlled upgrade(s) from %Custom control Folder%/PACK
/CO=V version controlled installation of the modules from
%Custom control Folder%/ VCUF
/CO=U version uncontrolled installation of the modules from
%Custom control Folder%/VUUF

August 2017 29
 /CO=PVU first all packages from "PACK" are installed in a version control manner,
then the modules from "VCUF" (version controlled) and finally all modules
"VUUF" (version un-controlled).

The setup searches for all Setup.exe versions in the packages and the VCUF
i folder. If a newer Setup.exe was found, the current active setup copies the most
current Setup.exe to the folder %ProBaseDestinationFolder%\INSTALL and
executes the program in this folder. Finally, this setup is located in the directory
%ProBaseDestinationFolder%\INSTALL.

A Setup.exe stored in VUUF is ignored.

If an older installation version is called during a maintenance installation, the

installation is aborted with the following message:

This ensures that the existing configurations or available functions, supported by

the last used setup.exe, are still supported.

targetfolders.ini
New modules must be assigned on the "targetfolders.ini".
This file specifies the target folders for new files and has the following structure:

[FILES]
<file name>=<target directory relative to %ProBaseDestinationFolder%>
<file name>=<target directory relative to %ProBaseDestinationFolder%>

Examples for "targetFolders.ini" entries:

[FILES]
new_driver.dll=dll
new_executable.exe=bin

Additional Options

/AO=<[B]>

[B] This option restarts the system at the end of the installation

30 August 2017
ProBase Setup Custom Control Center - Dialog

Custom Control Center - Dialog

All necessary parameters can be passed to the setup via the command line. If the setup
is started without a parameter, a dialog will be displayed which provides the possibility to
collect all necessary information.

The appearance of the dialog depends on the type of installation (first installation, or
maintenance). The result of this dialog is the command line with which the setup is
started.

First installation

A short information is stored for all available functions which can be displayed by pressing
the ? button.

 The selected checkboxes depends on the contents of the "</CF>" subdirectories.

 The activation of the buttons "HW_CONF" and "Probase.Cus" depends on the status
of the checkboxes (A)utomatic and (C)ustom.
 "PRO_DEL" and "Setup.log" are disabled during a first installation.
 With each selection the setup is automatically checked the validity.
 An incorrect command line cannot be created.
 In the "Command Line" field, the current command line is displayed, based on the
currently selected items.
 "Save CmdLine" stores the generated command line in the "Custom Control Folder".

August 2017 31
  The name of the command file is equivalent to the command line (no selection).

F|M = (F)irst or (M)aintenance

ST = (S)etup (T)ype (only at first installation)
PF = (P)roBase Destination (F)older (only at first installation)
CF = (C)ustom Control (F)older
CO = (C)ustom (O)ptions

After generation the file name can be changed.

 Example 1:
F.ST-RTC#[email protected]@CusControl.CO-ACV.CMD

(F)irst installation installs the components RTC and DAS to C:\Probase. Automatic
configuration using HW_CONF and Probase.Cus located at D:\CusControl\CONF.
Additionally files located at D:\CusControl\VCUF will be installed version controlled.

F first installation
ST-RTC#DAS Components RTC and DAS
PF-C@Probase ProBase Destination Folder (C:\Probase)
CF-Z@CusControl Custom Control Folder (Z:\CusControl)
CO-ACV Custom options automatic configuration, customizing and
version-controlled update

Example 2:
[email protected]

(M)aintenance installation: installs only files version controlled located at

D:\CusControl\VCUF.

M maintenance installation
CF-D@CusControl Custom Control Folder (D:\CusControl)
CO-V Custom option version-controlled update

Example 3:

[email protected]

(M)aintenance installation: installs all packages version controlled located at

D:\CusControl\PACK.

M maintenance installation
CF-D@CusControl Custom Control Folder (D:\CusControl)
CO-P Custom option version-controlled update from package(s).

32 August 2017
ProBase Setup Custom Control Center - Dialog

Maintenance

For a "Maintenance Installation", the CUSTOMER and DEVELOPER option fields as

well as the DAS checkbox are not available. Therefore an over installation is not
possible.

 The de-installation can be started directly from the "Custom Control Center" dialog via
"PRO_DEL".

 "Setup.Log" displays the current log file. The logfile is newly created during the first
installation. In “Maintenace Mode” all information from further installations is added to
the logfile.

 An activated "REBOOT" checkbox restarts the system after the end of installation.

August 2017 33
Finish dialog

At the end of the setup, the "Finish dialog" is displayed (not when the setup has been
started with a command line). Depending on the result, the dialogs regarding the display
texts and the setup status in the registry differ in
"HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ProBase\Setup"

Example

Finally reboot the system

 Setup completed successfully

HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ProBase\Setup Status = OK

Warning(s) occurred during installation

 Setup could not be executed without error.

HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ProBase\Setup
Status = Warning
HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ProBase\Setup\Warning
Listing of all “Warnings”

If the setup was terminated with the "Warning" status, the causes should be analyzed.
Details can be found in the "Setup.Log" file. After the cause (s) is corrected, the setup
should be run again.

<error message>

 Setup could not be completed due to a fatal error.

HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ProBase\Setup
Status = Error
HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ProBase\Setup\Error
<error message>

If the setup has finished with the "Error" status, a fatal error has occurred, details are
written to the Setup.Log file.

In this case the Setup leaves an undefined state. A complete uninstallation is

necessary!. After eliminating of the cause(s), you must run Setup again.

i You always have to reboot the system after a first installation.

34 August 2017
ProBase Setup Custom Control Center - Dialog

Setup information

Registry
The settings are stored in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ProBase\CurrentVersion

CustomFolder --> <directory>

Feature --> installed components - [RTC],<DAS>,<SDK>
InstallDir --> %Probase%Install
LastSetup --> Date, time from the last Setup
Status --> OK | WARNING | ERROR
Version --> SETUP.EXE version
WARNING --> ../probase/setup/warning (Warning(s)
ERROR --> ../probase/setup/error (Error message)

SETUP.LOG
In all cases, the installation process is logged in detail to the SETUP.LOG file.
This file is created during the setup process in the directory
%ProBaseDestinationFolder%\INSTALL (e.g. C:\ProBase\INSTALL).

If the installation fails, check the appropriate registry settings and/or the
i SETUP.LOG.

August 2017 35
36 August 2017
Abbreviations
BOF Basic Operating Functions
CEN Comité Européen de Normalisation (European Committee for Standardization)
CWA CEN Workshop Agreement
DiagServ Synonym and abbreviation for Diagnostic and Serviceability Platform
FDI Financial Device Interface
IP Internet Protocol
ISSS Information Society Standardization System
JRE Java Runtime Environment
JVM Java Virtual Machine
ProBase/C stands for the system platform ProBase/C
RK Resource Kit
RMI Remote Method Invocation
SOP Service and Operating
TCP Transmission Control Protocol
TPM Trusted Platform Module
TLS Trace and Logging System
XFS Extensions for Financial Services

August 2017 37
38 August 2017
Notes

August 2017
Published by
WINCOR NIXDORF International GmbH
33094 Paderborn
Germany

August 2017