Working locally (both IE & FF), only working in FF on live server

I just got my personal website (link) updated with some Atlas enabled stuff, right there on the front page you can do "Show Different Image" in the top left or use the Calendar's left and right arrows to go through the months without postback.... but... as the subject says

Running on my laptop here: Atlas CTP installed, using studio's built in web server:
- All functions work in both browsers (IE 6, FF 1.5.0.4)

Up on my web server: Atlas CTP installed, IIS 6.0
- FF works 100%, but IE spews javascript errors on page load

And it's weird, one time i get one error (and this is the common one, btw that line # shown doesn't have anything!):

Other times, IE is totally confused! (i do not have that many lines in that page needless to say)

I've already tried seeing what's going on with Fiddler, not sure what i am exactly looking for, but all looks well in that tools... and just for good measure i uninstalled Atlas on my server and reinstalled it, that didn't help things either

Any ideas? (link again)

So i got by this problem by installing theMicrosoft Script Debugger and seeing what IE was whining about and it was the javascript for Google Analytics causing the above problems (although it makes *no* sense why it worked 100% in FF)

So now I have the "css refresh" problem where IE/Atlas is working, but the whole page's CSS refreshes, i swear i saw a blog post by someone at Microsoft to fix it... gotta track that down

would like a detailed explanation of dynamic populate page method

hey everyone

could someone explain to me what the bonuses are of using dynamic populate page method
(and therefore stuff like dynamiccontrolID and dynamicservicemethod)

as opposed to just executing a sqlcommand inside an eventhandler
when the user clicks a linkbutton

i know theres probably a really good reason
its just pretty muddy to me right now

thanks

Dynamic populate happens via a web service call and does not incur the overhead of a postback with full page lifecycle. The downside is that you can't create new server controls via a dynamic populate that are accessible in the underlying page.

DynamicServicePath: path to the web service