Dead Ink Vinyl

Linksys no longer bothers to print the voltage-amperage settings for its products on the products themselves. The Linksys Web site doesn’t help. The product guides online don’t cover all the versions of each product. For example, I own version 2 and a version 3 of the EZXS88W 8-port switch. The User Guide only states that the 88W takes 3.3V at 3.0A, but one of the two 88W’s I have takes 9V at 800mA.

For people like me who own a lot of Linksys products, this is a huge problem. I have five Linksys products and four different power adapters. So that other people don’t have to suffer the mix-and-match games I’ve endured, I’m sharing the configurations I know:

EZXS55W v.3

7.5V 700mA

EZXS88W v.2

3.3V 3.0A (3000mA, 3A)

EZXS88W v.3

9V 800mA

WRT54G v.3

12V 1000mA (1A, 1.0A)

I’ve taken to labeling all of my power adapters with the products to which they belong as I pull them out of the box (for new products) or determine the proper matching (for existing products).

Robert Lougher, maintainer of the JamVM virtual machine, posted a comment to an earlier entry of mine. Rob requested more information about the problem I experienced, so I poked around a little more and responded to him. I am posting the heart of that information here for the benefits of others.

The relevant details are:
– Jetty v5.1.2
– JamVM v1.2.4
– GNU Classpath 0.13

Running the command “java -jar start.jar” produces:

java.lang.NullPointerException
  at java.text.DecimalFormatSymbols.setCurrency (DecimalFormatSymbols.java:397)
  at java.text.DecimalFormatSymbols. (DecimalFormatSymbols.java:151)
  at java.text.NumberFormat.computeInstance (NumberFormat.java:327)
  at java.text.NumberFormat.getNumberInstance (NumberFormat.java:456)
  at java.text.NumberFormat.getInstance (NumberFormat.java:381)
  at java.text.SimpleDateFormat. (SimpleDateFormat.java:218)
  at java.text.SimpleDateFormat. (SimpleDateFormat.java:202)
  at org.mortbay.util.DateCache.setTimeZone (DateCache.java:126)
  at org.mortbay.util.DateCache. (DateCache.java:87)
  at org.mortbay.log.OutputStreamLogSink. (OutputStreamLogSink.java:59)
  at java.lang.reflect.Constructor.constructNative (Native Method)
  at java.lang.reflect.Constructor.newInstance (Constructor.java:265)
  at java.lang.Class.newInstance (Class.java:1146)
  at org.mortbay.log.LogImpl.defaultInit (LogImpl.java:190)
  at org.mortbay.log.LogImpl.message (LogImpl.java:415)
  at org.mortbay.log.LogImpl.message (LogImpl.java:399)
  at org.mortbay.log.LogImpl.info (LogImpl.java:332)
  at org.mortbay.util.FileResource. (FileResource.java:60)
  at org.mortbay.util.Resource.newResource (Resource.java:113)
  at org.mortbay.jetty.Server. (Server.java:78)
  at org.mortbay.jetty.Server.main (Server.java:432)
  at java.lang.reflect.Method.invokeNative (Native Method)
  at java.lang.reflect.Method.invoke (Method.java:355)
  at org.mortbay.start.Main.invokeMain (Main.java:151)
  at org.mortbay.start.Main.start (Main.java:480)
  at org.mortbay.start.Main.main (Main.java:94)
  at java.lang.reflect.Method.invokeNative (Native Method)
  at java.lang.reflect.Method.invoke (Method.java:355)
  at jamvm.java.lang.JarLauncher.main (JarLauncher.java:50)
1113542079746: INFO :Checking Resource aliases @ [main] org.mortbay.util.FileResource.(FileResource.java:60)
java.lang.reflect.InvocationTargetException
  at java.lang.reflect.Method.invokeNative (Native Method)
  at java.lang.reflect.Method.invoke (Method.java:355)
  at org.mortbay.start.Main.invokeMain (Main.java:151)
  at org.mortbay.start.Main.start (Main.java:480)
  at org.mortbay.start.Main.main (Main.java:94)
  at java.lang.reflect.Method.invokeNative (Native Method)
  at java.lang.reflect.Method.invoke (Method.java:355)
  at jamvm.java.lang.JarLauncher.main (JarLauncher.java:50)
Caused by: java.lang.ExceptionInInitializerError
  at org.apache.xerces.impl.dv.xs.SchemaDVFactoryImpl. (Unknown Source)
  at java.lang.reflect.Constructor.constructNative (Native Method)
  at java.lang.reflect.Constructor.newInstance (Constructor.java:265)
  at java.lang.Class.newInstance (Class.java:1146)
  at org.apache.xerces.util.ObjectFactory.newInstance (Unknown Source)
  at org.apache.xerces.impl.dv.SchemaDVFactory.getInstance (Unknown Source)
  at org.apache.xerces.impl.dv.SchemaDVFactory.getInstance (Unknown Source)
  at org.apache.xerces.impl.xs.SchemaGrammar$BuiltinSchemaGrammar. (Unknown Source)
  at org.apache.xerces.impl.xs.SchemaGrammar. (Unknown Source)
  at org.apache.xerces.impl.xs.XMLSchemaValidator. (Unknown Source)
  at org.apache.xerces.parsers.IntegratedParserConfiguration.configurePipeline (Unknown Source)
  at org.apache.xerces.parsers.DTDConfiguration.reset (Unknown Source)
  at org.apache.xerces.parsers.XML11Configuration.parse (Unknown Source)
  at org.apache.xerces.parsers.DTDConfiguration.parse (Unknown Source)
  at org.apache.xerces.parsers.XMLParser.parse (Unknown Source)
  at org.apache.xerces.parsers.AbstractSAXParser.parse (Unknown Source)
  at javax.xml.parsers.SAXParser.parse (SAXParser.java:273)
  at org.mortbay.xml.XmlParser.parse (XmlParser.java:165)
  at org.mortbay.xml.XmlParser.parse (XmlParser.java:181)
  at org.mortbay.xml.XmlConfiguration. (XmlConfiguration.java:122)
  at org.mortbay.jetty.Server. (Server.java:103)
  at org.mortbay.jetty.Server. (Server.java:78)
  at org.mortbay.jetty.Server.main (Server.java:432)
  at java.lang.reflect.Method.invokeNative (Native Method)
…7 more
Caused by: java.lang.RuntimeException: internal error
  at org.apache.xerces.impl.dv.xs.XSSimpleTypeDecl.applyFacets1 (Unknown Source)
  at org.apache.xerces.impl.dv.xs.SchemaDVFactoryImpl.createBuiltInTypes (Unknown Source)
  at org.apache.xerces.impl.dv.xs.SchemaDVFactoryImpl. (Unknown Source)
  at org.apache.xerces.impl.dv.xs.SchemaDVFactoryImpl. (Unknown Source)
…30 more

However, launching the application “manually” using the following command got me further (the server listens on 8080 and provides a listing of the known webapps):

java -cp /opt/jetty-5.1.2/lib/org.mortbay.jetty.jar:/opt/jetty-5.1.2/lib/javax.servlet.jar:/opt/jetty-5.1.2/ext/jasper-runtime.jar:/opt/jetty-5.1.2/ext/jasper-compiler.jar:/opt/jetty-5.1.2/ext/xercesImpl.jar:/opt/jetty-5.1.2/ext/commons-logging.jar org.mortbay.jetty.Server

So the problem might be Jetty’s, not JamVM’s.

In an earlier post I mentioned investigating the use of Sveasoft’s firmware for the Linksys WRT54G to place all of my computers on a local private network and use IP mapping (“DMZ”) to allow full Internet access to some of them. I found this post (login required?) on the Sveasoft forums that describes how to configure the WRT54G in this manner. Now I just need a WRT54G…