Eric Dannewitz / 08.1.31 / 4:41 PM wrote: >Funny, cause a lot of companies recommend doing this. In fact, M-Audio >had be do this with some driver issues I had in 10.4.11, and it >cleared up the problem.
Well, this is how it goes. If the vender used Apple installer, it will leave a Receipt package, which is a database of install activity. If something goes wrong permission wise, DiskUtil looks up on the database and correct the errors to where files were installed originally. OS components has the same skill sets. If a vendor used bad installer such as legacy VISEX, the installer itself changes permissions of OS components around. This is why we always had to run repair permission before and after you run installer especially if you detect the installer was VISEX. Finale used to use VISEX. In my vague memory, they don't use it anymore. Over the time, VISEX has improved, while many developers also abandoned VISEX, and Tiger has improved to prevent from VISEX to change permissions around. I wonder what M-Audio installer messed your OSX up. If M-Audio installed just a driver, I am not sure where the installer changed the permission since driver is only kext file sudo cp to Lib. Are you sure companies recommending repair permission isn't pre-Tiger? -- - Hiro Hiroaki Honshuku, A-NO-NE Music, Boston, MA <http://a-no-ne.com> <http://anonemusic.com> _______________________________________________ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
