HighRoad Mac OS

Open source implementation called OpenBFS is used by the Haiku operating system. Btrfs – is a copy-on-write file system for Linux announced by Oracle in 2007 and published under the GNU General Public License (GPL). CFS – The Cluster File System from Veritas, a Symantec company. It is the parallel access version of VxFS. Open source implementation called OpenBFS is used by the Haiku operating system. Btrfs – is a copy-on-write file system for Linux announced by Oracle in 2007 and published under the GNU General Public License (GPL). CFS – The Cluster File System from Veritas, a Symantec company. It is the parallel access version of VxFS.

1. Highroad Mac Os X
2. Mac Os Catalina
3. High Road Mac Os X
4. Highroad Mac Os Catalina

Highroad Mac Os X

Yesterday I got to experience something new today in Adobe Illustrator CC (2014). It was an error 16 configuration error. Sounds redundant? It might be. But it kept me from opening my copy of Illustrator on the iMac.

The Roots of the Problem

This started out with an article that I read on MacWorld.com on how a white-hat hacker from Sweden had found a major vulnerability in the 'Yosemite' version of Mac OS X. Somehow, you can manipulate the OS into creating a shell account on a with root privileges. The article doesn't say if this can be done remotely or not. I'm personally leaning towards the hacker having to be physically on the Mac to do this. That's the way most Mac exploits work.

One of the ways to prevent this exploit is to create a user account without administrator privileges and use it instead of the default admin account. I'm pretty lazy at times, and I hate having to make my computing experience more difficult than it needs to be. Plus I constantly back up my Mac. That said, I decided to take the 'high road' and created a new admin account for installing software and modifying my system. Then I removed my current account's administrative privileges. Now I'm finally safe from hackers and whatever. (I guess.)

That morning, I decided to work on an ebook cover in Illustrator. Clicked its icon in the dock, and before I even got a glimpse of AI's start screen or interface, I received this fun little error message: Slime dad mac os.

I just assumed that some settings or preference file was corrupt, and that this was AI's way of vomiting it up. It does that ever so often. Then I'll have to hold down Control–Option–Command to get it working again.

'I'll just reboot my machine, and I'll be back to work.' Well, I was wrong. The other funny thing was that my Creative Cloud menu was displaying 'Free Trial' buttons next to my copy of AI. Seeing that began to make me a little paranoid. I began to wonder if my credit card blasted through its limit or if it was simply rejected by Adobe for whatever reason. I brought up my Abode CC account, and everything was hunky-dory. No issues with payment.

Per the screenshot above, I took Adobe's advice and uninstalled then reinstalled Illustrator. That solved nothing. Then I researched the issue on Google and Bing. I had found an Adobe help page that claims that you need to adjust the permissions to specific folders. But the permissions to both my SLStore folder and Adobe PCD folder in my system had already been set correctly.

Then I had to think back to the things that I had done recently on this computer. The reason why I developed this habit was due to my experiences with 'extension conflicts' back in Mac OS 9 and earlier versions. Extensions back in per-OS X operating systems were much like plugins in PhotoShop. Often times extensions had the tendency of conflicting with each other or with the system itself. This often caused all sorts of annoying problems or just simply brought down the system. I remembered that I had taken away the admin privileges from my current account. So I restored them and magically Illustrator worked like it should.

But It Wasn't Over Just Yet!

This morning, my copy of PhotoShop gave me the same grief. (Another freakin' Error 16 dialogue box.) I own a version from one of the older CS families. I'm not sure why that made a difference, but I had to get this resolved ASAP.

I had done some more research via Google this time. I found a thread on the Apple Support forums discussing this issue. Scroll down four boxes. A person named Nobby66 gave the suggestion to set all of the permissions to the Adobe PCD folder to Read & Write. Here are the steps:

Mac Os Catalina

1. Use the Finder to navigate to Library/Application Support/Adobe/Adobe PCD.
2. Then select the Adobe PCD folder and use the keystroke Command–I to Get Info on the folder.
3. Go to the Sharing & Permissions panel and click on the lock in the bottom-right-hand corner.
4. The Finder will ask for an administrator login and password. Enter that.
5. Click in the Privilege side of the panel and set every user to have Read & Write access. It should look like this below:
6. Click the Sprocket button, which resides next to the minus button along the bottom of the Sharing & Permissions panel. That will bring up a small menu, and you will select, 'Apply to enclosed items…' That will set the permissions for all files and folders within the Adobe PCD folder to what has been selected within the Sharing & Permissions panel.
7. You're done!

High Road Mac Os X

Are We Done Yet?

Highroad Mac Os Catalina

I think we are. I don't know if the same resolution will work in Windows. Adobe gives the same remedy for Windows users experiencing a Configuration Error 16. You may want to play around with either opening your Adobe app under an admin account and/or tweaking your permissions the same way I did under Mac OS X. For Windows users please take these suggestions with the proper caution. I have no idea if tweaking permissions will cause any issues in Windows.