Mac - Installer creates bad file permissions?

After installing Filter Forge 2 Beta 2.002 on MacOSX 10.6.2, I did not have permissions to access the "Filter Forge 2" folder in Applications.

I fixed this by using "Get Info" and then editing the sharing and permissions. giving myself read-write access, (Read access is probably enough for here?)

Next I copied over my Filter Forge 1 library from CD to /Users/MyUserName/Library/Application Support

After doing that, FilterForge would exit without explanation immediately after pressing the Try button. (No FilterForge process visible anywhere, nor any CPU usage).

Eventually I noticed that nothing in the system had access to read /Users/MyUserName/Library/Application Support/Filter Forge 2/System

Giving myself read-write access to this directory (and all enclosed items) made everything happy -- starting FilterForge again caused it to have a big long think about all the filters it found in the library, and then came up happy and well.

Subsequent runs of FilterForge come up fast as expected, so it's just a permissions on installation issue (and a lack of error handling when the permissions are bad).

Haven't had a chance to try out any of the cool new stuff yet, just wanted to document the above while it was still fresh in my head.

I downloaded and installed FF2 fresh today.

I'd cut&paste the version info but it won't let me
Doesn't seem worth a screen shot

Here's a retype:

Build: Filter Forge universal 2.002.15268.19170 Release-10.5, December 18, 2009, 13:44


I've no idea what went wrong with the install, or why, but here's an experiment for you to try: remove permission to your entire /Application Support/Filter Forge 2 directory and see what happens when you run Filter Forge!

Hmm, rereading my post I'm not sure I was totally clear: I resolved my problems by adding permissions, and am now happily using Filter Forge 2.002 -- seems to be working fine!