Version 1.0 requires JDK 1.4 or higher. The version in CVS HEAD and future releases will require JDK 1.5 or higher. However, some users have contributed patches to make later versions compatible with JDK 1.4. Please check the contributions/ directory for any such patches. Note that any code in this directory is untested and unsupported, so please use at your own risk and do not file bugs based on that code.

Author: John Zukowski (http://www.jguru.com/guru/viewbio.jsp?EID=7) You can find this question answered in the Microsoft Knowledge Base at http://support.microsoft.com/support/kb/articles/q214/8/28.asp. Hint, it isn't JDK 1.2.

There is a known limitation with the 1.3.1 JDK in relation to it calculating the correct time for entering and exiting DST transitions. This behavior has been present since 1.3.1 FCS. It has been corrected in 1.4 and in later JDK versions when the time zone framework was re-coded. The limitation arises from complexities in determining whether a given timestamp is in standard or daylight time savings rules.

CA supports JDK 1.3.1 and higher. It understands JDK 1.5 syntax such as new keywords and language changes.

ShapeLogic is compiled with JDK version 1.6. There are parts of it that is using the JSR 223 scripting framework, introduced in 1.6. It might be possible to compiled it with JDK 1.5.

The support for object-oriented programming was completely overhauled with the introduction of PHP 5 in July 2004. The changes included both semantic changes and syntaxtical changes to the PHP language. then $object_a and $object_b will both reference the same element. In particular, you will see that $object_b->getValue() returns the string just stored in $object_a (since they are the same object). With PHP 4 you would have gotten two different objects, which is generally not what you want.

lt;plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <configuration> <verbose>true</verbose> <fork>true</fork> <executable><!-- path-to-javac --></executable> <compilerVersion>1.3</compilerVersion> </configuration> </plugin>

Reducing the timeout interval often reduces execution time significantly. Not performing memory leak testing also reduces execution time. Not performing null value tests also helps reduce execution time.

PD4ML is intended to be used with JDK1.4 and above, although it works with minor restrictions under JDK1.3.1 as well.

The current version is designed for Sun JDK 1.3, but will also run on JDK 1.4, 1.5 and 1.6. Both Sun and IBM JDKs are supported. LICENSING INFORMATION

JDK 1.4 is the minimum version required. MapViewer will not work with JDK 1.3 or any earlier version. Also note that if you are using a standalone OC4J instance, you must start it using the Java executable that is under your JDK installation's top bin directory. The java executable under the jre/bin directory will NOT work with OC4J.

The stack is compiled with JDK 1.4.1. The packages uk.co.westhawk.nothread.oscar and uk.co.westhawk.nothread.trap have to be compliant with JDK 1.2.X, since that is what Oracle™ 9i supports. However, this can be done by setting the javac target option to 1.2.

JDK version 1.3.1 is limited in its capacity to represent DST time zone rules. It can only represent one set of rules. Therefore, the latest update (1.3.1_20) will use the newest DST rules on any date regardless of the year used. For example, consider a Date object represented by the "America/New_York" time zone. DST will be entered on the first Sunday on or after March 8th. DST will be exited on the first Sunday on or after Nov 1st. JDK version 1.3.

I am using Process.waitFor() to force my application written for the Java platform to wait until the native process has finished...

MPP requires Sendmail version 12 in order to take advantage of enhancements in the LibMilter interface. Back To Top sendmail[655]: [ID 801593 mail.error] j1SK7r9Q000655: Milter (mppd): local socket name /var/run/mppd.sock unsafe sendmail[655]: [ID 801593 mail.info] j1SK7r9Q000655: Milter: initialization failed, temp failing commands This means that MPP is not running. Check the MPP logs in /var/log/MPP/[yyyymmdd].log and you will most likely find that your license, i.e., key.

Taskline works with all the current Outlook versions - 97, 98, 2000, 2002, 2003 and 2007. However, there are some minor functionality and interface limitations with Outlook 97 and 98. Please note that Taskline will not run on an NT4/Outlook 98 combination.

To run, GUIdancer requires Java 1.5 or later. This Java version is included in the Windows download of the program. The GUIdancer server requires Java 1.3 or later. In effect, applications under test can be written with Java 1.3.

You don't need Powerpoint software if you are only running EasiSlides in Database Mode. If you wish to run Powerpoint presentations, Powerpoint 2000 is the minimum version required. Yes, for each screen. However, animated Gifs can't run indefinitely or else EasiSlides won't be able to control the slide movements. Also, because of the way Powerpoint operates, EasiSlides can't handle Powerpoint custom shows.

SCE comes with SQL Express in-the-box, for free. You do not need to buy other versions of SQL to run SCE. SCE does support all other versions of SQL 2005, such as Express, Standard, Workgroup, and Enterprise. No, SCE does not support SQL in a clustered topology. For high-availability configurations, you need to upgrade to Ops Mgr 2007.

While to date LyteMeister has been free of errors, if a clinically significant error is detected we want to make sure we can notify you promptly to ensure you will always have the best and most up-to-date version of LyteMeister. Yes and no. Registration of ICDMeister, CPT®Meister, and NCDMeister include free updates for all editions based on the current year's ICD-9-CM or CPT® codes.

JMF 2.1.1 runs on Java Compatible platforms running JDK 1.1 or greater. For complete Y2K compliance, you should use JDK 1.1.6 or greater.

In order for the Java communications API to find ports the file javax.comm.properties must be in the correct place. The preferred location is in <jdk>/lib. See the installation instructions for alternate locations and further information.

Java 5 (or 1.5) is the officially supported version. Not all components require it (some will work with 1.4). Java 6 will also probably work.

To take full advantage of DrJava's features, you will need to have either the JDK 5.0 or the J2SE v 1.4.2 SDK installed on your system. We highly recommend version 5.0, as it provides a number of language features, additional APIs, and GUI improvements. If you are using version 1.4.0 or 1.4.1, you may see some buggy behavior, some of which is documented below.

Not yet. When mono adds support for the Windows.Forms extensions made by .NET 2.0 then I will release a mono version, but this is not likely to be until mid 2007. Update: Since it is now mid 2007, I guess I should add to this. mono does now support most of the stuff I need, and I do indeed have a mono version of obmm working. There's still a couple of things missing which I want fixed before I release, but this should be done by the next couple of mono releases.

ADAT version 3.04 or higher is necessary in order to have an ADAT operate in conjunction with a BRC. If the BRC has version 2.00 or higher, you would need ADAT version 4.00 or higher. 4.03 is the current version of ADAT software. Versions 3.06 or higher may be updated by software alone. Versions below 3.04 or lower require additional hardware and must be updated at a service center or at the factory. (back to top)

The Application version of EIOBoard does not require much bandwidth at all. You can think of the Application as a fancy web browser. Also, while the application is minimized it is using even less bandwidth because it is not refreshing everyone's statuses while minimized.

of January 26th, the Jini binaries work with the JDK 1.2 FCS release. If you downloaded the Jini binaries prior to January 26th, your Jini binaries will NOT work with JDK 1.2 FCS, but with JDK1.2b4. Jini will not work with any JDK release prior to JDK 1.2. It is built on top of many features, such as new features of RMI, that did not exist in the JDK prior to JDK 1.2.

I apologize but we don't have this kind of software. If we'll not set it up this way, the software could crash and we can't allow that to happen...