Installing R2013a on Mountain Lion

Question

Léonard Roussel 2013-10-21

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/90924-installing-r2013a-on-mountain-lion

关闭： MATLAB Answer Bot 2021-8-20

Dear all,

I'm having trouble installing MATLAB R2013a on my Mountain Lion machine. The installer is not even starting up. It shows in the Dock for a few seconds and then disappears.

I've been in touch with the Mathworks support team about this but all they seem to be able to do is giving me new installer files to download and run but on which the problem stays the same.

It should be a problem about all this Java / X11 / XQuartz conflict, right? I'm a total noob there and would gladly welcome any kind of help.

Thank you very much.

Léonard.

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

此问题已关闭。

Answer 1

Walter Roberson 2013-10-21

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/90924-installing-r2013a-on-mountain-lion#answer_100373

I am doing okay with R2013a and R2013b on Lion (before Mountain Lion). However, I do not seem to be able to use the automatic installer. I have to use the manual installation instead. Download and unarchive the installer. Download all the appropriate components into the resulting directory, but do not unarchive them. When ready, double-click on the installer executable that was in the unarchived installer directory.

The bit about not unarchiving the other components but putting them into the unarchived directory was the trickiest part of it all.

1 个评论
显示 -1更早的评论隐藏 -1更早的评论

Léonard Roussel 2013-10-21

I'm not sure I get it. I only have one .iso file containing all (I suppose) installation files, including the "InstallForMacOsX" one (with the Matlab logo as icon). Should I re-archive (how?) all the other files into that same folder?

Thanks a lot.

Answer 2

David Sanchez 2013-10-21

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/90924-installing-r2013a-on-mountain-lion#answer_100374

Make sure the installation files are executable. Use chmod as sudo if not. I had a similar problem that was solved once some files within the java folder were made executable. I don't remember which ones, so, you'd better make them all executable.