![]() ![]() You could say that this proves (yet again) the need to place librarypath.txt and classpath.txt in a user folder rather than modifying the system files. I needed to manually copy my changes from the previous version onto the new version’s files. Matlab’s installer copies many user-generated preference files, but unfortunately not some files that are critical to using Java in Matlab, namely librarypath.txt and classpath.txt. This can easily be fixed using pathtool or the main menu’s File / Set path…, but I am guessing that most users would not have easily noticed this issue. This is a real shame.Ī more pressing problem is that the new installation keeps the old Matlab path (which points to the pre-release folders), rather than to the new production folders. So while I can still see my modified files in the pre-release folders, I can no longer see them in action. In effect, it uninstalled my pre-release without physically removing the files. Unfortunately, the Matlab installer may be too smart: It installs Matlab onto the new folder but prevents running the old pre-release in parallel. ![]() I often choose the later since I make changes to system files and I do not want them to be overwritten automatically. Matlab’s installer is smart enough to automatically detect an existing pre-release installation of Matlab, and polite enough to ask me whether to overwrite that location or to install Matlab into a new folder. I can’t do much regarding the first two, but at least I can delete the Japanese installer files after they have been downloaded: install_guide_ja_JP.pdf, archives/MATLAB713_doc_ja.zip, help/ja_JP etc. I have nothing against Japanese in general, I just hate my time, bandwidth and disk space being wasted in vain. The hickup here is that the installer automatically downloads dozens of MB of Japanese-related materials (documentation, translation files etc.) that are irrelevant to me (as well as for most Matlab users). This second XML file actually contains the list of installer application file URL and some zip files that contain the actually installable files. After downloading the specified JARs, is invoked with a specified URL of another XML file. Installerĭouble-clicking the JNLP file then runs the JNLP using the OS’s JRE. jnlp extension manually solves this issue. I cannot then run this file, since it has no file extension. The hickup I encounter four times a year (two pre-releases and two production releases) is that at least on my system, FireFox downloads the file not as download_agent.jnlp but as download_agent. This is a very small (2KB) XML file that tells your Operating System’s Java runtime engine, which automatically runs JNLP files, which JAR files to download (yes, the basic loader is Java-based). Matlab uses a simple download_agent.jnlp file as its installer bootstrap loader. All these issues have occurred for the past several Matlab installations, and are NOT unique to the new R2001b: Bootstrap loader Note that on your system you may be unaffected by some or all of the issues below. Perhaps the items below might alleviate some of the pain. ![]() Ubunto) need to go through in each installation. I have a plain-ol’ Win XP machine and hate to think what users of Macs/Linux (esp. 7.13), once again I came across a few undocumented hickups. With Matlab’s latest release yesterday (R2011b, a.k.a.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |