[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference abbott::teamlinks_windows

Title:TeamLinks for Windows
Notice:Kit and ECO locations: See replies to note 8.o note 8.
Moderator:ORION::chayna.zko.dec.com::tamara::eppesAN
Created:Mon Aug 28 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2238
Total number of notes:9650

1987.0. "Closing POP3 blanks screen" by OASS::ANDRES_B () Thu Feb 13 1997 13:57

    TeamLinks 2.7-001
    WFW
    
    This site has TeamLinks 2.7 and 2.7-001 installed on 6 PCs.
    All but one of these PCs has a problem with closing the POP3
    retriever.  When the POP3 retriever is closed the screen goes
    blank and the PC has to be rebooted.  The users are closing the
    POP3 retriever using File | Exit or by clicking on the Title
    Bar.
    
    If TeamLinks Information Manager is running then POP3 retriever
    can be closed without the screen going blank.  This site has one 
    PC that is not having the problem.  They also ran a utility to 
    tell me which dll files are open.  A comparison was done of the 
    two PCs and the files match by size and date.  We have closed all
    programs that were running and the problem still occurs.  Normally
    they have a clock and schedule program that runs.
    
    This site has been experiencing this for about 3 months and they
    want to start installing to the rest of their users but would
    like to get this issue resolved first.
    
    Thanks,
    
    Beth Andres
T.RTitleUserPersonal
Name		DateLines
1987.1some questionsXANADU::qwert.zko.dec.com::mcclungJohn McClung, 381-2774Thu Feb 13 1997 21:0224
Beth,

A few questions (with more to come probably):

- What type of PC's are these, how much memory, ...? Any differences between the 
5 that don't work and the one that does?

- What TCP/IP stack is being used?

- When the screen "goes blank" is there an error message? 

- Is it necessary to do a mail retrieval for the problem to occur? To invoke 
TLPOP3 *without* doing a mail retrieval, use "TLPOP3 NOMAIL" on the command 
line.

- If it is necessary to do a mail retrieval, does the retrieval succeed, or is 
an error indicated?

- Do these users have an Internet Mail file cabinet defined? Is it primary?

Thanks,

John
1987.2Answers to questionsOASS::ANDRES_BFri Feb 14 1997 18:1247
1987.3more questionsXANADU::qwert.zko.dec.com::mcclungJohn McClung, 381-2774Fri Feb 14 1997 19:2518
Beth,

You have TLPOP3 in your Windows startup group, right? Do you have any other 
programs in the startup group? Can you reproduce the problem if you remove 
TLPOP3 from the startup group, and manually start it after Windows has started?

Is your WINSOCK.DLL in the pathworks directory? (on mine, this is C:\PW)
Do you have only one WINSOCK.DLL on your system (

Can you do a File.Properties from File Manager on your WINSOCK.DLL and list the 
info, such as Product, version number, size, date, path...

Is this info the same as on the other systems (especially the one that does not 
have the problem)?

What is your DOS path info (do a PATH command from a DOS box)?

John
1987.4Some Info and I will get the restOASS::ANDRES_BMon Feb 17 1997 13:4231
    You have TLPOP3 in your Windows startup group, right? Do you have any
    other programs in the startup group? Can you reproduce the problem if 
    you remove TLPOP3 from the startup group, and manually start it after 
    Windows has started?
    
    ** TLPOP3 is in the startup group, there are other programs in
    ** the startup group.  It can be reproduced if TLPOP3 is removed
    ** from the startup group and manually started.
    
    Is your WINSOCK.DLL in the pathworks directory? (on mine, this is
    C:\PW) Do you have only one WINSOCK.DLL on your system (
    
    ** WINSOCK.DLL was in the C:\PW directory.  If I remember correctly
    ** there was only one on the PC.  I will verify this.
    
    Can you do a File.Properties from File Manager on your WINSOCK.DLL and
    list the info, such as Product, version number, size, date, path...
    
    ** I will request from the customer.
    
    Is this info the same as on the other systems (especially the one that
    does not have the problem)?
    
    **  I will verify, but I believe so,  The size and dates of this
    ** file is the same.
    
    What is your DOS path info (do a PATH command from a DOS box)?
    
    **  I will have customer do this.
1987.5Possible WINSOCK.DLL problemOASS::ANDRES_BMon Feb 17 1997 20:0397
1987.6Pathworks WINSOCK.DLL version 6.062 is the culprit?XANADU::qwert.zko.dec.com::mcclungJohn McClung, 381-2774Tue Feb 18 1997 11:5930
Beth,
 
>    Below is the information I received from the customer.  It looks like
>    the winsock.dll is the culprit but the question is why?  One thing I 
>    don't really understand is she sent me copies of .dll files that were
>    open and the Winsock.dll files are the same on the two PCs.  I guess
>    the version change did not change date or size (?).  

She seems to have said that the WINSOCK.DLL files *are* different on the 2 PCs. 
The one that works (for her and me) is version 6.059, size 61952. She didn't 
mention the date, but mine says 10/26/95. The one that doesn't work is version 
6.062, size 64000, date 12/4/96.

>    The other thing
>    is I think I was told to have her upgrade Pathworks due to some other
>    TeamLinks problems she was having in with the sending Internet Mail.
>    So it looks like this updated winsock.dll has problems with closing
>    the POP3 window unless it is particular to her site.  If anyone could
>    try this version of winsock.dll on a WFW 3.11 system to verify I
>    would appreciate it.

If you mail me (mcclung@xanadu.zko.dec.com) the WINSOCK.DLL (version 6.062) I 
can try it on my system. It does appear that this is a Pathworks issue - for 
some reason the latest WINSOCK.DLL causes the problem. I would guess that it 
could be reproduced using other Winsock applications as well. Do you remember 
what TeamLinks problems there were that supposedly would be solved by upgrading 
Pathworks? You may want to enter a note in the Pathworks conference once I 
verify that I can reproduce the problem.

John
1987.7file copied to XANADU::OASS::ANDRES_BTue Feb 18 1997 13:3814
    John,
    
    I have copied the WINSOCK.DLL to XANADU.  I did not get this file
    from the customer but from ECO2 for Pathworks 6.0.  I tried this
    version of WINSOCK.DLL on my Windows 95 system and the POP3 retriever
    window will not even start.  I know this is not the version for 
    Windows 95 but I thought I would try it anyway.
    
    Let me know what you find out.
    
    Thanks,
    
    Beth
1987.8reproducible here using Winsock 6.062XANADU::qwert.zko.dec.com::mcclungJohn McClung, 381-2774Tue Feb 18 1997 16:1018
Beth,

I can reproduce the problem using WINSOCK.DLL version 6.062. Exiting TLPOP3 when 
Infoman is *not* running results in a hang. Exiting TLPOP3 when Infoman *is* 
running works fine.

It may have something to do with the fact that when Infoman is running, 
WINSOCK.DLL is in use (since CFCIMAIL.DLL needs it). Then when TLPOP3 is 
running, WINSOCK's usage count goes from one to two, and when it exits, WINSOCK 
stays in memory (since Infoman still needs it). For some reason, invoking 
Infoman then exiting Infoman does not produce the same problem.

For now I'd stay with pre EC02 version of WINSOCK (6.059 apparently), and ask 
the Pathworks people if they have any ideas.

John
1987.9XANADU::laceup.zko.dec.com::tamara::fitzellWed Feb 19 1997 12:509
Beth,
	If this is the Atlanta Regional Commission we had them upgrade 
because of memory leaks in that version of WINSOCK. We also gave them an 
ICF that helped with the problem. As long as they use the CFCIMAIL.DLL from 
the ICF or ECO1 they should be OK with the previous version of WINSOCK.DLL.
I think we also had to muck with the size of the send buffer. 


Mike