Howard Schwartz <[EMAIL PROTECTED]> wrote:
>For many years I've used the Yarn offline news/mail reader for dos, with
>mixed feelings.
[snip]
I have also had these mixed feelings for a while but in the meantime
I've learned a lot about Yarn and have a better command of it.
>What I dislike about yarn is that its modified SOUP format makes the
>files that hold messages quite fragile: It starts each message with
>hex digits that specify the message's byte length, and includes a # of
>lines field in the header. Thus if a few bytes in the file get messed
>up, you have a corrupt file from Yarns view. Also, there are millions
>of hard to remember utilities to fix little or big things that go wrong
>in yarn.
SOUP 1.2 is not Yarn's format. It only imports this format (and a couple
of others). OK, you're right, it uses it also for replies.:-) My
experience is that Yarn always needs a well maintained HD, sufficient
memory and perfectly created SOUP packets (if you have to insist on
them) for its import process. So a Yarn user has to use Scandisk and
Defrag ( or similar programs ) more often. Yarn (at least Yarnx for
i386) needs much memory. You can adjust and improve Yarn's behaviour
using PMWSETUP.EXE, which can be used for other programs built with the
PMODE DOS extender, too. My experience is that a good editor and 3-4
utilities are enough to fix possible problems.
>I am almost content using Jeroem Schipper's readmail version 5 beta to
>read mail offline in dos and send replies. However, it is a discontinued
>program some bugs in its message setup, very little information about
>how to define message headers in its later versions, and the author
>pretty much wants to have done with the thing and not answer
>correspondence.
Why don't you use the automatic message-type recognition? IMO its not
bad. As you say, unfortunately there is no information about header
definition in the last version. Just recently I found a very short
readme.doc for ver.5.0 that helps to create message types. Should you
not have it, I could mail it to you.
--
Tibor Mocsar
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.