freeCommander (dual pane filemanager, new version)

[Frank Delamarre]

freeCommander is an alternative to Windows Explorer. You can take
freeCommander anywhere - just copy the installation directory on a CD,
USB-Stick or even a floppy disk.

Main features:
Dual-panel technology
Optional tree view for each panel
Built in file viewer to view files in hex, binary, text or image
format
File viewer inside archives too
Built in archive handling: ZIP (read, write), CAB (read, write), RAR
(read)
Nested archive handling
Easy access to system folders, control panel, desktop and start menu
Copy, move, delete, rename files and folders
Wipe files
Create and verify MD5 checksums
File splitting
File properties and context menu
Calculation of folder size
Folder comparison / synchronization
Modification of file date and attributes
Folder / program favorites
File searching (inside archive too)
File filters for display
DOS command line
Multiple language support

More important changes in the version 2004.10 (21 Oct. 2004):
1. Folders synchronize - revised
2. New settings
- Use long / short filename
- Show grid
- Colors for folders / files with attributes: folder, read-only,
hidden, System
- Define Start folders
- Define source for freeCommander.ini
3. Wipe files
4. Create and verify MD5 checksums
5. Favorite tools - revised
6. 'Only selected files (Ctrl+S)' - are displayed with underlining in
the folder line
7. Wrap text in the file viewer (text view)
8. Keyboard shortcut for desktop snapshot active immediately after the
program start
9. Command line parameter
10. New keyboard shortcuts were defined
11. Several bugs were repaired

http://www.freecommander.com/index_en.htm
(1.3 Mb download)

Frank

 

[Roger Johansson]

freeCommander is an alternative to Windows Explorer.

It was updated two days ago.

Great news. It is the best dualpane freeware file manager, and it is
actively developed.

 

[Bill Day]

It was updated two days ago.

Great news. It is the best dualpane freeware file manager, and it is
actively developed.

better than the free version to PowerDesk? That's saying a lot,,,I may
have to try it...

 

[Roger Johansson]

better than the free version to PowerDesk?

I have Powerdesk too, but I never use it.

Powerdesk is not a dual pane file manager, and I am not used to working
with such a file manager.

Powerdesk has some kind of zip file treatment, but it doesn't work as it
does in classic file managers.

I cannot test the zip function in powerdesk because powerdesk complains
about missing dll files, it wants to be re-installed again.

Free Commander works without being installed and can be moved to another
drive. It runs happily from its own folder and nothing more.

Free Commander is real freeware, powerdesk has a splash screen when you
exit it.

 

[Antoine]

Free Commander works without being installed and can be moved to
another drive. It runs happily from its own folder and nothing
more.

The download file is actually a zip archive containing an executable
setup file. I first thought, this executable only extracted the
adequate files in a 'freecommander' folder and eventually added some
entries to the Windows startup menu but monitoring the installation
with Total Uninstall, I noticed that the installation also created
some entries in the registry, in the following branches :

HKEY_LOCAL_MACHINE/Software/Microsoft/Cryptography
HKEY_LOCAL_MACHINE/Software/Microsoft/Windows
HKEY_USERS/...
HKEY_CURRENT_USERS/...

So, may I ask you :

1/ if you use a specific version of free commander with no
installation

2/ if not, are you sure the free commander folder can
be copied 'roughly' from a computer to another one

3/ the free commander configuration window indicates that the .ini
file can be chosen ; by default, the .ini file is the one located in
the "installation" folder. Does it mean :
C:/Program files/free commander
or
C:/The_path_to_the_free_commander_folder_wherever_the_user_has_set_it

Thanks in advance.

 

[Roger Johansson]

The download file is actually a zip archive containing an executable
setup file. I first thought, this executable only extracted the
adequate files in a 'freecommander' folder and eventually added some
entries to the Windows startup menu but monitoring the installation
with Total Uninstall, I noticed that the installation also created
some entries in the registry, in the following branches :

HKEY_LOCAL_MACHINE/Software/Microsoft/Cryptography
HKEY_LOCAL_MACHINE/Software/Microsoft/Windows
HKEY_USERS/...
HKEY_CURRENT_USERS/...

So, may I ask you :

1/ if you use a specific version of free commander with no
installation

No, I used the only version available.

2/ if not, are you sure the free commander folder can
be copied 'roughly' from a computer to another one

I didn't try moving it to another computer, just another folder on
another drive, and it seems to work without problems from its new
location.

3/ the free commander configuration window indicates that the .ini
file can be chosen ; by default, the .ini file is the one located in
the "installation" folder. Does it mean :
C:/Program files/free commander
or
C:/The_path_to_the_free_commander_folder_wherever_the_user_has_set_it

I did not look into the ini file location choices at all, I just moved
the Free Commander folder to another location to see if the program
worked after being moved.

 

[Antoine]

I didn't try moving it to another computer, just another folder on
another drive, and it seems to work without problems from its new
location.

I installed, copied/paster the freecommander folder in a
given_folder then uninstalled the software and the executable in
the given_folder still seems to work.

I did not look into the ini file location choices at all, I just
moved the Free Commander folder to another location to see if the
program worked after being moved.

If you want to have a look it's in : Extras > Settings > Start
program.

I noticed what appears to me as glitches :

- when the tree view is activated, the folder icons of the left
window of a given pane have a non-transparent (dark grey) background

- whenever freecommander is launched it seems to look for a floppy :
there is no error message but I would like to avoid this floppy check.

Do you experience the same behaviour and have you found a way to
modify it ?

Again many thanks Roger.

 

[Roger Johansson]

I installed, copied/paster the freecommander folder in a
given_folder then uninstalled the software and the executable in
the given_folder still seems to work.

Good, then we know that it works without being installed at all.

If you want to have a look it's in : Extras > Settings > Start
program.

The default is good enough for me, the ini file in the same folder as the
program.

I noticed what appears to me as glitches :

- when the tree view is activated, the folder icons of the left
window of a given pane have a non-transparent (dark grey) background

- whenever freecommander is launched it seems to look for a floppy :
there is no error message but I would like to avoid this floppy check.

Do you experience the same behaviour and have you found a way to
modify it ?

If you close the program when one of the panes is showing the floppy
drive it will try to access it again when you start the program the next
time. The solution is, of course, to avoid closing the program when it is
set to show the floppy drive.

Try to set all panes to hard disks and then close the program.
Does it still want a floppy disk when you start it again?

 

[Antoine]

Good, then we know that it works without being installed at all.

I would be more careful : it _seems_ to work.

If you close the program when one of the panes is showing the
floppy drive it will try to access it again when you start the
program the next time. The solution is, of course, to avoid
closing the program when it is set to show the floppy drive.

Try to set all panes to hard disks and then close the program.
Does it still want a floppy disk when you start it again?

I have just done the test, both panes being set up to display C:.
At next start up, free commander still scans the floppy drive.
I guess you experience the same behaviour, don't you ?

Regards.

 

[Roger Johansson]

I have just done the test, both panes being set up to display C:.
At next start up, free commander still scans the floppy drive.
I guess you experience the same behaviour, don't you ?

No, Free Commander has not been interested in my floppy drive at all, so
I have no idea what causes this behaviour for you.

Hmmm..

In the settings, first page, there are settings for "Auto Refresh" for
fixed, removable and remote drives.

I guess that you could remove the marking for refreshing removable
drives to get rid of this problem. Maybe I don't see the problem because
I never used FC for a floppy, so there is nothing to refresh.

This setting should have been off by default, for removable and remote
drives.

 

[Antoine]

No, Free Commander has not been interested in my floppy drive at
all, so I have no idea what causes this behaviour for you.

Hmmm..

In the settings, first page, there are settings for "Auto Refresh"
for fixed, removable and remote drives.

I guess that you could remove the marking for refreshing removable
drives to get rid of this problem. Maybe I don't see the problem
because I never used FC for a floppy, so there is nothing to
refresh.

I unchecked all the 3 boxes for fixed, removable and remote drives,
closed free commander, launched it again and : FC still scans my
floppy drive.

In case I had done something wrong without noticing it, I also
checked the .ini file in order to be sure that there was no path
defined (eg shortcuts or favorites) invoking the floppy drive.

I have just sent an email to FC's author reporting those facts.
Thanks anyway for having tried to help, Roger.

Regards.

 

[Bjorn Simonsen]

In the settings, first page, there are settings for "Auto Refresh" for
fixed, removable and remote drives.

My guess is that refresh only works the for the current panes.

On the settings page, under view - there is a setting called
"show removable drives only with disk" which I guess is for the drive
bar. The OP should try check that one, or remove if checked.

Else, try search the ini file the program directory for any mention of
A:, the edit/remove it.

All the best,
Bjorn Simonsen

 

[Bill Day]

I have Powerdesk too, but I never use it.

Powerdesk is not a dual pane file manager, and I am not used to working
with such a file manager.

PowerDesk would be surprised to find it is not dual-pane! It is
actually 4 pane, (dual pane with secondary pane for files and primary
pane for tree listing) either horizontal OR vertical, with single pane
as an option. I have never used it except as dual pane.

Powerdesk has some kind of zip file treatment, but it doesn't work as it
does in classic file managers.

I have used the zip function a lot, and it never compalined or needed
and .dlls here..*shrug* but I use stand-alone archivers more & more
now

I cannot test the zip function in powerdesk because powerdesk complains
about missing dll files, it wants to be re-installed again.

Free Commander works without being installed and can be moved to another
drive. It runs happily from its own folder and nothing more.

yes...I see that. It seems to be a fine, well done program, and I will
experiment with it...time will tell whether I need or use its features

Free Commander is real freeware, powerdesk has a splash screen when you
exit it.

yes, I know....they want to sell the PRO version, but that is the
teeniest 'nag' I know of in all freeware.

 

[Doc]

yes, I know....they want to sell the PRO version, but that is the
teeniest 'nag' I know of in all freeware.

And if that teeniest 'nag' still bugs ya, then open a hex editor, find the
delay setting and change it. Mines gone in the blink of an eye.

 

[Antoine]

My guess is that refresh only works the for the current panes.

On the settings page, under view - there is a setting called
"show removable drives only with disk" which I guess is for the
drive bar. The OP should try check that one, or remove if checked.

I tried this too and unchecked either "show removable drives only
with disk" alone either with "don't show floppy drives (A:,B" and
FC stills scans the floppy drive each time it is launched.

Else, try search the ini file the program directory for any
mention of A:, the edit/remove it.

That is what I tried too (see my other post)
Unfortunately, it didn't solve the 'problem'.

I finally tried when using the FC executable obtained with a proper
installation (without any copy/paste of its folder) ; the results,
with all the previous tests redone, are the same.

Thanks anyway for your help, Bjorn.

 

[Bjorn Simonsen]

That is what I tried too (see my other post)

Sorry missed it. Btw did you also remove A: from the history section?

Unfortunately, it didn't solve the 'problem'.

I finally tried when using the FC executable obtained with a proper
installation (without any copy/paste of its folder) ; the results,
with all the previous tests redone, are the same.

FWIW you could always try clear your Windows "Most Recently Used"
list, with fx MRU-Blaster from <http://www.javacoolsoftware.com/>.
I don't remember how much FreeCommander is tied into the shell, but
maybe it is getting the A: from there? You could thus also try, just
for testing, to open Window Explorer, make sure the A drive is not
current there, then exit it, and then run FC again and see. Also make
sure you do not have any other app (say AV client) running in the
background that tries to read A:..I'm thinking if so then maybe FC
will try to scan A: too, as it may see A: as "active" for this reason
perhaps.

All the best,
Bjorn Simonsen

 

[omega]

The download file is actually a zip archive containing an executable
setup file. I first thought, this executable only extracted the
adequate files in a 'freecommander' folder and eventually added some
entries to the Windows startup menu

I downloaded what should be the same file you did: fc_setup_200410.zip.
I used InnoUnp (Inno Setup Unpacker, http://innounp.sourceforge.net/)
to extract setup.exe, bypassing the installer. Then I monitored my first
run of it.

There were no regentries nor external files added to my environment.

If I'd run the installer on this guy, then I'd expect it would have not
added much. Common is to add an entry under [HKLM\...Uninstall] to make
an entry in the CPL Add/Remove section. Common too is an entry under
AppPaths, for user to launch the program by first name from the Run box.

So, on Free Commander's installer, I shouldn't think you'd be looking at
much of anything in the way of registry entries. And for external files,
most you should have was what you mentioned, the .lnk files dropped onto
the startmenu.

but monitoring the installation
with Total Uninstall, I noticed that the installation also created
some entries in the registry, in the following branches :

HKEY_LOCAL_MACHINE/Software/Microsoft/Cryptography
HKEY_LOCAL_MACHINE/Software/Microsoft/Windows
HKEY_USERS/...
HKEY_CURRENT_USERS/...

HKEY_CURRENT_USER is a subset of HKEY_USERS.

HKEY_USERS has all user profiles for that system. The HKEY_CURRENT_USER is
the currently logged-in user.

So set TUN to monitor only one or the other of those branches. To eliminate
the debris of redundancy.

HKLM/.../Cryptograpy/ -- well, I can't remember what that's about. Just I'd
propose it's Windows doing whatever it does normally, and does not concern
the behavior of a particular program.

HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/ .... Under this large area,
you're going to get two kinds of records. One is Windows' normal activities.
The other can be externally added subkeys under there. Such as the
..../Uninstall/ entry, and maybe that .../AppPaths thing, too.

You want to get TUN configured so that it does not tell you about normal
Windows activity in its installation reports. The standard approach for
this is to run TUN for a snapshot; do some of your normal Windows things;
then when it gives you a report from that, set the keys shown in that report
into its TUN's Ignore settings.

And, build up your Ignore settings in TUN over time. Stop and look over
its install reports periodically. Let your pattern-recognition kick in.
You'll eventually notice when it is showing certain keys that have regular
change, which is not caused by individual installers. At that point, add
to the Ignore list.

It's not only some standard Windows activity you want to put into TUN's
Ignore list. It's also about your usage - during your monitored installs -
of external programs that write to your registry. Such as your notepad, or
your file manager. Set their keys into TUN's ignore list.

So, may I ask you :

1/ if you use a specific version of free commander with no
installation

IMO, it should not have been distributed in installer form in the
first place. It runs totally green. And user has only to delete its
folder from drive for uninstall.

2/ if not, are you sure the free commander folder can
be copied 'roughly' from a computer to another one

It uses a local ini. Some programs have got mad at me when I was too lazy
to not do an S&R in their ini to change referenced files paths, prior to
moving them. But with Free Commander, I did a lazy move just now, and it
gave no complaint, coping easily.

3/ the free commander configuration window indicates that the .ini
file can be chosen ; by default, the .ini file is the one located in
the "installation" folder. Does it mean :
C:/Program files/free commander
or
C:/The_path_to_the_free_commander_folder_wherever_the_user_has_set_it

The second one: path_to_the_free_commander_folder.

 

[omega]

[...]

Unfortunately, it didn't solve the 'problem'.

FWIW you could always try clear your Windows "Most Recently Used"
list, with fx MRU-Blaster from <http://www.javacoolsoftware.com/>.

Sounds to me like a good plan.

I don't remember how much FreeCommander is tied into the shell, but

Regmon log: on the 1-2 seconds of launching FC, that's ~7,000 lines of
regseeks that FreeCommander is making. About average for a file mgr.

maybe it is getting the A: from there? You could thus also try, just
for testing, to open Window Explorer, make sure the A drive is not
current there, then exit it, and then run FC again and see. Also make
sure you do not have any other app (say AV client) running in the
background that tries to read A:..I'm thinking if so then maybe FC
will try to scan A: too, as it may see A: as "active" for this reason
perhaps.

Good advice, nothing to add. (The floppy A: seek problem has plagued
Windows users so very many times...)

 

[Antoine]

Sorry missed it. Btw did you also remove A: from the history
section?

Yes I checked the "Delete history entries on close" in the settings.
No change either.

FWIW you could always try clear your Windows "Most Recently Used"
list, with fx MRU-Blaster from <http://www.javacoolsoftware.com/>.

I just installed and ran MRU-Blaster : 245 MRU items deleted but
still no change regarding Free Commander.

I don't remember how much FreeCommander is tied into the shell,
but maybe it is getting the A: from there? You could thus also
try, just for testing, to open Window Explorer, make sure the A
drive is not current there, then exit it, and then run FC again
and see.

I had not thought of this one, thank you. But still no change.

Also make sure you do not have any other app (say AV
client) running in the background that tries to read A:..I'm
thinking if so then maybe FC will try to scan A: too, as it may
see A: as "active" for this reason perhaps.

I deactivated all security software that were running ie :
- Avast free version
- Spybot S&D resident
- My firewall (not freeware)

I simply don't understand what is happening. Thank you again Bjorn
for your suggestions.

 

[Bjorn Simonsen]

I simply don't understand what is happening. Thank you again Bjorn
for your suggestions.

Well then you might have found a bug - and a OS dependent one maybe,
since FC seems to work fine here w/ Win2k (and your OS is?). Same
behavior as you experience (tries to read floppy drive when loaded
even if floppy pane is not active/current) until I select "show
removable drives only with disk" under the options menu (view->disks),
then no problem.

All the best,
Bjorn Simonsen