The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,969 other subscribers

Archive for February 5th, 2018

Odroid-C1 (and likely others): fixing the textmode cursor on the physical console

Posted by jpluimers on 2018/02/05

Somehow the Odroid C1+ does not support a blinking hardware text cursor. Which means that when you logon to the console in text mode, it is really hard to edit the command-line or text files a there is no visual clue where the cursor is.

It took me to find out the cause, but odroid C1 console no “hardware cursor” got me there: [Archive.isArch Linux ARM • View topic – ODROID-C1: No hardware cursor in terminal. The odd thing is that sending escape sequences like mentioned in [WayBackCursor Appearance in the Linux Console LG #137 didn’t fix the problem either. For instance, these didn’t help at all:

echo -n -e '\e[?17;14;224c'
echo -e "\e[?16;0;64c"

I tried similar ones from [WayBackVGA-softcursor.txt as well, but they failed too.

Since I usually ssh into the box, doing without a console cursor usually is no problem except when you run into network trouble and really need the console.

Fixing it took a bit longer to find out,  but refining to  “odroid C1” console no blinking cursor got this as first hit: [WayBackODROID Forum • View topic – fbcon cursor. And it came down to going to the second page of the first archived link above. So I had a kind of “duh” moment. Anyway, at [WayBackArch Linux ARM • View topic – ODROID-C1: No hardware cursor in terminal – pagee 2 is the below code which got me a nice large light-blue cursor:

infocmp >> ~/terminfo.txt
sed -i.bak -e 's/?0c/?112c/g' -e 's/?8c/?48;0;64c/g' terminfo.txt
tic terminfo.txt
tput cnorm

These are the commands used:


Posted in *nix, Linux, Power User, Ubuntu | Leave a Comment »

Changing the network from public -> private in Windows 10 is way to convoluted (works for 8.1, 8 and 7 too)

Posted by jpluimers on 2018/02/05

I often wonder why do they make changing the network location more difficult in each Windows version.

Anyway: for Windows 10, the secpol.msc way still works even though by default you now need to use a command prompt or the Windows-R key-combo to start it as typing it in the “Ask me Anything” search often gets you to bing (the search is too slow to figure out it is available locally even if you’re running a machine with SSD).

So from [WayBackTop 10: Windows Firewall Netsh Commands (via: Windows Server content from Windows IT Pro), this still works in Windows 10:

a secpol.msc way that is easy:

  1. Press Win+R, then type secpol.msc
  2. Click on “Network List Manager Policies”
  3. Double-click on your network
  4. Optionally give your network another name
  5. Click on “Tab Network Location”
  6. Set “Location Type” to “Private”

Go back to Network and Sharing Center to check the result.

In Windows 10 there are half a dozen other ways: [WayBackNetwork Location – Set to Private or Public in Windows 10 – Windows 10 Tutorials

  • Option One: To Change a Network Location in Settings app
  • Option Two: To Change a Network Location in Registry Editor
  • Option Three: To Change a Network Location Local Security Policy
  • Option Four: To Change a Network Location in PowerShell
  • Option Five: To Change Network Location of Current Network Connection in PowerShell
  • Option Six: To Change Network Location of Current Network Connection using a VBS file

I like this PowerShell script too via [WayBacknetworking – How do I force Windows 10 to see a network as private? – Super User:

## Change NetWorkConnection Category to Private
#Requires -RunasAdministrator

Get-NetConnectionProfile |
  Where{ $_.NetWorkCategory -ne 'Private'} |
  ForEach {
    $_|Set-NetConnectionProfile -NetWorkCategory Private -Confirm



Posted in Power User, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1 | Leave a Comment »

%d bloggers like this: