A Change Directory program for OS/2 and DOS.
Copyright 1989-1992 Les J. Ventimiglia. All rights reserved.
VCD (Ventimiglia Change Directory) is an enhanced change
directory utility featuring a full screen mode and a command
line pop-up window for similar name directory changes. VCD
makes changing directories very easy. Accessing directories
anywhere on your disk is greatly simplified.
VCD [/rn] [d:][path]
Where : /r = Causes a complete rescan of the specified drive.
/n = Do not write the VCD data file.
d: = Drive to scan.
path = partial path to change to. Only the portion
after the last \ is used.
An invalid option will display the usage.
/ options can be combined or be specified separately before or
after any of the filespecs.
/rn == /n/r == /r /n
* Note: Protected mode usage must use the command file VCD.CMD,*
* using the executable in protected mode without the *
* command file will look like it is changing to the *
* directory but will not due to OS/2 restoring the *
* environment when the program is finished running. *
* In case someone tampers with this zip file and deletes *
* the vcd.cmd file from it, the cmd file should look *
* as follows: *
* @echo off *
* vcdpgm %1 %2 > c:\vcdx.cmd *
* if errorlevel 1 goto end *
* call c:\vcdx.cmd *
* :end *
* del c:\vcdx.cmd *
VCD will rescan the specified or implied disk in the
- The VCD database does not exist or
- The /r (Rescan) option is specified or
- The current directory of the specified disk is not
in the VCD database.
VCD will not save the database when used on drives A: or B:
or if the /n (nosave) option is used.
The database file is written to the root directory of the
specified or implied drive using the name "VCD_data". If the
drive is write protected (as some network drives are), VCD
will attempt to save the database on drive C: using the name
"VCD_x.dat" where x is the drive letter.
VCD is designed to keep the database for each drive on the
root directory of that drive. Scanning never crosses drives.
I chose to do this to support removable hard drives, such as
the Tandon Personal DataPacs. If I were to scan all drives
and keep the database on drive c: (as someone's DOS imitation
does), it would not find a directory on a drive that has been
ejected and replaced by another. Keeping the database on each
drive also allows for faster searches for the desired directory.
If [path] is specified on the command line, VCD will do the
- VCD scans the entire tree for a match to [path].
- If there is only one match,
then VCD will change to that directory.
- If there are no matches,
then VCD will remain in the current directory.
- If there are multiple matches, VCD will first check
for one exact match. If there is one exact match,
VCD change to that directory. Otherwise, VCD will
popup a box containing the choices. Move the
highlight to the one you want to reach and press to select it, VCD will change to that
Command line EXAMPLES:
To change to your INCLUDE directory on the current drive and
rebuild the VCD data file:
VCD include /r or VCD /r include
To change to the \bin directory on drive c:
If the [path] option is not specified, VCD will start up in
full screen mode.
VCD will display a graphical tree display of the directory
Once the display is up, you can use the following keys to move
around the display:
or - moves highlight up or scrolls screen down
or - moves highlight down or scrolls screen up
- - - - - - moves the screen up one page
- - - - - - moves the screen down one page
- - - - - - moves to the root directory "\"
- - - - - - - moves to the end of the display
- - - - - - ends the program and goes to the
- - Speed searches for directory match.
- - - - - - - ends the program without changing
- - - Speed search for next directory match.
- - - - - - - ReScan the current drive.
- - - - - - - Change to a different drive.
REGISTRATION AND LICENSING
If you find VCD useful, your registration would be
appreciated. Registration costs $15. Send registrations to
Les J. Ventimiglia
15247 Monroe Ave.
Moorpark, CA. 93021
Phone : (805) 529-6370
CompuServ : (CIS) 76307,1246
This program is distributed under the SHAREWARE concept.
You are encouraged to copy and share this program with other
SUPPORT SHAREWARE WITH YOUR REGISTRATION FEES!!
SHAREWARE is based on these three beliefs:
1. The value of software is best assessed by the
user on his own system.
2. Creation of personal computer software can and
should be supported by computing community.
3. That copying of programs should be encouraged,
rather than restricted.
This document and the current version of this program
("the software") are copyrighted by the author. The
copyright owner hereby licenses you to: use the software; make
as many copies of the program and documentation as you wish;
give such copies to anyone; and distribute the software and
documentation via electronic means.
However, you are specifically prohibited from charging, or
requesting donations, for any such copies, however made.
No copy of the software may be distributed or given away without
this document; and this notice must not be removed.
DISCLAIMER OF WARRANTY
LES J. VENTIMIGLIA hereby disclaims all warranties relating to
this software, whether express or implied, including without
limitation any implied warranties of merchantability or fitness
for a particular purpose. LES J. VENTIMIGLIA will not be
liable for any special, incidental, consequential, indirect or
similar damages due to loss of data or any other reason. In no
event shall LES J. VENTIMIGLIA's liability for any damages ever
exceed the price paid for the license to use the software,
regardless of the form of the claim.
Through out the testing of this program, I have found
that the VIO functions used to display output onto the
screen may not work as expected when run in real mode in a
Windows windowed DOS session or if your are running the
Novell client software on top of real mode DOS.
For Windows 3.0, I have found that if I run a VIO'ed program
in a windowed DOS session, I tend to get black characters on a
black background. This problem goes away as soon as the
cursor reaches the bottom of the windowed box.
For Novell, I have found that running VIO'ed programs tend to
crash the client software if the network card is set to I/O
port 2e0h. The solution to this problem it to move the
port address of the network card to 300h. This conflict is
due to a bug in the VIO libraries supplied with the toolkit.