VGO is a program that lets you execute other commands upon files or groups of files according to their dates, sizes, and/or attributes, and lets you do things to faraway files without specifying the location of those files.
First you tell VGO what kind of files you want to find, and what areas of your system you want VGO to search in order to find them. Then VGO finds all the files that match your specifications and shows them to you on its second window. You select the files you want to act upon, and tell VGO what you want to do to those files, and then VGO tells OS/2 to perform your desired command on each of the files you had selected.
VGO'S FIRST WINDOW
It is very important that the user pay attention to the Status Lines at the bottom of each window. A small bit of online help appears there, for whatever object your mouse pointer is on, and during execution VGO puts various warning messages and status messages there.
The dropdown menus work the same way as any other CUA-compliant OS/2 menus. One thing a lot of people don't seem to know is that you can often get a little online help (in the Status Line) for a menu item by clicking your mouse on that menu item. That doesn't mean you have to execute it to find out what it does, because the item doesn't get executed until you unclick the mouse! You can hold the mouse button down and read the Status Line and then drag the mouse pointer elsewhere before letting go of it.
And here are descriptions of each of the objects on the First Window:
FILE SPECIFICATION dropdown combo box
Here's where you tell VGO what kind of filenames to look for. You can select one of the defaults like *.TXT, *.EXE, etc. And you can customize that list of defaults from the Wildcards option on the Configuration menu.
Or you can type your own specification. That filespec can use wildcards if you want, the same way the OS/2 commandline does, with a few enhancements. If your filespec doesn't contain . or * then VGO will add *.* to it so that FILE would turn into FILE*.*. If your filespec starts with . then VGO will add * to the beginning of it so that .INI turns into *.INI. (Can you tell we don't like to type asterisks?) Or if you leave this box blank, VGO will search for *.*.
But this specification cannot contain a \ character. If it did, that would mean you were specifying a particular directory, and this box is not the place for that. That's the job of the dropdown combo box that is enabled when you click on the One Dir Only radio button.
If you're typing an HPFS filename in this box, do not surround it with ' or " symbols.
INCLUDE FLOPPIES check box
Unless you tell it to, VGO will not waste your time by checking to see whether you have a disk in a floppy drive and then searching on the drive if there is a disk. VGO just ignores floppy drives altogether. So if you want VGO to include floppy drives in the search, you want to click on this option. Then VGO will look to see if there's a disk in each floppy drive, and search the drives that do have disks in them.
VGO will ignore floppy drives that do not contain disks, rather than bothering you with continual "Abort, Retry, Fail" error messages like so many programs do.
SEARCH ALL DIRECTORIES OF ALL DRIVES radio button
This is the default. Unless you tell it otherwise, VGO will always search all directories of all drives except A: and B:. (A: and B: will be included if you check the Include Floppies check box.)
If you want to exclude any drive(s) from the search, take a look at the Drives option on the Configuration menu. That option allows you to tell VGO to ignore certain drives that it wouldn't otherwise ignore. Drives that don't exist are always ignored, of course. Floppy drives that don't contain disks are ignored. And CD-ROM drives that don't contain data disks are ignored. So you don't need to exclude those.
But if you do have a data disk in your CD-ROM drive, and you don't want VGO to waste time looking at it, you can exclude that drive. And you can make that exclusion either temporary or permanent (see the section THE VGO.INI FILE below), as you desire.
SEARCH ONE DRIVE ONLY radio button
If you want VGO to search only one particular drive, click here. (If the drive you want to search is A: or B:, click on Include Floppies first!) After a moment, a dropdown combo box will become enabled and offer you a selection of all the drives that are currently available on your system. If you forgot to put a disk into a floppy drive, that drive won't show up in the combo box. Put the disk in and click on Search One Drive Only again (and wait a second) to refresh the combo box.
ONE DIR ONLY radio button
If you want VGO to search only one particular directory, click here. After a moment, a dropdown combo box will become enabled and offer you a selection of all the directories on all the drives that are currently available on your system. (If you particularly want one drive's directory names to appear at the top of that list, select that drive from the Search One Drive Only radio button before you click on One Dir Only.)
If you go to another OS/2 session and create a new directory, its name won't show up in the combo box until you refresh it by clicking on One Dir Only again (and then wait a second for VGO to reread your drives).
Of course you don't have to select the directory's name from the combo box. You may simply type the full d:\dir\subdir of the directory you want, in the entry field.
ONE DIR AND ITS SUBS radio button
This one works exactly like the One Dir Only radio button, except that it causes VGO to search your selected directory's subdirectories also.
DATES group box
If you want to narrow down the search according to the last update dates of the files, you want to specify your desired dates here. The labels for the entry fields say "Later than:" and "Earlier than:" but what they actually mean is "Later than or equal to:" and "Earlier than or equal to:".
When you specify the dates, you must give the month first, then the day, and then the year. If you don't use any / or - separators between the parts, then you must use two digits for each part, even for numbers less than 10. For example 010593 will work for January 5, 1993, but 1593 will not. However if you do separate the parts with / or - characters, then you don't need both digits for months and days less than 10. 1/5/93 and 1-5-93 (and 1/5-93, for that matter) will work fine.
If you fill in both the "Later than:" box and the "Earlier than:" box, the "Earlier than:" date cannot be earlier than the "Later than:" date. That would be telling VGO to show you files that are both earlier than an earlier date and later than a later date. A file can't be both at the same time!
If the "Later than:" date is earlier than the "Earlier than:" date, then the result will be all the files from those two dates and all dates in between. If the two dates are the same, then the result will be all the files from that date and no others.
A different way to specify a date is by typing a - followed by a number. -25 would mean 25 days ago. -0 would mean today. -365 would mean one year ago, and that's as far back as this feature goes. Of course, these numbers are relative to your computer's system date. If your computer is not set to the right date, then this -### option is going to give you results that may not be what you intended.
ARCHIVE, HIDDEN, READ-ONLY, and SYSTEM group boxes
By default, the only files VGO will find are ones that have no Hidden, Read-only, or System attributes, regardless of whether they have their Archive attributes turned on or not. If you want VGO to search for files with other attributes, you use the radio buttons in these four group boxes to tell it so.
And if you want to have a different default, you can get it easily. Just set the radio buttons in these four group boxes the way you want them, and then hit the Attributes option in the Configuration menu. VGO will save your preference in a file named VGO.INI and use that as the new default for these four group boxes from now on.
Each of these group boxes has three radio buttons. The + one means that VGO will search only for files that do have that attribute turned on. The - button means VGO will search only for files that have it turned off. And the Both button obviously means VGO is going to ignore that attribute and show you all the files that do have it and all the files that don't.
VGO can't change the behavior of a command that doesn't see hidden files or doesn't write to read-only files. If you click on the "Both" button in the "Hidden" group box so that VGO shows you hidden files, and then execute a COPY command after selecting a hidden file, all COPY is going to do is say "File not found", just like it would at the commandline. COPY can't see hidden files at the commandline, so it can't see them when executed from within VGO either.
The exception to the above paragraph, though, is the DEL and ERASE commands. If your command is DEL or ERASE, VGO will always remove H, R, and S attributes from any selected files that have them, before passing the DEL or ERASE commands to the operating system. So if you don't want to delete any hidden files, don't use the DEL command with the "Both" or "+" buttons set in the "Hidden" group box.
SIZES group box
If you want to narrow down the search according to the sizes of the files, you want to specify your desired sizes here. The labels for the entry fields say "Larger than:" and "Smaller than:" but what they actually mean is "Larger than or equal to:" and "Smaller than or equal to:".
If you don't tell VGO otherwise, then the numbers you type here will be specifying the file sizes in bytes. If you want to type the number of kilobytes (that's 1024 bytes) instead, type a K after your number. If you want to type the number of megabytes (that's 1024 kilobytes), type an M after your number.
If you fill in both the "Larger than:" box and the "Smaller than:" box, the "Smaller than:" number cannot be smaller than the "Larger than:" number. That would be telling VGO to show you files that are both smaller than a smaller size and larger than a larger size. A file can't be both at the same time!
If the "Larger than:" size is smaller than the "Smaller than:" size, then the result will be all the files that have either of those two sizes or anything in between. If the two sizes are the same, then the result will be all the files that have that exact size and no others.
When we said "that exact size", we meant "that EXACT size". 3K does not mean "between 2.5K and 3.5K". It means 3K. 3072 bytes. If you want "between 2.5K and 3.5K", then you type 2.5K in the "Larger than:" box and 3.5K in the "Smaller than:" box.
SEARCH button
When you're done telling VGO all about what kinds of files you want it to find, click on the Search button. Your mouse pointer will turn into a little clock, and VGO will start searching for files.
Unless of course one of your entries is invalid (such as a filespec that contains the \ character or a size entry field that contains the letter B), in which case VGO will send your cursor back to the object you made the error on (the File Specification box or the Sizes box, in those two examples) so you can correct your error. Or if there are no files that match your specifications, VGO will say so and send your cursor back to the File Specification box.
While VGO is searching for files, you might decide you want to cancel the search. If so, click on the Stop Now! check box (which is only enabled when VGO is doing a search) and VGO will stop searching as soon as it's done with whatever step it's working on at the time you click on Stop Now! The time interval should rarely be over one second, except when VGO has just started searching a CD-ROM drive when you click on Stop Now! Shouldn't even take long then, either.
VGO'S SECOND WINDOW
As soon as VGO is finished with the search, the second window comes up while the filenames are still being added to the second window's list box if there are a very large number of filenames to add. You can interact with any of the objects on the second window while the filenames are still being added, except the list box, the three radio buttons right below it, and the Execute button.
When the files are done being added to the list box, if you find that you've made a wrong selection on the First Window so that the list box is showing you the wrong filenames, you can just move the Second Window out of the way and make your change to the First Window, and then click on either the Search button on the First Window or the Refresh button on the Second Window, to get VGO to search again.
But if you do that, and an entry you made on the First Window is invalid (such as a date like 31/2/93 -- because 31 is not a valid month), VGO will make the Second Window disappear so that your attention is forced back to the First Window so you can correct your error.
There are no Minimize or Maximize buttons on the Second Window. If you want to do something with the First Window, you simply move the Second Window out of the way. If you want to minimize the entire VGO program, you move the Second Window enough so that you can reach the First Window's Minimize button, and then clicking on it will minimize both windows. When you bring VGO back up from the Window List, both windows will come back up if both were up at the time you minimized the First Window.
COMMAND TO EXECUTE dropdown combo box
This is where you tell VGO what you want to do to the files it helps you to select. You can select one of the default commands like COPY, DEL, etc. (And you can customize that list of defaults from the Commands option on the Configuration menu.) Or you can type your own command. Of course the only kind of command it makes sense to execute from VGO is a command that takes a filename as a parameter.
VGO just passes this command to the operating system as is, so it'll only work from within VGO if it would work from the commandline. It must be an internal command, or in the current directory, or on the PATH variable, or else you must specify its pathname right here in the Command To Execute box. Just like you would at the commandline. Otherwise OS/2 won't be able to find the command to execute it.
TAKING ADVANTAGE OF THE START COMMAND
One interesting use for VGO that most people might not think of, is using START as the command, and the command you really want to execute as the filename for VGO to find! Let's say you have a command you want to execute, but you don't remember where you put its executable file and you can only remember that the first two letters of its name are AB.
With VGO, all you have to do is put AB into the File Specification box and click on Search, then select your executable file in the Second Window's list box when VGO finds it, choose START from the Command To Execute box, click on the Change Directory check box so that your command will execute in its own directory, and click on Execute.
Of course if your AB*.EXE program wants any parameters, they go in the Parameters After Filename entry field. And don't click on Use START Command though, or else you'll be executing START /C START AB*.EXE instead of START AB*.EXE (where AB*.EXE is, of course, the filename that VGO found for you that began with the letters AB).
HELP button
If you enter the name of an OS/2 command that takes a filename as a parameter into the Command To Execute box, then you can click on this button and VGO will execute HELP [command] in the background. This will bring up OS/2's Command Reference online book, open to the page that tells about your Command To Execute.
PARAMETERS BEFORE FILENAME and PARAMETERS AFTER FILENAME entry fields
VGO lets you work with any command that takes a filename as a parameter. But many commands also require or allow other parameters so that you can tell them more about what you want them to do with the filename. When you want to pass any parameters to your command other than the filename, you put them in one of these boxes.
If the command wants a parameter to go before the filename on its commandline, then you put that parameter in the Parameters Before Filename entry field. The Parameters After Filename entry field is for parameters that are supposed to go after the filename on the command's commandline.
For example, if you wanted to execute COPY [filename] A:\DIRNAME then you would put COPY in the Command To Execute box and A:\DIRNAME in the Parameters After Filename box.
If you wanted to execute FIND /I "Text" [filename] then you would put FIND in the Command To Execute box and /I "Text" in the Parameters Before Filename box.
If you wanted to execute PRINT /B [filename] /D:LPT2 then you would put PRINT in the Command To Execute box and /B in the Parameters Before Filename box and /D:LPT2 in the Parameters After Filename box.
This "Parameters Before Filename" and "Parameters After Filename" business is the main reason for our statement in the README.1ST file that VGO can't help you too much with executing commands whose syntax you don't understand. Except for the little Help button next to the Command To Execute box (which will help you a little), VGO can't make you put the right parameters into the right places. You have to know that for yourself.
THE FILE SELECTION LIST BOX
Obviously this is where you select the file or files you want your command to act upon. You select files from this box using the same rules that work in any other CUA-compliant OS/2 list box. If you want to select more than one file right next to each other, you can just select the first one and hold the mouse button down and drag it across the others you want to select.
But if you want to select items that are not next to each other, then in order to select later ones without unselecting earlier ones, you must hold down a Control key while selecting the later ones. No, we don't like it either, but that's the CUA specification so that's how OS/2 programs are supposed to work.
The list box will show the date, size, attributes, and full pathname specification for each file it finds. It's all very intuitive except the attributes display. The attributes display is five digits wide. The first column is for the Archive attribute, the second is for the Directory attribute (which will always be - in VGO since VGO doesn't display directories), the third is for Hidden, then Read-only, then System. They're in alphabetical order.
An attribute that's turned on will be represented by its letter, and one that's turned off will be represented by a - sign. So A--R- would be a file that has the A and R attributes turned on and the D, H, and S attributes turned off.
Due to VX-REXX's use of the List Box instead of the Text Container Object, and the fact that OS/2's List Box code is 16-bit instead of 32-bit, the File Selection List Box can't hold more than 64K of data (until the next version of VGO which will be after the next version of VX-REXX which will allegedly allow Text Container Objects).
That means if you make some file specifications that lead to a really long list of matching files, they may not all fit in the list box. When that happens, VGO will say "WARNING! #### files found but only #### files displayed!" in the Status Line at the bottom of the Second Window so you'll know that you're not seeing all of the files that match your specifications.
Under these circumstances, if you click on the Select All or Exclude Highlighted radio buttons and then the Execute button, VGO is going to ask you whether you want to execute your command on all of the files displayed in the list box or all of the files that matched your specification (or in the case of the Exclude Highlighted radio button, the question will be which group of files you want to exclude the highlighted ones from).
That way, you never delete files you haven't confirmed in the list box unless you want to, even if all your matching files aren't showing in the list box and you choose Select All.
SELECT ALL radio button
This tells VGO to select all the files in the list box without making you do it manually.
SELECT HIGHLIGHTED radio button
This is the default. It tells VGO to perform your command only on the files that you've selected in the list box.
EXCLUDE HIGHLIGHTED radio button
This is the opposite of Select Highlighted. It tells VGO to perform your command on all the files in the list box except for the ones you've selected.
CHANGE DIRECTORY check box
If you check this option, VGO will change to the drive and directory that contains each filename before executing the command with that filename. For example if you tell VGO to do something to C:\DIR1\FILE1.EXT and D:\DIR2\FILE2.EXT, then VGO will make C: current and make DIR1 current before executing the command with FILE1.EXT as the parameter, and then VGO will make D: current and make DIR2 current before executing the command with FILE2.EXT.
FILENAME ONLY check box
Usually VGO passes the full filename specification of each of your selected files to the command, as in [command] [d:\dir\subdir\filename.ext]. But if you check this box, then VGO will only pass the filename itself, as in [command] [filename.ext].
And the Change Directory check box will automatically get checked because obviously the command won't work on [filename.ext] unless it's in the current directory. In fact you can't uncheck Change Directory while the Filename Only check box is checked, even if you try.
ONE LONG COMMAND check box
Usually VGO executes your command over and over again, once with each filename you've selected. If you want VGO to execute the command just once, with all the filenames on the same commandline at the same time, then check this check box.
Just be careful, because it would be possible to exceed OS/2's commandline length limit that way, and doing that can have some very bad consequences (or not, depending on the particular command you were trying to execute).
If you're using VGO to execute a DOS program, it gets really easy to hit the limit! Because the limit for DOS programs is only 127 characters, and for some reason OS/2 itself uses up over twenty characters of that when it starts a DOS session.
You might want to use the Filename Only check box to keep the length down, but if you do, be aware that it will only work if all the files you select are in the same directory. Because when you're only executing the command once, you can only do it from one current directory, right?
PAUSE check box
If you're selecting more than one file to act upon and you want VGO to execute the command with one filename and then wait, before executing the command with the next filename, and wait again, and execute the next filename, etc., then you want to check this check box.
USE START COMMAND check box
If you check this box, VGO will change your command from [command] to START /C [command] before executing it, so that each iteration of the command will start up in a separate session.
This is particularly necessary for commands that require what's called VIO support. That means fullscreen (or full window) character mode programs such as the wonderful text editor Qedit. If you try to execute Qedit from within VGO without checking the Use START Command check box, it'll try to run and it'll say "A program in this session has encountered an error and cannot continue".
Just check Use START Command and hit Execute again, and then it'll work right. Qedit (or whatever command you're using that needs VIO support) will run in a separate session, so it won't be trying to use the VGO Command Output window, so all will be well.
EXECUTE button
When you're done messing with all the other objects in the Second Window and you want VGO to execute your command, click here. The Stop Now! check box on the second window will become enabled, so that if you want to you can stop whatever commands have not already been executed by the time you hit that check box.
If your command is DEL or ERASE, or if your command is COPY, XCOPY, or MOVE and you did not specify any target location in the Parameters After Filename entry field (so that the files would be copied or moved into whatever happens to be the current directory), VGO is going to ask you if you're sure you want to do that.
If you don't want VGO to ask you that, you can turn off this feature temporarily by hitting the No suboption under the Confirmation option on the Configuration menu. And you can make that change permanent (see the section THE VGO.INI FILE below) after changing it, by hitting the Save option there if you want to.
VGO will execute your command once for each filename you have selected. The commandlines that get executed will be made up of these parts:
[command to execute] [parameters before filename] [file specification] [parameters after filename]
If you've selected three filenames, then the above command format is going to be executed three times; once for each filename. If you've selected a hundred and forty-two filenames, the above command format will be executed a hundred and forty-two times with a different filename specification each time.
Of course the above paragraph is true only if you have not checked the One Long Command check box.
VGO's mouse pointer will turn into the clock symbol while the commands are being executed.
THE VGO COMMAND OUTPUT WINDOW
This is where your command's output will show up, if your command puts out any of what's called "Standard Output" or "Standard Error". Those are the kinds of output that are given by most non-fullscreen character mode utilities. The VGO Command Output window will always come to the foreground so that you can easily read the output, and then it will always go away automatically so that it doesn't get in your way too much.
If you want to see the VGO Command Output window again after it has minimized itself, just hit the Output button at the bottom of VGO's Second Window. Then minimize it again when you're done by clicking on its Minimize button.
If you use 4OS2 rather than CMD as your default command interpreter, the VGO Command Output window may act just a bit strangely. Particularly with the DIR command. No harm done, it's just an irritation. It makes you hit <Enter> to continue after every few lines of output. We've only seen this happen with the DIR command so far, though.
In your Window List, the VGO Command Output window will always show up as "VX-REXX Console" instead of by the name it has on its title bar. VX-REXX is the development environment we used to create VGO, and VX-REXX Console is what they call the window where the output shows up. The title bar can be changed from within the program, but what it says in the Window List cannot. So I could put "VGO Command Output" into its title bar, but it still says the same old thing in the Window List.
Each time you hit the Execute button, a line that says -=-=-=-=- gets added to the VGO Command Output window. This is so that you can tell where one execution ends and the next begins, if you hit the Execute button more than one time during one VGO session.
THE AFTERMATH
When VGO's done executing your command with each and every filename you had selected, you find yourself back at the Second Window again.
You can perform a different command on the same filenames that are still highlighted.
You can hit the Refresh button to make VGO redo the search (which is often desired after deleting files, so you can see that they're really gone).
You can close the Second Window or move it out of the way to return to the First Window.
In fact, you can do pretty much anything you want to do at this point.
THE VGO.INI FILE
When you make a change to VGO's configuration, that information is stored in a file named VGO.INI in the same directory where your VGO.EXE file is. Every time you run VGO, it looks in that location for the VGO.INI file and if that file is found, then VGO will use your desired configuration rather than the default.
If you ever change all of your preferences back to the defaults so that there's no longer any purpose for the VGO.INI file, the program will delete it for you automatically rather than leaving it on your drive taking up space for nothing.
If you want to rename VGO.EXE to SomethingElse.EXE, be sure and change VGO.INI to SomethingElse.INI also, since what VGO actually looks for is an .INI file with the same first name it has, rather than VGO.INI specifically.
Other places in this online help have mentioned making a permanent change to VGO's configuration. Of course nothing is actually permanent. In this case the word "permanent" only means "until you delete your VGO.INI file or use the Configuration menu to change your options again". Not really permanent. Just permanent from one VGO session to the next.
So here are the things you can configure and put into the VGO.INI file:
FONT
In order to change VGO's font, you just drag a font from OS/2's Font Palette and drop it onto the Search button on VGO's First Window. Yes, I said the Search button. Sorry, but nowhere else will work. The next time you activate the First Window (by switching away from it and switching back, for example), the font of all the objects on the window will change to the font you dragged and dropped. And the next time the Second Window is activated, it'll get this new font too.
Every time you exit from VGO, it looks to see what font is on the Search button and if it's different than the font that was there the last time you started VGO, then the new font name will be saved to the VGO.INI file for use as the default in the future.
The list box object on the Second Window, though, where the filenames are displayed, will not use the font you dragged and dropped if you have the System Monospaced font installed in your system. VGO will use System Monospaced for that list box whenever possible, so that the columns will line up. Every other part of VGO, though, will use the font that you drag and drop. The list box will too, if you don't have System Monospaced installed at all.
ATTRIBUTES
By hitting the Attributes option on the Configuration menu, you can store your current Attributes radio button settings as the default for future VGO sessions. Just set those four group boxes of radio buttons the way you want them, and then click on this option.
COMMANDS
On VGO's Second Window, the Command To Execute dropdown combo box contains a list of the most commonly-used OS/2 commands that take filenames as parameters. If you want a particular one of those to appear at the top of the list or if you want to add other commands or program names to the list that appears in that combo box, click on this option and follow the instructions provided.
CONFIRMATION
Whenever you try to execute a DEL or ERASE command, VGO will ask you if you're sure you want to do that. Whenever you try to execute a COPY, MOVE, or XCOPY command without specifying a target location, VGO will ask you if you're sure you want the files to be placed into the current directory (which is what happens when you tell OS/2 or DOS to copy or move a file without telling it where).
If you don't want VGO to ask you these two "Are you sure?" questions, you can tell it so by clicking on the No option on the Confirmation submenu under the Configuration menu. This change does not become permanent, though, until you also hit the Save option on the same submenu. And of course later, if you ever want VGO to ask those questions again, you can make it do so by hitting the Yes option, and if you want to you can make that change permanent by hitting Save on that menu again too.
DRIVES
If you have a drive that VGO would see as available (hard drive, floppy with a disk in it after you've clicked on the Include Floppies check box, or CD-ROM drive with a data disk in it) and you want VGO to ignore that drive, you can tell it so via the Drives option on the Configuration menu.
You can specify one drive or twenty here, and you can make the exclusion temporary or permanent, as you desire.
WILDCARDS
On VGO's First Window, the File Specification dropdown combo box contains a list of the most commonly-used wildcard specifications like *.DOC, *.EXE, *.TXT, etc. If you want a particular one of those to appear at the top of the list or if you want to add other filenames or wildcard specifications to the list that appears in that combo box, click on this option and follow the instructions provided.
DISCLAIMER
While this Program has been thoroughly reviewed and tested, it is provided solely "as is" and without warranty of any kind. M.O.S.E.S., Kari Jackson, Bart Toulouse, and Watcom specifically disclaim all warranties, expressed or implied, including but not limited to implied warranties of merchantability and fitness for a particular purpose with respect to defects in any portion of the package.
In no event shall M.O.S.E.S., Kari Jackson, Bart Toulouse, or Watcom be liable for any loss of profit or any other damage, including but not limited to special, incidental, commercial, consequential or other damages of any kind resulting from defects in this software or its documentation. USE THIS PROGRAM AT YOUR OWN RISK.
(Watcom is the company which provides VX-REXX, the development environment under which VGO was written, and VROBJ.DLL, the runtime module that tells OS/2 how to draw the dialog boxes and many fascinating things like that. Without VX-REXX and VROBJ.DLL, VGO would be just GO.)
SHAREWARE
This Program is shareware, not freeware. What that means is this: It may be freely distributed to anyone as long as all of its files and documentation are distributed together. It may be freely used for evaluation purposes, to decide whether you like it. If you do like it and want to continue using it, you are supposed to register it. We will not have you arrested or sue you if you don't, but you should feel guilty about it if you have a conscience.
Using someone else's copyrighted work without their permission is against the law, and we do not give you permission to use VGO.EXE or GO.CMD longer than necessary for evaluation purposes (like about a month) unless you register it.
To register VGO and GO, just send $15 to Kari Jackson at 3201 Monroe Street, Omaha NE 68107-4048. If you've already registered a previous version of VGO, don't do it again. Future versions are all free to registered users of earlier versions.
Sorry, we won't send you a registered copy of the program because the shareware version just does not have one single disabled feature, so there's no reason to. <grin>
