Jump to content
Excelsior Forums


Excelsior Staff
  • Content count

  • Joined

  • Last visited

Posts posted by snowman

  1. CMD.EXE vs COMMAND.COM should make no difference.

    Check the value of COMPILERHEAP in the .prj file. If it is set to zero (which means adaptive behavior) and you do not have much RAM on your system, e.g. you only have 128MB, set it to some explicit value: [pre]


    [/pre] and do not forget to close all applications you do not need runnning during compilation.

  2. That is only true for the Professional Edition.

    SWT-based executables created by the Standard Edition require both JRE and JET run-time DLLs, so there is little sense in moving to SWT for Standard Edition users, except that SWT classes precompiled to a DLL takes 1.8MB disk space, whereas Swing/AWT DLLs from JET run-time take together about 10MB. (You may save some more space by adding swt.jar to your project.)

  3. JetPack is present and fully functional in the Evaluation Package.

    Please check that the file BIN\jetini.ini contains correct paths to JET and JDK and that the BIN subdirectory of your JET directory is present in the PATH.

    Don't you have an older version of JET installed? Or maybe the Personal Edition?

  4. Unfortunately, there is no simple way like BOOTCLASSPATH because the respective classes are pre-compiled into JET RT DLLs

    A possible workaround is to make customized versions of JET/BIN/sym.zip and JET/BIN/bod.zip :

     - rename or copy them to sym1.zip and bod1.zip

     - remove the org/xml/sax directories from sym1.zip and bod1.zip

     - edit JET/BIN/jc.red (replace original zip names with the customized ones)

    This trick is known to work with CORBA, but there is no guarantee that it will work with other packages. And NEVER try it with core packages like java.lang.

  5. Your program triggers an assertion in the memory manager when it returns a memory block to the operating system. Looks like a problem in native methods. Make sure you have the latest version of OpenCard and that your program works properly on the VM from that very JDK/JRE which you specified when installing JET.

    If it appears that your program works on that VM but fails when compiled with JET, create a sample illustrating the problem and email it to java@excelsior-usa.com, or upload to ftp.excelsior-usa.com/incoming (write-only) and drop us a note.

  6. You cannot do this in the current version, but there is a simple workaround:

    Suppose you had installed JET in C:\JET and specified that you want to use it with JDK 1.3.1_01. Rename C:\JET to, say C:\JET1.3.1_01 and run the installer again, specifying C:\JET as the installation directory and selecting JDK 1.4.0.

    Now, when you need to switch back to 1.3.1_01, rename C:\JET to C:\JET1.4.0 and C:\JET1.3.1_01 to C:\JET.

    If you need to uninstall JET completely, uninstall the copy currently in C:\JET from the Control Panel or the JET Statt menu, and then simply remove directories with the other copy(ies).

    The multiple JDKs capability will be implemented in the next version of Excelsior JET.

  7. That figure is the amount of virtual address space reserved by the process. JET runtime always reserves 512MB of space, but it does not commit more than the heap size you have specified.

    This reservation does not affect the amount of memory available to other processes, because it occur in the process' virtual address space.

  8. Am I correct in understanding that JET will still work with APIs not in that list (such as OpenCard)?

    Yes, you can use any third-party class library or API. For APIs on that page, there are project files and samples available for download. For other APIs, you would just have to figure out the necessary settings yourself or with the help of the JET graphical front-end.

  9. The JET installer does not alter your JDK directory and/or registry entires in any way. You can safely assume that JDK files are accessed in read-only mode by JET. All the generated DLLs are placed into the JET directory.

    As for Java extensions like COMM API, JavaMail, JavaHelp, Java3D, JAI, etc., they are not precompiled during install, but they are fully supported. Check out http://www.excelsior-usa.com/jettested.html, section "Java Optional Packages".

  10. -gui+ should work. The console window is always opened by the graphical front-end. If you run your application from the command line or from Windows Explorer, there should be no console window displayed.

    Nevertheless, have a look into the linker response file, <projectname>.rsp - the second line should contain "/sys=W".