README.TXT File

Genitor (R) Object Construction Suite
Version 4.01

(C) Copyright 1998 Genitor Corporation

This file contains complementary and
late-breaking information about the Genitor
Object Construction Suite.

If you have not yet installed the Genitor
system, you can run SETUP.EXE directly from
the distribution media.

=-=-=-=-=-=   Setup Errata   =-=-=-=-=-=-=

o  Installing Genitor to a NetWare server
   Drive

The InstallShield installer may not run properly
on a server running certain versions of Novell
NetWare, particularly those which do not 
completely support long file names.  If you need
to install Genitor to a Netware drive and 
experience difficulties during the process, 
contact Genitor Technical Support at 
support@genitor.com or (734)213-2500 for a 
workaround procedure.

o  Running the Genitor toolbar in Microsoft 
   Visual Studio on Windows NT without 
   Administrative rights.

Visual Studio requires its user to have 
administrative rights to install additional
toolbars.  They are only needed during the
initial installation and activation of the
toolbar, and can be removed once the toolbar
appears.

o  Installing Genitor on Windows 98

Some users have reported long (2-5 min) delays
at the beginning and end of the install program
when running on Windows 98.  There appear to be
no ill effects other than the delay.

o  Installing Genitor on Windows 98 running the
   Client for NetWare Networks.

In this configuration, clicking the browse button
during the installation process may cause the
installer to crash.  This is due to a known bug in
the Nwnp32 DLL.  If you experience this problem,
re-run Setup, and type the necessary paths manually
rather than using the browse button.

o  Installing Genitor on a Windows 95 Network
   Drive with Windows/NT Client Workstations

If you plan to locate the Genitor system
directory on a shared network drive on a Windows
95 peer-to-peer server, and you plan to setup a
Windows NT machine as a Genitor workstation, you
should use only short (8.3) directory names for
the Genitor System directory.

Using long directory names in this configuration
will cause the Genitor Workstation Setup program
to fail (when launched from an NT workstation)
with an error message indicating that SETUP.EXE
can not be found.

This problem is caused by a documented
communication problem that exists between Windows
95 servers and Windows NT client workstations.
If you must install Genitor in this
configuration, you can avoid this problem by
using only 8.3 directory names.

o  Installing Genitor in a Read-Only Network
   Drive

Genitor can be configured to execute from a
read-only network drive. Refer to your Genitor
User's Guide (Genitor.hlp) for details.

=-=-=-=-=-=   Release Notes   =-=-=-=-=-=-=

Additional complementary and late-breaking
information, including a list of changes in this
release, is contained in the Release Notes
document which is installed by the Genitor System
Setup program. You can access this document via
the Genitor System or Genitor Workstation item on
your start menu after Setup has completed.

^{Source:readme.txt Rev 15.0}