Más detalles de 4NT 6.0 y de Take Command/32 6.0 (build 180)

4NT and Take Command have been rewritten to share a common .DLL
(TakeCmd.dll). This means they will use much less memory when
you have multiple shells open.

4NT and Take Command use a new IPWORKS version (IPWORKS6.DLL and
IPWSSL6.DLL).

4NT – no longer needs a separate KEYSTACK.EXE (it's built into
TakeCmd.dll).

4NT and Take Command now recognize Windows 2003.

Added FTPS (SSL FTP) support. The syntax is:

"ftps://[user:password@]server[:port]/filename"

For example:

copy "ftps://jpsoft.com/4nt/4nt600.exe" .

(The SSL support is still somewhat primitive; it will be enhanced
soon to support various options.)

Added HTTPS (SSL HTTP) support. The syntax is:

"https://[user:password@]server/filename"

For example:

copy "https://jpsoft.com/foo.htm" .

(The SSL support is still somewhat primitive; it will be enhanced
soon to support various options.)

Added TFTP (trivial FTP) support. Note that TFP only works with
COPY (and with a MOVE when the source is a local file). The
syntax is: "tftp://server[:port]/filename". For example:

copy update "tftp://190.189.188.0/update"

4NT and TC will now look for your FTP usernames and passwords in the
file "FTP.CFG", which is kept in the 4NT or TC directory by default
(you can specify another directory with the FTPCFG .INI directive).
You'll need to add entries to the FTP.CFG file manually; the format
for each line is:

url username password

For example:

ftp://jpsoft.com fred secret
ftp://microsoft.com anyone mypassword
ftp://sco.com ima dufus

We recommend you encrypt this file if you're using NTFS. If FTP.CFG
doesn't exist the first time 4NT / TC look for it, it will be created
as an encrypted file (NTFS only). If you're using Win9x or FAT /
VFAT, the file will *not* be encrypted. (But if you're using Win9x
or FAT/VFAT, you obviously aren't concerned with security!)

Added a new type of redirection (like the *nix "here-document").
The syntax is:

program << word

The current batch file is read up to the next occurrence of
"word", and the resulting text becomes standard input to
"program". For example:

c: estprogram.exe << endinput
input 1
input 2
input 3
endinput
echo This is the next line after "program.exe"

The parser will perform variable expansion on each line, unless
the word following << is enclosed in double quotes. If the <<
is followed by a – the leading white space on the following
lines will be removed before passing them to "program".

You can now preface an .INI filename on the startup line with a /.
This is to work around a Windows problem with not displaying
the entire command line in a shortcut when an argument begins
with @. (Note that the @ is still required; i.e.:

d:jpsoft4nt4nt.exe /@d:jpsoft4nt4nt.ini

Increased key substitution table from 64 to 128 entries.

Increased command line length to 8191 characters, and maximum length
(after expansion) to 16383 characters.

Increased maximum number of arguments per batch file command line
to 511.

Increased the global alias list size to 128K characters.

Increased the global user function list size to 64K characters.

Removed nesting limits for DO and IFF.

User functions now support the %# variable (number of arguments
passed to the function).

The user function parsing has been changed so that the switch character
('/') is not considered a parameter delimiter. (Note that this may
be changed back if too many compatibility issues arise!)

The environment variable TreeExclude specifies which drives & directories
to ignore when updating the JPSTREE.IDX file. The syntax is:

TreeExclude=dir1;dir2;dir3;…

The specified drive/directory and all of its subdirectories will be
excluded from JPSTREE.IDX update. For example, to exclude everything
in c:windows, d: emp emp2, and everything on drive g:

TreeExclude=c:windows;d: emp emp2;g: