Welcome to Version 2.16.0!

 

TERMS for Windowsä

MAXCOM, A Division of Haas TCM

 

 

OVERVIEW

 

This is fully functional version of TERMSÒ. This program is not time restricted. Yearly maintenance agreements to update regulatory information and product features can be obtained by contacting the Sales department:

 

voice:                888/707-8819

fax:                   520/434-2200

email:               maxcominfo@haastcm.com

technical Email: tech@haastcm.com 

Web:                http://www.maxcomonline.com

Technical Web:  http://www.maxcomonline.com/cs/index.htm

 

Comments and suggestions are always appreciated.

 

CONTENTS:

-----------------------------------------------------------------

1.         MINIMUM SYSTEM REQUIREMENTS

2.         INITIAL INSTALLATION STARTUP NOTATION

3.         WINDOWS NT AND 32 BIT OPERATING SYSTEMS

            A.         PERMISSIONS

            B.         INSTALLATION FROM A SHARED ENVIRONMENT

4.         WINDOWS VISTA AND WINDOWS 7 OPERATING SYSTEMS

5.         STARTUP ERROR ASSISTANCE

A.                  ERROR -1607 (1603 AND 1605) DURING INSTALLATION

B.                  ERROR 429

C.                  Error DCOM95.EXE does not exist

D.                  Error 20599 When Printing reports

E.                  Error 339

F.                  Error 432 during Installation

G.                 Error Fatal Error when installing LAN/WAN Version –Windows 98 to Novell Server.

H.                  FMOD error when loading the CD-Rom

I.                     ERROR WHEN IMPORTING PDFS – DOES NOT SUPPORT LZW ENCRYPTION

6.         Uninstalling TERMS (All Operating Systems)

7.         Scanning MSDSs - Notations

8.         TECHNICAL SUPPORT NOTATIONS

A.         REPORTING ERRORS/TECHNICAL SUPPORT

9.         SARA 313 REPORTING NOTIFICATION

10.        PRODUCT UPDATES

 

 

1.         Minimum System Requirements

 

            TERMSÒ Version 2.16 requires the following:

            Pentium 166 (200 recommended minimum) or higher

            32 Megs or higher of RAM

            Microsoft operating system (95, 98, NT, 2000, ME, XP)

            TWAIN Compliant Scanner (if direct scanning is desired)

            Internet Explorer 4.0 or higher

            Image Viewing Software (required to view TIFF images)

            Adobe Reader (required to view Adobe PDF Images)

 

2.         INITIAL INSTALLATION STARTUP NOTATION

 

            This is a full installation for Version 2.16 and encompasses all other updates since Version 2.0 and above.  Use the Full Installation method if your previous version is 1.8 – Version 2.3.  If you have Version 2.4 or higher, you can use the Update Installation Method.

 

            If you are Upgrading your data to from Version 1.8 to 2.16:

 

            There are four important items you must do prior to installing this update.

 

1)       Make sure you have administrative privileges via your network login to install this program.  We require ability to install MDAC 2.5 if necessary which occurs during our installation process.  Problems were encountered when user on an NT 4.0 or Windows 2000 machine did not have Administrative privileges.

 

2)       Run DBUpdate/then File and Repair Database on the msds.mdb file

 

3)       Make a backup of your msds.mdb, tier2.mdb, and scans.mdb

 

4)       Make sure you are using data in Version 1.8 of TERMSÒ. We cannot guarantee success with the conversion process of this product from versions earlier than 1.8 without first please doing these 3 items.

 

            This program will convert the msds information from Version 1.80 to Version 2.x and will delete the Scans.mdb.  All the tiff images from the scans.mdb will be stored to an exterior directory labeled "Scans" within the program directory if you have a PC version, or on the Database shared directory if you have a LAN/WAN Version. To enable the dbupdate to convert your data, you must first backup your msds.mdb, scans.mdb and tier2.mdb within the Version 1.8 Database location (found in the WT.INI and the datapath= statement). Make a copy of this information and paste to the WT32 database directory.  This is found in the wt32.ini file in the datapath= statement.  Then run DBUpdate for TERMS 2.x and then File and select Update MSDS Standard.  For those with large scanned image files, and databases are on a network drive, it is suggested to run the DBUpdate utility from a local path point rather than the LAN database location, make sure a subdirectory called NEW is within your local database location and containing the following files: msdsnew.mdb and tier2new.mdb. Do not interfere with the dbupdate conversion process after starting or data corruption may occur. If you are already in Version 2.1, please disregard this statement, you have already upgraded your data from 1.8 to 2.9.

 

            It is strongly recommended to make sure Explorer is the only program running in the background during installation.  We have had reports of windows system file problems with TERMSÒ when it was installed with various TSR or Windows programs running in the background.  Examples of programs which interfere with our installation include, Microsoft Office Suite, Lotus Office Suite, Lotus ccMail, Microsoft Outlook, and McAfee and Norton Antivirus. These programs when running during installation interfere with the installation process and could potentially corrupt system files necessary to run TERMSÒ.

 

            Important note for PC Users:

            TERMSÒ shipped as a PC License or as a LAN/WAN License.  PC Users must choose the PC installation.  To enable the LAN/WAN license installation, you must have the password supplied by MCT.  If you have your databases (msds.mdb and Tier2.mdb) in another location other than your program directory, you may have difficulty accessing your data.  To Remedy:

1)                   Open the WT32.INI file typically located within the root of your TERMS directory (as of Version 2.2).  The default is C:\WT32.

2)                   Change the DataPath= statement from the program installation directory to the proper location and save the file.

3)                   Also, open the control panel and open 32 bit ODBC Administrator.  Go to the File DSN tab and change the location settings for the MSDS.DSN and Tier2.DSNs to the location of where the data is on the network drive.  Not necessary with Version 2.3 or higher.

 

Important note for LAN/WAN Users:

New for version 2.3 and later is the ability to create Microsoft Visual Installer installations where using switches will allow you to create a batch deploy of our installation to all of your users.  See AdminGuide.PDF within the Manuals folder of the LAN/WAN Version CD-Rom.

 

Windows XP and LAN Installations:

There is a problem when using the LAN/WAN on XP and 2000 machines.  A Severe error will occur with a message no specified number when installing in previous versions of our installation.  This is a bug in our installation software.  There is no work around so far from the software vendor.  For Version 2.3 and above, please use the Update installation that does not change anything except program files that were replaced since Version 2.2.  If you are a new customer, please see our AdminGuide.PDF provided on our CD-Rom for more information.

 

            MDAC 2.5:

Our program requires the usage of MDAC 2.5 (Microsoft Data Access Components) to be installed on the Client's machine.  This windows component is not backwards compatible with TERMSÒ Version 1.80 and below.

 

           

3.         WINDOWS NT AND 32 BIT OPERATING SYSTEMS

 

            A.         PERMISSIONS:

 

Before installing TERMSÒ to your system, you may want to contact your Windows NT Network Administrator to make sure you have the security permission to allow the copy of system files on your computer.  There have been reported system file problems with Windows NT, 2000 and XP users, especially for ODBC installation, because of security permission reasons.

 

A programming change to TERMSÒ in Version 2.2+ may ease the security burdens of Windows 2000 and XP.  We now have moved the Initialization file (WT32.INI) from the root directory of your operating system, to the program directory where you installed TERMS.  This is typically c:\wt32.  All documentation will be updated with this change. All settings from the root directory will be maintained into the program directory.

 

A programming change to TERMS/MSDS Standard for Version 2.3+ may ease the ODBC burdens for all operating systems.  All reports no longer require an ODBC DSN to run.   This will eliminate the many calls for support for blank reports when or error 20599, Unable to open SQL Server when opening a report.

 

Important Windows NT Notes:

 

                        You must have Service Pack 6 or higher installed to install TERMS for Windows. 

 

                       

           

            B.         INSTALLATION FROM A SHARED ENVIRONMENT

 

Past versions of TERMSÒ would not allow installation from a Shared CD-Rom source or from unmapped drive.  Also, please make sure the user has Internet Explorer Version 4.01 or higher installed to the machine and if using Windows NT Workstation, Service Pack 6.  After installation of our product, MDAC 2.5 should occur for Windows NT workstation users, please allow this installation to occur and reboot if necessary. You will experience ADO errors when running the program after installation.  We now use Installshield Version 7.03.  This installation as been tested in all environments we support (Windows 95, 98, NT4.0, 2000,XP, ME), but due to individual configurations, the installation may fail.  If you have difficulties with installing this product, please contact technical support at 800-524-7096. 

 

4.         WINDOWS VISTA AND WINDOWS 7 OPERATING SYSTEMS

                        TERMS does install and work on windows vista and windows 7 operating systems.  You may have to do extra steps since our default directory of C:\WT32 is not acceptable for windows to give non Read only permissions. After installation you will need to make sure this directory and sub directories are not read only for the user.  It’s imperative that it is installed by a administrative user or the installation will fail. 

 

                        Winhelp is no longer supported by Vista and Windows 7 and you can download and install a winhelp program from Microsoft that will allow our help files to run.  We will address in our next version of TERMS.  To obtain the files see http://support.microsoft.com/kb/917607

 

5.         STARTUP ERROR ASSISTANCE

 

A.                  ERROR –1607 (-1603) Unable to install program (Installshield error)

 

This error will occur if the user does not have adequate permissions to install programs. 

See Installshield knowledge base article, http://support.installshield.com/kb/view.asp?articleID=Q107070

 

B.                  ERROR 429

 

                        You may encounter Run-Time Error 429, "Can't Create Object", when running the program for the first time in Windows 95 or NT40.  This is caused by and older version or no indications of MDAC Version 2.0 (Microsoft Data Access Objects).  We have supplied this Microsoft product on our CD-rom.  Run the Setup and follow the prompts on the Screen to install. 

 

            C.         Error DCOM95.EXE does not exist

 

                        This error has occurred on PCs where they had an older version of Internet Explorer 3.02 or lower.  Our minimum requirement is Internet Explorer 4.0.  You will need to upgrade the Internet Explorer to version 4.0 before you can use our program.

 

D.                  Error 20599

 

                        You may encounter an Error 20599 (In the details tab of    our error handler) (if you are using Version 2.2 or lower), "SQL Server Error".  There could be several Solutions:

 

a.       In Windows NT or Windows 2000: You may not have proper rights to install the program.  Contact your Network administrator to install the program for you.

 

b.       Your databases are not in the same directory as the program.

 

                                                                           i.      Open the WT32.INI file within the WT32 folder and note the DataPath= statement.

                                                                         ii.      Then open the control panel and ODBC Administrator (32 bit).

                                                                        iii.      Click on the File DSN tab. 

                                                                        iv.      Change the location of the Chemregs.dsn, msds.dsn and Tier2.dsn to the location set to the same location as the WT32.ini file. 

 

c.       Another resolution for this problem is if the user's machine has Crystal Reports installed.  Crystal Reports creates a directory called "Crystal" beneath the Operating System folder.  When our program calls Crystal that we provide for Reporting, by default, Crystal looks for this directory first and then the System32 directory for any system dlls to run the report.  If this error occurs and there is no other explanation, open Windows Explorer and navigate to the root of the operating system.  If there is a Crystal directory, find a file called p2sodbc.dll.  Rename this file to p2sodbc.old and then try to run the report in question.  It should work at this point.

 

Starting with Version 2.3, we changed our reports to look at your data directly without the need for ODBC.  This has caused a lot of problems with the software that we changed how the reports get data to generate.  Please let us know your feedback on this change.

 

            E.         Error 339

           

You may encounter error 339, "SHDOCVW.DLL does not exist or not correctly registered".  You do not have Internet Explorer Installed on the computer.  Contact your network administrator and ask for Internet Explorer 4.0 or higher to be installed to your machine.

 

F.                  Error 432 During Installation

 

                        You may encounter error 432 and says that unInstallShield is running, and its not.  This could be happening if IsUninst.exe is corrupted on a particular machine. IsUninst.exe is the InstallShield uninstallation file, and when it's corrupted it might appear to be in use even though it's not showing up has a process that is running in Task Manager.  To fix, delete all instances of IsUninst.exe from the Windows directory and try running your setup again. If IsUnist.exe can't be deleted because it's in use, please try to reboot the machine and run the setup again.  Also, this error occurred on a Windows 2000 workstation where the user did not have sufficient rights to install programs. Make sure you are logged in as administrator before installing the program.

 

G.                 Fatal Error Quitting when installing LAN/WAN on Windows 98 and using Novell

 

                        You may encounter this error during installation when specifying a LAN/WAN Installation on a Windows 98 Machine and using the browse button to locate the Network directory on a Novell 4.11 or higher network.  This is due to a bug in NWNP32.DLL that affects program installation that display a 16-bit style open file common dialog box and affects the browse button.  For more information regarding this error, see: HTTP://support.installshield.com/kb/view.asp?pcode=ALL&articleid=Q102400.

 

                        A fix is available on Microsoft's website at: HTTP://support.microsoft.com/support/kb/articles/q192/2/49.asp.

 

H.                  FMOD error when loading the CD-Rom

 

If you receive an error “FMOD Warning FMOD could not initialize Windows Multimedia or Direct Sound device.  MMBuilder will run without sound support….”, Please select ok and the autorun will proceed to load. This error has been resolved in the later versions of TERMS.

 

I.                     ERROR WHEN IMPORTING PDFS – DOES NOT SUPPORT LZW ENCRYPTION.

 

If you receive this error, verify that only one period is within the name of your document you are trying to import.  The program sees the period as the end of the document name.

 

6.         Uninstalling TERMS on all Operating Systems

           

Please be aware this important notation when uninstalling the TERMS program (Using Corbus or MCT MSDS Software) through Add/Remove programs through Control Panel.  The Installation program will, during uninstall, ask if you want to remove shared files and folders.  If you choose Yes to All, you will remove the msds information files (msds.mdb, tier2.mdb and scans exterior directory).  Please make sure you have a backup of these files before uninstalling this product.  If you receive an update to this program, do not add/remove before installing the update, but install the update over the existing version.

 

7.         Scanning MSDSs Notations

 

            If you require use of the scanned image ability for obtaining MSDSs, please note the following:

 

            A.         Scanner Recommendations

                       

At the time of this writing, the TERMSÒ program requires a TWAIN compliant scanner.  The current recommended scanner list is HP7400C, HP7450C or any scanner that uses the HP Precision Scan Pro software.  We also have scanners tested by our customers such as the UMAX 1200 or higher USB scanner that works with our software. 

 

                        The following scanners have been tested and will NOT work with our program:

                       

1)                   Hewlett Packard 5000 series (Any)

2)                   (any) Parallel interface,

3)                    Visioneer Brand (any),

4)                   Microtek (any).

 

We found that parallel interface scanning products tend to have difficulty.  We more so recommend a scanner with USB or SCSI interface connectibility.  If you purchased a scanner and it works with our program, please email or contact technical support so we can add it to our recommended scanner list.  Phone: 800-524-7096 or E-Mail: tech@haastcm.com.

 

 

B.         If you experience errors when scanning an msds such as freezing, General Protection Fault Errors with files such as TWUNK32, HPPro.EXE, HPSCANNER.DLL or files related to Hewlett Packard's software or hardware, please refer to their support pages at the following URL: http://www.hp.com/ These type of errors are related to their software or hardware. 

 

 

8.         Windows 95 Users

 

            You must have IE 4.0 or higher installed to the user's machine prior to installing this product.  During installation, if the computer did not have MDAC 2.5 installed, the MDAC 2.5 installation will occur automatically.  You must allow this installation to occur.  ADO and similar errors will happen when running the program after installation.

 

 

9.         TECHNICAL SUPPORT NOTATIONS

           

            A.         REPORTING ERRORS/TECHNICAL SUPPORT

 

* YOUR FEEDBACK IS IMPORTANT TO US *

 

To report any problems, errors or suggestions, you may have, call our Technical Support at (800) 524-7096 or email us at tech@haastcm.com .

 

Please be prepared to provide all relevant information including any error messages, error codes, memory addresses, or other information appearing on-screen when the problem was encountered. You will be asked to provide the specific steps leading to the problem. Additionally, you may be asked to provide the contents of various system configuration files or any event viewer messages of any applications running in the background

 

10.        SARA 313 REPORTING NOTIFICATION

            Due to requirements of the EPA and its first time to remove elements from the report rather than add to it, once you install Version 2.90 or higher, you will no longer have the ability to generate FORM R/A reports for RY2004 and previous.  Please keep this in mind before loading this update.  However, if you need to use the TRI-ME software to submit your report, you MUST install this update for RY2009.

 

12.        PRODUCT UPDATES   

            To obtain the latest version of our program, please go to http://www.maxcomonline.com/cs/download.htm. Make sure that you have the release installed to your computer from the CD-Rom provided before installing any updates.  If you have any questions, please contact technical support.  See the Revisions.htm in the manuals directory for any problems that have been resolved or any known issues pending.

 

dab: 01/12/2010 Current Version: 2.16.0.0