Tonight I set about trying to get my IIS7 server to serve files with the application/x-javascript content type as compressed. After a bunch of testing, back and forth, ultimately this is what worked for me in my applicationHost.config file:

<dynamicTypes>  
    <add mimeType="text/*" enabled="true" />

    <add mimeType="message/*" enabled="true" />

    <add mimeType="application/x-javascript; charset=utf-8" enabled="true" />

    <add mimeType="application/x-javascript" enabled="true" />

    <add mimeType="*/*" enabled="false" />

</dynamicTypes>

You have to be specific it seems, specifying the charset. And it needs to go before the regular x-javascript entry. Go figure. Hopefully this saves someone else some headaches.

Also, while you’re tinkering with applicationHost.config, you might as well change this:

<serverRuntime />

Into this:

<serverRuntime frequentHitThreshold="1" />

That specifies that IIS7 should compress/cache any static content the first time it’s requested. Otherwise, it defaults to “2”, which means it will only cache the compressed content if it’s requested at least 2 times within 10 minutes.

I keep getting this weird error after my Windows session has been logged in for a long time. It happens if I try to run any Office program (Excel, Outlook, Word, etc.) or if I try to run Windows Media Player.

Logging off and logging back in fixes the problem, but that’s hardly ideal.

I found a forum post regarding the issue, and it seems that Microsoft is indeed aware of the issue:

In the meantime: You don't need to reboot, just log off and log back on. It's a per-user issue. That will clear it up if it's the same issue.  I realize it can be a pain and I'm not trying to minimze the issue at all, but the workaround is simpler/quicker than a full reboot.

It hits different people in different time frames. It depends on how many apps you are running and how often you have loaded/unloaded them.

I appologize that it takes this long, but we'd rather not give you an update that had other problems/regressions, so we want to make sure it's fully tested, and that can take a few weeks in an environment as complex as this, as I'm sure you know. 

Reading further, it seems the fix is actually finally released, but won’t be forced upon users (via Windows Update) until July. If you’re having this problem, you can download KB952709 and fix it right now!

Since getting my console back after having it repaired, due to the red ring of death problem, I haven't played it much. I decided today to sit down and play Assassin's Creed, and about five minutes into it, my screen starts to look posterized. Basically, it looks like the colors are reduced. Think cheesy 80's music video special effects. Here's some shots:

Of course, if I go to XBox.com and look up my repair information, it says I'm out of warranty. Fantastic. A console I hardly play is broken yet again. I'm going to try to call and deal with their customer service people (in India.. ugh.) But I doubt I will be able to get them to fix this for free.

I haven't found any other information online about this problem. I can't be the only one, though.

Stuff I've tried:

- Changing from 1080p to 1080i, 720p, etc. -- no change.

- Jiggling the entire cable, in case there's a short.

- Unplugging/re-plugging in the video cable.

- Performing the "Reset Video Settings" trick per Microsoft's KB article.

How *$()@% frustrating is this? Microsoft really doesn't get it sometimes.

Update: According to users who replied to my XBox.com forum post, the problem appears to be that the GPU is either overheating, or beginning to break away from the motherboard. This is similar to what causes the "Red Ring of Death" errors, but not the same. I think I'm going to just have to bite the bullet and pay for repairs, even though this is clearly a design flaw, and not a problem I caused.

Xobni (inbox backwards) is an add-on for Outlook that seems to fill in all the missing spaces that Microsoft forgot about:

Looks pretty spiffy. I really want to get into the beta, and you probably do too if you use Outlook. Click this link to check it out:

I was trying to open a project from SourceSafe under the new Visual Studio 2008, and my list of SourceSafe servers was blank. After a few moments of frustration, I found a CTP (beta) release of a pack of fixes for SourceSafe, and Microsoft suggests you install it before using Visual SourceSafe 2005 in Visual Studio 2008.

http://www.microsoft.com/downloads/details.aspx?FamilyID=FAF41EDD-924D-449F-AEFC-9C86DD499720&displaylang=en

The CTP seems to have fixed my problem, as I can now open VSS2005 projects from VS2008.