Done fork in the road

[fpefpe]

Hello — I have been a long-time user of JPSoftware shells from when I first discovered NDOS with norton a/v. Since then, I migrated to 4dos, 4nt (and take32) to the current “take.” Over the years I have invested in various DLL (plugins too) for the 32bit verison of TAKE. When I got my win10 laptop I did not have (which is true today) the resource to create or find 64bit version of these dll, so I was “locked in” to the 32bit version of TAKE.

That was fine — at the time there was a 32- and 64-bit installer. This stopped with version 20 – where it would install the 32 or 64 bit version depending on the OS, so since then I been relegated to version 19.

Today was the “fork in the road” With the expending EOL of win 10, I got a new win 11 computer. I installed my 32 bit TAKE V19 — install OK but tcmd.exe would not start correctly. The TAKE window was created, and tcc started and stopped and close the tcmd window. I was able to jerry-rig a tcstart.btm file with the “pause” command in it., That worked. I was able to type a few command like “echo %_cmdproc” echo show “TCC” but
echo %_ininame show “echo is off” implying there was no inifile found — but there is the ini file in the same folder as tcc.exe and tcmd.exe

The weird part of all this if I use Window’s Terminal to run tcc.exe it works fine with no issue,

Any suggestions to a solution with tcmd.exe would be appreciated – thanks

 

[rconn]

This is due to a recent Windows timing bug (the tab window is created, a valid handle is retrieved, but Windows thinks it doesn't exist yet). Version 34 has a workaround for this; older versions can do something like put a short delay in tcstart.

If you run OPTION it will show the TCMD.INI that TCC is using on the caption bar.

 

[fpefpe]

thanks for the info and reply --- I don't see a "sleep" or "wait" (internal) command in tcc would an external command work. ie wait.exe ( it this exist) --- but by the time tcstarts would it be too late? there is the ini directive "tcstartuppath" which has the location of the tcstart ---- sort of the chicken and egg issue

 

[Fross]

DELAY is the internal sleep command.

DELAY
Pause for a specified length of time.

DELAY [/B /F /M] [seconds] [UNTIL [yyyy-mm-dd] hh:mm[:ss]]
        /B(reak): Exit on any keystroke
        /M(illiseconds): Argument is in milliseconds
        /F(lush buffer)
        seconds:  Number of seconds to delay

 

[fpefpe]

thanks for the info

 

[fpefpe]

Has MS corrected the "timing issue?" --- I did come up with a solution that is to modify the tcmd shortcut to include the "/t" switch ---- /t cmd.exe

so now when tcmd starts, it will launch cmd.exe in the first tab -- from then I can start tcc

 

[rconn]

No, Microsoft has not fixed this (I don't have much confidence they will soon, if ever). They've known about it for more than a year.