Category: windows

USBasp driver for Windows 10

In the past I used USBtiny and USBasp programmers to flash Atmel microcontrollers. Under Windows 10 the programmers did not work, even though Windows 10 seemed to detect them correctly.
It turns out Windows 10 does not use/fetch the correct drivers.
To make things work again most folk use Zadig a tool which automatically installs some legacy drivers typically used for USB programmer dongles.

USB driver installation with Zadig

After the drivers are installed Windows 10 finally detects my USBasp programmer dongle as it should.

References:
[1] https://rayshobby.net/dead-simple-driver-installation-for-usbasp-and-usbtiny-on-windows/
[2] https://zadig.akeo.ie

WSL on Windows 10

There is a new kid in town when it comes to “doing Linux under Windows”. Up to now there was primarily Cygwin and MinGW. But for a while now Microsoft offers the Windows Subsystem for Linux (WSL). I personally think the name should be the other way around (LSW) but what do I know.

To enable WSL under Windows 10 you first need to enable the required feature.
1. From the start menu go to “Apps and Features”
2. Scroll to the bottom and select “Programs and Features”
3. Click “Turn Windows features on or off” on the left side.
4. Set the check mark on “Windows Subsystem for Linux”
5. Finally a reboot is required for the changes to take effect.

That’s it. Almost. Now we need to install a Linux distribution to run. WSL only brings the environment for Linux to “run on” Windows 10, but there is no default distro included.
The easiest way is to go the App Store and install one of the available distros, like Ubuntu 18.04.
Alternatively you can download the required .appx package and install it manually using the PowerShell (Administrator permissions required) with
Add-AppPackage <filename&gt;.appx

Let’s see when Windows will completely adopt the Linux Kernel.

More Windows 10 Issues

On my new Windows 10 installation I came across a few more issues:

LibreOffice did have a nasty offset where the mouse pointer would click way above where it was pointing. The solutions to this bug was to disable OpenGL rendering as described here.

Another bad experience was with VirtualBox which would sometimes boot up virtual machines with corrupted graphics where nothing is readable or even recognizable. The solution to this behavior seems to be to set the “Override high DPI scaling behavior” setting to “Application”; the setting can be found by right clicking on the VirtualBox shortcut/executable &gt; Properties &gt; Compatibility &gt; Override high DPI scaling behavior. I found the solution here.

© bananatronics.org