Take Command / TCMD/LE / TCC/LE 11.0 build 47 uploaded

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

rconn

Administrator
Staff member
May 14, 2008
10,207
86
#1
I've uploaded build 47 to the web and ftp sites.

Build 47:
---------
@LINE / @LINES - fixed an erratic problem with ASCII files.

Build 46:
---------
TCC - added checking for keystroke plugins during filename completion, keyboard block marking, and history recall.

TCC - (Hopefully) Fixed a problem when redirecting output if your code page is UTF-8 or DBCS.

TCC - reinstated support for Regina REXX.

@LINES - fixed a sporadic Windows problem when the file contains extended ASCII characters (and the file is not Unicode).

DESCRIBE - fixed a sporadic Windows problem when descriptions contain extended ASCII characters (and the description file is not Unicode).

FOR - added support for batch & environment variables at the beginning of the FOR command (to set FOR switches). All variables up to the variable immediately preceding "in", are assumed to be in need of expansion before the FOR command is parsed.

TCTOOLBAR - fixed a problem with /U not always correctly updating TCMD.INI.

Build 45:
---------
LIST - fixed a (Windows) problem with the Print dialog sometimes appearing behind the Take Command window.

TCTOOLBAR - updated docs and fixed a problem when not specifying a tab title.

UNZIP - fixed an error message when unzipping with /D in a directory with embedded whitespace.

Help file updates.
<O:p
Build 44:
---------
TCC - fixed a problem when invoking help from a stand-alone TCC console window.

TCC - fixed a problem with not displaying Windows loader popup errors.
<O:p
Build 43:
---------
TCMD - fixed a problem when loading a custom console color palette from the registry that doesn't define all 16 colors.

Fixed a Windows IPC bug that caused 32-bit versions of TCC to potentially hang 64-bit versions of Take Command.
<O:p
Build 42:
---------
TCMD - now detects custom console palettes when attaching an existing console window.
 
Jul 1, 2008
81
0
71
Montreal
#2
I've uploaded build 47 to the web and ftp sites.

Build 47:
---------
@LINE / @LINES - fixed an erratic problem with ASCII files.
Confirmed that @lines[] and @line[] both work again, but now @ipaddress[] needs a hostname - without one it returns "ECHO IS OFF" instead of the local IP address.
--
Peter
 
#4
On Mon, 19 Apr 2010 13:01:27 -0400, rconn <> wrote:

|@IPADDRESS hasn't changed for months.

I haven't used it recently, but today, with build 47, it doesn't work as
documented (whereas in v10, it does).

v:\> ver & echo %@ipaddress[]

TCC 11.00.47 Windows XP [Version 5.1.2600]
ECHO is OFF

v:\> ver & echo %@ipaddress[]

TCC 10.00.78 Windows XP [Version 5.1.2600]
74.71.55.217
--
- Vince
 
#5
| @IPADDRESS hasn't changed for months.

The internal variable _IP provides the information the OP sought.
Nevertheless, there are issues with both @IPADDRESS[] and @IPNAME[]. Below
are the results of a small batch file I ran both V10 and V11, with differing
results.
@IPADDRESS in V10 works as documented. In V11 an empty parameter string
returns empty value string, contrary to documentation.
@IPNAME works as documented in both V10 and V11, but the return strings
are sometimes unexpected. IMHO empty parameter string ought to return the
full IP name of the host, i.e., the same string as %_IPNAME. Why does
%@ipname[%@ipaddress] return a value other than the url... host.jpsoft.com ----------- -- Steve
 
#6
On Mon, 19 Apr 2010 14:29:55 -0400, Steve Fábián <> wrote:

|Why does
|%@ipname[%@ipaddress] return a value other than the url...lways give the canonical name. -- - Vince
 
#7
On Mon, 19 Apr 2010 14:29:55 -0400, Steve Fábián <> wrote:

|IMHO empty parameter string ought to return the
|full IP name of the host, i.e., the same string as %_IPNAME.

As documented, an empty string is not allowed. But it does seem easier for the
user (than @IPNAME[0]) and more like the way @IPADDRESS[] works.
--
- Vince
 

rconn

Administrator
Staff member
May 14, 2008
10,207
86
#8
> |@IPADDRESS hasn't changed for months.
>
> I haven't used it recently, but today, with build 47, it doesn't work
> as documented (whereas in v10, it does).
>
> v:\> ver & echo %@ipaddress[]
>
> TCC 11.00.47 Windows XP [Version 5.1.2600]
> ECHO is OFF
@IPADDRESS in v11 uses ipworks8.dll to return the host address. (In v10, it
used ipworks6.dll.) Ipworks8 has changed the class so that an empty field
now returns an empty result. I will update the documentation to reflect
this.

(Since there's an easier way to return this value, it's not much of a loss.)

Rex Conn
JP Software
 

rconn

Administrator
Staff member
May 14, 2008
10,207
86
#9
> The internal variable _IP provides the information the OP sought.
> Nevertheless, there are issues with both @IPADDRESS[] and @IPNAME[].
> Below are the results of a small batch file I ran both V10 and V11, with
> differing results.
> @IPADDRESS in V10 works as documented. In V11 an empty parameter
> string returns empty value string, contrary to documentation.
The third-party dll changed; I will update the documentation to reflect that
an empty parameter is not allowed.


> @IPNAME works as documented in both V10 and V11, but the return
> strings are sometimes unexpected.
WAD; I don't know of any cases where the returned strings are incorrect.


> IMHO empty parameter string ought to return the full IP name of
> the host, i.e., the same string as %_IPNAME.
Why not just use %_IPNAME? I see no purpose in duplicating functionality.


> Why does %@ipname[%@ipaddress] return a value other than the url...'s the correct name. Rex Conn JP Software
 
#10
| ---Quote---
|| The internal variable _IP provides the information the OP sought.
|| Nevertheless, there are issues with both @IPADDRESS[] and @IPNAME[].
|| Below are the results of a small batch file I ran both V10 and V11,
|| with differing results.
|| @IPADDRESS in V10 works as documented. In V11 an empty parameter
|| string returns empty value string, contrary to documentation.
| ---End Quote---
| The third-party dll changed; I will update the documentation to
| reflect that an empty parameter is not allowed.
|
|
|
| ---Quote---
|| @IPNAME works as documented in both V10 and V11, but the return
|| strings are sometimes unexpected.
| ---End Quote---
| WAD; I don't know of any cases where the returned strings are
| incorrect.
|
|
|
| ---Quote---
|| IMHO empty parameter string ought to return the full IP name of
|| the host, i.e., the same string as %_IPNAME.
| ---End Quote---
| Why not just use %_IPNAME? I see no purpose in duplicating
| functionality.
|
|
|
| ---Quote---
|| Why does %@ipname[%@ipaddress] return a value other than the ||...nted, is still a bit of mystery. -- Steve
 

rconn

Administrator
Staff member
May 14, 2008
10,207
86
#11
> The reason why the value of %@IPNAME[0] is only the local machine
> name, not the local URL, although exactly as documented, is still a
> bit of mystery.
Because that's what ipworks8.dll returns for GetHostName(0).

If this is a problem for you, I'd recommend not using that syntax, or even
pretending it doesn't exist! :-)

Rex Conn
JP Software
 
#12
| ---Quote---
|| The reason why the value of %@IPNAME[0] is only the local machine
|| name, not the local URL, although exactly as documented, is still a
|| bit of mystery.
| ---End Quote---
| Because that's what ipworks8.dll returns for GetHostName(0).
|
| If this is a problem for you, I'd recommend not using that syntax,
| or even pretending it doesn't exist! :-)

As I wrote previously, it's not an issue, I was just curious. You explained
how TCC obtains the value, I am still curious (but nothing more) why the
vendor of ipworks8.dll selected this value (which is already available
directly from the environment).
--
Steve
 
#13
On Tue, 20 Apr 2010 08:52:21 -0400, Steve Fábián <> wrote:

|| ---Quote---
||| IMHO empty parameter string ought to return the full IP name of
||| the host, i.e., the same string as %_IPNAME.
|| ---End Quote---
|| Why not just use %_IPNAME? I see no purpose in duplicating
|| functionality.

What's %_IPNAME? It doesn't seem to exist in my TCC.

%_IP is difficult to use because it contains **all** IPs.

Can TCC turn "74.71.55.217" (my IP) into "cpe-74-71-55-217.twcny.res.rr.com" as
NSLOOKUP does? I can get "vefatica.net" out of @IPNAME[] because that's what my
HOSTS file says. Without that HOSTS entry, @IPNAME[] gives "ZZ.twcny.rr.com" (a
meaningless combination of my computer name and a default suffix). How Windows
responds to some Winsock calls changed some years back, making it more difficult
to query an outside DNS server. I doubt IPWorks has taken the trouble to do it.
--
- Vince
 
#14
| What's %_IPNAME? It doesn't seem to exist in my TCC.

Sorry, it is actually in my own TCSTART:
set _ipname=%@ipname[%_ip]

(actually it is a loop to process all IP addresses that might be enumerated
by _IP). Obviously I had forgotten how it is created until I searched my
batch files...

--
Steve
 
Feb 1, 2010
15
0
#15
[...]
DESCRIBE - fixed a sporadic Windows problem when descriptions contain extended ASCII characters (and the description file is not Unicode).
[...]
Thanks for that! I was waiting for it since I bought TCC 11.

Regards,
Esteban
<o><o><o>

</o></o></o>