Last Updated 2000-10-19-15:30 -0700 (pdt)
From: Dennis E. Hamilton [mailto:infonuovo@email.com]
Sent: Thursday, 22 June 2000 21:42
To: sramnath@MEGSINET.COM
Cc: ODMA TECH LIST; GIBNEY@woodsrogers.com
Subject: RE: ODMA 2.0 sample w/ MS Word 2000
%To: S Ramanathan
%Cc: ODMA Tech
Clay Gibney
%From: Dennis E. Hamilton
%Re: ODMA Incident X000600: Word 2000 + ODMA32 + SampleDMS
I have logged a new incident report on failure of the SampleDMS (ODMASamp32.dll)
in combination with Word 2000 and ODMA32. The particulars are at
http://www.infonuovo.com/odma/support/X000600.htm
This is based on information from you and from Clay
Gibney. It does not include reported failures of ODMA32 to produce
logs. That will be researched separately.
I have performed the particular sequence under Windows 98 without any failure.
This provides a worked case where the configuration performs as expected.
We can compare logs and other material with the failing configurations.
I now request the following information to provide a failure case. I will
work with that to find a configuration on which I can duplicate the problem:
Open Microsoft Word 2000 and obtain the following information:
1. On Help / About Microsoft Word
record the Microsoft Word 2000
version number (e.g., 9.0.2720)
Click "System Info" and
record the Microsoft Windows version information at the top of the list
(e.g., Microsoft Windows 98 4.10.2222 A)
Close Word 2000
2. Create a new file with ODMA activated and with
ODMASAMP as the default DMS.
e.g., open Word after everything is
set and create a new document by typing a small amount of test data into an
unnamed file (e.g., Document1), then use the Save button to save it to the
Sample DMS.
Get as far as you can get.
Notice what shows up in the title bar.
3. When you quit windows or shut it down after a
failure, capture the following information and package it in a ZIP file (so that
there are no problems with character sets between systems):
a. The
ODMA32 log that you created.
b. Do a
file find for ODMASAMP.INI and include that file.
c. Do a
search of your configuration's temporary file (historically, Windows\TEMP) for
files named ODM*.tmp (these should all have zero length) and ODM*.txt, where the
"*" should be 3-4 numeric digits. (The ODMASAMP.INI file, if
readable, will tell you the file locations where ODMASAMP was telling word to
put things, and the names it was giving them.)
Send me any of these you aren't
concerned about the content of. (By the way, they are not necessarily text
files. They will likely be Word Document files. ODMASAMP stores away
everything with extension *.txt. This is harmless though a little
disconcerting.)
4. That's enough for now.
Thank you for whatever you are able
to provide.
I invite others who have information
to contribute on this incident to also provide information of comparable
quality. This will help us get the most value out of the ODMA 2.0 test
fixtures and also see if we can demonstrate failure modes that are happening
with production DMS integrations and WordPerfect.
created 2000-06-22-22:31 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 00-10-19 15:32 $
$$Revision: 4 $