Yes, the Ptolemy II 1.0.1 installer has problems installing under versions of Java that were not known when the installer was created. I created dummy files for some versions of Java, probably up through Java 1.3.1_02, so there would be a problem with Java 1.3.1_07.
This is because of a serioius limitation in the version of Installshield that was used to create the installer. We no longer use Installshield, we are using Installanywhere, and the most recent HyVisual installer includes a dialog that allows the user to select a JVM to use. The error you saw might have been the installer failing to find a suitable JVM. See http://ptolemy.eecs.berkeley.edu/ptolemyII/ptII1.0/installshield.htm#bugs for a list of the InstallAnywhere limitations. The primary workaround is to install Ptolemy II 2.0. Another workaround is to install Ptolemy II 1.0 from source. Alisson Brito wrote the following about how to tell the installed version of Ptolemy II 1.0.1 to use a different version of the JVM: > I've unmounted the installer file with the > command: > > ptolemyII1.0.1.exe :is extract > > After that I've created a file called > sun_win32_140.jvm > Then I 've made the product,xml to know that my > .jvm file exist and that > I have a jdk1.4.0 installed in a determinated path. > And finally I run: > > java run (that execute run.class) Ptolemy II 2.0.2 should read in Ptolemy II 1.0.1 models, but as always, there could be a bug in the conversion process. The Ptolemy bug you would see would not be Java crashing, it would be a dialog window popping up with a stack trace. The bug you report below is a platform specific Java bug that is triggered by Ptolemy II. I've verified that I can run a model under Ptolemy II 2.0.1 with JRE 1.3.1_07 under Windows 2000 on an IBM 600X with the most recent updates installed using IE's 'Tools -> Windows Update' facility. The updates include SP3, DirectX 8.1 and Net -------- Hi Christopher, My platform is Windows 2000 and updated all service pack through windows update. I installed Java 1.3.1_06 and sucessfully installed PT 2.0.1. But i discovered that PT 1.0.1 can't be installed under Java 1.3.1_06. It complains "No suitable JVM found". However, after I installed Java 1.3.1_02, PT1.0.1 can be successfully installed. Now, PT 2.0.1 still can't reads PT1.0.1's library. How can I solve it? [EMAIL PROTECTED] ("Christopher Hylands") wrote in message news:<200301 [EMAIL PROTECTED]>... > That is a bug in Java, not a bug in Ptolemy II. > Java should not crash, no matter what Ptolemy II does. > > What platform are you on? > I'm guessing Windows NT. > What service pack? > You might try a different OS, or upgrade your current OS to > the most recent service pack. > > It looks like you are running under Java 1.3.1_06 > Ptolemy II 2.0.1 works best under Java 1.3.1 > Try using the most recent version of Java 1.3.1, which is > 1.3.1_07, see > http://java.sun.com/j2se/1.3/download.html > > There is a slightly similar bug at > http://developer.java.sun.com/developer/bugParade/bugs/4410477.html > at the bottom someone reports a similar error, but there is no > solution. > > You could also try running under Java 1.4.1. Note that the > code generator facility in Ptolemy II 2.0.1 will not work with > Java 1.4.1, but everything else should. > > BTW - 2.0.1 is not backward compatible with 1.0.1's library. > 2.0.1 will convert 1.0.1 libraries to be compatible to 2.0.1. > The ptolemy/moml/filter/*.java classes do the conversion, which > is summarized in the release notes > http://ptolemy.eecs.berkeley.edu/ptolemyII/ptII2.0/ptII2.0.1/doc/ptII2.0. release.htm > In principle, it should be possible to convert from Ptolemy II 2.0.1 > back to Ptolemy 1.0.1. I would probably use xslt to do this though, > > -Christopher > > -------- > > Our project started using Ptolemy in 2001. We used the Ptolemy versio n > 1.0.1 to build a good deal of self-defined library. Now, we are using > Ptolemy2.0.1 and try to import our library. Unfortunately, the 2.0.1 > is incompatible with 1.0.1's library. 2.0.1 can't open or import the > library, with error showing in a txt file. > How can we solve this problem? As it is non-sense to rebuild our > library. > > Thanks > > b > // txt file shows error > An unexpected exception has been detected in native code outside the > VM. > Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at > PC=0x6d0d9c03 > Function name=Java_sun_awt_Win32GraphicsConfig_getBounds > Library=F:\jdk\jre\bin\awt.dll > > Current Java thread: > at sun.awt.windows.WToolkit.eventLoop(Native Method) > at sun.awt.windows.WToolkit.run(WToolkit.java:183) > at java.lang.Thread.run(Thread.java:479) > > Dynamic libraries: > 0x00400000 - 0x00455000 F:\Ptolemy\vergil.exe > 0x77F80000 - 0x77FF9000 F:\WINNT\System32\ntdll.dll > 0x77D90000 - 0x77DEA000 F:\WINNT\system32\ADVAPI32.dll > 0x77E60000 - 0x77F36000 F:\WINNT\system32\KERNEL32.DLL > 0x77D20000 - 0x77D8F000 F:\WINNT\system32\RPCRT4.DLL > 0x77DF0000 - 0x77E54000 F:\WINNT\system32\USER32.dll > 0x77F40000 - 0x77F7C000 F:\WINNT\system32\GDI32.DLL > 0x777E0000 - 0x777E7000 F:\WINNT\system32\VERSION.dll > 0x75950000 - 0x75956000 F:\WINNT\system32\LZ32.DLL > 0x75E00000 - 0x75E1A000 F:\WINNT\System32\IMM32.DLL > 0x6D420000 - 0x6D4F9000 f:\jdk\jre\bin\hotspot\jvm.dll > 0x77530000 - 0x77560000 F:\WINNT\System32\WINMM.dll > 0x78000000 - 0x78046000 F:\WINNT\system32\MSVCRT.dll > 0x67ED0000 - 0x67ED7000 F:\WINNT\System32\serwvdrv.dll > 0x66360000 - 0x66367000 F:\WINNT\System32\umdmxfrm.dll > 0x6D220000 - 0x6D227000 f:\jdk\jre\bin\hpi.dll > 0x6D3B0000 - 0x6D3BD000 f:\jdk\jre\bin\verify.dll > 0x6D250000 - 0x6D266000 f:\jdk\jre\bin\java.dll > 0x6D3C0000 - 0x6D3CD000 f:\jdk\jre\bin\zip.dll > 0x6D020000 - 0x6D12A000 F:\jdk\jre\bin\awt.dll > 0x777C0000 - 0x777DD000 F:\WINNT\System32\WINSPOOL.DRV > 0x77A30000 - 0x77B24000 F:\WINNT\system32\ole32.dll > 0x6D1E0000 - 0x6D21B000 F:\jdk\jre\bin\fontmanager.dll > 0x72700000 - 0x72746000 F:\WINNT\System32\DDRAW.dll > 0x727A0000 - 0x727A6000 F:\WINNT\System32\DCIMAN32.dll > 0x10000000 - 0x10170000 F:\WINNT\System32\i81xgicd.dll > 0x0D970000 - 0x0D9CD000 F:\WINNT\System32\i81xGDEV.DLL > 0x6E260000 - 0x6E266000 F:\WINNT\System32\INDICDLL.dll > 0x6D190000 - 0x6D1B2000 F:\jdk\jre\bin\dcpr.dll > 0x77900000 - 0x77922000 F:\WINNT\system32\imagehlp.dll > 0x72900000 - 0x7292D000 F:\WINNT\system32\DBGHELP.dll > 0x68E00000 - 0x68E0B000 F:\WINNT\System32\PSAPI.DLL > > Local Time = Fri Jan 31 16:16:37 2003 > Elapsed Time = 748 > # > # The exception above was detected in native code outside the VM > # > # Java VM: Java HotSpot(TM) Client VM (1.3.1_06-b01 mixed mode) > # > -------- -------- ---------------------------------------------------------------------------- Posted to the ptolemy-hackers mailing list. Please send administrative mail for this list to: [EMAIL PROTECTED]
