It’s hard to find time in our busy schedules to just sit down and soak up a new technology, especially when we don’t have something shiny in our hands. Microsoft’s msdev training portal, however, has an entire suite of Windows Phone 7 videos that are all narrated by Nancy Strickland, who does a decent job at making these videos less sucky, and have a runtime of seven minutes max (totaling 2 hours of content). Of course, if you’d rather read boring documentation, be sure to check out the Programming Guide for Windows Phone 7 on MSDN.

Do you have any other tips on quickly absorbing Windows Phone 7? Do share.

Limestone in the traditional sense is a type of sedimentary rock, consisting of layers and layers of “schtuff” mushed together. This is perhaps why the word was chosen for Microsoft’s Office internal scaffolding. The software, which actually leaked under the radar back in Office 14 beta days, appears to have been developed for the purpose of testing each and every layer of the Office suite – ranging from the basics like text formatting to the more complex Ribbon and Backstage UIs. Judging by the screenshots, it’ll never be a consumer facing application or magically integrate anything with everything. It’s simply a fun dev. tool.

(This particular build of Office 14 (14.0.4302.1000) doesn’t uninstall properly, therefore I used an older Windows Vista virtual machine I had lying around for screenshot purposes.)

While swimming around the registry, looking for hidden settings to disable the now permanently enabled sequential message grouping, I stumbled upon a hardware “blocklist” at HKEY_CURRENT_USER\Software\Microsoft\Windows Live\UX\HwBlockList. After punching a few of the PCI-SIG registered DeviceId and VendorId pairs into a PCI database, it was clear this list was purely for blocking video cards.

But why?

A cursory analysis came up empty, so I took a different approach; I placed my ATI Radeon HD 5900’s hardware ID pair (vendor 1002, device 689C) into the registry location and restarted Windows Live Messenger. After firing it back up, it was immediately obvious what the list’s purpose was. All the UI elements were purely static and made no effort to wow me; all whizz-bang animation effects were disabled.

But why?

Resolving all the IDs in the list paints a damning picture. Dominating the list are NVIDIA’s GeForce FX-based cards, known for their god-awful DirectX 9 performance. (Remember the whole Valve and NVIDIA fight?) Intel also made the list with its equally horrible and buggy GMA 500 chipset but ATI was strangely missing from the list, due to lack of data no doubt.

Conclusion: Windows Live Messenger uses a list of known under-performing (read: crap) DirectX 9 video cards, to ensure a consistent and stable user experience. Case closed. If you have one of these cards, it’s really time to upgrade.

The list, as of August 19, 2010 (WLM Wave 4 Beta Build 15.4.3002.810), follows.

Thanks to the anonymous tipster who mailed in a more official logo and for indicating that the below poll is “pretty darn accurate” in terms of what’s being discussed internally.

Michael Pietroforte at 4sysops emailed me about a month ago, wanting to run a cross-technical-blog poll of sorts, garnering feedback to potentially help shape Windows 8. I agreed to participate, it sounded neat. I mean, it can’t hurt, right? Worst case, Microsoft simply ignores the whole thing.

Here’s how it works: Scroll down and follow the on-screen instructions. It’s pretty simple. At the conclusion of the poll, the results will be gathered from all the participating blogs – actually already done on the backend – and be published. If you have any questions regarding the definition of some poll items, don’t guess – simply refer to Michael’s post. (If Microsoft works on UAC, vice the bare-metal hypervisor, because of an errant vote… I will hurt you.)

Participating blogs: Demonic Talking Skull - markwilson.it - msigeek - Standalone Sysadmin - Teching It Easy: with Windows - The Experience Blog - The things that are better left unspoken - The Windows Club - WindowsPro - Within Windows (you are here) - 7tutorials – 4sysops

Back in May, I was invited out to the Microsoft campus to join Garrett Serack and a hand-selected crew of astronauts in the kick-start and development of CoApp. While we all have a fuzzy understanding of what CoApp is, it’s admittedly hard to explain to normal people. Thankfully, we don’t have to work at explaining anymore! We now we have an awesome video Garrett put together, using clean audio from his recent OSCON presentation. Warning: This isn’t your usual boring WinHEC video.

[See post to watch Flash video]

(I’ll be adding pseudo-streaming markers to hopefully let you skip around tomorrow.)

Microsoft Kinect, the motion sensing, wii-beating, game changing Xbox 360 add on, now has official pricing.

US = $149.99
UK = £129.99

It’s good to have pricing but it does seem we’re getting the short end of the stick here in the UK. The current conversion rate puts it around £90, which would far more palatable. I don’t see why it is so much more over here…almost 50%!

When I pre-ordered my Kinect a couple of weeks ago, Game told me they expected it to be less than £100 as Microsoft wanted to “make it as accessible as possible”…that sounded plausible but alas, clearly isn’t the case

In my opinion the Kinect should be positioned as a way to attract new Xbox owners, but I can’t see £300 being seen as that attractive…especially when a Wii costs £119.99!

Will I still pick up my pre-order? To be honest, yes…but I’ll be expecting even more from it now!