Hyperwave Logo
June 24th, 1998

The Hyperwave Information Server and Tools Patch directory

1 Available patches

Important: The content of this directory has slightly changed. Especially the patch archives were renamed, their content stayed the same. So it's not necessary to download an already installed patch.

1.1 Hyperwave Information Server 4.0

1.1.1 Patch #1

Patch status:
required. Patch must be applied before an upgrade from 2.x to 4.0.
Applicable to:
Hyperwave Information Server 2.x for Windows/NT
Solves problem:
When upgrading from previous versions of Hyperwave Information Server (2.x), the upgrade process of the data residing in the Hyperwave database may be incomplete. This patch will fix the problem and should be applied to the 2.x database files PRIOR to an upgrade to Hyperwave Information Server 4.0.
File:
./win32/is40p1.exe

1.1.2 Patch #2

Patch status:
replaced by patch #3
Applicable to:
Hyperwave Information Server 4.0 for Windows/NT
Solved Problems:
When pressing the "Restart Server" button in WaveSetup hwservercontrol crashes under some circumstances. This patch contains a fixed hwservercontrol.
File:
./win32/is40p2.exe

1.1.3 Patch #3

Patch status:
recommended.
Applicable to:
Hyperwave Information Server 4.0 for Windows/NT
Solves problem:
Under some circumstances reorganization of the fulltext index stops before being complete. Thus search results can be incomplete. Also the Hyperwave CD creation tool can stop exporting.

The hwservercontrol process consumes all CPU time when WaveSetup is accessed from a remote client.

When pressing the "Restart Server" button in WaveSetup hwservercontrol crashes under some circumstances. This patch contains a fixed hwservercontrol.

External identification using the NT authority is not responding.

This patch replaces patch number 2. Do not apply patch number 2 after patch number 3!

File:
./win32/is40p3.exe.

1.1.4 Patch #4

Patch status:
required.
Applicable to:
Hyperwave Information Server 4.0 all platforms
Solves problem:
  • Delete and move operations can cause problems with Hyperwave Information Server 4.0; especially if the object which is deleted or moved is a child of more than one parent the collection hierarchy may become slightly inconsistent in some rare cases. However, the patch should be applied in all cases.
  • Automatic Identification does not work in Hyperwave Information Server 4.0.
Files:
AIX 4.3
./unix/ibmaix/is40p4.tgz
HP-UX 10.20
./unix/hpux/is40p4.tgz
Linux 2.0.x
./unix/linux_el/is40p4.tgz
OSF/1 V4.0
./unix/alpha_os/is40p4.tgz
Solaris 2.5
./unix/sun5/is40p4.tgz
Reliant Unix 5.43
./unix/reliant/is40p4.tgz
IRIX 6.x
./unix/sgi/is40p4.tgz
Windows NT
./win32/is40p4.exe.

1.1.5 Patch #5

Patch status:
required.
Applicable to:
Hyperwave Information Server 4.0 all platforms
Solves problem:
  • Link, move and delete operations on collections can fail under certain circumstances with Hyperwave Information Server 4.0.
  • If Hyperwave Information Server 4.0 is running out of disk space during reoganization it may happen that your object soup is damaged.
  • With Hyperwave Information Server 4.0 it is possible to change an object of type 'Cluster' to an object of type 'Collection'. However, the database may crash during this (in fact, undocumented) operation -- this patch will fix this problem.
Files:
AIX 4.3
./unix/ibmaix/is40p5.tgz
HP-UX 10.20
./unix/hpux/is40p5.tgz
Linux 2.0.x
./unix/linux_el/is40p5.tgz
OSF/1 V4.0
./unix/alpha_os/is40p5.tgz
Solaris 2.5
./unix/sun5/is40p5.tgz
Reliant Unix 5.43
./unix/reliant/is40p5.tgz
IRIX 6.x
./unix/sgi/is40p5.tgz
Windows NT
./win32/is40p5.exe.

2 Patch installation

2.1 Windows

All patches in the win32 directory are selfextracting archives. To apply the patch:

  1. Download the patch into a temporary directory.
  2. Doubleclick on the patch file.
  3. Follow the instructions during the extraction of the file.

2.2 UNIX

  1. Download the patch into a temporary directory.
  2. Change to the Hyperwave Information Server home directory.
  3. Call "gzip -cd <patchfile> | tar xf -" in the Hyperwave Information Server home directory.
  4. Stop the server.
  5. Call ./tartmp/hwinsttar.
  6. Start the server.