SDK/J

Hello Support,

I signed our xlet using the demo signature tool, but when I try to start it on our MFP, I get a J522 error.  I attached a screenshot and log of the error.  This part of the log seems like it's a problem with the demo signature:

java.lang.SecurityException: invalid SHA1 signature file digest for jp/co/ricoh/dsdk/framework/panel/IPAddressEditSet$CancelActionListener.class
[stderr]        at sun.security.util.SignatureFileVerifier.verifySection(SignatureFileVerifier.java:441)
[stderr]        at sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:231)
[stderr]        at sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:176)

We got a demo signature from support a month or two ago that worked.  I attached 34094850.zip.  Could you give us a demo signature for this one?

Thank you,

Samantha Valanzuolo

I have a small change in the next release of our SDK/J solution that should only require a maintenance signature.

1. We are still supporting devices with SDK/J versions 4, 5, 7, 10, 11, 12.

2. SVGA COLOR, WVGA COLOR and HVGA COLOR.

3. 34099970.jar and 34099971.jar are the only modified jar files.

4. No modifications to the .dalp file other than updating the version.

Changes:

1. Fixed a customer issue brought up by Partners.  They have a large number of jobs on a personal queue, and our HTTP receive logic was taking a very long time to process the data, to the point where the device was unresponsive.  This has been fixed and runs much faster.

Thanks,

 Bryan

We installed our latest version of Ricoh Embedded Java (3.3.0.14) at one of the client location and the copier becomes unusable after the device is rebooted for installation.

We see a Login Module Set Exception in the logs while initializing our Login application after installation.

Attached are the logs.

Could you please give us some more information regarding this.

Thank you,

Divya

PrinterOn is requesting a maintenance signature for SOP 1.03 version. This version resolves the issues reported by Expedia. We have informed Joe Gromley about this request. We are requesting your assistance to expedite the process. Thanks.

Hello,

This is a maintenance signature request by PrinterOn.  This is for Ricoh HotSpot Embedded version 6.15 and Smart Operation Panel 1.03 version.These versions resolves the issues reported by Expedia. I have notified Joe Gromley about this submission. Please review the request as early as possible.  Thank you for your assistance.

Wells Fargo wants to migrate to a new card reader, the aptiQ MT20. This is a keystroking reader that is know to work when plugged into Windows. When connected to Ricoh printers the reader does not appear to be functional with Pharos iMFP.  They've primarily seen instances in which swipes over the reader produce no apparent activity within Pharos iMFP.  Less frequently, they've seen instances in which a badge swipe triggers activity, however, the value provided to the Pharos iMFP is not correct.  For example, instances have been seen in which the same badge produces different results; conversely, they've also seen instances in which different badges produce the same value, typically a single character. 

I theorized that the card reader is too fast for the MFP as we have seen this behavior with Blackboard card readers as well. We used a USB protocol analyzer to measure the keystroking frequency for a known good reader and the MT20. For an RFIdeas reader (that works) we see a 15-31ms intracharacter delay. With the aptiQ MT20 reader the intracharacter delay is 2 microseconds. We performed this test on our SP5200 and the MP2554 in the Pharos lab.

Attached is the trace from the protocol analyzer.

Question for Ricoh:

Is the hardware on the MFP capable of reading data from USB at such a high frequency?

Hello,

Please find attached version 6.0.4 of the PaperCut SDK/J application. It fixes the following issues:

- Fixed an issue where integrated scanning zero stop may not work correctly when using payment gateway

- Added support for Basque translations

The application supports SDK 4/5/7/10/11/12 on uWVGA, WVGA and SVGA.

Please Note:

The attached ZIP was built and signed using our development product ID (which is different to our official product ID). After it has been built and tested I have modified the product ID in the DALP file to be the official product ID and created a new ZIP which is attached, as was requested last time.

Thanks,

Daniel

Hello Support,

We would like to get a maintenance signature for our DocuWare Connect to Ricoh xlet. The platforms we support are 2.X, 4.X, 5.X, 7.X, 10.X, 11.X, 12.X all without uWVGA support.  We had to fix a bug for a customer where importing documents with special characters such as Spanish characters would cause the import to hang/crash.

Thank you,

Samantha

Attached is our verification packet for version 3.3.0.

This will be a new feature release along with some bug fixes and performance improvements.

Changes include:

-  Changes to Login page and DMS (IManage and Prolaw) to support no cost recovery feature.

-  New Quick pick DM (My workspace) implementation.

-  Few bug fixes.

The "PO" and the "nQueue billback CT countersigned" documents will be attached later this afternoon.

Thank you,

Divya

Hi,

We installed our application at one of our client sites and we see the SC672-11 error after installation. There are a lot of memory ticks in the log. 

We would appreciate if you can give us some insight about what might be causing the issue and why there would be so many memory ticks per second.

Attached is the log file.

Thank you,

Divya