[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:AMIGA NOTES
Notice:Join us in the *NEW* conference - HYDRA::AMIGA_V2
Moderator:HYDRA::MOORE
Created:Sat Apr 26 1986
Last Modified:Wed Feb 05 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:5378
Total number of notes:38326

3746.0. "Hard Drive "protection"" by WHAMMY::SPODARYK (Binary Throttle) Thu May 03 1990 10:45

I was wondering if there might be a program/method of "write-protecting"
your hard drive.  I don't know enough of the specifics to know for sure,
but it seems like someone could write something that checks when a write 
is issued by your hard drive device ("hardframe.device", whatever), 
and puts up a requester saying "writes not allowed to device X:".

Is it possible, has it been done, or am I all wet?

Steve
T.RTitleUserPersonal
Name
DateLines
3746.1WJG::GUINEAUThu May 03 1990 10:463
I believe the AmigaDOS  LOCK command does this.

john
3746.2LockNBOIS2::FRIESThu May 03 1990 10:492
    There is a program called 'Lock' in my c: directory, which
    write protects the HD (optional with a password).
3746.3SetFunction, your favorite hackers tool...FROCKY::BALZERChristian Balzer DTN:785-1029Thu May 03 1990 11:086
Besides the more generic (and not always sufficient) LOCK command,
you may very well write a routine using SetFunction() that intercepts 
Writes() to a(ny) device.

<CB>
3746.4NSSG::SULLIVANSteven E. SullivanThu May 03 1990 14:3713
For those with a HardFrame and 1.5C (Or thereabouts) ROM in it you can make
a partition write protected by setting the "mount" bit in the RDB to zero.
Technically, this is a bug, but is fixed in beta versions of the Hardframe 
driver and a proper write protect flag is supported.

The RDPrep program makes this change easy to do. Just select the drive and 
modify the partition settings.

For those with BIX access there is a graphic user interface version available in
Microbotics/Listings.

	-SES
.
3746.5Could someone upload RDPrep? pleaseLODGE::LENDavid M. LenThu May 03 1990 19:439
>For those with BIX access there is a graphic user interface version available in
>Microbotics/Listings.
    
    I have a Hardframe, but do not have the new version of RDPREP.  I also
    don't have an account on BIX.  I would appreciate it if someone that
    has this lastest version would upload it so I could get it from the
    net.  Thanks.
    
3746.6LOCK is not permanentULTRA::KINDELBill Kindel @ BXB1Fri May 04 1990 11:514
    For those attempting to use LOCK, you should know that it's a SOFTWARE
    lock only.  You need to set it in SYS:s/startup-sequence so that it
    takes effect each time you boot.  It will NOT protect your hard disk
    partitions from tampering by whatever (games, etc.) you boot in DF0.
3746.7WJG::GUINEAUFri May 04 1990 12:067
And unfortuenatly, SCSI has no standard means of write protecting a device. 
You can ask a device if it's write protected, but you can not tell it to 
write protect itself.

Write protect is accomplished via a jumper on devices which support it.

john
3746.8Kronos Can (I think)CACHE::BEAUREGARDTime to change this messageFri May 04 1990 12:489
    If I remeber correctly, the Kronos controller will allow you to write
    protect a disk. I think there is a field in the devsetup (don't
    ask) that provides for this. This protection is at the device driver 
    level and is perhaps more secure than the AmigaDos lock. I'm not sure
    if you can un-protect/re-protect the disk without generating a new
    devsetup.
    
    Roger
    
3746.9Beware of LOCKVCSESU::MOORETom Moore MRO1-3/SL1 297-5224Fri May 04 1990 13:3311
re:.6
<<  For those attempting to use LOCK, you should know that it's a SOFTWARE
<<  lock only.  

    Also beware that it is not completely effective. If you LOCK the drive
    and then reset Preferences, the next time you boot you will get the
    reset values rather than the "locked" values. This was my experience
    when showing the salesman down at Leiser how LOCK works on a A500 with a
    A590. I said "See there is no change. Oops! Sorry about that."

    -Tom-
3746.10thanksWHAMMY::SPODARYKBinary ThrottleFri May 04 1990 14:526
Thanks for the answers folks.  It seems I should pay more attention to
my documentation.  Like last week when I wanted to change my workstation's
time, I asked someone who replied "try - $set time=xxx".  How obvious can
it get?

Steve
3746.11BAGELS::BRANNONDave BrannonFri May 04 1990 18:098
    the best "lock" I've found is an external disk drive box that
    can be powered off separately from from the computer.  I assume
    a similar power off switch could be done for internal harddrives.
    That guarantees nothing will get written to the disk by some program
    going wild.  Of course it's not terribly useful powered off, but
    it is safe from harm.
    
    -Dave
3746.12ALFprotectFRSOLD::ZIMMERMANNWer von Euch Kerls ist KowalskiSat May 05 1990 15:116
    
    Alf-users have the Alfprotect (v1.6/can't remember the v2.0-name)
    to select between protection against format or write.
    
    Ralf
    ====
3746.13SyQuest drives support hardware write protectionTPWEST::MJJONESCursed with a pornographic memoryTue May 22 1990 15:214
The SyQuest 44mb removable media hard drives support hardware write protection.
Each 44mb cartridge has a write-protect device that can be enabled (same
function as the slider on the 3 1/2" floppies).  This activates a HARDWARE
protect, and it works (really).  See topic 3789 for more details.