Index of /download/A0630/win32
Name Last modified Size
Parent Directory -
README 2000-06-05 18:05 11K
eq63_client_developer.cab 2000-06-05 18:06 2.9M
eq63_client_gui.cab 2000-06-05 18:06 770K
eq63_client_runtime.cab 2000-06-05 18:06 1.2M
eq63_doc_html.cab 2000-06-05 18:06 558K
eq63_manuals_html.cab 2000-06-05 18:06 973K
eq63_manuals_pdf.cab 2000-06-05 18:06 1.7M
eq63_server.cab 2000-06-05 18:06 1.3M
eq63_win2k.exe 2000-06-05 18:06 231K
eq63_win9x.exe 2000-06-05 18:07 1.6M
eq63_winnt.exe 2000-06-05 18:07 1.6M
old/ 2019-08-07 16:03 -
readme.txt 2000-06-05 18:05 11K
HP Eloquence A.06.30 - Windows Installation - 2000-06-05
This directory holds the current release of the HP Eloquence A.06.30
installation program for the 32bit Windows platform.
This installation program is based on the Microsoft Windows Installer and
thus complies to the Microsoft Windows 2000 logo requirements.
Supported platforms: Windows 2000, NT, 98 and 95
* IMPORTANT NOTE: If you have a previous A.06.30 beta release installed *
* it is required that you uninstall it first using the *previous* *
* installation program before starting the new installation program. *
* This applies to previous A.06.30 beta releases before 2000-03-08. *
1) Download the appropriate setup executable depending on your operating
eq63_win2k.exe - for the Windows 2000 platform
or if the Microsoft Windows Installer engine is already
present on your Windows NT, 98 or 95 system
eq63_winnt.exe - for the Windows NT platform
eq63_win9x.exe - for the Windows 98 and 95 platforms
Unless you plan to install HP Eloquence A.06.30 on several machines
and different platforms you need only one of these three files.
The setup executables for Windows NT, 98 and 95 are about 1.4 MB bigger
than the one for Windows 2000 because they additionally include the
Microsoft Windows Installer engine which is a Windows 2000 system component.
If the Microsoft Windows Installer engine is already present on your
Windows NT, 98 or 95 system it is sufficient to download the rather small
eq63_win2k.exe (use Start Menu -> Find -> Files or Folders to look for a
file named msiexec.exe - if it exists the Microsoft Windows Installer
engine is already present).
2) The several HP Eloquence components are divided into separate "cabinet"
files by category. Depending on your requirements, you might not need all
of them. Each cabinet is self-contained and can be selected during the
setup process if you choose a customized installation.
Just download all the components you need. They are:
- contains the runsrv32 and dlgsrv32 graphical user interface components
necessary to execute any local or remote GUI-enabled HP Eloquence
program. Such a program can conveniently be started with either the
eqstart or eqexec32 utilities which are both included as well.
This is the minimum client installation.
- contains the eloqcore program which enables you to locally execute
your HP Eloquence programs. Additionally, the HP Eloquence configuration
utility is included. If your programs all reside on remote systems it
is not necessary to install this cabinet.
- contains the HP Eloquence Integrated Development Environment (the IDE)
as well as the list and store utilities and all data base client
programs such as schema, dbcreate and dbimport. If you do not modify
your programs or data bases on the particular system it is not necessary
to install this cabinet.
- contains the eloqdb6 data base server as well as the eloqsd daemon. If
the particular system runs Windows 2000 or NT and is intended to act
as a HP Eloquence data base and/or application server this cabinet must
- contains the core on-line documentation and release notes and should be
installed along with the client_runtime and/or client_developer cabinet
- contains the entire manual set in HTML format. Since these are a lot
of small files you should consider to install this cabinet in a central
location and integrate it into your intranet web server's document
- contains the entire manual set in PDF format to be viewed with the
Adobe Acrobat Reader (TM) which is freely available on the internet
In a complete installation, the three client cabinets are installed as well
as the doc_html cabinet. On Windows 2000 or NT, the server cabinet is
additionally installed. The manuals are not installed unless you choose
a customized installation and select them manually.
3) On Windows 2000 or NT, please ensure you have administrative capabilities.
4) If you have a previous HP Eloquence A.06.30 beta release installed, please
uninstall it first (Start Menu -> Settings -> Add/Remove Programs). If this
does not succeed, try the installation program of the previous beta release.
If this does not work at all, please refer to the Known Problems section
However, if you have HP Eloquence A.06.00, A.06.10 or A.06.20 installed,
a prior uninstallation is not necessary. You should choose a customized
installation and make sure you install A.06.30 into your previous HP
Eloquence installation directory.
In any case, your previous configuration files are not overwritten by the
HP Eloquence A.06.30 installation process.
5) Now start the setup executable which reflects your operating system
and follow the installation instructions.
6) After installation on Windows 2000 or NT, an A.06.30 license key is required
in order to use the HP Eloquence server components. During installation, a
temporary license key is generated on demand which is valid until 30 days
For your convenience we provide a temporary license key which is valid until
the end of April 2000:
B1368B A.06.30 none 100-3-1 100-4-30 0 debfcc5bac0a635720124a6695276b3f
Please visit the HP Eloquence Web site at
for details about ordering a permanent HP Eloquence license key.
Your license file is located in the "etc" subdirectory of your HP Eloquence
installation, for example at
C:\Program Files\Hewlett-Packard\HP Eloquence\etc\license.
Please comment out the previous license key when adding the new A.06.30
license key to your license file. Otherwise the new license may not be
recognized and chklic might output the following messages:
A.06.20: Bad license key revision.
Duplicate sequence number: Ignoring license
If you're using the HP Eloquence Personal Edition, please use the license
template file "license.sam", it contains an updated license key for the HP
Eloquence Personal Edition. The file is located in the "etc" subdirectory
of your HP Eloquence installation and should be copied into the "license"
file located in the same directory.
If you detect any problem not listed here please send us a message either by
e-mail (firstname.lastname@example.org) or fax (+49-202-2431-420). Thank you.
* If you do not succeed to uninstall a previous HP Eloquence A.06.30 beta
release it is necessary to manually clean-up the Windows Installer data base:
1) Open the "Installer" subdirectory inside your Windows installation
directory (for example C:\Windows\Installer).
2) In this "Installer" subdirectory, please delete the subdirectory which is
3) For each .msi file in the "Installer" subdirectory, you should find out if
it is related to HP Eloquence by starting it with a doubleclick and wait
until the first dialog window appears. If this is a "HP Eloquence A.06.30
Setup" window, immediately click the "Cancel" button and delete the file.
If it is not, immediately click the "Cancel" button and proceed with the
next .msi file.
4) Finally, start the new HP Eloquence A.06.30 setup executable as explained
above and use the "Remove" option to uninstall the previous beta release.
This should now succeed. Afterwards, start it again to install the new
5) If this does not succeed which we have experienced in rare cases it is
necessary to manually remove all references to the previous beta release
from the Windows registry. To do this, open the "Run" dialog from the
start menu and execute "regedit". In the "Edit" menu choose "Find" and
search for "355A0BB2B9AC3D1118300001A5CB964D" (without the quotes) in
all keys, values and data. Then delete each occurrence which is found.
* This distribution contains patch PE63-0006020 as of 2000-06-02 which solves
a problem with the eloqdb6 data base server (see below).
* With the server cabinet as of 2000-03-24, the eloqdb6 data base server
crashed immediately after start-up. This has been solved with the current
* All known problems which occurred during installation before 2000-03-08 have
disappeared just because the installer engine was replaced by the most
current one. We found out that since the Microsoft Windows Installer is a
new technology the first releases of the accompanying installer tool kits
had several problems which unfortunately affected our early beta releases.
* After installation of the client_runtime cabinet on Windows 2000 it was not
possible to locally execute or even list or edit any HP Eloquence character
mode program since eloqcore did not display correctly on the Windows console.
The problem was related to a different screen buffer default size on Windows
2000 and has been solved with the current release.
* With the client_developer cabinet, the HP Eloquence IDE dialog plug-in
modules were not installed. This has been solved with the current release.
* During the product registration phase in former A.06.30 installations, an
error 1406 occurred. This has been solved with the current release.
Patch PE63-0006020 (eloqdb6 data base server)
* A problem related to rollback of subtransactions was solved.
Depending on data base usage this could result in btree corruption
or an eloqdb6 server panic.
When a subtransaction was rolled back but the main transaction
continued it could happen that invalidated btree information
remained in memory and was used by subsequent btree operations.
This problem could only happen when using transactions.
- Assertion failed: f_bhp->id.node_id == node_id
server panic: Aborting on internal failure, file mpool.c, line 392
- DBPUT failed due to duplicate secondary index
- dbfsck reports corrupted btree pages
A data base which shows the symptoms above must be reloaded (dbexport,
dberase and dbimport). Information besides internal btree is not
* The eloqdb6 server could panic during processing volume recovery
complaining about a buffer leak. This was caused by a bug
processing defective recovery information from the log volume.
* Cache buffer management has been tuned to provide better performance
for delete and update operations in a transaction. This should also
improve the impact of transactions on concurrent read operations.
Your HP Eloquence Team