I'm using SecureCRT at windows 10.
And it's my SecureCRT version
Version 7.2.6 (x64 build 606) - Official Release - August 19, 2014
I want to open windows cmd terminal at SecureCRT.
How to I do it?
The answer is yes. But, you have to upgrade your SecureCRT software.
Local shell sessions are supported in SecureCRT v8.7.x.
You can reference the offical release note.
Open a local shell by [FILE] -> [Connect Local Shell] or press ALT+SHIFT+L
New in SecureCRT 8.7 (Official)
Local shell session (Windows):
On Windows 10 and Windows Server 2019 or later, you can open a local shell session within SecureCRT. A tabbed CMD or PowerShell session makes it easy to work on the local system without having to leave SecureCRT. Local shell was already supported on macOS and Linux.
Related
I am trying to install Git-2.38.0-64-bit.exe on my Windows 10 Laptop. It immediately shows the error message "This program requires Windows service pack 1 or later."
I am running Windows 10 v. 21H1 Build 19043.2130. I am running Windows updates all the time, so this should be a quite current version. And I thought service packs were a thing of Windows 7.
So what should I do to be able to install that Git?
Your Windows 10 is officially supported by Git For Windows
Try and:
uncompress the portable archive PortableGit-2.38.0-64-bit.7z.exe in C:\Git
set a simplified path in a CMD:
set PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\
set "GH=C:\Git"
set "PATH=%GH%\bin;%GH%\cmd;%GH%\usr\bin;%GH%\mingw64\bin;%GH%\mingw64\libexec\git-core;%PATH%"
Check that Git is working in that CMD session, starting with git version.
I have both Ubuntu and Debian installed for WSL. When I open a WSL workspace using VS Code remote development, it always opens Ubuntu. How can I open a workspace under the Debian install using WSL in VS Code?
The VS Code Remote - WSL extension always uses the default WSL distro. You can change the default distro using the wsl command (wslconfig on earlier windows versions):
# List the available distributions
wsl --list
# Set the default version to debian
wsl --setdefault debian
After changing the default for WSL, make sure to restart VS Code
Click the "remote button" in the bottom left
Choose New Window using Distro...
Pick your distro!
so the new windows subsystem (2019 Windows 10 April Release) for Linux is out and my ubuntu subsystem was upgraded.
I'm supposed to be able to open the Linux folder in my windows explorer but I'm not getting the correct folders when I run the command.
falieson#firefly:~$ explorer.exe ~/
Opens the windows user's My Documents folder.
falieson#firefly:~$ explorer.exe .
Opens C:\Windows\System32
My only guess is that when I did the windows install for GitHub desktop and opted into a Linux-ification of my shell it borked this upgrade from Windows.
Thanks for your ideas to resolve this.
This is currently not possible as mentioned in JosefZ comment.
If you have the latest Windows Insider Preview, or you can wait until the next Windows release, that changes as described in the WSL Blog
I recently installed Ubuntu for Windows and now inside the Start Menu there are 2 new items:
Bash
Bash
This terminal opens in:
root#myName-PC:/mnt/c/Windows/System32#
Ubuntu
Ubuntu
This terminal opens in:
root#myname-PC:~#
What is the difference between the two?
For example, we want to install Git and Utils, RVM (Ruby) then clone a Git project and deploy via SSH with Capistrano commands. Should that be run with Bash or Ubuntu as above?
Also, should the commands be run in system32 or C:/ folder when inside the terminal?
Thanks
The Bash terminal is the old style (prior to Windows 10 v1790 a.k.a. Fall Creator Update). It resides in %LocalAppData%\Lxss and is managed using lxrun.exe.
The Ubuntu terminal is the new style, downloaded from Microsoft Store. The launcher part is a Windows App (%ProgramFiles%\WindowsApp) and its data resides in %LocalAppData%\Packages.
Those are two isolated installation of Windows Subsystem for Linux and do not interfere with each other. Practically you need only one of them, so choose one at your own preference.
I personally dislike the Windows Store version as it can be easily removed, which isn't a good thing for a productivity environment.
I was trying to delete the legacy "Bash on Windows" and wasn't unable to because lxrun.exe is not available in my system. But in case anyone needs it, here's how:
If you wish, you can manually delete your legacy instance. This may be required if you encounter issues uninstalling the legacy distro using lxrun.exe, or are running Windows 10 Spring 2018 Update (or later) which do not ship with lxrun.exe.
To forcefully delete your legacy WSL distro, delete the %localappdata%\lxss\ folder (and all it's sub-contents) using Windows' File Explorer, or the command-line: (using PowerShell)
rm -Recurse $env:localappdata/lxss/
The git bash vs the Ubuntu bash.
Basically there is nothing much different except maybe the versions of the bash. Because bash is bash. It's most likely different versions of bash were installed at different times for different purposes on the PC. And they will also likely be found in different folders on the PC.
Run the following code from the two different shells. This returns the version of bash:
echo "$BASH_VERSION"
On this PC, using the two terminals (MinGW and Ubuntu) returned the following versions of bash: (see image link below)
5.0.17(1) - release
4.4.23(1) - release
It's likely most people using PCs that have been around a while will find that there are two (or more) different versions of bash installed on their PCs. On this PC, the older version of bash was installed some time back.
That older version of bash might have been installed when Cygwin was installed on this PC. Or maybe the older version of bash was installed when Git was installed long ago. It really doesn't matter now. On this PC, bash is found in at least these following locations:
C:\cygwin64\bin\bash.exe
C:\Program Files\Git\bin\bash.exe
C:\Program Files\Git\git-bash.exe
The Windows 10 on this PC was updated. Specifically, the WSL kernel was updated from WSL to WSL2. Part of this update involved turning on some Windows features, including the: Windows Subsystem for Linux.
There was an old (virtual) version of Ubuntu (18.04) that had been installed on this PC some time back. But that old version of Ubuntu went away with this update. This WSL2 update changes the way Linux (Ubuntu) operates on this PC. After the WSL2 update, Ubuntu was installed from the Microsoft Store. This is Ubuntu 20.04.
This WSL2 update and the newly installed version of Ubuntu also installed a newer version of bash on this PC. And this newer version of bash is the newer version of bash that is showing above.
Another good way to understand the difference between these two versions of bash would be to enter the following into each shell:
type ping
The result should clearly show that one version of bash is providing the source from Windows while the other version of bash provides the source from Ubuntu.
ping is /c/windows/system32/ping
ping is /usr/bin/ping
Sometimes a picture is worth more than a thousand words. Attached below are two of the new Windows Terminals side by side.
These terminals show the two different versions of bash. Echo returns the older version of bash being used in the MinGW shell and Echo returns a newer version of bash being used in the Ubuntu shell.
After some M$ Windows updates Cygwin mintty (desktop shortcut installed by setup-x86_64.exe) starts but ends immediatelly. I tried to install all missing DLL's which can be observed with dependency walker. I installed 2012 and 2008 Microsoft Redistributable packages which were missed on My Windows 7. I installed both builds (x86 and x64). But it didn't help me to get my CygWin back, because as far as I can see from mintty's logs there is a security issue. I've got a log with the only row:
This account is currently not available.
I tried to create passwd file with CygWin's mkpasswd and with this command:
getent passwd %USERNAME%
It didn't help also and I don't have any ideas what to do next.
Now I've got a CygWin installation (Cygwin DLL 2.9.0) with mintty ends immediatelly. I can run Cygwin.bat and use the most of CygWin's functionality, but mintty is more comfortable than M$ Connhost and I want it back.
Something have happened, but today, after an ordinary reboot, mintty begun working.
P.S. It has begun after "Definition Update for Windows Defender - KB915597 (Definition 1.253.822.0)" and ended after "Definition Update for Windows Defender - KB915597 (Definition 1.253.973.0)".