Startup/Shutdown order of events for TCC

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
Jun 7, 2008
121
0
#1
Hi

This might be undocumented and for good reason:
It gives Rex freedom to change things.

Is it documented anywhere what order TCC does thing on startup/shutdown? I mean processing of TCSTART, TCEXIT, the startup options etc.

Thanks

Stephen Howe
 
#2
On Thu, 04 Dec 2008 14:53:10 -0600, Stephen Howe <> wrote:


>Hi
>
>This might be undocumented and for good reason:
>It gives Rex freedom to change things.
>
>Is it documented anywhere what order TCC does thing on startup/shutdown? I mean processing of TCSTART, TCEXIT, the startup options etc.
It only makes sense that INI directives are applied and plugins are loaded
before tcstart and that tcexit is processed before plugins are unloaded. Can
you be more specific?
 
Jun 7, 2008
121
0
#3
Hi

It only makes sense that INI directives are applied and plugins are loaded
before tcstart and that tcexit is processed before plugins are unloaded. Can you be more specific?
That is what I meant (and any other detail fleshed out). Is it documented as such?

Cheers

Stephen Howe
 
#4
Stephen Howe wrote:
| ---Quote---
|
| It only makes sense that INI directives are applied and plugins are
| loaded
| before tcstart and that tcexit is processed before plugins are
| unloaded. Can you be more specific? ---End Quote---
|
| That is what I meant (and any other detail fleshed out). Is it
| documented as such?

Help topic "autobatch.htm" states that the location of TCSTART can be
specified in the .INI file, which IMPLIES that the .INI file must be
processed first.

Rex:

1/ It would be useful if the order of events during starting and stopping of
the command processor were documented.

2/ I did not find OPTION dialog entries to control the StartupFile and
ExitFile directives introduced in V7, nor any documentation. They ought to
be in help topic "autobatch.htm", which only mentions the now obsolete
method of specifying a StartPath without TCSTART to avoid using one.
--
Steve
 

rconn

Administrator
Staff member
May 14, 2008
10,099
85
#6
Stephen Howe wrote:


> This might be undocumented and for good reason:
> It gives Rex freedom to change things.
>
> Is it documented anywhere what order TCC does thing on
>

> startup/shutdown? I mean processing of TCSTART, TCEXIT,
> the startup options etc.

It is documented in "TCC Startup Options", but it has changed in recent
versions of TCC and in different versions of Windows.

Why do you need to know?

Rex Conn
JP Software
 

rconn

Administrator
Staff member
May 14, 2008
10,099
85
#7
Steve Fábián wrote:

> Stephen Howe wrote:
> | ---Quote---
> |
> | It only makes sense that INI directives are applied and plugins are
> | loaded
> | before tcstart and that tcexit is processed before plugins are
> | unloaded. Can you be more specific? ---End Quote---
> |
> | That is what I meant (and any other detail fleshed out). Is it
> | documented as such?
>
> Help topic "autobatch.htm" states that the location of TCSTART can be
> specified in the .INI file, which IMPLIES that the .INI file must be
> processed first.
>
> Rex:
>
> 1/ It would be useful if the order of events during starting and stopping of
> the command processor were documented.
It already is. But why would you care?


> 2/ I did not find OPTION dialog entries to control the StartupFile and
> ExitFile directives introduced in V7, nor any documentation. They ought to
> be in help topic "autobatch.htm", which only mentions the now obsolete
> method of specifying a StartPath without TCSTART to avoid using one.
There never has been, because they're not useful and have been retired.

Rex Conn
JP Software