Date: Sat, 06 Jan 2001 13:38:18 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: John Casey <jgcasey AT vic DOT ozland DOT net DOT au>
Message-Id: <8296-Sat06Jan2001133818+0200-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6
CC: djgpp AT delorie DOT com
In-reply-to: <3A561094.5DFA@vic.ozland.net.au> (message from John Casey on
	Sat, 06 Jan 2001 05:21:08 +1100)
Subject: Re: exe end up in bin folder
References: <3A554115 DOT 3760 AT vic DOT ozland DOT net DOT au> <934jhu$86$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <1190-Fri05Jan2001181934+0200-eliz AT is DOT elta DOT co DOT il> <3A561094 DOT 5DFA AT vic DOT ozland DOT net DOT au>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: John Casey <jgcasey AT vic DOT ozland DOT net DOT au>
> Newsgroups: comp.os.msdos.djgpp
> Date: Sat, 06 Jan 2001 05:21:08 +1100
> > >
> > > [This is all in the FAQ, too, I think.
> > 
> > Yes, in section 22.1.
> 
> I _did_ unzip and read djgppfag. section 22.1 is,
> 
> 22.1 Unzipping gppNNb.zip complains about g++.exe

This is an old version of the FAQ.  The latest one, v2/faq230b.zip,
has a different section 22.1, reproduced at the end of this mesage.
I suggest to upgrade to the latest FAQ, the previous version is very
old.

> I measure the user friendlyness of an interface or program by
> the degree to which you don't have to read the manual or FAQ.

There's limit to which you can learn a complex and powerful program
without reading the docs.

I don't maintain RHIDE (I don't even use it); I put that section in
the FAQ because it tends to be asked a lot.

------------------------------------------------------------------
22.1 Problems with using RHIDE.
===============================

_*Q*: Why does RHIDE put all my source files in the `C:\Windows\Desktop'
directory?_


_*Q*: RHIDE doesn't remember the path names of the files I edited in my
previous session...._


_*Q*: Why does RHIDE show the "Compile" option as disabled, although there's
a source file loaded?_


_*Q*: Sometimes, especially during debugging, RHIDE seems to screw up the
display, or crash, or blank the screen and hang.  How can I avoid this?_


*A*:  To prevent problems with source files not being found by RHIDE or being
put into strange directories, use a simple two-step recipe:

   * Always start RHIDE from the same directory where you want your sources
     to live.  On Windows, open a DOS box (you can use a shortcut to do
     that), change to the directory where you want to put your files using
     the `cd' command, then type `rhide FILE' from the command line, where
     FILE is either the name of the source file or the name of the project
     file, usually with a `.gpr' extension.

   * Use project files.  Start RHIDE from the directory of your project, as
     described above, then add the source files to the project using the
     `Project | Add' dialog from the main menu.  If you use a project file,
     you can have your source files in several different directories; in that
     case, start RHIDE from the directory where you keep the project file.

Alternatively, you could double-click on the project file for your project;
Windows will then invoke RHIDE in the directory of the project file.  You
might need to associate the `.gpr' extensions with RHIDE, before you can use
this feature.

By default, your program's `.exe' executable file goes to the same directory
where you keep the project file, but the `Project' dialog lets you specify a
different directory, in case you need that.

Display-related problems with RHIDE are usually caused by a faulty video
driver (on Windows 9X) or bugs in the SVGA firmware.  RHIDE uses advanced
VESA functions to save and restore the screen contents and mode-specific
settings, and some SVGAs and video drivers don't implement these functions
very well.  One particularly problematic SVGA card (which will remain
unnamed) has bugs even in the standard VGA modes.  Downloading the latest
video drivers from the vendor's site and upgrading the video BIOS usually
helps; if not, the only solution is to replace the video adapter.