From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Warning:  is write protected in rhide
Date: 18 Sep 2000 13:31:14 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 15
Message-ID: <8q55f2$mal$1@nets3.rz.RWTH-Aachen.DE>
References: <WDUw5.6573$YG5 DOT 13679 AT tor-nn1 DOT netcom DOT ca>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 969283874 22869 137.226.32.75 (18 Sep 2000 13:31:14 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 18 Sep 2000 13:31:14 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Daniel <cdnhermit DOT msn AT attcanada DOT net> wrote:
> Hello, I checked the Faq, and rhide documentation and I could not find
> anything on: Warning: is write protected.

The only situation where I could imagine something like this happening
would be when you run RHIDE from some write-protected directory. Like
a CDROM, or maybe something copied or unpacked from CDROM. Some tools
have a habit of setting the read-only bit, in such cases.

If you're Windows'ing: be sure you open RHIDE not by clicking onto it,
but by opening a DOS box, 'cd'ing to the directory the source is in, and
*then* starting RHIDE from the command line.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.