> >placing their DLLs in the System folder. However, a work around to this
> >problem is to put the DLL in question (the one that the newly installed
> >application wants to place in the System folder, overwriting the current
> >DLL in that folder) in the application's own folder. Then create a zero
> >byte file that is named the same as the application, plus an extension of
> >.local. For instance, if the application was called crankyapp.exe, you
>
A similar trick works on the Mac when different programs insist on their own
version of a dynamically linked library. Put the new (or most commonly
used) version of the DLL in the system extension folder and place the other
DLL in the same folder as the application that requires the incompatible
DLL. On the Mac there is no need for the *.local file.
