foxyproxy

I had been using ff2 and foxyproxy with no problem. After the ubuntu upgrade to ff3 I'm getting problems.
Here is my basic setup: ubuntu8.04 / winxpsp2 dual boot. I have ff on both OSes and I have them both configured to read my user profile from my default windows directory. Firefox and all my addons were working fine before. Now, I clean installed ff3b5 on both OSes and set them both up again to use the same directory. All my other addons seem to be ok with this setup except for foxyproxy which gives this error upon starting ff in ubuntu:

Error writing settings file: [xpconnect wrapped nsIFile]. Ensure the path exists and that Firefox has write access, then restart Firefox. FoxyProxy will not function until then.

Note, when I was using ff3 in windows, foxyproxy was working perfectly well.

I'm not sure if this is because foxyproxy needs access to the registry or what is going on that wasn't a problem before. Foxyproxy still appears in the "Tools" menu but not in the statusbar. It appears as "Disabled". When I try to switch it from "Disabled" I get the following message (about 4 times, plus the same error given on startup):

Error writing settings file: file:///C:/Documents%20and%20Settings/mrg/Application%20Data/Mozilla/Fir.... Ensure the path exists and that Firefox has write access, then restart Firefox. FoxyProxy will not function until then.

I guess it's because that path is hardcoded into foxyproxy... Other plugins probably are ok bc they only write to the user's foxyproxy profile folder. I'm not sure what the fix for this would be, as I'm assuming many of us use ff on both OSes in (increasingly more common) dual-boot setups.

Possible solutions? Maybe a simple workaround via file or folder links. Maybe foxyproxy allows you to specify where this config file should be and let you specify a backup location to check if the first one fails. Maybe simply just putting the config file back in the firefox user profile directory like before (i'm assuming it was there before since ff didn't have this problem before). Finally, maybe I could try mounting my windows c partition as /C/ under linux, but that seems a little extreme, time consuming (bc I'm no expert), and not sure if it would solve the problem.

Other than this, thanks for the help and for a great add-on :) Please provide a fix for this regression when possible or let me know if there is something I can do on my end to fix it.

Thanks :)