TCC/LE x64 exits on startup, giving no errors; TCC/LE x86 starts properly - more info below

[KattPhloxworhy]

Hello!

I wanted to start using TCC/LE a bit more. On the computer I usually sit at and do the most work at under Windows 11 Pro, I have a problem: 64-bit TCC/LE won't properly start, giving a terminal window and a signon message, then exits quietly without any hints as to what might have happened. However, 32-bit TCC/LE starts properly.

Others have suggested that Windows Defender's real-time protection might be the culprit. I turned off Windows Defender's real-time protection; 64-bit TCC/LE still unceremoniously exits without so much as a hint as to why.

I've tried adding the path to the 64-bit TCC/LE as both a process and a file. Neither work.

However, if I go to a normal Windows command prompt session, change into the TCC/LE 64-bit install directory, starting it with a bogus command flag, e.g. /d, it seems to start, but not the way TCC/LE normally starts with an OS/2-style prompt, with a "ver" command confirming that it started. If I give "tcc" without any command flags, it also exits quietly.

Finally, I installed an eval copy of the 64-bit version of TCC, and it fires up just fine, so I may just go ahead and get a license in about two weeks (next payday at work).

About the only thing I can figure might be a file I may need to delete somewhere in my home directory, but the one JPSoft directory in that hierarchy has nothing in it, even when checked with attrib.

Elsewhere in my assets which run Windows 11, like the machines I use for my streaming, the 64-bit TCC/LE happily starts just fine. I did not install the 32-bit version as I didn't see a need to do so on these computers.

I guess I may just get that license and be done with it on this machine. I really SHOULD just reinstall this machine, but I hate reinstalling systems, despite conventional wisdom concerning Microsoft systems, which I hate anyway. >:(

Thanks!

--Katt. =^.^=

 

[Eric Pement]

64-bit TCC/LE won't properly start, giving a terminal window and a signon message, then exits quietly without any hints as to what might have happened. However, 32-bit TCC/LE starts properly.

I know that it's been a few weeks. Has this problem been resolved, or is it still a live issue?

 

[KattPhloxworhy]

I know that it's been a few weeks. Has this problem been resolved, or is it still a live issue?

It has not been resolved and is therefore still live.

About the only thing I can think of is that there's a file from an older installation that may have been hosed, requiring that I delete it for things to work again. Unfortunately, I couldn't find anything when looking in the usual offenders, notably %APPDATA&\JPSoft or the registry in the most obvious places, like HKCU\Software\JPSoft or HKLM\Software\JPSoft.

--Katt. =^.^=

 

[KattPhloxworhy]

Update:

One thing I hadn't thought of trying yet is using a different account on this machine. It works fine under a different account on this computer, so it's definitely something with the environment it's trying to run in, specifically the one I'm using most of the time and therefore not an issue with TCC/LE itself, as I had figured. It's just a matter of figuring out what needs to be cleaned out to fix this situation. I'm just trying to figure out what I need to clean up so it'll work again.

--Katt. =^.^=

 

[KattPhloxworhy]

I ended up buying a license the day TCC 36 got released (also the day I got paid). I will likely use the recent releases of TCC on machines I will likely have considerably more routine contact with. I'm still using TCC/LE on other machines in my fleet because I don't need anywhere near the functionality of recent releases of TCC since I'm mainly using it on several machines I use here for my streaming operations.