MATLAB: Can I install MATLAB R2006a on a MacBook Pro with Intel Core 2 Duo processor

javavmmacMATLABprocessor compatibilityr2006a

I have an old original MATLAB installation kit for Standalone Named User Installations with accompanied License File. At my current job I have to work on a MacBook Pro running Mac OS X Version 10.6.8 with Intel Core 2 Duo processor.
Installation works fine. But when I try to launch MATLAB, the logo banner appears as a flash and than disappears.
In the Console this log appears:
JavaVM: requested Java version ((null)) not available. Using Java at "" instead.
JavaVM: Failed to load JVM: /bundle/Libraries/libserver.dylib
JavaVM FATAL: Java for ppc cannot run in this configuration.
JavaVM FATAL: Please consult documentation.
JavaVM: requested Java version ((null)) not available. Using Java at "" instead.
JavaVM: Failed to load JVM: /bundle/Libraries/libserver.dylib
JavaVM FATAL: Java for ppc cannot run in this configuration.
JavaVM FATAL: Please consult documentation.
Warning: Failed to start the Java Virtual machine - JNI error: -1.
Warning: Disabling Java support
< M A T L A B >
Copyright 1984-2006 The MathWorks, Inc.
Version 7.2.0.283 (R2006a)
January 27, 2006
To get started, type one of these: helpwin, helpdesk, or demo.
For product information, visit www.mathworks.com.
>>
Are there any way I can make my current MATLAB product work on my Mac?

Best Answer

  • R2006a was supported only on PowerPC. Apple switched to Intel processors and had a transition time where executables would run on either PowerPC or Intel. This was first supported in R2007a. R2006b was only PowerPC.
  • The OS version supported for R2006a were 10.4.x and 10.3.x. 10.6.8 is significantly newer, and Apple dropped PowerPC support for it -- it's only supported on Intel. So system libraries which were needed for PowerPC simply aren't there in 10.6.x and later.
So given that you are running a version built for PowerPC and the only processor architecture supported by Apple for the OS you are running is Intel, it's likely not to work.
You could try startup flags like -nojvm and so on, but I'd expect that you might just end up creeping a little bit further to hit another error.