Paul, at 19:40 on Jun 10 1995, you wrote to Bill Grimsley...

PE> Here is the entire text of the message that I commented on. 

Bloody hell, most of it was missing then!  Dunno why, but the original
(which I have imported below) didn't have the Scanned flag set, and I can't
remember now if I added to it after I'd run Squish, or what. 

PE> The only bug reported is with the x'8d', and I have updated MSQALPHA
PE> and crashed it to both David and to Noel, because I thought you
PE> said you weren't going to be shipping these echos for a week.

As from Monday, and I will be missing for a few days, but probably not a
full week as first suspected.  Everything here was up in the air this
weekend, as Molly died on Thursday, but as the funeral won't be held until
Tuesday, I don't need to leave until Monday night now.

PE> Obviously I won't be getting it out on Monday as hoped.

Nor, I would guess, even by the following Monday.  :)

PE> Please tell me what these other mysterious bugs are.

Here is my original message in total...

===============================================================
Date:   Fri Jun 09 1995 06:57:04
From:   Bill Grimsley
To:     Paul Edwards
Subj:   latest alpha
Attr:   local 
PUBLIC_DOMAIN                  -------------------------------

Paul, at 23:07 on Jun 08 1995, you wrote to Bill Grimsley...

PE> As per latest message in MSGED_ECHO which you should get in a
PE> couple of days time, here is a new alpha.  Please report bugs
PE> back via this echo preferably before Monday as I want to release
PE> 3.1 then.  BFN.  Paul.

I'm using it right now, and whilst it appears no different from the last two 
releases, this one still suffers from that weird problem which was introduced 
last time, where it displays the 0x8b soft CR character in some messages.  I'll 
ignore this problem for the time being, in order to test the reliability of the 
new version, but I still find it rather annoying. 

Later... 

I have just noticed another problem.  When replying to some messages, the 
"{at}fidonet" is missing, and extraneous data is being displayed in the From: 
field of the message header instead (although it is not being saved, so 
presumably the problem is cosmetic only).  Still a worry though.

Example, this first C&P shows what should happen (and usually does)...

1386 of 1394
From:  Bill Grimsley, 3:640/305.9{at}fidonet
To:    Andy Page
Subj:  Dynalink 1414VQH
Attr:  local
ÄAUST_MODEMÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

However, frequently something like the following is occurring, and I noticed 
that in one case it was a CR/LF combination, whilst in another, it has used 
some of the text from the actual message to which I was replying...

1386 of 1394
From:  Bill Grimsley, 3:640/305.9{at}Help...  <--- This is what varies!
To:    Andy Page
Subj:  Dynalink 1414VQH
Attr:  local
ÄAUST_MODEMÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

Later still...

Yet another problem has been noticed (only twice so far today) where, when 
pressing Alt-R to invoke the reply/quote function, the on-screen text does NOT 
have quote headers inserted in front of the original writer's text.  A simple 
ESC and then another Alt-R has fixed it immediately though.  Still, something 
is obviously not right, so I guess you'd better check it out ASAP.

To date, the 16-05-95 17:46 3.1.alpha OS/2 executable has been faultless, and 
is considerably more reliable than the two subsequent versions.  I may even end 
up using it permanently, regardless of future releases.

Haven't checked the DOS exe yet, but will crash it to Noel and David for 
evaluation regardless, some time later today.

Regards, Bill
=========================================================================
@EOT:

--- Msgedsq/2 3.10 alpha