Notes for Environment 6.17 -- 15 Apr 2012 ----------------------------------------- All installations: ------------------ SCD Installations: ------------------ For installation instructions, see manual M86-E02087 APEX2 and PROTEUM2 Installation Notes. This manual covers installation for new or existing (upgrade) systems to either APEX2 or PROTEUM2 software suite. Note: The Bruker SCD CD does not check that either the Bruker Environment CD was installed nor the PATH environment variable is correct. These must be correct before installing BrukerSuite*.exe XRD Installations: ------------------ For installation instructions, see manual M86-E05084 PILOT Install Notes. This manual covers installation for new or existing (upgrade) systems to either standard or 21 CFR Part 11 PILOT installations. Note: The Bruker PILOT CD will check that the Bruker Environment CD was already installed and that the PATH environment variable is correct. If not, an appropriate message is displayed. Environment 6.17 requires: --------------------------- - Windows-7 or Windows-XP [PostgreSQL installer limited to XP or later]. - 32-bit or 64-bit editions. - Professional edition is the only version tested by Bruker. - Recommend latest service packs and security patches. V6.17 Release Notes: -------------------- * PostgreSQL is patched against the "could not reattach to shared memory" bug. V6.15 Release Notes: -------------------- V6.14 Release Notes: -------------------- V6.8 Release Notes: ------------------- * This release changes the name of the PostgreSQL server daemon account from BrukerDb to brukerdb. Newer Linux distributions no longer allow upper case characters in user and group names. The change is backward compatible to older installations that use the former spelling. * The PvAPI library from Allied Vision Technologies has been added. It allows communication with AVT GigE Vision cameras. V6.7 Release Notes: ------------------- * This release ensures that the Python interpreter loads the OpenSSL DLLs that come with the Python environment. Otherwise, if an incompatible version of LIBEAY32.DLL or SSLEAY32.DLL is installed in the Windows system directory, Python will be unable to communicate with the PostgreSQL database. * OpenCV has been updated to v2.1.0 and for the first time the header files and import libraries for OpenCV are included with the Python environment. * The pycbf package for reading and writing CBF/imgCIF diffraction images has been added. [Added pycbf v0.8.1.] * Added the pycbf documentation to the Qt Assistant. V6.6 Release Notes: ------------------- * This release contains a number of changes to make the Python environment compatible with Windows 7 (32 bit and 64 bit). V6.5 Release Notes: ------------------- Below is a list of changes. (L) refers to the Linux version only. * This release fixed an incorrect dependency with the termcap library under Linux that prevented straight forward installation on systems that were missing this library. There is no need for Windows users to update to v6.5 because it is identical to v6.4. Changes in v6.5 of the Python environment: =============================== * PostgreSQL v8.3.6 was compiled with readline support, which caused problems when the Python environment was installed on a Linux system that did not have the termcap library installed. (L) V6.4 Release Notes: ------------------- Below is a list of changes. (W) refers to the Windows version only. Changes in v6.4 of the Python environment: =============================== * Updated to PostgreSQL v8.3.6. * Added cx_Oracle v4.4.1 for Oracle 10g. * Added the "keramik" style from KDE v3.5.10. * The PostgreSQL service account is now switched from BrukerPostgreSQL to LocalSystem. The internal LocalSystem account is not susceptible to interferences from the domain, which can deny the log on as a service right from the BrukerPostgreSQL account, the consequence of which is that after a reboot the PostgreSQL service might no longer start automatically. The BrukerPostgreSQL account is still needed during installation because the PostgreSQL installer needs to log on as that user, which is not possible with LocalSystem. (W) V6.3 Release Notes: ------------------- Below is a list of changes. (L) refers to the Linux version only. * This release fixes a problem with NVIDIA OpenGL drivers under Linux. There is no need for Windows users to update to v6.3 because it is identical to v6.2. Changes in v6.3 of the Python environment: =============================== * The GLUT extension in PyOpenGL is now explicitly linked against the Xxf86vm library. This is necessary to make the Python Environment compatible with NVIDIA's OpenGL driver, which is not linked against this library and which causes an error when GLUT is imported in Python due to unresolved symbols. (L) V6.2 Release Notes: ------------------- * This release adds the OpenCV library to the Python environment. Changes in v6.2 of the Python environment: =============================== * Added OpenCV v1.1pre1a. Added the OpenCV documentation to the Qt Assistant. V6.1 Release Notes: ------------------- Below is a list of changes. (W) refers to the Windows versions only. * This release fixes a DLL mismatch between Python and PostgreSQL under Windows. Changes in v6.1 of the Python environment: =============================== * Updated to OpenSSL v0.9.8e. This is the same version of OpenSSL as is used by the precompiled PostgreSQL v8.3.4 under Windows. A version mismatch between the OpenSSL DLLs caused an error during database updates ("The ordinal 284 could not be located in the dynamic link library SSLEAY32.dll"). V6.0 Release Notes: ------------------- Below is a list of changes. (W) refers to the Windows versions only. * The primary change in this release is the update to PostgreSQL v8.3.4 and the transition of the character encoding scheme for the database from ASCII to UTF8. Both changes were requested by the ALASKA project. For older databases, which are migrated during the installation process, the recoding of strings from ASCII to UTF8 takes place as part of the migration. The conversion can potentially cause problems if the older database uses ASCII characters from the 128 to 255 range. In places where this is likely to happen, such as the sample notes, our client applications use pickled strings to prevent this problem. The PostgreSQL driver we used in the past to connect to the database from Python, pyPgSQL, is no longer compatible with PostgreSQL v8.3.4. As a consequence, pyPgSQL has been replaced with PyGreSQL. My tests show that as an additional benefit, PyGreSQL is about 6% faster than pyPgSQL. This switch between drivers means that Python environment v6.0 will not be compatible with Bruker Suite v2008.5 and older. * The Python environment for Linux is now compiled under Fedora Core 6 after my old SuSE 7.3 box has finally ceased to exist. The FC6 build is linked against libreadline.so.5 to make installation on current Linux distributions easier. FC3 users have to install readline-5.0-3.i386.rpm from the FC4 distribution to become forward compatible (note that readline-4.3 and readline-5.0 need to be installed side by side in this case which requires the use of the --force parameter with the rpm installer). Support for Red Hat 8.0 has been discontinued. Changes in v6.0 of the Python environment: =============================== * Updated to PostgreSQL v8.3.4. * Removed pyPgSQL because it is incompatible with PostgreSQL v8.3.4. Because of this, Bruker Suite before v2008.6 is incompatible with Python environment v6.0. (W) * Added PyGreSQL v3.8.1 as a replacement for pyPgSQL. (W) * Changed the character encoding scheme for the BAXSdb database to UTF8. * The database migration process now grants all privileges on schemas in the BAXSdb database to the Bruker role. * The BAXSdb database now has its own tablespace named BAXSts. The user is prompted for the location of the tablespace as part of the installation process. The default location of the tablespace is on the same level as the default tablespace. (W) * The Bruker PostgreSQL installer now creates the tablespaces in "%CommonAppData%\Bruker AXS". For a typical U.S. Windows XP this is "C:\Documents and Settings\All Users\Application Data\Bruker AXS". The location of the tablespaces for the Python environment installer has not changed. (W) * The PostgreSQL installer is now executed with a modeless dialog, i.e. the dialog no longer has a Cancel button. (W) * The Python environment is now linked against libreadline.so.5 to make installation on current Linux distributions easier. The new Python environment installs readily under Fedora 8 and Fedora Core 6. Fedora Core 3 users have to install readline-5.0-3.i386.rpm from Fedora Core 4 to become forward compatible (note that readline-4.3 and readline-5.0 need to be installed side by side in this case which requires the use of the --force parameter with the rpm installer). Support for the Red Hat 8.0 distribution has been discontinued. (L) * Change the security context of libraries with text relocations so that SELinux permits their execution. (L) * The bnrun script now supports the -v command line switch. (L) Notes for Environment 5.4 -- 18 July 2008 ----------------------------------------- All installations: ------------------ There is a known issue when installing bnpython4.5.exe off a CDROM and under Windows-2000. Sometimes the PATH environment variable does not get updated for the Python folders. When this happens, please add the following to your PATH (see Control Panel > System > Advanced > Environment Variables): ;C:\bn;C:\bn\Python23;C:\bn\Python23\DLLs;C:\bn\Python23\Lib\site-packages\win32\lib Usually, you append this string to your PATH under "System variables". All installations: ------------------ "Failed to set permissions on the installed files." Bruker has seen this error on a few computers. While the cause of this error is still unknown, we have successfully fixed the installation by using Windows Explorer: 1) Highlight your C: drive on left pane. 2) Tools > Folder Options, then View tab. 3) Scroll to the bottom. 4) Uncheck "Use simple file sharing (Recommended)". 5) Navigate to C:\bn\data-8.0. 6) Set the ownership to ?. SCD Installations: ------------------ For installation instructions, see manual M86-E02087 APEX2 and PROTEUM2 Installation Notes. This manual covers installation for new or existing (upgrade) systems to either APEX2 or PROTEUM2 software suite. Note: The Bruker SCD CD does not check that either the Bruker Environment CD was installed nor the PATH environment variable is correct. These must be correct before installing BrukerSuite*.exe XRD Installations: ------------------ For installation instructions, see manual M86-E05084 PILOT Install Notes. This manual covers installation for new or existing (upgrade) systems to either standard or 21 CFR Part 11 PILOT installations. Note: The Bruker PILOT CD will check that the Bruker Environment CD was already installed and that the PATH environment variable is correct. If not, an appropriate message is displayed. Environment 5.4 requires: --------------------------- - Windows-XP [Windows-2000 PostgreSQL installer limited to XP or later]. - Recommend latest service packs and security patches. V5.4 Release Notes: ------------------- Below is a list of changes. (W) refers to the Windows versions only. * The PostgreSQL 8.2 service needs to be stopped explicitly before the database can be uninstalled. With PostgreSQL 8.0, the uninstaller stopped the service automatically. With PostgreSQL 8.2, if the service is not stopped, the following error occurs: "The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2803." (W) * The PostgreSQL database can now be installed in a location that contains whitespace characters in its path. (W) * The default install location for the Bruker PostgreSQL installer has been changed to the Program Files directory. The install location for the Python Environment is unchanged. (W) * If the InnoSetup installer is running in silent mode, i.e. was started with the /VERYSILENT command line parameter, then the PostgreSQL installer is now running in silent mode as well. (W) * The Bruker PostgreSQL installer encountered a "list index out of bounds" error if the Python Environment was installed without the database. (W) * The batch file that runs Epydoc called the wrong (and actually not existing) Python module. (W) V5.3 Release Notes: ------------------- * This release fixes a problem with too long passwords under Windows. Some Windows computers enforce the maximum password length of 14 characters as required by the LAN Manager 2.0 standard from 1990. (W) * The Bruker user/group/role in the database did not have the right to log in, which prevented users logged into the operating system as Bruker from using the database. (W) Below is a list of changes. (W) refers to the Windows versions only. * The password for the database service account is now truncated to 14 characters if the account is created by the installer. This prevents problems on those Windows computers whose password policy enforces a maximum password length of 14 characters, as required by the LAN Manager 2.0 standard. (W) * The Bruker group/role did not have the login right, i.e. when logged into the operating system as Bruker, the user did not have access to the database. (W) * The SEATTLEHOME environment variable is no longer created in the user settings but only in the system settings. (W) V5.2 Release Notes: ------------------- This release fixes a bug in the Windows installer that corrupted the system and user paths by replacing all space characters with semicolons. Below is a list of changes. (W) refers to the Windows versions only. * The installer corrupted the path by replacing all spaces with semicolons unless they were surrounded by quotes. (W) * All Python and PostgreSQL paths are now put exclusively in the system path. The user path is no longer modified. (W) * The installer tried to recreate the database service account even when that was not necessary. (W) V5.1 Release Notes: ------------------- The primary change in this release is that the database service account in the Windows installer is now created in the last step before the actual installation of the Python environment takes place. There had been serious incidences before, where a user destroyed an existing installation simply by moving back and forth between installer pages or by exiting from the installer. This problem still exists if the user cancels once the installation process has started. Below is a list of changes. (W) refers to the Windows versions only. * The database service account is now created in the last step before the actual installation of the Python environment takes place. There had been serious incidences before, where a user destroyed an existing installation simply by moving back and forth between installer pages or by exiting from the installer. This problem still exists if the user cancels once the installation process has started. (W) * The database contents is downloaded for migration only once now, even if the user moves back and forth between installer pages. (W) * Allowed the separate PostgreSQL installer to run on 64-bit architectures. (W) V5.0 Release Notes: ------------------- The primary change in this release is the update to PostgreSQL v8.2.6 and the introduction of a stand-alone database installer for Windows. The latter is part of the ALASKA project which requires a database server that should be compatible to the Python environment. Special emphasis has been put on the compatibility between the installers for the Python environment and the stand-alone database (from hereon called the PostgreSQL installer). For example, the Python environment installer will not offer to install the database if the PostgreSQL installer has already done so. Similarly, the PostgreSQL installer will refuse to run if the database has already been installed with the Python environment. This means that database updates on a system whose database was originally installed with the Python environment have to be made with a newer version of the Python environment and not the PostgreSQL installer. The opposite is true if the database was originally installed with the PostgreSQL installer. Please note that for implementing these compatibility checks between installers it was necessary to limit the PostgreSQL installer to Windows XP and later. The Python environment installer may still be used under Windows 2000 and later. Below is a list of changes. (W) refers to the Windows versions only. * Updated to PostgreSQL v8.2.6. * Added a separate PostgreSQL installer that does not install the Python interpreter and libraries. (W) * The installer now ensures that the path to the destination location does not contain space characters. (W) * The command line interface for Epydoc now accepts more than nine parameters. Some common and benign warning messages are now filtered out. (W)