Problem statement: use a Samsung Galaxy Tab A7 with OneUI 3.1 as a seccond screen on Windows.
According to Samsung at time of writing, a "Second Screen" button comes as part of the OneUI 3.1 update (article here). However, for me (as for many people), this doesn't work on a Galaxy Tab A7, at least with OneUI 3.1.
The solution that works for me is a free application called spacedesk from DatronicSoft in Germany.
Steps to install on tablet:
The OpenSSH SSHD service on Windows 10 an 11 is extremely useful, but a bit tricky to set up. Here are my notes on how to do it.
Follow the instructions from [[1]] to "Install OpenSSH" via Windows Settings. Alternately, use PowerShell:
Add-WindowsCapability -Online -Name OpenSSH.Client
Add-WindowsCapability -Online -Name OpenSSH.ServerIPFire supports net-to-net connections.
Part of setting up the connection with non-IPFire peers often involves generating a .ovpn file from the client package.
There are some client docs about how to do this, but not net-to-net.
For net-to-net clients, IPFire generates a zip file containing two files. Both files are named based on the name you choose for the VPN.
MCCI needs OpenSSL for a Windows project (that will be cross-platform). A casual search didn't turn up either a good source for cross-platform libraries, which meant we have to build them ourselves. A deeper search found a detailed guide here, and yet the details don't match what I found when I checked out the code; and the post doesn't talk about doing it directly from GitHub (which I wanted to do).
Here's the procedure for building OpenSSL on 64-bit Windows 10, with Visual Studio 2015. Others (July 2019) report that this procedure works with Visual Studio 2017 as well. I've not had a chance to try with Visual Studio 2019.
As this procedure dates from late 2016, you may find that there's a CMake or other, newer, procedure that's more suitable.
| # Prep WSL | |
| dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart | |
| dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart | |
| ### Make it mine | |
| # Timeout / battery prefs | |
| powercfg /Change monitor-timeout-ac 5 | |
| powercfg /Change standby-timeout-ac 0 | |
| powercfg /Change monitor-timeout-dc 5 | |
| powercfg /Change standby-timeout-dc 30 |
I couldn't find a concise summary, so I looked at the schematics (page 11 of SPF-3880_A2.pdf).
SW1 is BOOTMODE_1, and SW2 is BOOTMODE_0. The board ships with SW1=1 and SW2=0.
We bought a couple of MCIMX8M-EVKB, and one came in bricked. It's a bit complicated to reflash them; here are the instructions all in one place.
These are instructions for Windows.
uuu from GitHub12.0.0_1.0.0_DEMO_8MQ:
Do you have a Yeti (or other) USB microphone that worked perfectly on your previous Windows 10 system, but doesn't work on a your new system? This tip might help.
Here are the symptoms:
I had occasion to get my company's FAR and DFARS reports from sam.gov recently, and the process was surprisingly obscure. I did a search, but all I found were videos on YouTube that were out of date; and I wasn't able to find a help article that explained what to do.
So here's a quick runthrough.
Log into sam.gov
The website will open your "Workspace" page. Click on the "Active" entities bubble:
I recently installed PSpice for TI (version 17.4-2020 S002 Windows SPB 64-bit edition).
After installing, Git for Windows bash no longer worked as expected. Instead of starting up in my home directory, it started up in the (emulated) root directory; and it didn't load my profile. (In other words, installing PSpice for TI broke my Git for Windows installation.)
Investigation revealed that the installation had created an environment variable HOME in my profile, with the value c:\mcci\projects\SBP_Data. It was easy enough to fix this.
System