*Words of Wisdom From The Elder

There are very few pieces of software that I hate to install.  QuickTime from Apple is at the top of the list.  I can’t honestly think of a single good thing to say about QuickTime.  But no matter how much I dislike having yet another tray icon and getting annoyed by software updates I had to install QuickTime.  At least until Windows 7! 

The camera I purchased back last year only made movies in .MOV format and for me it was a major drawback of the camera.  So much so I rarely found myself using it and instead using my Canon camera which takes native .AVI movies. 

This morning I discovered my QuickTime worries were officially over since Windows 7 supports QuickTime movies natively with Windows Media Player.  The announcement to support .MOV files was buried deep within the Windows 7 blog entry back in February (I looked this up because I missed it myself). 

Improved playback support for video content from digital camcorders and cameras

Customers loved the increased range of formats natively supported by the Windows 7 Beta, but noticed areas where they wanted broader support.  For example, one was unable to seek to a specific spot in the video in Windows Media Player or Windows Media Center for AVCHD content that was imported from a digital camcorder. We’ve addressed this.  Also, while the support for video from some digital cameras worked great, we also got feedback about supporting a broader set of devices out of the box.  We’ve since added support for Windows Media Player to natively support the .MOV files used to capture video for many common digital cameras.

This morning my trophy wife came into the office asking me to look at the movies she recorded at school yesterday.  I put the drive into my computer and copied the nearly 2GB’s of files to the computer.  After the first one finished copying I double clicked the file and even though the icon showed Windows Media Player I didn’t notice.  Then Windows Media Player started and too my surprise started playing a QuickTime file. 

As soon as I realized what was happening I paused the video and had a moment of silence.  It’s little gems of features like this that make you realize why so many people are going to love Windows 7. 

The best part?  Media Player plays QuickTime movies BETTER than QuickTime.  Movies start instantly and use less CPU than QuickTime.  Plus you get a native supported Windows application that takes advantage of other Windows 7 features (previews).    Here’s a sample video playing in Media Player that I took right before Hurricane Gustav hit this past year. 

YARTIW7
Yet Another Reason to Install Windows 7

Now that we have .MOV support native in Windows 7, my only other request is for Windows Live Movie Maker to support .MOV files. 

I thought I had everything tested after my recently Windows 7 RC upgrade this weekend and was ready for work this morning.  One thing I didn’t actually test was getting my work development VM on the Internet or VPN.  Turns out I had a problem with the network drivers in VMWare.

Here’s the lovely error I got when I tried to enable the network card on the VM.

“The virtual network drivers on the host are incompatible with the installed VMWare application. Expected version 5. Please reinstall the product. Virtual device Ethernet0 will start disconnected.”

This error was confusing since I didn’t have version 5 installed.  I’ll spare you the war story I went through to fix this and the countless reboots.  Here’s the end to the means.  I downloaded VMware and told it to “Repair” the installation and then rebooted. 

Someone else had the same problem after a Vista to Windows 7 upgrade.  I tried the fixes listed in the thread below but they didn’t work for me.

http://communities.vmware.com/thread/197009

Looking at the Network settings in Windows before and after the repair of VMware these two adapters were missing after the upgrade and then added back in during the repair.

All is well and good now. 

Glad you asked.  I finally got around to installing Windows 7 RC this morning.  The only hardware related problem I had during my upgrade was my Microsoft VX-6000 LifeCam.  When I ran the compatibility check during the upgrade Window 7 told me to uninstall the software for the LifeCam.  I stopped the upgrade and uninstalled the LifeCam software and then restarted the upgrade.  After the upgrade I was wondering how much of a pain it was going to be to get the camera working again. 

The first thing I did was open Devices and Printers.  Notice the new icons?  Fancy huh?

The LifeCam VX-600 is listed as having a problem.  I right clicked the icon and pressed troubleshoot.

The system then runs through a series of checks to detect the problem.

Then it came back with a solution.  Brilliant!

I of course clicked on “Apply this fix” and waited.

Whoops, my problem is NOT fixed.  Now what?

The reason it couldn’t be fixed is the camera requires software + a driver.  Turns out to fix this was simple.  There are updated versions of the LifeCam software that work with Windows 7.  Downloads for this and other Windows 7 related software can be found at http://www.microsoft.com/hardware/windows7/support.mspx. 

After a quick download and update of the new software everything is working. 

I’ve been running Windows 7 in virtual machines for awhile and on an older notebook.  This is the first time I’ve had it on the metal on my main workstation.  I have to say I’m pleased with being able to A) run x64 with no issues and B) open the device manager after the upgrade and see no known hardware problems.

I can say I didn’t have the same experience with Vista.  As more things unfold I’ll try to keep blogging if I run into issues or other things.  So far, so good.

I recently built a new machine and when I built it I installed Windows Vista x64.  Windows 7 RC came out this past week and I wanted to install the RC release on my new machine but like everyone else I didn’t want to take the risk installing it only to have a hardware configuration problem.  Not only that but I’d have to reload the whole machine when Windows 7 RTM (release to manufacturer) came out.  But there is hope! 

For starters a new tool was released called the Windows 7 Upgrade Advisor that checks to see if a system is ready for Windows 7.  And then for those of us that have Home Server, upgrading and playing with the Windows 7 RC becomes a no brainer.  Here’s how.

Upgrade Advisor

Install the 6MB MSI file after you download it and press the start check button.

A few minutes will go by (depending on speed of your machine) presenting you with the ever popular green bar streaming from left to right.

The elapsed time on my machine was about 20 seconds or maybe a little longer, maybe 30.  Here’s my results:

Apparently I can upgrade but will have to download some newer versions of Live tools.  Not a big deal.  Upgrade instructions can be found here by the way.

I was curious about the “Passed 4 other system requirements”so here is what the “See all system requirements” looks like.

The good news is I can upgrade with confidence.  Now, how do I upgrade and then upgrade again when the real version comes out?  Answer: Home Server.

Using Home Server For Windows 7 Upgrade, Restore and then Upgrade

If you are like me and have Windows Home Server and want to upgrade your machine I say go for it!  Don’t even hesitate.  Why?  Because Home Server has your back.  Here’s what I did this morning to prepare for my Windows 7 RC upgrade this afternoon.

The first thing I did was go into the home server console and rename the last backup Home Server took of my machine.  After renaming it I told Home Server to “Keep this backup”.

Now I’m ready to install Windows 7 RC because I have a full backup of my current Vista x64 install.

What Happens when Windows 7 RTMs?

Simple.  I grab the restore CD for Home Server and restore the machine back to the “Pre-Windows 7 RC Backup” listed above.  After that is done, I’ll take the Windows 7 RTM disk and do another upgrade of the machine running Vista x64 again to Windows 7 (which is fully supported and has been fully tested). 

It may seem a little weird but trust me I don’t want to spend 2 days reloading all the software on my computer and I REALLY want to play with Windows 7 RC on the metal instead of a VM.  The way I figure it, I should be able to have Windows 7 RTM installed and working in about an 2 hours after it comes out.  And the best thing is I won’t miss a beat in productivity.

Don’t have Windows Home Server?  No?  Then I officially deduct 100 geek points from you if you are a reader of this blog.  There are tons of uses for Home Server.  Don’t walk, but run to the store and buy one.  Especially if you are a developer. 

I’ll see you on the other side running Windows 7 RC.

At work we include XSD schemas in our Framework to allow developers to configure their web.config or app.config files and get Intellisense.   This helps to make sure they don’t make mistakes when they are configuring logging or other options for the framework (the same way the .Net Framework provides Intellisense for config files).  The problem is developers had to go to the XML menu of Visual Studio and add the schema by hand each time.  In other words, kind of a pain.  If you’ve never done this before it looks something like this:

Each time Visual Studio is opened or closed the schemas that are added have to be re-added.  I wanted to find a fix, not only for me, but the developers using our Framework as well. 

My first thought was to copy our framework schemas out to c:\program files\Microsoft Visual Studio 9.0\xml\Schemas.  But while I was looking around I found a catalog.xml file within that folder.  Interesting I thought.  I opened it up and went AHA here is the answer.

The file looks like this:

   1: <SchemaCatalog xmlns="http://schemas.microsoft.com/xsd/catalog">

   2:   <Schema href="%InstallRoot%/Common7/IDE/Policy/Schemas/TDLSchema.xsd" 

   3:           targetNamespace="http://www.microsoft.com/schema/EnterpriseTemplates/TDLSchema"/>

   4:   <Schema href="%InstallRoot%/Common7/IDE/Policy/Schemas/Policy.xsd" 

   5:           targetNamespace="http://schemas.microsoft.com/VSPolicy/PDLSchema"/>

   6:   <Schema href="%InstallRoot%/xml/schemas/%LCID%/snippetformat.xsd" 

   7:           targetNamespace="http://schemas.microsoft.com/VisualStudio/2005/CodeSnippet"/>

   8:   <Schema href="%InstallRoot%/xml/schemas/%LCID%/vstemplate.xsd"

   9:           targetNamespace="http://schemas.microsoft.com/developer/vstemplate/2005"/>

  10:   <Schema href="%InstallRoot%/xml/schemas/%LCID%/Microsoft.Build.xsd"

  11:           targetNamespace="http://schemas.microsoft.com/developer/msbuild/2003"/>

  12:   <Schema href="%InstallRoot%/xml/schemas/%LCID%/vscontent.xsd"

  13:           targetNamespace="http://schemas.microsoft.com/developer/vscontent/2005"/>

  14:   <Schema href="%InstallRoot%/xml/schemas/%LCID%/customUI.xsd"

  15:           targetNamespace="http://schemas.microsoft.com/office/2006/01/customui" />

  16:   <Schema href="%InstallRoot%/common7/packages/SDM/Schema/SystemDefinitionModel.xsd" 

  17:           targetNamespace="http://schemas.microsoft.com/SystemDefinitionModel/2005/1" /> 

  18:   <Association extension="config" schema="%InstallRoot%/xml/schemas/dotNetConfig20.xsd" condition="%TargetFrameworkVersion% = 2.0" />

  19:   <Association extension="config" schema="%InstallRoot%/xml/schemas/dotNetConfig30.xsd" condition="%TargetFrameworkVersion% = 3.0" />

  20:   <Association extension="config" schema="%InstallRoot%/xml/schemas/dotNetConfig30.xsd" condition="%TargetFrameworkVersion% = 3.0" />

  21: </SchemaCatalog>

I copied one of the Association tags which has the extension=”config” attribute in it and made my own pointing to the location of our XSD file.  Having the ability to set the minimal version is nice as well.  I restarted Visual Studio and BAM, immediate Intellisense in my config file!

If you have been looking for a way to have XSD’s provide you Intellisense for your config files automatically, there you go.  Hope it helps.