Should "tc2usb" tool be updated?

[PeaceMaker]

Hi to all! Please vote...

[m^2]

Why?

[PeaceMaker]

Well, it could have some changes:

- New TC v7.x icon.
- Some nice splash screen during startup (like "Portable Firefox").
- Installation feature from USB to local machine (with all shortcuts, REG entry and *.INI files placement).

[m^2]

- Some nice splash screen during startup (like "Portable Firefox").

*cough*cough*cough*

- New TC v7.x icon.

This one is OK. But it's not an important thing, at least if I were tc2usb user, I wouldn't care.

[PeaceMaker]

- New TC v7.x icon.

This one is OK. But it's not an important thing, at least if I were tc2usb user, I wouldn't care.

"Could" doesn't mean "have to"

[karlchen]

Well, well, if the only things that need being updated/added are a fancy splash screen and changing programme icon itself, hm, then updating tc2usb is not really the most urgent affair in the world.

Karl

[PeaceMaker]

TC2USB tool could also support TC7 logging feature by default.

[menet]

I have encountered several bugs using it.

I have, after using it, to review the INI files installed and to delete several folders created twice. The problems occur with plugings using :
- space characters in the file name (Total SQX, HTTP Browser, ...),
- being of several types (Imagine is WCX and WLX, ...),
- being an only file not in a dedicated folder (cpio.wcx, rpm.wcx, ...)
- ...

Without review, the size of TC directory on USB was multiply by 2 and I don't know if all plugings were running well.

Regards

[ghisler(Author)]

How should tc2usb detect these cases? It simply cannot know which files in the same directory belong to the plugin and which don't. There are several plugins out there which use several supporting files like dlls, language files etc. Since the normal way to install a plugin is in a separate folder, tc2usb copies that folder to the stick. This way the plugin will most probably work, but there may be additional files.

[VSB]

I said "No!" because all that nee is straight hands to replace c:\totalcmd to %COMMANDER_PATH% (it's also useful if you are using TC in different systems which have different "C:\" drive(e.g. XP and Vista))
and create simple bat file to run it with needed paths and load the needed inis

[m^2]

I said "No!" because all that nee is straight hands to replace c:\totalcmd to %COMMANDER_PATH% (it's also useful if you are using TC in different systems which have different "C:" drive(e.g. XP and Vista))
and create simple bat file to run it with needed paths and load the needed inis

You don't need a .bat file. Search the forum for questions about TC's portablility.

[geoapps]

Just been using it, and a couple of things it needs:

1. it will only accept "wincmd.ini" as the INI file; if you use something else (e.g. totalcmd.ini) it won't set that to the default INI file for totalcmd.exe

2. FWIW it doesn't change "InstallDir" in the copied INI file

3. If there are subdirectories of the TC install directory, you should be able to copy those. I keep button-bar icons in a subdir called ".\icons", for example, and I have to copy those manually, and if you have utilities or editors you want to copy with WinCMD those could be in a ".\bin" subdir, with the appropriate pathing set in DEFAULT.BAR or WINCMD.INI

4. It should tweak DEFAULT.BAR, WINCMD.INI, and WCX_FTP.INI to remove references to the original install path (e.g. C:\Util\WINCMD) and replace them with relative paths (e.g. \Util or .\icons).

Just some thoughts ...

[VSB]

No.
All, what You need is Straight_Hands, Notepad, and TC.
Just change absolute paths in INI to relative (with %COMMANDER_PATH%), then copy TC folder to USB and write correct command line.

[VSB]

Also, it's usefull to use PStart

[moonmoon]

it's no need to update.just i thought.