HOME Forums Gateways EZSrve New Java Discovery and Firmware Upgrade Tool

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
  • Anonymous
    Post count: 256

    Thanks to Lee Saferite, an operating system independent utility is now available to discover and upgrade your EZSrve. This Java utility executes the EZSrve discovery protocol to locate the IP of any EZSrve(s) in your network. Once located, one simply double-clicks on the IP found and a browser window is automatically open to the specific EZSrve.
    The tool also allows for automatic firmware upgrades. The firmware version of the selcted EZSrve is shown and the user can load any of the firmware versions from simplehomenet.com. The utility even takes you to the release notes after upgrading the EZSrve firmware!!

    The utility assumes that the Java runtime environmenet is loaded in your machine. This is a free download available for Windows, Linux and Mac from Sun Microsystems.

    Download the new utility at http://www.simplehomenet.com/Downloads/Discovery.jar

    Post count: 5

    If anyone has any problems or comments regarding the Java Discovery program, please post them here.

    Post count: 3


    I tried to run the discovery tool on the latest version of OS X and had the following error:

    john$ java -jar Discovery.jar
    Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version number in .class file
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:675)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:316)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:280)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:374)

    And here’s the output of my java version:

    john$ java -version
    java version "1.5.0_16"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b06-284)
    Java HotSpot(TM) Client VM (build 1.5.0_16-133, mixed mode, sharing)

    Any ideas? Does the jar require a newer version of the java vm?

    Post count: 5

    Ah, sorry. I neglected to mention that important fact.

    Yes, it needs Java 6 for some of the functionality.

    Sorry for not mentioning that before.

    Lee Saferite

    Mac Users: http://www.apple.com/java
    Windows/Linux/Solaris: http://java.com

    Post count: 5

    And for anyone who may be interested, you can have the discovery tool start, detect your EZServe and open a web page to it automatically by adding ‘–auto-start’ and a command line argument.

    This would allow you to have an icon on your desktop that would discover your device and open the webUI for it even if you don’t know the IP address.

    If anyone has problems getting this to work and needs help, just post here or ask me via IM.

    YIM: lee.saferite

    Post count: 256

    Version 2.0 was just posted. Thanks to AJ Cohen for the following enhancements:

    – Displays correct firmware version for 2.00 and above. Sorry, now 1.6 wont display correctly..
    – Goes to Simplehomenet.com/downloads and gets the latest firmware, DevClusters.xml and does the complete upgrade.

    Feedback is always appreciated!

    Post count: 2

    Please don’t use the version of the Discovery tool I provided yet. There is a functional inconsistency with upgrading the DevClusters.xml file which needs to be resolved. For now, manually loading DevClusters.xml and manually upgrading to 2.0, both on the website, will get you there.

    I hope to have this fixed shortly.

    Post count: 256

    Sorry about the issues with the revised utility. We pulled it out altogether and just posted rev. 1.1 based on the older version. It has the following changes:
    – Firmware version displays correctly for both version 1.x and 2.x EZSrve firmware
    – Upgrades of firmware are correctly done
    – The menu was expanded to enable rebooting and factory resetting the EZSrve (compatible only with 2.x versions)

    We are working to bring you file management so all auxiliary files (including DevClusters.xml) can be backed up and restored on the local machine.

    Again, we apologize for the inconvenience and confusion of the past couple of days.

Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.