🚀 go-pugleaf

In article <1992Nov22.140508.12220@bsu-ucs> 00clcoffing@leo.bsuvc.bsu.edu writes:
>I figure I should put on my $.02 about DRDOS 6.0....
> [stuff deleted]
>     My friend down the hall also used (note past tense) DRDOS and SSTOR.
>Somehow part of SSTOR's data file became corrupt.  When SSTOR loaded, it
>displayed a message to the effect of "...file corrupt, mounting device as
>read only."  The DRDOS manual advised us to run CHKDSK to correct the problem
>then reboot.  How is it possible to correct the problem when SSTOR has the
>drive write protected?  We backed up all data which wasn't corrupted, and
>removed DRDOS for good!

After backing up (you didn't before hand? tsk tsk), did you even TRY to 
run chkdsk?  

I assume SSTOR is similiar to STACKER in this aspect:

When a *possibly* corrupt compressed volume, it is mounted read only.  However,
the volume is represented on the host drive as a bid hidden file.  Normally
this file is set with the bits Hidden, Read-only, and System.  SSTOR/STACKER
aware programs (such as DRDOS chkdsk and STACKERS scheck) can play with those
bits and go in and muck around with the file.  Hmm... I would think that 
putting all the functionality of regular chkdsk and sstor-aware chkdsk would
bloat the binary a little bit.  (Or does DRDOS offer 2 version of those 
binaries which would need to be sstor-aware?). 

anyway, my observations,
mrc