IMPORTANT NOTE: This FAQtip contains time-sensitive information. It applies only to releases of ODMA Software through ODMA 2.0.0-1, all released on or before 1998-05-07. To verify that there are no later releases, check the AIIM DMware ODMA Support area. Confirm that you have the latest version of this note by accessing the on-line FAQtip Q000603 on the AIIM DMware ODMA development site.
Summary:
This response addresses the questions "What Are the Latest ODMA Software Versions? How Can I Obtain/Confirm Them?"
There is also information on how to install ODMA software so that trouble-shooting is easily supported.
Contributors
Change History
As part of any trouble-shooting activity, first make sure that the current ODMA software is installed on your computer systems. Review the following steps:
- Identify the Versions You Have
ODMA Configuration Manager versions are identified by their size and time-date stamps. Identify what you have and determine what you need.- Obtain Current Versions
Determine which versions you require and download any that you do not have.- Clean Up the ODMA Configuration
Make sure that there are no possibilities of.DLLconflicts among the ODMA components on your system, and keep backups where they can be used to restore or alter the ODMA configuration in a straightforward way.- Manage the Configuration
Apply opportunities to keep the ODMA configuration well-managed.
- see also
- Q000703: ODMA-Aware Application and Connection-Manager Version Compatibility
X000700: Win16 Down-Level Interoperability ProblemsThrough ODMA 2.0 Connection Manager release 2.0.0-1, there have been six official editions of ODMA software: 3 versions for 16-bit Windows (Win16), 3 versions for the Win32 platform (Intel architecture):
Table 1. Identifying ODMA Software Versions Name Size (bytes) Time Stamp
(local time)Edition Description Odma.dll
28672
1998-04-09-15:212.0.0-1 Win16 edition of ODMA 2.0 Connection Manager ODMA32.dll
69632
1998-05-07-13:102.0.0-1 Win32 edition of ODMA 2.0 Connection Manager. ODMA.DLL
14816
1996-10-31-13:051.5.0-1 Win16 edition of ODMA 1.5 Connection Manager ODMA32.DLL
12168
1996-10-31-13:031.5.0-1 Win32 edition of ODMA 1.5 Connection Manager. ODMA.DLL
47616
1995-06-26-12:591.0.0-2 Win16 edition of ODMA 1.0 Connection Manager ODMA32.DLL
34304
1995-06-26-12:341.0.0-2 Win32 edition of ODMA 1.0 Connection Manager. All editions are identified by size and time stamp. There are no version-identification properties carried in the files themselves. Because time stamps can be changed depending on how your versions were installed, you may want to replace any versions that appear to be these and that do not have the correct time stamps. See section 3, Cleaning up ODMA Configurations.
Find all copies of
Odma.dllandODMA32.dllthat reside on your system:
- Conduct a global search of your hard drive(s) to determine where there are any copies.
If there are multiple and/or different versions, you will want to consider cleaning up your copies so that there is only one that will be used. See section 3, Cleaning Up ODMA Configurations.- The primary copies of ODMA Connection Manager software will be stored in the Windows\SYSTEM directory. On Win16 configurations (e.g., under Windows 3.11), there will only be
Odma.dll. On Win32 configurations there can be bothOdma.dllandODMA32.dll.ODMA 2.0 Connection Manager versions are preferred. They can operate with all versions of DMS Integrations. They provide enhanced support for trouble-shooting.
16-bit Windows (Win16) applications may have difficulty operating with different ODMA Connection Managers for Win16. To configure for 16-bit applications, you may need to find a version of connection manager that matches the version for which the 16-bit applications were constructed. For more information, see Q000703, ODMA-Aware Application and Connection-Manager Version Compatibility and X000700, Win16 Down-Level Interoperability Problems.
2.1 Download ODMA 2.0 ODMA32.DLL Directly
2.2 Download the ODMA 2.0 SDK
2.3 Download Older Versions
- see also,
- Q000706: ODMA Version-Interoperability Configuration
- Prerequisite:
- All ODMA software is archived in Zip format. To download and use any of these version, you will require a Zip-compatible utility for extracting the archived material. The version of WinZip currently used in ODMA support activities is described in Technical Note Q000706.
For most situations involving recent software and platform releases (e.g., on Windows 98 and Windows 2000), it is only necessary to make sure that you have the latest version of
ODMA32.dllinstalled. Download that Connection Manager if it is not already installed along with the ODMA-compliant document-management software being used.If you also require the ability to trouble-shoot an ODMA configuration, it is useful to download more-extensive material. To have full trouble-shooting capability, always start by downloading and installing the ODMA 2.0 SDK.
If you also need to use or trouble-shoot older versions of ODMA software, you can add older versions to an ODMA 2.0 SDK setup. There are simple procedures for switching among ODMA versions and avoiding conflicts between them.
To have the most recent, most-commonly requested version of the ODMA 2.0 Connection Manager, download
ODMA32.dlledition 2.0.0-1. Follow the procedure specified for its download from the ODMA Download area.This is sufficient to ensure that you have the latest version of the most-commonly required ODMA Connection Manager version. For basic ODMA operation on recent Win32 configurations, this is all that is required.
To have a complete trouble-shooting configuration for ODMA 2.0, obtain and install the latest version of the ODMA 2.0 SDK from the ODMA Download area.
Installing the ODMA 2.0 SDK automatically installs the Win32 and/or Win16 ODMA 2.0 Connection Managers, based on computer configuration and options exercised during the installation process. There are further tips on setting up the ODMA 2.0 SDK at
It is recommended that you backup the Connection Managers immediately after installing the ODMA 2.0 SDK.
If older (ODMA 1.0 and ODMA 1.5) versions of the ODMA software are required, it is necessary to download the corresponding SDK packages. These are described, with links to their download locations, in the technical note
In general, you must have at most one each of
Odma.dllandODMA32.dllinWindows\SYSTEM.All other copies of these DLLs, including backup copies of the active ones, should be in directories that are not shared with any other software. An example of this principle is provided in the Setup of ODMA Version-Interoperability Tests.
This prevents conflicting DLLs of the same name from being accessed in a running configuration. The key is to arrange is so that all applications will end up loading the very same
Odma.dllorODMA32.dll, and those single DLLs will provide the Connection Managers for all ODMA-aware Win16 and Win32 applications that might be running at the same time.If any ODMA-aware applications complain about operating in a lean-and-mean ODMA software setup, please contact the ODMA Tech distribution list and also check for known problems related to that application. Generally, no DMS integration has any dependency on where the ODMA software is located. Some ODMA-aware applications might have dependencies on specific copies of the ODMA software.
- See also,
- Q000703: ODMA-Aware Application and Connection-Manager Version Compatibility
X000700: Win16 Down-Level Interoperability Problems
There are additional controls available for monitoring an ODMA Configuration. Applying configuration techniques supported by the ODMA 2.0 Connection Managers,
- Choose whether to have an overall default DMS that any installed ODMA-aware application will use in the absence of any other configuration choice
- Assign a specific DMS as the default DMS for a specific ODMA-aware application
- Choose to exclude an ODMA-aware application from ODMA operation, especially as part of a problem workaround (if implemented by the assigned DMS)
The ODMA 2.0 Specification provides instructions for these cases in Section 5, Installing a DMS.
Dennis E. Hamilton
AIIM DMware Technical Coordinator
2000 August 24
- Dennis Hamilton
- collected the contributed material and organized versions 0.10 for initial trial and review.
version 0.12 Slight adjustments while updating for the ODMA Interoperability-Testing Configuration information being an independent FAQtip.
version 0.11 Reviewed and verified all links used on the page. Adjusted presentation of the table of Connection Manager versions.
version 0.10 Minimalist information needed for obtaining ODMA Connection Managers. Adapted from a workaround in the troubleshooting for incident X000500.
created 2000-08-23-16:56 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 00-09-13 11:25 $
$$Revision: 6 $