Stand-alone updates, CS5 plug-in does not

Sorry if this this has been covered before...

I've tried downloading the latest update to FF2 ver .009. The funny thing is, the stand-alone version updates and runs fine. However when I try to run FF2 through the filters window of Photoshop CS5 it returns an error message and if I ignore it, FF2 opens without any filters. If I check the "about" info while it's running it lists the version as .008. I can't quite figure out what if anything I'm doing wrong. I'm on a Macbook Pro (intel) OS 10.6.5. I've even gone so far as to uninstall and try to reinstall FF2 restarting CS5 FF2 and the computer itself numerous times with no luck.

Thanks for any help or advice

Removed the manually placed files and attempted to re-install FF2 again. The stand-alone program runs fine but when I attempt to run FF2 from photoshop I'm greeted with the endless spinning "beach-ball" CS5 will not respond and I have to force quit the program. When I check the plug-ins>Filters folder of CS5 the alias for the plug in that it points to is the Filter Forge 2 universal x86.plugin Is this the correct file? In addition my process for "un-installing" FF2 has been to manually delete the FF2 folder in the applications folder and manually delete the alias the plug-in places inside of CS5. If there is a different process I would be appreciative if it could be explained to me. I could not find any answers to this question in a search of the forum.

Similar. I have FF2 pro. When run from inside CS5 as a plug-in it will not "switch" me over to FF2 from CS5. However, if I navigate to FF2 in the dock and click it's icon FF2 appears to run perfectly. When I choose to apply the filter the changes are carried over and executed in CS5. So, much similar to Ellie's issue, I need to physically navigate to FF2 and CS5 just has the appearance of "not responding" thank you for pointing that out to me GMM and allowing me to try some things I hadn't considered at so late of an hour. Next time I will attempt a more diligent search of the forums before posting my question. It appears as if tech support is aware of this issue and I will watch for the fix in the near future.