-
Think Pad You can specify the source and destination directory
(CVIPHOME)
-
Repair You can specify the installation method, which has three
choices
-
Data Recovery Binary installation: This is the easiest way, which will install
the CVIPtools executables and other run-time support modules,
including the full documentation. With binary installation, you
will be able to run cviptcl, cvipwish, and the CVIPtools with the
graphical user interface. This type of installation requires about
18 megabytes of disk space, plus 26 megabytes if you install the
images. The binary installation process will take about 10 minutes,
although this may vary depending on the speed and type of your
computer system.
-
Cisco Library installation: Besides all you get from the binary
installation, you will also get the libraries which you can link to
create your own applications. You will also get CVIPlab, which is a
skeleton program showing how to create stand-alone applications
using the libraries. This type of installation requires about 22
megabytes of disk space, plus 26 megabytes if you install the
images. The library installation process will take about 10
minutes, although this may vary depending on the speed and type of
your computer system.
-
Keyboard Source installation: This is the most sophisticated way, and
should be used only if you intend to modify the CVIPtools source
code itself. With the source installation, the installation script
will install the source and then compile to get the libraries and
executables. Of course, you need an ANSI C compiler to do this.
Right now we only provide the makefiles for Microsoft Visual C++
4.0 or higher versions. This type of installation requires about 55
megabytes of disk space, plus 26 megabytes if you install the
images. The source installation process will take about 1 hour,
although this may vary depending on the speed and type of your
computer system. Do not be surprised if warning messages appear,
this is OK.
-
Monitor The installation program can be used in 3 ways, but note that
two versions exist:
To install CVIPtools from the CD-ROM shipped with the
book use the version on the CD-ROM.
To install CVIPtools if you have downloaded the files
from the FTP site (http://www.ee.siue.edu, use the version from the
FTP site.
To install CVIPtools from one directory to another one,
which is usually used when you export a file system from one
computer to another computer of a different architecture, use the
version from the FTP site.
Desktop If you are unsure which version you have, run the install
program. The CD-ROM version says "Installation for CD-ROM" in the
header and sign-on message, the other version does not.
Infosys Quick reference for problems during
installation:
Refurbished Laptops It is possible that during installation, or when you run the
CVIPtools.bat file, you get an error message " of environment
space" (this will happen only in Windows 95, not Windows NT). In
that case go to the MS_DOS Prompt window, click the mouse button at
the top of this window and select '' Then select the '' folder and
set the ' Environment' to the maximum value. Next, try to run
CVIPtools. If it still doesn't work, performing the installation
again should solve the problem.
Wipro If you get an error message during installation that says " file
MSVCRT.DLL", you will need to get the file from the Microsoft
website, www.microsoft.com. This may occur if your computer system
setup does not include this file, it is available from Microsoft
for free.
Lap Top If you do the library installation and have problems linking
with our precompiled libraries, we recommend that you do a source
installation. This will compile the libraries with your specific
compiler and system configuration. If, after source installation,
the system cannot find the libraries, be sure they have been copied
from their respective directories to the %CVIPHOME%\lib directory
(the library files are called libname.lib).
Refurbished If you try a source installation under Windows95, and you get a
message " to create CVIPtools.bat file", you need to first remove
the CVIPtools.bat file in the %%\bin directory. Next, redo the
installation and change both the source and destination directory
to be the same as the destination directory that you specified for
the first installation (note: the default destination is
C:\CVIPtools).
Memory With the source installation under Windows95, if there are
compilation problems, try running the installation program again
with the source AND destination directories specified to be the
original destination directory - this will redo all the compilation
processes. This usually solves compilation problems. We found that
with some versions of the compiler, operating system and libraries,
that we had to run the install two or three times to successfully
compile. Note that these problems are typically internal compiler
errors, and not related to the CVIPtools code.
Intel In case you are able to run the cviptcl shell but not the
CVIPtools GUI, first run the cviptcl shell, then within that shell
change to the GUI_SCRIPTS directory under the %%\CVIPTCL directory
and type: ' ./ *.tcl' This command is used for setting up the
indexing information for the GUI scripts.
As400 If the CVIPtools windows do not fit on the screen, increase the
screen resolution with the 'Control Panel', using the 'Display'
folder (a resolution of 800×600 works for most CVIPtools windows,
but a few require 1024×768). Also, check the configuration under
'File->Preferences/Window manager name' in the CVIPtools GUI -
it should be set to Win32.
================================================================
Averatec CVIPTOOLS ENVIRONMENT
Hardware The CVIPtools environment variables are initialized to default
values during installation, and can be changed by editing
%CVIPHOME%\bin\CVIPtools.bat.
Dual Xeon CVIPHOME is set to the top of the CVIPtools source tree.
CVIPHOME is used by CVIPtools to locate its various modules. It is
also used by the accompanying CVIPlab module to locate libraries
and include files. During installation, CVIPHOME is initialized to
the directory in which you install CVIPtools.
Storage CVIP_IMGPATH is a search path used by CVIPtools to locate
images. Set this to point to your image directories. By default,
CVIP_IMGPATH is initialized to
%%\Images.
Seagate TK_LIBRARY and TCL_LIBRARY are needed by the tcl scripts, and
are set to point to the tcl and tk distributions inside CVIPtools.
These distributions are located under
%%\CVIPTCL\lib\tk4.2,
%%\CVIPTCL\lib\tcl7.6.
Computer Sales Another required environment variable for tcl/tk scripts is
XF_LOAD_PATH, which will be set to
$/CVIPTCL/GUI_SCRIPTS.
Computer Hardware CVIP_DISPLAY controls the program that is used to display images
after processing by CVIPtools. Currently,the Win32 counterpart to
the X-windows based image viewer (which is used for UNIX systems)
has not been ported. However, you can choose any image viewer
available on your system, as long you can display an image by
typing the following command in a DOS shell:
Printers Viewer_name <image_name>
Technology By default, the viewer environment variable, CVIP_DISPLAY, is
set to lviewpro.exe, which is a shareware program we used in our
testing. It works well with CVIPtools and has nice features.
Lviewpro is shipped with CVIPtools, but you are free to use any
viewer you want. Note that with lviewpro, you must hit the escape
key after an image is displayed.
Mainframe For WindowsNT/95 users we have provided the UNIX man (manual)
pages in HTML format. These pages describe each of the CVIPtools
library functions, and have examples of their usage. The files are
located in the %%\man\html1 and %%\man\html3 directories.
===============================================================
Samsung SUPPORTED PLATFORMS:
-
Computer Repair Microsoft Windows NT3.51/4.0/95. Compiled and Tested using
Microsoft Visual C++ 4.0 and 5.0(See the README.unix for
information on the unix systems).
-
Used Computers Solaris 2.x (the primary development platform). Compiled and
tested with gcc and Sparc C compiler 3.0
-
Network IRIX 5.3/6.2. Compiled and tested.
-
Digital Cameras Linux RedHat 4.0, Slackware 96. Compiled and
tested.
-
Desktops FreeBSD 2.1.5. Compiled and
Tested.
Cognos If you port to other systems, please let us
know.
================================================================
Hosting PURPOSE AND INTENDED USAGE:
Netfinity Of course, you're free to use this package for whatever you
please, with the notable exception that you can not charge a fee
for it. However, this software was developed with two specific
goals in mind: education and research.
Internet CVIPtools was developed, and is continually being upgraded, at
Southern Illinois University at Edwardsville (SIUE). At SIUE
CVIPtools is used in both undergraduate and graduate courses in
conjunction with a laboratory manual. Each student sets up his/her
environment using the files located in %%\docs\CVIPlab. The student
then has the full set of libraries available for linking.
Cheap Computer CVIPtools may also be used for research. We have found that much
of the time spent on research in the field is spent in recoding
algorithms which have already been coded elsewhere by others. It is
our hope that CVIPtools contains a complete enough collection of
algorithms as to eliminate some of this coding overhead.
Researchers creating custom code should find much of interest, and
may wish to set up a development environment as described above and
link with the CVIPtools functions. Additionally, check out our Web
site at http://www.ee.siue.edu/CVIPtools for current and upcoming
developments. Current work includes:
-
Digital Camera Extending the history function to allow the user to create their
own algorithms and automatically create a GUI for them
-
Printer Creation of a wavelet/vector quantization compression
toolkit
-
Xseries Addition of more and better image sharpening
algorithms
-
Maxtor Enhancement of edge detectors, edge linking, Hough
transform
-
Data Storage Various utilties and more compression
algorithms
-
Hitachi Additional transforms and better filtering for
wavelets
-
Rational And others...
Websphere At this release, we don't provide a Win32 Makefile for the
CVIPlab program for two reasons. First the makefile is dependent on
your compiler, but the CVIP libraries are designed to be compiler
independent (we built the libraries using MSVC++4.0 and tested
using MSVC++5.0, but they can be linked by other compilers).
Secondly, most people prefer to use the integrated development
environment like the developer studio of MSVC.
================================================================
Battery CVIPtools copyright notice:
It Support Copyright © 1996, 1997 SIUE - by Scott E
Umbaugh.
Western Digital Permission to use, copy, modify, and distribute this software
and its documentation for any non-commercial purpose and without
fee is hereby granted, provided that the above copyright notice
appear in all copies and that both that copyright notice and this
permission notice appear in supporting documentation. This software
is provided "as is" without express or implied arranty. The
developers and SIUE shall not be held liable in any event for
incidental or consequential damages in connection with, or arising
out of, the furnishing, performance, or use of this
program.
