Purchase an update,
either one at a time
or an annual subscription

1. Back up your c:\aJile folder, especially if it has any of your own your jembuilder projects (.ajp) or configurations, since those could be overwritten by this update. It's best to keep any ajp files with the code for them, not in the \ajile folder, then you don't have to bother backing up this folder.
2. Do one of the following:
1. uninstall your current ajile folder, using Control Panel -> Add or Remove Programs. Then you will probably need to delete the aJile folder manually. On XP I usually also have to reboot.
2. Rename your current installation root folder from c:\aJile to something meaningful like c:\aJile4303 for release 4.3.03. This is what I usually do so that any of the old installation files are still easily accessible for comparison.
3. Get the files,
• When you open the .zip file (I use WinZip), you will see an aJile install and a Systronix supplement file inside.
• Extract the files to a temp folder or execute them from within  your ZIP utility - it's up to you
  
4. Run the aJile installer - this installs the new runtime from aJile Systems. Let it use c:\aJile (the default) since some other things in the aJile tools are hard-coded for that folder and won't work if you use something else.
5. I get a popup about warnings during the installation but so far I cannot find the installation log file which I am supposed to check for details.
6. Copy ajileant.jar from C:\aJile\Ant to your Ant {ANT_HOME}\lib folder. This provides classes such as com.ajile.tools.ant.JemBuilderTask which Ant will use later to compile examples. (Note to self - is this still needed in 4.4.02??)
7. Note that the installer creates a system environment variable AJILE_CLDC which points at the runtime root, such as
   AJILE_CLDC=C:\aJile\Runtime_cldc11
   So this is a good choice to use in Ant files since this variable can easily be set to some other path, unlike AJILE_HOME. So I'm going to convert my build.xml files to use AJILE_CLDC
8. Run SystronixSupplement installer which overlays the Systronix configurations and examples over the aJile installation.
9. Run Ant on the build.xml file in the folder C:\aJile\Systronix to create the Rts.jar file, examples, JemBuilder properties, and more
   
10. C:\aJile\Examples\CLDC\doc contains example javadocs. Not all examples apply to JStamp and JStik. Start with HelloWorld and SerialHello
11. JemBuilder project files are in C:\aJile\Examples\CLDC\Projects
12. Source code is in C:\aJile\Examples\CLDC\src\com\ajile\examples such as C:\aJile\Examples\CLDC\src\com\ajile\examples\io\charadeio\HelloWorld.java and C:\aJile\Examples\CLDC\src\com\ajile\examples\serial\serialhello\SerialHello.java
    The binary load files are in C:\aJile\Examples\CLDC\builds and the
    Java source code is in C:\aJile\Examples\CLDC\src
13. To invoke Charade, use the shortcut in the C:\aJile\Systronix folder, which you can copy to your desktop or task bar. This starts Charade in the C:\aJile\Systronix folder and uses the Systronix configurations, and Systronix versions of Charade.wcf and Charade.cfg. This includes things like a Charade "verify" button, and a Charade Device menu listing of all Systronix platforms. If you right-click on the shortcut and select "proprties" you should see a dialog box like this one.

1. You get CLDC 1.1 runtime code with the aJile install, but no source code or docs. So get the Sun CLDC 1.1 Reference Implementation for all that.
2. You can use this CLDC JAR to create the JemBuilder Runtime definition, rather than the JAR included with the aJile runtime. In theory they are the same... but the size is different... so there is some hopefully minor difference. Use the aJile CLDC runtime JAR since that's what aJile uses in testing.
3. Extract this into some convenient location. I put all my Java tools under a "javasoft" folder to help keep them in one location. You will access this folder later in JemBuilder setup.
4. Create an ME classes JAR file so that Eclipse can use it later:
1. Browse to your ME installation, the bin\common\api\classes folder, which in my case is:
   D:\javasoft\cldc11\j2me_cldc\bin\common\api\classes
   and open a command line window there.
2. Type this JAR command:
   jar cvf ..\classes.jar *.*
   which will JAR up all the \classes subfolders but not the \classes folder itself. Now you should have this file:
   D:\javasoft\cldc11\j2me_cldc\bin\common\api\classes.jar
   whih contains all the Java ME base classes (e.g., String)
5. Add a new System variable for all users: CLDC_HOME, with - in my case - a value of D:\javasoft\cldc11\j2me_cldc which is the root folder of my Java ME CLDC installation.
6. Test this with an echo from a simple Ant target. I make this part of my Ant "init" target which also cleans output, creates output folders, etc. It's a line like this:
   <echo message="CLDC_HOME is set to = ${env.CLDC_HOME}"/>
   Now you can see at the start of each Ant run if your paths are correct. Also you can now refer to the CLDC class.jar within Ant like this:
   ${env.CLDC_HOME}/bin/common/api/classes.jar"

• aJile expects its releases to be in C:\ajile, if you place the install elsewhere some paths will be broken (mainly in the examples)
• there may be some aJile JNIB drivers such as USB which don't have hardware support on Systronix hardware. You are on your own with such drivers since we can't support them yet.
• We don't know about bootloader documentation yet, but we are asking
• The ant jembuilder task is in the /ant subfolder
• GC: You should only be using the mark & sweep algorithm. The generational and train algorithms are not fully implemented.