• Identity Template: xsl:copy with recursion
• Reading Multiple Input Documents (also demonstrates for-each)
• Conditional execution
• Pretty much everything else

A simple winforms Squeeze client.

I thought it would be nice to be able to control SqueezeCenter from something sitting in the taskbar, so over the last couple of days I made a simple .NET client. I’ve got 90% of what I need running, so as a proof of concept it has served its purpose.

Most of my effort was spent on data access and marshalling threads into the UI. Once I finish under the hood I might make a WPF UI layer, which would make it much more presentable.

Once you register, select the following pieces of evidence (for some of them, you need to drill in to get the individual items):

1. Tyre tracks (117h)
2. Short cigarette (117b)
3. Origami bird
4. Coffee shop C (“diner”)

Once submitted you get a code which you can redeem in the Playstation store (there is a little button next to your basket icon at the top which took me an embarrassingly long time to find).

I really enjoyed the sleazy place demo, despite the clunky camera. This is a classic problem: you can let the player control the camera, or provide canned control sequences which are more cinematically gratifying. Although the shots might be framed better, you blunder about like a fool. This tends to break the suspension of disbelief, and is exacerbated by an animation engine which fails to adapt well enough to recover from most blunders.

This sort of criticism is missing the point I think, and failed to put a dent in my enjoyment. Quick time events have evolved slightly since Shenmue, and I like the way button sequences physically reflect the onscreen action and are embedded in the game world.

Watching this I realised that when I played it parts of some scenes ended differently (it clearly depends which questions you ask).

Fault bucket 736400234, type 5
Event Name: VMM20
Response: None
Cab Id: 0

Problem signature:
P1: vmmservice
P2: 2.0.4271.0
P3: Engine.TaskRepository
P4: 2.0.4271.0
P5: M.V.D.T.Task.GetAllTasks
P6: S.C.Generic.KeyNotFoundException
P7: cdb2
P8:
P9:
P10: 

Attached files:
C:\Windows\Temp\SCVMM.f5c52a6e-8f74-450c-bc57-d0ede6234a3b\report.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Report069118df

The logs were empty, and a quick search based on this error didn’t yield any useful results. Eventually, I tried running a DBCC CHECKDB in SQL Server and found some corrupted page links like this:

Table error: Object ID x index ID x, partition ID x alloc unit ID type In-row data). Page x is missing a reference from previous page Possible chain linkage problem.

No wonder I got no hits by searching, it’s quite unlikely that somebody else’s SQL Server suffered the same corruption. I had to repair with data loss, but was able to recover practically everything (my automated backup hadn’t been running for some time).

ALTER DATABASE VirtualManagerDB SET SINGLE_USER WITH NO_WAIT
DBCC CHECKDB (VirtualManagerDB, REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE VirtualManagerDB SET MULTI_USER WITH NO_WAIT

Good old DBCC CHECKDB did the job.

Repair: The Nonclustered index successfully rebuilt for the object "dbo.tbl_TR_SubtaskTrail, PK_tbl_TR_SubtaskTrail" in database "VirtualManagerDB".
Msg 8945, Level 16, State 1, Line 3
Table error: Object ID 2137058649, index ID 1 will be rebuilt.
        The error has been repaired.
Msg 8978, Level 16, State 1, Line 3
Table error: Object ID 2137058649, index ID 1, partition ID 72057594039173120, alloc unit ID 72057594040418304 (type In-row data). Page (1:12338) is missing a reference from previous page (1:50295). Possible chain linkage problem.
        The error has been repaired.
Msg 8981, Level 16, State 1, Line 3
Table error: Object ID 2137058649, index ID 1, partition ID 72057594039173120, alloc unit ID 72057594040418304 (type In-row data). The next pointer of (1:50295) refers to page (1:34253). Neither (1:34253) nor its parent were encountered. Possible bad chain linkage.
        The error has been repaired.
Msg 8945, Level 16, State 1, Line 3
Table error: Object ID 2137058649, index ID 2 will be rebuilt.
        The error has been repaired.

The moral of this tale: make sure your automated backups are working properly.

Robozzle combines three things I like: games, programming and robots. It’s surprisingly addictive.

The source code is available here. If you get stuck, try this.

This breaks the previous record for a ramp-to-ramp rally car jump by 98 feet.

Ultimately, I’m sure they’re planning to miniaturise and embed this into people.

GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}

It’s not quite TweakUI, but it is quite handy.

Some newer versions of Windows display the input region widget on the login screen if you install multiple input locales. On XP, I couldn’t get this to appear.

To get around this, I found it is possible to change the default keyboard settings in the registry. Obviously I had to log in using the local Admin account in order to make this change, which fortunately had a password I was able to type.

Toward the beginning there is quite a nice illustration of why you might not find Heisenbugs by stress testing. Further in there is a more detailed explanation of how CHESS works, and how the thread interleaving state space is reduced to a manageable level.

In this installment we see how to use the managed version of CHESS within a Visual Studio concurrency unit test.

Finally, here we get an overview of the tooling which helps visualise different thread interleavings.