The Kaypro ran CP/M and I'm thinking it wouldn't have had a clue what to do with a DOS program. If that line lasted into the DOS era and ever ran under DOS, I didn't know about it.

3.5" disks. When they went from 360K (or whatever it was) to 1+ MB (or whatever), it was as if the sun rose in the sky for the first time. : ) Then there were the 8" hard-sector disks we used in typesetting machines. Argh, what a painful memory. One unfortunate crimp and bye-bye, disk. I still...

Ohmigosh, it's Tom Rawson! I used to send you irritating bug reports! My wife was going through old stuff in our basement once and came across one of those 4DOS registration cards. What is this, anyway? she asked. And: Throw it away? No way, says I. That's a historical document. I shoulda...

I also had this problem with the file viewer. I could not get it to work properly. Finally I just bought the thing, installed it, and added the executable's directory to the PATH variable that's in use when TCC is running. Now it works fine. (Never did find out why it wouldn't run properly. I...

I have been able to do this with minimal typing when I've had files in a sequence — for example, when someone has split a large file. Filename.001 Filename.002 or Filename-001.bin Filename-002.bin and so forth. I know the output is supposed to be, say, a .zip file, and the following has...

Using the "/o:n" switch+argument within the "for" line also seems to sort in correct numerical order. At least it did for a me a few minutes ago (I'm using an older version of TCC, though — things might've changed since then). Incidentally, the line containing "@eval[]" can be shortened a bit...

Does the file C:\Windows\system32\find.EXE exist on your system? If so, is C:\Windows\system32 in your path?

Agreed. If there's a text string that appears in a predictable way, that seems far easier than trying to do it via "@instr". Below — one possible approach (tested with a small number of files). Uses "ren /n" to test what would happen. If it appears to work as needed, remove "/n" switch. do...

> Still I like mikea's "inelegant" file I should have said that the output is somewhat inelegant-looking. The DO loop itself is a thing of exquisite beauty. :-) Speaking of ITERATE, see the documentation for the LEAVE command — also very useful in a DO loop.

"Dir /z" does mangle the filenames. I use the following in a .btm file. It isn't elegant, but it works. The commands "Yellow" "White" and "Cyan" are simple aliases that change the text color (for example, "bri yel on blu"), and "Normal" returns to the default text color. do _x in /a:-d * if...

Thanks. I was stuck thinking Perl-ish and didn't think it through enough. The matches I did get seem to have been case-insensitive by default, so I'd be using something like this for case-sensitivity: "%1" =~ "(?i:.*[abc].*)"

I'm still back in the dark ages, using TCC v.20 (under Windows 10 Pro). I've written a bazillion regular expressions over the years but rarely use them in TCC. I've never been clear about using regexes successfully in TCC. (Per the OPTION command, they're set to Perl.) iff "%1" =~ "[abc]" then...

I realize this reply doesn't address your question — I don't use the batch debugger myself so I'm no help on that account. But, a question about your .cmd file: Do you plan to make batch files written in standard cmd.exe fashion so that they can be used, unaltered, in both cmd.exe and Take...

I downloaded the full distribution package for Everything and installed it. Now it works. I don't know what caused the version that ships with TCMD to fail.

Thanks. I had totally forgotten about %_ininame. Now while getting TCC set up again I've encountered something else odd. At first the Everything tool was working fine. I don't know just what changed to make this happen, but Everything has now stopped working. I set its service to launch when...