Jump to content
Excelsior Forums

johnrule

Members
  • Content count

    0
  • Joined

  • Last visited

Everything posted by johnrule

  1. Mac OSX version

    Have you changed your position on providing a Mac OSX version? I would really like to deploy my Java application to the Mac platform...it is one of the main reasons stopping me from upgrading. Thanks, JR
  2. Mac OSX version

    I hope you realize that by the time you get around to this there may not be an OSX -- maybe you should focus on an IOS version.
  3. Mac OSX version

    Any progress?
  4. Windows 8 support?

    My stuff seems to run ok, but not 100%...you have to test everything to make a determination yourself. I hope you are working on the OSX version of JET before you worry about Windows 8!
  5. Mac OSX version

    OK...I will keep an eye on your website, and hopefully you will send out emails announcing anything. I hope you will maintain support for Linux too. By the way, I like the new forum! Thanks, John
  6. Random memory leak

    Ok...this is strange. I don't know how long this has been happening, and it is random, so it is difficult to track down. It seems that only sometimes my executable develops a memory leak during a thread execution, but other times it runs fine doing the exact same thing. For example, I start-up my executable and watch the task manager to see how much memory is taken after everything settles down (all windows open, etc.). I have been using the same test every time...I simply start a thread. It doesn't seem to matter what thread, just any thread, and the memory starts accumulating until I get an "Uncaught exception: Out of Memory" error (after only a few hundred k by the way). However, sometimes it runs fine, and it always runs fine after a fresh boot or restart. I know you don't like to hear this, but it runs fine every time as a .jar...it is my only other reference. I guess I am hoping that this is common and you will know what it is right away. I have tried many different settings for memory and garbage collection with the same results. Windows XP SP3 JET 6.4 (6.10) 2 gig Ram Any ideas? Thank you, JR
  7. Random memory leak

    It was a conflict with another running process... JR
  8. Well, I thought I would do a test to see how this works for a limited user account, and I discovered that my Excelsior made installer fails. I have been working with JET using an administrator account, and I didn't check this. I am not referring to file associations, I am stating that my installer failed with an error that it could not install a particular file...so it installed nothing. It would be more professional if a dialog would at least inform the user that it will not work because of limited user rights (or something), and exit gracefully...rather than starting the install and failing towards the end. I am going to try another installation system. I am simply compiling to a single executable using JET, but any other files I need to include (or any other advice) would be welcome information. JR
  9. Installation without admin rights

    The solution is to use NSIS as the installation system... JR
  10. Installation without admin rights

    I am not sure why this was moved from the original thread to "Installation without admin rights"...that is not my question, and I am not looking to circumvent anything. You can close this thread if you wish. JR
  11. File associations

    I just noticed in the JetPack II produced installer (6.4) that file associations do not happen (and there is no screen for selecting/deselecting) when the user selects "Personal" for "Installation Type". Is this normal? Thanks, JR
  12. File associations

    As far as I can tell there is only one place in the registry to impose file associations (Windows XP), and I see no evidence that 'Personal" settings should affect that. I think this should be changed since it is very easy for a user to choose 'Personal' rather than 'Common'...currently, they would have no file associations if they did. JR
  13. File associations

    I am trying to find information that verifies what you stated...it just doesn't make sense. Do you have anything to back this up? I can't imagine that all 'Personal' installations would be void of file associations. My first question would be: why? JR
  14. reverse engineering

    Can you (Excelsior) reverse engineer your own product, or is the conversion process pretty much one-way (i.e. hard for everyone)? Thank you, JR
  15. Installing as Root on Linux

    While I was checking out the Linux 6.4 demo in Suse 11.1, I tried to install under my root account and got the infamous Runtime error #3. Everything installed fine, and I could run jetsetup with its typical commands. However, I got the #3 error when I tried to run the LaunchPad...everything seems to work under my normal accounts though (except for that 'Package' thing). JR
  16. Linux demo problem

    Hello, I just tried the Linux demo (6.4), and I ran into an issue that I just reported for the Windows version. When you open JetPackII to build, you get an error dialog that states the version of the executable was built with an older version, and cannot be used. On Windows, this only happens the first time but there was no work around in Linux. In other words, I was not able to build a standalone for distribution...quite unusable. I still have an older version (4.5) that seems to work fine... This was tested on a new install of Suse 11.1 with Java 5 build 8 installed, Athlon dual core x64 (32 bit install). JR
  17. Linux demo problem

    I have an older install of JET 4.5, and I installed the 6.4 demo to check it out. This is on Suse Linux 11.1 by the way... It happens right after the compile finishes, and a prompt comes up asking if you want tor Run or Package. If you press 'Package', JetPack is launched, but it points to the default JET install directory (i.e. my 4.5 install, which has an executable in there)...so it sees the wrong executable, and gives me an error. This is not a big deal (you just open JetPack separately) but for someone who has an older installation and is looking at upgrading, it can be a little frustrating. Even after I created a new .jpn file, and saved to a new directory (I have a totally separate directory from my 4.5 install of course), it still points to my old directory if I launch JetPack II from the 'Package' button. Thanks, JR
  18. Save as Updateable

    How does the 'Save as Updateable' feature work between JET upgrades? I have a product that was compiled using the Java 1.6.0.7 profile, and I want to update everyone to the new 1.6.0.10... I just ran a test, and it appears to work, but I thought I might ask first before I release. Just out of curiosity, how far back can an updateable work? What if I have a customer who has not upgraded for a long time (i.e. they are still on 1_5_0_ and they use my updater? I will run a few test here, but an answer from the experts would be more reassuring Thank you, JR
  19. Save as Updateable

    I just did a test using the latest JET (6.4 Professional on XP). I have an older application installed (compiled with profile 1.6.0_7) and I created an updater using the new build (compiled with profile 1.6.0_10). It did not go as smoothly as I hoped. The first issue is that a 'Read Me' file that was updated from the last build (and from the time the updater project was created) was not included in the new updater. When I went to look at the included files for the updater build, the tooltip that came up when I hovered over the 'Read Me' file stated: "This file was included in the original build and will not be included" (or something to that effect) I would expect that the updater would simply compare modification dates on any files that I have included for packaging and include them. The fix was to manually copy it over into the 'Package Files' field. The other unexpected behavior was from the packager itself. When I opened the updater profile it gave me a warning stating: "The file: 'your executable' was compiled by another version of JET. Though it is compatible with this project, it is recommended to rebuild." This was not correct since I did the build with the 1.6.0_10 profile. The test that I performed was to install a fresh copy of my 1.6.0_7 application, and then apply an update from the 1.6.0_10 updater. Since I have not really changed much in my code it seems to work, but I did have one glitch with the database interface. I rebuilt the updater and applied, and now it seems to work. However, I did not feel confident about this process, so I uninstalled and did a full installation. I guess I am still wondering how JET manages a change in profiles like this? How automatic is it? Do I need to manually include files (like the 'Read Me' example) that have changed? Do I recommend a fresh install for my customers when a new profile is created? Thank you, JR
  20. Save as Updateable

    Never mind...I read the help on 'Updatable'. JR
  21. How do i complile the JMF

    > Try to remove the DLLs from System32 and copy them to the directory where the compiled executable resides. And here in lies the missing piece of information that was not in the original instructions: The dlls need to be in the same directory as your executable jar. So, it was pointless to upload my project file (which was my point ) because this would relate to how the .dlls are included with JetPack. If anything, you should have asked for my JetPack project file (.jpn). > This is called "customer does not cooperate" First of all, what you were asking made no sense. Second, telling a customer to "just do it" is not a good practice, and I found it offensive. I have the right to not cooperate at this point. I also reported the issue because I did not know your were an employee. > We've checked the last two support cases you filed some time ago and found that they were caused by inaccuracies or bugs in your code and configuration files. I don't understand what relevance this has to the thread, but now I need to clear this up... As a customer with a professional license for Windows and Linux, I reported what I thought was a problem with JET because my .jar would work fine by itself, but crash as a JET executable. Eventually, it turned out to be a memory leak that I fixed without your help from what I recall. That was it...don't exaggerate. I think we should stay on topic if we want to accomplish anything, agreed? I was simply responding to Dmitrys request to help with the thread... JR This is called "customer does not cooperate" I'll explain what's the point. We've checked the last two support cases you filed some time ago and found that they were caused by inaccuracies or bugs in your code and configuration files. In fact, we spent much time to help you debug your applications. Those stories deserve publication in the "Support's Fairy Tales" topic of this forum (without names, of course). So an extra sanity check definitely makes sense. Hope for your understanding.... -------------- Ok, let's make an optimistic assumption that your project file is correct. Try to remove the DLLs from System32 and copy them to the directory where the compiled executable resides. Let us know the results.
  22. How do i complile the JMF

    This is pointless... JR
  23. How do i complile the JMF

    What would the project file show? That the classpath entries are incorrect? The point is, you need the .dlls in the Windows/System32 directory to make this work. In order for the 'classpath' method to work, you would have to modify how all jars are accessing the .dlls... Unless there is some ambiguous translation that happens in JET, I don't see how this will work. Can you upload a project that works with this method? JR
  24. How do i complile the JMF

    I just did some testing (on Windows XP) and I absolutely need the .dlls installed in the Windows/System32 directory to get things like mp3 to work. Did you actually uninstall JMF before you tested this procedure? I saw no connection (and neither did JET obviously) between the classpath entries of the 'lib' and 'jmfresources' and the .dlls. I imagine that something is looking specifically in the Window/System32 folder, so how could this possibly work? In my findings, the only way to get this to work is to provide a post installation of the .dlls to the Windows/System32 directory. In fact, this is what I did to test this: - I installed the JMF without the option to copy the .dlls to Windows/System32. - I copied the .dlls to a separate folder. - I uninstalled JMF, and deleted all JMF System variables. Then, I tested these instructions (from JET and from NetBeans), and I kept getting "unrecognized file format" errors from the jvm. To remedy this, I simply copied all of the .dlls (from my separate folder) to the Windows/System32 folder and viola! It works. Someone please clarify if I missed a step, or if there was some 'understood' step in this procedure because I would like to get this to work without installing JMF. Thanks, JR
  25. I think there is a problem with the way that JET 4.5 handles drawing buttons with transparent images (i.e. they are 'translucent'). I am getting a lot of contention when I press a button that has it's alpha channel set to a value that makes the current image translucent. This only happens with JET 4.5, and I do not have this problem with anything else: (with JRE 1.5.0_08 and 1.6.0_03) NetBeans 5.5.1 execJ ProGuard Launch4J (and running the jar by itself) As a test, I downloaded JET 6.0 evaluation, and the problem is gone. I don't even have to compile because the test run works fine...which indicates that the compiled JET files have the fix, correct? The workaround for now (in JET 4.5) is to turn the border off for buttons that have a translucent image to draw, and then it will draw (seemingly) normally. So maybe this is a border issue? Please fix. JR
×