BDEBUGGER and CMDebug

#1
I have updated TCMD and CMDebug to;
Code:
c:\users\jlc\utils>ver

TCC  22.00.29 x64   Windows 7 [Version 6.1.7601]
I have the following;
Code:
 Directory of  C:\Program Files\JPSoft\TCMD22\library\*

12/09/2017  18:49         <DIR>    .
12/09/2017  18:49         <DIR>    ..
12/09/2017  18:59             346  vb.library
                 346 bytes in 1 file and 2 dirs    4,096 bytes allocated
     666,219,638,784 bytes free

c:\program files\jpsoft\tcmd22\library>library /f vb
vb {
@setlocal
@echo off
echo set fso=CreateObject("Scripting.FileSystemObject") > c:\utils\vb.vbs
echo set stdout=fso.GetStandardStream(1) >> c:\utils\vb.vbs
echo stdout.WriteLine %* >> c:\utils\vb.vbs
echo set fso=Nothing >> c:\utils\vb.vbs
cscript //nologo c:\utils\vb.vbs
if exist c:\utils\vb.vbs del /q c:\utils\vb.vbs
endlocal
}
I have this .BTM;
Code:
c:\users\jlc\utils>type test.btm
@setlocal
@echo off
ver
vb date
endlocal
quit
When I step through this with bdebugger test.btm, it works as it should.

When I step through this with CMDebug test.btm, I step through the .BTM, and when I step into the
Code:
vb date
it opens
Code:
C:\Windows\VB.INI
in notepad, and never executes the vb library function.

upload_2017-12-9_19-19-51.png

Works as it should from the TCC command line.

Joe