Current Page: NeXtMidas Training Support & Maintenance Debugging
-   | Debugging Problem: Shell does not come up Check the Java version and make sure it is compatible with the version of NeXtMidas you have installed.
        $ $JAVAHOME/bin/java -version
        java version "1.5.0_06"
        Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
        Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)
    If you are on a 64-bit platform make sure it has the 64-bit version of Java installed. (The 32-bit version will NOT work properly on a 64-bit platform.)
        $ $JAVAHOME/bin/java -version
        java version "1.5.0_04"
        Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
        Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_04-b05, mixed mode)
    It is also possible that the NeXtMidas state file is corrupt. You can clear the state file by starting a new NeXtMidas session (starting a new session clears out any previous state file).
        $ nmstart
    Problem: java.lang.UnsatisfiedLinkError when starting shell If you get an error like this:
        Shell.loadLibrary err: java.lang.UnsatisfiedLinkError:
        /home/smith/nxm200/nxm/sys/lib/Native_lin.so: cannot
        open shared object file: No such file or directory.
You probably have one of the following problems: NeXtMidas was built using another system (usually via a NFS mount or a shared drive) and the resulting binaries are incompatible with your OS. You are using the wrong version of Java. Most likely using a 32-bit version of Java on a 64-bit system.