SOLVED: How *echo and *if can be unknown commands? ANSWER: If you’ve done setdos /x-1

[Claire_CJS]

I’m just curious how *echo and *if can be unknown commands. Ever.

unknown command

clairecjs_bat/BAT-and-UTIL-files-1/unknown_cmd.bat at main · ClaireCJS/clairecjs_bat

Claire's personal BAT files, often TCC.exe-specific - ClaireCJS/clairecjs_bat

github.com

 

[rconn]

It is impossible for me to recreate this from a screenshot. Please put the command line in a code block or post a batch file with that echo command.

 

[Claire_CJS]

It is impossible for me to recreate this from a screenshot. Please put the command line in a code block or post a batch file with that echo command.

I can’t, because it was the result of letting my AI-transcription system run overnight in 5 or so tabs

One of them was hung the next morning with this in the output

Unfortunately I have accidentally closed the window since.....
[Apparently Microsoft finally fixed the "no *))$)$#)## confirmation when you hit Alt-F4" buti n the upcoming Windows Terminal release, just saw the issue closed this morning. Doesn’t help me now tho haha.]

the main 2 BAT files are >1000 lines each and >50 are used in the system, so it’s really hard to trace just how this happened.

I’ll keep my eye open for if this happens again.

But yea. I’m apparantly great at making things that shouldn’t happen happen. I probably should have been a tester instead of a developer in the past (Actually i did do a couple years of testing when the money was good)

 

[Claire_CJS]

It is impossible for me to recreate this from a screenshot. Please put the command line in a code block or post a batch file with that echo command.

And oh, sorry, I didn’t respond to what you said here and i should have:

i did post the BAT file - it’s the BAT file linked to in the post, the unknown_cmd.bat

clairecjs_bat/BAT-and-UTIL-files-1/unknown_cmd.bat at main · ClaireCJS/clairecjs_bat

Claire's personal BAT files, often TCC.exe-specific - ClaireCJS/clairecjs_bat

github.com

 

[Joe Caverly]

Just as an aside,
you can disable commands such as ECHO using OPTION;

No need to restart TCC,
as the change is immediate.

Joe

 

[Claire_CJS]

No need to restart TCC,
as the change is immediate.

Joe

I forgot about that!

That would be a possible explanation.

I’m definitely not doing that, but I wonder if it’s somehow being done, via memory leak or anything else.
Including me doing some dumdum stuff without realizing it!

That’s often the cause!

I just can’t figure it out this time. This really shouldn't happen. Maybe not ever, but it shouldn't happen in my situation.

 

[Charles Dye]

Just as an aside,
you can disable commands such as ECHO using OPTION;
...

Or with SETDOS /I, or with COMMANDS.

 

[rconn]

And oh, sorry, I didn’t respond to what you said here and i should have:

i did post the BAT file - it’s the BAT file linked to in the post, the unknown_cmd.bat

clairecjs_bat/BAT-and-UTIL-files-1/unknown_cmd.bat at main · ClaireCJS/clairecjs_bat

Claire's personal BAT files, often TCC.exe-specific - ClaireCJS/clairecjs_bat

github.com

I have your unknown_cmd.bat file, what I don't have is the oddball ECHO command you showed in your screenshot (with all the funky non-ASCII characters). I suspect something in that line was confusing the parser (or the parser was interpreting it correctly but not as you expected).

I can think of a dozen plausible & expected reasons for the errors you were seeing, but without the original command line they're simply SWAGs in this context.

 

[Claire_CJS]

I have your unknown_cmd.bat file, what I don't have is the oddball ECHO command you showed in your screenshot (with all the funky non-ASCII characters). I suspect something in that line was confusing the parser (or the parser was interpreting it correctly but not as you expected).

I can think of a dozen plausible & expected reasons for the errors you were seeing, but without the original command line they're simply SWAGs in this context.

A dozen!??!?! wow!

Here is the snippet of the (1400-line) Bat file where the echo is:

:we_decided_to_never_check_for_txtfile
:Force_AI_Generation
:AI_generation
echo ❇❇❇❇❇❇❇❇❇❇❇❇❇❇❇❇❇ AI generation! ❇❇❇❇❇❇❇❇❇❇❇❇❇❇ >nul
echo off


REM if a text file of the lyrics exists, we need to engineer our AI transcription prompt with it to get better results
        rem 2023 version: set CLI_OPS=
        rem Not adding txt to output_format in case there were hand-edited lyrics that we don’t want to overwrite already there
        rem CLI_OPS=--model large-v2 --output_dir "%OUTPUT_DIR%" --output_format srt --highlight_words True  --beep_off --check_files --sentence --standard       --max_line_width 99 --ff_mdx_kim2 --verbose True
        rem CLI_OPS=--model large-v2 --output_dir "%OUTPUT_DIR%" --output_format srt --highlight_words True  --beep_off --check_files --sentence --standard       --max_line_width 25 --ff_mdx_kim2 --verbose True
 

<etc>

And in case you’re wondering why i’m echoing to nul.... I do that a lot instead of REM because i can see the expanded variable values if echo is on, and nothing if echo is off.

And in case the character doesn’t display right in the forums, here it is:

It’s a bit wide of a character given that it covers up the right bracket :)

 

[rconn]

And if you copy that ECHO statement to the command line & run it, do you see any errors?

 

[rconn]

And what version of TCC are you running?

 

[Claire_CJS]

And if you copy that ECHO statement to the command line & run it, do you see any errors?

Nope!

 

[Claire_CJS]

And what version of TCC are you running?

 

[rconn]

A dozen!??!?! wow!

If you were to pin me down to a single SWAG, I'd guess you have a SETDOS /X-1 somewhere. That would mean something like a "*ECHO ..." would not have the * stripped, so TCC would look for a command named "*ECHO" and obviously fail to find it.

 

[rconn]

View attachment 4932

TCC v33 will definitely have many problems with double-wide characters (it only supports them in DBCS languages). Wide character support everywhere was introduced in v34.

 

[Claire_CJS]

I absolutely am doing setdos /x-1

Wow. Good call! I didn’t know it worked like that!

I’ll have to put a setdos /x0 at the beginning, then!