“So, when are the dev guys going to fix the installation process of the Surface PC so that it can be done without needing a mouse and keyboard. I have it from reliable sources that it is, indeed, not working. This fact is also not noted in the documentation. That’s kind of cheap for a US$15,000 computer, isn’t it,” I asked, as I walked up on the guy, hand extended. He sort of stared around a bit and then seemed to realize it was a question. He took my hand, shook it slowly, then her gave it a couple of good shakes and started to talk.

“Whoever you heard that from they’re lying.”

“Interesting. So you’re saying that a Surface PC can be set up using the touchscreen display,” I inquired. 

“Did you read that story on [insert gadget blog here],” he asked me, possibly attempting to look intimidating.

“I read it on [same blog here] and it was substantiated by people I know personally,” I responded. “So, can you set up the Surface PC using the touchscreen and if not, why is this fact not documented for the customer,” I drilled on. 

He then went on to explain that there are two types of customers; developers and some word which I guess means retailers in Microsoft-speak and I can’t recall. Developers get the unit au naturel. Retailers get a concierge type who works with them to configure the system for their needs and then arranges for its installation. Developers are expecting to have to set it up and they get all of the help they need to get it done. Retailers, however, have it all taken care of for them and never have to directly experience configuration. 

Here, then, is where the problem occurred. The retailer involved had it purchased by a 2nd party involved in the project who then had the unit shipped to their marketing firm and since the marketing firm wasn’t “in the loop” they never received the concierge service they would normally receive. The Microserf went on to explain that Microsoft was fully aware of this user-initiated failure in processing and claimed that the Redmond Giant was going to stomp all over the losers for reporting it to a blog before letting Microsoft fix the problem going to rectify the communications issues involved in the overall issue.

Purchase this and related items at Amazon now: