NetNews Usenet Archive 1992 #30/NN_1992_30.iso/spool/comp/sys/ibm/pc/misc/15900

Internet Message Format | 1992-12-16 | 1.7 KB

Path: sparky!uunet!usc!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!att!drutx!dwroll!dfh
From: [e-mail] (D461-David_F_Haertig(Dave)83040)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: Stacker ate my hard disk again.  :(  help....
Message-ID: <[e-mail]>
Date: 16 Dec 92 23:37:20 GMT
References: <[e-mail]>
Sender: [e-mail]
Reply-To: [e-mail]
Lines: 23
Originator: dfh@dwroll

From article <[e-mail]>, by [e-mail] (Mikey):

>Here we go again with horror stories about write-protected disks. The write
>protection is a _fail-safe Feature_ of Stacker, _not_ an error.  When Stacker
>determines that an error has occured, it write protects your hard disk so that
>the integrity of the data remains stable while you run the utilities to fix the
>problem. Then, after re-booting the machine, all is well again. Read the manual
>people  ;)

Actually, the volume write-protection feature *is not* covered well at
all in the *Stacker 2.0* manual.  I've heard the 3.0 manual is better.
The 2.0 manual mentions it only in passing, in the "error message" section
of the manual.  I can't quote it exactly, but it's something to the
effect:  "Run SCHECK and do what it recommends".  That's it.  More
detail on the feature can be had if you download the proper Technical
Note from STAC's BBS.  Even though I read my Stacker manual cover-to-cover
before installing (version 2.0), I had no clue on fixing a write-protected
volume until *after* I read the tech note.  No, I haven't encountered
any problems with Stacker to date -- but I keep all the tech notes handy
should that day ever come.

Dave Haertig
[e-mail]