4690 V6R5 Getting Started Guide-CSD3-0HN0-V5Memupdate PDF

V6R5 Getting Started Guide for CSD3 0HN0-V5
4690 V6R5 Getting Started Guide:

Question:
What is new in 4690 OS since the release of V6R4 and with the release of 4690 OS V6R5?
Answer:
This document is your go to guide for what has been delivered in the V6R5 delivery, including the CSDs
currently available for V6R5. Functions that were delivered in the V6R4 CSDs provided after the GA of
V6R4 are also listed.
Contents:
V6R5 Deliveries:
 Support for TCxWave™-Model A3R

 Support for TCx™700
 Support for TCx™300
 Support for TCx™Cash Drawer
 Support for new 2x20 Display
 Toshiba Development Kit 8 (TDK 8)
 Whitelisting
 File Integrity Monitoring Tools
 CMOS update Utility for TCx™System units
 ADXSITQL
 Launch utility for Python Editor IDLE
 CSD 0GM0
o HDD Power on Hours exceeded Message
o Scanner/Scale Inventory Data
o Whitelisting ASM
o TCx™Display – 15” Touch displays
o Support for the TCx™700-786 i5 model
o Support for the TCx™300-Model 380 (i5 model)
 CSD 0HL0
o Last updates to Java 6 JVM
o Mbrowser Kiosk mode
o Enablement for Toshiba 4690 Premium Enablement for Netop®
Page 1 of 26
“Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners."
 CSD 0HN0
o Support for the TCxWave™ Models 14C, 145, 15C, & 155
o CHANGE in Minimum terminal memory
V6R4 CSD Deliveries of new Function:
Since V6R4 was released in September of 2013 there have been 6 CSDs that provided new
function to the 4690 Operating System. The details of these new functions are documented in
the V6R5 version of the publications if applicable with the exception of Netop Support.
The deliveries for each CSD that provided new function is listed below:
 0D10 Deliveries
o Netop Support- See 4690 OS User’s Guide for details
o Support of 4810-350 as Controller and Controller/Terminal
o Javax.usb Support in Enhanced
o Printing of QR Barcodes
o Polish Programmer’s Keyboard Support
 0E00 Deliveries
o Ethernet Printer support
o TCx™Wave Model 120
o Addition of Dump to Remote Cold Boot
o Cold Boot During Staged IPL
o Support for TCx™Displays
o Font updates
 0E20 Deliveries
o QR Barcode Scanning
o Directory Services support for Referrals
o Java Plug-in Extension
o Full Profile Backup of Mbrowser
 OF00 Deliveries
o Support for new 2x20 display
o Alternate method for 6140 dump and clear NVRAM operations
 0F10 Delivery
o Updates to PW encryption
 0F20
o Enable Netop Host 12.20 include Host ID <hostname>@<storenumber>
Page 2 of 26
New hardware supported is in the Getting Started Guide and the Controller Matrix.
Summary of New Features in V6R5
New HW supported with V6R5 release:
 TCxWave™ model A3R- The new TCx™Wave A3x models introduces a compact design,
perfect for where retail space is a premium. The Getting Started Guide for the
TCxWave™ T0S412802 will provide you additional information.
 TCx™700 models 4900-746,C46, 786 and C86- These new models deliver up to 30
percent more performance with faster processing and more storage options to drive the
most demanding applications. The Getting Started Guide for the TCx700 will provide
you additional information on the TCx™700 models. TOS889321
 TCx™300 models 4810-36x and 37x – The-These models bring smarter store solutions to
small and midsized retailers who need a high-performing, energy-efficient point-of-sale
system with a small footprint—and at the lowest cost. Getting Started Guide for the
TCx™300 will provide you additional information on the TCx™300 models. TOS893250
 TCx™Display family has three new models 6149- 5SR, and 5SD are available in a 15 inch
(4:3) format with projected capacitance touchscreens.
 TCx™300-380 support with 0GM0 CSD. The 380 model adds an i5 processor to the 300
family of systems.
 TCxWave™ models 14C, 145, 15C, & 155- These models replace the previous TCxWave
models 100, 120 and A3R. For additional information on these TCxWave models see the
Getting Started Guide for TCxWave T0S412802.
4690 V6R5 offers the following new features:
 Toshiba Development Kit 8(TDK 8) – With V6R5 Toshiba is introducing the Toshiba
Development Kit 8 (TDK 8), derived from OpenJDK 8 . V6R5 continues to support Java 2 in
the 4690 Operating System but now TDK 8 will be the Linux default. Providing continued
support of Java 2 will allow retailers to move from their legacy Java 2 applications to a more
robust and powerful platform.
NOTE: If you currently use a Java 6 application, the Mbrowser Java Plugin or RMA please
read the details for Migration below.
 File Security - A new 4690 configuration option, Whitelisting. is a security function that
is now available with 4690OS enhanced mode. Whitelisting in this case specifically refers
to a security configuration where an operating system, such as 4690, is only allowed to
Page 3 of 26
access or execute files that are on a list of “known good” or “trusted” files. It helps
prevent modified or compromised files from being introduced to a system. Files are
hashed as they are accessed by the system. The file hashes are compared with the
whitelist(s) installed on the system. If a file is not found in the whitelist, the system may
log an error or prevent access to the file depending on configuration.
Related to whitelisting are a set of file integrity monitoring tools. These tools scan the
files on a system and generate a scan report. This report can be sent back to the
enterprise and compared with a whitelist to find new or modified files.
0GM0: With the CSD we will now provide a whitelist file for each of the file contents of
the CSD. This file will need to be downloaded from the same location as the CSD
package if you have implemented Whitelisting in your stores. See the V6R5 User’s
Guide, Chapter 1 for additional information on ASM and Whitelisting. Updated sample
include and exclude files are also available on the Enhanced Supplemental in the
4690opt folder.
 CMOS update Utility - This new CMOS update utility will allow retailers to customize
and update the CMOS settings of the new TCx™300, 700 and Wave system units.
 Additional functions added with 0GM0 CSD:
o Scanner/Scale Inventory Data: With this CSD, there are new DirectIO commands
that will allow Scanner vendors to report health and maintenance of their
scanner devices. This data will be reported through RMA if the DirectIO
commands are recognized by the scanner model. This may require the retailer
to update the scanner firmware
o New Event for Message 872 Logged: An E104 for message W872 will be logged
when a SATA HDD has exceed the recommended maximum Power on Time. Max
Power on for these HDDs is 43000 hours. Unique data will log POH followed by
the number of hours on for the HDD indicated.
 Additional function added with 0HL0 CSD:
o Mbrowser Kiosk Mode: With this CSD, there is a new parameter for Mbrowser
that allows the Mbrowser to be launched without a URL field. See the 4690 OS
User’s Guide for more details.
o Enablement for Toshiba 4690 Premium Enablement for Netop®
o This is the last delivery with the Java 6 JVM and contains the last security
updates for Java6. This package will not be available once 0HN0 is.
o W620 message updated to display the process ID.
o RMA 3.2.0 included.
Page 4 of 26
 Additional changes with OHN0 CSD:

o Java 6 will not be in the package, but it will not be removed from your system.
Hardware Requirements for V6R5- Controllers
Minimum/Maximum controller memory (Classic Mode) - 256 MB/1 GB

Minimum/Maximum controller memory (Enhanced Mode) - 512 MB/16G utilized with 32G
tolerated with CSD1 (chkdsk command will report 16G of memory regardless of amount of
memory installed over 16G)
NOTE: If you intend to use the Mbrowser, Java 6, TDK8 or other Linux programs the minimum
memory is 1GB of RAM. Your unique software stack may require more memory.
Maximum controller memory used by 4690 OS is 1GB. In Enhanced Mode, the hardware
abstraction layer can make use of code above the 1GB limit when running Java 6, TDK 8 or
Python applications such as RMA or Mbrowser.
1G of Memory is required for V6R5 Classic systems that are going to use the C2E utility to move
to enhanced. If you have not converted your controllers from Classic to Enhanced, and you are
on a V6R3 or lower release, do the conversion before you migrate to V6R5.
Controller NVRAM is required for Enhanced and Classic controller modes. NVRAM is integrated
in SurePOS ™700 system up to the 4900-xx5s. TCx ™700s-4900-xx6 require the Riser Plus card
for NVRAM support. SurePOS™ 300, TCx™300s, System x and Blade Servers require an NVRAM
card. The TCxWave™ 100, 120 and A3X requires the 4G SD card for NVRAM support. The new
TCxWaves models, 14C, 15C, 145, & 155 require a 64G SSD minimum for NVRAM.
Enhanced controllers only support Ethernet LAN communications and requires the speed of the
network to be 100M or higher.
Loop and Token Ring are no longer supported for Classic or Enhanced.
Configuration Options
Enhanced controllers can be used with Classic controllers in an MCF environment. When
controllers are mixed, the Master Controller should be Enhanced Mode to support the DST
function of Enhanced.
The following table shows controller and controller/terminal models supported in Classic
and/or Enhanced Mode on 4690 OS V6R5
Page 5 of 26
Model Enhanced Classic Controller / Controller /

Controller Controller Terminal Terminal
Enhanced Classic
TCxWave™: 6140-A3x,14C,145, X X
15C,155
TCx™700: 4900-746,786 (3 processor X X
options for 786 model)
TCx™300:4810-36x, 37x, 38x X X
TCx™700: 4900-C46,C86 (Both come X
with 4G of memory base)
SurePOS™ 700: 4900-745, 785 X X
SurePOS™ 700: 4900-C45, C85 X
SurePOS™ 300: 4810-35x X X
SurePOS ™700: 4800-784 X X
SurePOS ™700: 4800-C84 X
SurePOS™ 700: 4800-C41, C42, C43 X X
SurePOS ™700: 4800-741, 781, 722, X X X X
742, 782, 723, 743, 783
IBM System x3100M5 5457 X
(SATA and
SAS models)
IBM System x3200M3 7327, 7328 X
(SATA and
SAS models)
IBM System x3200M2 4367, 4368 X X
(SATA and (SATA only)
SAS models)
IBM System x3200 4362, 4363 X X
HS23 Blade 7875-A1x X
Page 6 of 26
HS12 Blade 8014,8028 X (SATA and

SAS Models)
HS20 Blade 8843 X X
BladeCenter S Chassis 8886 X X
BladeCenter E 8677 X X
Note: The eServer xSeries 206M Server is not supported on 4690 V6R5
For more information, see:

4690 OS Controller Matrix article TOS832937 located in the Knowledgebase at
http://www.toshibacommerce.com/support.
Search the Point of Sale articles with the keyword CONTMATX or TOS832937
Hardware Requirements—Terminals
Memory Requirements
Classic Mode
Minimum terminal memory with Java™ - 128 MB
Maximum terminal memory - 512 MB (for those 4694 and SurePOS™ 700 terminals that can
support 512 MB)
Enhanced Mode
Minimum terminal memory - 512 MB TERMINAL NOW REQUIRES 1G minimum.
NOTE: If you intend on running Mbrowser, Java, or TDK8 or other Linux programs the minimum
terminal memory required is 1GB of RAM.
Maximum terminal memory - 16G with CSD 1 0GM00 will be utilized with 32G tolerated in
terminals. Memory beyond 16G installed on terminals will not be utilized by V6R5.
Terminals that support

Enhanced Mode Shipped Memory Max Memory Video Memory Default
4800-741 256M 2G 8M
4800-781 512M 2G 8M
4800-722 & 742 256M 2G 8M
4800-782 512M 2G 8M
4800-723 256M 2G 16M
4800-743& 783 512M 4G 64M
4800-784 1G 8G 64M
Page 7 of 26
4900-745 & 775 1G 4G 32M

4900-785 2G 8G 32M
4810-35x 1G 8G 32M
6140-100,120 2G 8G 64M
6140-15C, 155 4G 32G++ 64M
4900-746 2G 16G 32M
4900-786 4G 32G 32M
4810-36x,37x, &38x 2G 16G 32M
6140-A3x 2G 8G 64M
6140-14C & 145 4G 32G++ 64M
++ 16G DIMMS require a RPQ
NOTE: Your solution stack may require additional memory for your terminals. When ordering
memory for your terminals ensure you have enough memory to cover your future solutions as
well as your current. Dual SIGUI running in Java6 or TDK8 will require a minimum of 2G of
memory for the terminals.
In Enhanced Mode, Linux programs such as Java 6, TDK 8 and Python, the 1GB limit no longer
applies as these applications can use memory beyond the 1G limitation of Classic.
Supported Terminals
The following table shows terminal and controller/terminal models supported in Classic and/or
Enhanced Mode on 4690 OS V6R5.
Note: The 4800-723 is supported in Enhanced mode. While the Enhanced Controller/terminal
configuration is supported, it is not recommended.
Since 4690 OS V6R3 the OS no longer supports loop attached or token ring attached terminals.
Page 8 of 26
Model Enhanced Classic Controller / Controller /

Terminal Terminal Terminal Terminal
Enhanced Classic
*TCxWave™ 6140-100, 120 X
*TCxWave™ 6140-A3R,14C,15C,145, and X X
155
*TCx™300: 4810-36x, 37x and 380 X X
*TCx™700: 4900-746 and 786(3 X X
processor options available)
*SurePOS ™300: 4810-35x X X
*SurePOS ™700:4900-745, & 785 X X
*SurePOS™700:4900-775 X
SurePOS ™700: 4800-741, 781, 722, 742, X X X X
782, 723, 743, 783
SurePOS™700: 4800-784 X X
SurePOS™700: 4800-721 V6R2 only X
SurePOS™ 700: 4800-73x, 75x, 202, 242 X X
4694-all models-Ethernet only X X
*These terminals support Network boot of Diagnostics
Configuration Options
Enhanced terminals can be used with Classic or Enhanced controllers and Classic terminals can
be used with Classic or Enhanced controllers. Terminals can be a mix of Classic and Enhanced.
Enhanced terminals only support Ethernet LAN communications with a network speed of 100M
or higher.
Page 9 of 26
Installation and Migration
4690 V6R5 Packaging and Media
4690 V6R5 is distributed with the following media:
 V6R5 CD Volume 01—Install

 V6R5 CD Volume 02—Migration
 V6R5 CD Volume 03—Enhanced Supplementals with Optional Programs
 V6R5 CD Classic Supplemental
When 4690 V6R5 PID 5639-P70 is ordered with feature code 5889, the media listed above will
be shipped. CD Volume 01 and the Classic Supplemental are bootable. CD Volume 02 is the
migration CD and is not bootable. This is used to migrate existing 4690 V6R4 Classic and
Enhanced systems to V6R5 Classic or Enhanced and the 4690 Features. See the 4690 Users
Guide for information on converting a store from Classic to Enhanced. CD Volume 03 is the
Enhanced OS Supplementals and is bootable. This CD will also contain the 4690 Optional
Programs. The Optional Programs provide sample files for Python, ADXZUDIR and an Idle.bat
file to allow an easy launch of the Python editor IDLE.
Note: When ASM is available for download from the Toshiba Site there will now be two CDs for
the package: the non-bootable ASM package and the Bootable Enhanced OS Supplementals
with Optional Programs. Starting with 0GM0, there will be a Whitelist file also available for
download for those retailers that have enabled whitelisting.
Note: 1G of memory is required in a Classic Controller using the C2E utility for conversion to
Enhanced.
The V6 Classic supplemental CD is used to boot a controller with the V6 Classic Mode
supplemental OS. An alternative Enhanced Mode Supplemental CD for use with Enhanced
Mode systems can be created using the Enhanced Menu Options on the 4690 V6 Enhanced
controller or the BURNISO option, which is documented in the 4690 OS User’s Guide. Use the
Enhanced Supplemental CD only with Enhanced Mode systems, the Classic Supplemental CD
only with Classic Mode systems.
Reminder, the Enhanced Supplemental CD needs to be the same OS level as the system that is
installed on the HDD.
Installation
Installation of the operating system begins by booting the controller from the V6R5 base install
Page 10 of 26
CD (Volume 01) and selecting "Install 4690 OS V6R5" from the boot menu. This process will
install 4690 V6 in Enhanced Mode on the controller.
Installation of V6 Classic Mode is not supported.
See the 4690 OS Planning, Installation and Configuration Guide for additional information.
Migration
4690 OS V6R5 supports migration to V6R5 Classic Mode from 4690 V6R4 Classic.
4690 OS V6R5 also supports migration from V6R4 Enhanced Mode to V6R5 Enhanced Mode.
Both local and remote migration options are supported.
A local migration begins by inserting the 4690 V6R5 migrate CD (Volume 02) then initiating
migration through the "P:\4690migr\start" command provided on the CD.
NOTE: If you currently use a Java 6 application, the Mbrowser Java Plugin or RMA then you
must follow these pre-migration steps or your programs may not execute.
You will need to configure the adxjava6 and adxjava6_system extensions on a V6R4 system
before migration. 4690 OS V6R5 provides versions of these extension files specifically for
migration in the 4690OPT directory of the Enhanced Supplemental ISO image (they do not
contain any program code). When the system is migrated to V6R5 these extensions will be
replaced by the extensions containing Java 6.
To install these extensions:

1. Place the V6R5 Enhanced Supplemental CD into the CD drive of your V6R4 system.
2. Extract the file JAVAEXR4.ZIP to adx_spgm: by using ADXZUDIR.
To do this, run the following command on the command line:
"adxzudir -x p:\4690OPT\javaexr4.zip adx_spgm:"
3. This will create the following files:

ADXXTSJ6.DAT
ADXXTSS6.DAT
ADXXTSJ8.DAT
4. Select the extension for Java 6 ADXXTSJ6.DAT and ADXXTSS6.DAT for the controller if
you are using RMA, Mbrowser Java Plugin or any other Java 6 application on the
controller. Activate configuration and reload the controllers.
5. Select the extension for Java 6 ADXXTSJ6.DAT and ADXXTSS6.DAT in terminal Load
Definition for the terminals if they are using Mbrowser Java Plugin, or SIGUI6 on the
terminal. Activate Configuration and reload the terminals.
Page 11 of 26
See the 4690 OS Planning, Installation and Configuration Guide for additional information about
Migration.
TCx™700
The award-winning 700 Series is being transformed to embody some of the new design
elements introduced by Toshiba Global Commerce Solutions. The new TCx™700 will continue to
be Toshiba's most powerful point-of-sale system, delivering maximum performance,
serviceability, energy efficiency and adaptability to drive today's consumer centric store
environment. New design elements create a unique brand experience through the store
technology to optimize each customer engagement.
TCx™700-model-786:
The 4900-786 offers a choice between three high performance Intel processors. The Intel Core
i5 4590OS (with CSD 0GM0), Intel Core i3-4330 and the Celeron Dual Core G1820, 500 GB HDD,
64GB or 128GB M2 SSD drive options, 4GB base memory expandable to 32GB and integrated
RAID support standard.
TCx™700 model 4900-746:
The model 746 often referred to as the value model maintains a high level of performance with
the Intel Celeron G1820TE (dual core) processor. This is a significant improvement over the
previous Intel Celeron 440 processor. The 4900-746 offers an Intel Celeron Dual Core G1820TE,
2 GB DDR3 base memory expandable to 16GB. Drive options include 500 GB SATA HDD, 64GB
or 128GB SSD M2 drives.
Controller Offerings C46 and C86:
The controller offering provides a comprehensive back-office hardware solution designed for
the high demand retail environment. The controller is based on the performance model,
equipped with a standard configuration that adapts to a server environment by including an
Page 12 of 26
optical drive and removing the SurePorts. The Intel Core i3 4330 and the Celeron Dual Core
G1820 and with CSD 0GM0 the Intel Core i5 4590OS. The 500 GB SATA HDD standard, 4 GB
DDR3 base memory and no SurePorts. In the US the system ships with a PC 101-key keyboard.
To support 4690 V6R5 OS all of the above units will require the Riser-Plus Option to be
installed.
The TCx™700 will display ‘4690 Terminal Clear’ briefly on the display during system start up.
This will allow users to clear the terminal number in NVRAM without requiring a second boot of
the system unit.
When this button is selected with a touch or mouse the contents of terminal number will be
cleared from NVRAM. This is only intended for stand-alone terminals. Controllers or
Controller/Terminals will be forced to PXE boot if this is pressed during IPL but the node ID will
not be cleared.
4690 will not support the My Image feature TGCS recovery option of the TCx™700s.
For additional details on the TCx™700s see the TCx™700 Getting Started Guide located with our
other publications on the Customer Portal TOS889321
TCx™300-4810-36x, 37x and 380 Support
The new Toshiba TCx™300 is being offered as the technology upgrade and replacement of the
existing Toshiba SurePOS 300 platform. Available in two models the new Toshiba TCx™300s
include powerful and energy efficient Haswell generation Intel processors, Celeron G1820TE for
the 36x model and i3 4330TE for the 37x, and with the release of CSD 0GM0, model 38x with
the Intel Core i5 4570TE, making the new TCx™300 the most powerful 300 family product yet.
All models of the TCx™300 family will be supported on 4690 V6R5 as a terminal, controller or a
controller/terminal.
Page 13 of 26
The NVRAM Riser option is required to support 4690 V6R5. The dump switch, as with the
SurePOS™300, will be provided on the back of the unit.
TCx™300 will display ‘4690 Terminal Clear’ briefly on the display during system start up. This
will allow users to clear the terminal number from NVRAM without requiring a second boot of
the system unit. This function is for stand-alone terminals only.
For additional information about the new TCx™300 systems, please see the TCx™300 Getting
Started Guide located on the customer portal with the other publications or TOS893250 on the
knowledgebase.
Page 14 of 26
TCxWave™ – 6140-A3R, 14C, 145, 15C & 155 Support
The V6R5 introduces newest member of the TCx™Wave family, the 6140-A3x, now provides
retailers seeking the benefits of its innovative design and projected capacitive touch technology
a smaller footprint option for spacing and placement alternatives as a terminal, a controller or a
controller/terminal.
Supported in multiple form factors, the 6140-A3x TCx™Wave can be docked to its base and
function like a traditional integrated POS platform OR undocked and mounted to the newly
offered table top stand or a standard VESA mount via the VESA 100mm attach points on the
back!
The TCx™Wave A3x model incorporates a powerful liquid cooled, Intel J1900 2.0GHz Quad Core
Celeron processor, providing enough power to run the most demanding retail applications
while staying energy efficient.
The optional POS Base incorporates a unique translation mechanism, allowing the unit to be
easily adjusted and repositioned for user preference. When coupled with the enhanced glare
reduction capabilities of the display glass, the system affords superior glare reduction and view-
ability over a wide range of varying light conditions.
As with the 6140-100 and 120 models the 4G SD option must be installed to provide NVRAM
support for 4690 OS.
A second display is supported for the A3R with the release of CSD1 0GM0.
The new TCxWave models 14C, 145, 15C and 155 models do not require a SD card to be
installed for NVRAM. They do require the 64G SSD, or larger, be installed for use as NVRAM.
All four of these models can be configured as a Controller, as a Terminal and as a
Controller/Terminal. These models are only supported 4690 V6R5 0HN0 and higher Enhanced
OS. The TCxWave 145 and 155 models have i5 processors. The 14C and 15C models are Celeron
models.
Page 15 of 26
These new models will require the user to enter the System Setup screens during IPL and
change the CMS settings to Enabled.
4690 Supports up to 16G of memory installed.

The support for memory beyond 16G will require a RPQ.
Limitations: The 14C, 15C, 145 and 155 models will not support a second display or any Power
Management functions. These models will not honor the power button configuration settings
in the OS Terminal Load definition for Shutdown, Suspend or Dump options as it can only
function as a dump button.
It is recommended that the power button be disabled through the BIOS screens to avoid
unintentional dumps to happen. The power button will always allow the unit to be powered on
when it is powered off.
This unit does come with a dump button that is on the left side of the display. A dump can be
obtained with a quick insertion of a paper clip into the dump button. Holding the dump button
in for longer than 5 seconds will cause the unit to power off.
The TCxWave™ supports the USB Cash drawer as well as an optional integrated 2x20 and MSR
Module.
Only one cash drawer will be supported on the TCxWave™.
The TCx™Wave has enhanced control buttons and panel indicator LED’s, located on the lower
right of the display. To afford maximum flexibility, the appearance and behavior of the control
panel indicators is now configurable in CMOS Setup which will allow the retailer to disable any
of these LEDs.
From right to left, the following three control buttons are LED backlit icons and are projected
capacitance touch enabled.
Page 16 of 26
 Power – provides standard ACPI power button functions and indicates system power
state. This is configurable in the Terminal Load Definition
 Brightness + Increase LCD brightness (4690 Does not use the Brightness Buttons)
 Brightness – Decrease LCD brightness
To the left of the three control buttons is one panel indicator LED:
 System Activity (HDD/LAN) – Operation configurable, see the TCx™Wave Getting Started
Guide for more detail.
Dumping the TCxWave™:
The TCxWave™ A3R model, like the previous models of TCxWave™, does not have a physical
dump button. To obtain a memory dump the TCxWave™ when the power button was not
configured to be the dump button in the Terminal load definition, a keying sequence has been
provided.
Activate the Dump Button sequence to start a memory dump of the system unit. The sequence
does not require that the Power Button is enabled to be successful. Please note, however, that
these are Capacitive Sensitive buttons and typically need one swipe to “activate” the buttons,
at which point all BIOS-enabled button will light up a bright blue. Once the enabled buttons are
bright blue, the sequence can be activated:
Press the Power Button and – (minus) Brightness Button for 3 seconds until the
+ (plus) Brightness Button blinks.
Press the + (plus) Brightness Button within two seconds and the system will dump.
This key sequence can also be used on the 14C, 15C, 145 and 155 models of TCxWaves™
regardless of the power button being disabled in BIOS or not.
Page 17 of 26
Clearing the terminal number:

This same sequence used to dump the TCxWave™ can be used to Clear NVRAM on the terminal
during the PXE Load process at U005.
The 4690 Terminal Clear button presented during the power on sequence can also be used to
clear the terminal number from the NVRAM if being used as a stand-alone terminal. This is not
intended for use when configured as a controller or controller/terminal and will force the unit
to PXE boot.
Since the Power Button for a TCxWave™ can be disabled in the CMOS settings, there is a keying
sequence that will allow the user to enable the Power Button to allow for the TCxWave™ to be
powered off.
The Key Sequence to enable the Power Button for the 6140-A3R for the model:
(1) Hold the + (plus) and – (minus) Brightness Buttons

concurrently for 5 seconds until the Power Button blinks
(2) Press the blinking Power Button (after approximately

2 seconds, the Power Button Light will stop blinking and
you must return to step 1)
(3) The Power Button will now be enabled (solid light)

and can be pressed to activate the function defined
for the Power Button (after approximately 5 seconds,
the Power Button will disable again and you must start over)
This sequence is not supported on the 14C, 145, 15C and 155 models.
Page 18 of 26
Toshiba Development Kit 8 (TDK 8)
Linux Java Application Support (Java 6 and TDK8)
OS4690 Version 6 Release 5 will introduce a new tool kit to support Linux Java applications,
Toshiba Development Kit 8 (TDK 8). With OS4690 Version 6 Release 5 we will continue to
provide support for Java 6 JVM as well as TDK 8. Having both available will allow for more time
for applications to be potentially modified and tested to run on TDK 8. Note, however, that
support for Java 6 is time limited. TGCS will not support Java 6 after July 31, 2017. Java 6 will
not be included in any 4690 V6R5 package after this date. ASMs to your system after the July
31, 2017 will NOT remove Java6 from your system but it will not contain any update code for
Java6 either. 0HL0 is the last package with Java 6.
The Java 6 JVM is the same as was provided in earlier versions of 4690, specifically it is an IBM
JVM. The TDK 8, on the other hand, is based on OpenJDK 8. The reason both are provided is
because the vendor change and large jump in version number could cause issues with Java
applications.
Migration from earlier releases of 4690
Java 6 support has been provided in V6R5 to give customers ample time to migrate their Java
applications to Java6. In particular, configuring Java 6 to be the system Java application
launcher will allow applications to continue to be started as expected. If your applications will
run either on Java 6 or TDK 8, then there won’t be a problem. However, this could make
migration more difficult. In particular once you migrate to V6R5, the applications won’t run
until you configure the new adxxtsj6.dat and adxxtss6.dat extensions, activate configuration,
and reboot the controllers/terminals.
To help streamline the migration process, versions of the new Java extensions will be provided
for use on V6R4. These extensions do not contain any java code. Their only function is to allow
you to modify your configuration to use the extensions prior to migration. If the extensions are
configured prior to migration, the operating system will detect the updated versions of the
extension files in V6R5 and make the configured versions of the extensions available. The
extensions will have the same names and be configured in the same ways as the V6R5
extensions. For example if none of your applications will be ready to run under TDK 8, you can
configure the adxxtsj6.dat and adxxtss6.dat extensions on all of your terminals.
The files provided are:

 adxxtsj8.dat – TDK 8 (adxtdk8)
 adxxtsj6.dat – Java 6 (adxjava6)
 adxxtss6.dat – Make Java 6 the system Java application launcher (adxjava6_system)
Page 19 of 26
If you have BAT files or other programs that launch Java6 directly, they likely currently run
javaebin:java.386 directly. If these programs will continue to require Java6 after migration to
V6R5 you’ll need to install adxxtsj6.dat in V6R5 for them continue to work, but have two
choices on how to launch the program:
1. Modify the BAT file or other program to use javaebin:java6.386
2. Install adxxtss6.dat in V6R5 and continue to use javaebin:java.386
Because Java 6 will be going out of support soon, it will be preferable in many cases to leave the
system Java launcher set to TDK 8. This is especially true in cases where both Java6 and TDK8
will be is use on a controller. To allow BAT files and other launchers to be modified to use
java6.386 prior to migration, a version of this program is being provided on V6R4 as well. When
the V6R4 version of the adxjava6 extension (adxxtsj6.dat) is installed, it installs the program
javaebin:java6.386. This program simply runs javaebin:java.386 with the parameters it is
passed. The program will be replaced with the correct version of java6.386 upon migration.
The migration extension files are provided with V6R5 in the file 4690OPT/JAVAEXR4.ZIP on the
4690 supplemental OS CD. To extract these files on 4690 V6R4, run the command:
adxzudir -x p:/4690opt/javaexr4.zip adx_spgm:
This will extract the files to adx_spgm:. If you wish to extract these files on another operating
system, unzip them using a standard zip tool and transfer them to 4690.
Note: If you make use of these extensions, an extra step is required if you wish to cancel
migration. In addition to following the other documented steps, you must also manually copy
the V6R4 versions of the java extensions onto the controller. This must be done before
rebooting the controller, otherwise the V6R5 version of the java extensions may interfere with
the proper operation of Java 6 in V6R4.
See the 4690 V6.5 Programming Guide for additional information on using TDK8 in the 4690 OS
system. Additional application development tips can also be found in the 4690 Programming
Tips document TOS892177 on the Toshiba Portal.
Overview - Whitelisting
Whitelisting is a security function provided by 4690OS in enhanced mode. Whitelisting in this
case specifically refers to a security configuration where an operating system, such as 4690, is
only allowed to access or execute files that are on a list of “known good” or “trusted” files. It
helps prevent modified or compromised files from being introduced to a system. Files are
hashed as they are accessed by the system. The file hashes are compared with the whitelist(s)
installed on the system. If a file is not found in the whitelist, the system may log an error or
Page 20 of 26
prevent access to the file depending on configuration. The actions taken by the OS depend on
the mode (see below). Only files accessed by 4690 can be checked by whitelisting.
1. Report Mode – In report mode, a trace entry is written for all files opened in
read or execute mode. File access is always allowed.
2. Report Exception Mode – Exception mode is similar to report mode except that
entries may also cause a 4690 error message (W898) to be logged. Access to files
matched by block rules will also cause a 4690 error message to be logged. As
with report mode, file access is always allowed
3. Protect mode – Protect mode is identical to exception mode except that in those
cases where a file access error message (W898) is logged access to the file is also
prevented. Specifically the open request is rejected if the hash does not match, if
the file is blocked or missing from the whitelist.
File Integrity Monitoring Tools

Related to whitelisting are a set of file integrity monitoring tools. These tools scan the files on a
system and generate a scan report. This report can be sent back to the enterprise and
compared with a whitelist to find new or modified files.
There are three 4690 tools that provide support for whitelisting and file integrity monitoring:
 ADXWLSCN – Scans file on a 4690 system. Can be used to generate a whitelist and to
scan a system for monitoring file integrity.
 ADXWLRPT – Compares the scan results file from a system scan with one or more
whitelist files and reports on new or modified files.
 ADXWLUTL – Various utilities used to update, validate, and create the files used in
whitelisting and file integrity monitoring.
It is presumed that most retailers will generate white list(s) on “trusted” 4690 system set up in
a lab. These whitelist files would be kept in a trusted location on the enterprise network. As
scans are done in stores, the scan report files will be compared to the whitelists. Whitelist files
for customer files and other retail applications can be generated in the same fashion (from a
trusted system) or manually. Manual whitelist file generation could be useful as part of build
processing for a software program.
Using Rules to Match Filenames
Page 21 of 26
Filename rules are used to determine which files are hashed during whitelist file generation and
the file integrity scans. There are three types of rules, include rules, exclude rules, and block
rules. The list of files to be matched includes all files matching the include rules that do not also
match the exclude rules. Logically speaking, in order to determine what files are important the
program does the following:
 Start with a list of all files on the system

 Ignore any files that match one or more of the block rules
 If there are any include rules, ignore any files that do not match any of the include rules
 Ignore any files that match one or more of the exclude rules
 Any remaining files are considered important (and are hashed)
By default, there are no rules. In this case, all files are considered important and will be hashed
unless otherwise excluded or blocked.
The valid rule types are:
 include – The rule is an inclusion rule. If a path matches this rule, it is scanned unless it
also matches one of the exclude rules. The filespec is the path to match (see paths
below).
 exclude – The rule is an exclude rule. If a path matches this rule it is not scanned. The
fileSpec is the path to match.
 block – The rule is a block rule. During a scan by ADXWLSCN this is treated like an
exclude rule. A hash will not be generated for the file.
Additional information for Whitelisting and File Integrity Monitoring tools can be found in
Chapter 15 of the 4690 6.5 User’s Guide.
CMOS Utility
This new function for Toshiba’s TCx™300/700 and TCx™Wave models will allow a retailer to
save the CMOS settings of a terminal and apply those settings to other terminals of the same
machine type, model and running the same BIOS level. This is built upon the same process that
allows the retailer to update the firmware of their OEM devices or the printers, ADXTAL4L.286
which runs on the controller. It loads applicable terminal application to designated terminals.
ADXTAL4L.286 is an existing 4690 program, currently used to launch printer firmware update
programs. We added two new parameters (-S and -U) for it to launch CMOS update programs
as well.
Page 22 of 26
Saving CMOS Settings:
With the ADXTAL4L –S command the TMCMOSSA.386 will be run on the terminal that is in the
ADXTALTF.DAT file. This application is used to save the terminal’s CMOS settings to the
controller in directory of the terminal’s primary controller.
C:/ADX_SDT1/<machinetypemodel>.<biosversion>
The ADXTALTF.DAT file should only have one terminal number in the file.
Note: The process of saving terminal CMOS settings is not intended to, nor likely to, run in a
store. The purpose and intent is for the customer to set up a terminal at their main site with the
CMOS options they desire and to save off its settings there. These can then be sent to the
stores and then distributed to all controllers in the store. The utility can then be executed at the
store.
Updating CMOS Settings:
When ADXTAL4L –U is executed the terminals listed in the ADXTALTF.DAT file will load
TMCMOSUP.386. This application will update the CMOS setting with the file from the primary
controller.
C:/ADX_SDT1/<machinetypemodel>.<biosversion>
This way a large number of the same model terminals can be updated at one time in a store or
across an enterprise.
In RCP:
Follow standard 4690 RCP usage, the return codes are documented in the RCP status file
ADX_SDT1:ADXCSHSF.DAT as always.
Additional information can be found in the 4690 V6R5 Communications Programming

Reference in Chapter 5, page 161 with the RCP commands. This should not be confused with
the previous capabilities that already exists with the Remote Terminal Utility (RTU) for the
SurePOS product line and is documented in the TCP/IP chapter 2 of the Communications
Programming Reference Guide. RTU is not supported for the TCx family.
ADXSITQL- System Information Tool

ADXSITQL – System Information Tool
ADXSITQL – System Information Tool is an "as is" tool and is not supported.
Page 23 of 26
The ADXSITQL program is a general purpose utility program used to gather information from a
remote machine. By default, the program collects a machine status file and enhanced mode log
files from the machine. The machine status file can be read by the support team to determine
the status of 4690. The log files are the same set of log files that are collected in the
VX_CSL?F.ZIP files when a dump is performed.
In addition to collecting log files from a remote machine, the ADXSITQL program can also
perform other operations such as checking memory status or controlling tracing daemons.
Note, however, that not all operations performed by ADXSITQL are documented or supported.
Many of the operations are intended for use at the direction of the support team only. Current
versions of ADXSITQL program help make this clear where earlier versions did not.
Chapter 26 of the 4690 V6.5 User’s Guide has additional information about this “AS IS” Tool.
IDLE Editor
With the introduction of the Python scripting language an additional editor is available on 4690
Enhanced controllers, the IDLE editor. It is written in the Python language. IDLE is an "as-is"
function that is available for use, but not otherwise supported. A sample batch file showing
invocation of IDLE on 4690 OS is available with the 4690 Optional Programs as IDLE.BAT.
Note: IDLE does not include command line logging support that is available with the DR EDIX
and XE editors provided in 4690 OS. IDLE is a graphical editor and will not be accessible
remotely if you do not have graphical remote access to your store controller.
For details on the IDLE editor https://docs.python.org/2/library/idle.html
Limitations
Hardware limitations
 Toshiba 4690 OS V6R5 ONLY runs on IBM/Toshiba hardware or VMware ESX, ESXi
supported systems.
 Terminals are limited to a maximum of 8G of memory before CSD1 0GM0
 E86 i5 models of the TCx™700 will not support 4690 V6R5 by only changing the model
number with the diagnostic utilities. E models of the TCx™700s do not come with Riser
Plus cards installed, the Riser Plus card is required for support of 4690. Contact your
Sales Rep for assistance in converting the E86 i5 for 4690.
 Store Loop is not supported with 4690 OS V6R3 and later.
Page 24 of 26
 The TCx™300 model 380 is not orderable for 4690 OS, please contact your sales rep for
assistance.
 Generation 1 USB POS Keyboard is not supported.
 The 4800-721 can only be supported as a Classic terminal.
 100M Ethernet or greater are required when using Enhanced terminals.
 IBM 4693 terminals do not support Java or terminal-based TCP/IP functions, and, as a
result, system management functions are not supported on these terminals.
 JavaPOS support for fiscal printers is not included in IBM 4690 OS V6.
 Controller displays must be able to support SVGA 800 x 600 resolution for Enhanced
Mode.
 With the announce of Toshiba 4690 OS V6, the following hardware is no longer
supported by the 4690 OS:
o TR7 Tape Drives

o Loop Attached Terminals
o Token-Ring Attached Controllers or terminals.
o External attached USB CD drives on all System x servers.
Software limitations
 4690 Remote Access is only supported in Classic Mode.

 Java 1 applications are not supported
 SNA is not supported.
 Installed 32G of memory will only be reported by the Chkdsk function as 16G.
 Java 2 application support requires the use of the Java Terminal Offline Function (TOF)
or terminal Java preload bundles in the 4690 OS.
 Graphics on SurePOS 721 models using 1024x768 64K colors are not supported by the
4690 OS.
 4690 OS does not support USB POS devices attached via a 5V USB port.
 IPSEC is not supported on Enhanced Controllers.
For more information, see:
4690 OS Controller Matrix article located in the Knowledgebase at
http://www.toshibacommerce.com/support
Documentation
The following Toshiba 4690 OS V6 publications will be available and require your Enterprise ID
for access at GA time:
http://www.toshibacommerce.com/publications
Page 25 of 26
Toshiba 4690 OS V6R5: Users Guide

Toshiba 4690 OS V6R5: Planning, Installation, and Configuration Guide
Toshiba 4690 OS V6R5: Messages Guide
Toshiba 4690 OS V6R5: Communications Programming Reference
Toshiba 4690 OS V6R5: Programming Guide
Getting Started Guides are now listed with the publications on the Toshiba Portal.
NOTE: All of the 4690 OS publications have gone through a much more significant update and
review then normal and many section of information that are no longer relevant have been
removed. Publications for the OS are now being updated at the time each CSD is available.
All previous levels of the publications will still be available on the Customer Portal.
Page 26 of 26

4690 V6R5 Getting Started Guide-CSD3-0HN0-V5Memupdate PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

4690 V6R5 Getting Started Guide-CSD3-0HN0-V5Memupdate PDF

Hochgeladen von

Copyright:

Verfügbare Formate

V6R5 Getting Started Guide for CSD3 0HN0-V5

4690 V6R5 Getting Started Guide:

 Support for TCxWave™-Model A3R

V6R4 CSD Deliveries of new Function:

Summary of New Features in V6R5

New HW supported with V6R5 release:

4690 V6R5 offers the following new features:

 Additional changes with OHN0 CSD:

Hardware Requirements for V6R5- Controllers

Minimum/Maximum controller memory (Classic Mode) - 256 MB/1 GB

Model Enhanced Classic Controller / Controller /

HS12 Blade 8014,8028 X (SATA and

For more information, see:

Terminals that support

4900-745 & 775 1G 4G 32M

++ 16G DIMMS require a RPQ

Model Enhanced Classic Controller / Controller /

Installation and Migration

4690 V6R5 Packaging and Media

4690 V6R5 is distributed with the following media:

 V6R5 CD Volume 01—Install

Installation of V6 Classic Mode is not supported.

Both local and remote migration options are supported.

To install these extensions:

"adxzudir -x p:\4690OPT\javaexr4.zip adx_spgm:"

3. This will create the following files:

TCx™700 model 4900-746:

Controller Offerings C46 and C86:

TCx™300-4810-36x, 37x and 380 Support

TCxWave™ – 6140-A3R, 14C, 145, 15C & 155 Support

4690 Supports up to 16G of memory installed.

Only one cash drawer will be supported on the TCxWave™.

Dumping the TCxWave™:

Clearing the terminal number:

(1) Hold the + (plus) and – (minus) Brightness Buttons

(2) Press the blinking Power Button (after approximately

(3) The Power Button will now be enabled (solid light)

Toshiba Development Kit 8 (TDK 8)

Linux Java Application Support (Java 6 and TDK8)

Migration from earlier releases of 4690

The files provided are:

adxzudir -x p:/4690opt/javaexr4.zip adx_spgm:

File Integrity Monitoring Tools

Using Rules to Match Filenames

 Start with a list of all files on the system

The valid rule types are:

Saving CMOS Settings:

Updating CMOS Settings:

Additional information can be found in the 4690 V6R5 Communications Programming

ADXSITQL- System Information Tool

For details on the IDLE editor https://docs.python.org/2/library/idle.html

o TR7 Tape Drives

 4690 Remote Access is only supported in Classic Mode.

For more information, see:

4690 OS Controller Matrix article located in the Knowledgebase at

Toshiba 4690 OS V6R5: Users Guide

Das könnte Ihnen auch gefallen