I’ve had a surface pro 3 for a long time and it has generally been amazing. But, twice now, I have had to go through an issue where a few parts of the screen totally stop responding.
It happened a year apart or more and I forgot the solution originally, so I’m posting it here!
This blog: https://www.sony.com/electronics/support/downloads/W0009338
Points you to this download (From sony.com, so it’s legit) -> https://www.sony.com/electronics/support/downloads/W0009338
You run that sony app, it calibrates in CLI for a minute, then open up your windows 10 touch screen callibrator (you can find that by searching for “touch screen” on your search bar on by the windows logo). Run that, and you should be good!
It turns out that cmder actually supports this out of the box now. Just launch the WSL::bash task (Windows Subsystem for Linux).
This is fantastic because the below approach seemed to have issues when you tried to use arrow keys in VIM despite having the -cur_console:p argument that supposedly fixes that issue.
Original Article (For Reference)
I don’t recommend this approach now that the out of the box one works well. But here is the original article anyway :).
Cmder is a great console emulator built on top of ConEmu (another great project).
In our last post about installing Apache Airflow into Windows using the Ubuntu bash sub-system, we properly installed Ubuntu from the Windows 10 store.
Assuming you have done this, you can make it work in cmder to improve the usability of the shell.
Simply do the following, which only takes 30 seconds or so:
- Right click on the top bar of cmder.
- Click settings.
- Click “Tasks” under “Startup” on the left navigation panel.
- Click the “+” with the underline.
- Give it any name you like. You may want to follow the naming conventions of the similar bash shells above, but its your choice.
- Add “%windir%\system32\bash.exe ~ -cur_console:p” in the commands section.
I actually had trouble fining the bash executable; you can’t just right click on the start-up icon and find it in this case. So, credit to this post: https://gingter.org/2016/11/16/running-windows-10-ubuntu-bash-in-cmder/ for that command.
NOTE: I fought this installation a lot and fixed numerous issues, but in the end I got stuck on a C++ compilation failure in the Airflow install via pip. So, I’m switching to installing it in a new post in an Ubuntu shell available in the Windows 10 store since I’ll be running Airflow in Linux in production anyway. So, there is probably some helpful stuff here; but its not a full solution and I recommend against doing Airflow this way given my experiences here.
I’m relatively new to Python and have only really used it for simplistic scripts in the past; but now I’ll be using it for a new job along with Apache Airflow (which is very cool).
Anyway, I just had a terrible time installing Airflow… so I thought I’d document the issues here and a working solution on Windows 10:
- Install python 3.6.7 from here: https://www.python.org/downloads/release/python-367/
- (Do not use Python 3.7; as of 2018-11-06, “pip install apache-airflow” will install apache-airflow-1.10.0, and the installer will try and use the “async” keyword, which is now a reserved word in Python 3.7, so it will fail).
- Make sure Python and its Scripts directory are in your path (Python’s installer may or may not do this. If you open a new command line after the Python install and “python –version” doesn’t show 3.6.7, you need to do it.
- Note that the scripts directory is where pip is; this is your package installer for adding modules to Python.
- Upgrade pip with: python -m pip install –upgrade pip
- The installation command for Airflow is “pip install apache-airflow”. But in my case, this failed a few more times due to other dependencies/issues. So, I had to do the following before this worked:
- Set this environment variable: “set SLUGIFY_USES_TEXT_UNIDECODE=yes”
- Install Microsoft Visual C++ 14 build packages (this is time consuming) and upgrade the build tools in Pip.
- pip install –upgrade setuptools
- install the “Build Tools for Visual Studio 2017” from: https://www.visualstudio.com/downloads/#build-tools-for-visual-studio-2017
- Once the interface opens for the installer, install Visual C++ build tools – Build Windows desktop applications using the Microsoft C++ toolset, ATL, or MFC. I also checked the following boxes on the right:
- Windows 10 SDK (10.0.17134.0)
- Visual C++ tools for CMake
- Testing tools core features – Build Tools
- VC++ 2015.3 v14.00 (v140) toolset for desktop
- Windows Universal CRT SDK
- Windows 8.1 SDK
- Installation is 2.5GB! Woah.
- Open a new command line so it picks up everything and then run
- set SLUGIFY_USES_TEXT_UNIDECODE=yes
- pip install apache-airflow
- IT STILL DIDN’T WORK! – The error is a complex SYSTEM_THREADING related one and online docs for it seem to not have a resolution.
There’s probably a way to fix this; but at this point I’m going to switch to installing it in a Ubuntu shell subsystem from the Windows 10 store in a new blog post – I’ve wasted enough time on this given I’ll be running Airflow in Linux in production anyway.