Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

Original command line?

May
603
0
When I came in to work this morning, my computer had rebooted itself
(presumably for some useful Microsoft updates) and I had four stand alone
tcc windows remaining on my screen.

Is there a way to see what the original invocation was? e.g. "c:\program
files\jpsoft\tcmd11\tcc.exe /c foobar"

--
Jim Cook
2010 Sundays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Monday.
 
Is there a way to see what the original invocation was? e.g. "c:\program files\jpsoft\tcmd11\tcc.exe /c foobar"
Depending on how big your screen buffer and history list settings are, you could in each of the four:

- scroll back using Alt + the arrow keys

- call up the command history window with the Page Up key

- type the history command with the options /p for page-wise output, and /n for no dupes. Commands are displayed in chronological order, i.e. oldest first.
 
Thanks, Charles. I should have thought of that. How that escaped my
attention, I do not know. I use procexp all the time, and in fact was just
showing somebody that usage this morning. /headslap

Arminius: Thank you, but I wasn't clear that the command would not be in the
history, but instead was passed in initially on the command line to
tcc.exe.
*
*
On Mon, Jun 28, 2010 at 8:36 AM, Arminius <> wrote:


> ---Quote (Originally by Jim Cook)---
> Is there a way to see what the original invocation was? e.g. "c:\program
> files\jpsoft\tcmd11\tcc.exe /c foobar"
> ---End Quote---
> Depending on how big your screen buffer and history list settings are, you
> could in each of the four:
>
> - scroll back using Alt + the arrow keys
>
> - call up the command history window with the Page Up key
>
> - type the history command with the options /p for page-wise output, and /n
> for no dupes. Commands are displayed in chronological order, i.e. oldest
> first.
>
>
>
>
>



--
Jim Cook
2010 Sundays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Monday.
 
On Mon, 28 Jun 2010 12:00:19 -0400, Jim Cook <>
wrote:

|> Is there a way to see what the original invocation was? e.g. "c:\program
|> files\jpsoft\tcmd11\tcc.exe /c foobar"

I know TCSTART has access to the command line args used to create the
TCC process. I was a little surprised that the command line is not
available later.

I added _STARTUPCMD to the 4UTILS plugin. It was nearly trivial;
maybe Rex will include such a variable in the next version. New
4UTILS on lucky.syr.edu and barnyard.syr.edu.

Code:
v:\> uhelp _startupcmd
TCC process command line

v:\> echo %_startupcmd
d:\tc11\tcc.exe /q
--
- Vince
 
Why did updates trigger TCC? Did you replace the compsec variable? Or change the default association for cmd?

I have always been very reluctant to do either, since TCC is not fully compatible with CMD.
 
On Mon, 28 Jun 2010 12:00:19 -0400, Jim Cook <>
wrote:

I added _STARTUPCMD to the 4UTILS plugin. It was nearly trivial;
maybe Rex will include such a variable in the next version. New
4UTILS on lucky.syr.edu and barnyard.syr.edu.

CMDCMDSPEC does this, too.
 
On Mon, 28 Jun 2010 21:18:09 -0400, dcantor <>
wrote:

|---Quote (Originally by vefatica)---
|On Mon, 28 Jun 2010 12:00:19 -0400, Jim Cook <>
|wrote:
|
|I added _STARTUPCMD to the 4UTILS plugin. It was nearly trivial;
|maybe Rex will include such a variable in the next version. New
|4UTILS on lucky.syr.edu and barnyard.syr.edu.
|---End Quote---
|CMDCMDSPEC does this, too.

What is CMDCMDSPEC?

Do you mean _CMDSPEC? That just gives the program name. See the
difference:

Code:
v:\> type startupcmd.bat
echo %_startupcmd
echo %_cmdspec

v:\> %comspec /c startupcmd.bat
D:\TC11\TCC.EXE /c startupcmd.bat
D:\TC11\TCC.EXE
 
I believe this is a Windows 7 feature. When Win7 installs an update and
reboots your PC, it attempts to relaunch all the same apps that were
running at the time it rebooted. I'm just guessing at that as I have
witnessed similar behavior. However, I haven't read anything about it.

-Scott




Rod Savard <> wrote on 06/28/2010 09:08:30 PM:


> Why did updates trigger TCC? Did you replace the compsec variable?
> Or change the default association for cmd?
>
> I have always been very reluctant to do either, since TCC is not
> fully compatible with CMD.
>
>
>
>
 
On Mon, 28 Jun 2010 21:18:09 -0400, dcantor <>
wrote:

|---Quote (Originally by vefatica)---
|On Mon, 28 Jun 2010 12:00:19 -0400, Jim Cook <>
|wrote:
|
|I added _STARTUPCMD to the 4UTILS plugin. It was nearly trivial;
|maybe Rex will include such a variable in the next version. New
|4UTILS on lucky.syr.edu and barnyard.syr.edu.
|---End Quote---
|CMDCMDSPEC does this, too.

What is CMDCMDSPEC?

Do you mean _CMDSPEC? That just gives the program name. See the
difference:

Code:
v:\> type startupcmd.bat
echo %_startupcmd
echo %_cmdspec

v:\> %comspec /c startupcmd.bat
D:\TC11\TCC.EXE /c startupcmd.bat
D:\TC11\TCC.EXE


Oops. I meant %CMDCMDLINE%

See cmd_comp.htm in the help file.
 

Similar threads

Back
Top