I am building a Surface compatible table with the Surface SDK.
I have built a few test stations allready, pictures will be up soon, of some proof of concepts.

Using a 19inch LCD and two mices, one with the buttons reversed to create a non-touch screen surface.
Screen was layed flat on a table and viewed from above.

• + Was easy and cheap, using available parts, and two inputs.
• + Would make for a pretty interesting kiosk or stand alone unit.
• + More mice = more inputs
• - Not touchscreen
• - Feels very hunt and peck like
• * Future: Add barscan/Video support for Surface Tags
• * Future: Build a complete table out of it

Using a projector to project on a wall, and the use of WiiMote for input to interact with the Surface Application.

• + Very big screen area
• + WiiRemote support
• - Uses WiiMote drivers, not Surface drivers
• - Projected on the wall, user shadows
• - Not easy to set up, not cheap
• = Tested: Rear projection works, both image and input work correctly
• * Future: To test in a top down manner
• * Future: Test in a down up manner (Bottom up through a table set up)
• * Future: Muti-Input methods

Using a Tablet PC laptop as the surface display

• + Made from exisiting units
• + Can be set up like the 19inch LCD test with mice
• - Must use the Pen, Non-Mutitouch
• * Future: Try using muti-type inputs

This has been a pretty interesting experiments, the goal to not just make a Muti-Touch unit but to
make a Microsoft Surface compatable with as little of added input code as possable.
I would think added outside input code to the Surface programs defeats the point of using the Surface Shell
and would make it harder to use on a actual Surface station.

Programs for Microsoft Surface (And Windows 7 MutiTouch) are planned.
Any software built for this will be in the Software area.