HP3000-L Archives

September 1995, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
David Doyle <[log in to unmask]>
Reply To:
David Doyle <[log in to unmask]>
Date:
Tue, 19 Sep 1995 09:54:17 PDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
See what happens when the development people move to the other side of the
building?  We have a program that quickly runs down the file checking each
block for corruption.  It's essentially an optimized version of Stan's
algorithm for finding a messed up message file.
 
 
______________________________ Reply Separator _________________________________
Subject: Re: Message files - how to detect corrup
Author:  Mark Sexton <[log in to unmask]> at Internet-Link
Date:    9/18/95 4:46 PM
 
 
Gee, at one time I would have expected someone from Quest to *answer* a
question like this.
 ----------
From: Lou Pendley
To: Multiple recipients of list HP3000-L
Subject: Message files - how to detect corruption
Date: Monday, September 18, 1995 1:32PM
 
     Is there any way to detect file corruption - specifically ->
 
     BAD VARIABLE BLOCK STRUCTURE (FSERR 105)
 
     It appears that after system failures message files can be corrupted,
     and we'd like to know if they are after a system failure.
 
     Please respond to this via e-mail, as I don't belong to the list
     anymore.
 
     Lou Pendley
     Quest Software
     [log in to unmask]

ATOM RSS1 RSS2