I had to replace jre and jdk 32 versions with 64 bit version since I am developing on a 64 bit machine and needed to get serial IO working.
The 64 bit NetBeans Design GUI seems to have vanished since I upgraded from 32 to 64 bit.
Solved: uninstalled then re-installed NetBeans.
Related
Would like to install Oracle Client (11g or 12c or 18c) 32 bit version on RHEL 7 64 bit version OS. Came to know that Oracle software 32 bit wont work on 64 bit RHEL verion. This is required for cognos usage. How this can be tackled.
I have a 64 bit MATLAB installed on my computer.
I am not allowed to install a 32 bit MATLAB on my machine.
I wrote a code and converted it to an executable using application compiler.
Now employees with 32 bit operating systems can not run the executable.
The question is:
Is there a way to create a 32 bit application using a 64 bit MATLAB?
(again, I am not allowed to install a 32 bit MATLAB on my machine)
Trying to install Oracle 9i (32bit) client on a Windows 7 64bit computer. Seems to install fine, but when trying to run anything, such as the Net Configuration Assistant, it doesn't do anything, no errors, and nothing started in the background.
So the question is:
Can the 32 bit client of Oracle be installed on a 64 bit Windows 7 PC? Or does it need to be a 64 bit client?
You can install a 32 bit client, and if your software is 32 bit, you need to install the 32 bit client to use it, even on a 64 bit system.
This might be a dumb/naive question, and if it is please excuse me :)
I have a brand new machine with the following specs:
Inter Core i7 2600#3.4GHz
RAM 8 GB
Windows 7
This machine has a 64 bits architecture.
On my previous machine, I used to install 32 bits versions of Eclipse and run it using a 32 bits JRE, and my current Eclipse setup works perfectly on the new machine.
I tried to install a 64bits version of Eclipse, and run it with a 64 bits JRE, and I am wondering if there are any compelling reasons to switch to this kind of setup or stick to my existing install. I guess that I would have to reinstall all the plugins, and maybe find that some of them are not compatible with the 64 bits version of Eclipse.
So far, the 64 bits version seems to need quite some more RAM than the 32 bits version, which is something that I expected, but nothing seems to have improved.
Thanks for your advice!
In general I use 64-bit Eclipse without problem, but there can be issues around plug-ins such as:
Adobe Flash Builder only works with 32-bit
The Subversion plug-in Subclipse needs a native 64-bit version of Subversion installed separately
There may be more but those are the ones I've encountered in the past.
Moving to 64-bit gives you access to more addressable memory but it won't speed anything up, in fact it might reduce performance in some cases (but nothing I see as significant to what I do).
Well the only thing that will improve is that you are able to use the advantages of 64bit. Other then that I'm not aware of any improvement.
For example what's better in 64bit is that if you have a very large project set you would be able to handle it more comfortably. For more information on 64-bit please look here
If you want to be on the edge of technology your choice would of course be the 64bit setup.
About the ram, this is expected because some of the Datatyps now use 64bit and are therefore larger to store in memory.
For most plugins you will get a 64bit version or alternative and so far for what I've used it it always worked.
I have just watched the bug report http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6972329 so I want to ask... Is there a JDK upgraded version which handles the problem? Because if I develop an app with 32-bit JDK 6 will it work on 64-bit linux?
I have compiled my project with jdk 1.6.0_05 so I am not sure will it work for 32 or 64 bit linux ... won't it be the user.home as '?'
Thanks
The bug has absolutely nothing to do with the JDK used to compile Java code - Java bytecode is completely platform independant. The bug only occurs when you run a Java app on a 32bit JVM on a 64bit Linux, and even then it seems to depend on a specific (and possibly faulty) LDAP configuration.