TC buttonbar on CD-Rom
Moderators: Hacker, petermad, Stefan2, white
TC buttonbar on CD-Rom
I want to put TC among with some other programmes on a cd-rom. Now to start some of these programmes, it would be nice to have them in the button bar. Is this possible (since the drive letter for the cd-rom is different on almost every computer)? Can I use somethin' like %srcdrv% (that one doesn't work, that's for sure, but it's an example of what I'm looking for).
- ghisler(Author)
- Site Admin
- Posts: 50475
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
There have been such discussions here in the board, just use the search function. The next TC version will set such an environment variable.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
- ghisler(Author)
- Site Admin
- Posts: 50475
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
The variable is called COMMANDER_PATH, and it will be used like this:
[FileSystemPlugins]
sampleplugin=%commander_path%\sampleplugin\sample.wfx
The variable itself does NOT contain a trailing backslash!
[FileSystemPlugins]
sampleplugin=%commander_path%\sampleplugin\sample.wfx
The variable itself does NOT contain a trailing backslash!
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
Could you also implement a variable like %commander_drive%?? That's what I'm looking for...ghisler(Author) wrote:The variable is called COMMANDER_PATH, and it will be used like this:
[FileSystemPlugins]
sampleplugin=%commander_path%\sampleplugin\sample.wfx
The variable itself does NOT contain a trailing backslash!
I fully agree to Guillaume: %COMMANDER_DRIVE% would be usefull too. If I want to start applications which are located above Total Commander in the directory tree %COMMANDER_PATH% isn't sufficient.Guillaume wrote:Could you also implement a variable like %commander_drive%?? That's what I'm looking for...ghisler(Author) wrote:The variable is called COMMANDER_PATH, and it will be used like this:
[FileSystemPlugins]
sampleplugin=%commander_path%\sampleplugin\sample.wfx
The variable itself does NOT contain a trailing backslash!
You are right. One of the variables is redundant. You could also use %COMMANDER_DRIVE%\Total Commander\program files\..whatevernorfie wrote:I don't agree.I fully agree to Guillaume: %COMMANDER_DRIVE% would be usefull too. If I want to start applications which are located above Total Commander in the directory tree %COMMANDER_PATH% isn't sufficient.
E.g.
COMMANDER_PATH=C:\TOTALCMD
access to program files can be realized with
"%COMMANDER_PATH%\..\program files"
But there is a disadvantage when using something like "%COMMANDER_PATH%\..\program files: Every time I change Total Commanders location I have to adept the location of the external programs:
Example:
H:\Whatever\Totalcmd
Program called:
H:\Programs\Test\Test.exe
your solution:
%COMMANDER_PATH%\..\..\Programs\Test\Test.exe
moving Total Commander to
H:\Totalcmd
i need to redefine the call to:
%COMMANDER_PATH%\..\Programs\Test\Test.exe

I don't want any dependency between Total Commanders location and external program locations!
Redundancy is good sometimes!
Summary:
%COMMANDER_PATH% - Fine for Total Commander related stuff
%COMMANDER_DRIVE% - Fine for programs not related to Total Commander
If these programs have the same drive as TC, then they are a bit related to TC, aren't they?Lefteous wrote:%COMMANDER_DRIVE% - Fine for programs not related to Total Commander

%COMMANDER_PATH% is intended for launching TC and its plugins from any location on any PC without changing ini and bar files. If your progs are located in TC dir you can use %COMMANDER_PATH% in config files. If your progs reside outside TC there's no reason to use %COMMANDER_DRIVE% to point to them. Use %MY_PROGS_DRIVE% env. var. for this, because they are not related to TC in this case (these progs may be in different places on different PCs or even absent at all).
Nevertheless I like %COMMANDER_DRIVE% idea but cannot think of any usage of it...

- sqa_wizard
- Power Member
- Posts: 3893
- Joined: 2003-02-06, 11:41 UTC
- Location: Germany
Keep fingers crossed, that the %COMMANDER_PATH% is filled with the real drive just after launching TC.
Usually TC is started by AUTORUN.INF, which means with smth. like ".\Total Commander\TotalCmd.exe".
No drive, no ini entry, no registry and even the CL entry looks like "/i=.\Total Commander\wincmd.ini".

Usually TC is started by AUTORUN.INF, which means with smth. like ".\Total Commander\TotalCmd.exe".
No drive, no ini entry, no registry and even the CL entry looks like "/i=.\Total Commander\wincmd.ini".

#5767 Personal license
- sqa_wizard
- Power Member
- Posts: 3893
- Joined: 2003-02-06, 11:41 UTC
- Location: Germany