[an error occurred while processing this directive]
Q: Why does RHIDE put all my source files in the
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
A: To prevent problems with source files not being found by RHIDE or being put into strange directories, use a simple two-step recipe:
cdcommand, 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
Project | Adddialog 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
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
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.