64bit Windows doesn't support 16bit programs unless they are run in a VM.

If you are intending to use Norton Commander in DOSBox to adminster you're files then I would recommend against doing that. DOSBox is not for managing your host file system and is not supported in that configuration.

If you want a Norton Commander type of interface for Windows tho there are a ton of free file managers out there.

[MOVED]

i not will change any files i just will be able to find every thing without
endless typing in the darkness of dos.
maybe every body have this but i dont no how to use.

Use a frontend then.

For anyone who wants to use NC or VC:
Make a folder "srv" at DOSbox's root
Extract a downloaded Volkov/Norton commander into srv/(nc# or vc# - depends on what you use)
Add the following after [autoexec] and the comments in DOSbox.conf:

1Mount y srv
2y:
3nc5/nc.exe

(in the example, it's Norton Commander 5). After the nc5/nc.exe (or vc4/vc.com) line follows your current autoexec - if any)

I'm using the old norton commander in dosbox.
I just put it in a directory in the dosbos directory.
I just made a directory in my dosbox directory called c:\nc and put it there and added nc in the path in the autoexec section of the dosbox config file:
path=c:\;c:\nc
works perfect except I used to alter the colors with ansiplus ( a replacement for ansi) to make it look better but I can't load ansiplus in dosbox.

I have a hard time understanding why anyone running DOSBOX using mounted folders would want to use any DOS utils for file management. Anything you use in Windows would be superior to any DOS shells of that era, including Norton Commander. The only time this would be useful is using hard drive images in DOSBOX otherwise it's a complete and utter waste of time.

There are plenty of good Norton Commander clones for Windows. My personal preference is Speed Commander while others rave about Total Commander.

If you find the prices a bit steep and want something more reasonable, like say free you can use either Free Commander or NexusFile.

If you are a die-hard user of Norton Commander and want the full-blown experience then Far Manager is for you.

Seriously though stop wasting time running DOS utils in DOSBOX and get to some gaming, which is what DOSBOX was written for

uhh... the point is, if you have many games at your dosbox c:, and want to navigate between them with the mouse, a Commander is of great help.

I have NC_EXIT if anyone wants a copy. One way to save on mem. It was a freebee as far as I remember.

garrynichol wrote:

I have NC_EXIT if anyone wants a copy. One way to sa_nc_free_and_exit […]
Show full quote

I have NC_EXIT if anyone wants a copy. One way to sa_nc_free_and_exit

SYNOPSIS
#include <curses.h>

void _nc_freeall(void);
void _nc_free_and_exit(int);

DESCRIPTION
These functions are used to simplify analysis of memory leaks in the
ncurses library. They are normally not available; they must be config-
ured into the library at build time using the --disable-leaks option.
That compiles-in code that frees memory that normally would not be
freed.

Any implementation of curses must not free the memory associated with a
screen, since (even after calling endwin), it must be available for use
in the next call to refresh. There are also chunks of memory held for
performance reasons. That makes it hard to analyze curses applications
for memory leaks. To work around this, one can build a debugging ver-
sion of the ncurses library which frees those chunks which it can, and
provides these functions to free all of the memory allocated by the
ncurses library.

The _nc_free_and_exit function is the preferred one since some of the
memory which is freed may be required for the application to continue
running. Its parameter is the code to pass to the exit routine.

RETURN VALUE
These functions do not return a value.

PORTABILITY
These functions are not part of the XSI interface.

SEE ALSO
ncurses(3NCURSES).

memleaks(3NCURSES)
Man Pages Copyright Respective Owners. Site Copyright (C) 1994 - 2011 Hurricane Electric. All Rights Reserved.ve on mem. It was a freebee as far as I remember.

Huh? What does that have to do with this? other than nc which is sometimes used for norton commander but this is supposed to mean ncurses if I'm not mistaken. And dosbox only uses ncurses in debug compiles.
So I don't get it

garrynichol is a tech-orc. 🙁 Just wrap up (or delete) this thread.

Norton Commander wrote:

I have a hard time understanding why anyone running DOSBOX using mounted folders would want to use any DOS utils for file management. Anything you use in Windows would be superior to any DOS shells of that era, including Norton Commander. The only time this would be useful is using hard drive images in DOSBOX otherwise it's a complete and utter waste of time.

I use Windows Commander (I *REFUSE* to call it "Total" Commander) on a daily basis. But, I still like the look and feel of the good old NC for DOS, and use it as well on a daily basis; under Windows XP, as well as DOSBox.

Been an NC user since version 2.0, and could literally use it with my monitor turned off 🤣!

(...and have, many years ago, as a demonstration for a friend of mine <grin>)

Anyhow, an attached pic (back from my W98SE days, although, same thing for my current WXPee rig)... how do you think I have Windows Commander "skinned" <grin? 😀

Dominus wrote:

Huh? What does that have to do with this? other than nc which is sometimes used for norton commander but this is supposed to mean ncurses if I'm not mistaken. And dosbox only uses ncurses in debug compiles.
So I don't get it

nc_exit allows exiting nc to free up memory while using nc to run programs. It's a clean way of having nc exit itself from of it's command menu when picking a command to run other software.

I just thought it may come in handy if someone using nc doesn't already have it.

nc_exit allows exiting nc to free up memory

Then your description about it, which mentions curses, is plain rubbish.

Probably first google result on nc_exit and instead of reading just copy/paste... Another Dr. Googleberg 😉

BTW, NC_EXIT ships with all versions of NC, version 5.0 and higher (may have came with NC4.0, but I can't really remember). In other words, his discussion is worthless, as it COMES with NC.

...and the *REAL* readme (much more descriptive than that 'so-called' source code):

1NC_EXIT.COM          Program and documentation by Tony McNamara, Symantec
2
3Purpose:
4========
5    Unloads the Norton Commander without the use of a TSR program.
6    Optionally stuffs up to an 11 character command for processing after.
7
8Version 2.0, 1 February 91
9    Added command-line string parameter support.
10
11Syntax:
12=======
13    NC_EXIT
14    or
15    NC_EXIT <string> 
16    where <string> is up to 11 characters to be entered, as if typed at the
17    keyboard, after The Norton Commander has been exited.  
18
19Compatibility:
20==============
21    Unloads only the Norton Commander.  
22    Windows compatible.
23    Designed to be highly compatible.
24    May be rendered ineffective by some keyboard accelerators.
25
26Usage:
27======
28    Call from a batch file or a sequence of commands in a user menu.
29    No parameters are required.  If given, an ASCII string is used.
30    Due to the method, NC_Exit should be the last command called by the user 
31    menu or batch file.  Otherwise, the keyboard input may be accepted or reset
32    by another program.
33    IMPORTANT: Both NC_Exit and the batch file or executable called by 
34               <string> should be in your PATH.  Otherwise, these won't
35               work.  You probably should put them in your Norton Commander
36               directory, which should already be in your PATH.
37    
38EXAMPLES:
39=========
40        To run Windows from outside of the Commander, you could set
41	the user menu to:
42        W:      MS Windows
43                nc_exit win
44    (assuming WIN.COM was in your path).  Then, whenever you chose Windows
45    at your user menu, you would leave the Commander and run MS Windows without
46    it.
47
48        
49    To change the PATH in NC and have it stick (as opposed to merely staying
50    in effect for the duration of a batch file), you must exit NC, set the 
51    path, and restart NC.  This can now be automated by doing the following:
52
53        1) Create a two line batch file, consisting of:
54                PATH=<the path you wish set>
55                NC
56
57        2) Set your User Menu, Extension Files, or whatever batch file is
58           called by these to call NC_EXIT <batch file name>
59
60        For example, call the following "SETNC.BAT"

61                SET NORCMD=ON
62                NC
63        and add the following to your User Menu:
64                T:      Test NC_Exit
65                        NC_EXIT SETNC
66        Then select "T" from your user menu.  You should wind right back
67        in the Commander, but when you type "SET", you should see the
68        new environmental variable "NORCMD".  
69
70
71If you have any questions or problems, please ask in the NORUTL forum
72on CompuServe.

a code troll, worst kind of netizen, is this one. Delete thread and ban him in hell.

wd wrote:

nc_exit allows exiting nc to free up memory

Then your description about it, which mentions curses, is plain rubbish.

The synopsis wasn't written by myself. I found that on a site.
I thought it might clarify what can be confusing. I should have stated it was from the web. There are many versions of norton commander, some even developed for Linux in the early days of Linux.

What I said is true and I don't appreciate your rudeness.