Upgrading from WC 4.53 to TC 6.03 on a new machine

[Robert_Charlton]

I've been using Total Commander since it was Windows Commander v4.52, but it's worked so well I've never stopped to upgrade it. I'm now making several changes simultaneously, including moving to a new computer, and I'd like to make sure I can have TC 6.03 up and running quickly on my new machine, preserving as many old settings, like my Directory Hotlist and my FTP settings, as I can.

I'm moving from v4.52 on Windows 9x to a clean install of Windows XP on a new computer. The directory structure of the data in My Documents will be essentially the same.

I understand from notes I'd made some years back that wincmd.ini and wcx_ftp.ini (both in the Windows directory) and *.bar (in the wincmd directory) are/were the key files. Additionally, I have my registration key, wincmd.key.

The *.bar files I find are Default.bar and No.bar. Also, I'm noticing that I have several other files in my wincmd directory that have fairly recent file dates... Wincmd.gid and default.br1... and I'm wondering whether these preserve any data I need.

I'm sure these file names have changed since the product has been renamed, though, and possibly the software itself has changed enough that these files may not convert over easily.

Additionally, in the new installation, I'd like to get the default program file out of the root and put it in the Program files where it belongs. The program got installed, before I knew any better, as it prompted, in c:\wincmd. I understand now that the program will install where I tell it to, but I'm concerned that there might be references to the old program default directory in, say, the ini file, which might confuse things.

I'd appreciate a step by step, if someone can guide me through. I'll be need Total Commander to manage much of the rest of my new computer setup, so it's "mission critical" that I get it up and running.

Thanks...

[Hacker]

I understand from notes I'd made some years back that wincmd.ini and wcx_ftp.ini (both in the Windows directory) and *.bar (in the wincmd directory) are/were the key files. Additionally, I have my registration key, wincmd.key.

That is absolutely correct. You only need these files (as long as you didn't add a new language to TC or use a custom icon library for TC's icons).

The *.bar files I find are Default.bar and No.bar.

From the *.bar files you don't need No.bar. It's just a button bar file that is used when the button bar is empty (just look at it in the Lister).

Also, I'm noticing that I have several other files in my wincmd directory that have fairly recent file dates... Wincmd.gid and default.br1... and I'm wondering whether these preserve any data I need.

*.br1 files are simply bitmaps that contain the icons of the files in the button bar next to each other, so that TC doesn't have extract icons from all the files everytime. It simply draws this .br1 bitmap. It gets automatically recreated when TC doesn't find it, so you can safely ignore it.
The .gid file is a file which is automatically created by Windows when you access TC's help. Just like an .fts file, which is also created by Windows when you search TC's help.

I'm sure these file names have changed since the product has been renamed, though, and possibly the software itself has changed enough that these files may not convert over easily.

No, not at all, TC is pretty much fully backwards compatible.

I'm concerned that there might be references to the old program default directory in, say, the ini file, which might confuse things

Yes, that's the only thing you should be concerned about.

So, step by step instructions:
Backup the wincmd.ini, wcx_ftp.ini, *.bar (except no.bar) and wincmd.key files to a dir.
Edit the wincmd.ini and replace "c:\wincmd" with the path you intend to install TC to (eg "c:\program files\totalcmd").
Install TC on the new machine and use Explorer to copy the ini files to the Windows dir and the other files to TC's dir.
Start TC and check if everything works fine.

HTH
Roman

[Robert_Charlton]

Roman - Thanks very much for your very clear and prompt reply. The changeover is sometime next week. If I'm not back right away, you'll know it went well.

...and use Explorer to copy the ini files to the Windows dir and the other files to TC's dir.

Ahh, there's the rub. I've gotten so spoiled by TC that I haven't used Explorer in a long while. Will have to brush up on it.

Incidentally, can you point me to any threads or resources that might serve as a quick guide to any changes I'll see between v4.53 and 6.03? I assume the core operations are pretty much the same.

Thanks again.

[Sticky]

Incidentally, can you point me to any threads or resources that might serve as a quick guide to any changes I'll see between v4.53 and 6.03? I assume the core operations are pretty much the same.

Most core operations will be indentical, though a few of their hotkeys may have changed (the multi-renamer tool comes to mind). Upon installing the latest version, you might look at the latest hotkeys list (in the help file) to make sure you're on the same page.
The what's new and feature list pages will describe a few of the changes, but for the most part you'll have to either look around the forum, or just play with the app. It might be a good idea to install it on your current machine (after you've backed-up all the files) just to get a feel for it before the move. Also, I would encourage you to poke around the forum a bit. More often than not, the tips and tricks I read about here become things I use everyday. Good luck!

EDIT: I forgot to mention history.txt, which will be included with the latest installation. This lists all changes since Version 3.00, though it's a bit of a read.

[Robert_Charlton]

Thanks. Nice to see such an active support community here. I guess the program inspires it.

[Hacker]

You're welcome.

BTW: TC 6.50 will be out in mid-December with even more exciting features, so don't forget to upgrade!

Good luck
Roman