Category Archives: windows

gaming, windows

Hands On: Xbox One Game Streaming to Windows 10

Xbox One Game Streaming has been switched on for all Windows 10 users and I gave it a quick try.

You need the latest Xbox app of course, as well as a wired Xbox controller (I used a 360 controller). Turn your Xbox on, run the app, make sure you are signed in with a Microsoft account that also has a profile on the console, and hit the Connect button near bottom left.

image

Once connected, click Test streaming to verify that you have enough bandwidth, or Stream to start streaming.

I tried Dark Souls 2. It worked pretty well, except that the screen (which is dark anyway for this particular game) was even darker over the streamed connection. With the in-game option set to maximum brightness it was playable. I did not notice any lag though there was an occasional stutter; this is over wireless though and a wired connection would be better.

While you are streaming, all the action displays on the TV connected to the console itself as well as on your PC.

Streaming only works full screen. If you are streaming and press the Windows key you get an odd effect where streaming continues in the background but the Start menu displays.

image

If you then run another application, the streaming pauses, but you can resume later. Or sometimes the Xbox app seems to quit. It seems best not to switch apps while streaming.

I noticed that trying to start streaming when the console is on standby does not work; you cannot wake it up. That is a shame.

Otherwise, it all works as you would expect. Although it is not as good as gaming in say the living room with what is probably your biggest screen, this is a nice feature for when that room is in use and you want to sneak off and play a game.

windows

Satya Nadella positions Windows Phone as small PC, Microsoft retreats from Phone business

3 Comments

Microsoft CEO Satya Nadella has spoken to journalist Mary Jo Foley about the future of Windows Phone and Windows Mobile. What you read there does, I suspect, reflect heated discussions on Microsoft’s board about Windows strategy. I am guessing of course; but given the departure of Stephen Elop in June, and the cuts announced by Nadella last week, including the departure of 7,800 employees mostly from the phone business and the write-off of the value of the assets acquired from Nokia, it is likely that Elop disagreed with the new strategy.

image

So what is the future of Windows Phone? I suggest you read the transcript carefully because it is not clear, deliberately so. Nadella says:

We will do everything we have to do to make sure we’re making progress on phones. We have them. Even today Terry (Myerson, the head of Windows and Devices) reinforced, again, yes, we will have premium Lumias coming this year.

When then was the meaning of last week’s announcement? Mainly, it seems to me, that having acquired a phone business from Nokia, Microsoft is now dismantling it and drawing back from the phone business. Nadella tells Foley she is right to conclude that “Your phones are going to be more of like showcase devices for what Windows mobile can look like on a phone.”

He also makes a couple of other remarks. Curiously, he says that “If no OEM stands up to build Windows devices we’ll build them. There will be Lumia devices.” What if we turn that round. Let’s say OEMs do continue to build Windows phones. You get the impression that in that case, Nadella would be happy to scrap Lumia. But what constitutes building a Windows Phone? The lacklustre efforts that appeared at the launch of Windows Phone 7, slightly adapted Android phones? Or beautiful Nokia devices like the 1020 with a 40MP camera, or the elegantly crafted Lumia 830?

Nadella views Windows Mobile through a PC lens. In fact, he says that the best thing about Windows Phone is its ability to be a PC:

So when I think about our Windows Phone, I want it to stand for something like Continuum. When I say, wow, that’s an interesting approach where you can have a phone and that same phone, because of our universal platform with Continuum, and can, in fact, be a desktop.

Like most things in IT, this has been tried before. The Asus Padfone has been around for several years in various guises, the idea being that you dock your phone into the back of a tablet to give it a big screen.

image

It is a great gimmick but the Padfone has had limited success; most people, it seems, use phones as phones, tablets as tablets, PCs as PCs. That could change, but I doubt Continuum will rescue Windows Phone.

This also betrays a PC-centric view of Windows Phone. Hey, it looks like a phone, but it has the brains of a PC. I can certainly see uses for this kind of device, but nobody goes into a phone shop and says, “I am looking for a phone that works like my PC”.

I recapped the history of Windows Phone here. Many things need to come together to make a successful phone, including not only the OS but the hardware design, the apps, the marketing, the sales channel and the operator partnerships. Microsoft proved incapable of doing this until Nokia adopted the platform.

There are now hints that Microsoft will outsource future Lumia (if it makes them) to OEMs to build. Here is what Nadella says:

I want people to evaluate us on the phones that we produce, but not the inside baseball — what are we doing to produce — because that should not be relevant to our broad consumers.

Don’t look too closely, Nadella seems to be saying, because Microsoft might not be as closely involved in the phones it makes as it first appears.

Financially, of course, the cost involved in paying the likes of Asus or Acer to make some phones running Windows is tiny compared to the cost of operating a phone business. The results though will not be the same at all.

All about the apps

The big puzzle here is about the apps. The single biggest factor holding back Windows Phone has been lack of apps, or the inferior quality of available apps. Thus, the Nokia acquisition combined with Windows 10 universal apps seemed to based on the idea that by providing a single developer platform across Windows and Phone, Microsoft could fix the app problem and make a success of the phone by combining it with Nokia’s hardware and design expertise.

Nadella now seems to be removing the Nokia element before the app strategy has had a chance to succeed, though he re-iterates the notion of Windows 10 being beneficial to the phone:

All of this comes down to how are you going to get developers to come to Windows. If you come to Windows, you are going to be on the phone, too. Even if you want to come to Windows because of HoloLens, you want to come to it because of Xbox, you want to come to the desktop, all those get you to the phone.

Note that in reality it is not that simple. Universal Apps will run on the phone and PC, but the user interface may require considerable effort before it makes sense on both form factors. There is still a cost, for developers, in supporting both phone and PC. In fact, there is a cost even in cases where the code runs untouched, just because of the additional testing and support required.

In practice though, Nadella does not think Windows Phone makes much difference to developers:

Universal Windows apps are going to be written because you want to have those apps used on the desktop. The reason why anybody would want to write universal apps is not because of our three percent share in phones.

This shows, I think, the extent to which Nadella has given up on Windows Phone. This too is where Nadella’s leadership has diverged from that of his predecessor, Steve Ballmer. Ballmer acquired Nokia because he believed that Microsoft needed to continue bashing away at Windows Phone until it worked, because the PC is in decline and mobile is the future. Nadella has abandoned that plan because he does not think Windows Phone can ever succeed, and thinks instead that Microsoft can prosper as a device-neutral company:

We want to be in every device, not only have our application endpoints on every device. I want the identity management. It’s not MSA [Microsoft Account] alone, it’s Azure Active Directory. It is managing those devices, securing those devices in terms of data protection. These are all core capabilities that we have. … one big mistake we made in our past was to think of the PC as the hub for everything for all time to come. And today, of course, the high volume device is the six-inch phone. I acknowledge that. But to think that that’s what the future is for all time to come would be to make the same mistake we made in the past without even having the share position of the past. So that would be madness.

Microsoft then is also hoping that some future thing comes up which makes its Windows Phone failure unimportant.

I am not so sure. I think Nadella should have given the Nokia acquisition a chance to work, and the destruction of value from this acquisition saddens me. The other side of this argument is that it is better to kill something that is not working earlier rather than later. Whichever is right, Microsoft has taken the most expensive route possible, making the Nokia acquisition and then changing course.

microsoft, mobile, windows

Windows Phone puzzles: strategy, what strategy?

Today Microsoft CEO Satya Nadella announced that 7,800 employees will be removed “primarily in our phone business” and that the company is taking a $7.6 billion “impairment charge … related to assets associated with the acquisition of the Nokia Devices and Services business.”

Time for a quick resume of the company’s troubled mobile efforts since the introduction of Windows Phone in October 2010:

October 2010: botched launch of Windows Phone. Despite much good work in the OS and user interface, Microsoft had lacklustre support from hardware partners, and focused on the consumer when its potential strength was in business integration with Office, Exchange etc. In addition, availability was poor; after the UK launch I went down to my local town centre and not one of the 4 or 5 mobile phone shops had it on sale.

February 2011: Nokia announces that Windows Phone will be its primary smartphone OS.

October 2011: First Nokia Windows Phones appeared. Lumia 800 was a nicely designed phone in some respects, but suffered from poor battery life and some quality issues.

Nevertheless, the Nokia Windows Phones were the first ones where the manufacturer made an effort to get the best from the OS and to tailor the hardware for it. In addition, Nokia brought excellent mapping and photography expertise, so that Windows Phones began to get some standout features.

11 July 2013: Launch of Nokia Lumia 1020 with an amazing 41MP camera.

September 2013: Microsoft announces that it will acquire Nokia.

An awkward period follows before the acquisition completes. It is meant to be business as usual at Nokia but of course it is not.

February 2014: Despite some progress, Windows Phone is not getting the market share Nokia needs, so CEO Stephen Elop announces the Nokia X range, Android smartphones with Google removed and replaced by Microsoft services. A curious announcement, since why would anyone buy Nokia X? It was not because Android works better than Windows Phone on low-end hardware; vendors have told me that the reverse is true. Nor does it make sense bearing in mind the Microsoft acquisition – though it will have been in the planning stage before that was decided.

April 2014: Microsoft’s Nokia acquisition completes. Elop joins Microsoft to head up devices. As soon as July, it is obvious that Microsoft will not be continuing with Nokia X.

September 2014: Microsoft announces Windows 10. “we are delivering one application platform for our developers … Windows 10 will deliver the right experience on the right device at the right time. It will be our most comprehensive platform ever,” says Windows VP Terry Myerson.

The new universal app platform is all very well, but it means that Windows Phone is now in stasis, waiting for Windows 10 before anything much can happen to it. There is a notable lack of new high-end phones. No phone since the Lumia 1020 has had a camera of equal resolution.

At the same time, part of the point of Windows 10 is to revive the application platform across phone and PC. If you remove the phone, the Universal Windows Platform is what, PC, Xbox (mainly a games console) and HoloLens? With a few Raspberry Pis and IoT devices thrown in?

17 June 2015: Elop leaves Microsoft following an executive re-shuffle.

8 July 2015: Suspicions that Microsoft is wavering in its commitment to Windows Phone (or Windows 10 Mobile) are confirmed by the announcement of major cuts to the phone business.

A few observations

Microsoft has given Nokia little chance of success following the acquisition. It is not quite a repeat of the Kin disaster (acquisition of Danger in February 2008, a strong company wrecked by its acquirers), but there are echoes. It is only a year and three months since the acquisition completed, and the phone range is in an uncomfortable “waiting for Windows 10” phase. What did the company expect, that a Microsoft halo effect would suddenly lift sales, even without distinctive new models?

Nokia did a much better job with Windows Phone than either Microsoft or its other hardware partners. Nokia’s retail presence, operator partnerships, and marketing, were all far superior.

The main reason for the failure of Windows Phone is the lack of apps and ecosystem, and the reason for that is that Microsoft was too late to launch; iOS and, more to the point, Android, were already well entrenched. The Windows Phone OS is pretty good, and superior to the competition in some respects; apps are easier to find, for example.

Another problem is that Windows Phone has been more successful in Europe than in the USA. This means that US-centric vendors perceive that Windows Phone has an even smaller market than in fact it has.

Bearing in mind that the app story is the biggest single problem for Windows Phone vendors, and that Windows 10 is intended to address that, it is puzzling that Microsoft is now writing off the phone division before Windows 10 has launched.

Nadella writes:

I am committed to our first-party devices including phones. However, we need to focus our phone efforts in the near term while driving reinvention. We are moving from a strategy to grow a standalone phone business to a strategy to grow and create a vibrant Windows ecosystem that includes our first-party device family.

The problem is that frail market confidence in Windows Phone will be further shaken by today’s announcement. Further, if Nadella thinks that Microsoft’s trusty hardware partners will step up their game if Lumia is given less investment, than he has forgotten their dismal performance first time around.

Does Microsoft need Windows Phone?

Microsoft has been investing in Android and iOS apps since Nadella’s appointment, and it may not have a choice about whether or not it needs a mobile OS, if it cannot find a market for it.

There some strategic issues though. Microsoft itself succeeded first with Windows on the desktop, and exploited its desktop presence to drive server products that integrated with Windows and shared its user interface and operating system.

Mobile operating systems are now ascendant, and if Microsoft has little or no presence in that market, it is vulnerable to its competitors exploiting their control of the client to drive users to their own services, rather than those run by Microsoft.

Therefore it seems to me that ceding the mobile market to Apple and Google is a strategic risk.

microsoft, tips, windows

How to overcome “A required drive partition is missing” in Windows 8.1 reset

3 Comments

Here is the scenario: an HP all-in-one PC gets a virus and as a precaution the owner wishes to reinstall Windows.

The recovery drive on the PC is intact, but attempting to use the Windows 8.1 troubleshooting tools to “Reset your PC” (in effect reinstalling Windows) raises the error “A required drive partition is missing”.

This seems to be a common scenario in cases where the PC was supplied with Windows 8 and upgraded to Windows 8.1. The problem seems to be that Windows 8.1 makes some changes to the drive partitions that make it incompatible with the Windows 8.0 recovery partition.

Here is the workaround I used:

1. In Windows 8.1, make a recovery drive. To do this, first connect a USB drive that you are happy to have wiped. It will need a capacity of around 16GB or more. Then run Control Panel, search for “recovery”, and choose Create a recovery drive.

image

2. When creating the recovery drive, make sure the option to include the recovery partition is checked. This will copy the recovery partition from the PC to the USB drive.

3. When you are done, you will be able to boot from the USB drive. You could choose the Reset option from there, however you will still get the error. First, go to Troubleshooting and Advanced and select the command prompt. When the command prompt opens, type:

diskpart

Now type:

list disk

You will see two disks (or more) listed, one for the USB boot device, and the others the disk(s) in the PC. Select the internal boot drive. It is normally obvious from the sizes which is which. Select it by typing:

select disk n

where n is the number of the drive as shown by list disk.

WARNING: the next step will delete all data on the selected drive. If in doubt, back out and make a backup of the drive before proceeding. If something goes wrong, your PC will no longer be bootable and you will need recovery media from the manufacturer, or to buy a new copy of Windows.

Once you are happy that it is safe to delete everything from the drive, type:

clean

or

clean all

The first command does a quick removal of the partition table from the drive but does not zero the data; it will be invisible but possibly recoverable using data recovery tools. The second command zeroes all the data and takes much longer (several hours), but it is more secure, if for example you want to sell or transfer the PC.

Once this is done,reboot the PC using the USB recovery drive. Select troubleshooting, then Reset your PC. This time it will work and you will be back in Windows 8.0.

Note: This scenario is common enough that it seems to be a flaw in the Windows 8.x recovery tools. I do not understand why Microsoft has so little regard for its users attempting to recover Windows (and usually highly stressed) that it has not fixed this problem.

Note 2: What if you cannot boot into Windows 8.1 to make the recovery drive? I have not tried it, but in theory it should be possible to create a recovery drive on another PC and copy the recovery drive to it.

microsoft, professional, windows

Installing Windows 10 on Surface 3 with Windows To Go

I am working on a review of Surface 3, Microsoft’s recently released Atom-based tablet, and wanted to try Windows 10 on the device. How to do this though without endangering the correct functioning of my loan unit?

The ideal answer seemed to be Windows To Go (WTG), which les you run Windows from a USB drive without touching what is already installed – well, apart from a setting in control panel that enables boot from Windows to Go.

image

Luckily I have an approved Windows to Go USB drive, a 32GB Kingston DataTraveler Workspace. I downloaded the Windows 10 iso (64-bit, build 10074) and used the Control Panel applet on my Windows 8 desktop (which runs the Enterprise edition) to create a WTG installation.

(There are unofficial ways to get around both the requirement for Enterprise edition, and the need for an approved USB device, but I did not have to go there).

Next, I plugged the drive into the Surface 3 and restarted. Windows 10 came up immediately. An interesting feature was that I was prompted to sign into Office 365, rather than with a Microsoft account. It all seemed to work, though Device Manager showed many missing drivers.

image

The wifi driver must have been one of them, since I had no network.

I had anticipated this problem by downloaded the surface 3 drivers from here. These were inaccessible though, since a WTG installation by default has no access to the hard drive on the host PC. I could not plug in a second USB device with the drivers on it either, since there is only one USB port on the Surface 3.

No matter, you can mount the local drives using the Windows Disk Management utility. I did that, and ran the Surface 3 Platform Installer which I had downloaded earlier. It seemed to install lots of drivers, and I was then prompted to restart.

Bad news. When trying to restart, boot failed with an “inaccessible boot device” error.

Fool that I am, I tried this operation again with a small variation. I rebuilt the WTG drive, and instead of mounting the drives on the host, I used it first on another PC, where the wifi worked straight away. I copied the Surface 3 files to the WTG drive C, then booted it on the Surface 3. Ran the Surface 3 Platform Installer, restarted, same problem “Inaccessible boot device”.

The third time, I did not run the Surface 3 Platform Installer. Instead, I installed the drivers one by one by right-clicking on the Unknown Devices in Device Manager and navigating to the Surface 3 drivers files I had downloaded using another PC. That looks better.

image

I restarted, and everything still worked. I have wifi, Bluetooth, audio, cameras and everything. So something the Platform Installer tries to do breaks WTG on my device.

The next question is whether the system will update OK when set to Fast for the Windows 10 bleeding edge. So far though, so good.

Note: there is an issue with power management. If the Surface 3 sleeps, then it seems to wake up back in Windows 8 if you leave it long enough. Not too much harm done though; restart and you are back in Windows 10.

Note 2: new builds will not install on WTG, they complain about an unsupported UEFI layout

microsoft, mobile, software development, visual studio, windows

Windows 10 at Mobile World Congress 2015: a quick reflection

1 Comment

I attended Mobile World Congress in Barcelona last week – with 93,000 attendees and 2,100 exhibitors according to the latest figures.

It was a big event for Microsoft’s new Windows. It started for me on the Saturday before, when Acer unveiled a low-end Windows Phone (write-up on the Reg). Next was Microsoft’s press conference; Stephen Elop was on stage, presenting two new mid-range Lumias as if nothing had changed since last year when he announced the now-defunct Nokia X:

image

The Lumia 640 looks good value, especially in its XL guise: 5.7” 1280 x 720 display, 8GB storage plus microSD slot, 13MP camera, 4G LTE, quad-core 1.2GHz CPU, €189 ex VAT. The smaller Lumia 640 is now on presale at £169.99; we were told €139 ex VAT at MWC, so I guess the real price of the 640XL may be something like £230, though there will be deals.

These phones will ship with Windows Phone 8.1 but get Windows 10 when available.

The big Windows 10 event was elsewhere though, and not mentioned at the press conference. This was the developer event, where General Manager Todd Brix, Director of Program Management Kevin Gallo and others presented the developer story behind the new Universal App Platform (not the same as the old Universal App Platform, as I explain here).

image

This was the real deal, with lots of code. There was even a hands-on session where we built our own Universal Apps in Visual Studio 2015. Note that the Visual Studio build we used featured an additional application type for Windows 10; this is not the same as a Store app in Windows 8, though both use the Windows Runtime.

As someone with hands-on experience of developing a Store app, I am optimistic that the new platform will achieve more success. It is a second attempt with a bit more maturity, and much greater effort to integrate with the Windows desktop, whereas the first iteration went out of its way not to integrate.

Much of the focus was on the Adaptive UX, creating layouts that resize intelligently on different devices. The cross-platform UI concept is controversial, with strong arguments that you only get an excellent UI if you design specifically for a device, rather than trying to make one that runs everywhere. The Universal App Platform is a bit different though, since it is all Windows Runtime. Microsoft’s pitch is that by writing to the UAP you can target desktop, Windows Phone, tablet and Xbox One, with a single code base; and without a cross-device UI this pitch would lose much of its force. Windows 7 legacy is a problem of course; but if we see Windows 10 adopted as rapidly as Windows 7 (following the Vista hiccup) this may not be a deal-breaker.

The official account of the MWC event is in Gallo’s blog post which went out on the same day. There was much more detail at the event, but Microsoft is holding this back, perhaps for its Build conference at the end of April. So in this case you had to be there.

image

Aside: if you look at the publicity Microsoft got from MWC, you will note that it is mostly based on the press conference and the launch of two mid-range Lumias, hardly ground-breaking. The fact that a ton of new stuff got presented at the developer event got far less attention, though of course sharp eyes like those of Mary Jo Foley was onto it. I have a bias towards developer content; but even so, it strikes me that a session of new content that is critical to the future of Windows counts for more than a couple of new Lumias. This demonstrates the extent to which the big vendors control the news that is written about them – most of the time.

android, microsoft, mobile, rants, smartphones, windows

Why Microsoft is hard to love

1 Comment

Microsoft CEO Satya Nadella stated last week that “We want to move from people needing Windows to choosing Windows to loving Windows. That is our bold goal with Windows.”

It is an understandable goal. Many users have discovered a better experience using a Mac than with Windows, for example, and they are reluctant to go back. I will not go into all the reasons; personally I find little difference in usability between Mac and Windows, but I do not question the evidence. There are numerous factors, including the damage done by OEMs bundling unwanted software with Windows, countless attacks from malware and adware, badly written applications, low quality hardware sold on price, and yes, problems with Windows itself that cause frustration.

There is more though. What about the interaction customers have with the company, which makes a difference to the emotional response to which Nadella refers? Again, Apple has an advantage here, since high margins enable exceptional customer service, but any company is capable of treating its customers with respect and consideration; it is just that not all of them do.

Now I will point Nadella to this huge thread on Microsoft’s own community forums.  The discussion dates from September 10 2014 and the contributors are customers who own Windows Phone devices such as the Lumia 1020. They discovered that after updating their devices to Windows 8.1 they experienced intermittent freezes, where the phone stops responding and has to be cold booted by pressing an emergency button combination (volume down plus power). These, note, are critical customers for Microsoft since they are in the minority that have chosen Windows Phone and potentially form a group that can evangelise this so far moribund platform to others.

The thread starts with a huge effort by one user (“ArkEngel”) to document the problem and possible fixes. Users understand that these problems can be complex and that a fix may take some time. It seems clear that while not all devices are affected, there are a substantial number which worked fine with Windows Phone 8, but are now unreliable with Windows Phone 8.1. A system freeze is particularly problematic in a phone, since you may not realise it has happened, and until you do, no calls are received, no alerts or reminders fire, and so on, so these customers are anxious to find a solution.

Following the initial complaint, more users report similar issues. Nobody from Microsoft comments. When customers go through normal support channels, they often find that the phone is reset to factory defaults, but this does not fix the problem, leading to multiple returns.

Still no official comment. Then there is an intervention … by Microsoft’s Brian Harry on the developer side. He is nothing to do with the phone team, but on 27 October receives this comment on his official blog:

Brian, sorry to hijack you blog again, but you are the only person in MS who seems to care about customers. Can you please advise whoever in MS is responsible for WP8.1 and make them aware of the “freeze” bug that MANY users are reporting (31 pages on the forum below). There has been NO feedback from MS whatsoever in the months that this has been ongoing and it is obviously affecting many users (myself included). If “cloud first, mobile first” is to be a success, you better make the bl00dy OS work properly. Thanks

Harry promises to raise the issue internally. On 12 Nov still nothing, but a reminder is posted on Harry’s blog and he says:

Nag mail sent.  Sorry for no update.

This (I assume) prompts a post from Microsoft’s Kevin Lee – his only forum post ever according to his profile:

I’m sorry we’ve been dark – I work closely with the Lumia engineering team that’s working directly on this. Trying to shed a little light on this…

Beginning in early September we started to receive an increased number of customer feedback regarding Microsoft Lumia 1020 and 925 device freezes. During the last two months we have been reaching out for more and more data and devices to systematically reproduce and narrow down the root cause. It turned out to be a power regulator logic failure where in combination with multiple reasons the device fails to power up the CPU and peripherals after idling into a deep sleep state.

I am pleased to pass on that we have a fix candidate under validation which we expect to push out the soon with the next SW update!

Appreciate your patience.

OK, so Microsoft knows about the problem, has sat back saying nothing while users try this thing and that, but now after two months says it has a “fix candidate”. This is greeted warmly as good news, but guess what? Phones keep freezing, no fix appears, and in addition, there is lack of clarity about how exactly the fix is being “pushed out”.

Two months later, user Shubhan NeO says:

And I broke my Lumia 1020. Not going back to Windows Phone ever ! Switching back to Android ! Here is sneak peek of my phone !

image

It is not quite clear whether he broke the phone deliberately in a fit of frustration, but perhaps he did as he comments further:

Works ? Seriously ? It hangs 2-3 a day, has stupid support for official apps. So many issue.

I’m done.

Here is another:

I paid the extra £ for a better phone; with a better ’41-megapixel camera’… now to find out that people with cheaper models have not had any freeze problems. Despite peoples comments about this being an aged device, and probably the reason for lack of support, I must add that I only purchased my 1020 ‘NEW’ in July 2014 (which is only 6 months ago). For 3 of those months it has been very unreliable … I am extremely disappointed in how I and everyone else here has been treated by Microsoft.

Read the thread for more stories of frustration and decisions never to buy another Windows Phone.

What are the real problems here? The hardest thing to accept is not the fact of the fault occurring, or even the time taken to fix it, but the apparent lack of concern by the company for the plight of its customers. If Mr Lee, or others from the team, had posted regularly about what the problem is, how they are addressing it, possible workarounds and likely time scales, it would easier for users to understand.

As it is, it seems that this part of the company does not care; a particular shame, as Nokia had a good reputation for customer service.

I post this then as feedback to Nadella and suggest that a cultural shift in some areas of Microsoft is necessary in order to make possible the kind of emotional transition he seeks.

microsoft, Web, web authoring, windows

The Windows 10 web browser story: it’s complex

3 Comments

Microsoft’s Jason Weber has posted details of the web browser story in Windows 10.

There will be two browsers and two rendering engines in Windows 10:

  • Project Spartan is the “universal app” version of the browser, the successor to Metro IE.
  • Internet Explorer will remain.

The two rendering engines are EdgeHTML (new) and MSHTML (old). Both engines can be used in either browser, so even the “Project Spartan” browser has a compatibility mode. Both browsers default to the new rendering engine.

image

However, only Internet Explorer supports features such as ActiveX controls and Browser Helper Objects, so some legacy web sites and applications will only work properly in IE.

For details of what EdgeHTML supports, see the status page.

Microsoft has been plagued by the “coded for IE” problem, where sites deliver inferior content if IE is detected – even where IE is fully capable of rendering the up-to-date content. Hence this comment:

Edge mode introduces an interoperable UA string designed to get today’s modern Web content, and to avoid old IE-only content. We’ve also spent a lot of time ensuring that the IE platform behaves like modern Web content expects.

It is unfortunate that Windows 10 will still have two web browsers, since this is a point of confusion for users. A lot will depend on presentation and defaults; if Microsoft can hide desktop IE so it is only used by those organisations that know they need it, that would be a good thing – presuming that Project Spartan offers a decent experience when used on the desktop.

There is a debate in the comments to Weber’s post about whether Microsoft should cease developing its own browser:

This looks like chrome. Please contribute to chrome if you want to make the web browser better. All this does is increase development costs by having to support another browser. Enough damage has been done by IE. Please stop development.

and the counter:

No, sane developers don’t want a single engine.

People want different engines that pushes each other forward, make things in a standard way (not like Chrome) and allows to check if the problem is their code or a bug in the browser.

My perspective on this is that Google already dominates web search and if Microsoft were to adopt its browser engine, there would be increased risk of Google dictating whatever standards suit its own purpose – just as Microsoft did in the dark days of stagnant IE development. Microsoft’s energetic development of IE is actually good for Google and for the rest of us.

microsoft, software development, windows

Windows 10 and HoloLens: quick thoughts and questions following the January reveal

3 Comments

Microsoft is revealing its Windows 10 plans in stages, presumably in part to build up expectation and get feedback, and in part because some pieces are ready to show before others.

image

Today in Redmond Microsoft shared a number of new features. In quick summary:

Windows 10 will be a free upgrade for all Windows 7 and 8.x users, at least for the first year.

Comment: this is necessary since the refusal of Microsoft’s user base to upgrade from Windows 7 is a strategic roadblock. For example, Windows 7 users cannot use Store apps, reducing the market for those apps. It is more important to persuade users to upgrade than to get upgrade revenue. Windows 10, of course, will have to be compelling as well as free for this initiative to work, as well as providing a smooth upgrade process (never a trivial task).

Windows to evolve to become a service Executive VP Terry Myerson says this in this post:

Once a Windows device is upgraded to Windows 10, we will continue to keep it current for the supported lifetime of the device – at no additional charge. With Windows 10, the experience will evolve and get even better over time. We’ll deliver new features when they’re ready, not waiting for the next major release. We think of Windows as a Service – in fact, one could reasonably think of Windows in the next couple of years as one of the largest Internet services on the planet.

And just like any Internet service, the idea of asking “What version are you on?” will cease to make sense – which is great news for our Windows developers.

Comment: What does this mean exactly, beyond what we already have via Windows Update? What does Myerson mean by “the supported lifetime of the device”? What are the implications for the typical three-year Windows release cycle? I hope to discover more detail soon, though when I enquired whether there will be, for example, a “Windows 11” I was told, “We aren’t commenting beyond what’s stated in post that you reference.”

Project Spartan (a code name) is a new browser developed as a universal app – this means an app built for the Windows Runtime (“Metro”) environment, though in Windows 10 these also run in a window on the desktop, blurring the sharp distinction you see in Windows 8. Project Spartan features, according to Microsoft’s Joe Belfiore, a new rendering engine along with features includes the ability to annotate web pages with keyboard or touch/stylus, and the ability to save pages for reading offline. There will also be “enterprise mode compatibility for existing web apps”, which means that old IE will live on.

image

Comment: Creating a new browser is a bold step though it may be as much for marketing reasons as anything else, since IE has a tarnished reputation. The advantages of the new rendering engine, and the way compatibility will be handled, are not yet clear. Another point of interest is compatibility issues caused not only by the new engine, but also by running in sandboxed universal app environment. Looking forward to more detail on this.

Windows 10 across PC, tablet and mobile: the OS will have the same name on all three, universal apps (like a new mobile Office) will run on all three, and there are new efforts to synchronize content. For example, notifications will sync across phone and PC/Tablet.

Comment: Sounds good, but there are a few downsides. One is that Windows Phone is tied to the same release cycle as full Windows, which is rather slow. Currently Windows Phone is falling back as it waits for Windows 10 in respect of both operating system upgrade and also the universal app version of Office – which is already available for iOS and Android. CEO Satya Nadella said today that there will be new “flagship” Windows phone devices, which is good news for what is currently a neglected platform, but it will be hard for the platform to thrive if it is constantly waiting for the next big Windows update. Update: if “Windows as a service” means no more monolithic upgrades but constant incremental improvement, perhaps this will not be the case. Watch this space.

Cortana coming to Windows PC and tablet: we saw Microsoft’s digital assistant, powered by Bing search, demonstrated on full Windows.

Comment: Cortana is impressive and fun, but I am not sure how much the feature enhances the platform. On the phone I do not use it much; the problem is that speaking to your phone “what meetings to I have today” and getting a spoken response is a great demo, but in practice it is easier to glance at the calendar, especially as voice control only works in quiet scenarios. The other aspect of Cortana is the personalisation it brings to things like web search or reminders; more data about our preferences and activities can bring some magic. This is Google Now territory, and while Microsoft’s approach to privacy may be preferable, Google will be hard to match in respect of the amount of data it can draw upon.

DirectX 12: Microsoft showed a demo of its latest DirectX graphics API, claiming up to 50% better performance and up to 50% less power consumption.

Comment: this is solid good news. If games run best on Windows 10 a significant enthusiast community will want to upgrade right away. Further, DirectX is not just for games.

Xbox One integration: Microsoft showed how Xbox Live team or competitive games can work across Xbox One and PC, and how games can be streamed from XboxOne so that the console becomes a kind of games server for your Windows 10 tablets and PCs. Xbox One will also run universal apps.

Comment: Better integration between Windows devices and Xbox is long overdue and can help to promote both. Xbox One though has a bit of a Windows 7 problem of its own, with Xbox 360 remaining popular simply because of the huge numbers of games that have not been ported. If only Microsoft could introduce backwards compatibility …

Surface Hub: this is a giant 84”, 4K display wall-hanging PC which you can use as an interactive whiteboard for meetings and so on. It seems to be the next innovation from the Perceptive Pixel folk who also developed the table-top Surface device.

image

Comment: Looks cool, but it will be expensive. May help to encourage businesses to keep faith with the Windows client.

Microsoft HoloLens: this was the big reveal, a secret project that, we were told, has been developed in the basement of the Microsoft Visitor Center on its Redmond campus.

image

HoloLens is a headset which enables 3D augmented reality: projected images are seen like holographic images in the space around you, and you can interact by gesture detected by cameras and motion sensors in the headset. Look carefully at the following image:

image

In this example, the demonstrator is assembling a quad copter using a palette of 3D components in Holo Studio, an application which uses the technology. However, note that you only see the quad copter through the HoloLens headset, the image from which in this case is merged with a view of the demonstrator herself using a custom camera:

image

If you had been in the room, you would see the quad copter only on the screen, not in the room itself. Therefore I suspect this is more accurately described as augmented reality than holography, though the scene does look holographic if you are wearing the headset.

In a final flourish, Microsoft a 3D printed version of the quad copter which duly flew up and down; I am sure the motor and so on was NOT 3D printed, but it made a lovely demo.

Apparently NASA loves the technology and will be using it with Mars Rover in July in a project called OnSight – read the NASA release.

image

Bringing it down to earth, Microsoft also stated that all universal apps will have access to the HoloLens APIs.

Comment: This looks amazing and must have potential for all sorts of scenarios: architects, planners, marketing, games and more. The tough question I suppose is how much it has to do with Windows 10 as experienced by most users.

In closing

Microsoft surprised us today and deserves kudos for that. Nobody can accuse the company of lack of innovation; then again, Windows 8 and the original Surface were innovative too, and proved to be a disaster. I do not think Windows 10 will be a disaster; we have already seen in the preview how it is an easier transition for Windows 7 users.

A key thing to note from a developer and technical perspective is that universal apps are right at the centre of the Windows 10 story. That is a good thing in many respects, since we get Store deployment, sandbox security, and a degree of compatibility across phone, PC, tablet and Xbox One. But is the Store app / Universal app platform mature enough to deliver a good experience for both developers and users, bearing in mind that in Windows 8.x it is really not good enough?

Look to Microsoft Build at the end of April, which Myerson said is the culmination of the Windows 10 reveal, to answer that question.

android, audio, reviews, windows

Review: Synology DS415+ Network Attached Storage

Synology’s DS415+ is a NAS (Network Attached Storage) device aimed at small businesses or demanding home users. I have been running this on my own network for the last 6 weeks or so.

image

First, a note about Synology’s product range. Let us say you want a NAS with 4 drive bays. Here are the choices, with current bare NAS prices from Amazon.co.uk:

  • DS414j £252.63: Budget offering, 512MB RAM, 1.2 GHz  dual core ARM CPU, 1 USB 2.0, 1 USB 3.0, 1 1GB Ethernet port. 90W power supply, 32.64W power consumption.
  • DS414 Slim £237.87: Smaller case designed for 2.5″ drives. All the other units here support 3.5″ drives. Given that you can normally tuck your NAS away in a corner, there is limited value in restricting yourself to these smaller drives, but there is also an energy as well as space saving. 512MB RAM, 1.2GHz single core ARM CPU, 2 USB 3.0 ports, 2 1Gb Ethernet ports. 30W power supply, 15.48W power consumption.
  • DS414 £332.83: Core product. 1GB RAM, 1.33 GHz dual core ARM CPU, 1 USB 2.0, 2 USB 3.0, 2 1Gb Ethernet ports, 90W power supply, 28.42W power consumption.
  • DS415 Play £379.99: Home oriented. Benefits from hardware video transcoding. 1GB RAM, 1.6GHz dual core Intel Atom CPU, 3 USB 2.0 ports, 2 USB 3.0 ports, 1 1Gb Ethernet port, 90W power supply, 27.33W power consumption.
  • DS415+ £460.74: Business oriented. 2GB RAM, 2.4GHz quad core Intel Atom CPU, 1 USB 2.0 port, 2 USB 3.0 ports, 1 eSATA port, 2 1Gb Ethernet ports, 100W power supply, 32.64W power consumption.

You can get a more detailed comparison of these four models in this table. Incidentally, I am guessing that in the Synology numbering scheme, the first digit represents the number of drive bays, and the second two digits the year of release.

The 415 models are the latest releases then, and the only ones to use Intel CPUs. The extra cost of the 415+ buys you double the amount of RAM, a quad core CPU, and an eSATA port.

The software is mostly the same on all the devices, Synology’s Diskstation Manager (DSM), currently at version 5.1. It looks as if some limits are lifted with the 415+, for example there is support for 256 iSCSI LUNs on the 415+, versus 10 on the 415 Play. The 415+ also has specifica support for VMWare VAAI (vStorage API for Array Integration) and Windows Server ODX (Offloaded Data Transfer); this enables some storage tasks to be offloaded to the storage system for better performance on the virtualization host.

Why buy a unit like this when you could simply get a server with plenty of drive bays, or with hardware RAID, and install Linux or Windows Storage Server? The two reasons are first, simplicity of operation, and second, low power consumption.

The distinction is not as sharp as it first appears, since a Synology device like this is in fact a server. If you require maximum flexibility and do not care about energy use, a generic server is probably better. If you require only simple network attached storage, such as a large shared folder on the network, a unit like the 415+ is overkill; just get a DS414j or some other brand. On the other hand, if you expect to install and use several apps, the extra for a DS415+ buys you a substantially more capable server.

Another way of looking at this is that the processing power in the DS415+, while still modest compared to a modern desktop PC, is sufficient for some real work, such as running web applications or even a media server with software transcoding.

Setup

image

Unpack the box, and you find the NAS unit, power supply and a couple of ethernet cables. Unclip the front cover and you can see the four drive bays, with caddies which can easily be removed for drive installation.

image

The drive caddies are screwless for 3.5″ drives; just remove the side panels, insert the drive, and replace the side panels to secure.

image

You can also install 2.5″ drives with four screws through holes in the caddy base.

At the rear of the unit, there are dual fans, two Ethernet ports, 2 USB 3.0 ports, eSata port, and the power connector.

image

I fitted four 3TB Western Digital Red drives – currently £89.36 on Amazon – attached the device to the network and powered up. You can than access the NAS management UI with any web browser. Normally, entering diskstation:5000 will find it. The initial setup downloads and installs the latest version of DSM, and offers an instant configuration which is a single large network folder backed by Synology Hybrid RAID (SHR).

image

I accepted this just to try it, and then blew it away in favour of a more flexible configuration.

Diskstation Manager

Synology DSM is a version of Linux. You can access the OS via SSH, or use the browser-based GUI. The GUI is rather well done, and presents a desktop-like environment with a windowing system.

image

The button at top right open a kind of Start menu:

image

Applications are installed and removed through the Package Center:

image

Generally, you should use only the Package Center to manage applications, though terminal access can be useful for troubleshooting, cleanup, or tweaking settings if you know what you are doing.

Since packages are only available from Synology, you are limited to those applications which are supported, unless you do a manual install:

image

Even a manual install has to be in the Synology package format (an archive with appropriate metadata). Some packages, such as the Plex media server, are available for download as manual installs, though may need tweaking to install correctly.

Third party developers can create packages, free or paid, and submit them to Synology for approval.

If an application is updated, it can take a while before the Synology package is updated. This could be a problem if, for example, a critical security bug is found in an application running on a Synology device exposed to the internet. There are not a huge number of packages available. I counted 63 in the DS415+ Package Center. However, this does include everything you need for a basic business server, including a mail server, DNS Server, LDAP Directory Server, Drupal CMS, SugarCRM, web server with PHP and MySQL, Tomcat application server, and more.

On the multimedia side, there are applications for serving audio and video, a DLNA media server, and Logitech Media Server (also known as Squeezebox Server).

There are several backup applications, including one for Amazon’s Glacier service (low-cost cloud storage).

Storage management

The primary role of a Synology device is for storage of course, and this is configured through the Storage Manager. Configuration begins with Disk Groups, which represent one or more physical drives in a RAID configuration.

image

There are several supported RAID configurations:

SHR: Synology Hybrid RAID with 1- or 2- disk fault tolerance. You need at least 4 drives for 2-disk tolerance.

RAID 0: disk striping, no fault tolerance

RAID 1: drive mirroring

RAID 5: 1-disk fault tolerance

RAID 6: 2-disk fault tolerance

RAID 10: RAID 0 across mirrored drives, 1-disk fault tolerance with high performance.

What is SHR? There is an explanation here. The high-level story is that SHR is more efficient with drives of varying capacity, and more flexible when adding new drives. It is not proprietary and apparently data can be recovered if necessary by mounting SHR drives in a Linux PC (provided no more than one drive has failed).

You set the RAID level when you create a disk group. Once you have a disk group, you can create volumes or iSCSI targets on that group.

I was interested in trying iSCSI. I have a desktop PC that is running out of space. I created a 1500GB iSCSI target and mounted it on the PC using the iSCSI initiator in Control Panel. It worked perfectly, and a new drive appeared in Disk Management.

image

Is this sensible, or should you just use a network folder which is more flexible, since it is shared storage? An iSCSI target behaves like a local drive, which can be an advantage, but iSCSI is mostly used for servers where centralising storage is convenient. You should also use a dedicated network for iSCSI, so it is probably not a great idea for a desktop PC.

I compared performance. On simple tests, such as time taken to copy a file, there was little advantage; in fact, my iSCSI drive was slightly slower: 61.2 MB/s vs 76.4 MB/s for a shared folder.

I tried ODX, copying a file from one iSCSI drive to another. Capturing the copy thermometer was a challenge, as it was near-instant:

image

In general, I have been very happy with the performance of the NAS.

Folder permissions

My local network uses Active Directory (AD), so I was keen to set up permissions on the NAS using AD. Connecting a Linux server to AD can be a problem, and at first the Synology would not play. I connected it, seemingly successfully, but it would not see any users. There are threads on the Synology forums showing users with similar problems. The fix for me was to enter my Domain Controllers as IP numbers rather then FQDNs (fully qualified domain names). Since then it has worked perfectly, though DSM shows the Domain Server Type as “NT4 Domain”, puzzling when my DCs are on Server 2012 R2.

Once connected, you can set folder permissions using the Synology File Station package. First, create the shared folder, then right-click the folder and choose Permissions.

image

Apps and Applications

Aside from the storage services, the main application I run on the Synology is Logitech Media Server (LMS). This used to run on a Windows server, and actually runs much better on the Synology. Search is quicker, the server is more responsive, and it is more reliable.

I tried the Synology audio and video applications, and the media server. There are various companion mobile apps, such as DS Audio and DS Video, for media playback.

image

The apps I tried worked well for me, though I am sticking with LMS for home music streaming.

Final words

I have no complaints about the DS415+, which has performed well so far. Browsing through the user forums though, I have noticed some areas of difficulty. One is that the Cloud Station service, which synchs files between your NAS, computers and mobile devices, is notorious for consuming disk space. Users find their drives filling up even though the total size of their files is much less than the available space. Currently, the best advice seems to be not to use Cloud Station.

The general issue with a system like this is that the friendly GUI is great while everything is working, but if something goes wrong and you have to dive into Linux, the ease of use disappears. That is worth noting if you plan to use this as the main server in a small business (beyond storage), unless someone there has the necessary troubleshooting skills.

The device does tick a lot of boxes though: resilient storage, excellent performance, low power consumption, flexible configuration, AD integration, and enough power to run something like Logitech Media Server without blinking.

Recommended.