=======================================================
              README FOR INTERBASE 7.0
=======================================================

________________________________
New Features

For a description of new features, and changes in 
InterBase 7.0, please read ReleaseNotes.pdf.

Printed versions of the InterBase 7 documentation can 
be purchased via the Web at http://shop.borland.com/ 

_____________________________
Installation

Before you install, please read the install.txt file
for your operating system.

________________________________
JDBC driver (InterClient)

InterBase 7 ships with a new type 4 JDBC driver. This
new driver does not require the presence of InterServer
and surfaces all the new InterBase 7 features. To
upgrade a client, all that is necessary is to place the
type 4 interclient.jar on the CLASSPATH of the client
machine. The type 3 driver is included for backward
compatibility. Borland strongly recommends that you use
the new type 4 driver if possible.

_____________________________
Known issues in InterBase 7.0


I.  Install Issue with Windows 2000

  If you have a previous version of InterBase 7.0 on your
  computer, you will need to follow these steps before
  you install:

  1.  Go to Services and shut down InterBase Guardian 
      and Server.
  2.  CLOSE THE SERVICES APPLICATION.  This looks like
      a Win2k bug, if you do not close this, the install
      fails until you reboot.
  3.  Go to Control Panel and launch "Add-Remove Programs"
  4.  Remove InterBase.
  5.  Delete the full InterBase directory.
  6.  Delete gds32.dll from c:\winnt\system32
  7.  Install InterBase.

II.  Performance Issue with Windows ME/XP

  Microsoft has implemented a backup and restore utility
  called System Restore.  Unfortunately they have decided
  to backup the default InterBase file extension 'GDB'.
  This is causing performance problems on these systems
  because every time a *.gdb file is attached to and
  modified, System Restore automatically backs it up.
  
  Because of this situation, we have changed the name of
  the InterBase security database from isc4.gdb to admin.ib.
  If you want to continue using your old security database,
  we recommend that when you restore it to a new name,
  such as admin.ib, when you back it up and restore it 
  with the InterBase 7 gbak. We also recommend that you no
  longer use .gdb for any of your database names on these
  platforms, to avoid the performance degradation
  associated with having the OS back up every database
  every time it is modified. 

  However, if you need to retain "gdb" as the extension
  for your security database and for other databases, we 
  have developed the following workarounds for this issue:

  1. Turn off system restore.
     a. Go to Start.
     b. Right click on My Computer
     c. Select Properties
     d. Select the Restore tab
     e. Check the "Turn off System Restore on all drives" box
  2. Install InterBase on its own hard drive or partition and 
     turn off Restore on the drive.
     a. Go to Start.
     b. Right click on My Computer
     c. Select Properties
     d. Select the Restore tab
     e. In the Drive Settings area, select the drive where you 
        installed InterBase.
     f. Select the Settings button
     g. Check "Turn off System Restore on this drive"
  3. Make isc4.gdb read only.
     a. Run "gfix -mode read_only"
     b. Please note:  This will disable gsec and other utilities
        from making security changes.  You will have to use 
        "gfix -mode read_write" to modify isc4.gdb.
  4. Our open source community has found a possible 
     workaround by editing its FileList.xml file that lists file
     extension to be restored.  This file is located in 
     c:\windows\system\restore on most systems.  However this
     workaround is not recommended and may infringe on licensing 
     issues on your operating system.

For bug fixes, future updates, and current information
on issues for InterBase 7.0, please go to our Community site:
http://community.borland.com/interbase

___________________________
Uninstalling InterBase 7.0

The Windows InterBase install/uninstall allows you to choose
between performing a complete install/uninstall or selecting
individual components. If you install a subset of the
components, you can run the install again later to add
more components.

__________________________
Migration

If you have a 5.x or older version of InterBase YOU MUST
BACKUP YOUR OLD DATABASE FILES!  There are no known cases
of data corruption, but you should always backup your files
before you install InterBase 7.0.

InterBase 7 uses the On-Disk Structure (ODS), ODS 11.
Databases created with InterBase 5 used ODS 9.1, InterBase
6 used ODS 10, and InterBase 6.5 used 10.1. To take
advantage of new InterBase 7 features, You must use gbak to
back up any databases that you intend to use with the
Version 7 software. Then restore it using the InterBase 7
gbak to convert it to ODS 11. Once a database has been
converted to ODS 11, it cannot be converted back to earlier
versions of the ODS.

__________________________
Tutorial

Because of popular demand, we have included tutorial.pdf in
this release.  It was written for InterBase 5 and 6 and
doesn't mention InterBase 7.0.  However, the information is
still true for 7.0 and customers will find it valuable.

-------------------------------------
Copyright (c) 2002 Borland Software Corporation
All rights reserved.

