home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
High Voltage Shareware
/
high1.zip
/
high1
/
DIR4
/
VGO10.ZIP
/
README.1ST
< prev
next >
Wrap
Text File
|
1993-11-14
|
8KB
|
141 lines
GO.CMD/VGO.EXE Copyright (c)1993 M.O.S.E.S./Kari Jackson.
All Rights Reserved.
Just some real quick notes to get you started.
These programs are shareware, not freeware. If you don't know
what that means, just read the GO.DOC and/or VGO.OLH file(s).
These programs require OS/2 2.1 (no reason to believe that 2.0
wouldn't work also, but it's never been tested) with REXX support
installed.
Installation instructions are in this file. Instructions for
running GO are in the GO.DOC file.
Instructions for running VGO are in the VGO.OLH (OnLineHelp)
file. That's the file that is displayed when you hit the Help
menu object (or the F1 key any time you're not on an object that
has its own context-sensitive help) from inside the program. You
can read it that way or with your favorite file browser. But if
your favorite file browser happens to be a text editor, BE
CAREFUL! If you were to look at the file with an editor and tell
it to wrap the text so you can read it (because every paragraph
in the file is one LONG line!), and then you forget to exit your
editor WITHOUT saving, then the file will be pretty much ruined.
Each paragraph is one long line because that's the way it has to
be. If you change that and then save the changes, the text will
look absolutely horrible when you use the online help from within
the program, from then on.
But with that caution, please do read the VGO.OLH file or you'll
probably miss some of VGO's features by just not noticing that
they're there. And the VGO.OLH file is much more complete than
the context-sensitive help that you get by hitting the F1 key
while a help-containing object has the focus (usually the dotted-
line box around it).
GO and VGO are virtually the same program, just designed for
different tastes. GO is the commandline version, and VGO is the
graphical (or Visual) version. Now if you like graphical things,
that does not necessarily mean you'll never want to use GO. If
you ever wish that you could have VGO do something while unat-
tended, it's very likely that what you want can be done using GO
with the right combination of commandline parameters. For this
reason, registration of VGO automatically gives you the right to
use GO also.
In very simple terms, GO and VGO can be thought of as "file
funnels". They are used to sort through mass quantities of
files, and feed individual file names to programs that use them.
GO and VGO can use names, sizes, file dates, and/or file
attributes as search criteria. Files can be retrieved and acted
upon from any location on the system without the user supplying
a directory name. The more you use GO and VGO as front ends for
commands that require filenames, the more you'll come to
appreciate the power of these "funnels".
GO and VGO cannot be properly used with commands you don't
understand. They can't help you to copy files unless you know
how to use the COPY command. You can't use them to change a
file's attributes without knowing the syntax of the ATTRIB
command. So GO and VGO really can't be called file maintenance
shells. But what they do is allow you to execute commands you do
know the syntax of, on faraway files without specifying those
files' locations, and/or on groups of files according to their
names, sizes, dates, and/or attributes.
We've never yet seen a utility that could do all the things that
GO and VGO can, and there are many GO/VGO features for which
we've never seen or heard of ANY equivalent utility. For example
we've seen utilities that will let you delete files according to
their date stamps, but never have we seen a utility that would
let you do ANYTHING YOU WANT to a group of files by date, other
than graphical shells where you have to find the files yourself
and select them and then tell the shell to do something to the
selected files. GO and VGO will find the files that fit your
date specification FROM ANYWHERE ON YOUR SYSTEM and show you ONLY
THOSE FILES, and let you say whether you want to do something to
all of them, or just some of them, or whatever. For many types
of tasks, that's much easier than the way those pesky graphical
shells work.
To install GO.CMD, just put it into a directory on your PATH
variable in CONFIG.SYS.
To install VGO.EXE, put the VGO.EXE file into a directory on your
PATH variable in CONFIG.SYS, put the VROBJ.DLL file into a
directory on your LIBPATH variable in CONFIG.SYS, and put the
VGO.HLP file into a directory on your HELP variable in
CONFIG.SYS. Then either type VGO from a commandline or create a
WorkPlace Shell program object for VGO and doubleclick on it.
You must use the version of VROBJ.DLL (1.01a) that was
distributed with VGO.EXE, or a later version. If you have an
earlier version of VROBJ.DLL and attempt to use VGO with that one
available instead of this one, then VGO.EXE will abort with an
error message saying that it can't run with that version of
VROBJ.DLL. Because of a confirmed bug in VX-REXX version 1.01,
the error message will confuse you by saying it wants VROBJ.DLL
version 1.00, which is probably the only one you would have
besides the one you're supposed to have. That's because Watcom
just forgot to change the text that the error message displays.
What you need is VROBJ.DLL version 1.01a, which is the one that's
bundled with VGO.EXE.
When you run VGO.EXE, if your default application font is too
big, you won't be able to read all the words on the VGO window.
All you need to do to fix that is drag a font from OS/2's Font
Palette and drop it ONTO THE SEARCH BUTTON of VGO's first window.
It will not work if you drop the font anywhere else.
The files included in this .ZIP archive are:
FILE_ID DIZ 448 11-14-93 1:00 Description
README 1ST 7872 11-14-93 1:00 This file
GO CMD 32712 11-14-93 1:00 GO executable
GO DOC 33544 11-14-93 1:00 GO instructions
VGO EXE 158794 11-14-93 1:00 VGO executable
VGO OLH 34284 11-14-93 1:00 VGO instructions
VROBJ DLL 581359 9-22-93 13:59 Runtime module
The name "OS/2" belongs to the International Business Machines
corporation, "VX-REXX" and the VROBJ.DLL file (which is being
distributed here according to the terms of the license) belong to
Watcom International, "4OS2" belongs to Rex Conn and J.P.Software,
and "Qedit" belongs to SemWare. And by the way, those are all
EXCELLENT pieces of software! (Well, obviously they are, or else
I wouldn't be using them and having reason to mention them in
VGO's documentation!)
Enjoy!
Kari Jackson
KariJackson@Delphi.COM
DWDP74A@Prodigy.COM
RIME node 5008
Bart Toulouse
Bart11903@Delphi.COM
RIME node 5008
Sunday, November 14, 1993