Discussion:
[Jxplorer-users] jXplorer install on Win2008 R2 SP1
Chris Betts
2012-03-27 19:27:53 UTC
Permalink
Hi Mark,

I don't know why the installer is failing (it's a commercial product;
usually pretty solid - but not our code :-) ). Windows installers have
always been a bit of a black art to me... I suspect some subtle problem in
identifying the java home directory.

That said, if you have a working install you should be able to just
copy over the jxplorer/ directory and use the jxplorer.bat file to start?
(or set up the windows short cut yourself - it really just runs the batch
file... )

Anyone else seen this?

- Chris
Hi Chris,
I'm a big fan of jXplorer and been using it for a while now with no
problems. I'm having a new problem I've never seen before and I'm pulling
my hair out.
I've installed jX on many machines, some 32-bit, a few 64-bit, including
Windows 2008 R2. However, I'm on a Win2k8R2 box and I can't install it and
have no idea why. I've tried to mirror another Win2k8R2 box on which
jXplorer is running just fine. I'm running JDK 6 update 25 on both
machines, including having installed a public JRE. Machine 1 has jXplorer
running fine, machine 2 I can't even install it. I get the splash screen
then this error: "The installer could not find a valid Java(tm) on this
machine. Supported versions: Vendor: Any min. 1.5.0 max. any"
Interesting side note... at one point, when I had forgotten jXplorer was
working on machine 1, I thought perhaps jXplorer needed a 32-bit Java, so I
installed one (just a JRE). *I could successfully install jXplorer*.
However, I think this 32-bit Java is creating completely unrelated problems
with things other than jXplorer, so I took it off. I removed all Java and
re-installed JDK 6 update 25 to get back to a fresh state. This is when my
install problems began again (I say "again" since it's the same problem I
had when I originally went down the path of installing the 32-bit Java).
Do you have any ideas what is going on here?
If jXplorer truly did need a 32-bit Java, I could understand that. After
all, I was able to to install it on this problematic machine 2 when I did
install a JRE 32. But then the question is: why is it running on my other
64 bit machine (machine 1)?
Thanks for any help you can provide.
Mark Bramer
--
Dr Christopher Betts
Pegacat Software
Melbourne, Australia
m: 0408 533 456
mark bramer
2012-03-27 19:38:47 UTC
Permalink
Thanks for the reply, Chris. Copying over a working install's folder and
running the .bat works fabulously. Thanks!!! -Mark
Post by Chris Betts
Hi Mark,
I don't know why the installer is failing (it's a commercial product;
usually pretty solid - but not our code :-) ). Windows installers have
always been a bit of a black art to me... I suspect some subtle problem in
identifying the java home directory.
That said, if you have a working install you should be able to just
copy over the jxplorer/ directory and use the jxplorer.bat file to start?
(or set up the windows short cut yourself - it really just runs the batch
file... )
Anyone else seen this?
- Chris
Hi Chris,
I'm a big fan of jXplorer and been using it for a while now with no
problems. I'm having a new problem I've never seen before and I'm pulling
my hair out.
I've installed jX on many machines, some 32-bit, a few 64-bit, including
Windows 2008 R2. However, I'm on a Win2k8R2 box and I can't install it and
have no idea why. I've tried to mirror another Win2k8R2 box on which
jXplorer is running just fine. I'm running JDK 6 update 25 on both
machines, including having installed a public JRE. Machine 1 has jXplorer
running fine, machine 2 I can't even install it. I get the splash screen
then this error: "The installer could not find a valid Java(tm) on this
machine. Supported versions: Vendor: Any min. 1.5.0 max. any"
Interesting side note... at one point, when I had forgotten jXplorer was
working on machine 1, I thought perhaps jXplorer needed a 32-bit Java, so I
installed one (just a JRE). *I could successfully install jXplorer*.
However, I think this 32-bit Java is creating completely unrelated problems
with things other than jXplorer, so I took it off. I removed all Java and
re-installed JDK 6 update 25 to get back to a fresh state. This is when my
install problems began again (I say "again" since it's the same problem I
had when I originally went down the path of installing the 32-bit Java).
Do you have any ideas what is going on here?
If jXplorer truly did need a 32-bit Java, I could understand that. After
all, I was able to to install it on this problematic machine 2 when I did
install a JRE 32. But then the question is: why is it running on my other
64 bit machine (machine 1)?
Thanks for any help you can provide.
Mark Bramer
--
Dr Christopher Betts
Pegacat Software
Melbourne, Australia
m: 0408 533 456
Loading...