![]() The only exception is when a new Mac ships with an as-of-yet-unreleased version of macOS specific to that hardware, which these days, is exceedingly rare. With rare exception, when a new Mac is acquired, we simply transfer a clone to the new Mac and keep working with little interruption. It has migrated across several Macs, as has most all the installations in our groups. I am literally running the same Mac OS to macOS installation started with the original release (and I believe even from the OS X Public Beta) there are zero measurable, let alone perceivable performance differences between it and a virgin installation of macOS and like applications. dlls and countless conflicts when something dies. Much to my chagrin, we have a number of supported machines which will continue to run versions from El Capitan through High Sierra and even Mojave – and a couple instances of Snow Leopard (Server) – in a VM, just so access to many dated, but impossible/difficult (e.g., Quicktime 7) and bothersome (e.g., iWeb, etc.) to replace apps can continue to live past their best-by dates.īoth Fusion and Parallels make sharing data in common Shared and User folders seamless and painless, so other than needing adequate RAM for the VM and plunking down the bucks for a novice-friendly interface (I feel the open source options are just too ugly for nervous users), they are totally viable.Īs stated above, you can clone your existing functioning 32/64-bit macOS installation, and drop it into a VM intact but I would caution that environment might have a number of background apps and tasks running that would be unnecessary duplicates in a VM, so you’d want to police the Startup and Login items to make sure you’re not running things there you don’t need (e.g, Adobe, Chrome, et al, Updaters iStat Menus, Memory Clean, etc) inside the VM.Īs for clean installs, don’t let the myths lead you down a painful path it’s *NIX, not Windows it will only load what you (and your app’s installers) tell it to load, and nothing else it doesn’t have a Registry filled with dead. ![]() It seems it might be possible but challengingġ0.15 is, to me, much more scary than the loss of Rosetta I only have one computer but both Clone and TM hard drives. I know I will have to do that when I upgrade to 10.15Īre there prior TidBITS messages OR Take Control books to use for reference? ![]() I haven’t done a clean install of a new operating ever. My sense is the answer to the above is NO! ![]() Will an UPGRADE to 10.15 remove all the 32 bit files (Apps and associated data / preference) files? Or will they all be put into a folder I can delete? Or will they be trying to run in the background and create even more sluggishness? Many still used that I haven’t found an update for OR a replacement. ![]() I have upgraded from pre OS X through macOS 10.14 and my (yes sluggish) iMac is facing a big change in life (and yes I still, yesterday, used iWeb to update a web site)Ī few questions, does anyone have information or informed speculation: For the first time in over about 30 years of owning Apple computer products I DREAD this fall when the Mavericks successor (macOS 10.15?) is released. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |