Welcome!

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

SignUp Now!

starting in chosen directory

When I start TCC it shows the path [C:\Program Files\JPSoft\TCMD12] -
I have in the past been able to get it to start in a directory of my choice instead. I have forgotten how to do it, and searching through help has been fruitless. Can anyone help?

Regards

_John Sampson_
 
When I start TCC it shows the path [C:\Program Files\JPSoft\TCMD12] - I have in the past been able to get it to start in a directory of my choice instead. I have forgotten how to do it, and searching through help has been fruitless. Can anyone help?

I would recommend setting the "Start in" directory in the properties of the shortcut you use to launch TCC. (Right-click on the icon, Properties, Shortcut.)

You can also change the directory in TCStart.btm, but I don't recommend that approach. It can have unforeseen side effects for pipes.
 
On Thu, 27 Jan 2011 12:16:07 -0500, Charles Dye <> wrote:

|You can also change the directory in TCStart.btm, but I don't recommend that approach. It can have unforeseen side effects for pipes.

But you could avoid such difficulties with the likes of

Code:
IF @_PIPE NE 1 .AND. @_TRANSIENT NE 1 CDD ...

Actually, I avoid all tcstart processing (appropriate for me) thus:

Code:
IFF %_TRANSIENT == 1 .OR. %_PIPE == 1 THEN
	QUIT
ELSE
	REM normal instance
	REM ...
ENDIFF
 
On Thu, 27 Jan 2011 12:16:05 -0500, Charles Dye <>
was claimed to have wrote:


>I would recommend setting the "Start in" directory in the properties
>of the shortcut you use to launch TCC. (Right-click on the icon,
>Properties, Shortcut.)
>
>You can also change the directory in TCStart.btm, but I don't
>recommend that approach. It can have unforeseen side effects
>for pipes.

Personally I've had my best luck changing the directory in TCStart.

I have a sections that I skip if _pipe or _transient are set to avoid
this exact situation. Within that block is this:

if "%_cwds" eq "%@path[%@full[%comspec]]"

This catches when TCMD wants to start in it's own directory, but avoids
changing the directory randomly when TCMD needs to start in another
directory.

I dislike modifying shortcuts (in general) because that's something I
need to do in several places, on several machines, and it often gets
undone when upgrading.
 
---- Original Message ----
From: thedave
| I dislike modifying shortcuts (in general) because that's something I
| need to do in several places, on several machines, and it often gets
| undone when upgrading.
Save your analyzed shortcuts using the SHORTCUT command. You can write a simple TCC batch program to build and install customized shortcuts (as well as aliases) based on a few environment variables describing each hardware platform.
--
Steve
 

Similar threads

Back
Top