Internet Explorer Beta 1 is now available for download.  For the first time ever, Microsoft's IE passes the Acid Test, a test designed to check web standards compliance in browsers.

I noticed several days ago when I had downloaded a file that it didn't show up on my desktop where I had saved it.  I thought I maybe inadvertently saved it somewhere else, so I proceeded to download again, selected the Desktop as the save to location, and clicked Save.

"Do you want to overwrite the file?"  I thought that was weird.  It's there, but I can't see it.  I went back to my desktop, hit F5 and ... BAM!  It appeared.

So, I did a little searching and found that there is a Vista update for this.  Knowledge Base Article 932406 "The Windows desktop may stop updating correctly after a Windows Vista-based computer has been running for an extended period of time" appeared.

Sure, I run my computer for extended periods of time, and my icons are AWOL.  It seems to fit my scenario.  So I downloaded it and installed.  We'll see how things go after the reboot.

Here's the link to the knowledge base article.

While writing this, I was listening to "Don't Dream It's Over" by Sixpence None the Richer

I first introduced this issue in a previous post.  It turns out that this problem occurs if a network hardware device, such as a router, does not support TCP Window Scaling. TCP Window Scaling is a new Windows Vista feature. 

The TCP window scale option is an option to increase the TCP congestion window size above its maximum value of 65,536 bytes.

I also have found that this can resolve problems like slow file copy operations in Vista as well as momentary loss of Internet connectivity.

Here are a couple of knowledge base articles from Microsoft:

• "It takes a very long time to download an e-mail message from a POP3 server in Outlook 2007"
• "Network connectivity may fail when you try to use Windows Vista behind a firewall device"

I have one Windows Server 2003 box in my environment that connects fine through RDP, but once I start clicking around in the RDP session, the response time is extremely slow even though the processor and memory usage is very low.

I'm not sure why one particular server would cause this problem, but I did some searching today and found in one of the forums which appears to be my solution.

From a command prompt, type:

netsh interface tcp set global autotuninglevel=disabled

This disables the autotuning parameter, which by the way, I have no idea what it does.  More research on that to come.