FAQ on launching Java on a PDA | Emulators, Java-machines, midlets, applets
FAQ on launching Java emulators, Java machines, midlets and applets on a PDA
Discussion
In this topic, messages can be created ONLY with suggestions and comments regarding the FAQ on launching Java on a PDA. We do not ask questions here. All messages that are not related to this topic are deleted without warning.
Post has been editedwandererbk - 20.10.09, 11:03
Discussion
In this topic, messages can be created ONLY with suggestions and comments regarding the FAQ on launching Java on a PDA. We do not ask questions here. All messages that are not related to this topic are deleted without warning.
!
Questions do not ask! Refinements and additions - to me in PM! For violation - 3 days RO!
Post has been editedwandererbk - 20.10.09, 11:03
Rubricator (in the process)
Introduction
I. First a bit of theory
Ii. JAVA midlet emulators on PDA
1) TAO Intent Java MIDlet manager emulator (TAO Intent JMM)
2) IBM J9 WEME MIDP20 JMM (IBM J9 WEME MIDP20 JMM Manual)
3) Coretek Delta java manager
4) Esmertec Java
5) JBlend
6) Mitac JVM
Iii. The procedure for installing and running midlets on the PDA
1) If when trying to install emulators on a device with WM 5.0, the system swears about certificates
2) Problems running midlets on the TAO Intent JMM emulator
3) Installing MIDlets in Coretek Delta java manager emulator
4) The order of running midlets with a virtual Java-machine CrEme JVM
5) How to run MIDlets with Esmertec Java emulator
Iv. Running applets on a PDA
Additionally:
About launching JAVA on BenQ P50 and Gigabyte G'Smart communicators
About jad files
How to adapt midlets that do not run on the PDA
The adapted midlet was launched, but it is still impossible to manage it.
Midlet started and waits for pressing the soft button. What to do?
Links to java games running on PDAs
Java games
Java-games, games adapted for the Touch Screen
Search java games
Java games on the desktop
Post has been editedPaLadin - 26.10.08, 14:11
Introduction
I. First a bit of theory
Ii. JAVA midlet emulators on PDA
1) TAO Intent Java MIDlet manager emulator (TAO Intent JMM)
2) IBM J9 WEME MIDP20 JMM (IBM J9 WEME MIDP20 JMM Manual)
3) Coretek Delta java manager
4) Esmertec Java
5) JBlend
6) Mitac JVM
Iii. The procedure for installing and running midlets on the PDA
1) If when trying to install emulators on a device with WM 5.0, the system swears about certificates
2) Problems running midlets on the TAO Intent JMM emulator
3) Installing MIDlets in Coretek Delta java manager emulator
4) The order of running midlets with a virtual Java-machine CrEme JVM
5) How to run MIDlets with Esmertec Java emulator
Iv. Running applets on a PDA
Additionally:
About launching JAVA on BenQ P50 and Gigabyte G'Smart communicators
About jad files
How to adapt midlets that do not run on the PDA
The adapted midlet was launched, but it is still impossible to manage it.
Midlet started and waits for pressing the soft button. What to do?
Links to java games running on PDAs
Java games
Java-games, games adapted for the Touch Screen
Search java games
Java games on the desktop
Post has been editedPaLadin - 26.10.08, 14:11
Introduction
Java programs do not run on the PDA with a tap on the program file or its shortcut. First, the Java program must be installed in the emulator. On most mobile devices, emulators are included in the standard set of programs, in their name they usually have the words “Java” or “MIDLet”. Ideally, the whole action should take place in 2 tapas with a stylus - first, tap on the program file (file of type ***. Jar), ​​the Java program is installed in the emulator, and then the program itself is launched by the tap on the program icon in the emulator window.
But this happens under the condition of perfect compatibility of Java-program, emulator and PDA operating system. Getting started with Java on a PDA, you need to keep in mind that most Java programs are written for another type of mobile device - for mobile phones. And yet - Windows for non-programmatic reasons does not contain native Java support. Therefore, we are dealing with Java emulation, which by definition is "imitation of the operation of one system by means of another without loss of functionality and distortion of the results." But imitation of the original is not the original. Putting it into practice without losing quality or functionality is not so simple.
If you have increased the number of users who failed to launch the Java program using the method described above, or there are problems with running Java programs on your mobile device, carefully read the following material that will help you understand the causes of existing Java problems and resolve them. “Go ahead, reader!” :-)
Post has been editedrendor - 27.01.08, 13:32
Java programs do not run on the PDA with a tap on the program file or its shortcut. First, the Java program must be installed in the emulator. On most mobile devices, emulators are included in the standard set of programs, in their name they usually have the words “Java” or “MIDLet”. Ideally, the whole action should take place in 2 tapas with a stylus - first, tap on the program file (file of type ***. Jar), ​​the Java program is installed in the emulator, and then the program itself is launched by the tap on the program icon in the emulator window.
But this happens under the condition of perfect compatibility of Java-program, emulator and PDA operating system. Getting started with Java on a PDA, you need to keep in mind that most Java programs are written for another type of mobile device - for mobile phones. And yet - Windows for non-programmatic reasons does not contain native Java support. Therefore, we are dealing with Java emulation, which by definition is "imitation of the operation of one system by means of another without loss of functionality and distortion of the results." But imitation of the original is not the original. Putting it into practice without losing quality or functionality is not so simple.
If you have increased the number of users who failed to launch the Java program using the method described above, or there are problems with running Java programs on your mobile device, carefully read the following material that will help you understand the causes of existing Java problems and resolve them. “Go ahead, reader!” :-)
Post has been editedrendor - 27.01.08, 13:32
I. First a bit of theory
Java is a programming language. There are 3 different editions of Java:
Jse (Java Standard Edition) is Java for computers (including for PDAs);
JEE (Java Enterprise Edition) - Java for servers;
Jme (Java Micro Edition) - Java for mobile phones, with very reduced capabilities, which has little to do with JSE.
Java cross-platform allows you to run the same Java programs on both PCs and PDAs.
Java programs are usually presented in the form of archive files with the jar extension, as well as in folders, which usually include (or inside which there are) html files for launching them by the browser.
Post has been editedrendor - 27.01.08, 13:33
Java is a programming language. There are 3 different editions of Java:
Jse (Java Standard Edition) is Java for computers (including for PDAs);
JEE (Java Enterprise Edition) - Java for servers;
Jme (Java Micro Edition) - Java for mobile phones, with very reduced capabilities, which has little to do with JSE.
Java cross-platform allows you to run the same Java programs on both PCs and PDAs.
Java programs are usually presented in the form of archive files with the jar extension, as well as in folders, which usually include (or inside which there are) html files for launching them by the browser.
Post has been editedrendor - 27.01.08, 13:33
Applet - This is a program written in the JSE. JSE codes directly into processor codes translate the JRE.
Jre - Java Runtime Environment is an environment for program execution, an interpreter, usually applied to a PDA Java Virtual Machine (JVM), i.e. virtual java-machine. Java Virtual Machine running on desktop and mobile computers, as a rule, understand only JSE and JEE codes, with rare JME codes they do not work, with rare exceptions.
Applets, as a rule, are executed in the browser environment. It uses virtual Java machines that are either embedded in browsers or are Java plug-ins to Internet Explorer. Browsers can execute an applet on-line (if the applet is downloaded from the network and does not remain on the PDA as a file) or off-line (if the file with the applet is on the PDA).
Applets can also be executed separately from the browser, for this purpose the function "main ()" is added to the applet class. That is, an applet can be launched separately from the browser if it implements the specified function (for example, the Toonel program used on a PDA to compress Internet traffic). The class of an applet with the "main ()" function is considered to be the entry point into the program by default, and there may not be one such entry point. When the program starts, the main () method of this class is called.
Applets running separately from the browser are executed by separately installed virtual Java machines (CrEme JVM, Jeode Runtime JVM, IBM J9 PPRO10 (11) JVM).
Post has been editedrendor - 27.01.08, 13:35
Jre - Java Runtime Environment is an environment for program execution, an interpreter, usually applied to a PDA Java Virtual Machine (JVM), i.e. virtual java-machine. Java Virtual Machine running on desktop and mobile computers, as a rule, understand only JSE and JEE codes, with rare JME codes they do not work, with rare exceptions.
Applets, as a rule, are executed in the browser environment. It uses virtual Java machines that are either embedded in browsers or are Java plug-ins to Internet Explorer. Browsers can execute an applet on-line (if the applet is downloaded from the network and does not remain on the PDA as a file) or off-line (if the file with the applet is on the PDA).
Applets can also be executed separately from the browser, for this purpose the function "main ()" is added to the applet class. That is, an applet can be launched separately from the browser if it implements the specified function (for example, the Toonel program used on a PDA to compress Internet traffic). The class of an applet with the "main ()" function is considered to be the entry point into the program by default, and there may not be one such entry point. When the program starts, the main () method of this class is called.
Applets running separately from the browser are executed by separately installed virtual Java machines (CrEme JVM, Jeode Runtime JVM, IBM J9 PPRO10 (11) JVM).
Post has been editedrendor - 27.01.08, 13:35
Servlet is a program written in JEE. Within the framework of this topic, we will not consider servlets and JEE.
Post has been editedrendor - 27.01.08, 13:35
Post has been editedrendor - 27.01.08, 13:35
Midlet - This is a program written in JME.
On mobile phones, midlets are executed directly (runtime) by kilobyte virtual machines (KVM) that convert JME codes to processor codes.
To implement the midlet on desktop and mobile computers, it is necessary to simulate (emulate) the behavior of a mobile phone, such as: there is only one display and no moving windows, soft buttons and a numeric keypad, there is only a canvas with a limited set of functions for drawing, there is text to enter standard set of input fields - all this must be implemented in the form in which it is presented in a particular phone or in some kind of hypothetical phone. This function is performed on computers (including PDAs)mobile phone function emulators converting JME codes, as a rule, to JSE / JEE codes (with their subsequent transfer to the built-in Java Virtual Machine emulator), or directly to processor or OS codes. Among the emulators working on the PDA, there are: TAO Intent Java MIDlet manager, IBM J9 WEME MIDP20 JMM, Coretek Delta java manager, Mitac JVM, Esmertec Java, CrEme JVM. Emulators of the functions of mobile phones are usually called midlet emulators or Java emulators, sometimes midlet managers, although the midlet manager is just the user interface of the emulator.
Thus, virtual Java machines running on desktop and mobile computers, as a rule, execute programs written in JSE, i.e. applets. The Java Virtual Machine, with rare exceptions, does not understand the JME codes on which the MIDlets are written and therefore cannot work with MIDlets. For the stated reason, neither games for mobile phones, nor Opera mini can be launched on Java Virtual Machine. An exception to this statement is the CrEme JVM Java Virtual Machine, which has an add-on for JSE - an emulator for executing JME code, with fairly modest capabilities that allow you to run small programs on JME.
Emulators of functions of mobile phones are intended for performance of midlets on desktop and mobile computers. Emulators understand only JME codes and therefore only run MIDlets. Work with programs written in JSE (ie, with applets), emulators can not.
The stated conclusion is not a universal rule and reflects the situation developing on computers running Windows (including Windows mobile). On mobile devices running Palm OS, JME codes are also interpreted by emulators, but on Symbian smartphones, there is no need to use emulators, since there virtual Java machines execute JME codes directly.
Post has been editedrendor - 27.01.08, 15:16
On mobile phones, midlets are executed directly (runtime) by kilobyte virtual machines (KVM) that convert JME codes to processor codes.
To implement the midlet on desktop and mobile computers, it is necessary to simulate (emulate) the behavior of a mobile phone, such as: there is only one display and no moving windows, soft buttons and a numeric keypad, there is only a canvas with a limited set of functions for drawing, there is text to enter standard set of input fields - all this must be implemented in the form in which it is presented in a particular phone or in some kind of hypothetical phone. This function is performed on computers (including PDAs)mobile phone function emulators converting JME codes, as a rule, to JSE / JEE codes (with their subsequent transfer to the built-in Java Virtual Machine emulator), or directly to processor or OS codes. Among the emulators working on the PDA, there are: TAO Intent Java MIDlet manager, IBM J9 WEME MIDP20 JMM, Coretek Delta java manager, Mitac JVM, Esmertec Java, CrEme JVM. Emulators of the functions of mobile phones are usually called midlet emulators or Java emulators, sometimes midlet managers, although the midlet manager is just the user interface of the emulator.
Thus, virtual Java machines running on desktop and mobile computers, as a rule, execute programs written in JSE, i.e. applets. The Java Virtual Machine, with rare exceptions, does not understand the JME codes on which the MIDlets are written and therefore cannot work with MIDlets. For the stated reason, neither games for mobile phones, nor Opera mini can be launched on Java Virtual Machine. An exception to this statement is the CrEme JVM Java Virtual Machine, which has an add-on for JSE - an emulator for executing JME code, with fairly modest capabilities that allow you to run small programs on JME.
Emulators of functions of mobile phones are intended for performance of midlets on desktop and mobile computers. Emulators understand only JME codes and therefore only run MIDlets. Work with programs written in JSE (ie, with applets), emulators can not.
The stated conclusion is not a universal rule and reflects the situation developing on computers running Windows (including Windows mobile). On mobile devices running Palm OS, JME codes are also interpreted by emulators, but on Symbian smartphones, there is no need to use emulators, since there virtual Java machines execute JME codes directly.
Post has been editedrendor - 27.01.08, 15:16
To understand what kind of Java program (applet or midlet) we see in front of you, you need to open the archive ***. Jar. If inside the archive ***. Jar there is no META-INF folder with the file MANIFEST.MF attached to it, then we have an applet that does not support the "main ()" function, i.e. This is an applet launched by the browser.
If inside the ***. Jar archive there is a META-INF folder with the MANIFEST.MF file attached to it, then:
- if in MANIFEST.MF there is the line "Main-Class ...", then we have an applet that runs Java Virtual Machine separately from the browser;
- if in MANIFEST.MF there is a line "Midlet1 - ...", then the MIDlet launched by the emulator is in front of us. The last indicator of the line "Midlet1 - ..." is the class that the MIDlet starts, from which the program starts.
Maybe this option: inside the archive ***. Jar there is a folder META-INF with the file MANIFEST.MF attached to it, but in MANIFEST.MF there is neither the line "Main-Class ..." nor the line "Midlet1 - ... ". This means that we have an applet launched by the browser.
If a Java program is presented in the form of a zip archive or a folder with a set of classes, this also means that we see an applet launched by the browser.
Post has been editedrendor - 27.01.08, 15:17
If inside the ***. Jar archive there is a META-INF folder with the MANIFEST.MF file attached to it, then:
- if in MANIFEST.MF there is the line "Main-Class ...", then we have an applet that runs Java Virtual Machine separately from the browser;
- if in MANIFEST.MF there is a line "Midlet1 - ...", then the MIDlet launched by the emulator is in front of us. The last indicator of the line "Midlet1 - ..." is the class that the MIDlet starts, from which the program starts.
Maybe this option: inside the archive ***. Jar there is a folder META-INF with the file MANIFEST.MF attached to it, but in MANIFEST.MF there is neither the line "Main-Class ..." nor the line "Midlet1 - ... ". This means that we have an applet launched by the browser.
If a Java program is presented in the form of a zip archive or a folder with a set of classes, this also means that we see an applet launched by the browser.
Post has been editedrendor - 27.01.08, 15:17
And one more note concerning the whole topic: there should not be folders with names written in Cyrillic on the way to emulators, virtual Java machines, midlets and applets.If you do not follow this rule, Java will not start.
More details about Java terms and definitions can be found here: http://electra.myff.ru/viewtopic.php?id=6
Post has been editedrendor - 27.01.08, 15:18
More details about Java terms and definitions can be found here: http://electra.myff.ru/viewtopic.php?id=6
Post has been editedrendor - 27.01.08, 15:18
Ii. Installing and running midlets on a PDA
A. Overview of the software used - emulator functions of mobile phones (mobile Java emulators)
Emulators are designed to run midlets (mostly mobile games) on a PDA.
1) TAO Intent Java MIDlet manager (TAO Intent JMM) emulator.
This emulator was installed as a staff device on HTC devices. The manager of midlets, which we see on Cuutecs and I-Meytah, is TAO Intent JMM. With the clipboard, the emulator does not work normally. dFine1107 wrote a script forcing TAO to paste text from the clipboard into the input window, see the messageпїЅ 889689.The 11th version of the emulator has access to the PDA file system. A jad file is not required when installing MIDlets. TAO is more suitable for java games than for working with network midlets. To operate this emulator on any device (and not just on HTC devices), elate.dll patches were developed (for versions 10.1.2.57, 10.1.2.76 and 11.1.7.1023 they were developed by ZuRiUs, and for version 11.1.7.1034 - dFine1107), which dFine1107 included in the cab files modified by him of the TAO versions presented below. Compared with the original versions, dFine1107 also added the ability to install anywhere (Storage, Storage Card, etc., by default it is placed in \ Program Files \ TAO \) and the ability to uninstall by regular means.
- TAO v. 10.1.2.49- the earliest available version, only for WM 2003;
- TAO v. 10.1.2.57- only for WM 2003;
- TAO v. 10.1.2.76- for WM 2003 and WM 5.0;
- TAO v. 11.1.7.1023 (Build 20060907) for communicators- for WM 5.0 and WM 6.0;
- TAO v. 11.1.7.1023 (Build 20060907) NOT for communicators- for WM 5.0 and WM 6.0;
- TAO v. 11.1.7.1034 for communicators- for WM 5.0 and WM 6.0.
There is no patched and modified version of TAO 11.1.7.1034 for communicators.
The original version of TAO 11.1.7.1034 (laid out by volta_john) will start only on HTC devices:TAO v. 11.1.7.1034
.
And in the following versions of TAO 11.1.7.1023 dFine1107 unpacked the zip files target.img.zip and rofs_target.zip from the standard installation kit, which gave a significant increase in the speed of the midlet:
- TAO TurboTweaked v. 11.1.7.1023 (Build 20060907) for communicators(for WM 5.0 and WM 6.0);
- TAO TurboTweaked v. 11.1.7.1023 (Build 20060907) NOT for communicators(for WM 5.0 and WM 6.0).
It is not yet possible to create a TurboTweaked version for TAO 10 due to the fact that if you unzip target.img.zip and rofs_target.zip zip files in 10 versions of TAO, the work of midlets will also be accelerated, but it will become correct to install new midlets It’s impossible, which is most likely a bug of 10 versions. For this reason, before installing midlets, it is necessary to disable Turbo mode each time, that is, restore zip archives. To turn Turbo mode on and off effortlessly, dFine1107 wrote a script that turned Turbo mode on or off with one tap, see its message for details� 871030.
.
In TAO 11 there is 3D, but the bluetooth from the emulator is still not available. Because of this, most games with 3D cannot be run on it - they support multiplayer via bluetooth, and require JSR-82 support from the emulator, which does not exist in TAO for its launch.
All established TAO midlets write to the app-jam-midlets directory, which, depending on various circumstances, can be found in different places.
The TAO versions for smartphones (original archive) were presented by daemonpnz, and the cab installers assembled dFine1107:
TAO.intent.Java.MIDlet.Manager.v10.1.0.14.Build.20040225.en_us.for.WM2003.Smartp
hone.by.dFine.cab
TAO.intent.Java.MIDlet.Manager.v10.1.7.559.Build.20060628.en_us.for.WM5.Smartpho
ne.by.dFine.cab
TAO.intent.Java.MIDlet.Manager.v10.1.7.561.Build.20060726.en_us.for.WM5.Smartpho
ne.by.dFine.cab
A. Overview of the software used - emulator functions of mobile phones (mobile Java emulators)
Emulators are designed to run midlets (mostly mobile games) on a PDA.
1) TAO Intent Java MIDlet manager (TAO Intent JMM) emulator.
This emulator was installed as a staff device on HTC devices. The manager of midlets, which we see on Cuutecs and I-Meytah, is TAO Intent JMM. With the clipboard, the emulator does not work normally. dFine1107 wrote a script forcing TAO to paste text from the clipboard into the input window, see the messageпїЅ 889689.The 11th version of the emulator has access to the PDA file system. A jad file is not required when installing MIDlets. TAO is more suitable for java games than for working with network midlets. To operate this emulator on any device (and not just on HTC devices), elate.dll patches were developed (for versions 10.1.2.57, 10.1.2.76 and 11.1.7.1023 they were developed by ZuRiUs, and for version 11.1.7.1034 - dFine1107), which dFine1107 included in the cab files modified by him of the TAO versions presented below. Compared with the original versions, dFine1107 also added the ability to install anywhere (Storage, Storage Card, etc., by default it is placed in \ Program Files \ TAO \) and the ability to uninstall by regular means.
- TAO v. 10.1.2.49- the earliest available version, only for WM 2003;
- TAO v. 10.1.2.57- only for WM 2003;
- TAO v. 10.1.2.76- for WM 2003 and WM 5.0;
- TAO v. 11.1.7.1023 (Build 20060907) for communicators- for WM 5.0 and WM 6.0;
- TAO v. 11.1.7.1023 (Build 20060907) NOT for communicators- for WM 5.0 and WM 6.0;
- TAO v. 11.1.7.1034 for communicators- for WM 5.0 and WM 6.0.
There is no patched and modified version of TAO 11.1.7.1034 for communicators.
The original version of TAO 11.1.7.1034 (laid out by volta_john) will start only on HTC devices:TAO v. 11.1.7.1034
.
And in the following versions of TAO 11.1.7.1023 dFine1107 unpacked the zip files target.img.zip and rofs_target.zip from the standard installation kit, which gave a significant increase in the speed of the midlet:
- TAO TurboTweaked v. 11.1.7.1023 (Build 20060907) for communicators(for WM 5.0 and WM 6.0);
- TAO TurboTweaked v. 11.1.7.1023 (Build 20060907) NOT for communicators(for WM 5.0 and WM 6.0).
It is not yet possible to create a TurboTweaked version for TAO 10 due to the fact that if you unzip target.img.zip and rofs_target.zip zip files in 10 versions of TAO, the work of midlets will also be accelerated, but it will become correct to install new midlets It’s impossible, which is most likely a bug of 10 versions. For this reason, before installing midlets, it is necessary to disable Turbo mode each time, that is, restore zip archives. To turn Turbo mode on and off effortlessly, dFine1107 wrote a script that turned Turbo mode on or off with one tap, see its message for details� 871030.
.
In TAO 11 there is 3D, but the bluetooth from the emulator is still not available. Because of this, most games with 3D cannot be run on it - they support multiplayer via bluetooth, and require JSR-82 support from the emulator, which does not exist in TAO for its launch.
All established TAO midlets write to the app-jam-midlets directory, which, depending on various circumstances, can be found in different places.
The TAO versions for smartphones (original archive) were presented by daemonpnz, and the cab installers assembled dFine1107:
TAO.intent.Java.MIDlet.Manager.v10.1.0.14.Build.20040225.en_us.for.WM2003.Smartp
hone.by.dFine.cab
TAO.intent.Java.MIDlet.Manager.v10.1.7.559.Build.20060628.en_us.for.WM5.Smartpho
ne.by.dFine.cab
TAO.intent.Java.MIDlet.Manager.v10.1.7.561.Build.20060726.en_us.for.WM5.Smartpho
ne.by.dFine.cab
The CODE tab contains the original (unmodified) versions of this emulator:
Post has been editedrendor - 27.01.08, 15:19
The original versions of the TAO Intent Java MIDlet manager (TAO Intent JMM) emulator presented in this tab
they are installed only in the main memory; they are not loaded onto the Storage card even when using the CabInstaller:
- v. 10.1.2.57:
[url = "http: //savagemessiahzine.com/forum/dl/post/52300/Java_10.1.2.57_WWE.CAB""hhttp://savagemessiahzine.com/forum/dl/post/52300/Java_10.1.2.57_WWE.CAB[/url] (laid out by Sterh78, only WM 2003);
- v. 10.1.2.76:
[url = "http: //savagemessiahzine.com/forum/dl/post/52309/CAB_TaoJava_10.1.2.76_PPC_ENU_17Aug05.cab""http://savagemessiahzine.com/forum/dl/post/52309/CAB_TaoJava_10.1.2.76_PPC_ENU_17Aug05.cab[/url] (laid out by Chuma, WM 2003 and WM 5.0).
To run these versions on non-HTC devices, they need to install the elate.dll patch from ZuRiUs:
[url = "http: //savagemessiahzine.com/ forum / dl / post / deleted / p102971 "] http: //savagemessiahzine.com/ forum / dl / post / deleted / p102971 [/ url],
which should be downloaded and copied to the device
with the replacement of a previously installed file (patch posted on the forum Chuma);
- v. 10.1.7.551:
[url = "http: //savagemessiahzine.com/forum/dl/post/52335/Intent_MIDlet_manager.cab""http://savagemessiahzine.com/forum/dl/post/52335/Intent_MIDlet_manager.cab[/url]] (laid out
Chuma), installed as a regular on Qtek 9100, works only on WM 5.0 and only on devices from HTC;
- v. 11.1.7.1023:
[url = "http: //savagemessiahzine.com/forum/dl/post/52341/JMM.ZIP""hhttp://savagemessiahzine.com/forum/dl/post/52341/JMM.ZIP[/url] (for WM 5.0 and WM 6.0).
The link to download this version of the emulator was provided by unrealwolf, and the attachment was posted on the volta_john forum.
To install this version of the emulator, see the message
volta_john No. 512742: [url = "http: //savagemessiahzine.com/forum/index.php?showtopic=1333&st=300#entry512742" Starting Java MIDlets on the PDA [/ url].
To run this version of the emulator on a device not from HTC, you need to install the elate.dll patch from ZuRiUs into it:
[url = "http: //savagemessiahzine.com/forum/dl/post/52347/elate_tao_11171023.zip""hhttp://savagemessiahzine.com/forum/dl/post/52347/elate_tao_11171023.zip[/url]
The elate.dll file in the elate_by_ZuRiUs folder is intended for communicators, and
The elate.dll file in the elate_NO_SMS_by_ZuRiUsp folder is NOT for communicators and does not work with SMS.
This file should be downloaded and copied to the device with the replacement of the previously installed file.
.
TAO Intent JMM, established in main memory, on devices with WM 2003, can be manually transferred to a memory card along with midlets,
installed in his manager, and he will continue his work already on the map without any problems. For more on this, see
in the message number 364653: [url = "http: //savagemessiahzine.com/forum/index.php?showtopic=1333&st=120#entry364653" Starting Java MIDlets on your PDA [/ url].
.
Deleting the original versions of the TAO Intent JMM emulator presented in this tab is a whole problem, as many removers
they are not seen. However, SK Tools and regular uninstallers on devices with WM 5.0 see early versions of TAO under the name Customization Tools. If
There is no such name in the list for deletion, you need to either make a hard-cut, or delete TAO manually. Chuma posted a list of files in this thread,
created by this emulator, which must be deleted: [url = "http: //savagemessiahzine.com/forum/index.php?showtopic=1333&st=30#entry107063" Starting Java Midlets on your PDA [/ url]
they are installed only in the main memory; they are not loaded onto the Storage card even when using the CabInstaller:
- v. 10.1.2.57:
[url = "http: //savagemessiahzine.com/forum/dl/post/52300/Java_10.1.2.57_WWE.CAB""hhttp://savagemessiahzine.com/forum/dl/post/52300/Java_10.1.2.57_WWE.CAB[/url] (laid out by Sterh78, only WM 2003);
- v. 10.1.2.76:
[url = "http: //savagemessiahzine.com/forum/dl/post/52309/CAB_TaoJava_10.1.2.76_PPC_ENU_17Aug05.cab""http://savagemessiahzine.com/forum/dl/post/52309/CAB_TaoJava_10.1.2.76_PPC_ENU_17Aug05.cab[/url] (laid out by Chuma, WM 2003 and WM 5.0).
To run these versions on non-HTC devices, they need to install the elate.dll patch from ZuRiUs:
[url = "http: //savagemessiahzine.com/ forum / dl / post / deleted / p102971 "] http: //savagemessiahzine.com/ forum / dl / post / deleted / p102971 [/ url],
which should be downloaded and copied to the device
with the replacement of a previously installed file (patch posted on the forum Chuma);
- v. 10.1.7.551:
[url = "http: //savagemessiahzine.com/forum/dl/post/52335/Intent_MIDlet_manager.cab""http://savagemessiahzine.com/forum/dl/post/52335/Intent_MIDlet_manager.cab[/url]] (laid out
Chuma), installed as a regular on Qtek 9100, works only on WM 5.0 and only on devices from HTC;
- v. 11.1.7.1023:
[url = "http: //savagemessiahzine.com/forum/dl/post/52341/JMM.ZIP""hhttp://savagemessiahzine.com/forum/dl/post/52341/JMM.ZIP[/url] (for WM 5.0 and WM 6.0).
The link to download this version of the emulator was provided by unrealwolf, and the attachment was posted on the volta_john forum.
To install this version of the emulator, see the message
volta_john No. 512742: [url = "http: //savagemessiahzine.com/forum/index.php?showtopic=1333&st=300#entry512742" Starting Java MIDlets on the PDA [/ url].
To run this version of the emulator on a device not from HTC, you need to install the elate.dll patch from ZuRiUs into it:
[url = "http: //savagemessiahzine.com/forum/dl/post/52347/elate_tao_11171023.zip""hhttp://savagemessiahzine.com/forum/dl/post/52347/elate_tao_11171023.zip[/url]
The elate.dll file in the elate_by_ZuRiUs folder is intended for communicators, and
The elate.dll file in the elate_NO_SMS_by_ZuRiUsp folder is NOT for communicators and does not work with SMS.
This file should be downloaded and copied to the device with the replacement of the previously installed file.
.
TAO Intent JMM, established in main memory, on devices with WM 2003, can be manually transferred to a memory card along with midlets,
installed in his manager, and he will continue his work already on the map without any problems. For more on this, see
in the message number 364653: [url = "http: //savagemessiahzine.com/forum/index.php?showtopic=1333&st=120#entry364653" Starting Java MIDlets on your PDA [/ url].
.
Deleting the original versions of the TAO Intent JMM emulator presented in this tab is a whole problem, as many removers
they are not seen. However, SK Tools and regular uninstallers on devices with WM 5.0 see early versions of TAO under the name Customization Tools. If
There is no such name in the list for deletion, you need to either make a hard-cut, or delete TAO manually. Chuma posted a list of files in this thread,
created by this emulator, which must be deleted: [url = "http: //savagemessiahzine.com/forum/index.php?showtopic=1333&st=30#entry107063" Starting Java Midlets on your PDA [/ url]
Post has been editedrendor - 27.01.08, 15:19
On TAO, this problem periodically arises - when installing or removing the next midlet, the process somehow hangs and suddenly ends with the user interface of the emulator suddenly being empty. For a quick treatment method, see message No. 472209:Method for quick recovery of a booted TAO
Post has been editedrendor - 27.01.08, 15:20
Post has been editedrendor - 27.01.08, 15:20
2a) IBM J9 WEME MIDP20 JMM - another java emulator. The full name of this program is The J9 VM, the Web of the WebSphere Everyplace Micro Environment (WEME), and the JVM Specification.
img-21373-333333.gif
Description and download linkold version (v. 1.3) of this emulator, also known under the name of its cab-file weme-midp20-wm2003-arm_22.cab, are in message No. 218058: IBM J9 WEME MIDP20 JMM v. 1.3 The version also works on WM 5.0.
.
2b) New version of the emulator IBM J9 WEME MIDP20 JMM - v. 6.1.0 also works on WM 5.0 and WM 6.0 . The options laid out here have JSR75 support by installing a patch, as well as VGA support. Direct download links:
- version for QVGA (cab-file):IBM J9 WEME MIDP20 JMM - v. 6.1.0 - QVGA(collected yukon_28);
- version for VGA (cab-file):IBM J9 WEME MIDP20 JMM - v. 6.1.0 - VGA(assembled dFine1107).
Post has been editedrendor - 27.01.08, 15:20
img-21373-333333.gif
Description and download linkold version (v. 1.3) of this emulator, also known under the name of its cab-file weme-midp20-wm2003-arm_22.cab, are in message No. 218058: IBM J9 WEME MIDP20 JMM v. 1.3 The version also works on WM 5.0.
.
2b) New version of the emulator IBM J9 WEME MIDP20 JMM - v. 6.1.0 also works on WM 5.0 and WM 6.0 . The options laid out here have JSR75 support by installing a patch, as well as VGA support. Direct download links:
- version for QVGA (cab-file):IBM J9 WEME MIDP20 JMM - v. 6.1.0 - QVGA(collected yukon_28);
- version for VGA (cab-file):IBM J9 WEME MIDP20 JMM - v. 6.1.0 - VGA(assembled dFine1107).
Post has been editedrendor - 27.01.08, 15:20
In the CODE tab - version 6.1.0 for VGA previously posted on the forum:
Post has been editedrendor - 27.01.08, 15:21
Version 6.1.0 for VGA, referenced below:
[url = "http: //savagemessiahzine.com/forum/dl/post/52322/weme_wm50_arm_hires_midp20_6.1.0.20060317_111429.zip"[http://savagemessiahzine.com/forum/dl/post/52322/weme_wm50_arm_hires_midp20_6.1.0.20060317_111429.zip[/url]
This is not an exe or cab distribution, but a copy of the contents of the IBM installation folder on the PDA.
The order of its installation, see the message volta_john в„– 353237: [url = "http: //savagemessiahzine.com/forum/index.php?showtopic=1333&st=120#entry353237" Start the Java MIDlet on the PDA [/ url]
[url = "http: //savagemessiahzine.com/forum/dl/post/52322/weme_wm50_arm_hires_midp20_6.1.0.20060317_111429.zip"[http://savagemessiahzine.com/forum/dl/post/52322/weme_wm50_arm_hires_midp20_6.1.0.20060317_111429.zip[/url]
This is not an exe or cab distribution, but a copy of the contents of the IBM installation folder on the PDA.
The order of its installation, see the message volta_john в„– 353237: [url = "http: //savagemessiahzine.com/forum/index.php?showtopic=1333&st=120#entry353237" Start the Java MIDlet on the PDA [/ url]
Post has been editedrendor - 27.01.08, 15:21
The emulator, when launched, forms the manager of the midlet under the name "Midlet HQ". He writes all the established midlets in My Documents / temp. After deleting a midlet from the "Midlet HQ", it may not be automatically removed from this folder, you need to check it and, if necessary, delete it manually. The emulator works well on the Storage card. Jad-file when installing midlets is not required. Works with clipboard.
The new version of the emulator works much better than the previous one.
But - the emulator eats up a lot of memory, while before performing any action, it analyzes the presence of memory, and if it is small, the action is not performed. For example, there is not enough memory to load the emulator (4.5 Mb) - it does not load, there is not enough memory to load Opera mini (5 Mb) - it does not load, and we do not receive any messages. If any game seems to start to open, but then everything slows down, it is also a signal to see how much memory is left. If you increase the slider memory for programs (relevant only for WM 2003), then everything starts to work.
Here -IBM J9 WEME MIDP20 JMM manual:
Post has been editedrendor - 27.01.08, 15:21
The new version of the emulator works much better than the previous one.
But - the emulator eats up a lot of memory, while before performing any action, it analyzes the presence of memory, and if it is small, the action is not performed. For example, there is not enough memory to load the emulator (4.5 Mb) - it does not load, there is not enough memory to load Opera mini (5 Mb) - it does not load, and we do not receive any messages. If any game seems to start to open, but then everything slows down, it is also a signal to see how much memory is left. If you increase the slider memory for programs (relevant only for WM 2003), then everything starts to work.
Here -IBM J9 WEME MIDP20 JMM manual:
Post has been editedrendor - 27.01.08, 15:21
If in v. 6.1.0 for QVGA You didn’t like the font, you can replace it with a larger or more sparse font, see message No. 324711 for details:Fonts for IBM J9 WEME MIDP20 JMM v. 6.1.0 for QVGAAn alternative way to replace the font, see the message Vadya corp. No. 468394:Another way to replace the font in IBM J9 WEME MIDP2.0
Post has been editedrendor - 27.01.08, 15:21
Post has been editedrendor - 27.01.08, 15:21
The standard IBM J9 WEME MIDP20 JMM bundle does not support the JSR75 specification, which prevents midlets running on this emulator from viewing the PDA file system. However, there is a small 20-kilobyte patch, the installation of which in the emulator adds the specified specification to it, with the result that the MIDlets running on this emulator (for example, Opera mini) begin to see the PDA file system in full. Direct link to download the patch:j9fix.zipThe patch is installed in the emulator according to the instructions attached to it. After installing the patch, we reconfigure the permissions of the modified Opera mini in the MIDlet HQ - Actions ->Permissions: Comm, File Read and File Write must be set to Always allowed (settings provided by volta_john). As a result, the modified Opera mini turns into a full-featured browser that can download any files (and with resume) to the PDA file system with its own means (without the support of an external browser). Downloaded files can then be opened in a naive (genuine) format.
Post has been editedrendor - 27.01.08, 15:22
Post has been editedrendor - 27.01.08, 15:22
The way to eliminate the security requests of the IBM J9 emulator, including allowing access to the network (if it bothers you), was posted by Yago De Malina in a messageпїЅ 886752.
Post has been editedrendor - 27.01.08, 15:22
Post has been editedrendor - 27.01.08, 15:22
IBM is sometimes buggy - all the installed midlets or bookmarks in Opera Mini run, Opera Mini loads white sheets, and then stops running at all, etc. For a quick treatment method, see message No. 472209:Method for quickly restoring IBM startup
Post has been editedrendor - 27.01.08, 15:22
Post has been editedrendor - 27.01.08, 15:22
3) Coretek Delta java manager - Java emulator, used mainly for launching Java games, allows you to use many games that are not running on other emulators. Works with clipboard. The screen size is 176x220, like on a smartphone, there is a separate topic on the emulator: Coretek Delta java manager
img-21441-1112333.jpg
The earliest version presented on the forum — the 2003 version — was translated from Chinese into English by Chuma (see the screenshot). This version creates the Coretek folder in the main memory in Program Files, all games are installed in it. In the case of deleting the game, it is easily removed from this folder. When installing midlets, a jad file is required. On WM 5.0, this version only works in the original (Chinese) version.
The new version of 2006 is designed for WM 5.0, but just like the previous one, it is sharpened for smart phones. On pockets it works with a resolution of 176x220. This version fully complies with the specifications from Sun (even the forms are the same as in official emulators), games are installed from jar (no jad is needed), originally in English, works from a memory card. On WM 2003 does not work at all. The version for the Storage Card is installed according to the instructions from the downloaded archive. The "com" folder is used to adapt midlets.
Direct download links (all versions are posted by Chuma):
2003 version:Coretek Delta java manager
New (2006) version for WM 5.0 and WM 6.0 (cab):Java.Coretek.MIDP.2.1.Bundle.cab
New (2006) version for WM 5.0 and WM 6.0 for installation on a Storage card:Coretek2_Storage_Card.rar
Post has been editedrendor - 27.01.08, 15:23
img-21441-1112333.jpg
The earliest version presented on the forum — the 2003 version — was translated from Chinese into English by Chuma (see the screenshot). This version creates the Coretek folder in the main memory in Program Files, all games are installed in it. In the case of deleting the game, it is easily removed from this folder. When installing midlets, a jad file is required. On WM 5.0, this version only works in the original (Chinese) version.
The new version of 2006 is designed for WM 5.0, but just like the previous one, it is sharpened for smart phones. On pockets it works with a resolution of 176x220. This version fully complies with the specifications from Sun (even the forms are the same as in official emulators), games are installed from jar (no jad is needed), originally in English, works from a memory card. On WM 2003 does not work at all. The version for the Storage Card is installed according to the instructions from the downloaded archive. The "com" folder is used to adapt midlets.
Direct download links (all versions are posted by Chuma):
2003 version:Coretek Delta java manager
New (2006) version for WM 5.0 and WM 6.0 (cab):Java.Coretek.MIDP.2.1.Bundle.cab
New (2006) version for WM 5.0 and WM 6.0 for installation on a Storage card:Coretek2_Storage_Card.rar
Post has been editedrendor - 27.01.08, 15:23
4) Esmertec Java - Another emulator for Windows Mobile 5.0. The forum has versions for PDAs and for smart.
Esmertec Java for WM 5.0 For Pocket versions:
- Jeodek.zip Build 20060420(laid out by ZuRiUs);
- Jeodek.rar Build 20061013(laid out mUn);
- Esmertec Java from O2 - only for VGA(posted mr_smith2005);
- Jeodek Java Build 20070425(laid out dFine1107). If you want to Russify this version of the emulator, read the message dFine1107пїЅ 890414.
Comments ZuRiUs to the version laid out by him: The emulator is designed to work with communicators. If it is NOT used on the communicator, then it is necessary to replace the jeodek.exe file with the same file from the attached jeodek_no_sms archive and to prevent the SMS from working with SMS in this case! (for the possibility of downloading not on communicators, ZuRiUs removed the import from sms.dll).
Post has been editedrendor - 27.01.08, 15:23
Esmertec Java for WM 5.0 For Pocket versions:
- Jeodek.zip Build 20060420(laid out by ZuRiUs);
- Jeodek.rar Build 20061013(laid out mUn);
- Esmertec Java from O2 - only for VGA(posted mr_smith2005);
- Jeodek Java Build 20070425(laid out dFine1107). If you want to Russify this version of the emulator, read the message dFine1107пїЅ 890414.
Comments ZuRiUs to the version laid out by him: The emulator is designed to work with communicators. If it is NOT used on the communicator, then it is necessary to replace the jeodek.exe file with the same file from the attached jeodek_no_sms archive and to prevent the SMS from working with SMS in this case! (for the possibility of downloading not on communicators, ZuRiUs removed the import from sms.dll).
Post has been editedrendor - 27.01.08, 15:23
©savagemessiahzine.com2005-2019. All rights reserved.
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement