Can't start IDE / Bdebugger

[KeithC]

Using TCC 32.10, I've been going through my collection of old 4DOS .BTM files to see if any are useful. One I tried wasn't doing what I expected (not surprising as it was written for 4DOS 5), so I thought I would try IDE or BDEBUGGER. Unfortunately, neither will start for me. I tried running them from a TCC prompt inside Take Command and from the Tools menu. All that happens is that the command seems to be accepted but the cursor only goes to the next line and sits there blinking slower than normal.
Edit On a hunch that they are connected, I tried TCEDIT. That at least didn't hang the TCC tab, but it simply returned to the prompt if called with no filename. If called with a filename, it sometimes correctly opened the file, albeit very slowly, other times it just returned to the command prompt. Watching the task manager during this, I could see the Take Command Editor (sometimes tcedit.exe) running as a background task using a few percent of CPU before it closed several seconds (maybe a few minutes) later. The debugger also ran in the background for some time, using about twice as much CPU. I got fed up with waiting and killed it.

 

[vefatica]

The cursor sitting on the next line is normal; TCC is waiting for a BTM/BAT to produce console output or for IDE.EXE to terminate. Are you sure it's not running and you're just not seeing it? Does IDE.EXE show up in the Task Manager?

 

[Alpengreis]

Here, the bdebugger works (from TCC console and also over TCMD menu), so I am not sure if that is really a bug. Maybe it's something with your TCMD install or system (OS) ...

What happens if you start direct the ide.exe (via double click over explorer)?

PS: Microsoft Windows 10 Pro x64 [19045.4529] [22H2] [de-CH] TCMD 32.10.21 x64

 

[KeithC]

After a bit more investigation...

• Clicking on IDE.EXE in explorer causes it to start in the background - visible in the Task Manager as Take Command IDE/Debugger
• Calling IDE.EXE from a TCC prompt using the full path causes it to start in the background and the console returns to the prompt
• Calling IDE without a path causes it to start in the background and the console sits unresponsive on a blank line, not taking any input
• BDEBUGGER cannot be called with a path, and has the same results as calling IDE without a path
• Using TCEDIT instead of IDE has the same results, except sometimes (haven't nailed down when), if called from its own directory with .\TCEDIT and a filename, it will correctly open the file

Take Command 32.10.21 x64
Edition Windows 11 Home
Version 22H2
Installed on ‎27/‎09/‎2022
OS build 22621.3593
Experience Windows Feature Experience Pack 1000.22700.1003.0

 

[vefatica]

Can you bring it to the foreground? If so, I suspect all is well. If not, that's very strange and must be some sort of bug or mis-configuration. Here, regardless of how I start them, IDE and TCEDIT always appear in the foreground. Have you changed your monitor configuration? Is it possible they're starting off the screen?

As I said before, the console is unresponsive because it's waiting for output from the BTM being debugged (or for the debugger to terminate).

I always use it by issuing the command BDEBUGGER BTM_filename (with a path to the BTM if it's not in the current directory).

I think the internal command IDE is basically the same as BDEBUGGER. I don't think there's any point in running IDE.EXE (or TCEDIT.EXE) directly (by name or with the mouse in Explorer.

 

[Charles Dye]

Maybe try activate "ide *" pos=0,0,1500,1000 from a different tab?

 

[vefatica]

If they are starting off the screen, you might try deleting these registry keys (where the window position is saved).

HKEY_CURRENT_USER\SOFTWARE\JP Software\IDE 32.10\Settings
HKEY_CURRENT_USER\SOFTWARE\JP Software\TCEdit 32.10\Settings

 

[KeithC]

Trying to answer all the questions, so some repeats:

• IDE.EXE does show in the Task Manager (as Take Command IDE/Debugger) in the Background Tasks
• Clicking on IDE.EXE in explorer causes it to start in the background - visible in the Task Manager as Take Command IDE/Debugger
• Calling IDE.EXE from a TCC prompt using the full path causes it to start in the background and the console returns to the prompt
• Calling IDE without a path causes it to start in the background and the console sits unresponsive on a blank line, not taking any input
• BDEBUGGER cannot be called with a path, and has the same results as calling IDE without a path
• Using TCEDIT instead of IDE has the same results, except sometimes (haven't nailed down when), if called from its own directory with .\TCEDIT and a filename, it will correctly open the file
• I cannot bring it to the foreground
• It is not running off screen or minimized, so I haven't tried deleting the registry keys as suggested
• I have had issues with 0Patch in the past so disabled that, uninstalled TC completely and reinstalled it. Made no difference
• Running TC as administrator made no difference
• Using "activate" got "Window title not found"

 

[vefatica]

It is not running off screen or minimized,

How do you know that? Is there a taskbar icon?

 

[KeithC]

How do you know that? Is there a taskbar icon?
View attachment 4476

No task bar icon, nothing in the notification area, not visible on Alt-Tab on Win-tab, shows as background task in Task Manager.

 

[rconn]

You probably have a third-party component that is messing with the IDE startup. Try disabling those sorts of apps (AV, screen manager, etc.) temporarily and see if the debugger starts normally & in the foreground.

TCC / Take Command just start the IDE with the default Windows settings (never in the background), and they have no control over it being put in the background or hidden.