
                    DVC v1.1 Msi Software 1997

                         System update util!

               (CLI/Shell only, for OS 2.0 or higher.)

-------------------------------------------------------------------
Usage: DVC FILE/A PUB/K

File is the name of a file.
Pub (optional) is the name of a pubscreen DVC will show the GUI on!
With the PUB option you can use DVC with DirWork/DirectoryOpus etc,
in fact, that's what I do, and I strongly suggest you do that also.
After you have set DVC up in your filemanager, you can use it to
check the version of new system files like libraries/devices etc.
And it will let you install/update if you want to ;-)

-------------------------------------------------------------------
What is DVC, what does it stand for?

DVC stand for "Database Version Checking",
and was the title of the original DVC.
Now DVC is just DVC ;-)

The original DVC used several databases to compare versions
of installed files with new files.
But it used an arsenal of complex DOS scripts to do this,
the DVC command itself just compared version numbers.
So the user had to update the database himself,
via a script, and even I got lost several times :-)

But the new DVC do all this by it self.
The old DVC was never released so I simply trashed it ;-)
The new DVC uses the directories themself as databases,
after all, it is where the files are supposed to go,
so why not see if they are there and what version.
So thanks to the new DVC, no databases is needed.
And no need to tell it where to put files,
all you do is click on either the YES or NO button,
it can't get any easier than that ;-)

-------------------------------------------------------------------
How does it work!

It's simple, VERY simple!
DVC looks at the file.extension,
and if it matches one of the know extensions.
It will then get the version of the file,
then it will look in the location of the INSTALLED file.
In other words it will check if you already have the given file,
and if you do it will compare versions.

Depending on the situation you will have the option to update
any new file, or install if you don't have the file on your system.

-------------------------------------------------------------------
The extensions (DVC's capability to install), is path dependant.
These are the extensions supported in this version of DVC,
and the expected paths DVC need to perform as was intended.

Normal paths:
OS 2.0+ - ".library " - "LIBS:"
OS 2.0+ - ".device  " - "DEVS:"

OS 3.0+ - ".class   " - "SYS:Classes"
OS 3.0+ - ".datatype" - "SYS:Classes/DataTypes"
OS 3.0+ - ".gadget  " - "SYS:Classes/Gadgets"
OS 3.0+ - ".image   " - "SYS:Classes/Images"

Custom paths:
OS 2.0+ - ".accent    " - "LOCALE:Accents"
OS 2.0+ - ".audio     " - "DEVS:AHI"
OS 2.0+ - ".spobject  " - "LIBS:spobject"
OS 2.0+ - ".svdriver  " - "LIBS:svdriver"
OS 2.0+ - ".svobject  " - "LIBS:svobject"
OS 2.0+ - ".svoperator" - "LIBS:svoperator"

Sub libraries:
OS 2.0+ - "xpk      " - "LIBS:Compressors"
OS 2.0+ - "smartplay" - "LIBS:smartplay"

-------------------------------------------------------------------
History!

 v1.0 - First release!

 v1.1 - Update!
        Added 4 more extensions!
        Fixed an old bug in the version routines,
        now more files will have correct version checks.
        DVC now handles version strings with "v" infront of the
        version number, but this is the only non-standard version
        strings I will let DVC handle, if DVC fail, blame the
        programmer of that file, tell him to get a proper $VER: ;-)
        DVC is now able to handle xpk and smartplay sub libraries!

-------------------------------------------------------------------
Future!

Let DVC handle more system files ;-)

So send me the name of a file DVC can't handle,
make shure you give be the real path and full filename.
I.e: name.extension, Full:File/Path/For/Drawer
For xpk sub libraries this would be:
xpkBLZW.library, LIBS:Compressors

I will then let the next DVC support the new files,
and put your name in this document for all to see ;-)

-------------------------------------------------------------------
Author!

For bug reports/comments/ideas etc, write to...

   Roger Hgensen          Email: "Msi Software <msi@sn.no>"
   Msi Software              Www: "http://www.sn.no/~msi/index.htm"
   Kolstadflata 35B
   N-7078 SAUPSTAD
   Norway

With a subject like: "DVC 1.1"

Updates of this software, and other software
can be downloaded dircetly from the above WWW address.

-------------------------------------------------------------------
Copyrights/Disclaimer/Distribution

DVC is Freely Distributable FreeWare,
it is illegal to make profit on DVC without my permission.
Only a small copying fee is permitted.
This also includes inclusion in ShareWare/SemiCommercial & Commercial,
and cover disk's/cover cd's and collection cd's.
The only exception is the Aminet CD releases,
they have my permission to put DVC on their CD's.

DVC and it's documentation and archive may not be altered and
re-released by anyone else than the original programmer,
unless authorized to do so by the original programmer.

This software is provided AS IS,
and while it has been tested and is used by the programmer himself.
This do not guarantee reliability or that it will work at all,
so you use this software at YOUR OWN risk.

This software and releated names/documentation/logos,
are copyright Msi Software 1997.

Some names in this document are Trademarks of companies/persons.

-------------------------------------------------------------------
Note to programmers and other people whom it may be of interest to!

Only files that have proper version strings will have correct version
info, if you are a programmer, look at the version string of DVC ;-)
It has a name (with no spaces), and version.revision separated by a dot ".",
and the date enclosed in () in this format: day.month.year
day may be 1-31 and month may be 1-12 year may be 0-99.
DVC has the Msi Software name behind the date,
this is not styleguide compliant but even C:Version support it in a way.
But else than that every thing must be done as described,
users/software/programmers begin to rely more and more on version info.
Simply because they have to know if a give file is correct,
if not, then using it may crash a machine.
I have taken this VERY serious,
and any software that have bogus $VER: strings or version info,
or don't even have any version info/$VER,
I will simply consider the program bad, and the programmer an amature.
This may be not be the case, but it gives them a bad first impression ;-)
