Subject: Re: Problems with Lan Workplace winsock and PC-PINE for windows

From: Alex Sharaz <[email-masked]>
Date: Mon, 3 Oct 1994 09:50:47 +0100 (BST)

On Thu, 29 Sep 1994, Barry Landy wrote:

> On Wed, 28 Sep 1994, Alex Sharaz wrote:
> 
> > Hi all,
> > 
> > I've noticed some messages on this group about the windows version of 
> > PC-PINE not working with certain flavours of winsocket. I'm running Lan 
> > workplace Vsn 4.2 and although I can look at myIMAP folders o.k. whenever 
> > I try to send a message, the PINE process "stops communicating".
> > I'm running windows 3.11 on a 486/33Mhz with 8 M ram. Did somebody post a 
> > solution to this problem that I missed or are there still problems 
> > running the Windows version of PC-PINE?
> > 
> > Alex
> > 
> > 
> > RFC-822: [email-masked]
> > X.400:   I=A;S=Sharaz;OU=Computer-Centre;O=Hull;PRMD=UK.AC;c=GB
> > X.500:   c=GB@o=University of Hull@ou=computer Centre@cn=Alexander Sharaz
> > Tel:     +44 482-465700 Fax:     +44 482-466441
> > 
> 
> Interestingly enough I have the same problem trying to run WinPine under 
> OS/2's TCP/IP interface (and OS/2's windows, of course).
> Even odder, it has worked OK just twice!
> I also get a stuck state when trying to postpone (^-O).
> 
> I have so far been prepared to be convinced that this is an 
> incompatibility between OS/2 windows and "real" windows, but I am 
> encouraged by your finding (and others in this group) to think that it 
> may be bug(s) in winpine after all.
> 
> 
> =======================================================================
> Barry Landy, Head of Systems and Development,
> University of Cambridge Computing Service
> [email-masked]      0-1223-334713   +44-1223-334713
> 
> 
> 
I've solved my problem with WinPine thanks to some messages from other 
people on this group. I have a number of PC Mail clients set up on my PC 
and one of them requires a TZ (timezone) varialbe to be set up. Once I'd 
removed this variable from my autoexec.bat file, everything worked o.k.

alex

RFC-822: [email-masked]
X.400:   I=A;S=Sharaz;OU=Computer-Centre;O=Hull;PRMD=UK.AC;c=GB
X.500:   c=GB@o=University of Hull@ou=computer Centre@cn=Alexander Sharaz
Tel:     +44 482-465700 Fax:     +44 482-466441

---

From: Cary Orange <[email-masked]>
Date: Mon, 03 Oct 94 08:32:08 PDT

> removed this variable from my autoexec.bat file, everything worked o.k.

Thanks for the tip.  I too had a TZ variable defined in my environment and 
after taking it out, my PC-PINE 3.90 now sends mail.  BTW, I'm using the 
NetManage winsock.

Cary

---

From: Barry Landy <[email-masked]>
Date: Mon, 3 Oct 1994 17:29:21 +0100 (BST)

> removed this variable from my autoexec.bat file, everything worked o.k.

Wow - what a wierd and wonderful idea - how on earth did you come to try 
that.
Believe it or not, removing the SET TZ=value from the AUTOEXEC.BAT solved 
my problems also!

I have emailed pine-bugs with the good news.

Of course, this is not a solution, as we do actually need to set the 
timezone (the piece of email I sent myself from Windows Pine under OS/2 
said it came from the PDT timezone, which is Pine's default).