Conference abbott::teamlinks_windows

I'd compare printer information between this computer and
one that works. I'd also compare fonts between this computer
and one that works.

I forwarded your note to another developer.

Jerry

    Hi,
    
    We have now determined that the problem is occuring with the special
    version of EC01 that was given to Mitre and EC02 of Team Links 2.7. 
    After further investigation we have determined that the problem seems
    to occur mainly with machines running Vshield.  I have seen some notes
    with Vshield causing problems with Team Links but NOT this particular
    problem.
    
    Please advise.
    
    Thanks,
    
    

Hi,

yesterday I installed ECO2 over ECO 1 (both 2.7 english) and since then I can't
create or reply to a message. No errors, just a hanging PC. I get out of this
situation by CTRL+ALT+DEL and stop the TeamLinks Information Manager.
I'm not using Vshield, not using Office97.

Any help out there ?

Thanks and regards.

Tomas
P.S. I had no problems with ECO 1 though...

    I've gone back to ECO1. Working right now, although I wanted to know
    what is happening. I played around with printer settings, connected/not
    connected etc. Just couldn't create/reply...
    
    Thanks for an input.
    
    Tomas

Tomas

Are you running an English verson of TeamLinks on a
German operating system.

Rick

    Yes.
    
    Thanks for your support.
    
    Tomas

    Mitre that the CSC is working with provided the following information
    
    The PCs that are having the problems are running ECO2 and VSHIELD
    if VSHIELD is not run they don't experience the problem.
    
    They are running version 3.01 of Vshield
    Windows 95
    Gateway 2000/200 PC
    
    The default startup parameters are used for VSHIELD.
    
    Beth Andres
    

Tomas,

We have found that TeamLinks ECO2 has a problem creating messages
and replying to messages when the English version is installed on
other that a English operating system. We have a fix that is currently
being tested and when testing is completed I will send you a pointer.

Rick

Re .7

Beth is the PC having the problem running off a
network? Also with ECO 2 installed does it actualy hang
or if they waited with the PC come back. Is it just this
PC running VSHIELD or others. Do others running VSHIELD 
work ok?

Rick

    Rick,
    
    I just received the following problem report from a Canadian site with
    this similar problem after installing ECO2.  
    
    This is TL 2.7-002
    WFW 3.11
    Pathworks 5.0B
    TeamLinks installed Locally
    Venturis 575/ 16 meg of memory
    
    This site was running ECO1 with no problems after installing ECO2
    when they click on the create message window it takes up
    to 2 minutes to come up.  After this initial start of the create
    message window the next times they try to load create message it
    comes up quickly.
    
    They had a product called Thunderbyte in the Startup Group which
    is an anti-virus product.  We removed this from the Startup Group
    and then when starting the create message window the first time
    after the PC is restarted takes about 30 seconds.  Still slower
    that with ECO1.
    
    This site is running the English version of WFW.  If they install
    ECO2 on Windows 95 the create message window comes up within 4 to
    6 seconds. 
    
    What should I check next?
    
    Beth
    

Beth I believe this problem is occuring because
we try and load each font when starting the 
create message window and the virus checker
is scanning each one. This functionality was
intruduced in ECO 2 this is why ECO 1 works.

Rick

Hi Beth,

I obtained a trial copy of McAfee Virus Shield 3.0.1 from McAfee's Web 
site, loaded it onto my DECpc XL 466d2, and ran TeamLinks locally under 
WFW 3.11.

I found that with VSHIELD it took an additional 13 seconds for my "Create
Message" window to be totally enabled.  This is with VSHIELD set to only
look at program files.  If I set VSHIELD to look at all files, it took an
additional 74 seconds!  I think that Mitre is running in check "All 
Files" mode or they have the font file extension names in the "Program 
Files" list of VSHIELD.  I do not beleive that VSHIELD looks at font 
files by default (RE .7).

What really makes a diffence is the number of fonts that are listed in
WIN.INI.  When I reduce the list, the amount of time needed to get to
a functional "Create Message" window is also reduced.

Joe

Hello Rick,

>We have found that TeamLinks ECO2 has a problem creating messages
>and replying to messages when the English version is installed on
>other that a English operating system. We have a fix that is currently
>being tested and when testing is completed I will send you a pointer.

Same problem overhere in Holland. Can I have the pointer when
the fix is there....

Thanks,

Jan

    re .12
    
    Joe,
    
    >>What really makes a diffence is the number of fonts that are listed in
    >>WIN.INI.  When I reduce the list, the amount of time needed to get to
    >>a functional "Create Message" window is also reduced.
    
    What causes a font to be listed in WIN.INI?  
    
    Thanks,
    
    Angela