|
|
 next
|
  Subject: Java Config and Win 2003 Server 64-bit
Author: Chris Welton
Date: 12 Aug 2005 04:52 PM
|
>Steven,
>the problem is probably that
>you are trying to convince
>Stylus Studio to use a 64bit
>JVM; Stylus Studio is a 32bit
>application; Windows 64bit
>allows 32bit apps to run, but
>probably not in mixed mode (a
>32bit app using 64bit
>libraries).
>
>Can you try installing a 32bit
>JRE and point Stylus Studio to
>it? Even without changing
>registries, you can force
>Stylus Studio to point to the
>32bit jvm.dll library. Unless
>you plan to develop/compile
>Java code with Stylus Studio,
>you don't need to worry about
>JDK.
>
>Thanks,
>Minollo
While you are correct in the 32 - 64 bit incompatability, there is a common misconception here that I would like to address. It's the 64 bit JVM trying to use Stylus code as native methods that causes the problem, not the other way around. When javaw needs to run code faster and cleaner than the JVM can itself, a developer will link the java classes to a dll so that the JVM can load the functions in the dll and have them run at optimal speed. The 64 bit JVM can not correctly break 32 bit dll's into function pointers, because it is looking for 64 bit functions (and, hence, 64 bit function pointers). In other words, Stylus Studio is not trying to use a 64 bit JVM, a 64 bit JVM is trying to use 32 bit Stylus libraries.
Chris
|
|
|
|
top