Updated September 2001 SECURITY NOTICE =============== SilverPlatter has detected a possible security exploit in the WebAdmin software that is installed with this server release. Contact support@silverplatter.com for details on securing your system. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Release Notes for the general release of ERL v4.11 for Windows NT and Windows 2000 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ========================= About these Release Notes ========================= These Release Notes should be read together with the ERL Administrator's Manual, which is available in PDF format on the ftp site, or from the SilverPlatter web site: http://www.silverplatter.com It is also available as a set of HTML files, for viewing with a browser. The ERL Administrator's Manual contains full details of how to install and configure ERL v4.11. These Release Notes contain the following additional information (along with other items listed in the Contents): * Information that is specific to the Windows NT or Windows 2000 platform, but has not yet been included in the ERL v4.11 Administrator's Manual. * Any other, late-breaking information about ERL v4.11 that has not yet been included in the ERL v4.11 Administrator's Manual. * Details of features that are new or are changed in this release. * Details of known issues in this release. *** IMPORTANT NOTICE *** Sites using ERL 4.11 with Silverlinker must first unmount and remove any SilverLinker database already installed. When you have upgraded to ERL v4.11 you must install either update SLNK078W or higher, or the monthly update SLNK0019 or higher. Earlier versions of SilverLinker database will not work correctly with ERL v4.11. Once you have ERL v4.11 and the SilverLinker database installed, it is important that whenever you update the SilverLinker database you install the new database before you uninstall the old one, to ensure that links are always available. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Contents =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 1. System Requirements 2. Downloading the software and the ERL 4.11 Administrator's Manual 3. Installing and Running ERL v4.11: Additional information for Windows NT/2000 4. Late-breaking information about ERL v4.11 5. New Features and Changes in this release 6. Known Issues and Points to Note on Windows NT/2000 7. Contacting SilverPlatter Technical Support =-=-=-=-=-=-=-=-=-=-=- 1. System Requirements =-=-=-=-=-=-=-=-=-=-=- This release requires one of the following platforms: Solaris 2.6 or 7, AIX 4.2 or 4.3, NT 4.0 with Service pack 6, Windows 2000, Red Hat Linux 6.0 and 6.1. One set of Release Notes is available for the Windows NT and Windows 2000 version (these release notes), and one set for the other platforms. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 2. Downloading the software and the ERL v4.11 Administrator's Manual =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- If you have not yet got a copy of the ERL v4.11 software, and ERL v4.11 Administrator's Manual, this is how you download them: Downloading with a web browser: ------------------------------- 1. Access the software download page on the SilverPlatter web site; http://www.silverplatter.com/support/registration.html 2. Choose the ERL dbserver 4.11 check box and select your platform from the drop-down menu. 3. Fill in the registration details, and click Submit Request. 4. The download package contains the following files: The compressed software (erlsrvr.exe). The release notes (readme.txt) (this document) The ERL Administrator's Guide (erlmn411.pdf) Downloading using ftp: ---------------------- 1. Use anonymous ftp to connect to SilverPlatter's site: ftp.silverplatter.com 2. Login with user-id anonymous and enter your email address as a password. 3. Change to the /software/erl-server directory. (To do this, enter cd/software/erl-server) 4. Change to the directory for the platform you will use for the ERL Server. 5. Make sure you will download the files as binary files. (To do this, enter bin) 6. Download all the files from the directory. (To do this, enter mget *. You are prompted to enter y to download each file.) The files will download into whatever is your local directory. The files are: The compressed software (erlsrvr.exe.) The release notes (readme.txt) (this document) The ERL Administrator's Guide (erlmn411.pdf) Note: Before you install the ERL v4.11 Server software, contact your local distributor or SilverPlatter Information to obtain the ERL Server ID and database license sheets that you need. Note: WinSPIRS 2.0 is no longer supported by SilverPlatter. ERL v4.0 and later only work with WinSPIRS 2.1 or later. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 3. Installing and Running ERL v4.11: Additional information for Windows NT/2000 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Full details of the hardware requirements for installing and running ERL v4.11 are given on the SilverPlatter web site: http://www.silverplatter.com/erl/erlserverreq.htm Full details of how to install the ERL v4.11 software are given in Chapter 2 of the ERL Administrator's Manual (erl411mn.pdf), but you should also note the following points: Upgrading to ERL 4.11 --------------------- * The ERL Server v4.11 software has been designed to replace ERL Server v2.x and ERL Server v4.0x. * If you are upgrading from ERL v4.0, you do not need to perform a system backup, or export your statistics, but you must uninstall ERL v4.0x and then install ERL v4.11. All your databases and data files will be preserved, but you should note the known limitation (detailed below) that the admin password is reset to "admin" when you upgrade. Be sure to change your admin password when the software installation completes. * Statistics from an ERL v4.x server are automatically converted to the new statistics format when you install ERL 4.05 and later. If you are upgrading from a version of ERL that is earlier than 4.0 you must perform a system backup and export any statistics before you install ERL 4.11, if you want to retain old statistics files. * Instructions for uninstalling software, and making a system backup are included in Chapter 2 of the ERL v4.11 Administrator's Manual. * Sites using ERL 4.11 with Silverlinker must first unmount and remove any SilverLinker database already installed. When you have upgraded to ERL v4.11 you must install either update SLNK078W or higher, or the monthly update SLNK0019 or higher. Earlier versions of SilverLinker database will not work correctly with ERL v4.11. Untarring Tapes --------------- The programs tar.exe and mt.exe are located in the \sproot\bin directory. You can use them to extract the contents of tar tapes. Included is the how2tar.txt file that provides more information about the tar command. Listing the Contents of a Tar Tape ------------------------------------- To list the contents of a tar tape type the following: tar -L \\.\tape0 The -L (Long Listing) option displays the contents in detail. In Windows NT, the tape device is \\.\tape0. If you have more than one tape device, the others are called \\.\tape1, \\.\tape2, etc. Untarring the Tape Contents ------------------------------ If you can list the contents of the tar tape, you can extract it with the following command, adding the -x (Extract) option: tar -Lx \\.\tape0 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 4. Late-breaking information about ERL v4.11 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Please note that the ERL Administrator's Manual has not been updated to include the Windows 2000 platform. References to Windows NT are also applicable to Windows 2000. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 5. New Features and Changes in this release =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Changes made in version 4.11 of ERL =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ----------------------- Changes in the software ----------------------- ERL v4.11 has the following new features: * You install the server software and the administration utilities from one package, which now contains the following items: * The ERL server software. * The WebAdmin software, and its associated Administration Server. The ERL Administration Server is a web server configured to allow you to run WebAdmin from a supported web browser from any location, over the Internet, by logging onto the server where ERL and WebAdmin are installed. You now access WebAdmin by entering the following URL in your browser: http://server_name:4416/webadmin/ * brladmin, the SilverPlatter tool that lets you make changes to ERL in batch mode. (For more information about brladmin, see the documentation (brlman) which is put into the brladmin destination directory when you install the software.) * ERL v4.11 supports SilverLinker 2, the latest release of SilverPlatter's solution for linking to electronic full-text articles. These articles could be available remotely, hosted at the site of a service provider (a publisher or subscription agent); but an additional feature of SilverLinker 2 is that we are working with service providers so that SilverLinker can link to articles that are available locally, in the form of a locally-hosted collection supplied by the service provider. We have already reached an agreement so that SilverLinker can work with ScienceDirect OnSite (using ScienceServer 3.1 or above), which offers local storage of all, or a selection of, Elsevier Science's journals in electronic form. Please note that you should contact your local ScienceServer technical support representative for assistance with ScienceServer. If you subscribe to Elsevier Science's journals in electronic form, but you do not make use of ScienceDirect OnSite, please contact SilverPlatter Technical Support for further assistance. * The WebAdmin user "guest administrator" can now view all screens in WebAdmin, but cannot create new entries or change (or delete) existing ones, with the following two exceptions: * They can set up and edit SilverLinker filters. This means you can share the responsibility for creating and maintaining filters by giving several members of staff the necessary permissions. * They can create and run statistical reports, save these to their account, and edit or delete the reports that they create. * Configurable automatic notification of imminent database expiry. The ERL administrator can specify the period prior to expiry and the e-mail address of the recipient of the expiry notice. * This release includes significant performance improvements for searches involving the explosion of thesaurus terms in those cases where "pre-explosions" have been calculated. * Key bug fixes. ----------------------------------- Problems Corrected in this Release: ----------------------------------- (Please note that some of these items refer to problems in the beta release, which have now been corrected.) Database Menu headings ---------------------- The problem with tiered subheadings not appearing in a database menu has now been fixed. (8285) Allow password modification --------------------------- The problem where setting Allow Password Modification to off for a user account still caused the client to prompt and accept a new password does not occur in this release. (9339) Incorrect address logging following WebAdmin relogin ---------------------------------------------------- The problem where the gateway IP address was logged after a WebAdmin relogin (whereas the client IP address is logged on the first login) has been fixed. (10151) Lists in WebAdmin not adjusted after deletion --------------------------------------------- A WebAdmin problem, where deleting all of the Accounts, Portfolios, or Statistical Reports from a list page displayed a blank page instead of the remaining section of the list, has been fixed. (8270) Statistics reports display correctly in WebAdmin ------------------------------------------------ A problem with displaying statistical reports in WebAdmin has been fixed. (10019) Incorrect counting of rejected logins ------------------------------------- If a user login is rejected (for example, where one or more database is unavailable because all licenses are in use), this is now logged as a single rejected login. (Previous versions of ERL logged a rejected login for each database that the user was trying to access.) (10676, 10677, 10678) Statistical reports include Account Description and Reference fields ------------------------------------------------------------------- Statistical reports created in WebAdmin and brladmin include Account Description and Account Reference fields. (10552) Color coding in WebAdmin publication lists correct -------------------------------------------------- The color coding in the publication lists is now as stated in the online help. The color red denotes that a publication is new in the last 30 days. The color blue denotes that information about a publication has changed. (10753 and 10754) Displaying the SilverLinker icon -------------------------------- A problem that meant that in certain circumstances the SilverLinker icon did not appear on the Database Selection page, although SilverLinker links were available, has been fixed. (10776) --------------------------------- Changes to the User Documentation --------------------------------- General ------- The ERL Administrator's Manual has been revised for the General Release. The structure remains the same, but it includes more information, particularly about installation, administration tools, and SilverLinker. This is available as a PDF file (to read it you will need the Adobe Acrobat Reader). You can use the Reader's search facility for full text searching, and the Table of Contents entries are links to the relevant sections of the Manual. The Manual is also available as a set of HTML files, for reading in a browser. References to the Windows NT platform should be taken as applicable to Windows 2000. WebAdmin -------- WebAdmin has fully context-sensitive online help, which has been revised for this release. It now includes an overview of the tasks you can carry out in WebAdmin (accessed through the Help Table of Contents) and “pop-up” definitions of glossary terms (available by clicking on text in green). Addition to the brladmin Reference Manual ----------------------------------------- At section 8.2.7:Commands Concerned with Users the following items should be added to the table headed "Value|Description": Value Description ----- ----------- 00000008 Allow user to set or alter SilverLinker filters for themselves 00000004 Allow SDIs (not currently implemented) 00000002 Allow Alerts (not currently implemented) 00000001 Allow user to access own statistics =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 6. Known Issues and Points to Note =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- General ======= If you start the server or mount or unmount a database when the network drive containing the installed databases is unavailable for any reason, and you have the SilverLinker database installed on that drive, the dblbuild process may fail to complete. This means one or more databases may not be visible to users. The solution is to shut down the server, make sure that the drive is available, and then restart the server. (10773) * When searching with the MEDLINE Advanced thesaurus, users who select and explode pre-exploded MeSH terms may very occasionally retrieve extra records with hits that are outside the MeSH field. This will be addressed in the next MEDLINE Advanced re-build. Platform Specific Points to Note ================================ Calculation of available RAM on Windows 2000 -------------------------------------------- Windows 2000 uses more resources for the operating system than Windows NT 4.0. However, the 4.11 server calculates available RAM using the method used for NT 4.0. If you specify a number of logins which the server calculates is too high for the available RAM a message is displayed. In this case, you need to reduce the number of suggested logins by 10 to 20 and specify this as the maximum. Stopping the Server service from the Windows 2000 Service Control Panel ----------------------------------------------------------------------- causes an error dialog ---------------------- The following error dialog is displayed if you stop the Server from the Windows 2000 Service Control Panel: Error 1067: The process terminated unexpectedly The process does actually shut down correctly, and can be restarted using either the Service Control Panel, or the dbserver -m command in a terminal. However, any subsequent dbserver -remove command will not completely remove the service, but will leave it in a Disabled state, only removable by rebooting the server. (10829) Cannot print the Licence Agreement when using Windows 2000 ---------------------------------------------------------- As it is not possible to print from the Dos prompt in Windows 2000 it is not possible to print the Software Licence Agreement. Running from domain account --------------------------- To run ERL as a service using a domain user account when ERL is not located on a domain controller: 1. As an administrator on the machine where ERL is located, add the user \ to the administrator's group on that local machine. 2. Click on the Services icon in the Control Panel folder and select the ERL Server 4.11. 3. Then select the Startup button and change the logon account to \, and enter this account's password where indicated. Click OK. 4. Back in the Services Menu, select the Start button. (9201) DBINSTALL ^C needs reboot ------------------------- If you use ^C to exit DBINSTALL or to stop output with --more-- prompts, an error may occur that requires a reboot. (8728,8729) Default timeout reverts with upgrade ------------------------------------ If you specified a new default timeout for v2.11, when you upgrade to v4.11, the default timeout goes back to the original value. Set a new default timeout for 4.11, if desired. (8640) WebSPIRS slow when loading databases on server ---------------------------------------------- Installing databases on an ERL v4.11 server on Windows NT/2000 may consume system resources such that client response can be very slow. We recommend that you only load databases during low usage periods. (8685) Databases installed on Windows NT/2000 -------------------------------------- If you install databases on Windows NT/2000 magnetically, or by magnetic link, remove the CD from the CDROM drive before you mount the database. Incorrect naming of statsplit file in some circumstances -------------------------------------------------------- We are aware that where dbserver is installed on a Windows NT/2000 server running on GMT, or a time zone in advance of GMT, the statsplit occurs correctly at 00.00 at the beginning of a new month, but the filename is for the last day of the previous month. (10168) Points to note when carrying out administrative tasks: ====================================================== Portfolios ---------- Do not delete portfolios with active users. Check to ensure all users in a portfolio are logged off before deleting it. Admin Password is reset with upgrade ------------------------------------ If you changed the admin password in v2.x, when you upgrade to v4.0x and later, the admin password goes back to the default "admin". (8906) Mounting databases ------------------ When mounting databases installed as CDROM, the ERL server software will prompt you to place the database (CDROM or DVD) in the first available drive. If you are mounting a DVD disc, the software may prompt you to place the DVD in a CDROM Drive. This situation can be avoided by making the first available drive be a DVD drive. You may also place the DVD in the appropriate drive and then use "auto" mount option to mount the disc. (8389) Licenses with blank site names cannot be entered manually --------------------------------------------------------- If a license contains a blank site name it cannot be entered manually, it must be entered as a file. (9343) Retrieval client problems when used with ERL Server v4.11 --------------------------------------------------------- When displaying Default and Hits fields or CITN and Hits fields, Hits fields display out of order. (8058) Verify Database Integrity doesn't work for magnetic links --------------------------------------------------------- If you install a database as a magnetic link, Verify Database Integrity doesn't accurately report problems with the database. (8077) Verify Database Integrity doesn't fix bad files ----------------------------------------------- If you magnetically install a database and then delete or rename a file in the \nodes directory, when you verify database integrity (#5 on the Install Menu), it reports the missing file but does not offer a way to correct it. (8564) "unknown" connections left behind --------------------------------- We are aware of a problem that can occur with multiple servers. If you have two or more ERL servers listed in the erlclnt.cfg file, logging on to one of the servers from a client can create an "unknown" connection on the other server. That connection remains until the user logs out. However, if the server times the user out, the connection remains until the server is restarted. (9903) Statistics: Points To Note ========================== Statistics for ERL v4.05 and later are more detailed than for ERL v2.x and, as a result, 4.05 and later statistics files are larger than 2.x statistics files. Most statistics reports are CPU intensive and should generally be run when your server is not busy. Browsing Index in WinSPIRS doesn't increase searches stat --------------------------------------------------------- When browsing the Index in WinSPIRS and looking at displayed records but not specifically performing a search, the TOTALRECS stat is incremented but the SEARCHES stat is not. (8380) Rejected Logins statistics -------------------------- Rejected logins refer to logins rejected due to license or portfolio constraints. Portfolios do not appear as part of the rejected logins information because databases can be listed in several portfolios that a user has access to. (8631, 8741) TOTALRECS statistic ------------------- When you look at statistics, you should be aware that the TOTALRECS number is the total number of records the client has requested from the server. A caching factor that depends on the number of records displayed in the client means that TOTALRECS is not necessarily the same as the number of records the user has seen. (10715) WebAdmin: Points To Note ======================== Starting the ERL Administration Server -------------------------------------- After you have started your ERL 4.11 server you may have problems starting the ERL Administration Server component. On UNIX, you may see the message: /sproot/apache/bin/apachectl start: httpd could not be started On NT, the service for the ERL administration server fails to start. It is also possible that you are able to access the WebAdmin login page, but when you click the Login button, the browser tries to open a URL starting with: localhost.localdomain or returns the message: document contains no data In all of these cases the problem probably occurs because the DNS is not working, or is not set up to work with this ERL server. The solution is to edit the /sproot/apache/bin/httpd.conf file to specify the IP address that WebAdmin uses to create self-referencing URLs. To do this, add the following tag to the httpd.conf file, to specify the numeric IP address of the server: ServerName 123.45.67.89 Users new to WebAdmin should note that the default username and password for the administrator to log into WebAdmin is admin/admin. Some publications missing in WebAdmin ------------------------------------- If you view the publications for the NRC or Project Muse services you may find that some are missing and that instead one or more blank lines are displayed. Consequently you will not be able to exclude these publications for any of your users. Session timeout may not always work ----------------------------------- Session timeout may not consistently disconnect a WebAdmin connection that has been inactive for the time specified. If the session timeout is set to the default of 30 minutes, the timeout is consistent. (8845) Problem using WebAdmin to change the database menu -------------------------------------------------- If you have edited your dbmenu.cfg file manually in the past, you may have problems saving the file when you edit it in WebAdmin. The solution is to start with a new dbmenu.cfg file that has not been edited manually: 1. Make a clean copy of dbmenu.cfg by copying /sproot/cfiles/dbmenu.eg to /sproot/cfiles/dbmenu.cfg 2. In WebAdmin, create 1 new heading with WebAdmin. 3. Remove all the redundant default headers that are by default in dbmenu.eg. 4. Continue to build the dbmenu.cfg file as you wish. Viewing the dbmenu.cfg file --------------------------- If you use Notepad (or WordPad) to view or edit a dbmenu.cfg file that was created or edited in WebAdmin with the server running on NT, you must have word wrap ON to see the file formatted correctly. If you create or edit a dbmenu.cfg file in WebAdmin with the server running on UNIX, and you transfer the file to a PC using FTP in text mode, the file displays correctly in Notepad, or any other editor. EC_BADKEY error --------------- If a WebAdmin user attempts to connect to the server before any databases have been installed, the dbserver reports an EC_BADKEY error. (9323) Database Menu headings need to be unique ---------------------------------------- Database Menu headings need not be unique, though this is enforced by the current release of WebAdmin. You can work around this by manually editing the dbmenu.cfg file that belongs to your ERL server. (8706) Empty Statistical Report window ------------------------------- Minimizing a Statistical Report window may cause it to display no content when it is restored. In this case, reload or refresh the screen. (8155) Database Menu headings cannot contain certain characters -------------------------------------------------------- Currently WebAdmin does not allow you to use the characters, * (asterisk), + (plus sign) or | (pipe symbol) when defining a database menu heading. In addition, you should not use HTML markup in the heading name as this can cause unexpected results and may even cause WebAdmin to stop functioning. (9258) Using vertical bars (|) in user accounts ---------------------------------------- WebAdmin uses a vertical bar | (pipe symbol) as a field delimiter. This means there is a problem if you use accounts that include the | in the description or reference fields, and try to edit those accounts in WebAdmin. If you intend to edit user accounts in WebAdmin, we recommend you amend them so that they no longer contain the |. (10770) Editing a downloaded list of publications ----------------------------------------- When you download a list of publications from the SilverLinker administration tool in WebAdmin, the list is formatted according to the operating system that the WebAdmin server is running on, not the operating system your browser is running on. This means that if you use a browser on NT to download a publication list from a Linux system, you will get UNIX-style line feeds, which Notepad does not recognize. You should therefore open and edit the list in a text editor other than Notepad (such as WordPad). (10771) Holdings: Points To Note ======================== Installation of holdings ------------------------ * When transferring holdings files from a machine where they were generated on to a machine where they will be used, the files should always be transferred as binary except when transferring the LHM file from NT to UNIX which should be transferred as ASCII. Note that this rule is different from ERL v2.x. * In addition, the HCU generated files are not compatible with the SPLHA files. If both types of holdings are required on a server then they should be placed in separate user specific directories under /sproot/cfiles. It is important that if HCU files are in a user specific directory that SPLHA files are not placed in /sproot/cfiles, otherwise a client connection loss will occur. (9375) Large holdings messages can cause a lost connection --------------------------------------------------- Holdings messages that contain hotlinks, and that are more than 8k in size, can cause a lost connection. (A workaround is to split up any such messages.)(10914) SilverLinker: Points To Note ============================ ERL v4.11 requires SilverLinker 2 databases ------------------------------------------- You cannot use SilverLinker 1 databases with ERL v4.11 and later, you must use SilverLinker 2 databases. The first databases that contained SilverLinker 2 links have the following volume IDs: weekly: SLNK078W monthly: SLNK0019 You may want to remove any updates earlier than these ones from your ERL server before you upgrade to ERL v4.11. (They will do no harm if you do not remove them: they will simply not show any links.) Once you have ERL v4.11 and the SilverLinker database installed, it is important that whenever you update the SilverLinker database you install the new database before you uninstall the old one, to ensure that links are always available. WinSPIRS cannot work with Elsevier ScienceDirect links ------------------------------------------------------ WinSPIRS is currently unable to use Elsevier ScienceDirect links. This is because of a problem with the number of characters in the link, which does not affect WebSPIRS. (10533) Problem with printing SilverLinker links in WebSPIRS ---------------------------------------------------- We are aware of a problem that when printing records in Netscape that contain SilverLinker links to full-text articles, the printing can come out with very small fonts. This happens when SilverLinker links are configured to appear in a drop-down menu. SOLUTION: * Users can de-select the FTXT field from the fields they want to print, before printing the records. * Administrators can make either of the following changes to the webspirs_user.cfg file. * Set SP.SILVERLINKER.format=TEXT (this ensures full-text links always appear as text links). Or, * Set SP.SILVERLINKER.format.select.min=4 (full-text links will only appear in a drop-down menu if there are 4 or more links for any one record.) (10319) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 7. Contacting SilverPlatter Technical Support =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= If you need further assistance with the ERL 4.11 software, please send an e-mail to support@silverplatter.com or contact one of SilverPlatter's regional offices: UNITED STATES: SilverPlatter Information, Inc. 100 River Ridge Drive Norwood, MA 02062 Tel: 800-343-0064 781-769-2599 Fax: 781-769-8763 ---------------------------------- LONDON: SilverPlatter Information Ltd Merlin House, 20 Belmont Terrace, Chiswick, London W4 5UG England Tel: +44 (0) 20-8585 6400 Fax: +44 (0) 20-8585 6640 ---------------------------------- AMSTERDAM: SilverPlatter Information BV Nieuwe Herengracht 49 1011 RN Amsterdam The Netherlands Tel: +31 (0)20-625 96 50 Fax: +31 (0)20-623 74 08 ---------------------------------- BERLIN: SilverPlatter Information GmbH Guentzelstrasse 63 D-10717 Berlin Germany Tel: +49 (0)30-857799-0 Fax: +49 (0)30-857799-99 ---------------------------------- =-=-=-=