Subject: General Tech | September 15, 2016 - 06:21 PM | Scott Michaud
Tagged: microsoft, windows 10, Windows Store
If you have developed a Win32 or .NET application, and are interested in publishing it for the Windows Store, then Microsoft has released a tool to translate from the one to the other. There are some obvious concerns about this, which I will discuss later in this post, but most of those are more relevant to society as a whole, versus a single person who writes an app. This used to be called Project Centennial, and it's designed to help users enter the UWP platform with little effort, using the APIs they are comfortable with.
The major concern (from a society standpoint) is that the whole reason why Microsoft doesn't deprecate Win32 is because there's too much of it in use. This conversion process forces the application to only be installed through sideloading, or by uploading it to Windows Store. This is much better than iOS and the now deprecated Windows RT, which don't allow sideloading content, but there's nothing preventing Microsoft from just killing sideloading in five, twenty, or a hundred years. Since that's the only way to express yourself through a native application without a license for Microsoft, you can see what could go wrong if a government tells them that encryption software needs to go away, or a civil rights group attempts to release a controversial work of art.
Again, as I said earlier, this is a society issue, though. For interested developers, the tool is a way to bring your old software to a new distribution method. People like Tim Sweeney will probably say “no thanks” for political reasons, but, if that's not a concern for you, the tool exists.
DesktopAppConverter is free on the Windows Store.
Subject: General Tech | August 22, 2016 - 01:26 PM | Jeremy Hellstrom
Tagged: microsoft, microsoft rewards, windows 10, bing, edge
If you remember Bing Rewards then this will seem familiar, otherwise the gist of the deal is that if you browse on Edge and use Bing to search for 30 hours every month you get a bribe similar to what credit card companies offer. You can choose between Skype credit, ad-free Outlook or Amazon gift cards, perhaps for aspirin to ease your Bing related headache; if such things seem worth your while. The Inquirer points out that this is another reminder that Microsoft tracks all usage of Edge, otherwise they would not be able to verify the amount of Bing you used.
Then again, to carry on the credit card analogy ...
"Microsoft Rewards is a rebrand of Bing Rewards, the firm's desperate attempt to get people using the irritating default search engine, and sure enough the bribes for using Edge apply only if you use Bing too."
Here is some more Tech News from around the web:
- Plexistor unveils storage-stack-perplexing PMoF tech @ The Register
- Building A DIY Heat Pipe @ Hack a Day
- Microsoft buys Genee AI calendaring app and will close it down in a matter of days @ The Inquirer
- Two-speed Android update risk: Mobes face months-long wait @ The Register
Subject: General Tech | August 19, 2016 - 01:06 PM | Jeremy Hellstrom
Tagged: yuy2, windows 10, skype, microsoft, idiots
In their infinite wisdom, Microsoft has disabled MJPEG and H.264 encoding on USB webcams for Skype in their Adversary Update to Windows 10, leaving only YUY2 encoding as your choice. The supposed reasoning behind this is to ensure that there is no duplication of encoding which could lead to poor performance; ironically the result of this change is poor performance for the majority of users such as Josh. Supposedly there will be a fix released some time in September but for now the only option is to roll back your AU installation, assuming you are not already past the 10 day deadline. You can thank Brad Sams over at Thurrott.com for getting to the bottom of the issue which has been plaguing users of Skype and pick up some more details on his post.
"Microsoft made a significant change with the release of Windows 10 and support for webcams that is causing serious problems for not only consumers but also the enterprise. The problem is that after installing the update, Windows no longer allows USB webcams to use MJPEG or H264 encoded streams and is only allowing YUY2 encoding."
Here is some more Tech News from around the web:
- lackberry and Windows phones hold just 7 percent of smartphone market combined @ The Inquirer
- Arduino + Software Defined Radio = Millions of Vulnerable Volkswagens @ Hack a Day
- Cisco joins Microsoft and flings out Skype-friendly collab app @ The Register
- Fujifilm X-T2 Mirrorless Camera Hands-On Preview @ TechARP
- instax SHARE SP-2 Mobile Printer Hands-On Preview @ TechARP
- Linksys LGS318P 18-Port Smart PoE+ Gigabit Switch Review @ NikKTech
- MSI Pro-Modding competition and GT73 VR at Gamescom 2016 @ Kitguru
Subject: General Tech | August 11, 2016 - 05:42 PM | Scott Michaud
Tagged: windows 10, microsoft
Previously, Microsoft said that they will end support for Skylake-based processors on Windows 7 and Windows 8.1 before the OS's extended support date. Later processors, like Intel's Kaby Lake and AMD's Bristol Ridge, will not be supported on 7 and 8.1 at all. To use those processors, their associated devices will need to be running Windows 10 (or, you know, Linux or something).
This has just changed for Skylake, but not for Kaby Lake and Bristol Ridge. Skylake will now be supported through the entire life-cycle of Windows 7 (January 14, 2020) and Windows 8.1 (January 10, 2023). This is particularly good because Skylake was already released and in the hands of users when they first announced pulling the plug. Now users will know before they purchase their hardware (albeit not before many have purchased a retail copy of Windows 7 or Windows 8.x with transfer rights that intend to continually upgrade beyond Skylake or to AMD's Zen architecture) that Microsoft will not support it outside of Windows 10.
Subject: General Tech | August 9, 2016 - 05:21 PM | Scott Michaud
Tagged: windows 10, microsoft
According to ComputerWorld, Microsoft has decided that their 30-day rollback period is too long, and so they reduced it to 10 days with version 1607. Honestly, 30 days seemed a bit too long to leave (in my case) 30 GB of crap laying around your main drive, especially considering a new build is dropped to the public once every six to nine months or so. They should have an interface for users to easily delete early, and maybe even a power-user tool to move it to external storage or something.
This should not affect users who upgrade from Windows 7 and 8.x, unless the rules have changed since the November (1511) update. A non-Windows Insider machine will only install a new build of Windows 10 if the previous install was a clean install, or if the rollback period has already timed out. Also, users can still return to Windows 7 or Windows 8.x by performing a clean install with their respective product key, and Microsoft still provides ISOs on their website even if the user lost their install DVD.
That said, Microsoft still should make this much more clear in their interface, though. Looking at the Settings page, above, there doesn't seem to be any indication that my time is running out. Not cool.
Subject: Graphics Cards | August 2, 2016 - 07:37 AM | Scott Michaud
Tagged: windows 10, vulkan, microsoft, DirectX 12
Update (August 3rd @ 4:30pm): Turns out Khronos Group announced at SIGGRAPH that Subgroup Instructions have been recently added to SPIR-V (skip video to 21:30), and are a "top priority" for "Vulkan Next". Some (like WaveBallot) are already ARB (multi-vendor) OpenGL extensions, too.
Original post below:
DirectX 12's shading language will receive some new functionality with the new Shader Model 6.0. According to their GDC talks, it is looking like it will be structured similar to SPIR-V in how it's compiled and ingested. Code will be compiled and optimized as an LLVM-style bytecode, which the driver will accept and execute on the GPU. This could make it easy to write DX12-compatible shader code in other languages, like C++, which is a direction that Vulkan is heading, but Microsoft hasn't seemed to announce that yet.
This news shows a bit more of the nitty gritty details. It looks like they added 16-bit signed (short) and unsigned (ushort) integers, which might provide a performance improvement on certain architectures (although I'm not sure that it's new and/or GPUs exist the natively operate upon them) because they operate on half of the data as a standard, 32-bit integer. They have also added more functionality, to both the pixel and compute shaders, to operate in multiple threads, called lanes, similar to OpenCL. This should allow algorithms to work more efficiently in blocks of pixels, rather than needing to use one of a handful of fixed function calls (ex: partial derivates ddx and ddy) to see outside their thread.
When will this land? No idea, but it is conspicuously close to the Anniversary Update. It has been added to Feature Level 12.0, so its GPU support should be pretty good. Also, Vulkan exists, doing its thing. Not sure how these functions overlap with SPIR-V's feature set, but, since SPIR was original for OpenCL, it could be just sitting there for all I know.
Subject: General Tech | August 1, 2016 - 06:33 PM | Scott Michaud
Tagged: windows 10, microsoft
Remember, folks, that “the road to Hell is paved with good intentions”. Microsoft has been trying to shed their stigma as a giant source of malware, but all solutions have side-effects, and those side-effects can have damaging consequences. When you believe that you or someone else is doing good, that is when you should be extra cautious, not less. It's a source of complacency.
With tomorrow's Windows 10 Anniversary Update, Microsoft will require kernel-mode drivers to be signed by them on systems with Secure Boot enabled. This change will not affect PCs that have been upgraded from a previous version of Windows, including Windows 10 1507 and Windows 10 1511. That said, this could be a concern for those (like me) who are planning to clean install soon.
To me, this doesn't look like it will be that big of a deal. Hobbyists should be able to manage with either disabling Secure Boot, if their system allows it, or by fitting their driver around the user-mode framework. It might cause an issue with hotfix graphics drivers, though, which are pushed out before getting signed by Microsoft.
Also, if Microsoft changes their driver signing policy in the future, then this
is could be (Update @ 7:30pm ET: original verbage was a little too strong) huge leverage against anyone attempting to circumvent it (such as implementing a graphics API that outperforms whatever DirectX version they have at the time -- see how Vulkan is not allowed on MacOSX). Even if you trust Microsoft now, you need to think about what Microsoft in 10+ years can do if they choose to.
Subject: General Tech | July 30, 2016 - 06:37 PM | Scott Michaud
Tagged: microsoft, windows 10
For the majority of users, the Windows 10 free upgrade period has just ended. That said, Microsoft is extending the offer for a specific group of people: those who use assistive technologies, such as text-to-speech software for those with visual impairments. They are being intentionally vague with which AT software allow users to qualify, which makes sense, because being pedantic to users with disabilities after offering it to everyone (sometimes like a hot potato) for a whole year wouldn't be the best PR.
They haven't yet announced an end date for this new offer. They also haven't really discussed why they are making this exemption, although they do promote the upcoming Anniversary Update several times, with its new accessibility features highlighted. This makes me think that, while of course Microsoft is going to namedrop the new build whenever possible, they might have found that users were hesitant to upgrade to 1507 and 1511 because of accessibility concerns. Since the general public upgrade offer ended just before the Anniversary Update, they might be allowing those users to jump aboard Windows 10 even though their disability prevented them from using 1511.
Either way, it's a nice extension to make.
Subject: Editorial | July 28, 2016 - 01:03 PM | Ryan Shrout
Tagged: XSPC, wings, windows 10, VR, video, titan x, tegra, Silverstone, sapphire, rx 480, Raystorm, RapidSpar, radeon pro ssg, quadro, px1, podcast, p6000, p5000, nvidia, nintendo nx, MX300, gp102, evga, dg-87, crucial, angelbird
PC Perspective Podcast #410 - 07/28/2016
Join us this week as we discuss the new Pascal based Titan X, an AMD graphics card with 1TB of SSD storage on-board, data recovery with RapidSpar and more!!
The URL for the podcast is: http://pcper.com/podcast - Share with your friends!
- iTunes - Subscribe to the podcast directly through the Store (audio only)
- Google Play - Subscribe to our audio podcast directly through Google Play!
- RSS - Subscribe through your regular RSS reader (audio only)
- MP3 - Direct download link to the MP3 file
Hosts: Ryan Shrout, Allyn Malventano, Sebastian Peak, and Josh Walrath
Make Sure You Understand Before the Deadline
I'm fairly sure that any of our readers who want Windows 10 have already gone through the process to get it, and the rest have made it their mission to block it at all costs (or they don't use Windows).
Regardless, there has been quite a bit of misunderstanding over the last couple of years, so it's better to explain it now than a week from now. Upgrading to Windows 10 will not destroy your original Windows 7 or Windows 8.x license. What you are doing is using that license to register your machine with Windows 10, which Microsoft will create a digital entitlement for. That digital entitlement will be good “for the supported lifetime of the Windows 10-enabled device”.
There's three misconceptions that kept recurring from the above paragraph.
First, “the supported lifetime of the Windows 10-enabled device” doesn't mean that Microsoft will deactivate Windows 10 on you. Instead, it apparently means that Microsoft will continue to update Windows 10, and require that users will keep the OS somewhat up to date (especially the Home edition). If an old or weird piece of hardware or software in your device becomes incompatible with that update, even if it is critical for the device to function, then Microsoft is allowing itself to shrug and say “that sucks”. There's plenty of room for legitimate complaints about this, and Microsoft's recent pattern of weakened QA and support, but the specific complaint that Microsoft is just trying to charge you down the line? False.
Second, even though I already stated it earlier in this post, I want to be clear: you can still go back to Windows 7 or Windows 8.x. Microsoft is granting the Windows 10 license for the Windows 7 or Windows 8.x device in addition to the original Windows 7 or Windows 8.x license granted to it. The upgrade process even leaves the old OS on your drive for a month, allowing the user to roll back through a recovery process. I've heard people say that, occasionally, this process can screw a few things up. It's a good idea to manage your own backup before upgrading, and/or plan on re-installing Windows 7 or 8.x the old fashioned way.
This brings us to the third misconception: you can re-install Windows 10 later!
If you upgrade to Windows 10, decide that you're better with Windows 7 or 8.x for a while, but decide to upgrade again in a few years, then your machine (assuming the hardware didn't change enough to look like a new device) will still use that Windows 10 entitlement that was granted to you on your first, free upgrade. You will need to download the current Windows 10 image from Microsoft's website, but, when you install it, you should be able to just input an empty license key (if they still ask for it by that point) and Windows 10 will pull down validation from your old activation.
If you have decided to avoid Windows 10, but based that decision on the above three, incorrect points? You now have the tools to make an informed decision before time runs out. Upgrading to Windows 10 (Update (immediate): waiting until it verifies that it successfully activated!) and rolling back is annoying, and it could be a hassle if it doesn't go cleanly (or your go super-safe and back-up ahead of time), but it might save you some money in the future.
On the other hand, if you don't want Windows 10, and never want Windows 10, then Microsoft will apparently stop asking Windows 7 and Windows 8.x users starting on the 29th, give or take.