| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1987.1 | some questions | XANADU::qwert.zko.dec.com::mcclung | John McClung, 381-2774 | Thu Feb 13 1997 18:02 | 24 |
| 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.2 | Answers to questions | OASS::ANDRES_B | | Fri Feb 14 1997 15:12 | 47 |
| > - What type of PC's are these, how much memory, ...? Any differences
> between the 5 that don't work and the one that does?
** In general PC's are Digital Venturis/Celebris 486/Pentium with
** 16mb of memory. My PC is a Digital XL 590 with 48mb of memory.
** The one that works is a Digital Venturis 5100, 16mb, cd, 3� floppy
** (Arnita's). One that doesn't work is also a Venturis 5100,16mb,
** no cd but 3� floppy.
>
> - What TCP/IP stack is being used?
** Pathworks 6.0
> - When the screen "goes blank" is there an error message?
>
** No
>
> - 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.
** No, my startup item has "nomail" on the command line and, if I
** reboot Windows and try to close the POP3 before doing anything
** else, this still happens.
> - If it is necessary to do a mail retrieval, does the retrieval
> succeed, or is an error indicated?
** It's not necessary but retrievals are successful in general.
> - Do these users have an Internet Mail file cabinet defined? Is it
> primary?
** Yes, they have an Internet Mail file cabinet defined. It may
** or may not be primary at the moment. The one I just tried
** Internet was primary and it did the same. And I just tried it
** with DECmailworks as primary and it did the same thing - so it
** doesn't seem to care one way or the other.
Please let me know if I can provide any additional information to get
this issue resolved.
Thanks,
Beth Andres
|
| 1987.3 | more questions | XANADU::qwert.zko.dec.com::mcclung | John McClung, 381-2774 | Fri Feb 14 1997 16:25 | 18 |
| 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.4 | Some Info and I will get the rest | OASS::ANDRES_B | | Mon Feb 17 1997 10:42 | 31 |
| 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.5 | Possible WINSOCK.DLL problem | OASS::ANDRES_B | | Mon Feb 17 1997 17:03 | 97 |
| John,
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 (?). 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.
From Customer:
Beth,
You probably want to skip to the !#!# at the bottom and read it first!
Trina
>Trina,
>
>Below are some additional questions from engineering. I have answered
>most of them but would like verification from you. Please add any
>additional information which you feel might help or any that I have
>added that is incorrect.
>
>
>
>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. In this order:
TimeToo! (program scheduler)
FAL
MSOFFICE button bar
TeamLinks Message Notification
(POP3 Retriever was last)
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:\PW6 directory.
** There's only one on the PC but the same one is also in a network
directory that is in the path, dated 12/4/96 and size 64000.
In the DLL listing I sent you last week, we should be able to
verify that the one on the C: drive is the one being loaded.
>
>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...
>
PATH: C:\PW6
LAST CHANGE: 12/4/96 11:08
Version: 6.0.62
COPYRIGHT: DEC
SIZE: 64,000 bytes
Version information
Company: Digital Equipment Corporation
File descr: Pathworks WINSOCK.DLL
internal name: WINSOCK
LANG: US ENGLISH
LEGAL TRADEMARKS: PATHWORKS� ... DEC
Original filename: WINSOCK.DLL
Product name: Pathworks for Windows or DOS
Product version: 6.0
>
>What is your DOS path info (do a PATH command from a DOS box)?
>
PATH=C:\PW6;C:\DOS;;C:\WINDOWS;C:\TEAMLINK;C:\MOUSE;E:\PCAPP;
C:\SQL\BINR;C:\SQL\DLL;;N:\S10COST
(I rewrapped manually so you would be sure to get it all.)
>
>Is this info the same as on the other systems (especially the one that
>does not have the problem)?
>
Well, this is interesting. The one on the PC that does not have
the problem is version 6.0.59 and size 61952. I remember we got
a new version of WINSOCK.DLL to fix some earlier problems but I
don't remember specifically what they were.
!#!# I copied this older version to my PC and tested it - guess what.
I opened and closed my POP3 retriever 3 times in a row and didn't
get hosed! But what were we trying to fix with the newer one
and why, oh, why and - a million other questions that come to
mind.
But I guess that means that this particular horror story is over.
Yes?
|
| 1987.6 | Pathworks WINSOCK.DLL version 6.062 is the culprit? | XANADU::qwert.zko.dec.com::mcclung | John McClung, 381-2774 | Tue Feb 18 1997 08:59 | 30 |
| 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 ([email protected]) 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.7 | file copied to XANADU:: | OASS::ANDRES_B | | Tue Feb 18 1997 10:38 | 14 |
| 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.8 | reproducible here using Winsock 6.062 | XANADU::qwert.zko.dec.com::mcclung | John McClung, 381-2774 | Tue Feb 18 1997 13:10 | 18 |
| 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.9 | | XANADU::laceup.zko.dec.com::tamara::fitzell | | Wed Feb 19 1997 09:50 | 9 |
| 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
|