DosTips.com

Ah, OK!
I expected it would output strings like case-dependent sorts in Unix: I just checked /CASE_SENSITIVE is present in XP and later versions of Windows, but not in Windows 98. Funny I never heard of it.

I think that TEMP and path are not part of the supported options. /TEMP worked for you as an abbreviation of the documented /TEMPORARY option. Also note that contrary to the other options before it, it is part of a longer string "TEMP path": C:\Windows\System32>strings sort.exe | ag "[a-z]{4,}" [Uni...

For quickly searching for strings in a large set of text files, try The Silver Searcher . The ag.exe program in that zip file is a port for Windows that I maintain, of the Unix tool ag. It supports full fledged regular expressions, so finding any sequence of valid characters you can think of will be...

I gave it a try, and it's indeed nice and easy to use for doing calculations at the command prompt. :) The rpn.exe executable is surprisingly small. Was it all written in assembly language? The stack-based RPN notation reminds me a lot of the old Forth programming language. Add support for strings, ...

No, you still can't nest them, but you can get the same effect very easily: So, yes, three commands instead of one. But barely more characters to type overall than in Bash or PowerShell.

Unix shells, and Windows own PowerShell, allow nesting commands inside each other using the $(subcommand) syntax. This syntax is extremely convenient for capturing the output of a subcommand, and passing it as an argument to an outer command. For example, using Docker, you can find containers that h...

You should use a Win32 port of the Unix tail utility. It's designed precisely to do what you want to do. There's one coming with git for Windows, if you have it. Typically in "C:\Program Files\Git\usr\bin\tail.exe". Else you can find a tail.exe in old win32 ports like UnxUtils or GnuWin32 . Then the...

This existed in MS-DOS, and was called AUTOEXEC.BAT: The first thing MS-DOS did after booting was to automatically run AUTOEXEC.BAT. Now you can still legally do that using FreeDOS. Windows is different. It is not an open-source operating system. Its commercial license forbids you to copy it to anot...

It's also possible to do that without invoking the where.exe program at all. Ex: C:\JFL\Temp>for %p in (notepad.exe) do @echo set N=%~$PATH:p set N=C:\Windows\System32\notepad.exe C:\JFL\Temp>for %p in (nothing.exe) do @echo set N=%~$PATH:p set N= C:\JFL\Temp> In a batch file, it'd become: for %%p i...

truename is an internal command of the command.com shell. This is independent of DOS or Windows 98: command.com is also available in Windows XP, as an alternative to its native cmd.exe shell. I'm pretty sure that you can even make the XP version of command.com run in 32-bits versions of Vista and la...

I found this entry presented as a version there: https://www.tiraniddo.dev/2019/09/overv ... iases.html
And this made sense to me as, as you've noticed, there are 4 strings in the list, not 3.

Jean-François

@Steffen I've posted on https://stackoverflow.com/a/65583702/2215591 a reply with all what I've found so far on how to use App Exec Link targets. I really hope that somebody eventually gets to the bottom of it, and explains how to use the information in these links (and just the information in these...

Maybe this is where the other information I was talking about are useful: The Windows Terminal probably uses a standard entry point name, so that CreateProcess() can run wt.exe without the additional information; Whereas Edge uses a non standard entry point? You can see for yourself by dumping repar...

Hello, I've released version 1.16 of my which.exe program for DOS and Windows. (Version 1.15 had some internal changes for compatibility with MacOS, but the DOS/Windows versions were otherwise unchanged.) It is available as part of the latest System Tools Library release: SysTools.zip As usual, this...

Cute, thanks for sharing