WAD @index not working in v16 x64

[Charles G]

TCC 16.00.38 x64 Windows 7 [Version 6.1.7601]
Copyright 2014 JP Software Inc. All Rights Reserved
Registered to Charles S. Galloway - 5 System License

[C:\Program Files\JPSoft\TCMD16x64]if not 1 == 01 echo FAIL (looks like CMD.EXE)

[C:\Program Files\JPSoft\TCMD16x64]*if %@index[4NT!TCC!TCCLE!TCMD32!,%_cmdproc!] == -1 echo FAIL (unknown shell)
FAIL (unknown shell)

[C:\Program Files\JPSoft\TCMD16x64]*if %_4ver lt 7 echo FAIL (_4VER less than 7)

[C:\Program Files\JPSoft\TCMD16x64]

[C:\Program Files\JPSoft\TCMD16x64]echo %_cmdproc
TCC

[C:\Program Files\JPSoft\TCMD16x64]echo "%_cmdproc"
"TCC"

[C:\Program Files\JPSoft\TCMD16x64]

 

[Charles Dye]

I've just installed v16 on another 64-bit machine to test. It still works as expected for me.

What does the SETDOS command report?

 

[Charles G]

[C:\Program Files\JPSoft\TCMD16x64]setdos
ANSI=0
COMPOUND=&
DESCRIPTIONS=1  (DESCRIPT.ION)
ESCAPE=^
EVAL=0.10
EXPANSION=0
MODE=1
NOCLOBBER=1
PARAMETERS=$
CURSOR OVERSTRIKE=15
CURSOR INSERT=100
VERBOSE=0

[C:\Program Files\JPSoft\TCMD16x64]

 

[Charles Dye]

Nothing weird there. I'm baffled.

I have found that OPTION CMDVARIABLES, if enabled, will break the test in question. But it breaks almost everything, including ECHO %_CMDPROC. If that were on, you'd be seeing a whole lot more issues.

 

[Charles G]

Are you able to install the x64 version?

Hopefully Rex will chime in soon....

 

[Charles Dye]

Are you able to install the x64 version?

Yes, on two different machines.

 

[vefatica]

Nothing weird there. I'm baffled.

I have found that OPTION CMDVARIABLES, if enabled, will break the test in question. But it breaks almost everything, including ECHO %_CMDPROC. If that were on, you'd be seeing a whole lot more issues.

I can toggle Charles's error with the "DelayedExpansion" directive, available via the OPTION dialog ... Yes = error, No = no error.

 

[Charles G]

What is the option text for the "DelayedExpansion" directive? Nothing seems to be close to it for me...

 

[vefatica]

What is the option text for the "DelayedExpansion" directive? Nothing seems to be close to it for me...

In the OPTION dialog, Startup tab, it's "CMD.EXE delayed expansion (!var!)".
In the INI file, I think it's "DelayedExpansion".

 

[rconn]

Works fine here. If you can't get it working, please send your tcmd.ini file to support@jpsoft.com.

If you have DelayedExpansion set, then a ! is about the (second) worst possible character to use wrapped around your variable names.

 

[Charles G]

Charles. I have it working now. Since it seems to be the DelayedExpansion INI directive - it might be a good idea to modify the RegTweaks.btm so it saves the OPTION[], changes it to off, then reverses the process before the BTM is finished.

Also I did the RegTweaks /undo and looked at the .REG file (attached) and it seems to be saving more then the JPSoft related items. Is it possible to modify the -undo processing so it just does the JPSoft products?

NOTE: Edited since I forgot to upload the .REG file (renamed)

 

[Charles Dye]

Charles. I have it working now. Since it seems to be the DelayedExpansion INI directive - it might be a good idea to modify the RegTweaks.btm so it saves the OPTION[], changes it to off, then reverses the process before the BTM is finished.

Or just change all the exclamation points to periods or dollar signs or something....

 

[samintz]

Or just simple spaces would work too.

*if %@index[4NT TCC TCCLE TCMD32,%_cmdproc] == -1 echo FAIL (unknown shell)

 

[Charles Dye]

Or just simple spaces would work too.

Yup. I think I was afraid that some future JP product might return a space in the _CMDPROC string, but surely Rex would never do that to us.

 

[Steve Fabian]

I typically use semicolon ";", esp. when spaces are possible. Hasn't failed me yet.

Of course, I never use CMD, so all CMD compatibility directives are off...

There are instances when only ASCII is available (7-bit), but not the vertical bar. In those circumstances I use the exclamation mark for column separator in tables (the visually closest), where the issue might have hurt me but for choosing incompatibility with CMD.