Flemming Dec 1 0 2023-08-18 #1 CMDebug seems not to be a part of TCC v 29. Please confirm. BDebugger start up fine but all commands seems to be "unknown" when I use "step into" Please advise. Regards Flemming PS: Attached the start up console Attachments bdebugv_tcc_v29.png 41.9 KB · Views: 85
CMDebug seems not to be a part of TCC v 29. Please confirm. BDebugger start up fine but all commands seems to be "unknown" when I use "step into" Please advise. Regards Flemming PS: Attached the start up console
Joe Caverly Aug 2,228 102 2023-08-18 #2 From the screen shot that you provided, you are trying to debug a .BAT file. As a result, it will only recognize commands that CMD.EXE uses. For TCC files, use .BTM instead of .BAT extension. Note also, in CMDebug 29 (or BDebugger), under Options, the Syntax can be selected manually. From the help file under CMD Compatibility; Joe
From the screen shot that you provided, you are trying to debug a .BAT file. As a result, it will only recognize commands that CMD.EXE uses. For TCC files, use .BTM instead of .BAT extension. Note also, in CMDebug 29 (or BDebugger), under Options, the Syntax can be selected manually. From the help file under CMD Compatibility; Joe
Joe Caverly Aug 2,228 102 2023-08-18 #3 Flemming said: CMDebug seems not to be a part of TCC v 29. Please confirm. Click to expand... CMDebug must be purchased separately. You can download the eval version from Download JP Software's Take Command, TCC, CMDebug, and TCC-RT Joe
Flemming said: CMDebug seems not to be a part of TCC v 29. Please confirm. Click to expand... CMDebug must be purchased separately. You can download the eval version from Download JP Software's Take Command, TCC, CMDebug, and TCC-RT Joe