Introduction Java-programs from running on the PDA tapom in the program file or shortcut. Initially Java-program must be installed in the emulator. On most mobile device emulators are included in the standard set of programs, in their name, they usually have the word В«JavaВ» or В«MIDLetВ». Ideally, all of the action should take place in 2 tapa stylus - first tapom on the program file (file type *** jar.) Java-program is installed in the emulator and then tapom the program icon in the window of the emulator runs the program.
But since there is provided the ideal Java-compatible program emulator and PDA operating system. Getting started with Java on your PDA, you need to bear in mind that the majority of Java-programs written for other types of mobile devices - mobile phones. And yet - Windows for reasons of non-program does not contain a character naitivnoy support Java. Therefore, we are dealing with Java emulation, which by definition is "an imitation of work by means of a system of another without loss of functionality and distortion of the results." But it is not an imitation of the original script. To implement it in practice without any loss of 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!” :-)
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.
.
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).
.
Servlet is a program written in JEE. Within the framework of this topic, we will not consider servlets and JEE.
.
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.
For sale on the desktop and mobile computers perform MIDlet need to simulate (emulate) mobile phone behavior, such as: Display only one and there is no moving of windows, soft-keys and numeric keypad, to draw only the canvas with a limited set of functions for text input there a standard set of input fields - that's all it is necessary to implement in the form in which it is presented in a particular phone or in some hypothetical phone. This feature on computers (including PDAs) perform
mobile phone function emulators Converting codes JME usually in JSE / JEE codes (and their subsequent transmission to the built-in Java Virtual Machine emulator), or directly into the operating system or processor codes. Among emulators running on the PDA are represented here: TAO Intent Java MIDlet manager, IBM J9 WEME MIDP20 JMM, Coretek Delta java manager, Mitac JVM, Esmertec Java, CrEme JVM. Emulators mobile phone functions commonly referred to as emulators MIDlet or the Java emulator, sometimes managers MIDlet, although MIDlet Manager - is a user interface emulator.
Thus, the virtual Java machine running on desktop and notebook computers, is performed as a rule, programs written in the JSE, ie applets. JME codes, which are written MIDlets, Java Virtual Machine, with rare exceptions, do not understand and therefore to work with MIDlets can not. According to a statement of reasons or games for mobile phones or Opera mini run on the Java Virtual Machine can not be. An exception to this statement is the Java virtual machine CrEme JVM, which is built on top of the JSE - emulator for execution JME code with modest abilities, allows 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.
.
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.
.
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.
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 can access the PDA file system. Jad-file when you install MIDlet is not required. TAO is more suitable for java-games than to work with network MIDlet. To work within the emulator on any devaysakh (and not only on a device from HTC) elate.dll patches have been developed (for versions 10.1.2.57, 10.1.2.76 and their 11.1.7.1023 developed ZuRiUs, and for version 11.1.7.1034 - dFine1107), dFine1107 that included a modified their cab-files listed below versions TAO. Compared with the original version dFine1107 also added the ability to install in any location (Storage, Storage Card, and so on, by default placed in the \ Program Files \ TAO \) and the ability to uninstall 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).
Produce version TurboTweaked for TAO 10 is not yet possible due to the fact that if in the 10's versions TAO unpack the zip-files and target.img.zip rofs_target.zip, the MIDlet work will also be accelerated, however, correctly install new MIDlets will it is impossible that the most likely is a bug 10th version. For this reason, before installing the MIDlet is necessary each time to turn off Turbo mode, t. E. To restore the zip-archives. To enable or disable Turbo mode effortlessly dFine1107 wrote the script, with a single tap enables or disables Turbo Mode, for details, see. His message
пїЅ 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.Smartphone.by.dFine.cabTAO.intent.Java.MIDlet.Manager.v10.1.7.559.Build.20060628.en_us.for.WM5.Smartphone.by.dFine.cabTAO.intent.Java.MIDlet.Manager.v10.1.7.561.Build.20060726.en_us.for.WM5.Smartphone.by.dFine.cabThe CODE tab contains the original (unmodified) versions of this emulator:
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]http://savagemessiahzine.com/forum/dl/post/52300/Java_10.1.2.57_WWE.CAB[/URL] (posted 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] (posted 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
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
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 в„– 512742: [URL = http: //savagemessiahzine.com/forum/index.php?showtopic=1333&st=300#entry512742]Zapusk Java-midlet on a 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
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
the report number 364653: [URL = http: //savagemessiahzine.com/forum/index.php?showtopic=1333&st=120#entry364653]Zapusk Java-midlet on a 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 emulator data that need to be removed: [URL = http: //savagemessiahzine.com/forum/index.php?showtopic=1333&st=30#entry107063]Zapusk Java-midlet on a PDA [/ URL]
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.
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.
Description and download link
old 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).
In the CODE tab - version 6.1.0 for VGA previously posted on the forum:
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
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 report volta_john в„– 353237:. [URL = http: //savagemessiahzine.com/forum/index.php?showtopic=1333&st=120#entry353237]Zapusk Java-midlet on a PDA [/ URL]
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 - emulator eats up a lot of memory, thus before any action it analyzes the presence of memory, and if it is small, the action is not performed. For example, not enough memory to load the emulator (4.5 MB) - it is not loaded, do not have enough memory to download Opera mini (5 MB) - it is not loaded, we do not get any messages at the same time. If any game there seems to be beginning to open, but then braked, it is also a signal to that to see - how much memory is left. If the slider to increase the memory to run programs (important for WM 2003 only), then everything starts to work.
Here -
IBM J9 WEME MIDP20 JMM manual: img-35017-install.zip (287.94 KB)
.
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.
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.
.
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.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.
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 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 2006 version is designed for WM 5.0, but in the same way as the previous one, sharpened by SMART. On Pocket works with a resolution of 176x220. This version is fully consistent with the specifications from Sun (of even shape are the same as in the official. Emulators), the installation is carried out games jar (not necessary jad), initially in English, it works with memory cards. At the WM 2003 is not working at all. Version Storage Card is installed according to instructions from the downloaded archive. Folder "com" is used to adapt the MIDlet.
Direct download links (all versions are posted by Chuma):
2003 version:
Coretek Delta java managerNew (2006) version for WM 5.0 and WM 6.0 (cab):
Java.Coretek.MIDP.2.1.Bundle.cabNew (2006) version for WM 5.0 and WM 6.0 for installation on a Storage card:
Coretek2_Storage_Card.rar.
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).
Pros of this emulator (according to ZuRiUs): faster than Tao; It is launched without any installation from anywhere (MIDlets are also saved in the working folder of the program); works with the clipboard. Cons (also according to ZuRiUs): does not work with the PDA file system; less stable than tao.
The program file of this emulator is called jeodek.exe, and therefore errors often occur associated with its identification.
Esmertec Java Version for Windows Mobile 5.0 For Smartphoneposted volta_john, and a link to download provided unrealwolf. Direct download link:
Esmertec Java For Smartphone.
5) JBlend - emulator for Windows Mobile 5.0 For Smartphone, posted on the daemonpnz forum. Direct download link:
JBlendFullScreen . Works on full screen, soft keys work.
.
6) Mitac JVM - Another emulator for Windows Mobile For Smartphone, posted on the santass forum. Direct download link:
Mitac JVM .
7) CrEme JVM . The CrEme Java Virtual Machine (see below) can also serve as an emulator.
.
If, when trying to install emulators on a device with WM 5.0, the system scolds about certificates, you can disable their checking. There are two ways (laid out in this EuGenEr topic):
1) Run
Disable security.cab(posted on the soloslava forum).
2) Download
Device Security Manager PowerToy for Windows Mobile 5.0, attach the poket to the BB, and follow the instructions on the Microsoft website to disable security.
.
B. The procedure for installing and running MIDlets on the PDA The emulators presented above form at startup midlet managers, which are the user interface of emulators. Therefore, midlets, as a rule, are first installed in midlet managers, and then they are launched from managers.
To install the MIDlet in the manager, just tap the stylus on the ***. Jar file , and the midlet will install on its own. You can also tap on the MIDlet jar for a long time, click on "Open with ..." in the Resco Explorer context menu, and select the name under which the emulator is listed in the list of programs.
Or you can open the manager first, the further procedure will depend on the emulator used:
- in emulator managers
TAO Intent JMM and
Esmertec Java you need to tap on "Install", the manager will show the jar files available on the PDA (TAO will show the jar files that are in the root directory of the memory card and in the My Documents \ My Midlet folder, and Esmertec Java - no more than 180 positions), then tap to the desired jar file, and it will be installed in the manager;
- in the emulator manager
IBM J9 WEME MIDP20 JMM (all versions presented on the forum) must be indicated in time
url the path to the midlet (for example, located on the memory card) as follows:
file: // \ Storage card \ midlet name.jar . The specified format of the path was posted on the Konrad forum. Some descriptions mistakenly indicate a slightly different path format, but it should be borne in mind that there are no other options besides the specified
file: // \ .... \ .... \ .... \ ***. jar (without spaces) does not exist.
.
MIDlets installed in MIDlet managers are launched by tapping on the corresponding icon or by clicking on Launch.
.
Problems running midlets on the TAO Intent JMM emulator: 1) If the TAO Intent JMM emulator of any of the versions presented on the forum has started,
but when you run the MIDlets installed in it, an error message appears usually helps reinstall the system font tahoma.ttf on the PDA (I personally tried it on Asus P535). We take the font tahoma.ttf from the PC, and it is mandatory from Windows XP (the 2000th and other versions do not fit!), And we replace it with the Resko Explorer using the native PDA in the Windows folder. Resko swears that they say the file in Rum is dangerous, but we can safely replace it. After soft-rezet, and TAO will start to run midlets (the method is posted on the forum by Mforward). Direct link to download this font:
Tahoma.ttf If replacing the tahoma.ttf font does not work, you can try replacing the rofs_target.zip file (located in the Windows directory, or if the TAO is on the map, then in the program folder c) with the attachment of the same name posted on the Mforward forum:
rofs_target_fonts.rar , do soft-rezet (! Attachment is suitable only for version 10.1.2.76!).
2) When Opera mini mods work on TAO 11 on many devices, there are constant errors when trying to load web pages, in fact, not a single web page can be downloaded. This is not a problem with Opera mini mods; most likely there is an error in the implementation of the http protocol in TAO 11. TAO 11 is treated according to Mforward’s method, see his message:
пїЅ 933641 3) If the network midlet at each tap asks for permission to access the Internet / network, see the solution to this problem in the VecH message dated 12/19/06
пїЅ 470277. You can also disable all security system requests in TAO; for the disconnection procedure, see message dFine1107
пїЅ 895819. 4) If the font in TAO is too small, it can be increased by editing the registry, see the VecH message
пїЅ 895764. .
Some features of running midlets on the IBM J9 emulator: 1) If you do not want to install MIDlets in the manager of the IBM J9 WEME MIDP20 JMM emulator, you can launch midlets using shortcuts. If the specified emulator and the MIDlet it launches are on the Storage card, the shortcut for launching the MIDlet looks like this:
77 # "\ Storage card \ IBM MIDP20 \ bin \ emulator.exe" "-Xdescriptor: \ Storage card \ Opera mini \ opera117.jar" (samples posted by Konrad and VitAR). This sample can be used to run any midlet, while changing only the file paths. Other parameters of this pattern, including the placement of quotation marks and spaces, cannot be changed. Sample labels can also be downloaded from this link (attachment to Konrad post):
MIDLETS.zip . When you start the midlet through the specified shortcut, it is temporarily installed in the emulator, and at the end of work, it is uninstalled. Therefore, the history and bookmarks in Opera mini are not saved with this launch method.
2) Tap on a shortcut of the following type:
77 # "\ Storage card \ IBM MIDP20 \ bin \ emulator.exe" "-Xjam: run = 1" MIDlets are launched directly, without starting the midlet manager of the IBM emulator. The last digit is the midlet serial number in the list of installed midlets. The specified shortcut can be displayed on the desktop (for this we first place it in the Windows / Start Menu / Programs folder) and run midlets with one tap on it (a sample shortcut was posted by Isidor). Run midlets in this way, i.e. Without starting the MIDlet manager, you can only use the IBM emulator.
.
The procedure for installing midlets in the emulator Coretek Delta java manager slightly different from the above. For details on installing MIDlets in the 2003 emulator, see the topic:
Coretek Delta java manager . To install midlets in new versions of the emulator for WM 5.0, you need to tap on the midlet jar file for a long time, click on "Open with ..." in the Resco Explorer context menu, and select jarinstall in the program list (this program is in the same folder as the emulator program file).
When you start the game on Coretek'e in most cases, the virtual keyboard is disabled. To fix this, you must not closing Coretek, run any program using the virtual keyboard (for example, click the Calendar hard button), and without closing the program, switch to Coretek. As a result, the keyboard does not disappear and is still active (the method laid volta_john). Osutstvie in the bottom bar soft keys when the game starts to Coretek'e does not mean that they are not there. They are simply invisible and are side by side in the lower left corner of the bar, is very narrow. However, do not always work, though, and properly pressed.
.
The procedure for launching midlets with the Java virtual machine CrEme JVM also very specific. If you can’t start running the MIDlets with a tap on the ***. Jad file, you should read the detailed statement of this issue in message No. 213155:
Features of launching midlets with the Java virtual machine CrEme .
The procedure for running midlets with the Esmertec Java emulator versions
for WM 5.0 For Pocket does not have any features. The procedure for launching midlets posted on the forum version
for WM 5.0 For Smartphone detailed in volta_john in communication No. 398636:
Launching midlets with Esmertec Java emulator .
On BenQ P50 and Gigabyte G'Smart smartphones emulators are installed (on BenQ P50 - iaJET, and on Gigabyte G'Smart - III iJet). These emulators are united by the fact that midlets on them are launched by tap on a file
***. jad . In addition, you must place midlets on these devices (jar and jad files) in the root directory, or edit
jad -file of the midlet, indicating in it the actual path along which it is located
jar -file of this midlet. To do this, you need to
jad -file (for example Jimm.jad) find the line MIDlet-Jar-URL: Jimm.jar and fix it on something like this: MIDlet-Jar-URL: file: // \ Storage \ JAVA \ Jimm.jar, i.e. the actual location of the jar file on your typewriter.
.
About jad files: Since some emulators, as well as the CrEme Java virtual machine, run MIDlets through jad-files (small files that contain various characteristics of jar-files, i.e. midlets), it is necessary in such cases to the folder with the ***. Jar file place (before installing the MIDlet in the manager) and the file of the same name ***. jad, i.e. these files should be near, for example:
Opera mini.jar
Opera mini.jad.
If the ***. Jad file is missing, select it from the ***. Jar file on the desktop PC using the program
Jadmaker(posted on the Chuma forum). Launch Jadmaker on the desktop PC, right-click on the file ***. Jar, then on the line “Make JAD” in the context menu, and the file ***. Jad appears.
It is also possible to select the jad file directly on the PDA by editing the Manitest.mf file; for more details, see message volta_john No. 365262:
Making jad files for midlets on PDAs.
Links to Java games running on PDAs: Using the link below, you can open a large base with games for SonyEricsson s700, most of which run normally and work on PDAs (posted by Chuma):
Games for SE s700(namely, games from SonyEricsson s700 run best and work on the PDA).
Links to direct download of individual games launched on the PDA (also posted by Chuma):
Asphalt urban,
Redaction,
Allods,
DoomChuma wrote about the Doom game: "Use the 0, *, # buttons on the on-screen keyboard (7- change weapons). Pretty playable."
GravityDefied, laid out Citrus:
GravityDefiedAnd 10 more games posted by Konrad:
MIDLETS.zipI also posted in this thread an archive with 100 games - MIDlets that normally run on PDAs, a download link:
PDA Java GamesThe forum also has a topic where games - midlets are laid out separately with pictures and a description:Java Games for the car of the same name .
How to adapt midlets that do not start on the PDA: You should not think that emulators for PDAs will be able to launch any midlet from any phone. Something will start, and something not. Games from Nokia, which usually do not start on PDA emulators, can be converted to a format suitable for playback on emulators for Windows mobile using special programs to adapt midlets
Motomidman and FullJava (links were posted by volta_john and Chuma respectively), for details see message No. 391312:
Motomidman & FullJava. There is also a universal program
Javaadapter (posted by sergey109), which converts games from various phone models - Nokia, Samsung, Sony-Ericsson, Siemens and others into a format suitable for playback on PDAs. But there is no 100% guarantee that the adaptation will be successful. Conversion to a format suitable for playback on a PDA can also be easily performed directly on a PDA manually using a folder
com containing specific classes from Nokia and nested inside the midlet, for more details, see message volta_john No. 467061:
Adaptation of midlets for Nokia mobile phones directly to the PDA. .
The adapted midlet started, but it’s still impossible to control it: :-{
There is also a lot of games, which, although they are run on a PDA, but playing them is almost impossible (such as Splinter Cell, Spider Man). You press the button, and the hero rushes forward as far as the program allows it to move in this direction, then stops, and to spice it up, you have to press a few keys, and then everything is repeated. Play, of course, impossible. In addition, many of the game after only managed to adapt to the virtual keyboard, and thus there is a problem that the numbers 1, 2, 3 on a mobile phone placed in the top row of keys, respectively, that are programmed and games. On the PDA, these numbers are located on the bottom row, and therefore the management of the CCP with the heroes of games moved as though in the wrong direction.
You can fix these problems by installing advanced keyboards from the MacCenter or from Resco (I put Resco in second place, since it does not correct the situation in all games), as well as the patch from volta_john, for more details, see volta_john message No. 435173 about this:
Management in java games (midlets). Known problems and some ways to solve them. The troubleshooting methods outlined by volta_john also work on WM 5.0.
.
Midlet started and waits for pressing the soft button. What to do? : mellow:
Thanks to the midlet adaptation program
JavaMagic MIDlets are beginning to respond to the pressing of the real or virtual soft buttons on your PDA. This is achieved, or by transferring the original midlet action soft buttons on the other (virtual) devaysa button, or by entering the source midlet codes soft-buttons understood emulator TAO 11 (from the emulator until only he support soft buttons). As a result of such adaptation MIDlet starts to take actions that it should respond to pressing the soft keys on the device. Those. emulator TAO 11 real soft buttons can now be used to control the MIDlet and other emulators action soft keys is transferred to the other keys, such as virtual buttons * and #. For more details see the report volta_john в„– 780872.:
Instructions for changing the encoding of buttons used in the MIDlet using JavaMagic software. (link to download and initial instructions for use provided by unrealwolf). Direct link to download JavaMagic with instructions from volta_john:
JavaMagic .
The telephone keypads available on some communicator models are not supported by Java emulators for Pocket PC. Smart Java emulators support both the telephone keypad and soft keys. Installing emulators for smartphones on Pocket PC is not recommended.
.
Java games on the desktop PC: Almost any MIDlet can run on an emulator MidpX Desktop from programmer Kwyshell'a. Weight emulator - only 1.7 MB, downloaded via the link:
Midpx(link posted by Chuma).
Another option for desktop PC - selection in the amount of 130 whith best MIDlet, recompiled at the JSE, which are with very good quality and large screen are run on a PC with the help of Free Java-player Mpowerplayer, see details in the report number 391335:.
Mpowerplayer.
III. PDA applets launch A. Overview of Software Used - Java Virtual Machine (Java Virtual Machines) Virtual Java machines are designed to run applets on a PDA.
1) CrEme JVM - a virtual Java machine from the group of companies "The NSI group":
1a) Version 4.10 Available in 2 versions - for WM 2003 and for WM 5.0. Direct download links:
- version 4.10 for WM 2003, installation with BB, you will need to install the patch:
CrE_ME410_ARM_CE42_PPC.rar- cab file version 4.10 for WM 2003, assembly dFine1107, the patch is applied and the patched file is packaged in CAB:
CrE_ME410_ARM_CE42_PPC_by_dFine- version 4.10 for WM 5.0, installation with BB, you will need to install the patch:
CrE_ME410_ARM_CE50_PPC.rar - cab-file version 4.10 for WM 5.0, assembly dFine1107, the patch is applied and the patched file is packaged in CAB:
CrE_ME410_ARM_CE50_PPC_by_dFine1b) Version 4.12 , cab-file, assembly dFine1107, works on WM2003 and higher:
CrE_ME412_ARM_CE42_PPC__dFine_mod It can be used both for working with applets running separately from the browser, and as a Java plug-in for Internet Explorer. This Java machine is preferably installed in the main memory. When installing it on a Storage card, she refused to open applets that run separately from the browser. However, as a Java plug-in for IE, it can work fine with a memory card.
It should also be noted that CrEme, unlike other virtual Java machines, has an add-on over JSE - an emulator for running midlets, with fairly modest capabilities that allow you to run small midlets.
.
2) Jeode Runtime Java Virtual Machine - Another virtual Java machine. Direct download link:
Jeode Java Virtual Machine PPC300 2577.cab . It can be used both for working with applets running separately from the browser, and as a Java plug-in for Internet Explorer. When installing on a memory card, this Java machine did not even open a test applet for me, so it is also recommended to install it in the main memory. However, as a Java plug-in, it can also work normally with a memory card.
.
3) Mysaifu JVM - a virtual Java machine by which exception opened a separate topic on the forum:
Mysaifu JVM The topic has a description and direct download links. This Java machine can only be used to work with applets that run separately from the browser; it does not have a Java plug-in.
.
4a) IBM J9 PPRO10 JVM - a virtual Java machine from IBM, the cab file is named: weme-ppro10-wm2003-arm_22.cab. Direct download link:
IBM_J9_PPRO10_JVM.rar. It can only be used to work with applets that run separately from the browser; it does not have a Java plug-in. It works normally with a memory card.
.
4b) New version of IBM J9 PPRO11 JVM - v. 6.1.0
also works on WM 5.0 . Direct download link:
IBM_J9_PPRO11_JVM v. 6.1.0. Also, like the previous version, it can only be used to work with applets that are run separately from the browser; there is no Java plug-in. This is not an exe or cab distribution yet, but a copy of the contents of the IBM installation folder on the PDA. To install this version of the Java machine, see volta_john No. 353237:
How to install the IBM J9 PPRO11 JVM Java Virtual Machine .
FAQ for all Java virtual machines
can be downloaded here..
B. The order of running applets on the PDA Running browser applets The vast majority of applets are executed by the browser. To run such applets, you need either browsers that have Java Virtual Machine embedded, or Java plug-ins to Internet Explorer. The built-in Java Virtual Machine has a NetFront browser:
NetFront - replacing the standard browserThe Java plug-in for Internet Explorer is installed along with the Java Jeode Runtime JVM or CrEme machines.
Java plugin from CrEme must be specifically registered in Internet Explorer.To register, go to the Start Menu - Programs - CrE-Me and click on the Register Plugin shortcut, then the registration message should appear. If registration did not occur, see a more detailed exposition of this question here:
The order of launching applets performed by the browserIf the applet is executed by the browser on-line , open one of the specified browsers the desired web-page with the applet, and it should launch on its own.
If the applet is executed by the browser off-line (located in the form of a file on the PDA), then it is launched by taping on the html'nik usually attached to it. To tap on an html to launch such an applet in NetFront, which is usually not the default browser, you need to long tap on the html file, in the context menu of Resco Explorer, click on "Open with ...", and In the list of programs, select "NetFront".
If the applet executed by the browser on-line or off-line does not start , read the detailed presentation of this issue in this topic, post number 235920:
The order of launching applets performed by the browser Running applets running separately from the browser Applets that run separately from the browser are launched by the virtual Java machines presented above. Managers of applets are not created by Java virtual machines - when they are launched, we will not see a window with programs installed in it. Although in Java-machines CrEme JVM and Mysaifu JVM we can see a list of previously launched applets, which in essence is equivalent to the manager - when tapping on the corresponding line, applets are launched again.
If you are lucky, applets on your PDA are associated with a Java machine and will be launched with a simple tap on the ***. Jar file. If this does not happen, applets can be run:
but) using the user interface available in the Java virtual machines Mysaifu JVM and CrEme JVM;
b) using launch shortcuts. On the order of making labels, see this topic post number 218361:
About shortcuts to applets running separately from the browser ;
at) using the console. However, we will leave this method for professional programmers.
Returning to the method
"but" as to the most simple.
The most advanced interface has a 10-megabyte virtual Java machine Mysaifu JVM . When you run it, we see the top of the line in "Type" disturbing normal user the word "Class" (meaning the class to run the applet), Tapan safely on the arrow and see the string "JAR file". Choose "JAR file", which means that we will not "Name" enter anything in the box, but just tapnite the selected jar-file. Next Thapa on "Browse" (review), then you want us jar-file and run the selected applet tapom on "Execute". The next time, when we run this applet, we will not have to open an overview of the path to the required jar-file is remembered and displayed at the bottom of the window in the "Recent list". To remove from the list any name, go to / Program Files / Mysaifu JVM / recent / and delete the line no longer need. But if we need to run the applet through the entry point is not registered as a Main-class Manifest.mf (for advanced users), then in the line "Type" select "Class", and in the box "Name" prescribes the startup parameters for a specific form.
In the virtual Java machine CrEme JVM user interface is more simple. The possibility of launching with a tap on the jar file is missing; you must manually enter the parameters and the path to the applet in the launch string. However, parameters and path are entered there only once. The text we have entered is remembered, and the next time we launch the applet, we simply tap on the desired line in the drop-down list. For more information on running applets using the CrEme JVM virtual java machine, see message No. 213155:
The order of launching applets, performed separately from the browser, by the virtual Java-machine CrEme Virtual Java-machines Jeode JVM and IBM J9 PPRO10 (11) JVM They do not have a user interface, applets on them can only be launched using shortcuts or the console.
Although manufacturers of Java Virtual Machine for PDAs declare full execution of JSE, some applets that work normally on PCs may not run on PDAs due to the lack of certain classes in Java machines.
Jad files for running applets are not required.
Here, as well as in the next post after it, some games are posted on the JSE, i.e. games that are applets:
JSE Games.
Home page Java Technology :
http://java.sun.com/Post has been editedrendor - 27.01.08, 15:39