DIR switches not working?

#1
Hello,

I just upgraded to TCMD version 9.02.151, after having happily trucked along with 4NT version 3.02B for quite a while. I've been a fan/user of JPSoft's products since 4DOS/4OS2, and even TCMD32 version 1.01

I just installed the new product on a fresh copy of Windows Server 2003 Std. edition R2 64bit, and noticed a problem with switches to the DIR command. They are not recognized, like so:

Unknown command "/2"

That syntax (dir /2) works OK on the same machine using the older version of 4NT. It's probably something stupid I've overlooked; can someone point me to the solution?

Searching these forums led to no result, because "dir" is too short for the search function.
 
#2
On Mon, Aug 18, 2008 at 8:02 AM, henry <> wrote:

> That syntax (dir /2) works OK on the same machine using the older version of
Is your DIR an alias? Using 9.02.151 and "*dir /2" here works just
fine. Perhaps your pseudovariables for Escape, Parameter, and/or
Switch are different than before. Use OPTION and look at the Advanced
tab to make sure the Special Characters match what you had before.

--
2008 Fridays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Saturday.
Measure wealth by the things you have for which you would not take money.
 
#3
On Mon, Aug 18, 2008 at 8:02 AM, henry <> wrote:



Is your DIR an alias?
Bingo, that was it. The DIR alias was part of an old ALIASES file I've been packing around for a dozen or so years, and it used the older parameters character (DIR=*dir /p %&). Change that last char to $, and all is well. I just knew it was something stupid like that. I guess that goes to show what happens when you wait so long to upgrade, but the product works so well I just kept using my tried and true version.
 
#4
henry wrote:
| Bingo, that was it. The DIR alias was part of an old ALIASES file
| I've been packing around for a dozen or so years, and it used the
| older parameters character (DIR=*dir /p %&). Change that last char to
| $, and all is well. I just knew it was something stupid like that. I
| guess that goes to show what happens when you wait so long to
| upgrade, but the product works so well I just kept using my tried and
| true version.

I still (and quite a few other users) use the 4DOS defaults for EscapeChar,
CommandSep and and ParameterChar (set in my TCC.INI file), without any
problems. It makes backward compatibility easier.
--
Steve