[Info-vax] ana/disk/repair

[AEF]

On Dec 26 2012, 3:21 pm, hel... at astro.multiCLOTHESvax.de (Phillip
Helbig---undress to reply) wrote:
> In article <5PKdnWqKnbcz2kbNnZ2dnUVZ_uedn... at giganews.com>, "Richard B.
>
> Gilbert" <rgilber... at comcast.net> writes:
> > Please use your "Enter" key or carriage return at reasonable intervals.
>
> Indeed!
>
> > When you enter more than about 120 characters without carriage returns
> > it can require the recipient to edit your text to make it readable.
>
> Right.  Sometimes, such stuff is encoded as well, even though it is just
> 7-bit printable ASCII.
>
> > One cause of this is cutting and pasting from text produced by Microsoft
> > tools.  There may be others.  What ever you did, PLEASE DON'T!!!!!
>
> Google Groups is one.
>
[...]

Hmmm. I've been posting here from Google Groups for a long time and no
one's complained about my postings (well, not for lines being too
long, anyway). Maybe posting from "New Google Groups" will do it. I
don't care for the new version.

The LaTeX manual recommends a limit of 75 characters per line,
including spaces and punctuation marks, when designing your own LaTeX
"document styles". I'm not sure what that translates into for fixed-
with font. Maybe 70 or 72.

I hate webpages that have very long lines that don't wrap when you re-
size the window. There should be a standard!

OK.

Back to the topic: I wouldn't run it without /CONFIRM first.

And using /REPAIR locks the disk, IIRC. That's could be a serious
performance hit!

But not using /REPAIR could find false errors which are due to the
disk not being locked, and files being written to during the scan, and
such.

OK.

AEF