New to TCC, Why does it use my old 4NT files?

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
Sep 11, 2009
35
0
Portland, Or.
#1
Had to get a new PC. It has Windows 7 64 bit. I installed my old 4NT and had some problems, so updated to Take Command 11 (the 64bit version)

Been using from 4DOS days, and as usual, I didn't read instructions before installing, and I was happy to note that T.C. found & used the old 4NT's 4ALIAS.BAT in the C:\ root.
It also seems to have found & used the old 4START.BAT (which has some commands that are not valid if placed in TCStart.BTM in the ...\TCMD11x64 directory ???)

There's no mention of these files in the TakeCommand.PDF (11.0) PDF file. Can I just assume that you've added that as a 'courtesy' feature? Should these be in other files?

All else seems to work much the same as those earlier versions, but I miss examples for Take Command (you had many for old 4DOS/4NT). T.C. is MUCH more complicated than those earlier programs. and more examples would be more helpful than the generic explanations in the PDF.
I have to admit, I'm having difficulty following "How to setup & use custom files" for T.C. from the PDF manual.

Bob
 

rconn

Administrator
Staff member
May 14, 2008
10,103
85
#2
> Been using from 4DOS days, and as usual, I didn't read instructions
> before installing, and I was happy to note that T.C. found & used the
> old 4NT's 4ALIAS.BAT in the C:\ root.
> It also seems to have found & used the old 4START.BAT (which has some
> commands that are not valid if placed in TCStart.BTM in the
> ...\TCMD11x64 directory ???)
TCC knows nothing about 4ALIAS.BAT; you've got to be loading that one
yourself.

TCC first looks for TCSTART.*; if it can't find that it tries 4START.*.
(This was added because a lot of users complained about being unwilling or
unable to rename their startup files.) The 4START.* / 4EXIT.* files are
obsolete, deprecated and will eventually be eliminated altogether.

Rex Conn
JP Software
 
Sep 11, 2009
35
0
Portland, Or.
#3
TCC knows nothing about 4ALIAS.BAT; you've got to be loading that one
yourself.

TCC first looks for TCSTART.*; if it can't find that it tries 4START.*.
(This was added because a lot of users complained about being unwilling or
unable to rename their startup files.) The 4START.* / 4EXIT.* files are
obsolete, deprecated and will eventually be eliminated altogether.

Rex Conn
JP Software
AHHA.. That explains it.. What was ALSO throwing me off, I hid 4ALIAS.BAT - got an error at startup, from 4START.BAT, that 4ALIAS.BAT was missing.

BUT I still had all my ALIAS's show!! ..

Turned out that I was testing with a second instance of TCMD, which must have been sharing the alias's from the first instance of TCMD! When I killed both, and started TCMD - Then I had NO alias's !

Ok, I take it then, that they belong in the TCMD11x64 directory .. In TCSTART?

Oh.. and 4START is not mentioned in the PDF.

Thanks,
Bob
 

rconn

Administrator
Staff member
May 14, 2008
10,103
85
#4
> Turned out that I was testing with a second instance of TCMD, which
> must have been sharing the alias's from the first instance of TCMD!
> When I killed both, and started TCMD - Then I had NO alias's !
>
> Ok, I take it then, that they belong in the TCMD11x64 directory .. In
> TCSTART?
Not with Windows 7 or Vista, because you can't modify anything in the
TCMD11x64 directory (unless you've installed it somewhere other than
\program files). In XP you can put it anywhere.


> Oh.. and 4START is not mentioned in the PDF.
Deliberately -- as I said, that name is obsolete and deprecated. Rename it
to TCSTART.

Rex Conn
JP Software