OSnews

A proposed change to Chrome would neuter content blockers: While we’re still waiting for a Chromium-powered version of Microsoft Edge to materialize, we do know that it is intended that the browser will end up supporting Chrome extensions. However, according to a draft of the Chrome Extension Manifest V3 implementation, it appears that there could be some bad news for content blocking solutions designed for the browser. According to the draft, use of the webRequest API currently used by content blockers “will be discouraged (and likely limited) in its blocking form” while a non-blocking implementation would allow nothing more than observation of network activity. Instead, developers will have access to the new declearativeNetRequest API. However, the proposal has drawn the ire from content blocker heavyweights such as Raymond Hill, best known as the author of uBlock Origin and uMatrix. This clearly feels like a slippery slope where eventually all forms of content blocking will be either made impossible or very limited. Google is an advertising company, after all, and content blockers must in some way influence the company’s bottom line. Luckily, there’s always Firefox.

How I modified DOSBox and the original Microsoft Flight Simulator 4 from 1989 to run on my immersive multi-display flight simulator set up. If that simple one-sentence introduction doesn’t get you to read this article from June 2017, nothing will.

Over the weekend, four commits were posted to various parts of Android’s Gerrit source code management, all entitled “Carrier restriction enhancements for Android Q.” In them, we see that network carriers will have more fine-grained control over which networks devices will and will not work on. More specifically, it will be possible to designate a list of “allowed” and “excluded” carriers, essentially a whitelist and a blacklist of what will and won’t work on a particular phone. This can be done with a fine-grained detail to even allow blocking virtual carrier networks that run on the same towers as your main carrier. I’m sure carriers won’t abuse this functionality at all.

Samsung is pushing out a big update to the Gear S3 which introduces a host of new features to the smartwatch. It carries the firmware version R760XXU2DSA1 and also bumps the device to Tizen version 4.0.0.2. The update is currently available in the US, with a wider roll out expected in the coming days. An update like this would normally barely even register on my radar, but the fact of the matter is that Samsung’s smartwatches are one of the very few sets of devices running Tizen – along with Samsung smart TVs.

In the first major example, the French data protection authority announced Monday that it had fined Google 50 million euros, or about $57 million, for not properly disclosing to users how data is collected across its services — including its search engine, Google Maps and YouTube — to present personalized advertisements. The penalty is the largest to date under the European Union privacy law, known as the General Data Protection Regulation, which took effect in May, and shows that regulators are following through on a pledge to use the rules to push back against internet companies whose businesses depend on collecting data. Facebook is also a subject of several investigations by the data protection authorities in Europe. Peanuts for a company like Google, but still – the GDPR at work here.

Given its history and relationship to the Alto, the Star seemed appropriate for my next emulation project. (You can find the Alto emulator, ContrAlto, here). As with the Alto a substantial amount of detailed hardware documentation had been preserved and archived, making it possible to learn about the machine’s inner workings… Except in a few rather important places. Fortunately, Al Kossow at Bitsavers was able to provide extra documentation that filled in most of the holes. Cross-referencing all of this with the available schematics, it looked like there was enough information to make the project possible. This is an amazing project, and the article provides a lot of details about the process of writing the emulator. I’m definitely going to try this out this week to see if I can get it running. I’ve never used the Star, and that’s likely never going to change – they’re rare, expensive, and in museums – so this is the next best thing. I think most of us owe it to ourselves to try this out.

If you’ve been looking at operating systems for the TI-84+, chances are you’ve come across KnightOS. It’s well developed and has plenty of Unix-like features such as filesystems and tasks, and even a C compiler. But maybe that’s not what you want. You want an minimal operating system that allows you to extend it in any way you wish, bonus points if you don’t need to know Z80 assembly to do so. zkeme80 is that operating system, a minimal core with a mostly ANS standard conforming Forth interpreter/compiler. From words covering sprites and graphics, to text and memory access, everything you need to make the next hit Snake clone or RPN-based layer is already there. zkeme80 lowers the barrier of entry for customizing an operating system and enable rapid development cycles. Below the Forth layer, you’ll find two lowest level and highest level languages, Z80 assembly and Scheme. The best assembler is an extensible one, where writing macros should be a joy, not a pain, and Scheme has that macro system. I wish I still had the TI-83 I used back in high school. A friend and I bought a communication cable for our TI-83s so that we could play multiplayer Bomberman during classes. Fun times.

Rather than some designer’s flashy vision of the future, Windows 98 icons made the operating system feel like a place to get real work done. They had hard edges, soft colors and easy-to-recognize symbols. It’s obvious that the icons were meticulously crafted. Each 256-color .ico file includes a pixel-perfect 16×16, 32×32 and 48×48 version that looks equally good on the taskbar and desktop. They are, indeed, quite good. Most platforms from that era had exquisite icon design – think Mac OS 9 or BeOS – and we really seem to have lost some of that usability. I feel like Haiku’s current icon set best captures that same aesthetic, but in a modern coat (and a unique, custom-designed vector icon format).

It’s all being blown way out of proportion. The Fossil deal is not going to fix Wear OS. This is not the acquisition that will lead to a Pixel Watch. In reality, the deal was probably too small to really matter. Let’s pour some cold water on all this optimism. Wear OS is still doomed. I wouldn’t call Wear OS “doomed” per se, but to say it’s not doing particularly well is a massive understatement.

Microsoft is planning to end support for Windows 10 Mobile devices in December. While Microsoft revealed back in 2017 that the company was no longer developing new features or hardware for Windows 10 Mobile, security and software updates have continued. These security updates will now cease on December 10th 2019, and devices will be unsupported after this date. “Windows 10 Mobile, version 1709 (released October 2017) is the last release of Windows 10 Mobile and Microsoft will end support on December 10, 2019,” reads a Microsoft support note that was updated this week. Microsoft is now recommending that Windows 10 Mobile users move to iOS or Android devices. “With the Windows 10 Mobile OS end of support, we recommend that customers move to a supported Android or iOS device,” explains a FAQ on Windows 10 Mobile end of life. After Microsoft pulls support in December, device backups for settings and some apps will continue for three months until March 10th, 2020. Microsoft notes “some services including photo uploads and restoring a device from an existing device backup may continue to work for up to another 12 months from end of support.” It’s yet another one of those moments where Windows Phone dies a little more, and every time, it makes me sad. I was a first-day adopter of both Windows Phone 7.x and 8.x, and to this day I maintain it was the most pleasant to use modern mobile operating system. I’m still sad Microsoft was unable to attract the third party developers required to keep a smartphone platform afloat.

Sailfish OS 3.0.1 has been released. From the release notes: Sipoonkorpi is mainly a bug fixing update, bringing in just a few new features. We’ve added Bulgarian language support and improved the handling of email folders. You can now create light ambiences, and respond to meeting invitations through Exchange and Google. We’ve also tuned up SD card encryption and protected critical Top Menu toggles with the security code. It’s available for Jolla devices and the Xperia X and XA2.

A library that I work on often these days, meshoptimizer, has changed over time to use fewer and fewer C++ library features, up until the current state where the code closely resembles C even though it uses some C++ features. There have been many reasons behind the changes – dropping C++11 requirement allowed me to make sure anybody can compile the library on any platform, removing std::vector substantially improved performance of unoptimized builds, removing algorithm includes sped up compilation. However, I’ve never quite taken the leap all the way to C with this codebase. Today we’ll explore the gamut of possible C++ implementations for one specific algorithm, mesh simplifier, henceforth known as simplifier.cpp, and see if going all the way to C is worthwhile.

Microsoft first unveiled its Microsoft 365 bundle of Windows 10 and Office for businesses and schools back in 2017. While a bundle of buying Office and Windows licenses makes sense for commercial customers, Microsoft is also looking to launch a similar bundle for consumers. Speaking to journalists at a media event earlier this week, attended by The Verge, CEO Satya Nadella gave some hints that Microsoft 365 will appear for consumers. I already have an Office 365 subscription, and the idea of adding Windows to that certainly seems appealing to me. It’s easy, straightforward, and doesn’t require any periodic large purchases either.

Tim Cook, in an op-ed in Time Magazine: In 2019, it’s time to stand up for the right to privacy—yours, mine, all of ours. Consumers shouldn’t have to tolerate another year of companies irresponsibly amassing huge user profiles, data breaches that seem out of control and the vanishing ability to control our own digital lives. This problem is solvable—it isn’t too big, too challenging or too late. Innovation, breakthrough ideas and great features can go hand in hand with user privacy—and they must. Realizing technology’s potential depends on it. That’s why I and others are calling on the U.S. Congress to pass comprehensive federal privacy legislation—a landmark package of reforms that protect and empower the consumer. Last year, before a global body of privacy regulators, I laid out four principles that I believe should guide legislation. If Tim Cook and Apple really cared about privacy, they wouldn’t have thrown 1.2 billion Chinese under the bus by handing over iCloud data to the Chinese government, and by sheepishly refusing to even mention “China” when it comes to Apple’s thin veneer of “privacy first”. Apple’s complete cooperation with the Chinese government makes it very clear that Apple is all too eager to roll over and disregard its privacy chest-thumping the second their own bottom line is at risk. And lest we forget – China is a totalitarian, repressive regime that doesn’t shy away from torture and concentration camps. How many Chinese Apple users have ended up in prison – or worse – because Tim Cook only cares about your privacy if you’re western?

Rumors about a Pixel Watch have abounded for years. Such a device would certainly make sense as Google attempts to prove the viability of its struggling wearable operating system, Wear OS. Seems the company is finally getting serious about the prospect. Today Fossil announced plans to sell its smartwatch IP to the software giant for $40 million. Sounds like Google will be getting a nice head start here as well. The deal pertains to “a smartwatch technology currently under development” and involves the transfer of a number of Fossil employees to team Google. Wear OS is definitely struggling, but it sure isn’t because of lack of trying from Fossil. The company has been churning out a whole wide variety of Wear OS devices, and they offer enough choice in design that anyone can find something they like – at acceptable price points, too. Sadly, like any other Wear OS OEM, they’re held back by a lack of acceptable silicon, since Qualcomm has been unable to deliver a chip that’s even remotely as good as Apple’s wearable SoC. Perhaps Google’s stewardship can address this problem.

Days after a nasty public split with cloud gaming developer Improbable, Unity has reinstated the company’s license and updated its own terms of service to offer what it is calling a “commitment to being an open platform.” “When you make a game with Unity, you own the content and you should have the right to put it wherever you want,” Unity wrote in a blog post explaining the move. “Our TOS didn’t reflect this principle—something that is not in line with who we are.” The new terms of service allow Unity developers to integrate any third-party service into their projects, no questions asked. As a caveat, though, Unity will now distinguish between “supported” third-party services—those Unity ensures will “always well on the latest version of our software”—and “unsupported” third-party services, which developers use at their own risk. Negative publicity can definitely work.

Microsoft has released a new Windows Insider preview build, and it contains a significant chance we’re all going to be happy about. Going forward, we’ll be decoupling Search and Cortana in the taskbar. This will enable each experience to innovate independently to best serve their target audiences and use cases. Some Insiders have had this update for a few weeks now, and we appreciate all the feedback we’ve received about it so far! For those new to this update, when it rolls out to you, you’ll find clicking the search box in the taskbar now launches our experience focused on giving you the best in house search experience and clicking the Cortana icon will launch you straight into our voice-first digital assistant experience. Cortana is useless, and any steps Microsoft takes to get it out of my way is welcome to me.

The early Android Q leaked build we have obtained was built just this week with the February 2019 security patches, and it’s up-to-date with Google’s AOSP internal master. That means it has a ton of new Android platform features that you won’t find anywhere publicly, but there are no Google Pixel software customizations nor are there pre-installed Google Play apps or services so I don’t have any new information to share on those fronts. Still, there’s a lot to digest here, so we’ve flashed the build on the Pixel 3 XL to find out what’s new—both on the surface-level and under-the-hood. This article will focus on all the surface-level changes we’ve found in Android Q. There’s a lot of good stuff in here, most notably a complete redesign of the permissions user interface, as well as even stricter limitations on what applications can do, such as only granting certain permissions while the application in question is in use. There’s also a system-wide dark mode, hints of a DeX-like desktop mode, and a lot more.

Christian Haschek found a Raspberry Pi attached in a network closet at the company he works for, and since nobody knew what it was or where it came from, he and his colleagues decided to investigate. I asked him to unplug it, store it in a safe location, take photos of all parts and to make an image from the SD card (since I mostly work remote). I have worked on many Raspberry Pi projects and I felt confident I could find out what it does. At this point nobody thought it was going to be malicious, more like one of our staffers was playing around with something. Interesting – but worrisome – story.

64-bit CPUs deliver faster, richer experiences for your users. Adding a 64-bit version of your app provides performance improvements, makes way for future innovation, and sets you up for devices with 64-bit only hardware. We want to help you get ready and know you need time to plan. We’ve supported 64-bit CPUs since Android 5.0 Lollipop and in 2017 we first announced that apps using native code must provide a 64-bit version (in addition to the 32-bit version). Today we’re providing more detailed information and timelines to make it as easy as possible to transition in 2019. Important information for Android developers regarding requirements around 64bit support.

“User tracking” is generally contentious in free-software communities—even if the “tracking” is not really intended to do so. It is often distributions that have the most interest in counting their users, but Linux users tend to be more privacy conscious than users of more mainstream desktop operating systems. The Fedora project recently discussed how to count its users and ways to preserve their privacy while doing so. As always, an exceptionally good article from LWN.

We’re excited to announce that map and address-related searches on DuckDuckGo for mobile and desktop are now powered by Apple’s MapKit JS framework, giving you a valuable combination of mapping and privacy. As one of the first global companies using Apple MapKit JS, we can now offer users improved address searches, additional visual features, enhanced satellite imagery, and continually updated maps already in use on billions of Apple devices worldwide. With this updated integration, Apple Maps are now available both embedded within our private search results for relevant queries, as well as available from the “Maps” tab on any search result page. I’m sure Apple users in San Francisco will be very happy with this news. For me, this means there’s no way I’ll be using DuckDuckGo’s location search and other mapping functions – Apple Maps is entirely unusable in The Netherlands, with severely outdated and faulty maps that are outright dangerous. I understand the privacy angle, but I feel like are better, more accurate options than Apple Maps. The world is larger than Silicon Valley.

AnandTech has seen documents and supporting information from multiple sources that show that Intel is planning to release a new high-end desktop processor, the Core i9-9990XE. These documents show that the processors will not be sold at retail; rather they will only be sold to system integrators, and then only through a closed online auction. This new processor will be the highest numbered processor in Intel’s high-end desktop line. The current top processor is the i9-9980XE, an 18 core part with a base frequency of 3.5 GHz and a turbo frequency of 4.0 GHz. The i9-9990XE, on the other hand, is not simply the 9980XE with an increase in frequency. The Core i9-9990XE will be a 14 core processor, but with a base frequency of 4.0 GHz and a turbo frequency of 5.0 GHz. This makes it a super-binned 9940X. This probably means this is very much a low-yield chip Intel can’t make enough of to sell at retail.

According to BuildFeed, which regularly posts about new builds of Windows 10, the first build of a new SKU for foldable devices has been compiled. It comes with the build string rs_shell_devices_foldables.190111-1800, and it’s from the 19H1 development branch. The build number is 18313.1004. The obvious conclusion to draw is that this is for Microsoft’s rumored Andromeda device. While the project was shelved back in July, it was originally for a foldable PC that could fit in your pocket. It’s likely now that it will be a larger device that’s slated for later on this year. Foldable devices are definitely coming this year, but I feel like it might take a while for both users and device and software makers to figure out where, exactly, the fit into our lives.

This post is about vintage gaming in vintage unusual operating systems, focused on Xenix/x86. Tried Hampa’s turnkey xenix86 images while they had been tested in fake86, 8086tiny and other emulators. The installation was surprisingly easy, because most software packages in floppy/tape images are basically in .tar format, so let’s check GAMES 360k floppy image’s content on host. I can’t get enough of articles like these.

With Android 6 (Marshmallow), Google has introduced Doze mode to the base Android, in an attempt to unify battery saving across the various Android phones. Unfortunately, vendors (e.g. Xiaomi, Huawei, OnePlus or even Samsung..) did not seem to catch that ball and they all have their own battery savers, usually very poorly written, saving battery only superficially with side effects. Naturally users blame developers for their apps failing to deliver. But the truth is developers do the maximum they can. Always investigating new device specific hacks to keep their (your!) apps working. But in many cases they simply fall short as vendors have full control over processes on your phone. This is a legitimate problem on my OnePlus 6T. I enjoy using this phone, but the aggressive non-standard application cycle management definitely leads to issues with not receiving notifications or login procedures being restarted as you leave an application. It doesn’t happen often enough to truly bother me, but I can definitely see how people who make more extensive use of their phone than I do run into this issue every day.

Recently I’ve gotten a hold of an old IBM mid-range computer, an AS/400 150. This is an 1997 server very much aimed at businesses, pay-rolling, inventory management and such. It can be used as a multi user system, with users logging in via a terminal. The operating system it runs is OS/400 and that is also the only OS it can run, no Linux available for this system. Of course it comes with all the fun programming languages like COBOL and RPG, all the business classics. It’s compatible with the IBM system/36, so any programs made for an 80’s S/36 machine run without problems on the AS/400 machines. It also looks very much 90s, though I personally like the cover at the back, hiding all ports. Stories like these are always great reads. This is the kind of hardware I eventually want to collect and play around with once I have the space to do so.

According to Mozilla’s plugin roadmap, the firm planned to disable Flash by default in Firefox sometime this year. Now, a new bug filing has revealed that the plugin will be disabled as of Firefox 69 which is due for release on September 3, 2019. Mozilla will disable Flash beginning with the Nightly builds before it works its way down to the Stable channel. The disabling of Flash comes in anticipation of Adobe ending support for its Flash plugin at the end of 2020. Mozilla has said that it will completely remove Flash support for consumer versions of Firefox in early 2020, while the Extended Support Release (ESR) version will have support until the end of the year. In 2021, Mozilla has said that Firefox will refuse entirely to load the plugin due to a lack of security updates from Adobe. Aside from the occasional Flash-based online game, is Flash even a thing these days? Do any of you still use it on a regular basis?

LG is going several steps further by making the TV go away completely whenever you’re not watching. It drops slowly and very steadily into the base and, with the push of a button, will rise back up in 10 seconds or so. It all happens rather quietly, too. You can’t see the actual “roll” when the TV is closed in, sadly; a transparent base would’ve been great for us nerds to see what’s happening inside the base as the TV comes in or unfurls, but the white is certainly a little more stylish. Functionally, LG tells me it hasn’t made many changes to the way the LG Display prototype worked aside from enhancing the base. I didn’t get to ask about durability testing — how many times the OLED TV R has been tested to go up and down, for example — but that’s something I’m hoping to get an answer to. We don’t really talk about TVs all that much on OSNews – it’s generally a boring industry – but this rollable display technology is just plain cool.

Ars Technica reports that software patents might be making a comeback. A landmark 2014 ruling by the Supreme Court called into question the validity of many software patents. In the wake of that ruling, countless broad software patents became invalid, dealing a blow to litigation-happy patent trolls nationwide. But this week the US Patent and Trademark Office (USPTO) proposed new rules that would make it easier to patent software. If those rules take effect, it could take us back to the bad old days when it was easy to get broad software patents—and to sue companies that accidentally infringe them. What could possibly go wrong?

Recently I got an internship doing back-end PHP and Python stuff for a website for my university. It’s a really nice job that I find fun and I’m thankful to have. But… at the same time, doing all this high-level web dev stuff has given me a big itch I need to scratch. That itch being the fun of low level bit fiddling. itch.io’s weekly game jam email came in my inbox and it announced the Mini Jam 4. It was a 48 hour (well, a bit more actually) jam where the restriction was to have graphics like a Game Boy. My perfectly logical and sound reaction to this was to make a Game Boy homebrew, because that seemed neat to do. The themes were “seasons” and “flames”. I’n not a programmer, but I can imagine old consoles like the Game Boy are great platforms to use to expand your programming skills.

Speaking of AMD, the company is on a roll as it also announced a new high-end consumer graphics card, which it says can take on Nvidia’s RTX 2080 graphics card. As it turns out, the video card wars are going to charge into 2019 quite a bit hotter than any of us were expecting. Moments ago, as part of AMD’s CES 2019 keynote, CEO Dr. Lisa Su announced that AMD will be releasing a new high-end, high-performance Radeon graphics card. Dubbed the Radeon VII (Seven), AMD has their eyes set on countering NVIDIA’s previously untouchable GeForce RTX 2080. And, if the card lives up to AMD’s expectations, then come February 7th it may just as well do that. At a high level then, the Radeon VII employs a slightly cut down version of AMD’s Vega 20 GPU. With 60 of 64 CUs enabled, it actually has a few less CUs than AMD’s previous flagship, the Radeon RX Vega 64, but it makes up for the loss with much higher clockspeeds and a much more powerful memory and pixel throughput backend. As a result, AMD says that the Radeon VII should beat their former flagship by anywhere between 20% and 42% depending on the game (with an overall average of 29%), which on paper would be just enough to put the card in spitting distance of NVIDIA’s RTX 2080, and making it a viable and competitive 4K gaming card. AMD has managed to shake up the processor market with their Zen architectures, and it’s high time the same happens to the video card market. Nvidia has basically had this market all to itself for several years now, so hopefully this new Radeon card can shake things up a bit and hold us over until 2020, when Intel will be entering the dedicated graphics card market as well.

During AMD’s CES keynote, the company unveiled some of the details of its upcoming 3rd generation Ryzen processors, which are built on top of the Zen 2 architecture. We don’t have any independent benchmarks quite yet, of course, but the power figures comparing a Ryzen 3 processor to an Intel 9900K are nothing to sneeze at (note that these figures are coming from AMD, so get out your salt). Also, in that same test, it showed the system level power. This includes the motherboard, DRAM, SSD, and so on. As the systems were supposedly identical, this makes the comparison CPU only. The Intel system, during Cinebench, ran at 180W. This result is in line with what we’ve seen on our systems, and sounds correct. The AMD system on the other hand was running at 130-132W. If we take a look at our average system idle power in our own reviews which is around 55W, this would make the Intel CPU around 125W, whereas the AMD CPU would be around 75W. Even assuming these figures are idealised, that’s still a pretty startling difference.

Microsoft is now hard at work on the next feature update for Windows 10, codenamed 19H1 and scheduled for release this April. This update is expected to include yet more changes, new features, and further UI refinements and improvements. Development of this release is almost at the halfway mark, meaning it shouldn’t be long now before 19H1 is marked as “feature complete” internally and a focus on fixing bugs before release begins. This new release is still a few weeks off, but this article is a detailed overview of what’s coming. I personally see a lot of good things in here, but Microsoft’s recent release history when it comes to Windows updates hasn’t exactly been stellar, so the company certainly has something to prove here.

Updates & improvements– Menu, Process manager, CtrlAltDel, Cmd, Faster bootup The release is available from the download page. And just in case you forgot, MenuetOS is a pre-emptive, real-time and multiprocessor operating system written entirely in assembly.

It was recently decided that FreeBSD’s ZFS file-system support would be re-based atop ZFS On Linux. That new “ZFS On BSD” implementation based on ZOL continues moving along and it’s now easier to test thanks to iX Systems and their TrueOS platform. With the ZFS On Linux code-base being more actively maintained and improved upon than the OpenZFS support within the Illumos kernel, FreeBSD developers are working on merging their “ZOB” changes with ZOL. Interesting to see that the Linux implementation sees more active development than the original one – although not entirely surprising.

This release fixes several outstanding bugs in bash-4.4 and introduces several new features. The most significant bug fixes are an overhaul of hownameref variables resolve and a number of potential out-of-bounds memory errors discovered via fuzzing. There are a number of changes to the expansion of $@ and $* in various contexts where word splitting is not performed to conform to a Posix standard interpretation, and additional changes to resolve corner cases for Posix conformance. The most notable new features are several new shell variables: BASH_ARGV0, EPOCHSECONDS, and EPOCHREALTIME. The ‘history’ builtin can remove ranges of history entries and understands negative arguments as offsets from the end of the history list. There is an option to allow local variables to inherit the value of a variable with the same name at a preceding scope. There is a new shell option that, when enabled, causes the shell to attempt to expand associative array subscripts only once (this is an issue when they are used in arithmetic expressions). The ‘globasciiranges’ shell option is now enabled by default; it can be set to off by default at configuration time.

This year at CES, we have a series of announcements from AMD before the company’s keynote presentation. Addressing the company’s mobile offerings, AMD is launching the first parts of the Ryzen 3000-series of processors, focused around the Ryzen Mobile 2nd Gen family for both the general 15W market as well as the high-performance 35W market. On top of this, AMD is also making an announcement regarding how it will address graphics drivers for these platforms, and then some icing on the cake comes from AMD’s venture into Chromebooks. AMD continues its hot streak, and now we even have several new inexpensive Chromebooks running on AMD hardware, a market segment the company wasn’t active in. The future is looking bright for AMD.

Samsung today announced that it has worked with Apple to integrate iTunes movies and TV shows, as well as AirPlay 2 support, into its latest smart TVs. The features will roll out to 2018 models via a firmware update this spring and will be included on new 2019 models. iTunes movie and TV show access will come via a new dedicated app for Samsung’s TV platform, available in over 100 countries. Apple pretty much had to do this, since it’s unreasonable to expect people to buy relatively expensive Apple TV devices to be able to watch iTunes content on their TVs. Several other platforms tend to be built right into TVs or can be added with cheap dongles like the Chromecast, and Apple couldn’t compete with that. Apple has announced that iTunes content will also become available on TVs from other brands.

FreeSync support is coming to Nvidia; at its CES event today, Nvidia announced the GSync-Compatible program, wherein it says it will test monitors that support the VESA DisplayPort Adaptive-Sync protocol to ascertain whether they deliver a “baseline experience” comparable to a GSync monitor. Coincidentally, AMD’s FreeSync utilizes the same VESA-developed implementation, meaning that several FreeSync-certified monitors will now be compatible with Nvidia’s 10- and 20-series GPUs. This is great news, since GSync support requires additional hardware and this increases prices; you’ll find that the GSync version of a display is always significantly more expensive than the FreeSync version.

Happy New Year everyone! I’ve got big plans for my Amiga projects in 2019, but thought I’d start off the New Year with a blog post on a not-particularly “exciting” topic, but an important one nonetheless: backups. As I am experimenting more with my X5000 and Amiga OS 4.1, I’ve been getting particularly “twitchy” that I didn’t have a solid backup/restore plan in place, particularly as some of my experiments will invariably go wrong and I’ll need a way to roll back my changes to a known-good state. I spent a few days researching and implementing a backup strategy that’s ideal for my needs and hopefully there will be something of use to other Amiga owners too. Developing and implementing a solid back-up strategy is not just something that’s important for computers running popular platforms like Windows, Linux, or macOS – there’s countless people who do all kinds of more or less important work on smaller platforms like Amiga OS to whom proper back-ups are just as important. This article is a great resource on how to get started with back-ups for Amiga OS 4.

But sometimes life using DOS was not so great, sometimes you would be using DOS and all of a sudden things like this would happen. This sample also plays a small tune on the PC speaker while it’s printing, so this could be really embarrassing in a office environment. Those bootsector viruses were incredibly resilient – your computer would be just fine, until you put in an older floppy that apparently still had a virus on it. Good times.

HelenOS 0.8.0 has been released. HelenOS is a portable microkernel-based multiserver operating system designed and implemented from scratch. It decomposes key operating system functionality such as file systems, networking, device drivers and graphical user interface into a collection of fine-grained user space components that interact with each other via message passing. A failure or crash of one component does not directly harm others. HelenOS is therefore flexible, modular, extensible, fault tolerant and easy to understand. You can read the release notes to figure out what’s new and improved, and download this new release.

K2 is an academic project OS developed out of the Rice University Efficient Computing Group. Its stated purpose is: “Modern mobile System-on-chip(SoC) often embraces heterogeneous cores that are hosted in separate coherence domains, i.e. no hardware coherence among them. This architecture promises high energy efficiency, however complicates software development, thus preventing the energy efficiency from being harvested by software.” Learn more here.

EmuTOS is designed to run on traditional Atari hardware (ST, TT, Falcon, based on Motorola 68000 or ColdFire microprocessors) and their emulators. It features functionality similar to TOS, which powered the Atari ST and its successors between 1985 and 1994. EmuTOS can run on real hardware, either as ROM replacement or from floppy, or on any Atari emulator such as ARAnyM, Hatari, or Steem SSE. EmuTOS is Free Software, and can run legacy third-party software on emulators without requiring copyrighted Atari ROMs, thereby avoiding legal issues.

Windows 7, released in July of 2009, was a gigantic leap forward in the evolution of the desktop OS. Good enough, it turns out, that a huge number of people and organizations are still using it, despite it being nearly ten years since its release. Back in February, Statscounter proclaimed that according to its analytics, Windows 10 had finally overtaken 7 in marketshare. But these kinds of measurements are never exact. They’re based on counting users that connect to various constellations of sites and services, so there’s going to be some variation depending on who’s counting. In December, though, rival analytics firm Netmarketshare revealed that it’s now also showing Windows 10 overtaking Windows 7 for the first time, with 39.22% share of the total OS market, with Windows 7 at 36.9% and Mac OS 10.14 at 4.73%. A surprising number of die hards (4.5%) are still on Windows XP. When you include mobile OSes into the mix, Windows 10 is still on top, followed by Windows 7, then iOS 12.1

We’ve long suspected that Google’s upcoming operating system, Fuchsia, would join the ranks of Chrome OS (and Android) in its support for Android apps. Today, that suspicion has been confirmed by a new change found in the Android Open Source Project, and we can say with confidence that Fuchsia will be capable of running Android apps using the Android Runtime. This just adds more fuel to the fire for Fuchsia’s future.

Regular readers will have noticed that we’ve been offline for several days. As you can see, during that time, we’ve made some major changes to the site, and though the design has changed substantially, we’ve made even more dramatic changes in the back-end. We are now running our 6th major iteration of OSNews. It all was precipitated by messages from readers we’ve received over the past few weeks alerting us that they’ve been getting spam, phishing attempts, and some weak-sauce cyber-extortion emails at addresses that were unique to their OSNews accounts. Read on for more. It certainly seems like we’ve had a breach. Our best guess is that someone was able to exploit a vulnerability in old, unmaintained code in the site’s content management system, and made off with at least some user data, which may be as little as a few user records or, at worst, our entire database. Your email addresses were in there, and the encryption on the passwords wasn’t up to modern standards (unsalted SHA1). The truth is that once we concluded it was likely that we were breached, our small volunteer team decided it was better to go offline than it was to learn the avenue of exploit, given that we had no interest in continuing to rely on the aged codebase. Other than potential spam, though, we’re not aware of any other nefarious use of your data, we don’t store much beyond email addresses and passwords, but nonetheless, we’ve very sorry that we weren’t more diligent over the years with keeping in lockstep with best practices with respect to site security. Upgrading the site has been long overdue. In fact, we’d made a serious attempt at discontinuing the old CMS a few years ago, and a few years before that, and it got bogged down both times by the fact that we depend on volunteer help and we all have real lives. The OSNews system is old. The last meaningful update to the codebase was in 2008, with much of the logic based on the 2005 “version 3” rewrite of OSNews. File modification times of 2014 or older were almost always small tweaks or bug fixes. The site was largely written for PHP 4 and it never had a proper maintenance plan. We’ve now migrated the site to WordPress. For all its faults, WP is at least a known quantity. Many thanks to Adam Scheinberg for spending so many hours over his winter break migrating the data from the old CMS to WordPress. To be perfectly honest, when contemplating what needed to be done to properly move the site to a new platform, I considered just throwing in the towel and going offline permanently. Revenues from advertising don’t cover expenses, and though this could probably be rectified by exploring more creative sponsorship approaches, I don’t have the time. I’m currently trying to get a startup off the ground. I love being a part of this community, and I’m willing to continue to invest in it, but I only want to keep it going if it’s going to remain vibrant and meaningful. In order to keep your history from the old site, and to make that re-association process as painless as possible, we’ve written a very simple account migration tool. The tool checks your login against a very stripped down version of our old user table and then re-encrypts your password. When you login to the new OSNews site, your password will be encrypted using a modern secure algorithm, which is currently PHP’s password_hash function, which uses Blowfish or Extended DES and can change over time so we don’t repeat any past mistakes. I’d like to conclude this update with a cry for help. The only way to achieve this dream of vibrancy and meaningfulness is with your help. One of the advantages of the new platform is that it will make it easier for us to include new contributors and do experiments. What can you do? Read and comment every day Submit news Share interesting stuff on the site with your friends Write an original article Suggest someone interesting for us to interview, and recommend some questions we can ask Suggest new topics you think we should cover with more regularity Volunteer to be an editor and post news everyday Help us with ideas on how we can make money. (sponsorships, ads, partnerships, whatever) Need a part time job? I’ll hire you to promote the site and manage our sponsorship and advertising relationships.

A former Microsoft intern has revealed details of a YouTube incident that has convinced some Edge browser engineers that Google added code to purposely break compatibility. In a post on Hacker News, Joshua Bakita, a former software engineering intern at Microsoft, lays out details and claims about an incident earlier this year. Microsoft has since announced the company is moving from the EdgeHTML rendering engine to the open source Chromium project for its Edge browser.Google disputes Bakita's claims, and says the YouTube blank div was merely a bug that was fixed after it was reported. "YouTube does not add code designed to defeat optimizations in other browsers, and works quickly to fix bugs when they're discovered," says a YouTube spokesperson in a statement to The Verge. "We regularly engage with other browser vendors through standards bodies, the Web Platform Tests project, the open-source Chromium project and more to improve browser interoperability."While we're unlikely to ever know the real story behind this particular incident, I don't doubt for a second that Google would do something like this.