Comments on: Surface SDK on Vista x64

By: Peter Brady

Peter Brady — Thu, 11 Mar 2010 20:11:29 +0000

I had the same problem as Vasco. It looks like the version of the simulator we have installs the simulator in not one but two directories. Make sure you run the corflags fix in both

C:\Program Files (x86)\Microsoft SDKs\Surface\v1.0 and
C:\Program Files (x86)\Microsoft Surface\v1.0

By: Surface SDK SP1 on Vista and Win7 x64 | GrumpyDev

Surface SDK SP1 on Vista and Win7 x64 | GrumpyDev — Fri, 22 Jan 2010 14:43:55 +0000

[...] is a follow up post to Surface SDK on Vista x64 where we got the original Surface SDK working on the unsupported Vista X64. Last week Microsoft [...]

By: srobbins

srobbins — Fri, 22 Jan 2010 14:38:44 +0000

Thanks Robin, very useful.

By: Robin Sanner

Robin Sanner — Thu, 31 Dec 2009 20:10:05 +0000

To get the samples to build and install correctly do the following:

- Edit the configuration properties for the sample solution and create an x86 platform for all projects.
- Edit InstallSamples.bat
– Comment out the lines on either side of the set as follows:

::FOR /F “eol=H tokens=2*” %%A IN (‘REG QUERY HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Surface\v1.0 /v IsLogicalSurfaceUnit’) DO SET LogicalTableValue=%%B
SET InstallingOnTable=false
::IF %LogicalTableValue%==0×1 SET InstallingOnTable=true

– Change the MSBuildParameters to reference the x86 PlatformName as follows:

SET MSBuildParameters=/p:Configuration=Release;PlatformName=x86 /noconsolelogger /fl /fileLoggerParameters:LogFile=%LogFile%;Append /nologo

By: srobbins

srobbins — Sun, 27 Dec 2009 08:42:39 +0000

Did you patch all of the assemblies? Is the crash giving you any more information in the event log?

By: srobbins

srobbins — Sun, 27 Dec 2009 08:41:55 +0000

I don’t think there’s anything you can do about this. The Simulator runs at the native Surface resolution (1024×768), but also adds the Simulator “chrome” around the outside, so you really need 1024 high to be able to use it.

Your only option is probably an external monitor (if you’re using a laptop) or cranking your resolution up if you are using a monitor.

By: teeeeaaa

teeeeaaa — Thu, 24 Dec 2009 03:04:59 +0000

Hi,
Tried installing the surface sdk, but kept getting an error about not meeting the minimum resolution required. How can this be fixed?

By: iria

iria — Sat, 19 Dec 2009 16:02:06 +0000

Hi,

I run it as administrator and now i get this:
Microsoft (R) .NET Framework CorFlags Conversion Tool. Version 3.5.21022.8
Copyright (c) Microsoft Corporation. All rights reserved.

corflags : warning CF011 : The specified file is strong name signed. Using /For
ce will invalidate the signature of this image and will require the assembly to
be resigned.

But i can’t run the simulator, i get a error the simulator is not working anymore.

Thanks,
Iria

By: srobbins

srobbins — Sat, 19 Dec 2009 10:41:35 +0000

It sounds like a permission issue, are you sure you’re running it from an elevated VS command prompt?

By: iria

iria — Fri, 18 Dec 2009 21:58:22 +0000

hi,

i’m at step 2.5
corflags Attract.exe /32bit+ /force
corflags AttractConfig.exe /32bit+ /force
corflags SurfaceInput.exe /32bit+ /force
corflags SurfaceOutOfOrder.exe /32bit+ /force
corflags SurfaceShell.exe /32bit+ /force

And i get a error:
corflags : error CF001 : Could not open file for writing

Thanks, Iria

By: Dan

Dan — Thu, 26 Nov 2009 11:39:40 +0000

After removing the sqm bit from the msi file, it worked like a sharm.
Thanks!

By: srobbins

srobbins — Sun, 30 Aug 2009 14:25:14 +0000

Is it the SP1 version you’re installing? Take a look at the updated article if it is, there’s an additional step required.

By: david

david — Sun, 30 Aug 2009 13:53:55 +0000

hi, when i try to install the new sdk modified via orca, at the finish of the install process it says that there is a problem and then it rollback unistalling the sdk

thank you
David

By: srobbins

srobbins — Wed, 03 Jun 2009 13:45:13 +0000

Yep, although that's not the case with SP1 (see the updated link). Is there a specific reason why you are using the original SDK rather than SP1 now?

By: Jack Ukleja

Jack Ukleja — Tue, 02 Jun 2009 15:11:28 +0000

For Windows 7 removing the 64bit check is not enough – you also have to remove the OS version & Service pack check, or else you will get the error “Your system does not have the correct service pack.”

By: Jack Ukleja

Jack Ukleja — Tue, 02 Jun 2009 14:57:00 +0000

For those of us doing the web install of the SDK to get Orca, which of the install options do we need to get *just* Orca? (save on 1.5GB of bandwidth!)

By: srobbins

srobbins — Fri, 22 May 2009 10:17:37 +0000

Thanks for that, I’m looking at putting a script together that will do the whole lot (or that’s the plan anyway), just haven’t had chance yet

By: Jeff Klawiter

Jeff Klawiter — Thu, 21 May 2009 14:16:19 +0000

To make it a little easier on people, you can copy and paste this into your command prompt to do the 32bit updates

cd “C:\Program Files (x86)\Microsoft SDKs\Surface\v1.0\Tools\Simulator”
corflags SurfaceSimulator.exe /32bit+ /force
cd “C:\Program Files (x86)\Microsoft Surface\v1.0″
corflags Attract.exe /32bit+ /force
corflags AttractConfig.exe /32bit+ /force
corflags SurfaceInput.exe /32bit+ /force
corflags SurfaceOutOfOrder.exe /32bit+ /force
corflags SurfaceShell.exe /32bit+ /force

By: Jeff Klawiter

Jeff Klawiter — Thu, 21 May 2009 14:06:05 +0000

this page is a godsend for us that demand to have modern development rigs but still need to develop for surface. I can understand they want the requirements to be the same or as close to what the real unit is but this is getting ridiculous.

Thanks for the CreateSqmMachineGuid update. I had just tracked it down that it was failing at that point. good ole msiexec /i SurfaceSDKWE.msi /L*v log.txt

By: srobbins

srobbins — Fri, 15 May 2009 20:17:42 +0000

Thanks for the comment.. I am putting together a new post for SP1, but I’ve only just reinstalled my x64 box so it’s taking a while! Glad you got it going.

By: JamesK

JamesK — Fri, 15 May 2009 20:10:52 +0000

Ok, just got SP1 working on Vista Ultimate x64. I’m way behind in my work so maybe someone else can put together a tutorial. Basically follow the x64 tutorial from above, but while in MSIEdi or Orca find the InstallExecuteSequence table. Look for the two SQM steps (SetupCreateSQMMachineGuid and CreateSQMMachineGuid) and remove them. Install as usual. Then when you do the 32-bit force on all the executables, remember to do the same to Attract.exe. Other than that is seems to work. Hope it helps some people.

By: JamesK

JamesK — Fri, 15 May 2009 15:08:15 +0000

Bart, did you get this running? I have exactly the same problem. Nothing in the event log or anywhere I can find to tell what is happening?

By: Bart Roozendaal

Bart Roozendaal — Wed, 13 May 2009 08:34:35 +0000

Now, I try to do the trick again for SP1 of the SDK. Unfortunately there are some other tweaks needed. There’s probably something else in the MSI that conflicts. The install rollsback when it’s almost at the end. I had a look at the MSI script, but can’t figure out what’s the offending part.

Btw: I’m running Windows 7 RC 64 bits.

By: srobbins

srobbins — Wed, 29 Apr 2009 13:59:56 +0000

Yeah, I’ve had it running on Win7, just haven’t got around to updating the post.. It’s an “exercise for the reader”

By: Bart Roozendaal

Bart Roozendaal — Wed, 29 Apr 2009 09:27:59 +0000

For the record: I only had to remove a launchcondition or two more and all works fine in Win7. What a relieve. That removes me from needing to have the actual unit in my office. The sound and temperature changes were getting to me a bit Now, let’s start developing on my nice HP Touchsmart… Great post.