G'day Rod,
       I've applied the pokes and the prog. has been functioning fine
(mostly) with the native partition on the ED disk.  But this evening
while Browseing the  twit file and using the space key to goto the next
message a glitch did occur.  The drive failed to read the next message.
 I waited some minutes (at least it seemed like minutes) and no message
appeared.  I removed and replaced the disk, got a "drive not ready
28,129" message and then the next message appeared.  The activity light
remained on the whole time.  I certainly hope I was not too impatient
for the next message, but as I couldn't hear any head activity from the
drive I concluded there was a prob.  The highest message number is 500
I think and the prob. happened at 213. If that makes any difference.
 RG> I sure hope I haven't just put out V4.2
 RG> that has bugs that you hadn't
 RG> made me aware of.  (You must *never*
 RG> assume that I know all the bugs,
 RG> or that others have reported them to me).
 RG> I am aware of a problem when using
 RG> revious in the header mode.. I
 RG> haven't heard of any problem relating to reading Next messages. :-(
I've tried to tell you as many details of this prob. because of what
you've said.  If I've jumped in too soon with this and it was just an
unusually long search for the next message it might be worth trying to
add some sort of indicator that all is well while nothing is apparently
happening for a long time.
AS for 4.2, I've looked for it when I first read about it but it hadn't
made it to Talisman or Network at that time (about 2 weeks ago)  I'll
have another look when I UL this message. BTW this message is being
typed during the same run session that the glitch occured.
This may be nothing but you've said you what to know so there it is.
BFN Reece.

... A seminar on Time Travel will be held last Friday - be there!
-=- QWKRR128 V4.1 [R]
--- FMail 0.96â