[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Virtual Memory too low, windows 8.1

From: Philip Nienhuis
Subject: Re: Virtual Memory too low, windows 8.1
Date: Sat, 24 Jan 2015 15:25:25 -0800 (PST)

BrianTerbush wrote
> Thank you so much for the quick and informative reply!  I would have
> responded sooner, but didn't know there was a reply yet, so, apologies.
> There seem to be other issues with my machine, because even after
> installing java (and uninstalling and reinstalling multiple times), now
> that I've tried to download the mxe build, it will not install properly,
> and warns that I do not have a version of JDE on my computer, and that
> some parts of the installation will not work.
> I did dowwnload the 64-bit version of 3.8.2, also, but only "portable" was
> available from that site, so I'm not exactly sure how to make that work
> from my computer.  Downloading the installer, and attempting to set up
> 3.8.2 is what I was doing when I found the java error today.
> I've been using this page for reference:
>, but haven't really found what
> I'm looking for yet.  Any tips, or anyone else experiencing the Java not
> existing problem?
> (JRE not being recognized on 3.6.4, while trying to follow the advice in
> the link Phil shared was what led me to the question about java issues).

I wouldn't know why the portable version wouldn't work from a hard disk in a
The 64-bit versions do not have a nice setup program yet; you have to unzip
/ un7-zip it into a subdir, in a path WITHOUT spaces; next thing is to copy
the bin/octave.bat file and paste it on your desktop *as shortcut* (right
click, "paste shortcut").

As to the Java JRE, that's another known issue. JRE's (and JDK's)  come in
32-bit and 64-bit flavors as well. I think that is what bites you now.
Luckily, it is my experience that you can have both flavors installed
alongside each other on a Windows system. I usually have one of them as JDK
(Java Developing Kit) and the other as JRE (Java Runtime Environemnt); and
the JDK includes a JRE as well.
I do not know what flavor has been used to make the 64-bit indexing Octave
build you are using; but it should match the flavor Octave's Java support
was built with. So you'd have to experiment.

The final pitfall is that on 64-bit Java JREs the jvm.dll file is in a
"server" subdir rather than a "client" subdir where Octave expects it at run
time (at build time is another story that has been covered).
Just search in Explorer from the 64-bit Java install directory for jvm.dll
and you'll soon find out. Just copy the server subdir verbatim to a client
subdir in the same place and it should all work (keep fingers crossed).

Oh and 3.6.4 is an old Octave version, that (AFAIK) has no 64-bit versions.
It'll only work with 32-bit Java JREs.


View this message in context:
Sent from the Octave - General mailing list archive at

reply via email to

[Prev in Thread] Current Thread [Next in Thread]