![]() ![]() Note that doing this without setting the $UserBaseDirectory to its 'new state' is a waste of time in most cases. Since it is only an issue of download time (unless you saved the installer), if you have invested this much time, it makes sense to install a fresh copy of Mathematica. I would keep the old folder somewhere, especially if you have custom stylesheets, palettes, or other add-ons. When you restart Mathematica, you will need to re-authorize. If you have no issues with other apps, or with Disk Utility, you may simply want to remove the Mathematica folder from within ~/Library (aka $UserBaseDirectory). It is possible that your issues have to do with obsolete stuff in the $UserBaseDirectory. Depending on your history, the same may be true for you. These computers had been updated from older installations over the years, and so there was a lot of cruft in the System Folder (and elsewhere). The download managers, and some other installers apparently do not clean up after themselves very well. In addition, inside the ~/Library folder, there was a lot less stuff from Wolfram. ![]() On my MacBook Pro, I saved the contents of my documents folder and did a clean install.Īfter I did that, there were no more problems with Disk Utility. I ended up using recovery mode (cmd-R on restart) to erase the hard drive, re-install Mojave, and then restore from a back-up. Apple support said that these were left-overs from the installation, and they should go away. I ran disk utility immediately after the installation, and it found orphaned dream object. When I installed macOS Mojave on my two main computers (a 2017 27 inch iMac and a 2016 15 inch MacBook Pro), there were issues with the installation. I had no issues with the program itself, although there were issues with the download manager. I tested each beta with Mathematica 11.3 - actually Wolfram Desktop from a Wolfram|One trial, since I don't have a third license. I was a beta tester for Mojave on my 'spare' computer (a 13 inch MacBook Pro). I checked my interactions with Apple and Wolfram re Mojave. If nothing else, it will restore your installation to a "known state" for dealing with tech support. (I have had to do a similar thing to other apps that I have upgraded over multiple versions of macOS and multiple computers.)įurther, if you encounter any weirdness with Mathematica, I would recommend un-install and re-install including removing the $UserBaseDirectory. The problem is more obvious now due to the 64 bit issue. Note that this is probably a general issue for upgrades of many apps, that there may be older bits that are no longer used, but which are still on disk. ![]() I did this for the final version of Mathematica 12, and everything worked just fine. Once you have gotten rid of the "cruft", you can probably install new versions by simply replacing the app. You will need to re-enter the activation key (or restore the file that contains it), and then copy back any stylesheets, etc. Refers to $BaseDirectory, which no longer exists for most users, but is otherwise pretty thorough. This is not the "official" web page, and recommends the use of a different application. There is a new web page (which Dale has linked to) about uninstalling Mathematica. Since I did this, there have been no issues, and macOS Mojave reports that not only is Mathematica fully 64 bit, there are no legacy apps or components associated with Mathematica. You should move this directory (folder) to another location so that you can copy back any customizations you have installed, such as stylesheets or applications or packages. depends on your installation history) before any upgrade. So, now, I routinely remove the $UserBaseDirectory (etc. There were some old components that earlier versions of Mathematica used that were not removed during a simple installation. I came across a similar issue during the beta test for version 12.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |