Wrong .INI file used by TCC

#1
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
 
#2
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
10,325
94
#3
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