Hi folks,

I've read the posts here and here already, but not found a solution to my problem.

I'm trying to design a package for both Windows 7 32 and 64 bit. The links above work perfect with 32bit Windows 7.

In 64 bit, what I am seeing is some sort of system file checker action going on. If I make a change to deployment.properties in the user context, when I run either the Java control panel, or invoke the browser that loads a page with Java on it, the deployment.properties reverts back to whatever contents it had before I made the change.

If I use deployment.config and point to a local deployment.properties (so to override at the system level) it works fine on 32bit windows 7. The values seem to be ignored on 64bit.

Does anyone have any insight here? I think the deployment.properties and deployment.config are the way to properly automate Jave JRE deployments, but we are rapidly moving towards a 64bit windows 7 environment and this is an issue.

Thanks in advance!


P.S. If I've missed any info, please don't hesitate to ask.
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


ORIGINAL: timmy22

I'm trying to design a package for both Windows 7 32 and 64 bit.

Isn't there a separate kit for Java 6 Update 23 64-bit ? Located here perhaps ?


Answered 01/15/2011 by: spartacus
Black Belt

Please log in to comment
Thanks for that, but 64bit java only works in a 64bit browser.

Very few activex controls have been ported over to 64bit, so the majority of folks still use 32bit browsers and 32bit plugins, like 32bit Java.

I had a little bit of success just before I walked out the door yesterday, but I'll go into the office later today to see why it partially worked...
Answered 01/15/2011 by: timmy22
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity