Downloading/Installing the Ewe Virtual Machine
and Development Environment


December 20th  2005, Michael L Brereton
http://www.ewesoft.com/

Ewe Virtual Machines – Version 1.49. 1

For Windows Desktop.. 1

For PocketPC... 1

For Microsoft SmartPhone. 2

For Casio BE300.. 3

For HandHeld PC Pro.. 3

For Linux Desktop and Sharp Zaurus. 3

For Java Runtime Environments. 3

For Other Windows CE Platforms. 3

For Emulated Devices (Developers only). 4

Running Ewe Programs. 4

Under Windows. 4

Under Java. 4

Demo Ewe Program.. 4

Ewe Software Development Kit (SDK) 4

Additional Developer Files. 5

Ewe Source Code. 5

 

 

Ewe Virtual Machines – Version 1.49

 

For Windows Desktop

Ewe149-Installer-Win32.zip – this file contains a single Windows executable file that will install the Windows desktop version of the Ewe VM on a PC.

Developers: You can manually install the VM if you wish by downloading the file: Ewe149-VM-Win32.zip and then copying all the files it contains into a directory of your choice on the target PC. When you have completed installation, run the file ewe.exe to run the VM – which will cause it to register itself correctly on the PC.

For PocketPC

Ewe149-CAB-PocketPC2003.zip (Low Resolution version) – this file contains a single CAB file that can be used to install the Ewe VM on a PocketPC 2003 device. Most devices purchased in or after 2004 will be a PocketPC 2003 device. You can verify the OS on your device by going to Start->Settings->System(tab)->About. It will report “Windows Mobile 2003” (possibly also “Second Edition”). The Version will also be 4.2x.xxx.

If you have a PocketPC device that features a VGA 640x480 high-resolution display then you can also use this version: Ewe149-CAB-PocketPC2003-HighResolution.zip. This version makes full use of the 640x480 display screen instead of running in 320x240 emulation mode.

If you have a PocketPC 2002 or one of the first generation PocketPC devices, then use this file instead: Ewe149-CAB-PocketPC.zip. This file, however, contains three different CAB files, one for each of the processor types supported by the original PocketPC – ARM (for StrongARM or Xscale processors), MIPS and SH3. All PocketPC 2002 devices will use the ARM CAB file. First generation PocketPC devices can be any of the three processors. Again check the About information to determine which CAB file to use.

Installing Using CAB Files

This is the recommended way of installing the Ewe VM. The CAB file installs the application and will also register information so that the Remove Programs utility will be able to uninstall the VM if necessary.

To install the application, use ActiveSync to connect to the PocketPC and copy the appropriate CAB file to any location on the PocketPC (including a Storage Card – if so desired). Then, disconnect from ActiveSync and run the File Explorer on the PocketPC itself. Locate the CAB file on the PocketPC file system and then simply select the CAB file with the pen. The VM will then be automatically installed on the system and the CAB file itself will be removed from the PocketPC.

After installation go to Start->Programs->Ewe and click the ewe icon to run the VM. You can also select the Solitaire sample or RegistryView sample as well.

To uninstall after a CAB installation, you can use the Remove Programs option in the Settings screen.

Manual Installation – Recommended for Developers Only

The Ewe VM can be manually installed on a PocketPC very simply as well. Download either Ewe149-VM-PocketPC2003.zip or Ewe149-VM-PocketPC2003-HighResolution.zip (for PocketPC 2003 devices) or Ewe149-VM-PocketPC.zip (for older PocketPC devices). For PocketPC 2003 devices, simply copy all the files in the ZIP file into any directory on the PocketPC. For older PocketPC devices, copy the files from the directory (ARM, MIPS or SH3) as appropriate for the target device into any directory on the PocketPC.

After manually copying the files across to the PocketPC, you must run ewe.exe to register the VM correctly in the PocketPC.

To uninstall after a manual installation, you simply delete the files that you copied across in the installation process.

For Microsoft SmartPhone

Ewe149-CAB-SmartPhone.zip – This file contains two CAB files. One for SmartPhone 2003 and one for SmartPhone 2002. You can determine which version of SmartPhone you have by going to Settings->About. In addition to showing the SmartPhone version, the operating system version will be 4.2x.xxx for SmartPhone 2003.

Installing Using CAB Files

This is the recommended way of installing the Ewe VM. The CAB file installs the application and will also register information so that the Remove Programs utility will be able to uninstall the VM if necessary.

For SmartPhone 2003, use ActiveSync to connect to the SmartPhone and copy the appropriate CAB file to Storage\windows\Start Menu\Accessories. Then disconnect from ActiveSync and go to Start->Accessories. The CAB file should be displayed as a menu item. Select the CAB file and the VM will then be installed – the original CAB file will be automatically removed from the SmartPhone at the end of the installation. The installation will create a new Ewe folder that will appear in the Start menu – usually just after the Accessories folder. Within that folder you will find the Ewe VM itself and the Solitaire application.

For SmartPhone 2002, use ActiveSync to connect to the SmartPhone and copy the appropriate CAB file to Windows\Start Menu\Accessories. Then disconnect from ActiveSync and go to Start->Accessories. The CAB file should be displayed as a menu item. Select the CAB file and the VM will then be installed – the original CAB file will be automatically removed from the SmartPhone at the end of the installation. The installation will create a new Ewe folder that will appear in the Start menu – usually just after the Accessories folder. Within that folder you will find the Ewe VM itself and the Solitaire application.

Manual Installation – Recommended for Developers Only

Ewe149-VM-SmartPhone.zip – this contains the individual files for the Ewe VM for the two SmartPhone versions. To install the VM manually simply use ActiveSync to create a Ewe directory on the Start Menu and copy the files across. Then you must run ewe.exe on the SmartPhone to register the VM correctly on the device.

To uninstall after a manual installation, you simply delete the files that you copied across in the installation process.

For Casio BE300

 

Ewe149-Installer-BE300.zip – this contains two installers for installing the VM on a Casio BE300 device.

 

In the zip file there is a sub-directory called PCConnect – this contains the files necessary to install the VM using the standard PCConnect installer.

 

For BE300 users who use ActiveSync, there is the Ewe-BE300.exe installer which can install the VM over the ActiveSync connection.

 

For manual installation you can download Ewe149-VM-BE300.zip – this contains the individual VM files that can be placed in any desired location on the BE300. Then you must run ewe.exe on the BE300 to register the VM correctly on the device.

For HandHeld PC Pro

 

Ewe149-Installer-HPC.zip – this contains an installer for installing the VM on a HandHeld PC Pro device.

For manual installation you can download Ewe149-VM-HPC.zip – this contains the individual VM files that can be placed in any desired location on the HandHeld PC. Then you must run ewe.exe on the HandHeld PC to register the VM correctly on the device.

For Linux Desktop and Sharp Zaurus

 

Ewe149-Linux-x86.zip – this contains two different versions of the standard Ewe VM. The directory Gtk2 contains a build for Linux systems with the GTK 2 library installed and the directory Gtk12 contains a build for systems with the older GTK 12 library installed. The only difference between versions is that the GTK 2 version provides support for scrolling via the mouse wheel. The directory CommandLine contains a build (called ewecl) that does not provide any GUI support and should work on any Linux system, or in a run-time environment that does not provide a GUI.

 

Ewe149-Linux-Zaurus.zip – this contains the installer package ewe_1.49_arm.ipk which is the standard installation package for the Zaurus. The Zaurus Add/Remove Software utility can be used to install and uninstall the VM using this package.

 

The zip file also contains a subdirectory called vm which contains the files ewe.ewe (the VM library), ewe the normal Zaurus Ewe VM executable and ewecl a command-line GUI independent build of the VM for the Zaurus. Both ewe and ewecl require ewe.ewe to be located in the same directory for them to work. These files can be manually installed/removed if necessary.

 

For Java Runtime Environments

Ewe149-JavaVM.zip contains three files. One is ewe.jar, which contains the ewe library for Java 1.2 or higher environments. This can be used on any system with a Java virtual machine installed. This can be used with the included java_ewe.dll and ewex_registry.dll, (for Win32 desktop systems) which allows Win32 Java 1.2 VMs to access the serial port, the system Registry and to play .wav files.

Developers, please note that these files are already included in the Ewe SDK provided below.

For Other Windows CE Platforms

 

Ewe149-VM-CENet.zip – this contains the individual files for the Ewe VM for the ARM/Xscale processors and for the x86 Emulator for the CE .net OS. You can install these manually by copying the files across to a directory on the destination device and then executing ewe.exe to register the VM correctly on the device. The emulator does not appear to support automatically installing applications via a CAB file as does PocketPC, nor does it appear to have a “Remove Programs” feature under the Control Panel. However I have provided the CAB versions of the Ewe VM for CE .net here: Ewe149-CAB-CENet.zip but I have not been able to test it out.

 

Ewe149-VM-RLC_ARM.zip – this contains the individual files for the Ewe VM for the RLC_ARM platform.

For Emulated Devices (Developers only)

There are also VMs for Emulated devices (those provided by embedded Visual C++). These are available as CAB files in Ewe149-Emulator-CAB.zip or as individual files VM files in Ewe149-Emulator-VM.zip.

Note that the VM is available for the following Emulated devices only:

PocketPC
PocketPC 2003
SmartPhone 2002
SmartPhone 2003
CE. Net Standard SDK

Use the Remote File Viewer tool in eVisual C++ to copy the files across to the Emulated device for installation.

Running Ewe Programs

Under Windows

To run .ewe files (the distributable version of a Ewe program) on a Windows/WindowsCE system, you only need to double-click (single-click on PocketPC) the .ewe file. This will cause the program to run on the Ewe virtual machine. To run on the command line you simply enter:

ewe <ewefilename.ewe>

e.g. ewe "C:\Program Files\Ewe\Jigsaw.ewe"

Under Java

To use a Java VM to run Ewe programs you must have downloaded the Ewe149-JavaVM zip file. Extract from that file the ewe.jar and the two DLLs. Then you must run the command line:

java -cp ewe.jar Ewe <ewefilename.ewe>

Demo Ewe Program

You can download the Ewe Jigsaw game here (not for use on SmartPhone). Use this with any image to create your own randomised, and always different, Jigsaw puzzles.

The files Jigsaw.ewe and Jigsaw.jar are included in the file. Jigsaw.jar will run on any Java 1.2 VM without the Ewe VM Jar file being present (it is fully self contained). Jigsaw.ewe will require a Ewe VM to run.

Ewe Software Development Kit (SDK)

There are four separate files to download for the development environment.

1. The Ewe Class Library/Java VM and Jewel Program Builder.

This is a file called Ewe149-Developer-SDK.zip which contains:

1.      The class library needed for your compiler to compile Ewe applications and for a Java VM to run Ewe programs. This is in a file called Ewe.jar, which is within the classes directory of the SDK. Note that this is the same file provided in Ewe-JavaVM.zip mentioned above.

2.      The Solitaire sample application, which is included as a demo and a means of testing your installation, and the HelloWorld sample.

3.      The Jewel program builder, which is used to package your application into .ewe files and also produce other targets.

Unzip this file into a development directory of your choice (e.g. c:\ewe) maintaining the directory structure as in the zip file.

Please read the Ewe Application Development Guide described below before using the Ewe SDK.

2. The Ewe API.

This is a file called Ewe149-Developer-API.zip and it is essential for all developers. It contains the JavaDoc generated API for Ewe 1.49.


3. The Ewe Applicaton Development Guide.

This is a file called Ewe149-Developer-Guide.zip and it is also essential for all developers. Unzip this file into a docs subdirectory in your Ewe development directory. If you are a new user, open index.htm in the EweDevelopment directory and read the first two chapters. These chapters tell you how to set up the programming environment and how to use the Jewel program maker to create distributable ewe programs.

An up-to-date version of the Developer Guide can be accessed directly from the Ewesoft.com website here: http://www.ewesoft.com/docs/EweDevelopment/index.htm

4. Sample Ewe Java Code.

This is a file called Ewe149-Developer-Samples.zip and it is very useful for all developers. Unzip this file into the classes subdirectory in your Ewe development directory. This will be frequently modified as it is brought up to date to demonstrate the new features of version 1.49.

Additional Developer Files

Deprecated Packages. This includes packages removed from the 1.49 VM. Currently this is only the ewe.datastore Package. You can download this at Ewe-Deprecated.zip.

Ewe Installer SDK.  This provides the SDK for creating your own executable installers for installing your applications and the Ewe VM on a WindowsCE device over ActiveSync or onto a Windows Desktop: Ewe149-Developer-InstallerSDK.zip. You will also need the individual zip files that contain the Ewe VMs. These must be renamed once you have downloaded them before including them in your Installer project. They are:

Ewe149-VM-PocketPC.zip or Ewe149-VM-PocketPC2003.zip => Rename to: Ewe-PocketPC.zip
Ewe149-VM-Win32.zip => Rename to Ewe-Win32.zip
Ewe149-VM-HPC.zip => Rename to Ewe-HPC.zip
Ewe149-VM-BE300.zip => Rename to Ewe-BE300.zip

Ewe Source Code

There are three source code packages:

Ewe149-Source-Win32.zip – contains the source code for the Windows/WindowsCE VM.
Ewe149-Source-Linux.zip – contains the source code for all Linux builds of the VM.
Ewe149-Source-Java.zip – contains the source code for the Java version of the VM.

The Win32 and Linux build zips contain an HTML document that explains how to build the VM. The Java version simply requires any Java IDE or compiler to build.