Toluu

UX Evangelist

...all Microsoft, all the time.

Windows 7 M3 Build 6801 Screenshots!October 8

Keeping it "short 'n sweet," WinFuture has posted some screenshots of build 6801. Check out the image below with the spiffy new wallpaper, then go visit WinFuture via the reference link below the screenshot to see the rest of them!

Reference: WinFuture.de

-Stephen

The United States of America LOVES Windows 7 Builds!September 29

Mike Tyson vs. Evander Holyfield? Psh.

Michael Jordan vs. Larry Bird? Puh-leeeease.

Kimbo Slice vs. Ken Shamrock? SMALL POTATOES!

Dated 9-18-08, a court document I found residing on Microsoft's servers has a page 1 title that I would pay to see (cue Darth Vader music):

SUNDAY, SUNDAY, SUNDAYYYYY! IT'S US VS. MS! BEEEE THEEERRRREE!!!

If you want to know about the case (it looks fairly boring unless you're developing a product for Windows that will go head-to-head against Microsoft's bundled applications), download the document via the reference link at the end of this post. The title of this post was meant to reflect the following excerpt cut 'n pasted from page 5 of said document into MS Paint and saved as a PNG:

See? The USA loves Windows 7 builds! (Anyone know if the TC is looking to hire? Muahaha...) This completely meaningless and random post has been brought to you by a half-asleep Stephen.

Reference: 09-18-08JointStatusReport.pdf

-Stephen

Ready to Start Developing for Windows 7? Take Note...September 29

While the information floodgates certainly haven't been opened on Windows 7 by Microsoft yet, it seems they're allowing for at least a trickle. In addition to my posts regarding the updated WSPP documentation to include Windows 7 and Microsoft's Update Catalog listing drivers available for Windows 7, Microsoft appears to be adding Windows 7 content to the MSDN Library. The fact that Microsoft seems to be slowly but surely allowing information to seep through is exciting but I've already noticed something that may be of particular interest to developers.

As written in the "requirements" section on the "GetUrlCacheConfigInfo Function" page (which I link to as a reference at the end of this post):

It appears that anyone who is familiar with the Winineti.h header in the GetUrlCacheConfigInfo Function will need to make a slight change to their code in Windows 7 Client and Server. While that certainly isn't a big deal in and of itself, it looks like Microsoft is hard at work with changing things up for developers (by natural process of development, of course; not intentionally to just change things for developer

From Windows 7 Server to Windows 7 Server (You read that right...)September 28

Being a firm believer of following through and in an effort to once and for all clear the air with the whole "Windows 7 Server was always planned to be Windows Server 2008 R2," I've decided to cook up a timeline of screenshots in chronological order from presentations found right on Microsoft's servers. This basically shows the shift in timing where Windows 7 Server went from being planned as a major release to an update release (or R2, if you will). A few of these shots are new and a couple of them are already being used in a couple of previous Windows 7 Server posts of mine. If you're a fairly new reader and haven't seen those previous posts, then get up out of your chair, stand in it, and (very carefully) proceed to jump up 'n down for joy while saying, "sinOFsky!" as if you've sneezed until someone says "gesundheit!" and asks you why you're jumping up 'n down. Show them my site and tell them to spread the word using the exact same method above. hehehe. Anyway, check it out:

What Was: Windows Server 2008 (Codename Longhorn Server) -> Windows Server 2008 R2 (Codename Longhorn Server R2) -> Codename Windows Blackcomb Server (Blackcomb became Vienna and Vienna became 7, so it was thought Windows 7 Server would indeed be what was to be Windows Blackcomb Server)

What Is: Windows Server 2008 (Codename Longhorn Server) -> Windows Server 2008 R2 (Codename: Windows 7 Server) -> Codename Windows 8 Server

2004 - 2005 (Wind

Windows 7 Client and Server: New and Modified Protocols for Beta 1September 28

Cutting straight to the point here (my oven's preheating in preparation for corn dogs... mmm... corn dogs...), a recently updated version (dated August 19, 2008) of Microsoft's WSPP (Workgroup Server Protocol Program) documentation contains information regarding new and modified protocols both in Windows 7 Client and Windows 7 Server. As noted in the following screenshot from said documentation, these protocols will be present in the Beta 1 release of Windows 7:

(...Time to put the corn dogs in the oven... mmm... corn dogs... brb...)

Okay, back. Now, unless you're in the business of security or a reverse engineer or developer, most of this stuff will go over your head. If you ARE, you may find all of this information quite interesting. There are few new protocols on this list but a ton are modified up to this point... so many, in fact, that I was going to list them here, but I'm waiting for corn dogs and don't have the patience to go through the whole list. Speaking of that, I'll be back to finish writing this in a little bit... mmm... corn dogs...

Alright, I'm back again (I heart corn dogs). Basically, there's a document that tells you what's updated, what isn't, which versions of Windows they work for, etc. For everything, there is a corresponding label which allows you to go