Single package combines five years of updates into a single patch.
Anyone who's installed Windows 7 any time in the last, oh, five years or so probably didn't enjoy the experience very much. Service Pack 1 for the operating system was released in 2011, meaning that a fresh install has five years of individual patches to download and install. Typically, this means multiple trips to Windows Update and multiple reboots in order to get the system fully up-to-date, and it is a process that is at best tedious, typically leading one to wonder why, at the very least, it cannot pull down all the updates at once and apply them with just a single reboot.
The answer to that particular question will, unfortunately, remain a mystery, but Microsoft did today announce a change that will greatly reduce the pain of this process. The company has published a "convenience rollup" for Windows 7 Service Pack 1 (and Windows Server 2008 R2), which in a single package contains all the updates, both security and non-security, released since the Service Pack, up through April 2016. Installing the rollup will perform five years of patching in one shot.
In other words, it performs a very similar role to what Windows 7 Service Pack 2 would have done, if only Windows 7 Service Pack 2 were to exist. It's not quite the same as a Service Pack—it still requires Service Pack 1 to be installed, and the system will still report that it is running Service Pack 1—but for most intents and purposes, that won't matter. Microsoft will also support injecting this rollup into Windows 7 Service Pack 1 system images and install media.
A patent complaint that Segway filed with the US International Trade Commission in 2014 has resulted in a wide-ranging order banning "personal transporters" that infringe some of its patents.
On Wednesday, the ITC issued a general exclusion order banning several types of the self-balancing devices often called "hoverboards." The case could affect the whole market, since a general exclusion order is the commission's most powerful remedy and can affect even parties not involved in the investigation.
There's also a limited exclusion order issued directly against the products of several Chinese companies sued by Segway. Only one of those companies responded and fought the case at all, while the others were in default.
The general ban applies to any device infringing US Patent No. 8,830,048, which could be a whole lot of products. The first claim of that patent describes a transporter with a drive, wheels, a "sensor for sensing the pitch of the user support," "yaw input," and a "control loop" for determining torque. Claim 2, also included in the exclusion order, describes the same thing, where the "user support" includes a handlebar.
Earlier this week, the team behind Ashes of the Singularity released an updated version of its early access game, which updated its features and capabilities. With support for DirectX 11 and DirectX 12, and adding in multiple graphics card support, the game featured a benchmark mode that got quite a lot of attention. We saw stories based on that software posted by Anandtech, Guru3D andExtremeTech, all of which had varying views on the advantages of one GPU or another.
That isn’t the focus of my editorial here today, though.
Shortly after the initial release, a discussion began around results from the Guru3D story that measured frame time consistency and smoothness with FCAT, a capture based testing methodology much like the Frame Rating process we have here at PC Perspective. In that post on ExtremeTech, Joel Hruska claims that the results and conclusion from Guru3D are wrong because the FCAT capture methods make assumptions on the output matching what the user experience feels like. Maybe everyone is wrong?
First a bit of background: I have been working with Oxide and the Ashes of the Singularity benchmark for a couple of weeks, hoping to get a story that I was happy with and felt was complete, before having to head out the door to Barcelona for the Mobile World Congress. That didn’t happen – such is life with an 8-month old. But, in my time with the benchmark, I found a couple of things that were very interesting, even concerning, that I was working through with the developers.