I have a problem building a standalone with Max 6 on Windows 7 which includes a mxj object. I get the following error message, when opening the standalone:

(mxj) Unable to resolve path of max.jar!mjx is rendered powerless.
•error: Unable to create JVM

I know this issue was mentioned bevore in this forum, for example here:

http://cycling74.com/forums/topic.php?id=13080

But copying the “Cycling’74/Max6.0/Cycling’74/java” folder in the standalone support folder didn’t work for me.

Has anyone experienced the same or knows how to solve this?

Thanks a lot – d

I tried every solution I could find in the forum, but no success.
I’m working on a project for some time now which includes making a standalone with some java objects. So this is a real bummer.

Any help much appreciated!

… do the pathnames include space or other characters that need to be escaped?

Jan

thanks for your reply. I’m not shure what you mean. The max.java.config File is included in the support/java Folder. It looks like this:

; This is the config used by Max when instantiating the JVM ;
; Comments are enclosed within 2 semicolons ;

; The file format is relatively fragile so pay attention ;
; when editing this file !! ;

; some example options one may use ;

; add all jars in /Users/topher/java/lib to the system classpath i.e. immutable classpath ;
; max.system.jar.dir /Users/topher/java/lib;

; add /Users/topher/foo to the system classpath i.e. immutable classpath ;
; max.system.class.dir /Users/topher/foo ;

; these next 2 are typically what you would want to use if you want additional directories ;
; added to your classpath for max ;

; add /Users/topher/myclasses to the dynamic classpath of MXJClassLoader ;
; max.dynamic.class.dir /Users/topher/myclasses ;

; add all jars in /Users/topher/myjars to the dynamic classpath of MXJClassLoader ;
;max.dynamic.jar.dir /Users/topher/myjars ;

; specify some jvm options ;
max.jvm.option -Xincgc
max.jvm.option -Xms64m
max.jvm.option -Xmx256m

; uncomment these options(i.e. remove surrounding semi colons ;
; to cause the JVM to be created ;
; in debug mode and listening for remote debugger connections ;
; on port 8074. This would enable you to interactively debug ;
; your mxj code using JDB or some other debugger which supports ;
; the JDI wire protocol ;

; max.jvm.option -Xdebug ;
; max.jvm.option -Xnoagent ;
; max.jvm.option -Xrunjdwp:transport=dt_socket,address=8074,server=y,suspend=n ;
; max.jvm.option -XX:-UseSharedSpaces ;

Do I have to edit it?

Thanks – D

1.) did you copy the files like described here: http://www.cycling74.com/docs/max5/vignettes/core/standalone_platform_win.html

2.) You are you on Max 6

I tried to build a standalone and a java class in max 6 on win XP and it fails as well. The same patch works fine on Max 5!

That’s a Bug I’d say!

Jan

thanks again for your time. Yes I copied all the files mentioned in the link.
I guess I’ll try contacting the support for this.

Cheers – D

I was building the standalone on my boot drive. When I tried building it on my secondary drive the error message disappeared…

I was building the standalone on my boot drive. When I tried building it on my secondary drive the error message disappeared…

That’s funny, I seem to remember the opposite being true of some version of Max5, except no error messages (standalones built anywhere but the boot volume just wouldn’t launch).

Not sure everybody has a second drive to build standalones…

p