SDK/J

Hi Ricoh Support, Our Xlet application is implementing the AAA Authentication for Ricoh (com.ricoh.auth.LoginListener). We are facing the following situation from our customer: 1. On some Ricoh MFPs, the Xlet state is "STARTING" or "STARTED" when the method login(java.lang.String arg0) from AAA Authentication is triggered. 2. On some Ricoh MFPs, the Xlet state is "INITIALIZED" when the method login(java.lang.String arg0) from AAA Authentication is triggered. Is this as designed? If not, why is there a difference between the two cases above? How we can make them consistent? Thanks,

Hi, 

We would like to get a maintenance signature of out package to SDK/J

Package is for 7x, 10x, 11x and 12x;  

Display Panels are uWVGA and WVGA;

The changed jar file was nddPrintClientRicoh.jar;

No changes in Dalp file beside version. 

attached the package and change log file;

Hello Support,

My manager, Erik Blair, contacted Joe Gormley about getting a maintenance signature our DocuWare Connect to Ricoh xlet, and said he would allow one. 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

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 files other than updating the version.

Changes:

1. Fixed a customer issue brought up by Partners.  The auto-logout timer in our solution is not logging the user out in the appropriate amount of time.  This has been addressed.

Thanks,

 Bryan

Hi,

I would need to get a Maintenance Signature for our Pcounter Authentication app.

We made a very small change concerning how we read the app's config file (see Release Notes below). it doesn't change anything in the functionality of the app.

I included the app's  .zip file.

Solution Release notes:

1) Our solution supports the following SDK/J platforms:  4.x, 5.x, 6.x, 7.x, 10.x, 11.x, 12.x and Smart Operation Panel where it runs on compatibility mode.

2) List of display panels supported:    HVGA, SVGA, WVGA.

3) The following .jar files where modified:  PcounterAuthentication.jar (in PcounterAuthentication.zip)
PrintJobRelease and ClientCode Xlets were not modified.

4) No modifications were made to the .dapl file except for the version tag. New version is 2018.01.19.
 

List of modifications:

Right now our Login app displays two buttons to enable the user to launch the Print Release and Client Code apps. If those apps are not installed, the corresponding button does not appear. We check if those apps are installed by reading an entry in the Config file.

Currently, we do that check every time someone logs in. We realized that sometimes this slows down the Login process. So in this new version, we changed it so that it only checks when the Login app is started. This is the only change we made to the code.

Regards,

Jean-Marc Palmier

Hello. Just a simple question. The MFP has access to internet through sdk/j? I mean, can I do a simple GET/POST HTTP request from a Servlet/Xlet to an external server?

I'm getting this error:

<strong>java.net.NoRouteToHostException: No route to host</strong>

Just want to confirm if this is a network issue or if the MFP isn't capable to do it.

Thank you!

Hi Gerardo,

We're looking for a maintenance signature for Pharos iMFP for Ricoh version 1.5.7.1.  This version has a change relative to 1.5.7 to help with issues reported from Telligen. Telligen is reporting the MFPs hang with soft keyboard errors or being prompted for the wrong information (password instead of username) and print all is not working.

Considering 1.5.7 is working at other major customers across MFP models with no complaints, we believe this is mostly environmental. It's possible there is something wrong with our solution because the user is configuring very short timeouts and this is something we don't normally test. But until we can collect more data, we don't know actual root cause.

This version has a few minor changes.

1. Additional debugging to the logs. This will help us better understand execution flow and track button events.
2. Remove code that was creating a soft keyboard and not using it. When the main UI is created a soft keyboard was created then when the user touched the home screen another soft keyboard was created and replaced the first instance. This is a one line deletion from the solution.
3. Prevent a user from logging in with a blank username. The original code checked to see if the value returned from the keyboard was !null and if so, collected the keyboard value and used it as the username. I modified the solution to check for !null and !empty instead of !null. Note: this one is strange. Since the !null check is original code we either missed this bug for nearly a decade or the platform changed so the keyboard returns a non-null empty string instead of a null object when nothing is entered on the soft keyboard.

Thanks,

Nick.

Charles,

As per the last update for incident # 2397, the Ricoh rep said he’s unable to find an update for M2a_System. Below are the Ricoh technician details,

Ricoh's support page provides printer drivers for Ricoh MFPs. All the drivers available on the site are Microsoft "Class 4" drivers which no longer support custom port monitors. Pharos relies on custom port monitors to manage print queues. Do you know where I can download earlier versions of a Ricoh printer driver that is not a "Class 4" driver?

Thanks,

Nick.