Sorry for the all-caps, but the thread's getting cluttered.

I've talked all day about this theory I was working on, and I've just uploaded a new version of the site (to test.msmphotography.com) that embodies the changes that might make it work (if I'm right).

At least with IE7. We've established so far that FireFox is just fine, and IE6 has some other problems...but IE7's the top priority for now. BTW, IE6 is looking better too, and I may get that one patched up soon. Last but not least, Apple Safari.

All you victims of IE7, I'd appreciate it if you'd take one more shot at it.

If you have problems, or even if you don't (as I'll explain in a minute), I'd like you to try that thing about appending "?debugmode=true" to display debugging messages. This time, I'd like to locate two messages near the top of the list, something like this:

XML/IE.GetAX: hit, DocCID='Msxml2.DOMDocument.3.0', ReqCID='MSXML2.XMLHTTP.3.0', XSLTID='MSXML2.XSLTemplate.3.0'

XML/IE.GetAX: Native XMLHttpRequest? yes

The first one has a little bold text to make it easier to find. What it's for is to tell me what version of Microsoft's XML software is installed on your computer (first line), and second, whether a component that's supposed to be native to IE7 is really there (or possibly deliberately disabled by your IT Guys).

I'm interested in tracking the software version even if you don't have a problem because I think that the version is the problem, and I'd like to get a feel for who's installed where. It's the sort of thing only Microsoft could do: The latest version of their XML is 6, yet the built-in component in IE7 seems to be based around version 3. Trying to mix-n-match 3 with 6 seems to be the source of the error. Go figure.

Aye chihuaha...I sure hope this fixes it!