From: "Johan Venter" Newsgroups: comp.os.msdos.djgpp References: <7tsjq3$65r AT acp3bf DOT knirsch DOT de> Subject: Re: How to configure rhide ? Lines: 31 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Message-ID: Date: Tue, 12 Oct 1999 13:04:21 +1000 NNTP-Posting-Host: 139.134.162.86 X-Trace: newsfeeds.bigpond.com 939723504 139.134.162.86 (Tue, 12 Oct 1999 20:18:24 EST) NNTP-Posting-Date: Tue, 12 Oct 1999 20:18:24 EST Organization: Telstra BigPond Internet Services (http://www.bigpond.com) To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hans-Bernhard Broeker wrote in message news:7tsjq3$65r AT acp3bf DOT knirsch DOT de... > The essence: _Don't_ start RHIDE by a desktop link with default > settings. At the very least, modify the 'working directory' setting in > the 'Program' tab of the properties of that link. It's usually simpler > to just start a DOS box, 'cd {your project directory}', and then type > 'rhide' from there. Here's some interesting behaviour I've found extremely useful in develpoment with Windows. I normally do all my coding in Windows with an Explorer window open. If you open an explorer window and change to any directory, it becomes the current directory for any other programs you care to load. For example: open an explorer box go to your djgpp directory (c:\djgpp for instance) go to start, then run and run 'bash' The bash shell starts with c:\djgpp as the current directory. The same is true if you replace bash with rhide. Another solution is to associate rhide with your .c files. Windows is smart enough to make the directory you load the c file from the current directory, so any executables you create from rhide will be in the same directory. -- Johan Venter ICQ 3643877 - jventer AT writeme DOT com The TPU DJGPP Interest Group - http://surf.to/djgppig The RSXNTDJ 1.5 HOWTO - http://surf.to/rsxntdj