Ricoh Taurus-C1a - RTB 21 f: Firmware Release Note: Java VM v7 UpdateTool

Technical Bulletin PAGE: 1/2
Reissued: 06-Jan-15
Model: Taurus-C1
Date: 26-Aug-11
No.: RD074021f
RTB Reissue
The items in bold italics have been corrected or added.
Subject: Firmware Release Note: Java VM v7 UpdateTool
Prepared by: S. Sasaki
From: 1st PP Tech Service Sect., PP Tech Service Dept.
Classification:
Troubleshooting
Mechanical
Paper path
Part information
Electrical
Transmit/receive
Action required
Service manual revision
Retrofit information
Product Safety
Other (Firmware)
Tier 2
This RTB has been issued to announce the firmware release information for the Java VM
v7 UpdateTool (MFP).
Version
Program No.
Effective Date
Availability of RFU
7.23.00
D4975907N_upd
December 2014 production
Not available
7.22.00
D4975907M_upd
April 2013 production
Not available
7.21.00
D4975907L_upd
January 2013 production
Not available
7.20.00
D4975907K_upd
July 2012 production
Not available
7.17.04
D4975907H_upd
March 2012 production
Not available
7.16.07
D4975907G_upd
November 2011 production
Not available
7.14.03
D4975907F_upd
June 2011 production
Not available
-
-
1st Mass production
Not available
Note: Definition of Availability of RFU via @Remote
“Available”: The firmware can be updated via RFU or SD card.
“Not available”: The firmware can only be updated via SD card.
Version
Modified Points or Symptom Corrected
7.23.00
Error corrected:
SDK platform may not boot up when next power-on if stopping start process
of SDK app.
7.22.00
Fixed:
When a device failed to reboot after receiving a reboot request from a device
management application, installed ESA applications would not restart
automatically and remained in "Stopped" status.
7.21.00
Fixed:
- When tracking is enabled using usage control service, incorrect scanning
paper size information is sent from ESA application which is installed on A4
models.
- Unlock the application switching function might results in
"NullPointerException" error.
- When ESA application sends a FAX job using multibyte character set, the
sender is garbled on the recipient device.
- AES-256 may be used as Kerberos encryption algorithm even though it is not
specified.
7.20.00
Fixed:
1. Kerberos authentication using AES128/AES256 is slower compared to
Kerberos authentication using RC4HMAC.