Floating Point

I have a macbook pro with bootcamp partition.

The windows OS is 64 bit, using Max 6.1.9 (64 bit).

I have used the final version of jdk se 7, namely 1.7.0_79-b15, to build my classes.

The VM build is 24.79-b02. The windows version is 6.1.7601 (2009)

My client has a windows box with the exact same version OS and JRE, and yet the classes of the standalone (which is an exact duplicate of my standalone) wont work on his machine-- all other aspects of the standalone work fine-- just the crucial mxj objects. It's strange, it's like the max.jar is not seeing the jre on the client's machine... any suggestions?

I have a macbook pro with bootcamp partition.
The windows OS is 64 bit, using Max 6.1.9 (64 bit).
I have used  the final version of jdk se 7, namely 1.7.0_79-b15, to build my classes.
The VM build is 24.79-b02. The windows version is 6.1.7601 (2009)
My standalone runs fine on my machine.

My client has a windows box with the exact same version OS and JRE, and yet the classes of the standalone (which is an exact duplicate of my standalone) wont work on his machine-- all other aspects of the standalone work fine-- just the crucial mxj objects. It's strange, it's like the max.jar is not seeing the jre on the client's machine... any suggestions?


max-6-standalone-java-classes-run-on-a-machine-but-not-other-identical-machine

What are the symptoms? Is any of the MXJ machinery working (such as the built-in demo classes)?

there isn't a max install on their machine, just the standalone I made that i've sent to them, so i can't as yet test for this-- the context is this:

I built a 32-bit max patch into a standalone that has some system interaction problems (intermittent kernel crashes, but only on their machine).

So, to placate them, I upgraded my 32-bit windows system to 64-bit, so it mirrors their system, and used the 64-bit version of max to make a standalone from the exact same original 32-bit patch (but with 64-bit versions of the objects of course) . I also installed a 64-bit version of jdk 7 as previously described, and recompiled my mxj classes used in my patch within the 64-bit java environment. They also put in a 64-bit jre 7 on their machine to run my compiled classes. So everything should be 64-bit.

I think what I'll do now is rebuild my standalone with the max window showing (at the moment it's hidden) , so at least I can see some diagnostic information. But to reiterate, everything in the standalone runs fine on my machine-- but nothing java-related works on their machine, even though the standalone launches, and anything non-mxj works fine on theirs.

Some of the classes I've written myself, some are adaptations of stuff topher lafata wrote for c74, some are pure max distribution (like net.udp.send) some are 3rd party... all work fine on mine-- none work at all on theirs....

What would you do? I can't install a demo version of max on their machine, coz I already did that a couple of years earlier for something else and it's expired... I can however access their machine remotely, so if you have any advice about what to look out for or re diagnostics, please let me know...

there isn't a max install on their machine, just the standalone I made that i've sent to them, so i can't as yet test for this-- the context is this:
I built a 32-bit max patch into a standalone that has some system interaction problems (intermittent kernel crashes, but only on their machine).
So, to placate them, I upgraded my 32-bit windows system to 64-bit, so it mirrors their system, and used the 64-bit version of max to make a standalone from the exact same original 32-bit patch (but with 64-bit versions of the objects of course) . I also installed a 64-bit version of jdk 7 as previously described, and recompiled my mxj classes used in my patch within the 64-bit java environment. They also put in a 64-bit  jre 7 on their machine to run my compiled classes. So everything should be 64-bit.

 I think what I'll do now is rebuild my standalone with the max window showing (at the moment it's hidden) , so at least I can see some diagnostic information. But to reiterate, everything in the standalone runs fine on my machine-- but nothing java-related works on their machine, even though the standalone launches, and anything non-mxj works fine on theirs.

What would you do? I can't install a demo version of max on their machine, coz I already did that a couple of years earlier for something else and it's expired... I can however access their machine remotely, so if you have any advice about what to look out for or re diagnostics, please let me know...


"solved" by reinstalling java on clients machine.... thanks, apologies for the noise

[max 6] standalone java classes run on a machine but not other identical machine