Monthly Archive:: November 2018

The mobile platform I chose was put to bed last year, with no new hardware or software features planned. As such, when Microsoft's Corporate Vice President of Windows 10, Joe Belfiore, confirmed that Windows 10 Mobile was no longer of "focus" to Microsoft, I threw in the towel. I've used both iOS and Android devices since then, and I can't say I've found my new home yet. Nothing I've used has been a full-time replacement for my Windows phones.

So, after over a year of hunting for my next true mobile companion, I've temporarily given up the search to go back "home". I jokingly called this Windows 10 Mobile's last voyage, but in a funny way, it's true. Outside of security updates, Windows 10 Mobile is no longer being maintained, meaning there are some issues that are starting to arise.

At a technical level, APEX has been compared to Magisk, which works by mounting folders into the system partition at boot, rather than modifying the system partition directly (which is detectable). APEX appears to extend that same functionality over into core Android packages, separating out things like the Android Runtime into their own packages, separate from the system partition. That means they can be individually and separately updated from the system image.

It's possible that modularized OEM modifications could then be distributed on top of a Google-maintained system image - basically meaning the version of Android itself on a given phone could potentially be updated by Google, but the bits responsible for an OEM skin could be present, updated, and maintained as separate components. That's not to mention how it could ease ROM development, as Treble has.

Microsoft skipped over Release Preview with Windows 10 version 1809, and four days later, the update was pulled from Windows Update. This was mainly due to some users' files being deleted upon upgrading. Moreover, it turned out that the issue had been reported to the Feedback Hub, but it hadn't been upvoted enough times for anyone to notice.

The company published a blog post a few days after that, explaining the issue and saying that you'll now be able to indicate severity of a bug in a Feedback Hub report. There was a slight apology, and a sign that Microsoft will do at least the bare minimum to make sure that this doesn't happen again.

Microsoft hasn't said a word about it since.

While I’ve been having a lot of fun with the new software written specifically for AmigaOS 4, the bulk of my software is still “classic” titles that used to run on my A1200. One of the first things I did when I set up my X5000 was to transfer my old Amiga’s hard drive over so I could continue running this library of software. I also wanted to set up an emulation of my A1200 so I can quickly launch a classic Workbench 3.9 session and pick up all my old projects and bits of code I’d written over the years.

Fortunately, the X5000 and AmigaOS 4 offers a variety of ways of running all your old software.

Some Windows 10 users are having problems with their Pro licenses today, as users on the company's Community Forums and Reddit are reporting that their Windows 10 Pro systems are saying they are not activated, and telling users to install Windows 10 Home instead. Most of the reports appear to be coming from users who obtained the Windows 10 license thanks to the free upgrade path Microsoft offered back in 2015, suggesting that the issue is somehow related to it.

According to some of the reports, while the system says that users have a Windows 10 Home license, the Microsoft Store link in the settings page blocks them from attempting to buy a Pro license.

Microsoft has just released an Emerging issue announcement about current activation issue related to Pro edition recently. This happens in Japan, Korea, American and many other countries.I am very sorry to inform you that there is a temporary issue with Microsoft's activation server at the moment and some customers might experience this issue where Windows is displayed as not activated.

Our engineers are working tirelessly to resolve this issue and it is expected to be corrected within one to two business days.

Apple's latest iOS devices aren't perfect, but even the platform's biggest detractors recognize that the company is leading the market when it comes to mobile CPU and GPU performance - not by a little, but by a lot. It's all done on custom silicon designed within Apple - a different approach than that taken by any mainstream Android or Windows device.

But not every consumer - even the "professional" target consumer of the iPad Pro - really groks the fact this gap is so big. How is this possible? What does this architecture actually look like? Why is Apple doing this, and how did it get here?

After the hardware announcements last week, Ars sat down with Anand Shimpi from Hardware Technologies at Apple and Apple's Senior VP of Marketing Phil Schiller to ask. We wanted to hear exactly what Apple is trying to accomplish by making its own chips and how the A12X is architected. It turns out that the iPad Pro's striking, console-level graphics performance and many of the other headlining features in new Apple devices (like FaceID and various augmented-reality applications) may not be possible any other way.

On the CPU side of things, AMD talked extensively about the forthcoming Zen 2 architecture. The goal of the original Zen architecture was to get AMD, at the very least, competitive with what Intel had to offer. AMD knew that Zen would not take the performance lead from Intel, but the pricing and features of its chips made them nonetheless attractive, especially in workloads that highlighted certain shortcomings of Intel's parts (fewer memory channels, less I/O bandwidth). Zen 2 promises to be not merely competitive with Intel, but superior to it.

Key to this is TSMC's 7nm process, which offers twice the transistor density of the 14nm process the original Zen parts used. For the same performance level, power is reduced by about 50 percent, or, conversely, at the same power consumption, performance is increased by about 25 percent. TSMC's 14nm and 12nm processes both trail behind Intel's 14nm process in terms of performance per watt, but with 7nm, TSMC will take the lead.

The headline feature for 0.4.10 would have to be ReactOS' ability to now boot from a BTRFS formatted drive. The work enabling this was part of this year's Google Summer of Code with student developer Victor Perevertkin. While the actual filesystem driver itself is from the WinBtrfs project by Mark Harmstone, much of Victor's work was in filling out the bits and pieces of ReactOS that the driver expected to interact with. The filesystem stack in ReactOS is arguably one of the less mature components by simple dint of there being so few open source NT filesystem drivers to test against. Those that the project uses internally have all gone through enough iterations that gaps in ReactOS are worked around. WinBtrfs on the other hand came with no such baggage to its history and instead made full use of the documented NT filesystem driver API.

Despite having officially launched back in July, Intel's Xeon E desktop platform has yet to see the light of day in systems casually available to users or small businesses. This should change today, with the official embargo lift for reviews on the parts, as well as the announcement today that SGX-enabled versions are coming for Server use. The Xeon E platform is the replacement for what used to be called the E3-1200 family, using Intel's new nomenclature, and these parts are based on Intel's Coffee Lake (not Coffee Lake Refresh) microarchitecture. We managed to get a few processors in to test, and today we'll start by examining most of the six-core family.

By default, Microsoft Windows isn't even bootable on the new Apple systems until enabling support for Windows via the Boot Camp Assistant macOS software. The Boot Camp Assistant will install the Windows Production CA 2011 certificate that is used to authenticate Microsoft bootloaders. But this doesn't setup the Microsoft-approved UEFI certificate that allows verification of code by Microsoft partners, including what is used for signing Linux distributions wishing to have UEFI SecureBoot support for Windows PCs.

You won't find nearly as many online resources about setting up OpenBSD, because honestly, you really don't need any. Unlike much of Linux and FreeBSD, the included manuals are high quality, coherent, and filled with practical examples. You also need very little third party software to do basic tasks - almost everything you need is well-integrated into the base system.

You'll notice that many features that require toil to achieve on FreeBSD, such as suspend on lid close, working volume buttons, and decent battery life, work out of the box on OpenBSD. You can tell the developers actually use this thing on their personal devices.

And while the official OpenBSD FAQ has all you need to get an installation up and running, it takes a bit of grinding to massage the base installation into a seamless laptop experience. So, I wrote this guide to give you a jump start. Things should just work as long as you have a non-bleeding-edge, semi-mainstream laptop, but ThinkPads are your best bet. Enjoy!

For some years now, one has not had to look far to find articles proclaiming the demise of the GNU General Public License. That license, we are told, is too frightening for many businesses, which prefer to use software under the far weaker permissive class of license. But there is a business model that is based on the allegedly scary nature of the GPL, and there are those who would like to make it more lucrative; the only problem is that the GPL isn't quite scary enough yet.

There are plenty of dead words in languages all over the world, but can the same be said about ghost words? Floating around the murky regions of digitized Unicode values are anywhere between 60 and 100 yūrei-moji - literally, "ghost characters" - haunting the Japanese kanji lexicon.