Berikut adalah daftar error code yang mungkin dialami Java Virtual Machine (JVM) di BlackBerry. Silakan terjemahkan sendiri dan googling untuk mendapat keterangan tambahan.
101 Previous startup failed — The device was reset during the JVM boot process. The JVM found the boot in progress flag was set on startup. The screen is intended to break continuous reset loops so that corrective action can be taken.
102 Invalid code in filesystem — The system checked the COD files in the device for modification and determined that a problem exists with one or more COD files.
If all loads fail, a build process error might occur (a problem exists with signing the COD files).
If a user action on the device resulted in this problem, the reset cycle is continuous because the code in the filesystem has been corrupted. The only recovery method is to wipe the device and restore a new system.
103 Cannot find starting address — The starting address for the boot COD file cannot be found. This might indicate that a boot COD file has not been installed on the device or that its format is invalid or corrupt.
104 Uncaught: <Java-type-name> — An uncaught Java exception was thrown by the Java code and diagnosed by the JVM. Execution can continue, or the device can be attached to a debugger on a desktop computer. The Microsoft® Windows® Event Viewer log should contain the traceback of the thrown exception.
105 Example, DbRecSize( %d ) -> %d — The file system application programming interface (API) has returned an error status for a specific operation. This might indicate a corrupt filesystem or an error in the JVM.
Continue reading →
Berikut paparan dari Cak Heru Subiyantoro, owner sekaligus moderator milis XLent-BB.
), juga 
