home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Artville: Photography Comping CD 99.7
/
Artville-StockImages-PhotographyComping-99.7-WinMac.bin
/
win_kudo
/
setup16
/
win31rdr.exe
/
README._XT
< prev
next >
Wrap
Text File
|
1996-08-05
|
6KB
|
131 lines
Kudo« Catalog Reader (tm) version 3.0 for Windoes 3.1 ReadMe file
(c) 1996 Imspace Systems Corporation.
All Rights Reserved.
San Diego,CA USA
support@imspace.com
www.imspace.com
August 05, 1996
System Compatibility:
*********************
Kudo Image Browser is a Windows 3.x application that will run under Windows 3.1, 3.11,
Windows for Workgroups 3.1, 3.11, For Windows NT, and Windows 95 please download and use
WIN95RDR.EXE.
Using the Browser.
******************
Launch Kudo by:
1. double clicking on the Kudo executable in the File Manager or the Kudo icon in the Program Manager.
2. Double clicking on a Kudo catalog.
Full details on functions and features of Kudo is contained in the Help file.
*********************************************************************************
STAY IN TOUCH - VISIT OUR WEB SITE! - www.kudo.com
*********************************************************************************
MORE INSTALLATION NOTES:
This section documents what the Kudo installer does during installation:
- Application files are copied to the target directory, typically c:\kudoRead
- The installer searches for the Microsoft OLE 2.0 DLLs on your machine. Three
things can happen as a result of this search:
1) If they are found (as the result of someone having installed
another OLE 2.0 compliant application), and they are of the same or
a newer version as the copies that Kudo is shipped with, then nothing
is done.
2) If they are found but are of an older version than the
copies Kudo is shipped with, then the Kudo installer will copy its
newer versions over the existing ones, wherever it might find them
on your machine.
3) If they are not found, Kudo places new copies of all the OLE 2.0
DLLs into your windows\system directory.
The OLE 2.0 DLLs are functionally an extension to the Windows 3.1 operating
system, and so are effectively not a part of Kudo at all. This means that,
once installed, they are available for all applications that support OLE 2.0,
and need not be installed more than once. Other OLE 2.0 compliant applications
will generally observe this convention, and will not duplicate these files in
their installation if they are already present. For this reason, if you
un-install Kudo, it may be risky to remove these files unless you are certain
there are not other applications that rely on them. The OLE 2.0 DLLs are:
ole2.dll
ole2conv.dll
ole2disp.dll
ole2nls.dll
ole2prox.dll
compobj.dll
storage.dll
- Additional DLLs, like BWCC.DLL, etc. are installed following an identical procedure
to the OLE DLLs. This file fills a support function and is shipped with
many applications.
- The Kudo installer determines if it needs to modify AUTOEXEC.BAT. You will
be prompted before it modifies the file. If you agree to modification, the
line:
SHARE.EXE /L:500 /F:5100
will be added to AUTOEXEC.BAT. If there is already a line present that loads
SHARE, then that line will be modified to ensure that the /L and /F options
are at least as large as the amount that Kudo requires.
- The Kudo installer then registers Kudo as an application with Windows,
and takes care of registering OLE 2.0 on your machine. Effectively, this
modifies the registration database, REG.DAT, in your windows directory, and
indirectly, your WIN.INI file. It is accomplished by running REGEDIT.EXE
with the files OLE2.REG and KUDO.REG, which are installed to your target Kudo
directory. This operation can be repeated manually if REG.DAT ever becomes
corrupted, see tech note file "REGEDIT.TXT".
********************************************************************************
Known Installation Problems:
Two situations have been observed to cause problems with the installer:
1) Installing to a PC that is configured as a diskless workstation can confuse
the installer as to the whereabouts of your AUTOEXEC.BAT file. In this
situation, the installer generally cannot access your boot drive. When the
installer attempts to modify your autoexec file, it will probably come
up with a path to an AUTOEXEC.BAT that doesn't exist, such as A:\AUTOEXEC.BAT.
If this happens, you will need to make the modifications yourself. Select
the option to NOT have the Kudo installer modify your autoexec file, and
then, after the installation is complete, manually add the line:
<path>\SHARE.EXE /L:500 /F:5100
to your AUTOEXEC.BAT file. <path> is the full path to your DOS directory
(or wherever SHARE.EXE exists). The /L & /F options are suggested minimums.
If you are already loading SHARE in your autoexec, then you only need to
ensure that you add the command line options to the SHARE statement. If
the options are already there, and they are larger, then leave them alone.
If they are there but are smaller, then use the values suggested here.
You will need to reboot your computer for this change to take effect.
2) Installing to a network version of Windows can cause problems if the
user does not have write privileges to some of the Windows directories.
The Kudo installer may need to add some DLL's to your current windows\system
directory. This directory will often be on a networked drive that is read-
only when you are running a network version of Windows. You will get messages
to the effect of "Can't write to file ... due to read-only protection...", etc.
This indicates that you will need to have the network supervisor run the
installation in supervisor mode to obtain proper write access to the
necessary directories.
*********************************************************************************
!!!!!!!!!!! LAST MINUTE CHANGES:
Relative Relative Addressing allows anyone with a Browser
Addressing: to access images or media files if the media files are in the same
directory as the catalog or in the same path with a different drive letter.
For example, if the CDROM drive letter changed from D: to L:, Kudo
Catalog Reader will locate the media file and display it or play it!
The same applies to placing images.