Wrong .INI file used by TCC

May 20, 2008
3,515
4
Elkridge, MD, USA
In my All Users\Start Menu\Programs\Startup directory there is a link file,
executed during logging in, which analyzed with the TCC9 command SHORTCUT is
as follows:

----- begin AllUsers.Startup.lnk -----
Command=C:\JPSOFT\K09\tcc.exe
Arguments=/H /IP /IS /@C:\LOG\LOADGLBL.INI /C STARTUP.BTM Allusers.Startup
Directory=C:\LOG
DescriptionLink=AllUsers.Startup.lnk
Icon=C:\JPSOFT\K09\TCC.EXE
Offset=0
Mode=1
Hotkey
----- end AllUsers.Startup.lnk -----

All files mentioned exist. One of the commands in STARTUP.BTM is:

echo %_isodate %_time + %pid %@word[0,%_wintitle] LOGIN %_cmdspec %ver
%_ininame >> C:\LOG\USAGE.LOG

(all in one line, of course)

where pid is %_pid, left padded with zeroes to 4 digits. I added the
"%_ininame" field today.

The line in USAGE.LOG created by this command is:

2009-01-28 15.22.56 + 2480 AllUsers.Startup LOGIN C:\JPSOFT\K09\tcc.exe
09.02.154 C:\Documents and Settings\ESF\Local Settings\Application
Data\JPSoft\TCMD.INI

(all in one line). What this report tells me is that despite the explicit
specification of the initialization file in the command starting this
instance of TCC it used the default path to find TCMD.INI (which did not
exist).

BTW, this is the problem which causes the DirHistory directive to be set to
4096, and my global history table to max. out at less than 11000 characters.
--
Steve
 
May 20, 2008
3,515
4
Elkridge, MD, USA
Steve Fábián wrote:
| In my All Users\Start Menu\Programs\Startup directory there is a link
| file, executed during logging in, which analyzed with the TCC9
| command SHORTCUT is as follows:
|
| ----- begin AllUsers.Startup.lnk -----
| Command=C:\JPSOFT\K09\tcc.exe
| Arguments=/H /IP /IS /@C:\LOG\LOADGLBL.INI /C STARTUP.BTM
| Allusers.Startup Directory=C:\LOG
| DescriptionLink=AllUsers.Startup.lnk
| Icon=C:\JPSOFT\K09\TCC.EXE
| Offset=0
| Mode=1
| Hotkey
| ----- end AllUsers.Startup.lnk -----
|

I changed the order of arguments to:

Arguments=/@C:\LOG\LOADGLBL.INI /H /IP /IS /C STARTUP.BTM

which fixed the problem!

Note: This is somewhat of an RTFM issue (meaning my fault). Topic
"cmdlineopts.htm" does display the alternate initialization file before
other options, but it may result in inconsistency - what happens if an
alternate initialization file is specified, as well as the /I or /II option
(oxymoronic command line - bot the use of no initialization file and an
explicit initialization file specified).
--
Steve
 

rconn

Administrator
Staff member
May 14, 2008
12,404
152
Steve Fábián wrote:


> I changed the order of arguments to:
>
> Arguments=/@C:\LOG\LOADGLBL.INI /H /IP /IS /C STARTUP.BTM
>
> which fixed the problem!

The .INI file *must* be the first argument on the line; no alternate
format will work.


> Note: This is somewhat of an RTFM issue (meaning my fault). Topic
> "cmdlineopts.htm" does display the alternate initialization file before
> other options, but it may result in inconsistency - what happens if an
> alternate initialization file is specified, as well as the /I or /II option
> (oxymoronic command line - bot the use of no initialization file and an
> explicit initialization file specified).

GIGO.

Rex Conn
JP Software
 
Similar threads
Thread starter Title Forum Replies Date
JohnQSmith New online help file wrong logo Support 7
vefatica @EXECSTR ... TCSTART ... something's wrong! Support 7
R History window wrong size, can't remember size change Support 12
mfarah Fixed The DATE command produces the wrong error message. Support 1
MikeBaas @regsetenv complains "wrong parameter" Support 14
mikea How to? TCC registered to wrong 'entity' Support 5
T @replace -- what is wrong here Support 2
vefatica Fixed KEYSTACK /i with repeat count sends wrong keys Support 7
C ZIP/U compares wrong timestamp Support 13
vefatica @WORDS, often wrong Support 0
vefatica gcd() ... wrong answer, lcm() hangs Support 5
D What is wrong with this code? Support 7
vefatica WAD DIR /HL still gets names wrong Support 16
H Fixed DIR /G returns wrong sizes Support 2
M Another "What is wrong?" Support 8
M What is wrong with this command? Support 4
vefatica Updater says wrong version Support 1
CWBillow Wrong icons keep sticking Support 6
M How to? What am I doing wrong/not understanding? Support 10
C News link wrong Support 1
M What am I doing wrong? Support 12
M What am I doing wrong here? Support 2
C Forum column headings wrong? Support 4
gschizas Installation folder for TCMD x64 15.1 is wrong Support 5
Dan Glynhampton Documentation v15 help: ECHOXERR Help Page Title is Wrong Support 0
M What am I doing wrong in this (very simple!) code? Support 3
vefatica Something wrong with @PID Support 10
J zip wrong central directory signature Support 12
S Fixed _DO_FILES and _DO_DIRS wrong Support 0
B Downloading Updates - Error: Wrong file size?? Support 3
vefatica What's wrong here? Support 2
vefatica Wrong startup file? Support 1
M How to? Missing closing quote: What am I doing wrong???? Support 7
gschizas (minor) Help topic "Colors, Color Names and Codes" is wrong Support 0
T Wrong prompt in Windows command console Support 3
M Where am I going wrong with ALIAS??? Support 7
G Wrong File Size Support 8
vefatica Updating v10: error wrong file size Support 2
K_Meinhard Wrong sender adress Support 0
G Documentation on TCMD.INI Support 9
RChrismon How to? Copy TCMD.INI to New Version Support 7
vefatica Documentation INI file location? Support 2
D Custom ini-file is not read, by tcmd.exe cli Support 6
Alpengreis Fixed New INI directive "ANSIWin10" is invalid Support 2
Alpengreis TCMD.INI: The "super hidden" problem ... Support 6
D Fresh instance of TCMD does not use TCMD.INI Support 7
C Optimum Placement for TCMD.ini and others? Support 6
cgunhouse Documentation Locating the TCMD.INI File Support 9
D V19: toolbar /r "path\tctoolbar.ini" Support 1
B Fixed Error messages from TCMD.INI Support 2

Similar threads