Using the EnvironmentCheck utility: To help diagnose classpath problems and also determine which version of Xalan-Java is being used, try running Xalan-Java's environment checking utility, checked in at xml-xalan/java/src/org/apache/xalan/xslt/EnvironmentCheck. Be sure to run EnvironmentCheck in the environment where you are experiencing the problem.

To determine what version of RADIUS is currently installed on your machine click the "Help" item on the menu bar and select "About." You will presented with a screen indicating the version of RADIUS you are using.

With an up to date perl installation one may query the local perl setup and all extensions via the command: perldoc perllocal For the Tk extension: version numbering has changed recently and determining the version of Perl/Tk that you are running now depends on what version you are running: Tk-b10 (and higher) has changed to $Tk::VERSION (rather than the older "$Tk:Version") to be consistent with other packages.

FrontPage forms only send email if the host server has FrontPage Server Extensions configured to recognize a mail server. You can direct your host to the FP Server Extensions Resource Kit for information on how to properly set up hosting for FrontPage users. America Online (AOL) uses unique proprietary dialer software. This article describes several items you should keep in mind if you are using FrontPage with America Online's Internet software.

To determine which version you're running, login to Active Trader Pro. Go to Help > About and you will see the version number. Top

You can use the Maven Help Plugin's describe goal. For example, to find out the version of the install plugin:

To find your version of Micrsoft Word, simply run Word and click "Help>About Microsoft Word." The version number will be displayed at the top of the dialog box- something like "Microsoft(r) Word 97 SR-2."

Or, at any point in an AMPL session, you can see the version message by looking at the contents of AMPL's version option, by typing The 8-digit number represents a date in the form yyyymmdd -- 16 May 2000 in this example. You can compare this date against the dates of the entries in the AMPL change logs and in the writeups of new AMPL features.

I would STRONGLY advise that you use the latest version of Java 1.4.2 for VASSAL development work. Java 1.5.0 has been released, but it adds additional methods and constructors to some classes that do not exist in 1.4.2 (e.g. Window.setAlwaysOnTop()). If you unwittingly use one of these methods, anybody trying to run your module using Java 1.4.2 will get a NoSuchMethod exception. Best to develop using 1.4.

Click "Menu" button; select "Show Preferences"; select the "About" tab. The version and build number is located the top of the dialog.

The ASE2000 software version can be found by starting the ASE2000 program, select Help and About ASE2000. This will display the software version number. You will need this information when contacting ASE for technical support. In general, no. Due to copyright restrictions ASE is prohibited from distributing protocol specification documentation. The best option is to contact the RTU or IED manufacturer and request documentation for the specific protocol.

The client and server software need Java 1.4.2 (or higher). The servlets require the Java Servlet library which is available from Java.com in the Java Enterprise Edition (J2EE), or via downloading a servlet engine such as Apache Tomcat.

We currently recommend JDK 1.4.2_05. This is the version we have tested most extensively, including running multiple Regional Contests. Other versions may work, but we have not done extensive testing on them. (Note that earlier versions of Java contain known bugs which can adversely affect PC2 operations.)

Sometimes you may need this information to implement a specific feature or to implement a workaround to a bug that has been fixed in later releases. Technical Note TN2110 discusses how to best do this, along with a comprehensive list of version strings for every Java release on every version of Mac OS X.

The Xalan-Java version 1 compatibility API has been deprecated and removed, so you must use the Xalan-Java version 2 API. We strongly encourage you to use the Java API for XML Processing (JAXP) 1.3. For more information, see the FAQ on TrAX and JAXP. The JDK 1.3 automatically places everything in the lib/ext directory in front of everything you place on the classpath.

will do the trick, provided you set your CLASSPATH correctly. If you are using j2sdk1.4.1_01, it will be always right as long as you can use java. In j2sdk1.4.1_01, xml stuff is bundled inside rt.jar already. My xerces/crimson parser does not validate for me? The following code does not work, why? org.apache.xerces.parsers.SAXParser parser = new org.apache.xerces.parsers.SAXParser(); // MyDefaultHandler extends DefaultHandler parser.setContentHandleler(new MyDefaultHandler()); parser.