| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2109.1 | 2050? | XANADU::CUMMINGS | Jerry Cummings, TeamLinks | Mon Apr 07 1997 13:12 | 7 |
| Yeah, I think it's note 2050 that discusses this. A
reinstall might fix it. Deleting FM.DLL and reinstall
should definitely fix it. One some machines here, the
second reboot after install of Office97 fixes it. We
are still looking into this one.
Jerry
|
| 2109.2 | Log file from customer on this problem | ALFSS2::GIANNETTI_D | | Tue Apr 15 1997 15:17 | 43 |
| To get to the bottom of the problem outlined turned on debug logging
and determined that he is seeing these errors and believes that the
information is releated:
Infoman:font vt320 ios2 dbl size
could not be set in text editor font reverted to ios2 dbl_wide.
He is also seeing the word cyrallic.
*************
Log file
Infoman: Font VT320 ISO2 Small Dbl-Size Uppe could not be set in Text
Editor. Font reverted to VT320 ISO2 Small Dbl-Wide.
Infoman: Font VT320 ISO2 Small Dbl-Size Lowe could not be set in Text
Editor. Font reverted to VT320 ISO2 Small Dbl-Wide.
Infoman: Font VT320 ISO7 Small Dbl-Size Uppe could not be set in Text
Editor. Font reverted to VT320 ISO7 Small Dbl-Wide.
Infoman: Font VT320 ISO7 Small Dbl-Size Lowe could not be set in Text
Editor. Font reverted to VT320 ISO7 Small Dbl-Wide.
Infoman: Font VT320 Cyrillic Small Dbl-Size could not be set in Text
Editor. Font reverted to VT320 Cyrillic Small Dbl-Wide.
Infoman: Font VT320 Cyrillic Small Dbl-Size could not be set in Text
Editor. Font reverted to VT320 Cyrillic Small Dbl-Wide.
Infoman: Font Modern could not be set in RTF Editor. Font reverted to
MS Serif.
Infoman: Font VT320 ISO2 Small Dbl-Size Uppe could not be set in RTF
Editor. Font reverted to VT320 ISO2 Small Dbl-Wide.
Infoman: Font VT320 ISO2 Small Dbl-Size Lowe could not be set in RTF
Editor. Font reverted to VT320 ISO2 Small Dbl-Wide.
Infoman: Font VT320 ISO7 Small Dbl-Size Uppe could not be set in RTF
Editor. Font reverted to VT320 ISO7 Small Dbl-Wide.
Editor. Font reverted to VT320 ISO7 Small Dbl-Wide.
Infoman: Font VT320 ISO7 Small Dbl-Size Lowe could not be set in RTF
Editor. Font reverted to VT320 ISO7 Small Dbl-Wide.
Infoman: Font VT320 Cyrillic Small Dbl-Size could not be set in RTF
Editor. Font reverted to VT320 Cyrillic Small Dbl-Wide.
Infoman: Font VT320 Cyrillic Small Dbl-Size could not be set in RTF
Editor. Font reverted to VT320 Cyrillic Small Dbl-Wide.
********************************************************************
|
| 2109.3 | FM.DLL wasn't it | AIMTEC::GIANNETTI_D | | Wed Apr 16 1997 13:00 | 7 |
| The customer has deleted the fm.dll and reinstalled - still has the
problem.
Next?...
Debbie Giannetti
|
| 2109.4 | | TAMARA::CUMMINGS | Jerry Cummings, TeamLinks | Wed Apr 16 1997 13:03 | 3 |
| I forwarded your note to Karen.
Jerry
|
| 2109.5 | request for more information | karenc.zko.dec.com::manana::chiasson | | Mon May 12 1997 19:01 | 47 |
|
The message is coming directly from our third party editor dll. If the
font is NOT a settable font in the VisualWriter editor, it returns this
non-trappable error. I have been able to reproduce this error only when
I install Office97 over TeamLinks.
It appears to have something to do with the files that TeamLinks 'was'
(and is no longer) installing in the windows system directory.
Re-installing TeamLinks will fix the problem if you have our latest
sources that installs to the TeamLinks directory rather than the win system
directory. A clean install will NOT overwrite existing files -- so if
you did not delete ALL the VisualWriter files, there still may be a
problem. We will only write the files if they do not exist.
There seems to be contention for a Visual Writer file in the system
directory. My guess was the FM.dll -- but I have had difficulty proving
that it is this file in particular. From your note I gather that you did
delete this file and re-install and it did not fix the problem for you.
There are also .FLT (filter) files that the editor uses. It is possible
that the dll cannot read this file, and is returning an error when it
attempts to verify the font as a settable font.
There are multiple files associated with the editor. All of which, we
are now installing into the TeamLinks directory rather then winsys.
Again, not all customers are seeing this --
It would be helpful if someone out there who is experiencing this can
remember what they installed after TeamLinks (when they started seeing
this message).
See note 2050.15 for a complete list of the VisualWriter files.
I suggest you move them from the win95 (or NT) system directory to the
TeamLinks directory (after a *clean install -- to make sure nothing
has munged with the files.)
This problem is still under investigation --
Thanks,
Karen Chiasson
|
| 2109.6 | more information | karenc.zko.dec.com::manana::chiasson | | Mon May 12 1997 19:10 | 15 |
|
This error does correlate directly to the entry in the logging file.
All the non-settable fonts are logged. Usually this is a silent log.
In other words, you do not get a TX error : "The designated text area is
too small for the new format settings". There are printer fonts that the
editor will not allow -- Infoman will NOT list these fonts in the
dropdown selection. Infoman is testing the settable fonts when the
Create Message window is first loaded.
Karen Chiasson
|
| 2109.7 | PowerTerm 525 Terminal Emulation/PathWorks | 34075::GIANNETTI_D | | Wed May 28 1997 18:40 | 17 |
| Karen,
I talked with the customer today and he said he had been working on
the issue lately and it appears that a terminal emulation package
that PathWorks now provides called the PowerTerm 525 loads 12 fonts
and adds those fonts to the list in the Windows INI files. He notices
the error occurs after first using PowerTerm 525 and ironically he
receives the error "The designated text area...", then clicks 12 OK's
before he can go on. He feels that the fonts PowerTerm 525 installs
and the 12 clicks prove that the PowerTerm fonts are responsible for
the error in TeamLinks.
I told him I would provide this information to you.
Hope it helps!
Debbie Giannetti
|