From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: more RHIDE problems
Date: 21 Nov 2001 13:21:57 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 40
Message-ID: <9tg9pl$sqv$1@nets3.rz.RWTH-Aachen.DE>
References: <3bfa04d0 AT leia DOT ktsnet DOT com> <3bfa0617 AT leia DOT ktsnet DOT com> <9tdave$5ql$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <3bfad5bc AT leia DOT ktsnet DOT com>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 1006348917 29535 137.226.32.75 (21 Nov 2001 13:21:57 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 21 Nov 2001 13:21:57 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Cody <cody1 AT ktsnet DOT com> wrote:
>> How *exactly* do you start RHIDE?  What were the earlier problems you
>> hint at in the first message of this thread, and how did you overcome
>> those?
> I created a shortcut to RHIDE that merely calls c:\djgpp\bin\rhide.exe.  

And that's exactly how you should *not* do it.  

This creates exactly the kind of problem you're having: the current
working directory of the running RHIDE is going to be set up to be
c:\djgpp\bin or whichever the current directory your explorer points
at happens to be.  From there onwards, everything falls down.  It'll
write executables into c:\djgpp\bin, where you definitely shouldn't
put them.  You won't be able to directly open a .cpp file store
anywhere but in c:\djgpp\bin, where they *definitely* shouldn't ever
be.

> I never fixed the earlier problem.  Just turned my computer on one day (such
> as today), and it was magically fixed.  

It wasn't fixed, it just happend to work by good luck.

> I did nothing different in the way I called rhide, opened the file,
> or nothing else.

>> Open a DOS box
>> 'cd' to the directory with your source in
>> rhide one         (or whatever it's called)
>> add 'one.c' to the project
>> Select 'Run' from the menu

> I do not use project files when compiling my programs.  

Please, if just for the sake of experiment, *do* try the above recipe
once before dismissing it just because you don't think you want to use
projects.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.