KNOWLEDGE BASE - Known Bugs and Solutions

SophiaCompress(Java) Bug informations and its solutions

KBSC0022

"java.lang.Error" occur in the compressed application

Version : 4.0.0 ~ / Date : 2006/07/11

KBSC0020

Compression failure

Version : 2.4.0 ~ 4.0.0 / Date : 2006/06/06

KBSC0017

Compressed application does not work

Version : ALL / Date : 2005/03/28

KBSC0013

Compression failures during pre-verifying

Version : 3.0.0 ~ 3.0.3 / Date : 2004/12/16

KBSC0012

Unusual termination of compressing process

Version : 3.0.0 ~ 3.0.2 / Date : 2004/12/16

KBSC0011

Compressed app does not work properly

Version : 3.0.0 ~ 3.0.2 / Date : 2004/12/16

KBSC0010

The possibility of Compressed app does not work on mobile device

Version : 3.0.0 ~ 3.0.1 / Date : 2004/09/09

KBSC0009

Failure in authentication before compression processes.

Version : Trial Version/ Date : 2004/08/19

KBSC0008

Compression failures during pre-verifying

Version : ~ 3.0.0 / Date : 2003/10/21

KBSC0007

Failures during compression or during compressing processes.

Version : ~ 2.3.0 / Date : 2004/08/19

KBSC0006

Compression failures when there is multiple apps on one JAR file.

Version : ~ 2.2.X / Date : 2003/09/17

KBSC0005

Compression failures, when there is size of greater than 72 bytes of code are included on a single line of a JAD file.

Version : ~ 2.2.X / Date : 2003/09/17

KBSC0004

Compression failures when there is pictoral symbol on app's name inside the JAM file.

Version : ~ 2.4.3 / Date : 2003/09/17

KBSC0003

Compression does not start even pressing "compress" button

Version : 2.X.X / Date : 2003/09/17

KBSC0002

Window size of the SophiaCompress become abnormal

Version : 2.X.X / Date : 2003/09/17

KBSC0001

Failures in installation of iKey driver

Version : 2.2.0 / Date : 2003/09/17

(KBSC0022)2006/07/11

"java.lang.Error" occur in the compressed application

Target :

2.0.x ~ 4.1.1

What happens :

When choosing [Class integration] for compress option, "java.lang.Error" occur in the compressed application.

Cause :

This error occur when non implemented abstract class inherits abstract classes or interfaces with abstract method.

Solution :

Do not use class integration function, or fix the target code.

Detail :

Fixed in version 4.2.

(KBSC0020)2006/06/06

Compression Failure

Target :

4.0.0 ~

What happens :

Error dialog pops up during compression, in the error log, MSD class is pointed as the error source.
"2. Error occurred during compression Detail: Java.langError: ... at MSD.J(Unknown Source)"

Cause :

This error occurs when the installed DLL is not collect.

Solution :

Uninstall SophiaCompress(Java), then re-install it. When using the installer, make sure that SophiaCompress(Java) is not running.

Detail :

Fixed in version 4.2.0.

(KBSC0017)2005/03/28

Compressed application does not work

Target :

ALL

What happens :

Access to resources within JAR file fails after being compressed.

Cause :

Names of the packages will change by class integration or class name shortening function. Therefore, access to the resource by relative path may fail.

Solution :

Use absolute path to access the resource, or turn off the class integration and name shortening function.

KBSC00132004/12/16

Compression failures during pre-verifying

Target :

3.0.0 ~ 3.0.3

What happens :

It shows error relating to failures in compression while pre-verifying.

Cause :

As a result of Class integration, it occasionally override the final method.

Solution :

Please use 3.0.4 or later versions.

Detail :

KBSC00122004/12/16

Unusual termination of compressing process

Target :

3.0.0 ~ 3.0.2

What happens :

It shows error relating to compression failures while compressing

Cause :

Non-correspondent Java extension was existed

Solution :

Please use "3.0.3" or later versions

Detail :

If "Deprecated attributes" (not recommended attributes) is located in Class, Field or Method, it determines as unidentified attributes during compression.

KBSC00112004/12/16

Compressed app does not work properly

Target :

3.0.0 ~ 3.0.2

What happens :

Compressed apps make errors on mobile devices and terminates processing.

Cause :

As a result of implementation of class integration, the function generates the irregular codes for some mobile device.

Solution :

Please use "3.0.3" or later versions

Detail :

Class integration function on rare occasions integrates an abstraction class and other classes. As a result, it generates codes for instances on abstraction class.

KBSC00102004/09/09

The possibility of Compressed app does not work on a mobile device.

Target :

3.0.0 ~ 3.0.1

What happens :

Compressed app does not work on some mobile devices and it ends with errors.

Cause :

As a result of implementation of class integration, the function generates the irregular codes for some mobile device.

Solution :

Please use ver.3.0.2 or later versions

Detail :

According to specification of "DoJa", AppClass (Inheritance classes of IApplication, MApplication) cannot generate instances. On version 3.0.0, 3.0.1 's implemented class integration function rewrites on AppClass instance generation code from other class instance code by integrating AppClass and other classes. Some of the mobile devices are made to output errors on its particular code.

KBSC00092004/08/19

Failure in authentication before compression

Target

:

Trial Version

What happens :

When you press Compress button, errors relating to un existent of the "Javaext.exe" is showed and compression is terminated.

Cause :

If there is space on its path of the directory where "SophiaCompress" folder is located

Solution :

Do not place the Trial Version of SophiaCompress on directory where containing path on its directory

KBSC00082003/10/21

Compression failures during pre-verifying

Target :

~ 3.0.0

What happens :

While compression processing or pre-verifying , it indicates errors relating to failures in compressions.

Cause :

Specification of the pre-verifier

Solution :

Please use SophiaCompress 3.0.1 or later versions

Detail :

This problem happens only in Japanese edition.

KBSC00072004/08/19

Failures in compression while pre-verifying

Target :

~ 2.3.0

What happens :

Error appears relating to Failures in compression while pre-verifying or compressing

Cause :

SophiaCompress Bug

Solution :

Please use SophiaCompress 2.3.1 or later version

Detail :

When you try to compress the files which obfuscaters been used such as "RetroGuard", the possibility becomes much higher

KBSC00062003/09/17

Compression failures when there is multiple apps on one JAR file.

Target :

~ 2.2.X

What happens :

If there is multiple apps on one JAR file, the compression will be failed

Cause :

Bug of SophiaCompress

Solution :

Please use "SophiaCompress 2.3.0" or later versions

KBSC00052003/09/17

Compression failures, when there is size of greater than 72 bytes of code are included on a single line of a JAD file

Target :

~ 2.2.X

What happens :

Compression failures, when there is size of greater than 72 bytes of code are included on a single line of a JAD file

Cause :

Bug of SophiaCompress

Solution :

Please use "SophiaCompress 2.3.0" or later versions

KBSC00042003/09/17

Compression failures when there is pictorial symbol on app's name inside the JAM file.

Target :

~ 2.4.3

What happens :

When you compress the Files containing pictorial symbols inside the JAM file, compressed JAM file will be garbled or compression will be failed.

Cause :

SophiaCompress does not have encoding libraries for solution on DoJa

Solution :

When you want to compress apps containing pictorial symbols, delete pictorial symbols in JAM file and then add those symbols after the compression.

KBSC00032003/09/17

Compression does not start even pressing "compress" button

Target :

2.X.X

What happens :

There is no reaction on a button

Cause :

When "Java 2 SDK 1.4.1_03" are used, SophiaCompress does not respond to the problems

Solution :

Please use "Java 2 SDK 1.3.1" and then start SophiaCompress

KBSC00022003/09/17

Window size of the SophiaCompress become abnormal

Target :

2.X.X

What happens :

Window size of SophiaCompress becomes abnormal For example, window become too small to control buttons

Cause :

There is only rare circumstances that occurs when you are using multi displays in a single environment.

Solution :

From command line, specify option [-resize] and then start the SophiaCompress, it enables to to adjust window size.

Example: Enter [java -jar scompress.jar -resize] then start.

Please refer FQSC0005 for more detailed information on starting Command line

KBSC00012003/09/17

Failures in installation of iKey Driver

Target :

2.2.0

What happens :

Under Windows2000 Professional environment,iKey driver cannot be installed, if Q8140033 patch were installed on a system.

Cause :

The cause are the patch on Q814033 environment

Solution :

Please use following steps

• Ensure that patch "Q814033" are allocated on Windows 2000 professional
• Click "Add or remove programs" and ensue that "Windows 2000 Hotfix (sp4) Q814033" is existing
• If it is not existed, please contact us
• Uninstall the Q814033 path from "Add or Remove programs"
• Re-start windows
• Installl iKey driver
• Please refer manual attached to driver for further information
  Re-install "Q814033" patch
• Re-install "Q814033" patch
• Start menu - Windows update or go to Microsoft Web page to download the patch

Detail :

The patch "Q814033" is released by Microsoft at 12 March 2003.

The failures in iKey installation is made by, the patch fixes the problems during INF data creation and also the patch modifies the controlling method.

iKey driver creates windows standard interface "card service" during installation. Installation has problem on this process. We have detected the same problems on Windows XP however, the problems can be coped with the same solution as windows 2000