Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!matt.ksu.ksu.edu!devolder
From: devolder@matt.ksu.ksu.edu (Eric DeVolder)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: How to write protect c: but not d: ?
Keywords: write protect
Message-ID: <1990Nov29.185615.25791@maverick.ksu.ksu.edu>
Date: 29 Nov 90 18:56:15 GMT
References: <1027@gistdev.gist.com>
Sender: news@maverick.ksu.ksu.edu (The News Guru)
Distribution: comp
Organization: Kansas State University
Lines: 39

In article <1027@gistdev.gist.com> flint@gistdev.gist.com (Flint Pellett) writes:
>
>I would guess that other people have faced this problem, so maybe someone
>can recommend a solution:
>
>Situtation: 
>
>[stuff deleted]
>What I need is the ability to write-protect the C: drive, while leaving
>the D: drive read-write: then I could leave the binaries I don't want
>changed on C: and leave datafiles for things like games on D:.
>(Actually I have drives up to I:, and they are all on one 300MB disk:
>I'd like to be able to pick-and-choose which drives would be write
>protected.)  Ideally, at boot-up time it would prompt me for a password,
>and if I gave it then C: would be read-write, if I didn't, it would be
>read-only.  The only stuff I have seen similar to this write-protects
>all your hard drives, which is not helpful unless I were to restrict
>the kids to running off the floppies.  I'm not worried about trying to
>protect myself from someone intentionally breaking in, I only need to
>protect myself from inexperience.
>
>The only thing I know of that would really work is always booting under
>UNIX and using VPIX-- but it would be nice if there were a solution for
>when I boot up under DOS.  Any ideas?
>-- 
>Flint Pellett, Global Information Systems Technology, Inc.
>1800 Woodfield Drive, Savoy, IL  61874     (217) 352-1165
>uunet!gistdev!flint or flint@gistdev.gist.com

I just recently created a program called RmDriv that will disable (and enable)
any drive on your DOS system.  This program would work well in your case: you
simply run this program to disable any drive (A-Z) before your son, or anybody
else has a chance to alter or destroy your files.

If you are interested, let me know.

Eric DeVolder
devolder@ksuvm.ksu.edu