Subject: Re: Porting pine to dos/windows ?

From: "Hans Hofman" <[email-masked]>
Date: Sat, 27 Mar 1999 11:12:02 +0100

Hi,

I'm having problems porting the source code of pine to windows/dos.
Is there a project file and files which are adjusted for Microsoft Visual
C/C++ v6.0 or Borland C/C++ v5.02
Ther is no projoct / makefile for this platform although Pine devellopers
are speaking about it.
I would like to make an automatic email extractor including attachments.

Any help is greatly appreciated.

Hans

---

From: Terry Gray <[email-masked]>
Date: Sat, 27 Mar 1999 08:18:18 -0800 (Pacific Standard Time)

Hans,
We already provide a windows version of pine, but we can't release source
for it because it includes proprietary code that we licensed for the
windows version.  

However, for your project it may be sufficient to have access to the
c-client libraries, for which complete source is freely available.  These
are used for both pc and Unix versions of Pine and provide all the
low-level MIME parsing and message access/storage routines.

-teg

---

From: Scott Leibrand <[email-masked]>
Date: Sat, 27 Mar 1999 09:42:25 -0800 (Pacific Standard Time)

Are there any plans to release a dos/win3.1 version of Pine 4?  It's a
major inconvenience for users to be unable to access their shared address
book on older machines...

Thanx.
-- 
Scott Leibrand
C&C Student Staff
[email-masked]
[email-masked]
How to contact me:
http://students.washington.edu/leibrand/howtocontactme.html
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message.          *

---

From: Terry Gray <[email-masked]>
Date: Sat, 27 Mar 1999 09:46:12 -0800 (Pacific Standard Time)

Alas,
DOS/Win3 users are relegated to the Pine 3.9x family... and can therefore
share addressbooks only via remote filesystems, not IMAP.

(Of course old machines also run telnet just fine :)

Sorry... it's a "price of progress"

-teg

---

From: Scott Leibrand <[email-masked]>
Date: Sat, 27 Mar 1999 16:34:02 -0800 (PST)

Ok, but why?  What is the technical limitation that prevents dos/3.1
machines from running Pine 4?

Thanx.
Scott Leibrand

---

From: Shoeless in San Jose <[email-masked]>
Date: Sat, 27 Mar 1999 17:56:20 -0800 (PST)

It's a 32-bit program.  At best, you'd have to have Win32 running, and I
personally have never been able to get it to work the way it's supposed
to.

Greg

---

From: Scott Leibrand <[email-masked]>
Date: Sat, 27 Mar 1999 18:09:38 -0800 (PST)

Ok...  Is Unix Pine 4 also 32-bit, then?  What's the difference between
16-bit and 32-bit programs, anyway?  :)

---

From: Shoeless in San Jose <[email-masked]>
Date: Sat, 27 Mar 1999 18:21:26 -0800 (PST)

16-bit programs were written for DOS / Windows 3.x, and 32-bit programs
are more for Windows 95 / 98 / NT.

---

From: Scott Leibrand <[email-masked]>
Date: Sat, 27 Mar 1999 18:33:55 -0800 (PST)

I know that much.  I'm interested more in the technical differences.

---

From: David Dyck <[email-masked]>
Date: Sat, 27 Mar 1999 20:41:18 -0800 (PST)

> > are more for Windows 95 / 98 / NT.

Ok, I'll try to contribute something here.

I just finished porting 2 apps from 16 bit to 32 bit
(actually they were dll's).  Anyway, we had the code written
to be pretty portable already (68000, Sparc, Dos, linux), 
so except for changes in the
way that win32 handled serial communication, it was pretty
much re-compiling.  Sometimes it can be simple, other times
you can run into limits
  no arrays with more than 64K elements
  there are limits on the size of individual arrays.
  in 16 bit land you sometimes need to be aware that pointers
    could sometimes be a 16 bit segment, and a 16 bit offset
  I think there is a limit (like 4096) possible segments, although
    the newer compiler libraries try to merge many news into the same
    segment.

I haven't looked at what services are provided in the libraries
that they can't release, that may be an issue also.

---

From: sch <[email-masked]>
Date: Sun, 28 Mar 1999 17:10:07 +0800

> for it because it includes proprietary code that we licensed for the

I think c-client is enough if we are trying to port pine to windows. I found
that
the pine,pico are sth deal with GUI,cfg and I guess the funtional work as
sending, recving mail,
parsing mail were done in c-client, but I still hope some documents will
introduce the API offered by c-client lib, the documents should have been made
by the
devel group, and why not publish them on internet for pine community?