Conference abbott::teamlinks_windows

I forwarded this to Carson.

Jerry

    Carson/Jerry,
    
    I talked with the customer today and he said this is beginning to
    become more of a problem for them.  They said they can take these
    "bad" messages, send them out through the internet back to themselves
    and they read fine.
    
    He wanted to know if someone could come out there.  Anyone up for a
    trip?
    
    Heh Heh
    
    Debbie
    
    P.S. He isn't in Atlanta he is also in snow country
    

Sounds like a bug fix was lost.
Off the top of my head, I don't recall working on this.
I'll forward this to the support folks and see if they remember who 
gave out an infoman.exe for this problem.

btw: using the task manager to blow away teamlinks during a hang isn't 
going to get you very far anyway. The .dll's will be in memory in some 
strange state so rebooting is the way to go unless you know how to blow 
away each .dll as well.

Do you have the original notes file number for this problem? IPMT, qar? 
Something to jog my memory about what might have been lost.

>>btw: using the task manager to blow away teamlinks during a hang isn't 
>>going to get you very far anyway. The .dll's will be in memory in some 
>>strange state so rebooting is the way to go unless you know how to blow 
>>away each .dll as well.

On NT if they nuke the NTVDM process that TeamLinks was running in they 
won't have to reboot. Since Teamlinks is running as a subprocess in the 
NTVDM nuking it cleans out all the dll's left hanging around. 

Mike

On NT, logging off and back on will clear
out those pesky DLLs.

Jerry

    Carson,
    
    I have no idea what could have been lost I had never heard of this
    problem prior to this call.  Do you remember a problem of this 
    sort?  Its a new one for me.
    
    Debbie

Rick remembers this:

     Yes there was an ICF for a spell check problem prior to ECO 1 of V2.7. 
     The fix was placed in V2.7 ECO 1 and tested.
=========
 
I think you'd better call them up and play dumb. Find out what "the" spell 
check problem is :-) 

First the note talks about spell checking; then reading messages (spell 
check is a "send" operation). There have been fixes in both areas.

TL2.7 eco has the following spell check fixes: Is it one of these?

  08.) Ref:  CFS.44660 - TeamLinks Spell Check Skip-All produces an
        unintelligible message when spellchecking '* ... *'

   TeamLinks Spell Check displays a garbled dialog box after Skip All
   is selected when attempting to add non-words to the personal
   dictionary.

   Modules Updated:  TLSPELL.DLL

12.) Ref:  CFS.45364 - TeamLinks Spell Check removes data in TO:,
        CC: and SUBJECT fields

   If Spell Check is performed on a message that was created or replied
   to using Windows NT V3.51, the data in the TO:, CC: and Subject fields
   is removed.

   Modules Updated:  INFOMAN.EXE

  14). Ref: QAR #1734 - Change wording for hard-hyphen error message

   A spell check of the word "hard-hyphenated" does not return a good 
   error message. It says "This is an unusual hard-hyphenated form. 
   Check that hyphens are appropriate."

   Modules Updated:  TLSPELL.DLL

17.) Ref:  QAR #2948 - TeamLinks Spell Check: "Do you want to send 
        now?" message is confusing if user in working in off-line mode

   When Spell Check on send is enabled, upon completion of spell 
   checking, the message "Do you want to send now?" is confusing.  
   If the user answers yes, the user may think it will trigger dialing
   the modem and connecting.

   Modules Updated:  TLSPELL.DLL

26.) Ref:  QAR 3119 - TeamLinks Spell Check: Message with no text 
        gives strange error message 

   The Windows NT RTF editor workarounds broke the "friendly" message
   you get when you hit spellcheck before typing in any text.

   Modules Updated:  TLSPELL.DLL

but I don't see the above causing a crash in convert.dll. Perhaps number 5?

05.) Ref:  CFS.41112, CFS.44398 - No viewer available for certain
        mail messages

   A user receives a message and then reads the message from the 
   TeamLinks client.  In the Read Message Window where the parts of 
   the mail message are defined, a number is placed where it should
   say Cover Memo (ex., 5600). The dialog box message displayed is:

       "There are no converters or viewers for object type 5600.
       Do you want to associate an application with this Object".. 
  
   Modules Updated:  INFOMAN.EXE

Sounds like the customer is saying that teamlink has had hangs reading some
messages since he got an ICF to fix a spell check problem?

And that they installed 2.7 eco1 and still see the hang problem (which they 
feel was introduced in the version they got which fixed a spell check 
problem)?

So is the problem that teamlinks hangs on NT as the read message window 
comes up sometimes and not when they run the spell checker. 

A problem like this was fixed in eco2 (out shortly); but it's not specific 
to NT (any operating system will do); but it will be easy to reproduce... 
the same message will do it every time.

There are a number of things to look for; but the tip-off is when there is 
a colon in the first line of the mail message. It's not as simple as any 
message with a colon in the first line will hang; that's just the first 
step in a long line of circumstances which have to be just right (wrong) to 
get a hang. 

If the user cannot reproduce the problem by reading the same message again 
then I'd say it's drwatson time.

    Carson,
    
    1. The customer does not feel the problem started happening since the
       update to the INFOMAN.EXE that resolved the SpellCheck issue but
       we wanted the engineers to know exactly what version of everything
       we are currently working with.
    
    2. The actual problem is that reading SOME messages causes the PC
       to hang.  The PC is an NT box and the hang appears to happen
       on messages that have been imported from VMSmail and from a 
       UNIX system. If they turn around and read the same message it
       still fails BUT if they forward that message to themselves via
       internet mail and receive it back into their file cabinet they
       can read the message just fine.
    
    I hope that clears things up.
    
    Debbie Giannetti

Please get me the body of the message. Since reading it is a problem
perhaps they can <ctrl><e> the envelope from infoman and then 
file-->export the attachment that crashes.

If the symptoms of .9 apply; try tl2.7 eco 2 (which is almost out the 
door); but I'd like to see a copy of the message in either case.

Since the exact text of the message is important you might want to uu
or pkzip it so I does not change during the journey to me. It's important
that lines at the top of the message not be changed (adding/removeing
of blank lines for example).

Copy it to xanadu:: and/or send mail to carson.hovey@zko.mts.dec.com

    Customer has a drawer/folders with nothing but these problem messages
    on a floppy that he is sending to me.
    
    Debbie