[ note : I removed some messages from this thread, because the forum doesn't like long threads, and because while useful suggestions they were going down a dead end.]
>> If it helps, I've attached a small png that shows the errors that Firebug kicks out.
what you showed were warnings, not errors. Warnings are fairly common (usually complaining about browser-specific stuff, as these were) and can be turned off in Firebug.
Back to your original problem though - this is one of those cases where firebug is not as clever as it could be. On the up side we are not limited to firebug, so there are other approaches to this.
the error you got is quite "common" but what it's really complaining about is the line eval(s); - and specifically it's complaining that some script that was passed back to the browser has stopped while executing.
In this situation I usually run in Chrome browser, F12 for developer tools, and then look at the console there. It often points to a different point on the page, or in the code.
If all else fails either send me an example, or put it online where I can access the effect from here.
Cheers
Bruce