tc2usb tool is obsolete

[eugensyl]

tc2usb tool is obsolete, as is write on TC site:
The tool will NOT copy programs to the stick to which you link on the button bar. New (December 15, 2009): Support new files included with Total Commander 7.50. Only works with 32-bit version so far!

Why only with 32-bit version?

Since 2009 a lot of improvement are made on TC and this tool is obsolete - and this is why I put the topic here.

I have TC on USB Stick and a various computer to support, both 32 and 64-bit version.

The main bug with this tool is that executable resulted always lance 32-bit version of TC, doesn't mater if the system is 64-bit or 32-bit.
My wish is to lance the appropriate version.

The version 8.50 is a major update and this tool must be updated too.


So, is not so bad bug... but must be considered as it is.

[Horst.Epp]

There is no real need for this tool at all.
If your TC installation uses the correct environment variables and has the settings in the program dir you can just copy the TC tree to any place and start the 32bit or x64 version of TC from this.
If course all the tools and icons you are using must be part of your TC tree.

[eugensyl]

There is no real need for this tool at all.
If your TC installation uses the correct environment variables and has the settings in the program dir you can just copy the TC tree to any place and start the 32bit or x64 version of TC from this.
If course all the tools and icons you are using must be part of your TC tree.

Sorry... Sychronizing TC folders is enough to keep an USB TC installation identical. My post is about the file starttc.exe in the root of drive witch must start the appropriate version of TC, depending of the OS version.

Now I must traverse three levels of directories and a lot of files in TC directory. In 32-bit is quite simple: Double-Click on starttc.exe and TC is running. I'm a lazy man and I hate to navigate with explorer.
For me is important only this file: starttc.exe but customized with my path, exactly like in 32-bit version.

I'm sure Mr. Ghisler understand...

[silencer]

I had the same situation, but i now just use a simple totalcmd.bat file in the root of my USB.

START "" ..\Programs\totalcmd\totalcmd64.exe

[silencer]

I like to choose myself if 64 or 32 is started (due to some 32bit plugins) but if you like the script to choose, you can use the following.

if "%PROCESSOR_ARCHITECTURE%"=="AMD64" goto 64BIT
echo 32-bit OS
START "" ..\Programs\totalcmd\totalcmd.exe
:64BIT
echo 64-bit OS
START "" ..\Programs\totalcmd\totalcmd64.exe
:END

[eugensyl]

I had the same situation, but i now just use a simple totalcmd.bat file in the root of my USB.

START "" ..\Programs\totalcmd\totalcmd64.exe

That is! I appreciate your code.
I meet somewhere the enviroment where CMD is forbidden.
I can made EXE from CMD with microsoft tools but my policy doesn't allow to run this .exe

So, the simple way is a proffessional tool to make this start_tc.exe file.

Thank you 'silencer' for your interest!

[Horst.Epp]

I had the same situation, but i now just use a simple totalcmd.bat file in the root of my USB.

START "" ..\Programs\totalcmd\totalcmd64.exe

That is! I appreciate your code.
I meet somewhere the enviroment where CMD is forbidden.
I can made EXE from CMD with microsoft tools but my policy doesn't allow to run this .exe

So, the simple way is a proffessional tool to make this start_tc.exe file.

Thank you 'silencer' for your interest!

If your policy allows to start start_tc.exe just use Autohotkey and compile a script with this name.
I don't see how your policy can detect it without being tied to a very special exe which is useless for security reasons.

[eugensyl]

I had the same situation, but i now just use a simple totalcmd.bat file in the root of my USB.

START "" ..\Programs\totalcmd\totalcmd64.exe

That is! I appreciate your code.
I meet somewhere the enviroment where CMD is forbidden.
I can made EXE from CMD with microsoft tools but my policy doesn't allow to run this .exe

So, the simple way is a proffessional tool to make this start_tc.exe file.

Thank you 'silencer' for your interest!

If your policy allows to start start_tc.exe just use Autohotkey and compile a script with this name.
I don't see how your policy can detect it without being tied to a very special exe which is useless for security reasons.

I do not allow to run a script from temporary directory, like self-extracting archive, because of extraordinary spreading of malware.

[ghisler(Author)]

No, it's not obsolete - it only supports 32-bit so far because only the 32-bit version runs on all Windows PCs since Windows 95. The 64-bit version only runs on 64-bit Windows.

[Horst.Epp]

That is! I appreciate your code.
I meet somewhere the enviroment where CMD is forbidden.
I can made EXE from CMD with microsoft tools but my policy doesn't allow to run this .exe

So, the simple way is a proffessional tool to make this start_tc.exe file.

Thank you 'silencer' for your interest!

If your policy allows to start start_tc.exe just use Autohotkey and compile a script with this name.
I don't see how your policy can detect it without being tied to a very special exe which is useless for security reasons.

I do not allow to run a script from temporary directory, like self-extracting archive, because of extraordinary spreading of malware.

A compiled Autohotkey file is a normal exe and not a script or self extracting archive..

[silencer]

If you prefer a tool you can also use the tool LaunchTC from Lefteous and configure the launchtc.ini to use totalcmd64.exe

[eugensyl]

No, it's not obsolete - it only supports 32-bit so far because only the 32-bit version runs on all Windows PCs since Windows 95. The 64-bit version only runs on 64-bit Windows.

I said 'obsolete' because when it was made the 64bit of TC wasn't exist or it was in testing.
No, it is not obsolete, I use it often. But must have an upgrade for each of OS version. One tool.
Remember the discussion about TC distribution kit.
It's the same request.
You can measure how many people download the 32bit, 64 bit or 32+64 bit and then you can take a conclusion how useful can be, even for you on testing.

Now I work with cmd version, but I prefer an executable.
As I said, my executable made with an archiver don't pass my local policy against viruses. I do not allow to run executable from temp.

Crypto Locker (please fill free to search about this most dangerous v1ru5) change totally my mind about protection and backups.

Thanks!