Adobe CS 5 Error 16 - uninstall and reinstall adobe product

Just came across this today on a staff machine. When they tried to use indesign it would crash almost immediately. I then logged in under a local account and tried to use any of the Adobe Creative Suite products, all of which showed this error straight away.

I rebooted, reseting the PRAM and running /sbin/fsck -yf. No changes were made to the operating system and Adobe CS 5 still came up with this error, so the problem wasn't here.

I read up on it and it looked like it has something to do with licensing. I finally logged in as Root and tried all the Adobe products, and IT WORKED!

After running this it worked on all local logins.

Coincidentally, when the staff member logged in and ran indesign, it crashed straight away (no error). After this the error 16 occurred on all logins!! So it was something with her account which much change something somewhere. I shall look into this!

MacBook Pro 17" fsck error EXITED WITH SIGNAL 8

Rob brought in his 17" MacBook which wouldn't get past the white screen with a gray apple and spinning dotty thing. I tried resetting the PR RAM. Next I tried single user mode with /sbin/fsck -yf. Results as shown:

Rebuilding B-Tree
could not repair volume
/dev/rdisk1s2 (hfs) EXITED WITH SIGNAL 8

Looked this up and found quite a few people with MacBook Pro's having the same error, looked to be related just with the file system and probably not a hard drive fault (hopefully). As Rob needed stuff off the HD I found only one command which might fix it, found it here:

1. Boot off the OS X CD (reboot, hold C while booting).
2. The installer will load up, go to Utilities in the menu and run Terminal.
3. Type df and look for the drive that has your Mac system mounted---you'll have to unmount this. On my MacBook Pro, it was /dev/disk0s2.
4. Type umount /dev/disk0s2, replacing disk0s2 with whatever disk your OS lives on.
5. Type fsck_hfs -r /dev/disk0s2. If you umounted the wrong thing, it will complain that you can't repair a mounted drive. Go back and umount the right thing and repeat this step.

I found netbooting to a deploy studio image had the same results as using the install disk. Coinsidence or not it, it was disk0s2 that was the OS X partition.

Anyway, it came up with another error, saying volume could not be repaired. I put it in target disk mode and mounted it on another MacBook Pro. It came up saying that there are serious issues with the volume which cannot be repaired, it is only being mounted to retrieve files which should be backed up immediately.

I used Migration Assistant to get the user account across, and copied other erroneous files. I re-partitioned and re-imaged the macbook pro and all is well.