Softpanorama
(slightly skeptical) Open Source Software Educational Society

May the source be with you, but remember the KISS principle ;-)

Google   


Orthodox File Managers

Home of OFM standards

2008 is the 22st year of OFM epoch


(the logo was awarded
on Jul 18, 2000)

News Recommended Links Comparison Table OFM Book OFM Standards Papers Ten Commandments
NCD clones Orthodox Editors GUI vs. command line TCL file managers Python OFMs Java OFMS Web OFMs
FAR Total Commander Midnight Commander Krusader Servant Salamander Classic Unix Tools Viewers and add-ons
Screen Macro
recorders
WebDriveFTP Quotes History Humor Etc
             

Orthodoxy: The things that are considered correct and proper beliefs. This word comes from the Greek words 'orthos' meaning straight or right and 'doxa' meaning belief.

TheoGlossary - A Glossary of Words and Theological Terms by Dr. Terry E. Shoup

Orthodoxy: Any practice or teaching that falls within the established framework of the conventions, beliefs and doctrines of a given religious tradition.

Glossary of Important Terms

This page is devoted to the Orthodox File Managers (OFMs) that are also known as "Commanders". They are remote descendants of  Norton Commander written by John Socha and first released in 1986. Members of this family of file managers with the most prominent example of FAR on Windows and Mc in Unix use simple yet very powerful command line windows managers with file management capabilities that use three windows: two symmetrical windows with listings of files in two possibly separate directories called panels and one "terminal style" windows that initially is minimized to one (bottom) line.   Modern OFM interface is a "screen" inspired generalization of Norton Commander (NC) interface and preserved "look and  feel" of the original program with its ability to shrink and manipulate visibility of left and right panel windows as well as expand command window (preferably gradually but at least to half-screen and full-screen).   Paradoxically leading Windows implementation (FAR) has richer interface with shell then Unix version (partially because of design flaws in Midnight commander where shell interface is implemented as a hack). There are also many GUI version that implement mainly file handling capabilities but not "visual shell" capabilities. the most prominent version is Total commander which in 2007 became fifteen years old implementation.  As advanced usage of OFM requires knowledge of shell, they became the tool of choice for system administrators, especially in xUSSR region, Eastern Europe, Germany and Scandinavian countries. Those regions were place of birth on most impressive OFM implementations such as Far, Total Commander, deco, Volkov Commander, Dos Navigator, Servant Salamander and many others.

I introduced the term "Orthodox File Managers" in 1996 with the first edition of my online book and now it seems to be more or less standard term for this category of file managers.  Sometime this type of managers is called 2-pane or two panel managers but this is a superficial term as it does not reflects the importance of command line in the interface, the key distinguishing feature of this type of managers as well as the level of integration with the underling shell (via extension menu, user menu and, especially in the access to the terminal window in Unix screen style).  It also hides close analogies of OFMs with such programs as XEDIT, vi and screen. All those programs has nothing to do with two panel concept despite the fact that they are pretty close to each other in key ideas and attract similar type of power users -- first of all system administrators.

There are numerous advantages of  Orthodox File Manager (OFM) paradigm, which refines the functionality of  the original Norton Commander for DOS and incorporates more then 20 years of development by many talented programmers including John Socha, Vsevolod Volkov, Eugene Roshal (of RAR fame). The first and the main advantage is portability (implementations exist for any major OS including Windows CE) and the availability of public standards.

The first and the main advantage is portability and the availability of public standard

All OFMs have a Spartan interface with the main window which is divided into three sub-windows. Two of them are called "panels" that are identical in structure (but can have different sizes and/or be hidden), and are positioned side by side at the top of the screen. The third  screen-wide window contains an instance of the shell and usually is minimized to one line but can be expanded either gradually (like in FAR) and/or is large increments (half screen and full screen in classic Norton Commander implementation). You should view this command like window as a separate shell session or, if you wish, telnet session to localhost. In case panels are hidden (with hotkey Ctrl-O ) it should provide full functionality of the OS shell window including history of commends, command completion and other niceties. In essence OFMs is a command line windows manager (similar to screen) with functions of two upper windows (panels) largely fixed. But the important feature of OFMs is that panels are implicitly  connected  to the operations performed in command window in several ways:

Surprisingly, attempts to enhance this simple, Spartan interface largely failed.  There were attempts to create the OFM manager with four panels. There were attempts to use tree view as the right panel (similar to Windows Explorer) and most OFM has the ability to replace left panel with tree view. But I personally and many advanced users that I know never learned to use this productively and prefer classic symmetrical panel view with two directories.  Strangely enough this two symmetrical panel with two directories remain the most productive for a very wide spectrum of real life file operations. When I need tree view for quick navigation I usually use separate view available vie Alt-F10 (find folder).   Probably there are some structures in brain that provide higher productivity with the symmetrical two panels  interface vs. various often more sophisticated asymmetrical variants.  Moreover after you achieve proficiency with it, it's rather difficult to switch to any other: all of them look inferior even if in reality they are more expressive  for some operations (like the Windows File Explorer asymmetric interface with tree on the left side or XTree interface provides very good capabilities of coping/moving files from left panel to the arbitrary place in the directory tree). There is some kind of  implicit "lock in": after several years of usage you start thinking about file movements and directories restructurings in terms of OFM operations.

Another advantage of OFM is that this is the only type of file manager that is standardized and the skills are transferable from command like to GUI and back as well as from one platform to another (for example Windows to Unix  -- this is an excellent way to dampen shock of the Unix command line for Windows users who want also use or even migrate to Unix).

Another advantage of OFM is that this is the only type of file manager that is standardized and the skills are transferable from command like to GUI and back as well as from one platform to another (for example Windows to Unix  -- this is an excellent way to dampen shock of the Unix command line for Windows users who want also use or even migrate to Unix)

OFMs are not for dummies. You need to know the shell of the OS you are using fully benefit from its capabilities. That's why they are extremely popular among administrators, especially in Eastern Europe and xUSSR area. 

The author argues that this simple classic interface offers the most efficient way to perform complex file operations, and both users and software developers deserve some help in the form of the standard and some kind of commentary about "the state of the art" of this type of file managers. That's why I spend considerable time writing my online book The Orthodox File Manager(OFM) Paradigm that introduced two level of standards (OFM1999 - minimal OFM requirements  and Dr Nikolai Bezroukov. The Orthodox File Manager(OFM) Paradigm. Ch. 9 The OFM2004  provide both commentary and overview of major implementations. This is a volunteer effort and some parts are outdated.  Still this is the only ebook on the subject and as such it can help system administrators more consciously choose the implementation they need and polish the methods of work with OFM.

In this ebook I tried to distill several possible reasons for this surprisingly high productivity of OFM users, the productivity that despite of the age of the interface (more then 20 years) and its Spartan character remains unmatched. Please read at least Ch.1 of the OFM book, the chapter that introduces the concept. 

But even if you do not want to read it, selects and enjoy any OFM you like! I am using this class of filemanagers since 1987 (NC 2.0) and still learn new things each year, things that help to increase my productivity. Despite interface simplicity latest OFMs are very powerful and flexible programs, that have rather steep learning curve and you will be better off learning incrementally,  starting with simple file operations and gradually moving toward full power that bring customarization and availability of user many, extensions menu and several other features of OFM.

I also have found OFMs to be indispensable productivity tool for webmasters and despite my interest and professional exposure to other Windows and Unix filemanagers I am still convinced that in the hands of professional, productivity-wise, OFMs  have a huge edge. BTW I never managed to fully switched to GUI based OFMs, and still use mc in Unix and FAR in Windows environments although recently I spent considerable time using Total Commander.   That's because command line OFMs should be viewed not only as filemanagers but as a new ingenious graphical interface to shell, interface that makes standard Unix-style typing command on the terminal irrevocably backward. Professional Unix administrator fully versed in OFM usually outperform Unix administrator limited to "pure" commend line by a factor of two in not more.  It's actually a pity to see how those poor people spend valuable time typing innumerous ls commands ;-)

And that brings us to an important point. While invented as a file manager in reality (and especially in Unix enviroenmnt) OFM should be viewed as new generation of shell interface (visual shell) and as such they should be closely integrated with shell. Unfortunately this point was missed by most Unix developers and capabilities of typical Unix implementation in this respect are rather primitive. In a way you should think about Unix OFM implementation as a fork of screen with specially predefined top windows split vertically (I know screen cannot split windows vertically but let's assume that this is just an implementation limitation).  This ides of "OFM as a visual shell for Unix" is the main point that I advocate in my ebook especially in chapter 4 devoted to Unix OFMs. That's why despite their origin in Windows OFMs proved to be extremely natural to Linux/Unix environment. IMHO a Linux/Unix sysadmin with good OFM skills can be probably twice more productive then any super-skilled UNIX guru that use just plain vanilla command line ;-) Actually good knowledge of OFMs is a trademark of best Unix administrators from Eastern Europe.

But while Europe (especially xUSSR region, Eastern Europe and Germany) became the new home of Captain Norton, the initial versions of NC were written by a talented American programmer John Socha. Like with any brilliant idea it did not take long to implement and develop it to a mature condition: all the major work concentrates in just two years 1985-1987. At this time John Socha was the first director of research and development for now defunct small software company: Peter Norton Computing. Peter Norton who wrote the initial version of Norton Utilities, but AFAIK was not involved in writing Norton Commander was one of the pioneer entrepreneurs in PC software development; now he is known mainly due to his role as a photo model on the boxes of Norton Utilities and other Symantec products belonging to a "Norton line" ;-). 

The first version of Norton Commander was released in 1986 and it instantly became the dominant file manager for DOS. In 1987-1991 more then a million copies were sold.  In Eastern Europe Norton commander became a synonym of DOS interface and many users did not even understand that this is an add-on program. 

In 1990 Peter Norton sold his company to Symantec to pursue his interests outside programming. John Socha left the company after the merger and created his own company, which was later acquired by Asymetrix. He continued cooperation with the Norton division of Symantec and wrote for them several good computer books including classic introductory assembler textbook Peter Norton's Assembly Language Book for the IBM PC .

Symantec first displayed some lukewarm support for this cash cow, but with the introduction of Windows killed it (as well as some other brilliant DOS product it acquired -- XtreeGold). Later they understood the mistake they made and in 1997 there was a reincarnation attempt: Norton Commander for Windows 1.0 was reintroduced in the Symantec product line. But talent was already gone and it  was "too little, too late" and after version 2.0 it died again (still as of January 2003 you can buy Norton Commander for Windows 2.0 in Europe, especially in Eastern Europe).  Not that I advice you to do that :-)

I would repeat it again that OFM can increase the productivity of sysadmins several times, especially for performing complex operation on Unix-style hierarchical file systems.  For some  unknown reasons no other file manager can compete with OFM in performing complex copying or moving of files on the directory tree. I several time managed to win a bottle of wine competing against Unix administrators who used only command line, and believe me as typists they were much better them me. The only other tools that I know, that have a similar semi-religious status with its adherents (but in a different area) are Xedit and vi editor (see my  Orthodox Editors for details).  That's why I consider OFMs to be a must (along with orthodox editors) for any advanced user, sysadmin or webmaster (both Windows and Unix).  As I wrote in my book:

One of the most distinctive advantages of OFMs is that the productivity of the power users is really amazing, especially in the command-line environment. To the uninitiated it often looks like a magic -- the speed with which an advanced user can perform complex file operations.  It looks much like playing piano. Advanced user probably have "motor maps" for typical operations that are executed on subconscious level much like a good piano player can instantly recognized specific accords in music notation.

OFMs can be found on all major and minor operating systems including  all flavors of UNIX, OS/2,  all existing versions of DOS, Windows 3.1, 9x,  NT and even PalmOS and Personal PC. Actually OFMs probably represent the most portable family of filemanagers in existence (Xtree is also a very good filemanager available on several platforms, but not that many, Windows Explorer is an average filemanager that was also widely ported to almost any OS in existence because of the influence of Microsoft Windows).

 The first and the main advantage of OFMs is simplicity and stability.
Attempts to enhance this simple, Spartan interface largely failed.  Also after the first three years of using OFM most file operations can be performed so fast that usefulness of further improvements  might be marginal ;-)

Ten OFM Commandments ;-)

"I have found jesus. He came to me in the form of muCommander."

-- A happy user

 

There is a large variety among OFM implementations. Moreover different OFMs are good for different situations and tasks -- there is no and never be the best OFM for all situations and environments. But they all share same distinctive interface framework and the following basic features:

  1. Spartan interface: two symmetrical panels that display files in two directories and a minimized telnet-style terminal ( command line ) at the bottom of the screen.  One panel is current (active) and second is passive; they are switchable with the Tab key and identical in functionality. For all "binary" file operations (copy, move, symbolic link, etc) the target by default is the directory of the opposite (passive) panel.  Unique (incompatible with usual Windows assignments) keystrokes assigned to each function. Traditional OFM function key assignments are: F1 - help, F2- user menu, F3 file view, F4 - file edit, F5 - file copy, F6 - file move/tree move, F7 - make a directory,  F8 - file delete, F9 - top menu, F10 - exit.  Often these function key assignments are depicted on the bottom line as buttons clickable by the mouse. Although functional key assignments are traditionally preserved in OFM implementations, they are not a part of OFM paradigm. If remapping of the keys is implemented (for example in a way, similar to vim implementation), than any other combinations (including more Windows like) can be used. Again only semantics of the operations is fixed and should be implemented "as is", although "old finger habits die hard" ;-). This the ability to perform most functions without mouse is especially useful on the laptops and now palmtops as well as  for troubleshooting; mouse serves as a useful supplementary, not primary input device in OFMs.
     
  2. Seamless integration with the shell making OFMs a synonym to "Visual shell.". Command line windows can be extended either gradually (expanding/shrinking line by line) or at least two steps (half screen/full screen)  providing  native shell window like in telnet. Any command line OFM should provide perfect emulation of telnet terminal capabilities for supported sizes of command line window with the ability to view more data by expanding the window (for example from one line to full size of from half-screen to full screen). In all cases where more then one line window is present the user should be able to view (and possibly scroll) the results of execution of commands entered on the command line like in regular telnet client (in this case telnet to localhost).  This command window capability links OFMs with famous Unix program screen and derivative Spartan text-mode windows managers like Ion (with fully documented configuration and scripting interface on top of the lightweight Lua extension language), Ratpoison twin, evilwm,  and several other that I forgot to mention.
     
  3. The ability to extend file manager functionality with custom scripts. Both command line and GUI-based OFMs should have the ability to create a set of shell scripts (accessible using F2) and invoke them by assigning each of them special hotkey. Scripts should permit macro variables that reflect the current status of both panels (path to active/passive panel, the current file on active/passive panel, selected files , if any, etc).  This simple, ingenious, and very functional  extensibility with custom shell scripts make OFM very attractive for system administrators. They are useful for regular users. Actually in late 80th, early 90th of the last century in the former USSR region many DOS users never suspected that any other DOS interface exists: this was the standard and only DOS interface they knew. 
     
  4. The availability of scripts associated with file extensions via special file extension menu and evoked by pressing Enter on the file with the particular extension on a panel.  This is another way to extend file manager functionality and file extension associations were pioneered by Norton Commander.  Special customizable extension files that permit context-dependent invocation of scripts and programs on a  file click (execute), F3(view) and in F4(edit). Customizable file extension menu should provides automatic passing of various panel-based parameters to shell scripts.
     
  5. "History for everything" approach to editable text. All OFMs provide the history of commands. Modern OFMs add to this the history of directories visited, files edited, selections, etc. Some advanced OFMs like Midnight Commander add to this the idea of "file/text completion for everything".
     
  6. Integration of application protocols into file manager framework via virtual file systems(VFS). Most popular are  ftp client VFS and archive VFS. Less popular, but still very important are Search VFS and "flat tree" VFS. They are all based on the same concept of a virtual file system:
    1. FTP virtual file system  -- historically important capability which provides that capability of working with ftp session like with the local filesystems. Perfect for complex ftp operations and as powerful as most standalone GUI FTP clients. Now with the availability of FTP virtual filesystems and ssh is less useful.
    2. Archive VFS: Extremely polished VFS-based  interface with archives (gzip, zip, rar, arj) and, in case of Unix OFMs,  installation packages (RPM).   It was historically first VFS implemented in OFMs and dates back to NC3 extensions.
    3. Search VFS: This VFS is usually implemented via "panelize command" and permit viewing on a panel as in virtual directory all the files and directories that were found in a particular search operation.
    4. XTree or "Flat tree" VFS.  Most modern OFMs provide the possibility of viewing all files in a branch of the tree in a "flat" representation (often bound to Ctrl-B). This representation is extremely important for working with files dispersed into several directories as is often the case in most application installations.
       
  7. Powerful built-in file viewing and integrated file editing capabilities. Most OFMs have an integrated viewer and best have an integrated editor. The latter has access to information on the panels (current file, path to the active/passive panel, etc). They usually support syntax coloring and regular expressions search (like in MC and FAR). There should also be a possibility of "sequential edit" or viewing of selected files. In this case closing the file invoke editor or viewer on the nest selected file. The editor should have an information line at the top and key shortcuts buttons at the bottom (similar to the panel view help buttons); the code of the letter under the cursor should be visible both in ASCII and hex at the editor information line. The viewer should has ASCII and hex modes of viewing files. It should work both in full screen mode and panel move (for quick view browsing). There should be a possibility of switching from the viewer to the editor and back. Both editor and viewer permit working a panel (left of write), pasting information to from the editor to panel (for example, change directory to selected, paste selected into command line, etc) and getting information from panel (names of selected files, etc) and selected parts of the command execution screen back into the editor. 
     
  8. Powerful, Unix grep-style, search capabilities with the ability to view results in browsable panel.  There should be abilities to find an arbitrary file(s) in the filesystem with capabilities equal of better then Unix  grep utility but with more friendly interface. The results of the search should be displayed iether in one of the panels (search VFS implementation) or in a special scrollable (in both directions) panel and at least several operations should be available from this panel:
  9. Rich capabilities of working with directory trees:  In OFMs there are two distinct tree panels:
  10.  There should be some kind of client-server connectivity between two instances of OFMs (preferably SSL based TCP/IP connection, or unencrypted TCP/IP connection like in MC, or connection via serial cable like in NC3-NC5, or parallel cable like in Total Commander).  Generally one instance OFM can be a server and second can be a slave and all commands and panels should be seamlessly replicated across the link.

Again those are Commandments and like in everyday life not everybody is observing them ;-). Still three key features stands out and are the key components of the OFM religion:

Paradoxically, but for complex file operations using mouse is not much superior to keyboard-based interface and combined interface is superior of any.  There are several reasons for that:

Please note that OFM usage of the command line interface is different from the typical shell interface and thus our "advantages of the keyboard" discussion is not equal to the classic "GUI vs. Command Line" debate. It's true that each interface has specific advantages and disadvantages:

OFM (especially in GUI-based incarnation) actually represent a hybrid model: commands entered from the keyboard changes the panels and provide instant visual clues that are a trademark of pure GUI interface. This hybrid model has unique capabilities and somewhat resembles comics.  You may try Scott McCloud's book Understanding Comics and Reinventing Comics for more information, as this sequel touches some interesting topics.  Personally, I find comics, when done well, to be of the few examples when a picture is really worth a thousand words, and a couple of words are worth a thousand of pictures. IMHO this is also the case with OFMs ;-).

I would like to stress that OFMs  are an essential (and underutilized ) tool for system administrators, especially UNIX system administrators. Midnight Commander (MC)  now seems to be the leading implementation for open source operating systems for Unix. There is also a portable Unix GUI based (X-based) version of OFM called Northern Captain and an excellent KDE-based Krusader.  But generally for X-windows the optimal implementation should be based on a scripting language and some OFM managers based on  TCL already are available. Scripting language based OFMs are much more powerful and flexible than the traditional complied implementations like MC. Although TCL seems to dominate this field, other scripting languages like Perl, REXX and Python, Jython are (with some reservations) also suitable as both an OFM macro language and implementation language. Recently Java written OFMs make some inroads into the territory. They are more portable then compiled implementations. See for example muCommander.

The author strongly believes that OFMs should become a standard tool for Unix system administrators and WEB masters, but penetration of OFMs in this area is very slow...

For the users with DOS/Windows that also need to use Unix they provide the most painless way to master Unix command line and can save them from a lot of frustration during first several weeks of struggling with a typical command like Unix arcana ;-). Now its less pronounced with the availability of  GUI environments like KDE and Gnome, but still a lot of work is done via telnet.

We can distinguish the following three important classes of OFM:

Good luck ! A challenge for human-computer interface is to support creativity and that's what distinguishes OFM from other types of file managers.  Please note that OFMs have a rather steep learning curve and don't be discouraged by initial difficulties. Your persistence will pay you nicely... 

Dr. Nikolai Bezroukov


Notes:
  • Those pages are written by people for whom English is not a native language. Some amount of grammar and spelling errors should be expected.
  • This is a Spartan WHYFF (We Help You For Free) site. It cannot replace the best teachers and the best books.
  • The site contain some obsolete pages as it develops like a living tree... Some links on older pages are broken. Please try to use Google, Open directory, etc. to find a replacement link (see HOWTO search the WEB for details). We would appreciate if you can mail us a correct link.

Search Amazon by keywords:

Google   
Open directory

Research Index

 

Comparison Table (from Ch.2 of the OFM book)

OFM name
(and link to a book chapter)
NC FC DN FAR Total Commander Nico NCW MC XNC Drall
OFM Type Classic Classic Classic Classic GUI GUI   GUI Classic GUI Web
Status of development
(active if the the version is less then six month old, stalled if a year, frozen if more the a year)
Aban-
doned
Stalled ndn
and
dnosp
Stalled Active Active Abandoned Active Active Stalled
Last stable version 5.0 2.30 beta
(as of Nov, 2003)
See dnosp

and
ndn
  
1.70
(beta 5 as of May 15, 2003)
7.0
(Jun, 2007)
5.61
( as of Jun May, 2007)
2.0 4.6.1
(Jun2007)
5.0.4  (as of Jun, 2007) 1.16.0.0
(as of  Feb 2005)
OS supported DOS
 OS/2, NT,
Win 9x

DOS, Win9x, WinNT,
Linux (ndn)

 Win9x, NT  Win9x, NT, XP
(there is an independent attempt to clone TC for Unix)
Win9x, NT Win95/NT Unix
 (versions for Win95, NT,OS/2 exist but are not that  impressive)
Unix Multi-platform
(Perl)
Size of compressed distribution 1.4M   0.2M ~1M 1M   1.5M 0.83    2M 1.56 M 1M 29K
Software type and download link (if different from the development Commercial Shareware Open source:
2 major versions:
dnosp
and
ndn
Shareware Shareware Shareware Commercial GNU
License
GNU License GNU License
Price $90 ? $25 $0 $25 $30 $20
Ł21/€ 35
$0 $0 $0

P.S: In order to save the bandwidth for humans (as opposed to robots ;-), Old News and Recommended Links were converted into separate pages.

 

Fifteen year jubilee of Total Commander !
Please visit www.ghisler.com
 and try TC. You may like what you see so much that you might register the same day !!!
 

Old News ;-)


"The future is here, it's just not evenly distributed."
William Gibson

2016 2015 2014 2013 2012 2011 2010 2009 2008 2007
2006 2005 2004 2003 2002 2001 2000 1999 1998 Archives

[Feb 29, 2008] Project details for Key Scripter

freshmeat.net

About:
Key Scripter listens to key press/release events from a keyboard device and sends fake key events to an X display. It supports gaming keypads such as the Nostromo SpeedPad and allows the creation and usage of complicated key scripts for games and other applications.

Release focus: Major feature enhancements

Changes:
This release also supports Windows. A Win32 binary has been added to the download packages. To compile the source files on Windows, the latest release of MinGW is required. Additionally, this release fixes a few memory allocation bugs, adds support for wildcard binds, and provides improvements to debug messages. The example configuration file has been extended with extra features.

Author:
Andrei Romanov [contact developer]

[Feb 10, 2008] FreeCommander - freeware file manager

FreeCommander is an easy-to-use alternative to the standard windows file manager. The program helps you with daily work in Windows. Here you can find all the necessary functions to manage your data stock. You can take FreeCommander anywhere - just copy the installation directory on a CD, USB-Stick or even a floppy disk - and you can even work with this program on a foreign computer.

Main features in FreeCommander:

[Feb 09, 2008]  wxCommander

freshmeat.net Project details for Ultimate Commander by László Monda

Written in C#

Ultimate Commander strives to be an incredibly powerful orthodox file manager developed with a special focus on usability, extensibility, portability, and power users.

[Feb 08, 2008] sharpfile - Google Code

Written in C#
As of right now, this is an alpha-quality file manager.

Current features include: drag and drop, right-click context menu, rename, automatically refreshing file view, ability to calculate directory size, tab file view, dual or mdi parent choice, filter file view on-the-fly, file icons (including svn icons), multi-threaded drive and file retrieval.

Features in the works: plug-in architecture for different file retrieval (for example, ftp/ssh) or different ways to show the file information (for example, audio files might show different information), thumbnail preview pane, show information about copy/move operations with ability to cancel, specification of columns for file information, Vista-compatibility.

Club Dr-DOS Wiki Main - File Managers

Doszip Commander (GPL, open source)

Project page: sf.net/projects/doszip/

By Hjort Nidudsson . A new Norton Commander clone … test it :-) It is very small and fast. Written mostly in 1996…1997 . Development has recently (2007) stopped, but as last fix the author updated it to support LFN ! Has built-in support for unZIPping - no PKUNZIP or similar needed, but supports only PKZIP 2.xx format incl. decryption. No ZIP creation, no support for other archive types.

It is the only one written in Borland C (use version 3.1, DOS 16-bit real mode).

[Jan 20, 2008] muCommander a cross-platform file manager

11/28/2007

muCommander 0.8.1 is out with a bunch of enhancements and bug fixes.
Get it now>>

New features:
- New bookmark:// filesystem, mapped onto the alt+B shortcut by default.

Improvements:
- Non-automatic sizing of columns is now working properly and preserved in the configuration.
- Columns order, sort and visibility are now preserved in the configuration.
- Editors and viewers are now centered on the current window rather than set to the upper-left corner of the screen.
- Shell encoding is now auto-detected by default, unless a specific encoding is set in the preferences.
- Simplified and extended the theme editor, with new 'selection outline' and 'alternate background' values. A new 'Striped' theme has been added to show these effects off.
- Added keyboard shortcuts for the items in the drive popup button.
- Windows: drives in the drive popup button now show extended names.
- Bzip2 read-access speed substantially improved.
- Improved icon representation of symbolic links.
- 'Delete' dialog now shows the list of file to be deleted (contributed by Alejandro Scandroli).
- New 'Find' functionality added to the text viewer and editor (contributed by Mariusz Jakubowski).
- command keyword substitution now applies to marked files as well as the current selection.
- Quit confirmation dialog now shows the number of open windows and asks for confirmation when the last window is closed.

Continue

Recommended Links

Top Links Sites Papers Xtree Add-ons WebDriveFTP Keymacros History Etc

Top links

Individual file manager sites

Recommended Papers

[Feb 05, 2004] simpleRECURSION 21st Century Nostalgia

Comments are more interesting the the article...
Also, I was surprised to find out that tomorrow, February 6, is NC5's ninth birthday. Weird. Could it be that many others like myself felt a point of anguish and somehow projected it into the collective unconscious? Or does NC5 have a psychic presence among us, in our hearts and minds? I don't know, but here's to you, old buddy!


I'm so glad to find someone else who is nostalgic for the days of Norton Commander. Back in those days, you were either an XTree Gold man or an NC man ... I was definitely an NC man through and through. My fingers would fly through the keystrokes with NC, and hapless customers would stand by open-mouthed :)

I was so disappointed when I discovered that NC for Windows was slow and ugly. After a careful search, I settled on Servant Salamander and I haven't looked back since. God bless you, Norton Commander!

PS. Yes, I too keep a copy of NC4 and NC5 on my hard disk for no reason other than nostalgia :)
 
Posted by Eric Pircher on June 20, 2006 05:39 AM
 

Norton Commander 5.5 for DOS with Long File Names really exists. Look at Wikipedia to proof that is true.
 

Posted by TurricaN on November 24, 2005 11:52 AM
 

 
Well, turns out you are right, TurricaN. I don't know if it was you, but the other day a guy e-mailed me a copy of NC 5.5 with LFN support.

I have to say that I was severely disappointed in this version. Unlike NC 5.0 and its predecessors, NC 5.5 needs to be installed and cannot be moved around with ease; it does not interact well with Windows, crashes a lot and is very slow.

P.S. TurricaN, just because someone says something on Wikipedia, it is not necessarily true.
 

Posted by Mike on November 26, 2005 12:50 PM
 

 
NC 5.5 inability to move and crashes exists only in NT line of WIndows, while in Windows 9x/ME this is not in the case. For Windows NT better use NC 2.01 for Windows.
 
Posted by TurricaN on November 28, 2005 04:50 AM
 

 
Win 9x/ME is utter crap, without argument; the first good, stable Windows version was Win2K, which is NT-based. I will have you know that NC 5.0 works perfectly on all NT-based systems, even though it does need tweaking to work with LFN.

Now, if I still wanted to use an orthodox file manager, I'd use FAR, by far (pun not intended) the superior NC clone, in all regards; NC for Windows is not a true OFM.

Posted by Mike on November 28, 2005 08:24 AM
 

 
If you want 100% NC-like archiver, use Commandline ACE - mentioned in one of links inside Wikipedia NC article.
Posted by ACEfan on February 13, 2006 07:27 AM
 

 
I would, Acefan; if I hadn't been lured by the power and compatibility (and increasing ubiquity) of WinRAR over the years. ;)
Posted by Mike on February 13, 2006 10:38 AM
 

 
I used to use NC 2.0-4.0, but then I discovered DOS Navigator.
Posted by Guti on February 28, 2006 08:07 AM

[May 25, 2001] Inside Solaris - Midnight Commander

A long time ago, on another computing platform, Peter Norton Computing released Norton Commander. This became my favorite file management program. As I wandered further and further into the UNIX realm, I found it hard to believe that a program like this wasn't available on UNIX. Finally, I came across Midnight Commander, as shown in Figure A. It offers more features than Norton Commander and, unlike Norton Commander, it runs on a variety of different computing platforms.

[Feb 7, 2000] Battle of the File Managers - the quest for the perfect file managers starts HERE!  Suggested by Nguyen Nam Duy <ndnguyen@wanadoo.fr>

An interesting review of several file managers...

File manager - Wikipedia
 

XTreePro as HTML-editor... : ion1.ionet.netbills


Xtree -- Another Classic File Manager

Xtree was another original file manager that created a strong following and almost cult-like devotion. Like OFMs Xtree users were able to achieve very high productivity in command line environment and it can became the style of thinking about filesystem, more merely a file manager. Like OFMs Xtree was re-implemented on most other operating systems, including Unix. See  UnixTree Homepage - XTree alike filemanager for Unix - Linux

Along with tree-like representation of the DOS filesystem Xtree was/is a pioneer that introduced two very important concepts that later and often incompletely found their way to other file managers including OFM:

As far as I can remember the original version was very small(34K ?) and did all this staff and more... It was really amazing masterpiece of programming.

Please take a look on the homepage of Jeff Johnson, the author of the original XTree and XTreeGold (Thank you Jeff, for your great work !)

Recommended Links:


Add-ons

UPX Homepage GPLed execution compressor

{*****} [Oct. 26, 1999]  WebDrive FTP Client Software by RiverFront Software -- a revolutionary FTP client that makes an autonomous FTP VFS implementation in OFMs redundant. This was probably the most important breakthrough for the 1999 and paradoxically it was produced by the company that has nothing to do with OFM development. Currently limited to Windows 9x/NT environment. Highly recommended. Shareware $39. Suggested by Eric Pement <epement@jpusa.org>.

WebDrive is a Windows 95/98 FTP software client  that allows you to map an Internet FTP site to a local drive utilizing the standard FTP protocol. This enables you to connect to an FTP site and perform familiar file operations like copy, xcopy, and directory functions with the Windows explorer,  a DOS box, or any other application like Microsoft Word, Excel, etc. WebDrive instantly FTP enables any application that reads or writes files by allowing the application to read files from or write files to the FTP site.

Until now, in order to upload or download files from an FTP site, you needed to run a client FTP utility that presented a user interface to manually select the files to transfer. The WebDrive FTP client makes the FTP site an extension of the file system which enables you to use any application to upload or download files to the FTP site transparently.  For more details, click here

Hiew 6.04  by Eugen Suslikov. Great external viewer for classic OFMs. Frequently used with VC...

Viewer for HTML and XML for DOS

George's Home Page -- textviewer with RTF reading capability

Polish Official VC site/Utilities -- indisputably the best collection of add-ons to DOS-based OFMs. Many will work in Linux's DOSEMU mode). I do not need to compile my own ;-). Please pay special attention to the following:


 


History

See also Softpanorama History links

Xtree History

XTree Fan Page More On XTree Links -- Page of our friends --  fans of Xtree file manager...  Pleas