Surface 2 design changes make it more difficult to crack open and repair
This is the kind of crap that I don’t understand…
To all you tech pundits, so-called tech journalists, bloggers and others that think they know what they’re talking about: LET ME SAY IT PLAINLY — the Surface RT and the Surface 2 were *NOT DESIGNED* to be opened, upgraded or repaired by mere mortals. In fact, normal people CAN’T upgrade any variant of the Surface: most component are permanently soldered or glued into place. This is squarely in the realm of the MacGyvers of the world.
And let’s keep it real: just how many people open up an iOS or AndroidOS tablet to “fix” or “upgrade” it? That number is incredibly and vanishingly small in the scheme of things. And those who really, really, really want to void their warranty are certainly more than welcome to open theirs up…
… but why the heck would you mess with that anyway when you can simply walk into a Microsoft Store (or kiosk) and say, “This is broken”? Their response (after verifying that it’s broken) is, “OK! Here you go!” and hand you a BRAND NEW device! I know this is true because I did just that with my first-run Gen 1 Surface Pro… and I didn’t even buy it directly from Microsoft; I got mine from Best Buy. Now of course that doesn’t cover wear and tear; if you crack the screen because you put it in a vise or slam it in a car door that your bad. But if you’ve got faulty hardware, you’re covered.
And if I’m not mistaken a normal person can’t convert a 32GB iPad into a 64GB model, correct? Again, a MacGyver would be needed.
Back to the point of this rant… these libelous “investigative reports” that report only a quarter of the truth are really, really stupid. Instead of creating garbage to “report on” regarding hardware that’s simply well put together and incredibly functional, how about you guys check your facts and tell the whole story?
My private take on this: “Sammy, you shouldn’t have expected ‘pretty’ to overcome single OS & device, not-yet-ready packaging and ridiculously expensive price.”
My public take on this: “Feature-rich ubiquity will ALWAYS reign supreme. Your offering was too little, too early, at too high a price.”
I do entirely expect the form factor to take off, and that very soon. However, Samsung has *proved*, with this its at least SECOND failing at a smart watch offering, that it needs to let someone else figure out how to make it work and improve upon that.
Full Article: Galaxy Gear has a staggeringly high return rate
Posted from WordPress for Windows Phone
I’ll be creating a “real” post about the speech recognition capabilities in Windows Phone 8 since my cohorts at the conference coerced me into doing so… but until I do here’s slide deck.
I don’t recall where I saw this first… I think it was from a LinkedIn email… but the point is that it is a great article that plainly states concepts that a lot of professionals seem to forget or ignore. I’ve only made it to page 2 and I’ve already decided to put it on my “completely consume and absorb the first chance you get” list.
… I just thought you should know that Big Brother, the Apple version, has his eye on you again. #ijs
Apple Has Quietly Started Tracking iPhone Users Again, And It’s Tricky To Opt Out
Read more: http://www.businessinsider.com/ifa-apples-iphone-tracking-in-ios-6-2012-10#ixzz29TKAQiJw
Visual Studio is the greatest programming IDE ever. Even when it’s frustrating it’s still the best thing around. However, you wouldn’t believe how it can act funny until it happens to you.
Today’s saga was when I finally got my Windows 8 environment capable of front-line development work for both Office 2010 and Windows Azure projects. I fired up the debugger and WHAM! I saw a “Visual Studio 2010 Ultimate ENU Installer” dialog that had no business being there, especially since the original installation went off without a hitch. It would spin for about 2 to 5 minutes before finally disappearing and allowing Outlook to run. Of course that was a frustrating nuisance but I realized it was getting to be a problem (after I did the math and saw that I’d about an hour today waiting after hitting F5).
Of course, searching for a solution on both Bing and Google was fruitless until I hit on this little gem: http://channel9.msdn.com/Forums/TechOff/527958-Every-single-time-I-boot-my-PC-I-get-a-VS-2010-RC-setup-dialog . It wasn’t actually my problem but it put me on the right train of thought. The key was that all their experiences had a complete file path for the missing piece that the original installation failed to provide. Mine didn’t; all I saw in my event logs was the drive letter “e:\”. I realized that it was looking for the drive assigned to the external USB drive I used to install the application… so when I plugged that drive back in and hit F5 everything worked (like it was supposed to!).
Good Times are here again.
“CREATE DATABASE permission denied in database ‘master’. (.Net SqlClient Data Provider)”
Oh SQL Server Express, how I hate you sometimes. Not only did you not let me specify an sa password when I installed you, but you didn’t take the time to make me a sysadmin either.
The worst part was that I got this when I was trying to get to a geek party an hour away from my house. Oh well. Part of the problem was that there was no clear answer (with example!) of how to get around this issue… so… here you go.
Prerequisites for this technique:
- You have to be a local administrator on the box that has the SQL Server instance you’re trying add a database to.
- You have to be able to change the settings on Services on that box.
- You have to be able to start and stop Services on that box.
- Go to Services and Stop the service that is the target SQL Server instance. Also stop any SQL Server Agent service which are tied to that SQL Server instance service.
- Go to the Properties of the target SQL Server Instance service.
- In the Start Parameters field, add “;-m” to the *end* of whatever is already there. DON’T put in spaces OR include the quotes, and if nothing’s already there then you don’t need the semi-colon.
- Click OK and start the target SQL Service Instance service.
- Do a Windows Search for sqlcmd.exe … don’t be alarmed if there are several. You should use the one in the path that matches the SQL Server version that the target SQL Server Instance.
- Open an elevated command prompt.
- Path to the folder that has the sqlcmd executable in it. In my case, this was C:\Program Files\Microsoft SQL Server\110\Tools\Binn>.
- Run the following, with the appropriate user info, and DO include the quotes:
sqlcmd -S MachineName\SQLServerInstance -e -Q “EXEC sp_addsrvrolemember ‘UserDomain\UserName‘, ‘sysadmin’;”
- Go back to the service, remove the “;-m” you added, then restart the service.
- Verify that the user now has the sysadmin Server Role (via SSMS or however you want to do this).
- Don’t forget to restart any SQL Server Agent services that were stopped in #1 above.
Special thanks to Raul Garcia for putting me on the right path. You can see his original post here: http://blogs.msdn.com/b/raulga/archive/2007/07/12/disaster-recovery-what-to-do-when-the-sa-account-password-is-lost-in-sql-server-2005.aspx