home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware 1 2 the Maxx
/
sw_1.zip
/
sw_1
/
WINDOWS
/
UTILS
/
WCMD110.ZIP
/
README.TXT
< prev
next >
Wrap
Text File
|
1992-04-04
|
9KB
|
178 lines
Windows Command Readme file
Welcome to Windows Command!
What is Windows Command?
Windows Command is a command line interface designed
for the Microsoft Windows environment. It combines the
features of enhanced DOS command line interpreters with the
ability to access the features of Windows. These features
include:
* User-definable execution menu
* Disk serial number retrieval in DIR and SER.
* FINDFILE command to search entire drives for files.
* Microsoft Windows 3.1 and 3.0 compatiblity
* Novell Netware compatible
* command history/recall with history save and load
* filename completion with wildcard support
* command aliases
* Parameter substitution and user-definable variables in
aliases and batch files
* multiple commands per line
* redirection of standard output
* a complete command set including MOVE, PRINT and EXCEPT
* a File Browser to access filenames through a file dialog
* minimize, maximize or close any window from the command line
* set Windows filename associations from the command line
* display various information in the title bar
* much more!
When and why would I use Windows Command?
Windows Command can be used any time you would normally
run a DOS shell, such as COMMAND.COM, under any mode of
Windows. This means you can have "DOS" running in a window
under 386 Enhanced, Standard, and even Real mode Windows!
You can also use Windows Command as your Windows shell,
instead of Program Manager or File Manager. If you are
accustomed to using the command line in DOS, and find you
can issue commands faster by typing than by dragging your
mouse around, Windows Command can help you to be more
productive while using Windows. If you don't have a mouse
(or just don't like to use it), you will find that Windows
Command makes it much easier to access the abilities of
Windows.
Windows Command is a true Windows program, which means
you may start any Windows program from its command line,
which is either impossible or difficult from ordinary DOS
shells. With Windows Command, you will use less memory, and
less processor time than if you ran a DOS program under 386
Enhanced mode Windows (Windows Command takes as little as
55K of RAM). The result is that Windows Command is a
faster, smaller command-line interface.
Windows Command allows interaction with Windows in a
manner much more familiar to experienced users than through
any graphical Windows program. Almost every computer and
operating system in the world is accessed through some form
of command line, be it DOS, Unix, VMS, CP-M, etc. While a
command-line may seem less friendly to new users, it still
provides the most powerful method of executing commands.
Windows Command takes advantage of this to provide the best
of both worlds: powerful command-line control over a
powerful graphical system. Experienced users will certainly
benefit from this, and the graphical elements make the
Windows Command environment a much friendlier and easier
place for new users to learn about DOS and the command line.
How do I use Windows Command?
Using Program Manager, File Manager, or another Windows
Shell program, execute the File Run command from the menu,
and type WCOMMAND.EXE (don't forget to include the pathname
to the directory it is in: e.g. C:\WIN\APPS\WCOMMAND.EXE),
then press ENTER, and Windows Command will start. That's
it! If you need help at any time, press F1, issue the HELP
command at the command line, or choose a Help option from
the menu. Since Windows Command uses most of the same
commands and conventions as COMMAND.COM for DOS, you can use
your DOS reference manual to help you get started, as well.
What files should I have received with Windows Command?
The complete package contains the following files:
General Information Files
README.TXT General information about Windows Command (this file!)
ORDER.TXT an order form for registering Windows Command
RELEASE.TXT notes on releases of Windows Command
LICENSE.TXT The Windows Command License Agreement
Program Files
WCOMMAND.EXE the Windows Command executable file
WCOMMAND.HLP the Windows Command help file
WCLIB.DLL the Windows Command function library
Sample feature/Utility files
RUN.BAT DOS batch file for running dos programs
SAMPLE.HST sample history list file
UNIX.WCB sample batch file to emulate a Unix C-Shell
WCOMMAND.MNU sample menu file
Anyone is free to distribute this unregistered package
of Windows Command provided that all the above files remain
together in the package. More detailed information on
copying this package is available in the license agreement,
in the file LICENSE.TXT.
What do I do with the sample feature files that come with Windows Command?
RUN.BAT is a batch file used for running DOS programs
that print text on the screen. Normally, when these programs
terminate from a DOS full-screen session under Windows,
the screen clears before you have a chance to see what
the output is on the screen. RUN.BAT puts a pause after
the execution of the program to allow you to see what
output the program gave, then you can press any key when
you are ready to continue. You can use RUN.BAT by issuing
RUN <command> at the command line, where <command> is any
DOS command with 9 or less arguments. For example,
RUN UNZIP WCMD11.ZIP would run the command UNZIP WCMD11.ZIP,
then pause after execution for you to press a key.
SAMPLE.HST is a file made by issuing a HISTORY LIST >
SAMPLE.HST command at the Windows Command command line. In
the file itself, each line represents one command saved in
the command history. You can load the commands in this file
into the history list by issuing a HISTORY LOAD SAMPLE.HST
command at the command line. You can save and load history
files of your own by using the commands described here.
UNIX.WCB is a sample batch file included just to
demonstrate one of the capabilities of Windows Command batch
files, the emulation of other command-line systems. Since
the shareware version of Windows Command does not support
batch file execution, you will not be able to execute
UNIX.WCB directly, but you can type in the commands from the
batch file individually to see what the result of running
the batch file would be.
WCOMMAND.MNU is a sample menu file that can be loaded
by issuing the MENU command. This will load the menu
described in the menu file into the Windows Command menu
bar. You can modify this menu file by editing it (with
Notepad or another text editor) to include any command you
wish to have menu access to.
More information on HISTORY, batch files, and MENU is
available in the Windows Command online help system.
Why should I register Windows Command?
After the 21-day evaluation period expires, you must
either register the program, or stop using it. However,
the sooner you register, the sooner you will be able to
take full advantage of all the features of Windows Command.
If you like Windows Command and want to use it as your
shell or just as a Windows utility, registering will eliminate
the introductory dialog boxes found in the shareware version
(yes, even the one with my smiling face on it). Those screens
are there to introduce new users to Windows Command, and to
remind you that your copy of Windows Command is not a
registered copy (and, I must admit, creating those dialogs
was fun!). The registered version eliminates these boxes,
and allows you access to all the available features of
Windows Command. These extra features are documented in the
file RELEASE.TXT, which should have accompanied this
package. Registered users will also receive discounted or
free upgrades to new versions of Windows Command as commands
and features are added.
How do I register Windows Command?
All the information you need is in the opening screens,
or in the file ORDER.TXT, which should have accompanied this
package. You should read over LICENSE.TXT completely before
filling out the order form. You can view any of the .TXT or
.DOC files that came with Windows Command by using Notepad,
which ships with Microsoft Windows.
What if I have an idea for a feature I'd like to see in
Windows Command?
By all means, send it to me! I'd love to hear your
ideas, and am looking forward to incorporating more
features. You can write to me at the address below:
Michael B. Tierney
205 Inglewood Dr.
Pittsburgh, PA 15228 USA
or send electronic mail to:
Compuserve: 70604,1512
Internet/Bitnet: 70604,1512@compuserve.com
I'm looking forward to hearing from you!