On February 20 Microsoft released a hotfix rollup package for Virtual PC 2007 SP1.
What's so cool about this is that it adds the long awaited support for resolutions higher then 1600x1200.

Virtual PC 2007 hotfix package, 32-bit versions

Download the 958162 package now.

Virtual PC 2007 hotfix package, 64-bit versions

• The Virtual PC 2007 support matrix is extended to include the following SKUs:
• Windows XP Home with Service Pack 2 (SP2)
• Windows XP Home with Service Pack 3 (SP3)
• Windows Vista Home with Service Pack1 (SP1)

These additional SKUs were not supported before this hotfix. These Home SKUs are currently supported in this hotfix rollup. Additionally, the following SKUs are supported as guest operating systems:

• Windows XP Home with Service Pack 2 (SP2)
• Windows XP Home with Service Pack 3 (SP3)

Improvement 2
This hotfix rollup includes following significant performance and stability improvements in virtual machine networking:
A virtual machine that uses a network in the Shared Networking (NAT) mode has severely low performance compared to a virtual machine that uses the Bridged Network mode. This hotfix rollup provides a marked improvement in virtual machine networking performance in Shared Networking (NAT) mode.
When using a bridged mode of networking, the guest will mirror the connection state of the host network adapter to which the guest adapter has been bound. When using Shared Networking (NAT), the guest network adapter will be disconnected only when all network adapters on the host are disconnected.
It takes a long time to copy multiple and large files to and from a virtual machine that is using the Shared Networking (NAT) mode. Additionally, this process sometimes results in stopping the network connection or stopping the copying process.
Auto detection of the http proxy works with Shared Networking (NAT) after you install this hotfix rollup.
This hotfix rollup sets the correct WINS address as part of the DHCP address assignment.

Improvement 3
The resolution is now extended to 2048x1920 (32bit). Virtual PC 2007 SP1 supported a screen resolution of up to 1600 x 1200.

This hotfix also fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

Issue 1
If a virtual machine window is closed while one of its child windows is active, the Virtual PC 2007 process crashes.

Issue 2
Some operating systems crash when they run in the virtual machine. When this happens, the host operating system may crash. This problem occurs when the guest operating system allocates the system memory in such a way that the virtual machine monitor component of virtual PC cannot find memory for its internal data structures. Under such circumstances, virtual machine monitor returns a fatal error exception to the guest operating system and prevents the crash on the host operating system.

Issue 3
Inconsistent behavior of Virtual PC 2007 occurs when you shut down a virtual machine that has the Undo disks option enabled. A dialog box may be displayed to ask you to decide what you want to do with your virtual hard disks when the close action is set to Automatically close without any message.

Issue 4
The virtual machine additions installation cannot start and shows the Windows Installer Help window. This problem occurs when the value of environment variable %temp% in the guest operating system includes a white-space.

The first plans for Mavention were made at the start of 2008. At that time we made the promise that we use the principle: ‘work hard, play hard´. One of the most important things that we already knew: `we will go on winter holiday as Mavention’.

Paul and Erik took the initiative and the first Snowvention became a fact. Thanks a lot guys! All the people of Mavention with their partners and children traveled to the snowy mountains of Fiesch in Switzerland. Snow was certainly present, loads of it. Fortunately also the sun was there and of course the drinks and laughs. We had a good mix of skiers and snowboarders. For some the first time on the slopes and for others the perfect opportunity to ski or board an extra weekend this year. After two great days of fun on the slopes it was time to return home.
 

The return trip turned into quite a challenge. Not only because it was a great weekend and everyone still rather wanted to stay longer. Our biggest challenge was that nearly all mountain roads from the village were blocked by heavy snowfall. It took us three extra hours to find a safe route to the Netherlands.

I think we can reminisce a fantastic weekend and if it´s up to me we will keep the winter holiday on the calendar each year.
 

I wanted to create a tailor made view of a list, using the first position in a calculated column to determine whether or not to place specific text in a cell. This calculated column A contains a status description of items in the list (1. Starting, 2. In Progress, ...).

In case an item is in phase 1 or 2, I wanted to show a specific text in the first cell. I used Frontpage 2003 to edit the page and I set the filter options using the standard dialog to A contains 1 Or A contains 2.

I succesfully tested the page in Frontpage, saved the page and found out that I got a nasty message:



All other pages kept working though. Just this page refused to serve right.

I checked the CAML code:

<dsp:Where xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp">

<dsp:Or>

<dsp:Contains>

<dsp:FieldRef Name="A"/>
<dsp:Value Type="xsd:string">1.</dsp:Value>

</dsp:Contains>

<dsp:Contains>

<dsp:FieldRef Name="A"/>
<dsp:Value Type="xsd:string">2.</dsp:Value>

</dsp:Contains>

</dsp:Or>

</dsp:Where>

And modified it to:
<dsp:Where xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp">

<dsp:Contains>

<dsp:FieldRef Name="A"/>
<dsp:Value Type="xsd:string">1.</dsp:Value>

</dsp:Contains>

</dsp:Where>
to see if the OR clause would be causing the problem. Unfortunately, still same error.

Now I tried:
<dsp:Where xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp">

<dsp:Eq>

<dsp:FieldRef Name="A"/>
<dsp:Value Type="xsd:string">1. Starting</dsp:Value>

</dsp:Eq>

</dsp:Where>

This one worked. Would it be the Contains clause?

I checked with some other field:
<dsp:Where xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp">

<dsp:Contains>

<dsp:FieldRef Name="ID"/>
<dsp:Value Type="xsd:string">56</dsp:Value>

</dsp:Contains>

</dsp:Where>
This one worked as well.

My conclusion is that you cannot use the Contains clause on a calculated column. Work around I used, was replacing Contains with Eq (Equals)

<dsp:Where xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp">

<dsp:Or>

<dsp:Eq>

<dsp:FieldRef Name="A"/>
<dsp:Value Type="xsd:string">1. Starting</dsp:Value>

</dsp:Eq>

<dsp:Eq>

<dsp:FieldRef Name="A"/>
<dsp:Value Type="xsd:string">2. In Progress</dsp:Value>

</dsp:Eq>

</dsp:Or>

</dsp:Where>

If you run Office 2007 on Vista you might have the annoying problem that Office alway's prompts for a login when opening a document from a SharePoint site even when you are already logged on.
 
This is a known issue and there is a hotfix available for this problem. This hotfix is included in Windows Vista Service Pack 1. However, you must still configure the AuthForwardServerList registry entry.

This is what you have to do:

1. Click Start, type regedit in the Start Search box, and then press ENTER.
2. Locate and then click the following registry subkey:
3. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
4. On the Edit menu, point to New, and then click Multi-String Value.
5. Type AuthForwardServerList, and then press ENTER.
6. On the Edit menu, click Modify.
7. In the Value date box, type the URL of the server that hosts the Web share (one URL per line), and then click OK.
8. Exit Registry Editor.
9. Restart the WebClient service 

Here's an example of valid URL's for the AuthForwardServerList registry entry:

• https://*.mavention.nl
• http://*.www.mavention.nl
• *.mavention.nl
• https://127.0.0.1