Dec 242017
 
Dir lister - files color coded by extension - very configurable - fast - Free.

Full Description of File


Color directory program for DOS & OS/2.
Allows configuration via an .INI file.
Use this instead of DIR... you'll love
it!! Command line switches have been
kept close to DOS and OS/2 DIR switches
for familiarity.


File NDIR220.ZIP from The Programmer’s Corner in
Category Recently Uploaded Files
Dir lister – files color coded by extension – very configurable – fast – Free.
File Name File Size Zip Size Zip Type
DESC.SDI 33 33 stored
DESCRIBE.EXE 21600 12693 deflated
FILE_ID.DIZ 216 165 deflated
ND.BAT 175 133 deflated
ND.CMD 165 126 deflated
ND.DOC 31579 9525 deflated
ND.INI 10409 2816 deflated
NDSHORT.INI 6300 1195 deflated
ND_DOS.EXE 64896 28227 deflated
ND_OS2.EXE 96701 39532 deflated
WHATSNEW.220 2225 984 deflated

Download File NDIR220.ZIP Here

Contents of the ND.DOC file


New Directory version 2.20 for DOS and OS/2

By : Ron L. Smith
Addr: 871 Oakwood Rd.
Charleston, WV 25314


New Directory and New Directory/2 are Copyright 1995 by Ron L. Smith.
Stated simply, you are free to do whatever you desire with your own copy
(modify, hack, etc.). I don't require any money or fees for the use of
this program. Please don't distribute modified copies to the general
public. See, no flowery lawyer BS.... 🙂 If you are a Shareware author,
I would appreciate a complimentary registration of one of your programs
if you like and make use of New Directory.


New Directory is a directory listing program. It will display file
directories in 1 to 6 columns. Filenames, extensions, sizes (or the
designator), and/or file attributes will be shown depending on the column
mode for ND you are in. Files are color-coded by mask. Default colors
are assigned, but you can override defaults by modifying the ND.INI file.


Requirements: New Directory for DOS requires DOS 3.00 or higher,
New Directory for OS/2 requires OS/2 2.00 or higher.
Both require an AT or compatible computer. XTs cannot
run ND for DOS (I'm SURE you don't run OS/2 in this case).



Installation:

1) Under OS/2, no DOS support: Unzip the files into a temporary
directory, and then delete ND.CMD, ND.BAT, and ND_DOS.EXE.
Rename ND_OS2.EXE to ND.EXE. Place ND.EXE, ND.INI, and ND.DOC
somewhere in your PATH (C:\OS2, for example).

2) Under OS/2, with DOS support: Unzip the files into a directory
in your path (accessible to both DOS and OS/2 sessions). You
might consider creating a directory, such as C:\OS2\ND, and then
unzipping the files there and adding that directory to your path
statements in both CONFIG.SYS and AUTOEXEC.BAT.

3) Under DOS or DOS/Windows: Unzip the files into a temporary
directory, and then delete ND.CMD, ND.BAT, and ND_OS2.EXE.
Rename ND_DOS.EXE to ND.EXE. Place ND.EXE, ND.INI, and ND.DOC
somewhere in your PATH (C:\DOS, for example).

4) All installations: If you don't want/need to keep ND.INI or
ND.DOC, they can be deleted. They are not required for operation
of ND. However, removing ND.INI takes away quite a bit of
the configurability of the program.

5) All installations: If you made changes to your CONFIG.SYS and/or
AUTOEXEC.BAT files, then reboot your system (OS/2 users shutdown
first...ha). Now you can use ND. Type ND /? for help at any
command prompt.


Usage:

The command line interface of ND has been kept fairly close with the DIR
commands found under DOS and OS/2 for ease of use, since most will already
be somewhat familiar with the switches used. However, there is much, MUCH
more you can do with ND!


New Directory is used exactly like the DIR command as far as specifying
files goes. Some examples of use:

1) C:\> ND shows all files in current directory
2) C:\> ND A: shows all files in current directory of drive A
3) C:\> ND \SYS shows all files in SYS sub-directory of drive C
4) C:\> ND \DOS\*.EXE shows all .EXE files in DOS sub-dir of drive C
5) C:\> ND \DOS\.EXE shows all .EXE files in DOS sub-dir of drive C
6) C:\> ND /D shows all sub-directories in current dir of drive C
7) C:\DOS\SYS> ND .. shows all files in C:\DOS directory of drive C
8) C:\> ND /3 shows all files in 3 column report mode

To display all files in a sub-directory, it is not necessary to add the *.*
to the command line (see example 3 above).



COMMAND LINE:


ND [drive:][path][filename] [/A[[:]attribs]] [/B] [/C] [/D] [/DT]
[/F[FS]] [/H] [/I] [/J] [/K] [/L[DFMAH]] [/O[[:]sortord]]
[/P] [/T] [/V] [/W] [/X] [/Z] [/#]


d: Drive specification, such as A: B: C: etc.
Default is current active drive.

path Path to files, such as \DOS \SYS\FILES etc.
Default is current active directory.

filename File specification, such as *.*, HI?.*, PROG*.EXE, etc.
Default is *.* (all files).


Options:

/A Displays files with specified attributes.
attribs D Directories R Read-only files H Hidden Files
S System files A Files ready to archive - Prefix meaning "not"

Example: ND /AR show all files with readonly bit on
ND /AS-H show all system, but not hidden files

/B Uses bare format (no heading information or summary).

/C Clear screen before display.

/D Display subdirectories only.

/DT Display directory tree.

Example: ND /DT show current drive's dir tree
ND D: /DT show drive D's dir tree

/F[FS] Display sizes in kbytes instead of bytes (Files/Summary).
/F alone means show files sizes and final summary (total
drive bytes, bytes free, etc.) in kbytes.
/FF means show files in kbytes, but not summary
/FS means show summary in kbytes, but not files

/H Display (or sort) files horizontally instead of vertically.

/J Use STDOUT instead of direct video writes (uses Black/White).
Using this will allow redirection.
NOTE: If you are calling the ND executable from a batch file,
redirection may not work as you expect. If not, try calling
the .EXE directly from the command line.

/K Do NOT use Color for output (Black & White). Unlike the /J
option, /K still uses direct video writes (faster, but can't
be redirected).

/L[DFMAH] Use lowercase (dirs, files, misc, all). Default=All.
Display in lower case letters.
/L or /LA directories, files, and attributes in lower case
/LD directories
/LF files
/LM attributes
/LH Use DOS case settings for OS/2 HPFS volumes.
You can combine these options, such as /LDF.

/O List by files in sorted order.

sortord N By name (alphabetic) S By size (smallest first)
E By extension (alphabetic) D By date (earliest first)
G Group directories first H Do NOT sort directories first
Z Do Not Sort - Reverse sort order

Example: ND /OGN Sort by name (alphabetic), dirs first.
ND /OG-S Sort by size (largest first), dirs first.

/P Pauses after each screenful of information.

/T Display text files (TXT, DOC, 1ST, ME).

/V Display source code files (ASM, C, CC, CPP, PAS, BAS).

/W Uses wide list format (default = 6 columns).

/X Display executable files (EXE, COM, BAT, (and CMD for OS/2)).

/Y# This option will be recognized by New Directory/2 only (ND for
OS/2). This is the default columns to display for HPFS volumes.

Example: ND /2 /Y1 means 2 columns for FAT, 1 column for HPFS

/Z Display archived files (ZIP, ARC, LZH, ARJ, ZOO, PAK, ICE).

/# Where # is 1 to 6, number of columns to display.

Example: ND /3 display files in 3 column format.


Switches may be preset in the NDCMD environment variable. Override
preset switches by prefixing any switch with - (hyphen)--for example, /-W.

Example: In autoexec.bat, you have the line
SET NDCMD=/OGN /A /3 /L /P
If you don't want to pause, then you type:
ND /-P
This method also works for overriding default program
values, as well as options set in ND.INI.



THE ND.INI FILE

You may set your defaults in the ND.INI file as opposed (or in addition to)
the NDCMD environment variable. When ND is executed, options are used in
this priority:
1. Command line switch
2. Environment variable
3. ND.INI file
4. Built in default

For example, a command line switch has priority over all others, so switches
used in that manner will override anything set in the NDCMD environment
variable, or the ND.INI file, or built in defaults.

By default, the ND executable will look for ND.INI in the same directory it
is located in. So if ND_DOS.EXE is located in C:\DOS, then when executed,
it will expect to find C:\DOS\ND.INI. If not, it will use defaults along
with other settings (environment variable, command line switches).

If the ND executable finds the environment variable NDINI set, it will try
to load and use that copy of ND.INI.

Example: SET NDINI=C:\UTILITY\ND.INI

The ND.INI file is designed to be used with both DOS and OS/2 executables.
Filemask color codes can be set individually for DOS and OS/2 in the same
.INI file. However, if you wish to use different global settings for DOS
and OS/2, then you may want to use the NDINI environment variable, or keep
the executables in different directories (see the details section for ND.INI
at the end of this file for more information).



Using DESCRIBE.EXE:

ND for DOS will recognize the presence of a file called DESCRIPT.ION in the
directory where files are being displayed. This is a hidden file created
by Norton's DOS Command Interpreter (NDOS.COM). If you are running under
NDOS, you can use NDOS's DESCRIBE command to add descriptions to your files
(type DESCRIBE /? for help). If ND is displaying in 1 column mode, and such
a file exists, it will display appropriate descriptions as shown in
DESCRIPT.ION. You can either use ND /1 command or make this the default.
If you are not using NDOS, but would still like to use file descriptions,
I have included a DESCRIBE.EXE which I have written which will work just
like NDOS's describe command. Just type DESCRIBE /? for help.

DESCRIBE [filename.ext]
-U[PDATE]
-D[ELETE]
-?

Examples:

DESCRIBE *.COM Will allow you to add descriptions to all .COM files
in the current directory. Just hitting by
itself for a description will cause that file to be
skipped.

DESCRIBE C:\DOS\*.EXE As previous example, except all .EXE files in C:\DOS.

DESCRIBE Will allow you to add descriptions to ALL files in the
current directory.

DESCRIBE -U Will cause the DESCRIPT.ION file to be updated for
the current directory. This is useful if you have
deleted some files. It will remove the descriptions
for files that no longer exist. If you are using
NDOS, this isn't necessary.

DESCRIBE -D Will cause the deletion of the DESCRIPT.ION file from
the current directory.

DESCRIBE -? Shows the help screen.


I plan to add the description capabilities to ND for OS/2 in the near
future, but currently only the DOS version supports it.



FILES.BBS

If ND for DOS finds a FILES.BBS in the target directory (the directory files
are being displayed for), and you are displaying in 1 column mode, then
it will try to read the descriptions and display the first line only.
Note that if the first line for the file is longer than 39 characters, then
it will be truncated before display.

NOTE: DUE TO THE SIZE, PROCESSING FILES.BBS TAKES SEVERAL SECONDS. DO NOT
BE ALARMED AT THE TIME IT TAKES. I HOPE TO IMPROVE THIS IN A FUTURE
RELEASE.



If anyone observes any problems with New Directory's operation, please write
to me at the address at the top of this document. Also, you can leave a
message for me on OS/2 Shareware BBS, (703)385-8450. Leave E-mail for
Ron Smith. I can also be reached at Byte My Sektor BBS, (505)892-2930,
E-mail Asmodeus (Ron Smith).


BBSANSI environment variable:

You can set the BBSANSI environment variable, and ND will use ANSI for
color changes instead of system code. The display is a bit slower with
this option set. However, under some BBS systems, if you drop to the
operating system prompt from remote, it may work better using ANSI. You
could set this up by placing
SET BBSANSI=TRUE
in the batch file that starts up the BBS, and when the BBS ends, place
SET BBSANSI=
in the batch file. Example, running WWIV v4.23 BBS:
Edit RUNBBS.BAT (or whatever batch file you use, maybe even AUTOEXEC):
(existing batch commands)
SET BBSANSI=TRUE
C:
CD \WWIV
BBS %1 %2 %3 %4 %5 %6 %7 %8 %9
SET BBSANSI=
(existing batch commands)


ND.INI DETAILS


This section describes in detail the settings in the ND.INI file.


As stated earlier, the ND executable (whether ND_OS2.EXE, ND_DOS.EXE, or
ND.EXE) will look for ND.INI in the directory the executable is located
in. If not found, it will not look further. You can override this by
setting the environment variable NDINI to point to the ND.INI you want
to use. The .INI file is designed to allow a common interface for both
DOS and OS/2 command line sessions, but still allow customized filemask
color-coding for each environment (different filemask color-codes for DOS
and OS/2). However, if you would like to use a different .INI file for
each, then you could use the NDINI environment variable:

Example: In CONFIG.SYS: SET NDINI=C:\OS2\ND_OS2.INI
In AUTOEXEC.BAT: SET NDINI=C:\OS2\MDOS\ND_DOS.INI

Under OS/2, CONFIG.SYS is run at boot. However, AUTOEXEC.BAT will only run
for DOS and Windows sessions. So, if you open an OS/2 window or full screen
session, ND_OS2.EXE (ND.CMD) will use C:\OS2\ND_OS2.INI for it's configuration
information. If you open a DOS window or full screen session, ND_DOS.EXE
(ND.BAT) will use C:\OS2\MDOS\ND_DOS.INI for it's configuration information.

If all you want is different color codes for OS/2 and DOS, then read on!

The ND.INI file included is well commented where necessary and fairly
self-explanatory elsewhere. However, I include it here with a bit more
detail:





New Directory configuration file, for OS/2 and DOS


[Color]

;Each color code should be in the form of KIBF, where:
; K is the blink option, 1 is on, 0 is off
; I is the intensity option, 1 is high, 0 is low
; B is the background color code, 0 to 7
; F is the foreground color code, 0 to 7
;
; Valid values for B and F are:
;
; Low intensity High Intensity (Foreground Only, intensity bit = 1)
; 0 Black 0 Dark Gray
; 1 Blue 1 Light Blue
; 2 Green 2 Light Green
; 3 Cyan 3 Light Cyan
; 4 Red 4 Light Red
; 5 Magenta 5 Light Magenta
; 6 Brown 6 Yellow
; 7 Light Gray 7 White
;
; Example:
; ClsColor = 0102
; VolumeText = 0014
;
; In the first example, if you use the clear screen option of ND, then the
; screen would be cleared to Light Green on Black (in order: 0=no blink,
; 1=high intensity (bright), 0=Black background, 2=Green foreground).
;
; In the second example, the "Volume in drive x: has no label" area of the
; ND display would be Red on Blue (in order: 0=no blink, 0=low intensity,
; 1=blue background, 4=red foreground).
;

ClsColor = 0107 ; Color to clear the screen to for /C option
HeaderName = 0106 ; "New Directory" header color
HeaderVersion = 0106 ; ND version color
VolumeText = 0107 ; Volume label text color
LabelFileSysType = 0101 ; DOS: Label, OS/2: File system (FAT/HPFS/CDFS)
SerialNumberText = 0107 ; DOS only: Volume serial number text color
SerialNumber = 0107 ; DOS only: Volume serial number color
DirectoryOf = 0102 ; Directory displayed color
DirectoryText = 0103 ; Directory text color
SeparatorLines = 0003 ; Double line separator color
FileSize = 0107 ; File size color
FileDate = 0002 ; File date color
FileTime = 0002 ; File time color
FileAttribs = 0103 ; File attributes color
Description = 0103 ; File description color
FooterText = 0106 ; Summary text color
DiskBytes = 0107 ; Total disk space color
FileBytes = 0107 ; Total size of files color
TotalFiles = 0107 ; Total files color
HiddenFiles = 0004 ; Hidden file color
DirectoryColor = 0105 ; Subdirectory color
DefaultColor = 0007 ; Default color
DirScanBgColor = 0000 ; Directory Tree (/DT) background color
DirScanLineColor = 0007 ; Directory Tree (/DT) linedraw color
PauseColor = 0106 ; "Press any key..." color
KbSizeColor = 0107 ; Size color for kbyte files

KbSizeKColor = 0106 ; Size of k in kbyte files
MbSizeColor = 0107 ; Size color for mbyte files
MbSizeMColor = 0104 ; Size of m in mbyte files
ForceKbSizeColor = 0107 ; Size color for forced kbyte files
ForceKbSizeKColor= 0106 ; Size of k in forced kbyte files
ForceMbSizeColor = 0107 ; Size color for forced mbyte files
ForceMbSizeMColor= 0104 ; Size of m in forced mbyte files


[Switches]

; Bits are either TRUE/FALSE or ON/OFF or YES/NO

ClearScreen = NO ; Clear screen before starting display
Pause = YES ; Pause on full screen

; Valid options for SortType are:
; 0 Do Not Sort
; 1 Sort by File Name (alphabetical order)
; 2 Sort by File Extension (alphabetical order)
; 3 Sort by File Size (smallest to largest)
; 4 Sort by File Time/Date Stamp (oldest to newest)
;
; Use the ReverseSort option or command line switch to reverse the
; order of the sorting.

SortType = 1
ReverseSort = NO

; Valid options for FatColumns and HpfsColumns is 1 to 6

FatColumns = 4
HpfsColumns = 1

; Valid options for UseColor are:
; 0 Black & White
; 1 Color
; 2 Use Standard Output (STDOUT) for display (for redirection)

UseColor = 1

; Valid values for DirCase, FileCase, and MiscCase are YES, TRUE, or
; ON for upper case, and NO, FALSE, or OFF for lower case.

DirCase = ON
FileCase = ON
MiscCase = ON

; Valid values for HpfsCase are YES, TRUE, or ON to use DOS case settings
; for OS/2 HPFS volumes, and NO, FALSE, or OFF to display HPFS volume
; names as found. Normally you would probably want OFF, since
; HPFS file names are case sensitive (for display, not execution).

HpfsCase = OFF

DirsFirst = YES ; Sort/display directories before files
HorizontalSort = NO ; Use horizontal instead of vertical sort/display
FilesOnly = NO ; Show files, but no subdirectories
AllFiles = YES ; Show all files (hidden, system, etc.)

; Use a single character for date/time separators enclosed by quotes ""

DateChar = "-"
TimeChar = ":"
FileKbDisplay = NO ; Show file sizes in kb instead of bytes
SumKbDisplay = NO ; Show drive summary in kb instead of bytes
UseCommas = YES ; Use commas in numbers displayed

; Valid value for WideColumns is 1 to 6

WideColumns = 6 ; number of columns for the /W switch
BareDisplay = NO ; no header or footer (summary)

; AutoSelect decides if ND should try to auto select the columns to display
; and if so, the limits. A value of 0 indicates that no AutoSelect should
; be done. A value of 1 to 6 indicates the column limit for AutoSelect.
; Any other value invalidates the entry, and turns AutoSelect off.
; For example, the following line sets the maximum column AutoSelect value
; to 4.

AutoSelect = 4


[FileMasks]

;DOSFileMask can be up to 12 characters for DOS.
; (8 chars for name, 1 for period, 3 for extension = 12)
;OS2FileMask can be up to 30 characters long.
; Any valid OS/2 file specification can be used.
; Note that for HPFS systems, case is NOT sensitive for color coding.
;Wildcards (? and *) are allowed in both DOS and OS/2 specs.

;FileMaskColor should be in the form of KIBF, where:
; K is the blink option, 1 is on, 0 is off
; I is the intensity option, 1 is high, 0 is low
; B is the background color code, 0 to 7
; F is the foreground color code, 0 to 7
;
; Valid values for B and F are:
;
; Low intensity High Intensity (Foreground Only)
; 0 Black 0 Dark Gray
; 1 Blue 1 Light Blue
; 2 Green 2 Light Green
; 3 Cyan 3 Light Cyan
; 4 Red 4 Light Red
; 5 Magenta 5 Light Magenta
; 6 Brown 6 Yellow
; 7 Light Gray 7 White
;
; Example:
; OS2FileMask1 = M*.BAT
; OS2FileMaskColor1 = 0104
;
; In the example, all files (under OS/2, using ND_OS2) that start with M
; and have an extension of BAT will be non-blinking, hi-intensity Red on
; a black background.

; If all 50 available filemask codes are not needed, i.e., if you only want
; to use 5 total filemasks under OS/2, then define OS2FileMask1 to
; OS2FileMask5 and OS2FileMaskColor1 to OS2FileMaskColor5. Although New
; Directory will scan through all 50 codes to get any valid ones, it is
; faster if they are defined in sequential order with no blanks in between
; definitions.

; Be aware that ND will stop scanning for matches after the first one it
; finds, so having:
; DOSFileMask3 = *.EXE
; DOSFileMaskColor3 = 0103
; DOSFileMask8 = F*.*
; DOSFileMaskColor8 = 0104
; will result in a file such as FSH.EXE being coded as 0103, NOT 0104.
; Reversing the order of the above defined masks, so 3 is F*.* and 8 is
; *.EXE, FSH.EXE would have been colored as 0104. Just make sure you
; remember that ND stops at the first mask that matches the filename.

; The following 50 codes will be recognized under OS/2 only.

OS2FileMask1 = *.LIB
OS2FileMaskColor1 = 0002
OS2FileMask2 = *.INI
OS2FileMaskColor2 = 0003
OS2FileMask3 = *.SYS
OS2FileMaskColor3 = 0005
OS2FileMask4 = *.C
OS2FileMaskColor4 = 0006
OS2FileMask5 = *.CC
OS2FileMaskColor5 = 0006
OS2FileMask6 = *.CPP
OS2FileMaskColor6 = 0006
OS2FileMask7 = *.PAS
OS2FileMaskColor7 = 0006
OS2FileMask8 = *.BAS
OS2FileMaskColor8 = 0006
OS2FileMask9 = *.ASM
OS2FileMaskColor9 = 0006
OS2FileMask10 = *.H
OS2FileMaskColor10 = 0101
OS2FileMask11 = *.COM
OS2FileMaskColor11 = 0102
OS2FileMask12 = *.BAT
OS2FileMaskColor12 = 0104
OS2FileMask13 = *.CMD
OS2FileMaskColor13 = 0104
OS2FileMask14 = *.EXE
OS2FileMaskColor14 = 0103
OS2FileMask15 = *.ZIP
OS2FileMaskColor15 = 0106
OS2FileMask16 = *.ARC
OS2FileMaskColor16 = 0106
OS2FileMask17 = *.ARJ
OS2FileMaskColor17 = 0106
OS2FileMask18 = *.ZOO
OS2FileMaskColor18 = 0106
OS2FileMask19 = *.LZH
OS2FileMaskColor19 = 0106
OS2FileMask20 = *.PAK
OS2FileMaskColor20 = 0106
OS2FileMask21 = *.DOC
OS2FileMaskColor21 = 0107
OS2FileMask22 = *.TXT
OS2FileMaskColor22 = 0107
OS2FileMask23 = *.1ST
OS2FileMaskColor23 = 0107
OS2FileMask24 = *.ME
OS2FileMaskColor24 = 0107
OS2FileMask25 =
OS2FileMaskColor25 =
OS2FileMask26 =
OS2FileMaskColor26 =
OS2FileMask27 =
OS2FileMaskColor27 =
OS2FileMask28 =
OS2FileMaskColor28 =
OS2FileMask29 =
OS2FileMaskColor29 =
OS2FileMask30 =
OS2FileMaskColor30 =
OS2FileMask31 =
OS2FileMaskColor31 =
OS2FileMask32 =
OS2FileMaskColor32 =
OS2FileMask33 =
OS2FileMaskColor33 =
OS2FileMask34 =
OS2FileMaskColor34 =
OS2FileMask35 =
OS2FileMaskColor35 =
OS2FileMask36 =
OS2FileMaskColor36 =
OS2FileMask37 =
OS2FileMaskColor37 =
OS2FileMask38 =
OS2FileMaskColor38 =
OS2FileMask39 =
OS2FileMaskColor39 =
OS2FileMask40 =
OS2FileMaskColor40 =
OS2FileMask41 =
OS2FileMaskColor41 =
OS2FileMask42 =
OS2FileMaskColor42 =
OS2FileMask43 =
OS2FileMaskColor43 =
OS2FileMask44 =
OS2FileMaskColor44 =
OS2FileMask45 =
OS2FileMaskColor45 =
OS2FileMask46 =
OS2FileMaskColor46 =
OS2FileMask47 =
OS2FileMaskColor47 =
OS2FileMask48 =
OS2FileMaskColor48 =
OS2FileMask49 =
OS2FileMaskColor49 =
OS2FileMask50 =
OS2FileMaskColor50 =

; The following 50 codes will be recognized under DOS and Windows, or OS/2
; when a DOS window/fullscreen session is opened.

DOSFileMask1 = *.BAT
DOSFileMaskColor1 = 0104
DOSFileMask2 = *.COM
DOSFileMaskColor2 = 0102
DOSFileMask3 = *.EXE
DOSFileMaskColor3 = 0103
DOSFileMask4 = *.SYS
DOSFileMaskColor4 = 0005
DOSFileMask5 = *.DOC
DOSFileMaskColor5 = 0107
DOSFileMask6 = *.TXT
DOSFileMaskColor6 = 0107
DOSFileMask7 = *.1ST
DOSFileMaskColor7 = 0107
DOSFileMask8 = *.LHA
DOSFileMaskColor8 = 0106
DOSFileMask9 = *.ZIP
DOSFileMaskColor9 = 0106
DOSFileMask10 = *.ARJ
DOSFileMaskColor10 = 0106
DOSFileMask11 = *.ARC
DOSFileMaskColor11 = 0106
DOSFileMask12 = *.PAK
DOSFileMaskColor12 = 0106
DOSFileMask13 = *.ZOO
DOSFileMaskColor13 = 0106
DOSFileMask14 = *.LZH
DOSFileMaskColor14 = 0106
DOSFileMask15 = *.BAS
DOSFileMaskColor15 = 0003
DOSFileMask16 = *.PAS
DOSFileMaskColor16 = 0003
DOSFileMask17 = *.CPP
DOSFileMaskColor17 = 0003
DOSFileMask18 = *.C
DOSFileMaskColor18 = 0003
DOSFileMask19 = *.ASM
DOSFileMaskColor19 = 0003
DOSFileMask20 = *.H
DOSFileMaskColor20 = 0101
DOSFileMask21 = *.OBJ
DOSFileMaskColor21 = 0002
DOSFileMask22 = *.LIB
DOSFileMaskColor22 = 0006
DOSFileMask23 =
DOSFileMaskColor23 =
DOSFileMask24 =
DOSFileMaskColor24 =
DOSFileMask25 =
DOSFileMaskColor25 =
DOSFileMask26 =
DOSFileMaskColor26 =
DOSFileMask27 =
DOSFileMaskColor27 =
DOSFileMask28 =
DOSFileMaskColor28 =
DOSFileMask29 =
DOSFileMaskColor29 =
DOSFileMask30 =
DOSFileMaskColor30 =
DOSFileMask31 =
DOSFileMaskColor31 =
DOSFileMask32 =
DOSFileMaskColor32 =
DOSFileMask33 =
DOSFileMaskColor33 =
DOSFileMask34 =
DOSFileMaskColor34 =
DOSFileMask35 =
DOSFileMaskColor35 =
DOSFileMask36 =
DOSFileMaskColor36 =
DOSFileMask37 =
DOSFileMaskColor37 =
DOSFileMask38 =
DOSFileMaskColor38 =
DOSFileMask39 =
DOSFileMaskColor39 =
DOSFileMask40 =
DOSFileMaskColor40 =
DOSFileMask41 =
DOSFileMaskColor41 =
DOSFileMask42 =
DOSFileMaskColor42 =
DOSFileMask43 =
DOSFileMaskColor43 =
DOSFileMask44 =
DOSFileMaskColor44 =
DOSFileMask45 =
DOSFileMaskColor45 =
DOSFileMask46 =
DOSFileMaskColor46 =
DOSFileMask47 =
DOSFileMaskColor47 =
DOSFileMask48 =
DOSFileMaskColor48 =
DOSFileMask49 =
DOSFileMaskColor49 =
DOSFileMask50 =
DOSFileMaskColor50 =




NOTES:

1) If you use only DOS, then you can delete ND_OS2.EXE, ND.BAT, and ND.CMD,
and rename ND_DOS.EXE to ND.EXE.

2) If you use only OS/2 (no DOS support), then you can delete ND_DOS.EXE,
ND.BAT, and ND.CMD, and rename ND_OS2.EXE to ND.EXE.

3) You might consider creating a small ramdisk, copying the ND related
files to it, and making that drive appear first in your path statements.
This will speed up the program(s) considerably for users with slower
computers. Under DOS (and/or Windows), this can be achieved by:

a) Edit CONFIG.SYS, add the line:
DEVICE=C:\DOS\RAMDRIVE.SYS 256
This creates a 256k ramdisk. Make it the last command in your
CONFIG.SYS if you have a CD-ROM drive, so that it is the last
drive in your system. Be sure the path to the RAMDRIVE.SYS driver
is correct.
b) Edit AUTOEXEC.BAT, add the line:
COPY C:\DOS\ND\*.* F:\ > NUL
Now put this drive first in your path, i.e., if you path was:
PATH=C:\DOS;C:\;C:\WINDOWS;C:\UTILITY
make it read:
PATH=F:\;C:\DOS;C:\;C:\WINDOWS;C:\UTILITY
Be sure the drive used (F: in this example) corresponds to the
actual drive letter of your RAMDISK.
c) Reboot your system.

Under OS/2, this can be achieved by:

a) Edit CONFIG.SYS, and at the end of the file, add the line:
DEVICE=C:\OS2\BOOT\VDISK.SYS 256,, (NOTE: This is under OS/2 3.0.)
(Under v2.xx, there may be a )
(different path, but the driver)
(name is the same, I believe. )
b) Also in CONFIG.SYS, insert the drive letter of your ramdisk as the
first pathname of the OS/2 PATH statement. So, if you path was:
SET PATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\INSTALL; (etc.)
then make it:
SET PATH=F:\;C:\OS2;C:\OS2\SYSTEM;C:\OS2\INSTALL; (etc.)
Be sure the drive letter used is the actual drive letter of your
ramdisk.
c) Edit AUTOEXEC.BAT, add the line:
COPY C:\OS2\ND\*.* F:\ > NUL
Replace C:\OS2\ND\ with the actual path to your ND files, and make
sure the target drive (F:\) is your actual ramdrive.
Now put this drive first in your path, i.e., if you path was:
PATH=C:\OS2\MDOS;C:\;C:\WINDOWS;C:\UTILITY
make it read:
PATH=F:\;C:\OS2\MDOS;C:\;C:\WINDOWS;C:\UTILITY
Be sure the drive used (F: in this example) corresponds to the
actual drive letter of your RAMDISK.
d) Shutdown and Reboot your system.


4) If you like all the speed you can get, you might consider deleting the
commented ND.INI file, and renaming the NDSHORT.INI file from the
distribution package to ND.INI. This is the same .INI file with all
comments removed, and any unset options removed (such as DOSFileMask50).
Even processing of comments takes a little time. 🙂

5) Remember that to override default switches, or switches set by the
NDCMD environment variable or ND.INI file, use the - for the switch,
i.e., if FileKbDisplay = YES in the ND.INI file, you can override this
by using the /-F or /-FF switch at the command line.

6) If you are displaying files on a HPFS volume under OS/2, then ND for
OS/2 will show files that were truncated for display with a trailing
^ character. Example:
This_Is_A_File
3 column mode will display the file as
This_Is_A_F^
to indicate that the filename has been truncated for display.
NOTE that OS/2 will hide long filenames/directory names from DOS
sessions, so you will not see them anyway.

OS/2 is (C) International Business Machines (IBM)
Windows is (C) Microsoft Corp.
NDOS is (C) Symantec


 December 24, 2017  Add comments

Leave a Reply