I just installed Windows 10’s April 2018 update, version 1803.
Part of this update entails removing XPS reader software that was part of all previous versions of 10, and instructing us to find an app in the Store for it.
I download Microsoft’s “Reader” app and install it from the Store.
Opening an XPS file with the new app brings up an error message… that I have to use XPS reader (the one installed with Windows).
Agfh! Is Microsoft trying to annoy me?
While perpetually scorned by people, for no real reason, Microsoft’s search engine “Bing” has a few tricks up its sleeve.
I was looking through my blog stats one day…
Technical post here. I noticed this obnoxious combination while using Firefox on Windows 10 recently (within the past week).
We all know that parts of a system that are used the least are generally the worst. They get the least attention and have the lowest priority when triaging bugs. In some cases they are so rarely seen that they don’t even get bug reports written about them. Vide the now notorious Windows 3.x font addition dialog that lasted until Windows Vista.
Here is a less egregious example from Windows 10 (current version, 1511):
Note the background color problem under the permissions section of the dialog. I suspect that it has been there since Windows 98 or something. If it was removed, this would look fine. Maybe in the next version of Windows, the anniversary update, they will improve this?
I am not mentioning the UNIX style permissions because that is a function of the FTP server, rather than the Windows FTP client.
I was bored and my PC could use a cleaning, I determined to “reset” Windows. This is something new in Windows 8 that was carried over to Windows 10 (unlike the “refresh” option) that essentially reinstalls Windows in place without having to boot from install media.
In reviewing my dayly “dashboard” to see who had been reading my blog, I found out that WordPress doesn’t like the copyright symbol (©) in post tituls:
I have not yet dared to try a post with ‘;– in it yet, to see if it is SQL vulnerable. I think (hope?) this is just a character encoding problem.