Installing gvSIG Mobile

Right now I just installed gvSIG Mobile on a Mobile Mapper 100, considering that it was my first time and that the rest of the year I think to take advantage of the experience, it is convenient to write as I did, lest others give them something of can (of the glandes).

1 What version

The process is similar for any installation of gvSIG Mobile on a Windows Mobile PDA 5 or higher. However for reference, I am using:

Windows Mobile 6.5 Professional, with a CE OS 5.2.21895

This is verified in Start / Settings / Systen / About

In the case of gvSIG, I am installing an 0.3.0 Build 0275 version and because I want to bet seriously on Java, I will mount it on this virtual machine (JVM) although it is also possible on PhoneME.

2 Download the programs

To download gvSIG I've done it in this link:

With this we will get a file called

Over time there may be a newer version, so be sure to link to this:

I have chosen, aware that this version does not have pre requisite included (the virtual machine), a pity because before they did. But they are consequences that we already expected after the policy changes that happened to Java after Oracle will buy SUN.

For this, additionally you have to download the virtual machine known as J9. Some links in the lists are broken, including that appears in the gvSIG Mobile manual, so I will suggest this to download J9:

Download a tablet called, you have to be careful when you unzip it, you must choose «Extract here» and not «Extract in J9 \», because this will create another folder called J9 that can later give us a can.

Finally we must hope that what we decompress is in the form "J9 \ PROJ11 \ bin ..."

3 Upload the programs to the Mobile Mapper

The version of Windows Mobile that brings the Mobile Mapper 100 (and in general for any PDA) usually gives a couple of problems to install the ActiveSync, almost always because the executable is built on Flash Player and sometimes, especially with Windows 7 not recognizes the existing update or does not allow installing unsupported applications. But that is resolved by downloading directly from the Microsoft page, in the download option for mobile devices.

The important thing is that we can see from the PC the connected equipment, otherwise we would have to pass it through an SD card.

There are only two things to upload:

-The file, which we put inside one of the folders, in this case I am doing it in the so-called "Application Data". I recommend you do it there, so you can follow this instruction step by step.

-The file called J9, which we place directly in the root. When I refer to the root, it means that the J9 folder should be at the same level as other folders such as Application Data, ConnMgr, Windows, etc.

This causes the Java virtual machine to be ready to run.

4 Install gvSIG

To install gvSIG, you have to go to the folder where we upload the file.

This is done with Start / Explorer, and then in this browser emulator we look for the "Application Data" folder, and there we should see the file. With one click, the program starts the installation process; If there is an earlier version, it will notify us that it will be replaced. You must choose to install on the device (My device) and not on the external card (Storage Card).

5 Eejutar gvSIG

To execute it, select "Start" and the gvSIG Mobile icon should already be in the panel that shows the applications.

Click on the icon and as a result the splash should be lifted for a few seconds and then the program interface.

6 Common problems

Install gvsig mobileFirst, in case of not executing the program (the 5 step), or leaving a Windows Mobile error message, the important thing is to know what the called file is saying G_mobile_launch_log.txt, which is in the gvSIGMobile folder. In the best case, you should leave a message like this:

GvSIG mobile launch log file:
Assumed gvSIG main folder: \ gvSIGMobile:
Checking if J9 is in root ...
Truncating, aux.npos = -1
Truncating, first = 3
Truncating, Resp = \ J9
J9 path truncated: \ J9
Writing start.opt file with good paths ...
Composing launch parameters ...
J9 params = «-Xoptionsfile = \ gvSIGMobile \ start.opt» p = \ gvSIGMobile m = J9
J9 path: \ J9 \ PPRO11 \ bin \ j9w.exe
J9 params: «-Xoptionsfile = \ gvSIGMobile \ start.opt» p = \ gvSIGMobile m = J9
GvSIG mobile was launched successfully.

Based on the message, you can see where the problem is. This is an example, which is usually because we do not place the folder J9, see that the system looks for the possibility of finding it outside the root directory, as well as if it is installed on SD cards or if PhoneME is installed:

GvSIG mobile launch log file:
Assumed gvSIG main folder: \ gvSIGMobile:
Checking if J9 is in root ...
Finding out sd card path ...
Searhing for '\ J9 \ PPRO11 \ bin \ j9w.exe' in roots ...
Found SD card path: \ Storage Disk
Found SD card path: \
File not found: '\ J9 \ PPRO11 \ bin \ j9w.exe' in any of the 2 SD cards.
Unable to find sd card, J9 not found!
Checking if PhoneME is in root ...
Finding out sd card path ...
Searhing for '\ phoneme \ personal \ bin \ cvm.exe' in roots ...
Found SD card path: \ Storage Disk
Found SD card path: \
File not found: '\ phoneme \ personal \ bin \ cvm.exe' in any of the 2 SD cards.
Unable to find sd card, PhoneME not found!
Unable to start gvSIG Mobile. Possibly in the JVM found.

Do not forget, the GvSIG mailing lists, because usually someone has already happened and the answer is there. If not, with a simple mail to the list will have response from the community quite effectively.

If not ... I'm all ears ...

Leave an answer

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.