Subject: Re: not reading .addressbook

From: [email-masked] (Neil Le Quesne)
Date: 8 Dec 1994 18:37:41 +1030

Mark A. Stephan ([email-masked]) wrote:
: When I switched versions of pine, I realized that the new pine was not
: accepting the old addressbook, and was trying to create a new one.  Anyone
: get this problem?

Interesting that you mention this. Just a few minutes ago I was discussing
Pine with the sysop on my system, and was advised that we would not be
upgrading to Pine 3.91 because it was not backwards-compatible (ie. will
not read old addressbook and other user-configurable elements). I'd love
to know if this can be overcome. Anyway..thought you might be interested :)

Neil Le Quesne
Managing Partner
Asian Trade Links

____________________________________________________________________________

                       A S I A N   T R A D E   L I N K S

                       Linking Australia & Asia in Trade

           3/237 Belair Road,  Torrens Park,  SA,  Australia,  5062
        Phone/Fax:  61 (8) 374-1130     E-Mail:  [email-masked]

____________________________________________________________________________

--

---

From: Steve Hubert <[email-masked]>
Date: Thu, 8 Dec 1994 10:15:18 -0800 (PST)

The address book code was almost completely rewritten for 3.90 and some
incompatibilities showed up.  In fact, there were some serious address
book problems with 3.90, ranging from not being able to read address books
that worked with 3.89 to some cases where address book data was destroyed. 
3.91 is much better than 3.90 with regards to address book bugs and other
bugs, as well.  3.92 will be even better, I think.  All of these versions
were *supposed* to be backwards-compatible with previous versions of the
address book.  If it still isn't, that's a bug and we'd really like to know
about it.  If anyone has an address book that 3.91 can't read please send
a bug report, including the addressbook as an attachment if possible. 

(3.90+ did introduce a new file, .addressbook.lu, that wasn't in previous 
versions.  This file should be built and maintained automatically.  You 
should be able to remove that file and it will come back by itself.  When 
it creates that file it isn't creating a new addressbook, just a lookup 
file for the same old address book.  The lookup file's purpose is to 
allow us to support large address books without slowing things down and 
without using lots of memory.)

Steve Hubert <[email-masked]>
Networks and Distributed Computing, Univ. of Washington, Seattle

---

From: Neil Le Quesne <[email-masked]>
Date: Fri, 9 Dec 1994 13:33:00 +57100

> Networks and Distributed Computing, Univ. of Washington, Seattle

Many thanks for your comments. I'll pass this on to our sysop, and 
hopefully he will attempt to resolve the problem with you.

Cheers,

Neil Le Quesne.